Can t use Zabbix anymore for snmp

[Kayou]

Hello,

Recently we did migrate on new type of network equipment, they are using large snmp counter wich gives very high values on 64 bits types and sounds like zabbix is not able to handle such kind of values.

Basicaly an snmp counter for the traffic for example starts from 0 then reach its maximum value then restart from zero etc .... The more you have an equipment that is very loaded, the more the recycle of the value will be done quickly.

In the low values zabbix has no problem until you reach 32 bits max values then goes completly wrong as soon it grows over. So at the beguinning it is impossible to notice it because the value are low enough to be handle without any problem and it works fine, but once it gets to the maximum value that zabbix can handle, it goes wrong.

I d love to know if something will be done in that domain (as well with snmp gets directly done by zabbix on such counter not supported by zabbix currently but working fine by simple snmp get) or if i have to find a new solution to manage these values.

Thank you.

[Alexei]

If you are talking about SNMP metrics having type counter64, it has been
fixed in the latest CVS code.

[Kayou]

Thank you for your answer Alexei, i tried to compile it and it seems we getting now values from these high value counters.

I think now the only problem left is the front end it self wich is not able to manage it once the values are growing to much :)

Thank you again.

[Alexei]

I think now the only problem left is the front end it self wich is not able to manage it once the values are growing to much :)
Please could you be more specific about this?

[Kayou]

Ok here some additional information :

1 - use of custom parameter :

i have a simple custom parameter, it is a snmpt get wich give me for example this value when i use under linux command mode : 5273916324713

The value in stored in database is : 1000000000000

So there might be a problem with the values with agentd and custom parameter values.

2 - use of direct snmp counter with snmpv2 item type :

When i use as is type to compare with snmpv2 command what are the values stored i have that on php front end :

2005.Oct.28 17:29:30 777326280.0000
2005.Oct.28 17:29:15 397217219663.0000
2005.Oct.28 17:29:00 777118389.0000
2005.Oct.28 17:28:45 397092934682.0000
2005.Oct.28 17:28:30 777001995.0000
2005.Oct.28 17:28:15 396846770270.0000
2005.Oct.28 17:28:00 776633546.0000
2005.Oct.28 17:27:45 396721907172.0000
2005.Oct.28 17:27:40 396721907172.0000

I have the same values in database.

But snmpv2 command is giving me 397092934682 or around value and gives the right values continuously (growing each seconds of course with the traffic).

To conclude it hink there is still a problem with big values handled by custom parameters and agentd and a problem somewher on iw zabbix handles snmp values, one value on tow seems wrong for some reason while each command from snmpv2 tool is giving the right value.

Hope this help.