General

The SNMP index of the egress policies we have configured is missing on several Bundle-Ether Interfaces.For BE11 and BE12, there is no information about outbound qos queue bit/s. For BE16, it works fine.The SNMP index of the egress policies we have configured is missing on several Bundle-Ether Interfaces.For BE11 and BE12, there is no information about outbound qos queue bit/s. For BE16, it works fine.For BE11(ifindex 1206), we can see that we only have ingress policy index.RP/0/RP0/CPU0:bx03.iad23#show snmp interface bundle-ether 11 ifindex Mon Mar 16 14:22:06.426 PDTifName : Bundle-Ether11 ifIndex : 1206ifName : Bundle-Ether12 ifIndex : 1207ifName : Bundle-Ether16 ifIndex : 1331qideng@nbh1-new:~$ snmpwalk -c public -v 2c bx03.iad23.net 1.3.6.1.4.1.9.9.166.1.2.1.1iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1197.1 = Gauge32: 1446755488iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1206.1 = Gauge32: 2078029712>>>>>>>>>>BE11iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1207.1 = Gauge32: 188101793>>>BE12iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1331.1 = Gauge32: 677941965>>BE16 ingressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1331.2 = Gauge32: 1827653290>>BE16 egressSince Bundle-ethe 11, bundle-eth 12 on lc 0/4/cpu0 , so workaround can try restart this process only on lc 0/4/cpu0 #process restart mibd_interface location 0/4/cpu0after workaround:=======The proposed workaround appears to have worked, I see both MIBs for the interfaces in question. nwinemiller@nbh1-new:~$ snmpwalk -c public -v 2c bx03.iad23.net 1.3.6.1.4.1.9.9.166.1.2.1.1iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1206.1 = Gauge32: 2078029712---BE11-ingressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1206.2 = Gauge32: 1266264741---BE11--egressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1207.1 = Gauge32: 188101793---BE12-ingressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1207.2 = Gauge32: 544924422---BE12-egressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1331.1 = Gauge32: 677941965---BE16 ingressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1331.2 = Gauge32: 1827653290--BE16 egress

Symptom

Missing Qos MIB entries. The configuration (show running-config ) and QoS MIB Polled result are not in sync.

Conditions

Workaround: =======The proposed workaround appears to have worked, I see both MIBs for the interfaces in question. nwinemiller@nbh1-new:~$ snmpwalk -c public -v 2c bx03.iad23.net 1.3.6.1.4.1.9.9.166.1.2.1.1iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1206.1 = Gauge32: 2078029712---BE11-ingressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1206.2 = Gauge32: 1266264741---BE11--egressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1207.1 = Gauge32: 188101793---BE12-ingressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1207.2 = Gauge32: 544924422---BE12-egressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1331.1 = Gauge32: 677941965---BE16 ingressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1331.2 = Gauge32: 1827653290--BE16 egress

Symptom

Missing Qos MIB entries. The configuration (show running-config ) and QoS MIB Polled result are not in sync.

Conditions

Workaround

Restart mibd_interface process on the RP. On restart the entire config will be replayed. #process restart mibd_interface after workaround: ======= The proposed workaround appears to have worked, I see both MIBs for the interfaces in question. nwinemiller@nbh1-new:~$ snmpwalk -c public -v 2c bx03.iad23.net 1.3.6.1.4.1.9.9.166.1.2.1.1iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1206.1 = Gauge32: 2078029712---BE11-ingress iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1206.2 = Gauge32: 1266264741---BE11--egressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1207.1 = Gauge32: 188101793---BE12-ingress iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1207.2 = Gauge32: 544924422---BE12-egress iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1331.1 = Gauge32: 677941965---BE16 ingress iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1331.2 = Gauge32: 1827653290--BE16 egress

Further Problem Description