Hex-String to Text

[aldevar]

Hi all!

I'm running a brand new Zabbix 3.0 server. No proxies
I'm trying to build a Template to monitor a Nutanix Cluster with Zabbix.
Nutanix uses it's own MIB and only accept SNMPv3

I loaded the MIB in the SNMP conf of the server and when I snmpwalk on the server I have the following entries :

.1.3.6.1.4.1.41263.8.1.3.1 = STRING: DEV.
.1.3.6.1.4.1.41263.8.1.3.2 = STRING: container02.
.1.3.6.1.4.1.41263.8.1.3.3 = STRING: RESERVED_SPACE.
.1.3.6.1.4.1.41263.8.1.3.4 = STRING: container03.

These are containers names (same things as Datastores in Vsphere)

When I launch the same snmpwalk on a server that does not have the MIB loaded, I have the following :

.1.3.6.1.4.1.41263.8.1.3.1 = Hex-STRING: 44 45 56 00
.1.3.6.1.4.1.41263.8.1.3.2 = Hex-STRING: 63 6F 6E 74 61 69 6E 65 72 30 32 00
.1.3.6.1.4.1.41263.8.1.3.3 = Hex-STRING: 52 45 53 45 52 56 45 44 5F 53 50 41 43 45 00
.1.3.6.1.4.1.41263.8.1.3.4 = Hex-STRING: 63 6F 6E 74 61 69 6E 65 72 30 33 00

Obviously, when I apply the template to my Nutanix Cluster, Zabbix tells me that my containers names are the Hex-Strings above.

Is there a way I can tell Zabbix to translate the Hex-String to 'normal' string ?

Regards,

[kloczek]

Is there a way I can tell Zabbix to translate the Hex-String to 'normal' string ?

Why not use correct MIB name in OIDs?
MIBs are the same as what DNS is for IP addresses.

[aldevar]

Thank you for your answer.
After reading it, I understand that I can call the MIB directly in Zabbix if it is already loaded in snmp on the server. (yes, i'm new to Zabbix )

So, the MIB is loaded as I have the right answers when I use snmpwalk

ie :

# snmpwalk -v 3 -a SHA -A SHAPASSWORD -u username -x AES -X AESPASSPHRASE server.name -l AuthPriv citContainerName              .1.3.6.1.4.1.41263.8.1.3.1 = STRING: DEV.
.1.3.6.1.4.1.41263.8.1.3.2 = STRING: container02.
.1.3.6.1.4.1.41263.8.1.3.3 = STRING: RESERVED_SPACE.
.1.3.6.1.4.1.41263.8.1.3.4 = STRING: container03.

Now, in my Zabbix template, here is what I'm trying to do :
In the SNMP OID of the dicovery rule, I enter :

discovery[{#SNMPVALUE},NUTANIX-MIB::citContainerName]

Here is the answer from Zabbix (logfile) :

snmp_parse_oid(): cannot parse OID "NUTANIX-MIB::citContainerName"

I tried multiple snmp OID (all of them have the 'current' status in the MIB)

I'm pretty sure i misunderstand something. It seems Zabbix doesn't know what the NUTANIX-MIB is.

[aldevar]

Ok, I found I just had to restart the zabbix-server process for the new MIB to be loaded.

Thanks for your help