Cisco Bug: CSCur47054 - Issue with updating Ingress WCCP with Egress label
Feb 03, 2017
- Cisco Catalyst 3850 Series Switches
Known Affected Releases
Symptom: Symptom 1) Egress WCCP not working on cat3850. Traffic is not getting redirected. 2) Traffic egressing on routed interfaces that have wccp on the ingress direction are being subjected to egress racls configured on some other routed interfaces. Conditions: 1) This problem will arise in certain scenario when ingress wccp is configured along with egress wccp on the same interface. The problem will only be seen if ingress wccp is applied after egress wccp which updates the egress label causing the problem. The problem will also be seen if ingress wccp is removed causing the label to be unset on egress wccp. 2) L3 interface A (port or svi) configured with an egress racl. L3 interface B configured with wccp on the ingress direction. Now traffic being routed out of B will be subjected to the egress racl of A. A and B are independent entities with no common config.
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