Cisco Bug: CSCun00910 - Need a Trident NP global counter for flood drop on egress Resolve
Oct 24, 2018
- Cisco ASR 9000 Series Aggregation Services Routers
Known Affected Releases
4.1.0.BASE 4.2.0.BASE 4.3.0.BASE 5.1.0.BASE
Symptom: When L2 flood traffic drop is done on egress NP in Resolve, ucode uses RESOLVE_VPLS_REFLECTION_FILTER_DROP global counter and also increase the output Generic drop counter on the interface. This causes fake error counters being incremented on these interfaces, thus impeding the ability to monitor these interfaces. Conditions: When RESOLVE_VPLS_REFLECTION_FILTER_DROP drop is on ingress NP, it shows how many L2 frames are dropped due to enforcing IEEE 802.1D loop prevention rules. This is real, but normal traffic drop. The drop counter should be reflected in the input drop of "show interface ...". RESOLVE_VPLS_REFLECTION_FILTER_DROP drop can also shows up on egress NP. When the drop is accounted as egress NP drop, the drop is not a real traffic drop. To help customer differentiate ingress drop vs. egress drop, DE team has stopped using RESOLVE_VPLS_REFLECTION_FILTER_DROP counter on egress NP.
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