[ZBX-5681] Discovery will fail and discovery rule will become ZBX_NOTSUPPORTED if there is an empty table next in the snmpwalk Created: 2012 Oct 10  Updated: 2017 May 30  Resolved: 2015 Mar 11

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 2.0.2
Fix Version/s: 2.2.3, 2.3.0

Type: Incident report Priority: Major
Reporter: Kester Allen Assignee: Unassigned
Resolution: Fixed Votes: 2
Labels: discovery, mib, snmptable, snmpv3, trivial
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 12.04



 Description   

Running discovery on a SNMP v3 OID that is at the end of the MIB except for an empty table causes the discovery rule to fail. The snmp walk for this situation looks like this:

snmpwalk -v 3 -u username -l authPriv -a MD5 -A password1 -X password2 192.168.1.131 VEMS-ALARM-MIB::vemsAlmGrpHotGuardLeafName
VEMS-ALARM-MIB::vemsAlmGrpHotGuardLeafName.1050001 = STRING: "group_001"
VEMS-ALARM-MIB::vemsAlmGrpHotGuardLeafName.1050001 = No more variables left in this MIB View (It is past the end of the MIB tree)



 Comments   
Comment by Alexei Vladishev [ 2012 Oct 11 ]

I am not sure what kind of problem you have here. Please elaborate.

Comment by richlv [ 2012 Oct 16 ]

could it be that snmp getnext returns "end of mib" instead of next oid which is not part of the table ?

Comment by Kester Allen [ 2012 Oct 17 ]

It is giving an "end of mib" error. Is there a way to configure Zabbix so that this won't kill discovery?

Comment by richlv [ 2012 Oct 17 ]

i don't think this is a configuration issue, seems to be a bug

Comment by Jason Kendall [ 2013 Feb 15 ]

I can confirm this on 2.0.4.

Cacti seems to have resolved this issue by ignoring certain strings: http://bugs.cacti.net/view.php?id=1361

Comment by Jason Kendall [ 2013 Feb 15 ]

Enabled debug and identified that it's hitting: Exception value found (checks_snmp.c Line 701).

Looks like checks_snmp on line 595 looks for the SNMP_ENDOFMIBVIEW and considers it an Exception. As far as I can tell, zabbix should just discard this value and keep the previous value for the same index.

I'd try and make a patch, but I'm not sure exactly how the code should look.

Comment by Aleksandrs Saveljevs [ 2015 Mar 09 ]

This was noticed and fixed together with SNMP bulk implementation in Zabbix 2.2.3 under ZBXNEXT-98.

Generated at Fri Apr 19 16:45:08 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.