Partial result from SNMP queries

[cmdickey]

We have several cisco switches set up in our data center, and we would like to track the port bandwidth i/o for billing purposes. We recently switched from using MRTG w/rrdtool to using Cacti. However, we create the device and associated graphs for all ports, and these errors creep in. The graphs are therefore never created.

What is the deal? I have searched through many forums, without a direct answer for my issue.

Thanks in advance for any help!


08/07/2006 01:00:05 PM - CMDPHP: Poller[0] Host[5] SNMP: v1: 209.237.248.3, dsna me: traffic_in, oid: .1.3.6.1.2.1.31.1.1.1.6.9, output: U

08/07/2006 01:00:05 PM - CMDPHP: Poller[0] Host[5] WARNING: Result from SNMP not valid. Partial Result:

[BSOD2600]

That OID is no longer valid. Click the green circle for the device under associated data queries to refresh the index.

[cmdickey]

Nothing...no dice. Still giving errors.

[gandalf]

Please perform an snmpget from command line against that very device, using the OID from the error message, and post the results
Reinhard

[cmdickey]

Code: Select all

agave:~# snmpget -v 1 -c .... 209.237.XXX.XX ifHCInOctets           
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: IF-MIB::ifHCInOctets

[cmdickey]

Code: Select all

agave:~# snmpwalk -Os -c .... -v 1 209.237.248.12 1.3.6.1.2.1.2.2.1.10.14
ifInOctets.14 = Counter32: 982765451

agave:~# snmpwalk -Os -c .... -v 1 209.237.248.12 1.3.6.1.2.1.2.2.1.10.14
ifInOctets.14 = Counter32: 982766267

I can obviously see it counting : \
[/code]

[gandalf]

Code: Select all

agave:~# snmpget -v 1 -c .... 209.237.XXX.XX ifHCInOctets           
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: IF-MIB::ifHCInOctets

HC Conters (aka 64bit Counters) are _not_ supported with snmp v1
Reinhard

[gandalf]

Code: Select all

agave:~# snmpwalk -Os -c .... -v 1 209.237.248.12 1.3.6.1.2.1.2.2.1.10.14
ifInOctets.14 = Counter32: 982765451

agave:~# snmpwalk -Os -c .... -v 1 209.237.248.12 1.3.6.1.2.1.2.2.1.10.14
ifInOctets.14 = Counter32: 982766267

I can obviously see it counting : \
[/code]

Those counters are 32 bit ones that _must_ be supported. Conclusion: please use 32 bit counters on your target unless you verified the 64 bit one's from comand line using snmp v2c.
BTB: NEVER post snmp community strings (so I had to edit your post)

Reinhard

[cmdickey]

They are all simple i/o bit counters...dunno what's wrong with em.

Could there be any other reason?