On Dec 21, 2008, at 7:44 PM, bradford wrote: > Not sure if anyone can help, but I have a problem with the 64 bit > ethernet counters. For some unknown reasons the returned values are > out for some interface but not others. See Below > > # snmpwalk -c public -v 2c 192.168.x.x 1.3.6.1.2.1.2.2.1.10 (32bit) > IF-MIB::ifInOctets.1 = Counter32: 499059965 > IF-MIB::ifInOctets.2 = Counter32: 1932051719 > IF-MIB::ifInOctets.3 = Counter32: 1062712220 > IF-MIB::ifInOctets.5 = Counter32: 0 > IF-MIB::ifInOctets.6 = Counter32: 0 > IF-MIB::ifInOctets.7 = Counter32: 2140404854 > IF-MIB::ifInOctets.8 = Counter32: 2105147657 > IF-MIB::ifInOctets.9 = Counter32: 4223502538 > IF-MIB::ifInOctets.10 = Counter32: 442742587 > IF-MIB::ifInOctets.11 = Counter32: 177212384 > > # snmpwalk -c public -v 2c 192.168.x.x 1.3.6.1.2.1.31.1.1.1.6 (64bit) > IF-MIB::ifHCInOctets.1 = Counter64: 442880756905 > IF-MIB::ifHCInOctets.2 = Counter64: 1393501799509 > IF-MIB::ifHCInOctets.3 = Counter64: 1062712220 > IF-MIB::ifHCInOctets.6 = Counter64: 0 > IF-MIB::ifHCInOctets.7 = Counter64: 2140404854 > IF-MIB::ifHCInOctets.8 = Counter64: 414422035866 > IF-MIB::ifHCInOctets.9 = Counter64: 25698360350 > IF-MIB::ifHCInOctets.10 = Counter64: 442788359 > IF-MIB::ifHCInOctets.11 = Counter64: 177237392 > > # snmpwalk -c public -v 2c 192.168.x.x 1.3.6.1.2.1.2.2.1.2 > IF-MIB::ifDescr.1 = STRING: GigabitEthernet0/0 > IF-MIB::ifDescr.2 = STRING: GigabitEthernet0/1 > IF-MIB::ifDescr.3 = STRING: Analysis-Module1/0 > IF-MIB::ifDescr.5 = STRING: Null0 > IF-MIB::ifDescr.6 = STRING: Loopback0 > IF-MIB::ifDescr.7 = STRING: GigabitEthernet0/0.1 > IF-MIB::ifDescr.8 = STRING: GigabitEthernet0/0.184 > IF-MIB::ifDescr.9 = STRING: GigabitEthernet0/0.191 > IF-MIB::ifDescr.10 = STRING: GigabitEthernet0/0.185 > IF-MIB::ifDescr.11 = STRING: GigabitEthernet0/0.190 > > # snmpwalk -c public -v 2c 192.168.x.x 1.3.6.1.2.1.31.1.1.1.1 > IF-MIB::ifName.1 = STRING: Gi0/0 > IF-MIB::ifName.2 = STRING: Gi0/1 > IF-MIB::ifName.3 = STRING: An1/0 > IF-MIB::ifName.5 = STRING: Nu0 > IF-MIB::ifName.6 = STRING: Lo0 > IF-MIB::ifName.7 = STRING: Gi0/0.1 > IF-MIB::ifName.8 = STRING: Gi0/0.184 > IF-MIB::ifName.9 = STRING: Gi0/0.191 > IF-MIB::ifName.10 = STRING: Gi0/0.185 > IF-MIB::ifName.11 = STRING: Gi0/0.190 > > As you can see Gi0/0, Gi0/1, Gi0/0.184 and Gi0/0.191 are different > when comparing to the 32 bit OID, but An1/0, Lo0, Gi0/0.1, Gi0/0.185 > and Gi0/0.190 are the same/similar (commands were run seconds apart). > > I am certain the 64 bit values are wrong as they show terabytes and > over 22 gigabyte utilisation. I've reverted back to the 32bit OID, > but would like to use the 64bit onces as the interfaces are 1Gb.
It's completely normal for these numbers to differ. These numbers are the total number of bytes that have passed through the interface since the device was powered on. However, the 32bit counter has likely rolled over (meaning starting over at 0 once it reached the maximum number storable in a 32bit integer) more times than the 64bit counter. This is what leads to the discrepency. Zenoss is only recording the delta (difference between the value at last check and current check) and not the total number. _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
