This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

wrong util and interface load data due to ifMib counter rollovers. How to make sure it uses ifXmibs?

 Hi:

 We are using Orion NPM version 8.1.0

We have a gigabit ethernet over which a large amount of data are transferred. During this transfer, the actual interface util is observed around 80% (800mbps). This util is observed on the device and by a 3rd party snmp poller/charting program.

However, on Orion, we see only 100mbps at most during the transfer. We know this is wrong. But when there is not much traffic on the link, Orion chart on this interface appears to be accurate.

I followed the thread below and checked the snmp poller packets with ethereal.  

 It clearly shows it polls only if-mibs, rather than ifx-mibs.

Clearly, this error is caused by using ifTable. Orion should use ifXTable on this device/interface.

When the load is 800Mb/s, the 5 minute (our poll interval) Out_TotalByte should be around 3*10^10. This causes 32bit counters rollover multiple times.

This device is a Cisco WS-C6509. version 6.4. The ifXTable is supported by the device as a 3rd party snmp poller can poll it.

So, my question is: how to make sure the ifXTabel is polled? Also, how to make sure it is set correctly for all devices? as we have quite some interfaces that could cause ifmibs rollover.

  • found the node detail window has a check "enable 64 bit counter". Maybe this will solve the problem. 


    because there are handreds of nodes, I tried update the Nodes table and set "Allow64BitCounters" to 1. However, when I open Orion Network Performace Monitor console, node details still show "Allow 64 bit counters" as unchecked. 


    Where else should I change to make all devices allow 64 bit counters? What are some concerns to enable this? I mean, why is the  "Allow64BitCounters" set to False by default?

  • Enabled "Allow 64 Bit Counters" for all devices in database. The trick is to restart the NPM after the change in database. Otherwise, the changes will be rolled back somehow.