SLES 11.1

Well, I have a 1.8.5 installed from Open Suse build server. And I have the error in 1.8.5

Problem is still not solved. But the issue is important. The sysObjectID is the OID to characterize new discovered systems in the wild.

Also, when querying device (cisco) for OID .1.3.6.1.2.1.1.2.0 (sysObjectID.0) item status get's to "Not supported" and no data retrieved. Same with OID .1.3.6.1.2.1.1.5 (sysName.0). Note, that snmpwalk gets data from device. Network discovery also not working with this OID's.

OS: Debian Squeeze
Zabbix server version: 1.8.8
NET-SNMP version: 5.4.3

Hi,
i've added this suggestion: http://www.zabbix.com/forum/showthread.php?t=24847

This seems to be related.

Seems pretty easy to fix. But not sure we can afford that before 2.0.

Would be really great to see this fixed in 2.0.

Probably related forum thread (russian) http://www.zabbix.com/forum/showthread.php?t=26264&highlight=0x06

issue confirmed in 2.0.2 compiled on latest debian release

This is still present on 2.0.4 and makes the disk usage templates a lot less useful since alerts are triggered when the volume "Real Memory" has less than 20% free, and there appears to be no way to filter this out if Zabbix doesn't handle OIDs as return values.

for the record, debuglevel4 returns :

discovery: item [SNMPv2-MIB::sysObjectID.0] error: Value has unknown type 0x06

(1) we should also document which versions support which types

asaveljevs Documented at the following locations:

• https://www.zabbix.com/documentation/2.2/manual/config/items/itemtypes/snmp?&#step_2
• https://www.zabbix.com/documentation/2.4/manual/config/items/itemtypes/snmp?&#step_2
• https://www.zabbix.com/documentation/3.0/manual/config/items/itemtypes/snmp?&#step_2

RESOLVED

wiper Added 2.4.3 version requirements to 2.4, 3.0 documentation, please review

asaveljevs Added 2.4.2 to notes regarding ZBX-8538 and ZBX-8621. RESOLVED.

wiper CLOSED

it not appearing at all is related to ZBX-5376

confirming in 2.0 branch r38714

Still true for 2.2.3

Were experiencing the same issue here.

In this case were monitoring a LIEBERT Air Conditioner that uses a SNMP table to store temperatures with the table row field lgpEnvTemperatureDescrDegC containing a reference to OID with a measurement description ie:

LIEBERT-GP-ENVIRONMENTAL-MIB::lgpEnvTemperatureDescrDegC.1 = OID: LIEBERT-GP-ENVIRONMENTAL-MIB::lgpEnvControlTemperature
LIEBERT-GP-ENVIRONMENTAL-MIB::lgpEnvTemperatureDescrDegC.2 = OID: LIEBERT-GP-ENVIRONMENTAL-MIB::lgpEnvSupplyAirTemperature
LIEBERT-GP-ENVIRONMENTAL-MIB::lgpEnvTemperatureDescrDegC.3 = OID: LIEBERT-GP-ENVIRONMENTAL-MIB::lgpEnvReturnAirTemperature

Is there any movement on this as were using 2.2.5 and it still is unable to pick this up?

I have solved the problem. I have included the file check_snmp.c which return the OID as a string.

Could you please attach it as a patch instead?

I do not know how to generate a patch, if you can give me a clue, than I will do it.

pgin, this is one way to get a patch:

[foo@example zabbix-2.4.0]$ cp -a src/zabbix_server/poller/checks_snmp.c src/zabbix_server/poller/checks_snmp.c.orig
[foo@example zabbix-2.4.0]$ diff -u src/zabbix_server/poller/checks_snmp.c.orig src/zabbix_server/poller/checks_snmp.c > /tmp/checks_snmp.c.patch

Here is the checks_snmp.c.patch

Available in development branch svn://svn.zabbix.com/branches/dev/ZBX-4054 .

Successfully tested

Available in pre-2.2.8 r50381. Merging into higher versions has to wait until 2.4.2 is released and 2.4 branch is unfrozen.

Available in pre-2.4.3 r50435 and pre-2.5.0 (trunk) r50436.

(2) Documented in "What's new":

• https://www.zabbix.com/documentation/2.2/manual/introduction/whatsnew228?&#daemon_improvements
• https://www.zabbix.com/documentation/2.4/manual/introduction/whatsnew242?&#daemon_improvements

wiper CLOSED