Symptom

HQoS policy is applied on egress interface Priority Queue level 1 and Priority Queue level 2 have policer configured Actual allowed traffic rate conforming though this policer will be higher than the configured value Issue seen on Cat3650 Mini switch but not on Cat9300 example policy ! class-map match-any CL1_OUT match qos-group 1 class-map match-any CL2_OUT match qos-group 3 class-map match-any CL3_OUT match qos-group 6 class-map match-any CL4_OUT match qos-group 4 class-map match-any CL5_OUT match qos-group 2 class-map match-any CL6_OUT match qos-group 0 class-map match-any CL7_OUT match qos-group 5 ! policy-map EGRESS_WAN class CL7_OUT priority level 1 police cir percent 10 conform-action transmit exceed-action drop queue-limit 1000 packets class CL4_OUT priority level 2 police cir percent 30 conform-action transmit exceed-action drop queue-limit 2000 packets class CL3_OUT bandwidth remaining percent 5 queue-limit 7500 packets class CL2_OUT bandwidth remaining percent 20 queue-limit 7500 packets class CL5_OUT bandwidth remaining percent 20 queue-limit 7500 packets class CL1_OUT bandwidth remaining percent 29 queue-limit 15000 packets class CL6_OUT bandwidth remaining percent 25 queue-limit 20000 packets policy-map EGRESS_WAN_SHAPED class class-default shape average 1750000 service-policy EGRESS_WAN ! ! egress interface interface range Te1/1/4 service-policy output EGRESS_WAN_SHAPED

Conditions

Cat3650 mini [and possibly other Cat3650/Cat3850 switches] Fuji-16.9.1 software HQoS service policy with Policer applied on Priority Level 1 and Priority Level 2 queues

Workaround

decrease the configured policer values to compensate for policer inaccuracy

Further Problem Description