Cisco Bug: CSCun62019 - Reg 6.1.5 S7 : WCCP Packets loop because of incorrect labels
Mar 17, 2016
- Cisco Nexus 7000 Series Switches
Known Affected Releases
Symptom: 1) WCCP packets start looping. That is, they hit the egress wccp ACL, goto the cache, and come back and hit the WCCP ACL again. This happens till the TTL (time to live) of the packet becomes Zero. 2) The labels on the interface where Egress WCCP is applied look incorrect. 3) Egress WCCP will not work the way it is expected. The packet will never get out of the switch. Conditions: This bug is hit only if all the following conditions are met. 1) ACLQoS process restarts. This normally happens during ISSU ( In-Service Software Upgrade) or after an ACLQoS crash. 2) Egress WCCP is present before and after restart. It is removed or reapplied before and after the process restart. 3) A reparse should happen on that interface. This can be triggered by applying any Egress policy on the same interface (where the WCCP Egress policy is present), after the process restart.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases