[ZBXNEXT-4314] Missing index processing in SNMP LLD Created: 2018 Jan 05  Updated: 2021 May 19  Resolved: 2021 May 19

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Proxy (P), Server (S)
Affects Version/s: None
Fix Version/s: None

Type: Change Request Priority: Trivial
Reporter: Olegs Vasiljevs (Inactive) Assignee: Andris Zeila
Resolution: Duplicate Votes: 3
Labels: index, lld
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by ZBX-13065 LLD incorrectly returns SNMPINDEX values Closed

 Description   

Hello!

Say there is an array of network interfaces available on a networking device and these differ in it's nature:

  • 9 FastEthernet interfaces
  • 1 Gigabit Ethernet interface
  • 1 Serial interface
  • 1 terminal line
  • 1 Virtual Private Network (VPN) Module

Such devices may provide network interface info in both ifHCInOctets and ifInOctets counters, and provide interfaces with only ifInOctets counters.
In SNMP tree, these will have different traffic counters present: ifInOctets and ifHCInOctets. With the current SNMP discovery implementation, if there is no entry for a certain SNMP OID, the discovery will fail by itself with the following message: Cannot accurately apply filter: no value received for macro "{#IFHCINOCTETS}".

As a workaround, user requires to define two different discovery rules as can be observed in Template Module Interfaces Simple SNMPv2 and Template Module Interfaces SNMPv2 out of the box templates.
It would be nice, if SNMP discovery would be able to process missing entries in SNMP tree in case index of device is present.

Sample SNMP tree layout for a reference:

IF-MIB::ifInOctets.1 = Counter32: 4266470707
IF-MIB::ifInOctets.2 = Counter32: 0
.3, .4, .5 ...... NO GAPs
IF-MIB::ifInOctets.12 = Counter32: 0
IF-MIB::ifInOctets.13 = Counter32: 4217786513
IF-MIB::ifInOctets.14 = Counter32: 1162860867

<...>

IF-MIB::ifHCInOctets.7 = Counter64: 0
IF-MIB::ifHCInOctets.8 = Counter64: 159481902502
GAP
GAP........
IF-MIB::ifHCInOctets.11 = Counter64: 151918525828
IF-MIB::ifHCInOctets.12 = Counter64: 0
IF-MIB::ifHCInOctets.14 = Counter64: 1014752389343


 Comments   
Comment by Alex [ 2018 Aug 07 ]

I am having the same issue. What's the workaround?

 

I am trying to filter on IF-MIB::ifAlias but not all interfaces return data. I don't care if they return data or don't – I just need to check via reg ex if they contain a certain exclusion flag. 

 

but I can't do this because they don't all have data.

Comment by Leandro Rocha [ 2018 Oct 27 ]

Same thing here.

I have several LLD rules and some of them are suppose to not find the value if they don't exist in the host.

But now its generating errors.

Will be nice if we can "silence" in some parameter in the Zabbix.

Comment by Oleksii Zagorskyi [ 2019 Apr 17 ]

historically related - ZBX-12259

Comment by Oleksii Zagorskyi [ 2019 Apr 17 ]

ZBX-10785 (see (1) ) is related - as for user friendly message that LLD rule works, just shows the information, which does not mean that rule is not supported.

Comment by Oleksii Zagorskyi [ 2021 May 19 ]

As I understand ZBXNEXT-6252 resolves it.
So, closing as duplicate.

Generated at Wed Apr 16 12:50:35 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.