[ZBX-6370] LLD with decreasing OID numbers does not work Created: 2013 Mar 09  Updated: 2017 May 30  Resolved: 2016 Jul 04

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 2.0.6rc1
Fix Version/s: 3.0.4rc1, 3.2.0alpha1

Type: Incident report Priority: Major
Reporter: Róbert Szénásy Assignee: Unassigned
Resolution: Fixed Votes: 12
Labels: lld, oid, snmp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Freebsd


Attachments: GIF File error screen.gif     Text File full walk.txt     File without-oid-not-increasing-check.patch    
Issue Links:
Duplicate
is duplicated by ZBX-8126 SNMPv2 LLD IF-MIB::ifDescr vs Mikroti... Closed
is duplicated by ZBX-9192 LLD error OID not increasing. Closed
is duplicated by ZBX-10853 Decreasing OID numbers does not work Closed

 Description   

Hi there !

I have a problem, and cannot solve it.
I have an equipment with full MIB file.
When I take an snmpwalk on the sysBufferAlrIdx the records are the following:

ITC_ZABBIX# snmpwalk -v 1 -c public -m RAD-MIB 172.32.1.30 sysBufferAlrIdx
RAD-MIB::sysBufferAlrIdx.154 = INTEGER: 154
RAD-MIB::sysBufferAlrIdx.153 = INTEGER: 153
Error: OID not increasing: RAD-MIB::sysBufferAlrIdx.154
>= RAD-MIB::sysBufferAlrIdx.153

The index id decreasing.
Zabbix say the OID is not increasing, and fail the walk/work.

Attached the full walk (with SnmpB) and the error screen.
Very interesting, in the full walk there is a break in the numbering sequence in the middle (1>256)

Have you any suggestion how to read the values wiht LLD ?

Thank. Bob



 Comments   
Comment by Róbert Szénásy [ 2013 Apr 18 ]

Not yet seen by anyone ?

Comment by Thomas Wouters [ 2013 Apr 19 ]

An option to allow decreasing OID's would be nice.
My device is sending snmp results in a seemingly random order.

Comment by Renato de Oliveira Diogo [ 2013 Sep 19 ]

My device (Mikrotik Router) results ramdom too.

Ubuntu 12.04.2, zabbix 2.0.6

Comment by Diego Luisi [ 2013 Oct 31 ]

I have the same problem in Sonicwall,

Centos 6, Zabbix 2.0.6

I have to put snmpwalk -Cc

Comment by Thomas Wouters [ 2013 Nov 01 ]

Diego,

SonicWALL has a firmware update which fixes the order of (some?) SNMP results.
I'll check next week if it's available in a public firmware or not.

Comment by Róbert Szénásy [ 2013 Nov 02 ]

Hi !

Where did you put the snmpwal -Cc ?

Comment by Diego Luisi [ 2013 Nov 04 ]

Hi,

snmpwalk -Cc -v2c -c public 192.XXX.XXX.XX 1.3.6.1.4.1.XXX.X.X.X.X.X

Thomas Wouters can you send me the new firmware?

Thanks!

Comment by Philipp Jakubowski [ 2014 Sep 17 ]

Hi all,

this error is really anoying. Any suggestions for a workaround?

Thanks,
Philipp

Comment by Róbert Szénásy [ 2014 Sep 17 ]

The time is spending.
Nothing done since more than 1 year.

I think the problem is located deep in LLD routin.

We are still hopeing...

Comment by Aleksandrs Saveljevs [ 2014 Sep 18 ]

Attached is a patch that disables the check for OIDs being increasing during SNMP walk for Zabbix 2.2.6. We do not have the hardware to test, but it seems like it could work. Please let us know your experience.

Comment by Denis Pozdnyakov [ 2014 Nov 05 ]

Hello
Yes, attached file was helped - now it works, and LLD is working.

Comment by Oleksii Zagorskyi [ 2015 Sep 18 ]

Let's change status to CONFIRMED.

Comment by Joakim Plate [ 2016 Feb 16 ]

See the same issue with a netgear (WNAP210) WIFI accesspoint:

snmpwalk -v 2c -Cc -c public 192.168.0.243 iso.3.6.1.4.1.4526.100.7.4.3.1.1.2.24
iso.3.6.1.4.1.4526.100.7.4.3.1.1.2.24.8 = STRING: "NETGEAR-7"
iso.3.6.1.4.1.4526.100.7.4.3.1.1.2.24.7 = STRING: "NETGEAR-6"
iso.3.6.1.4.1.4526.100.7.4.3.1.1.2.24.6 = STRING: "NETGEAR-5"
iso.3.6.1.4.1.4526.100.7.4.3.1.1.2.24.5 = STRING: "NETGEAR-4"
iso.3.6.1.4.1.4526.100.7.4.3.1.1.2.24.4 = STRING: "NETGEAR-3"
iso.3.6.1.4.1.4526.100.7.4.3.1.1.2.24.3 = STRING: "NETGEAR-2"
iso.3.6.1.4.1.4526.100.7.4.3.1.1.2.24.2 = STRING: "NETGEAR-1"
iso.3.6.1.4.1.4526.100.7.4.3.1.1.2.24.1 = STRING: "NETGEAR"

Comment by Andris Mednis [ 2016 Jun 20 ]

Proposed patch disables "OID not increasing" check in Zabbix. The patch helps in case if the only problem with an SNMP device is OID order. However, the patch introduces the risk of endless looping in Zabbix poller process (and apparently memory leak) if an SNMP device is returning OIDs in a loop ("OID not increasing" check prevents this scenario).

Comment by Andris Mednis [ 2016 Jun 30 ]

Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-6370 .

Implemented solution: initially the "OID increase check" is active. If a smaller OID arrives then the "OID increase check" is deactivated and the OID is accepted and stored in memory. The following OIDs are accepted regardless of order and stored. If any OID is seen twice then a loop is detected and LLD rule becomes NOTSUPPORTED. Up to 1 million OIDs can be stored before LLD is NOTSUPPORTED . Hopefully it will help to deal with problematic SNMP devices.

Comment by Alexander Vladishev [ 2016 Jul 01 ]

Successfully tested! Have a look at my changes in r60850 before a merge.

andris Thanks! Reviewed, accepted.

Comment by Andris Mednis [ 2016 Jul 01 ]

While this ZBX is about LLD with decreasing OID numbers it also fixes monitoring of an SNMP item with dynamic index - now it does not stop with "OID not increasing". Could not find a separate ZBX on that issue.

Comment by Andris Mednis [ 2016 Jul 01 ]

Fixed in versions:

  • pre-3.0.4 r60862
  • pre-3.1.0 (trunk) r60855 .
Comment by Andris Mednis [ 2016 Jul 04 ]

Documented in
https://www.zabbix.com/documentation/3.0/manual/introduction/whatsnew304

sasha Reviewed. CLOSED

Generated at Fri Mar 29 08:40:19 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.