Hi!
I've got troubles getting correct octet-string values from printer.
Trying to get OCTET STRING values from printer (hrPrinterDetectedErrorState)
item configuration is on the attached picture.
The problem is that
* sometimes values are returned as OCTET STRING, correctly parsed by Zabbix and put into database
* sometimes values are returned as STRING that seem like OCTET STRING (0..9A..F) and put into database incorrectly
* sometimes values are returned as STRING that do not seem like octet, and no values put into database.
as explained here, http://net-snmp.sourceforge.net/wiki...from_the_tools, smnp tools use isprint() function to determine the way it shows the OCTET STRING value, but zabbix doesn't analyse the output of the snmp and always uses the value as-is.
Here's the test runs of snmpwalk over the OID.
(The same values in hex (-Ox) and ascii (no snmp switches))
root@msk-zbx:/usr/share/mibs/ietf# snmpwalk -mALL -v1 -Ox -cpublic 192.168.0.75 hrPrinterDetectedErrorState
HOST-RESOURCES-MIB::hrPrinterDetectedErrorState.1 = Hex-STRING: 40
root@msk-zbx:/usr/share/mibs/ietf# snmpwalk -mALL -v1 -cpublic 192.168.0.75 hrPrinterDetectedErrorState
HOST-RESOURCES-MIB::hrPrinterDetectedErrorState.1 = STRING: "@"
(another state of printer, wrongly seen as hex value A)
root@msk-zbx:/usr/share/mibs/iana# snmpwalk -mALL -v1 -cpublic 192.168.0.75 hrPrinterDetectedErrorState
HOST-RESOURCES-MIB::hrPrinterDetectedErrorState.1 = STRING: "A"
QUESTION:
Is there a way to force Zabbix using -Ox key when getting HEX values from SNMP devices?
Zabbix 2.4 I know it's rather old and unsupported, have things changed since then?
I've got troubles getting correct octet-string values from printer.
Trying to get OCTET STRING values from printer (hrPrinterDetectedErrorState)
item configuration is on the attached picture.
The problem is that
* sometimes values are returned as OCTET STRING, correctly parsed by Zabbix and put into database
* sometimes values are returned as STRING that seem like OCTET STRING (0..9A..F) and put into database incorrectly
* sometimes values are returned as STRING that do not seem like octet, and no values put into database.
as explained here, http://net-snmp.sourceforge.net/wiki...from_the_tools, smnp tools use isprint() function to determine the way it shows the OCTET STRING value, but zabbix doesn't analyse the output of the snmp and always uses the value as-is.
Here's the test runs of snmpwalk over the OID.
(The same values in hex (-Ox) and ascii (no snmp switches))
root@msk-zbx:/usr/share/mibs/ietf# snmpwalk -mALL -v1 -Ox -cpublic 192.168.0.75 hrPrinterDetectedErrorState
HOST-RESOURCES-MIB::hrPrinterDetectedErrorState.1 = Hex-STRING: 40
root@msk-zbx:/usr/share/mibs/ietf# snmpwalk -mALL -v1 -cpublic 192.168.0.75 hrPrinterDetectedErrorState
HOST-RESOURCES-MIB::hrPrinterDetectedErrorState.1 = STRING: "@"
(another state of printer, wrongly seen as hex value A)
root@msk-zbx:/usr/share/mibs/iana# snmpwalk -mALL -v1 -cpublic 192.168.0.75 hrPrinterDetectedErrorState
HOST-RESOURCES-MIB::hrPrinterDetectedErrorState.1 = STRING: "A"
QUESTION:
Is there a way to force Zabbix using -Ox key when getting HEX values from SNMP devices?
Zabbix 2.4 I know it's rather old and unsupported, have things changed since then?
Comment