I'm monitoring a network device with snmp which presents two 32 bit counters for network IO. One 32 bit high counter, one 32 bit low counter. Monitoring the one 32 bit low counter doesn't produce sane graphs since counter is always rolling over. Is there simple method to combine these two 32 bit counters into one 64 bit counter in Zabbix?
Ad Widget
Collapse
Combining snmp 32 bit counters into 64 bit counter
Collapse
X
-
Do you mean that these two counters have different OIDs? -
Hi,
Not sure if this is what you're talking about, but....
For 32 bit I use:
ifInOctets .1.3.6.1.2.1.2.2.1.10
ifOutOctets .1.3.6.1.2.1.2.2.1.16
For 64 bit I use:
ifHCInOctets .1.3.6.1.2.1.31.1.1.1.6
ifHCOutOctets .1.3.6.1.2.1.31.1.1.1.10
Hope that helps.
MrKenDisclaimer: All of the above is pure speculation.Comment
-
I think we could implement native support of the strange logic at some point. Now we are too busy with other stuff.
Comment
-
I've been having this problem as well.
I doubt that its usefull to implement this right now, since netapp is already fixing this in the new ontap major version (or so they told me).
I havent tried this myself yet, but you could look at snmp proxy tools, perhaps they have support to mangle oid's.Comment
-
SNMP OIDs - different capacitites
Hello!
I have several SNMP-enabled switches from different brans monitored and I always have to use the 64 bit counters.
Its really simple: the 32 bit limit states that 4Gb is all you get... So the graphs for traffic, etc always roll over at 4Gb
The Zabbix SNMP template should be revised and changed with the new OIDs. Beware of this: the 64 bit counters only work in SNMP v2c devices!!
SNMP v1 does not allow (on my switches) the use of 64 bit counters.
Cheers,
Ivo Pereira
IT Consultant
PortugalComment
-
Thanks for replies. They have been helpful. I haven't found any information on NetApp updating their snmp to v2 and fixing the mess which is high and low 32 bit counters.
(I will be meeting with my NetApp folks next week and I'll do my best to publicly shame them)
Since there is no known work around in Zabbix to directly address this issue I'll just have to sit down and write my own script two combine two 32 bit OID's into a single value and feed it into Zabbix. Thanks again.
Comment
Comment