I have a question about the Zabbix Discovery Rule process and how it attempts to detect and assign the correct SNMP version of a discovered device to a host.
I currently have 65 Discovery Rules. Each of which are identical, with the exception of the network IP range assigned.
There are 9 checks in total. 8 are SNMPv1 and 1 is SNMPv2. Each with a unique OID it is checking for.
Over a year ago we upgraded Zabbix from 5.X to 6.0.3. Ever since that upgrade we have had a rather odd issue of Zabbix detecting & assigning the wrong SNMP version to some hosts. It is not random as it is consistently happening to the same hosts over and over again. Each time the related Discovery Rule is processed. It has become a daily routine to check this and switch the hosts back to the correct SNMP version.
First off, the SNMPv1 OIDs being checked for are only available in the SNMPv1 devices and the SNMPv2 OID being checked for only exists in the SNMPv2 device.
Out of almost 7000 hosts, I found about 15 are being assigned SNMPv2 and 2 are being assigned SNMPv1.
Now, for the host that are being assigned SNMPv2, I'm not sure how the system could even think they are available via SNMPv2 as these devices only support SNMPv1.
And for the hosts being assigned the SNMPv1 that should be SNMPv2, that is a little more possible, but still problematic as the values for the OIDs I want to monitor in the assigned template are only available if SNMPv2 is in use.
I removed the SNMPv2 OID check in the associated Discovery Rule check and it stopped the assignment of SNMPv2 to those related devices.
My question is, when does the SNMP version get assigned to a new host? Is it done by the Discovery Rule or the Discovery Action? As there isn't any option to set the SNMP version, I assume the version is discovered by the Discovery Rule and assigned to the host by the Discovery Action.
Any clarification of this would be greatly appreciated!
Any advise as to how to prevent this from happening would be even better.
Thank you for your time.
I currently have 65 Discovery Rules. Each of which are identical, with the exception of the network IP range assigned.
There are 9 checks in total. 8 are SNMPv1 and 1 is SNMPv2. Each with a unique OID it is checking for.
Over a year ago we upgraded Zabbix from 5.X to 6.0.3. Ever since that upgrade we have had a rather odd issue of Zabbix detecting & assigning the wrong SNMP version to some hosts. It is not random as it is consistently happening to the same hosts over and over again. Each time the related Discovery Rule is processed. It has become a daily routine to check this and switch the hosts back to the correct SNMP version.
First off, the SNMPv1 OIDs being checked for are only available in the SNMPv1 devices and the SNMPv2 OID being checked for only exists in the SNMPv2 device.
Out of almost 7000 hosts, I found about 15 are being assigned SNMPv2 and 2 are being assigned SNMPv1.
Now, for the host that are being assigned SNMPv2, I'm not sure how the system could even think they are available via SNMPv2 as these devices only support SNMPv1.
And for the hosts being assigned the SNMPv1 that should be SNMPv2, that is a little more possible, but still problematic as the values for the OIDs I want to monitor in the assigned template are only available if SNMPv2 is in use.
I removed the SNMPv2 OID check in the associated Discovery Rule check and it stopped the assignment of SNMPv2 to those related devices.
My question is, when does the SNMP version get assigned to a new host? Is it done by the Discovery Rule or the Discovery Action? As there isn't any option to set the SNMP version, I assume the version is discovered by the Discovery Rule and assigned to the host by the Discovery Action.
Any clarification of this would be greatly appreciated!
Any advise as to how to prevent this from happening would be even better.
Thank you for your time.
Comment