Zabbix can't treat SNMP discovery long Indexes correctly
Hello Sir / Madam,
I find SNMP discovery rules doesn't work on long indexes. If Zabbix changes the method to get SNMP discovery Indexes, it will works for multi-session or single session SNMP Indexes.
We try SNMP discovery on an Aruba switch for AP information. The discovery rule get AP Names with an OID
.1.3.6.1.4.1.14823.2.2.1.5.2.1.4.1.3
, and get values like
Name/OID: .1.3.6.1.4.1.14823.2.2.1.5.2.1.4.1.3.36.222.198.19 2.59.48; Value (OctetString): 8F.AP93.253
Ths SNMP reply shows an AP called '8F.AP93.253' with an index '36.222.198.192.59.48', which is a long SNMP Index mentioned. However, Zabbix 2.0.5 assumes the SNMP Index as '48', instead of '36.222.198.192.59.48'. Therefor, all item prototype queries fail due to wrong SNMP Indexes.
If Zabbix treats SNMP Index by remove queried OID from SNMP replies, it will work for both mult-session or single session SNMP Indexes. Such as, [.1.3.6.1.4.1.14823.2.2.1.5.2.1.4.1.3] .36.222.198.192.59.48.
I look forward to get this suggestion built into coming release soon!
Thanks for your kind works!
I find SNMP discovery rules doesn't work on long indexes. If Zabbix changes the method to get SNMP discovery Indexes, it will works for multi-session or single session SNMP Indexes.
We try SNMP discovery on an Aruba switch for AP information. The discovery rule get AP Names with an OID
.1.3.6.1.4.1.14823.2.2.1.5.2.1.4.1.3
, and get values like
Name/OID: .1.3.6.1.4.1.14823.2.2.1.5.2.1.4.1.3.36.222.198.19 2.59.48; Value (OctetString): 8F.AP93.253
Ths SNMP reply shows an AP called '8F.AP93.253' with an index '36.222.198.192.59.48', which is a long SNMP Index mentioned. However, Zabbix 2.0.5 assumes the SNMP Index as '48', instead of '36.222.198.192.59.48'. Therefor, all item prototype queries fail due to wrong SNMP Indexes.
If Zabbix treats SNMP Index by remove queried OID from SNMP replies, it will work for both mult-session or single session SNMP Indexes. Such as, [.1.3.6.1.4.1.14823.2.2.1.5.2.1.4.1.3] .36.222.198.192.59.48.
I look forward to get this suggestion built into coming release soon!
Thanks for your kind works!