SNMP - value has unknown type [0x80]

[kayjay]

I'm using V1.8.2 server and get lots of data via SNMP in most cases I juen use the raw numeric OID. In this case I am attempting to get the CPU loading of a switch. The server log shows this:-

error: OID [1.3.6.1.4.1.890.1.5.8.16.9.7.0] value has unknown type [0x80]

Yet "snmpget 10.104.102.2 -c public -v2c 1.3.6.1.4.1.890.1.5.8.16.9.7.0" correctly reports this:-

SNMPv2-SMI::enterprises.890.1.5.8.16.9.7.0 = INTEGER: 44

What can the problem be?

Many Thanks

[untergeek]

Did you try putting in a leading . in front of the OID?

If you have the MIBs installed at zabbix_server start time, you can also use the MIB name, e.g.

.1.3.6.1.4.1.890.1.5.8.16.9.7.0

or

SNMPv2-SMI::enterprises.890.1.5.8.16.9.7.0

[kayjay]

In general I find it simpler to locate the correct OID using my mib browser tools and then use the value for OID that it gives me directly - that way I don't have to install any mibs and I already have 'proved' that it's correct. The fact that snmpget works OK is what puzzles me. I don't have a leading '.' in any of my other similar 'items' and they all work great.

[pHiney]

SameSame

This is precisely what i have.

are there debug logs, debug levels ? anything that can be activated for just a host even ?

I see that no one has responded, did it get resolved ?

snmpwalk -v1 -c xxxxx  server1 .1.3.6.1.4.1.334.72.1.1.6.3.6
SNMPv2-SMI::enterprises.334.72.1.1.6.3.6.0 = INTEGER: 134

it's the lotus notes number of users.

On the same device, i have the Network traffic in/out working. so i know snmp and zabbix is working.

p

[kayjay]

I am afraid not

[pHiney]

oh sod.

look carefully at the example i gave.

there's an extra '.0' in the answer.

as soon as i added the extra .0, it worked


i really dislike the silliness of SNMP

p

[shalley303]

I was getting this error on a standard INTEGER type OID. I eventually noticed that I forgot to update the community string when I created the new item, so it was trying to use public. Pointing this out because it may be the cause of this error for others tracking down this thread.