OS Centos 7.4 x64, server Dell R210, two HDD as RAID

Hello Vladimir,

please attach both the discovery rule screenshot and item prototype screenshot here. Now it seems like a wrong discovery rule configuration, not a Zabbix bug.

Regards,
Kaspras

Hello! I uploaded the required screenshots. The full string of discovery rule is

discovery[{#SIPPROXYDNS}, 1.3.6.1.4.1.369.1.1.1.1.3,{#SIPPROXYSTATUS},1.3.6.1.4.1.369.1.1.1.1.6]

Hello Vladimir,

The AGAT-SIP-CONTROL-MIB.MIB file does not include translation for Oid:
1.3.6.1.4.1.369.1.1.1.1.6

Nevertheless MIB file still contains information about 1.3.6.1.4.1.369.1.1.1.1.3 which matches sipProxyDNS.

Please try to create discovery rule only with:
discovery[

,.1.3.6.1.4.1.369.1.1.1.1.3]

Nothing has changed with the new rule.

If you can provide us with the snmpwalk dump file for 1.3.6.1.4.1.369 , we will be able to reproduce the issue. Is that possible ?

I attached it.

Thank you, we will try to reproduce the issue.

Regards,
Kaspars

Hello, Vladimir

Please send another snmpwalk dump for 1.3.6.1.4.1.369, but this time provide OIDs in numeric format.
This can be done by passing -On to snmpwalk.

Hello!
Done

Hello Vladimir,

The problem is, that every SNMP tree in your device begins with a NULL entry, like

SNMPv2-SMI::enterprises.369.1.3.1.1.17.0 = NULL
SNMPv2-SMI::enterprises.369.1.3.1.1.17.1 = INTEGER: 0
SNMPv2-SMI::enterprises.369.1.3.1.1.17.2 = INTEGER: 0
SNMPv2-SMI::enterprises.369.1.3.1.1.17.3 = INTEGER: 0
SNMPv2-SMI::enterprises.369.1.3.1.1.17.4 = INTEGER: 0

Zabbix gets NULL value at the start of the tree and stops walking the tree, no more discoveries are made

Regards,
Kaspars

Hello!
Yes, I wrote it while opening the issue.
>>But Zabbix asks only one, then PBX answers with value NULL
I suspected that this is the reason and you have confirmed.
And how to solve the issue? Is vendor guilty for such a SMNP realization?

There are very rare cases of such SNMP realization. We can not confirm that this a bug in Zabbix, because Zabbix works with "normal" SNMP trees as expected, and breaks only on such strange SNMP solutions. You can contact vendor for possible SNMP updates, or you can open a new Zabbix feature request to handle such situations

Regards,
Kaspars

Why should I open a new request?
Where is the standart of "normal" SNMP trees?
Who estimates the normality?

Hello!
Any news?

Hello!
Any news?

Hi,

Where is the standard of "normal" SNMP trees?

Every leaf inside OID must belong to some data type. It can be a string, integer, hex. This approach also applies to things like Object-oriented programming. Values must have a data type. In other words, we invent data types to easier classify and store values.

I will close this ticket as won't fix. Please open a feature request to handle such exception in Zabbix.

P.S. When I tried to reproduce your scenario with SNMP simulator. This guy even don't allow NULL to be stored inside a tree