Am I missing something here or does below QOS counter output (C3850) not make any sense?
Output counters differ between parent and child (But there's only 1 child and 1 parent...)
- Bytes are allegedly output in priority queue but the priority class matches 0
- No packets match any classes but packets are being output not dropped (confirmed via show interface as well)
Only sane conclusion is that counters are not to be trusted
Note: this is a lab switch - reproducing a field issue (basically reproduced it, in a roundabout way... the 'real' unit has 0s across the board as to counters but there are no drops either)
me-ld8r07-esw04#sh policy-map int g1/0/3GigabitEthernet1/0/3 Service-policy output: PM-TESTQOS-50M-PARENT Class-map: class-default (match-any) 0 packets Match: any Queueing (total drops) 0 (bytes output) 366228586 shape (average) cir 990000000, bc 3960000, be 3960000 target shape rate 990000000 Service-policy : PM-TESTQOS-50M-CHILD queue stats for all priority classes: Queueing (total drops) 0 (bytes output) 112407452 Class-map: CM-TESTQOS-VOICE (match-any) 0 packets Match: dscp ef (46) 0 packets, 0 bytes 30 second rate 0 bps Priority: 20000 kbps, burst bytes 500000, Class-map: class-default (match-any) 0 packets Match: any (total drops) 0 (bytes output) 253821134 Config is bare-bones testing
class-map match-any CM-TESTQOS-VOICE match dscp ef policy-map PM-TESTQOS-50M-CHILDclass CM-TESTQOS-VOICE priority 20000class class-defaultpolicy-map PM-TESTQOS-50M-PARENTclass class-default shape average 990000000 service-policy PM-TESTQOS-50M-CHILD
QoS is done in hardware on the switches so counters arent ever right in my experience. The "show policy-map interface" command doesnt work for me, either on my switches. And it threw me for a bit in the past also.