<![CDATA[SNMP values: some are type STRING instead of Hex-STRING]]>Especially with MAC addresses we see situations in SNMP values like this:

ARP-Table:

.1.3.6.1.2.1.3.1.1.2.8.1.192.168.30.3 [Hex-STRING] = 4C 9E FF 6F E0 17
.1.3.6.1.2.1.3.1.1.2.8.1.192.168.30.4 [Hex-STRING] = 4C 9E FF 6F E2 15
.1.3.6.1.2.1.3.1.1.2.8.1.192.168.30.10 [Hex-STRING] = 00 08 9B DA 8B C5
.1.3.6.1.2.1.3.1.1.2.8.1.192.168.30.100 [STRING] = x~a?G
.1.3.6.1.2.1.3.1.1.2.8.1.192.168.30.103 [STRING] = Tä:?ön
.1.3.6.1.2.1.3.1.1.2.8.1.192.168.30.109 [Hex-STRING] = 28 6A BA 90 1B 77
.1.3.6.1.2.1.3.1.1.2.8.1.192.168.30.111 [STRING] = ô·âw_

Some values are of type STRING instead of Hex-STRING (in the same SNMP table!). We see this especially with ZyXEL devices, but other vendors too. Is this a problem of the monitored devices or in NetXMS? (NetXMS is V2.0-M3 on Linux x64, built from sources). If you need more information, no problem. Thanks.

]]>https://forum.netxms.org/topic/3690/snmp-values-some-are-type-string-instead-of-hex-stringRSS for NodeFri, 13 Nov 2026 17:13:58 GMTMon, 13 Apr 2015 12:26:37 GMT60<![CDATA[Reply to SNMP values: some are type STRING instead of Hex-STRING on Mon, 13 Apr 2015 14:14:12 GMT]]>Ok thanks Alex for the explanation. So if I need a MAC address human readable I have to manually convert it in an external converter.

]]>https://forum.netxms.org/post/16402https://forum.netxms.org/post/16402Mon, 13 Apr 2015 14:14:12 GMT<![CDATA[Reply to SNMP values: some are type STRING instead of Hex-STRING on Mon, 13 Apr 2015 13:51:34 GMT]]>When nxsnmpget detects non-printable characters, it display them as hex codes and mark them as "Hex-STRING".
It's just a matter of presentation – internally it's still 6 bytes with type "String".
Right now there are no argument which will force string/hex-string output.

]]>https://forum.netxms.org/post/16400https://forum.netxms.org/post/16400Mon, 13 Apr 2015 13:51:34 GMT