Firmware version comes back as hex string?

[abjornson]

Tried searching, but didn't find anyone else mentioning this.

I'm trying to track firmware versions of wispSwitches in my network.

I know this is reported as .1.3.6.1.4.1.46242.1.0

but when I snmpwalk this, I get back a hex string

snmpwalk -v2c -c XXXXX 10.20.6.37 .1.3.6.1.4.1.46242.1.0
SNMPv2-SMI::enterprises.46242.1.0 = Hex-STRING: 31 2E 33 2E 39 00 6E 00 00 00 00 00 00 00 00 00

if I force snmpwalk to interpret as ascii, then i get the firmware version I want:
snmpwalk -Oa -v2c -c XXXXX 10.20.6.37 .1.3.6.1.4.1.46242.1.0
SNMPv2-SMI::enterprises.46242.1.0 = STRING: "1.3.9.n........."
But unfortunately my monitoring tool (Zabbix) doesn't have an equivalent setting of -Oa

This seems to be related to this: http://www.net-snmp.org/wiki/index.php/ ... _the_tools

Has anyone dealt with this? Why does this particular value come back as hex? I get lots of other values as printable strings from the netonix.

[Eric Stern]

Since you do not appear to be using our MIB snmpwalk has to guess at the data type and the embedded NULLS in the string might be confusing it into thinking it is not a plain string.

The incorrect version string was recently reported by someone else and will be fixed in the next release.

[sirhc]

I moved this post to the proper thread, it was posted under share your installation picture??

Here is where are MIB files are located: viewtopic.php?f=17&t=251