Missing MIB instance

nicholas_ong · ‎11-24-2010

Hi Guys,

I have an issue here monitoring one of the sub-interfaces on a client's router. And I have no clue, any suggestions?

There are a few working instances of the OID for the monitoring of other links (also on sub-interfaces) out but this in particular doesn't and I can't figure out why.

An SNMP get at this interface index shows missing instances which is required for our NMS to work.

IF-MIB::ifAdminStatus.17 = INTEGER: up(1)

IF-MIB::ifOperStatus.17 = INTEGER: up(1)

IF-MIB::ifInOctets.17 = Counter32: 2683738196

IF-MIB::ifOutOctets.17 = Counter32: 2587587602

IF-MIB::ifInUcastPkts.17 = Counter32: 276106163

IF-MIB::ifInNUcastPkts.17 = No Such Instance currently exists at this OID

IF-MIB::ifOutUcastPkts.17 = Counter32: 4244077444

IF-MIB::ifOutNUcastPkts.17 = No Such Instance currently exists at this OID

IF-MIB::ifInErrors.17 = No Such Instance currently exists at this OID

IF-MIB::ifOutErrors.17 = No Such Instance currently exists at this OID

IF-MIB::ifInDiscards.17 = No Such Instance currently exists at this OID

IF-MIB::ifOutDiscards.17 = No Such Instance currently exists at this OID

Interface Configuration

interface FastEthernet0/1.114
bandwidth 8192
encapsulation dot1Q 114
ip address *removed*
ip flow ingress
ip flow egress
no cdp enable

Cisco IOS Version

c2800nm-advipservicesk9-mz.124-9.T.bin

Any help provided will be deeply appreciated.

Joe Clarke · ‎11-25-2010

It sounds like your NMS may be a bit archaic when it comes to sparse table handling. Most NMSes these days can handle situations where certain objects in a table are not instantiated. What you can do to workaround this is to configure:

no snmp-server sparse

When you do that, the missing objects should be instantiated with 0 values.

nicholas_ong · ‎12-09-2010

Thanks for the reply Joseph, I'm not sure whether that is the cure for this issue. We are suspecting that the router might have gone bonkas and though we may kinow after a reboot to the device. Anyway, the stats for that link is of lesser priority now since it'd be replaced shortly, so we have decided to ignore the issue for now.