Did this every resolve itself? If so, would you mind posting for the community?
1 of 1 people found this helpful
This is what we typically use, do a MIB walk and let us know what you see
OID = ifAlias
OID = ifName
32bit Counter based
OID = ifInOctets
OID = ifInUcastPkts
OID = ifInNUcastPkts
OID = ifOutOctets
OID = ifOutUcastPkts
OID = ifOutNUcastPkts
64bit Counter based
OID = ifHCInOctets
OID = ifHCInUcastPkts
OID = ifHCInMulticastPkts
OID = ifHCOutOctets
OID = ifHCOutUcastPkts
OID = ifHCOutMulticastPkts
I'll give it a try when i can get into the office and post the results.
The "speed" of the interface is taken from 220.127.116.11.18.104.22.168.1.5 - ifspeed
There is only one value stored in the mib table and this is used for both the tx and rx bandwidth. A limitation of SNMP so I guess this should be expected.
I have done a MIB walk on the OID's suggested by bshopp and darryld's comment is spot on, it is only reported on 22.214.171.124.126.96.36.199.1.5 as being 256k, the Mib makes no mention of the higher bandwidth rate on the recieve side, so what NPM is displaying is correct as far as it's what the device is reporting.
I guess i'll just have to keep manually entering the values.
Cheers for the information.
As the information is contained in the SNMPv2-SMI::transmission MIB (For example 857 router would be SNMPv2-SMI::transmission.188.8.131.52.1.2.12 and SNMPv2-SMI::transmission.184.108.40.206.1.2.12) is there a way to automate the input of these values into the interface speed?