Previously I had a zabbix 2.0.11 server that used a large amount of SNMP to get data.
In particular I probe dell servers to see if a minimum version of the driver software is installed for a given controller number. The details from the item prototype is
SNMPV2
OID .1.3.6.1.4.1.674.10893.1.20.130.1.1.45.{#SNMPINDEX }
If this value does not exist then previously zabbix reported the item as unavailable (desired behaviour) and I knew that the item didn't exist do the firmware was up-to-date.
Now, after the upgrade to 2.2.2 then all the items that were previously reporting as unsupported are now reporting "SNMP error: (noSuchName) There is no such variable name in this MIB."
Is there a way of changing this behaviour to the way it was previously or at least a better way of handling it?
In particular I probe dell servers to see if a minimum version of the driver software is installed for a given controller number. The details from the item prototype is
SNMPV2
OID .1.3.6.1.4.1.674.10893.1.20.130.1.1.45.{#SNMPINDEX }
If this value does not exist then previously zabbix reported the item as unavailable (desired behaviour) and I knew that the item didn't exist do the firmware was up-to-date.
Now, after the upgrade to 2.2.2 then all the items that were previously reporting as unsupported are now reporting "SNMP error: (noSuchName) There is no such variable name in this MIB."
Is there a way of changing this behaviour to the way it was previously or at least a better way of handling it?
Comment