Symptom

Getting WRONG bit-rate value which is more than the line rate of the physical interface when the object cbQosCMPostPolicyBitRate is being polled for the class-default class-map under the child policy within the parent policy that applied on the interface. All other defined classes under the same child policy reporting CORRECT bit-rate value. Down below is the collected wrong bit-rate value when the object cbQosCMPostPolicyBitRate is being polled for the class-default class-map under the child policy applied on the sub-interface Gi0/0/2.201 Step-1: Getting the IfIndex for the interface where the policy-map Parent Qos policy is applied by using ?show snmp mib ifmib ifindex? command on the router itself router1#sh snmp mib ifmib ifindex | i GigabitEthernet0/0/2.201 GigabitEthernet0/0/2.201: Ifindex = 33 The IfIndex for the subinterface is (33) Step-2: Getting the cbQosIfIndex on that interface by polling this OID (1.3.6.1.4.1.9.9.166.1.1.1.1.4) from the SNMP poller. % snmpwalk -v 2c -c $SECRET router1 1.3.6.1.4.1.9.9.166.1.1.1.1.4 SNMPv2-SMI::enterprises.9.9.166.1.1.1.1.4.114 = INTEGER: 7 SNMPv2-SMI::enterprises.9.9.166.1.1.1.1.4.530 = INTEGER: 33 The cbQosIfIndex on the sub-interface Gi0/0/2.201 is (530) Step-3: Getting the cbQosConfigIndex for the class-default class-map by polling this OID (1.3.6.1.4.1.9.9.166.1.7.1.1.1) from the SNMP poller. % snmpwalk -v 2c -c $SECRET router1 1.3.6.1.4.1.9.9.166.1.7.1.1.1 SNMPv2-SMI::enterprises.9.9.166.1.7.1.1.1.1593 = STRING: "class-default" <<<< SNMPv2-SMI::enterprises.9.9.166.1.7.1.1.1.276368515 = STRING: "CM-TEST1" SNMPv2-SMI::enterprises.9.9.166.1.7.1.1.1.277951569 = STRING: "CM-TEST2" SNMPv2-SMI::enterprises.9.9.166.1.7.1.1.1.318762642 = STRING: "CM-TEST3" SNMPv2-SMI::enterprises.9.9.166.1.7.1.1.1.319004883 = STRING: "CM-TEST4" SNMPv2-SMI::enterprises.9.9.166.1.7.1.1.1.329185212 = STRING: "CM-TEST5" SNMPv2-SMI::enterprises.9.9.166.1.7.1.1.1.367901553 = STRING: "CM-TEST6" SNMPv2-SMI::enterprises.9.9.166.1.7.1.1.1.369014409 = STRING: "CM-TEST7" SNMPv2-SMI::enterprises.9.9.166.1.7.1.1.1.380364054 = STRING: "CM-TEST8" SNMPv2-SMI::enterprises.9.9.166.1.7.1.1.1.385515072 = STRING: "CM-TEST9" SNMPv2-SMI::enterprises.9.9.166.1.7.1.1.1.385515073 = STRING: "CM-TEST10" SNMPv2-SMI::enterprises.9.9.166.1.7.1.1.1.385515074 = STRING: "CM-TEST11" SNMPv2-SMI::enterprises.9.9.166.1.7.1.1.1.387763000 = STRING: "CM-TEST12" SNMPv2-SMI::enterprises.9.9.166.1.7.1.1.1.392167379 = STRING: "CM-TEST13" The cbQosConfigIndex for class-default is (1593) Step-4: Polling this OID (1.3.6.1.4.1.9.9.166.1.5.1.1.2) with cbQosIfIndex (530) to get the cbQosObjectsIndex. Since there is a hierarchical policy applied on the interface we are getting 2 cbQosObjectsIndex values for the class-default 65536 is cbQosObjectsIndex for class-default under the parent policy Policy-map1 1048576 is cbQosObjectsIndex for class-default under the child policy Policy-map2 % snmpwalk -v 2c -c $SECRET router1 1.3.6.1.4.1.9.9.166.1.5.1.1.2 | grep 1593 SNMPv2-SMI::enterprises.9.9.166.1.5.1.1.2.114.65536 = Gauge32: 1593 <<< interface Gi0/0/1 SNMPv2-SMI::enterprises.9.9.166.1.5.1.1.2.114.1048576 = Gauge32: 1593 <<< interface Gi0/0/1 SNMPv2-SMI::enterprises.9.9.166.1.5.1.1.2.530.65536 = Gauge32: 1593 <<< interface Gi0/0/2.201 SNMPv2-SMI::enterprises.9.9.166.1.5.1.1.2.530.1048576 = Gauge32: 1593 <<< interface Gi0/0/2.201 Step-5: performing SNMPwalk for this OID (1.3.6.1.4.1.9.9.166.1.15.1.1.11) using cbQosIfIndex (530) and cbQosObjectsIndex (1048576) for the class-default class-map under the child policy. snmpwalk -v2c -c $SECRET router1 1.3.6.1.4.1.9.9.166.1.15.1.1.11.530.1048576 SNMPv2-SMI::enterprises.9.9.166.1.15.1.1.11.530.1048576 = Gauge32: 4294854296 <<<< ubuntu % snmpget -v2c -c $SECRET router1 1.3.6.1.4.1.9.9.166.1.15.1.1.11.114.1048576 SNMPv2-SMI::enterprises.9.9.166.1.15.1.1.11.114.1048576 = Gauge32: 4294840296 As we can see the returned bit-rate value is 4.2 Gbps which is more than the line rate of the GigabitEthernet physical interface.

Conditions

1- H-QoS is applied on the interface whether physical interface of logical sub-interface. 2- ASR1k is running in controller mode.

Workaround

None

Further Problem Description