Hello
After many search an readings, I have understand that OCTET STRING are returned by snmpget client as hexa value if some unprintable characters are present.
This behavior is manually avoidable by forcing snmpclient to return ascii output (-Oa parameter).
I try to configure net-snmp to do so by default, to import MIB and even to add a displey-hint "255a" in the mib TC definition.
Unfortunately, if unprintable character are present, zabbix still receive hexa value from net-snmp.
Does anyone already solved this issue ?
I run zabbix 3.2.4 on Centos 7.
Net-snmp is installed (devel, libs, utils and agent are present).
Thx by advance for any help.
After many search an readings, I have understand that OCTET STRING are returned by snmpget client as hexa value if some unprintable characters are present.
This behavior is manually avoidable by forcing snmpclient to return ascii output (-Oa parameter).
I try to configure net-snmp to do so by default, to import MIB and even to add a displey-hint "255a" in the mib TC definition.
Unfortunately, if unprintable character are present, zabbix still receive hexa value from net-snmp.
Does anyone already solved this issue ?
I run zabbix 3.2.4 on Centos 7.
Net-snmp is installed (devel, libs, utils and agent are present).
Thx by advance for any help.
Comment