search cancel

How to determine if a counter in a MIB is broken


Article ID: 36450


Updated On:


CA eHealth


A large delta error is reported when the delta between the counter value for the last poll and the counter value for the current poll counter reaches or exceeds 50% of its maximum value.  For a 32 bit counter the error is reported when this value is is 2^31 (2147483648) or greater.  For a 64 bit counter the error is reported when this value is is 2^63  (9223372036854775808) or greater

Background: You may find “No Data Available” in a report for a specific interface.

The first thing to check is to see if there are polling errors. You may see the following:

Received large delta from 'ABCDEFG1-GigabitEthernet0/1'. Poll is dropped (OID in error is ifInBroadcastPkts. Delta is 4294967286. Old value is 4294866507. Current value is 4294866497.)

eHealth all platforms, all versions

There are 2 possible causes for this type of error message. The most common cause is a broken counter.

This solution is designed to provide you a method to find the solution appropriate to your case.

The 2 possible causes are:

1. Fast Network Link
The speed of the device is so fast (> 10MB) that the counters are wrapping within the time interval of the polling cycle. Switch the polling speed to Fast Polling. Sometimes a device (such as a core network router) can have such a large amount of traffic that it appears to be a problem. By changing to fast polling, you decrease the amount of time the counter has to change and therefore reduce the likeliness that device speed is the cause. If the large delta messages continue, go to step #2.

2.  Mib Agent Failure

The MIB agent on the device in question has a broken counter.
For every mib object there is an Object Type: Counter or a Gauge.

A broken counter can be defined as a counter that does not increment, yet decrements.

No counters should ever decrement and therefore this would be considered a software bug initiated by the vendors’s mib agent / software. To verify a broken (decrementing) counter, use the example below:

1. In eHealth One Click—Managed Resources---Elements: Select the element, right-click
and run “Element Configuration report” and make note of the index value.

In the following example, the mib object is ifInBroadcastPkts.

ifInBroadcastPkts = and the index value is 2.

Log on to the eHealth server command line as $NH_USER and run the following:

nhSnmpTool –c communitystring –n –o objectID.index  ipaddress

 $ nhSnmpTool -c YMCA -n -o -a
SNMPv2-SMI::mib- = 4294858113

-bash-3.2$ nhSnmpTool -c YMCA -n -o -a
SNMPv2-SMI::mib- = 4294858111

-bash-3.2$ nhSnmpTool -c YMCA -n -o -a
SNMPv2-SMI::mib- = 4294858111

-bash-3.2$ nhSnmpTool -c YMCA -n -o -a
SNMPv2-SMI::mib- = 4294858000

2. Run the command sequentially or over a period of time. This will output the counter values, polled directly from the device mib agent, so as to document the decrementing counters.

You will be able to use this information when contacting the device manufacturer.

You may see the values decrementing right away or may not. If you don’t see the decrementing within a 15 minute period, open a case with CA Technical Support and we will assist you.



Release: LHDEVC99000-6.3-eHealth-Live Health Upgrade Elements