...
Show policy-map interface x/y doesnt show expected pkt counters under respective class, issue observed post router reload or LC reload. QoS classification is broken, traffic can also get classified under incorrect Class MAP or can bypass all class-maps. Note: No traffic loss or forwarding issues expected.
Issue has been seen on ASR9K having Bundle interface (with QoS) + Sub interface(without QoS) Possible Trigger: 1. Chassis reload 2. Line card reload/reset 3. subslot SPA/MPA reload/reset. 4. removing and adding all bundle members Condition I: main + sub interface config and Condition II: Service policy applied only on main interface and not sub-interface RP/0/RSP0/CPU0:#sh uidb data loc 0/0/cpu0 bundle-e 41 egress | i $ QOS Enable 0x1 QOS ID NP0 0x2048 QOS ID NP1 0x2000 QOS Format 0x11 TCAM QOS ACL FORMAT 0x1 RP/0/RSP0/CPU0:#sh uidb data loc 0/0/cpu0 bundle-e 41.212 egress | i QOS QOS Enable 0x0 >>> does not match primary bundle UIDB DATA 0x1 QOS ID NP0 0x0 >>> does not match primary bundle UIDB DATA 0x2048 QOS ID NP1 0x0 >>> does not match primary bundle UIDB DATA 0x2000 QOS Format 0x0 >>> does not match primary bundle UIDB DATA 0x11 TCAM QOS ACL FORMAT 0x
Removing and reapplying the service policy under the main interface may resolve the issue but not 100%. while reapplying the policy on the main interface if PM returns sub-interface list as zero again will hit the same issue even with reapply. Example let's say here is the bundle-eth config: RP/0/RSP0/CPU0:ASR9001-E#sh run int bundle-eth 41 Tue Oct 30 07:24:42.171 EDT interface Bundle-Ether41 mtu 9216 service-policy output ABCD bundle minimum-active links 1 load-interval 30 Workaround is: int bundle-eth 41 no service-policy output ABCD commit service-policy output ABCD commit
The issue was seen post Code upgrade As part of the upgrade process the chassis was reloaded. Post the chassis reload LC were reloaded for FPD upgrade.