Some vendors' SNMP implementations (MIBs) do very stupid things with types, like call a 64-bit integer a STRING. It would be really useful if Zabbix -- when I tell it the value of an SNMP Item is "integer" -- would *try* to convert whatever value comes back *to* an integer (I don't really care what the failure mode is because getting the data is actually much more important).
For instance:
[root@zabbix00 zabbix]# snmpwalk -cpublic -v1 netscaler0.example.com 1.3.6.1.4.1.5951.4.1.1.53.1.1
SNMPv2-SMI::enterprises.5951.4.1.1.53.1.1.0 = STRING: "599831317"
Yes, it's wrong, but I *need* to save that data as an integer!
Any chance this feature can be added to Zabbix?
Yikes! Apparently this is even worse than I'd feared: Zabbix claims it doesn't even recognize the type:
18263:20081209:164314 OID [1.3.6.1.4.1.5951.4.1.1.53.1.1] value has unknow type [81]
So how does Zabbix's type parsing differ from snmpwalk's?
For instance:
[root@zabbix00 zabbix]# snmpwalk -cpublic -v1 netscaler0.example.com 1.3.6.1.4.1.5951.4.1.1.53.1.1
SNMPv2-SMI::enterprises.5951.4.1.1.53.1.1.0 = STRING: "599831317"
Yes, it's wrong, but I *need* to save that data as an integer!
Any chance this feature can be added to Zabbix?
Yikes! Apparently this is even worse than I'd feared: Zabbix claims it doesn't even recognize the type:
18263:20081209:164314 OID [1.3.6.1.4.1.5951.4.1.1.53.1.1] value has unknow type [81]
So how does Zabbix's type parsing differ from snmpwalk's?
Comment