:confused: Gauge32 values :confused:

[tensk8]

Hi experts,

I'm trying to get a gauge32 value from my Cisco equipments but it's triggers an error every time I ask for this values.

I know that gauge32 are unsigned numbers.

Someone know how to solve this issue, or can you send me to another thread where this issue was resolved.

Regards

Tensk8

[MrKen]

Hi,

You can monitor Gauge32 using Type of Information: Numeric (float). It works for me.

If that doesn't help, you should post a copy of any error messages you receive. Maybe even your Item configuration.

Good luck.

MrKen

[tensk8]

Hi MrKen

I already has my OID with Numeric (Float) and the issue still.

Message display by Zabbix:

Type of received value [] is not suitable for value type [Numeric (float)]

SNMP get directly from the server:

lhdw@lab:~$ snmpget -v 2c -c SPC IP 1.3.6.1.4.1.9.9.48.1.1.1.5.2
SNMPv2-SMI::enterprises.9.9.48.1.1.1.5.2 = Gauge32: 3606140

Regards

Tensk8

[MrKen]

Could it be a BUG?

On closer inspection I also find errors like that in the Sever.log. I noticed these errors after upgrading to 1.6.1 or 1.6.2.

I get these errors for Numeric (float), and Numeric (Integer 64 bit).

Quite often the error has been related to an interface that is unreachable, but later becomes reachable again. Have a look at these two entries:

15063:20090327:084415 Item [HP_9250C_Digital_Sender:PrtMarkerSuppliesMaxCapaci ty.1.1] error: Type of received value [] is not suitable for value type [Numeric (integer 64bit)]

15063:20090327:085415 Parameter [prtMarkerSuppliesMaxCapacity.1.1] became supported by agent on host [HP_9250C_Digital_Sender]

Strange how one minute the value is not suitable, but ten minutes later it became supported.

Maybe it is throwing the wrong error message.

Bug?? Don't know!

MrKen

[georgew]

Type of received value [] is not suitable for value type [Numeric (integer 64bit)]

I'm getting the same type of error for a different application:

Type of received value [-69 dBm] is not suitable for value type [Numeric (float)]

Notice that I'm trying to store the value "-69 dBm" as a numeric, when it is really a string.

In your case you are storing "" as a number... this is a "null string", and is not a valid number. The error is telling you that you don't have a number, and you are trying to call this a number. So either the router intermittantly returns a null, OR there is a problem somewhere, and the value is getting lost.

Now what *I* need is the ability to extract the number from the string.

What you need is to find out why/if the router is returning a null, or ignore the error if it is intermittent. Perhaps it is a cisco firmware bug?

It would be really nice if we could ask zabbix to run a SNMP query in debug mode, and display what it sends, and what it gets back. That would have saved me days of debug time.