SNMP Discovery Issue with Uniqueness Criteria
Recently, I noticed that when we have an SNMP discovery rule and one of the OID values is "uniqueness criteria", the other OID is no longer discovered.
For example:
A discovery rule queries the OIDs ".1.3.6.1.2.1.1.2.0" (object id) and ".1.3.6.1.2.1.1.5.0" (hostname).
Two devices are found, and both SNMP "services" are discovered.
When the "uniqueness criteria" is set to ".1.3.6.1.2.1.1.5.0", however, the first OID (object id) is then not discovered anymore.
I'm not sure this happens for any OID, but I'm not seeing a reason for this behavior, and couldn't find an explanation in the documentation.
Has anyone else observed this before?
For example:
A discovery rule queries the OIDs ".1.3.6.1.2.1.1.2.0" (object id) and ".1.3.6.1.2.1.1.5.0" (hostname).
Two devices are found, and both SNMP "services" are discovered.
When the "uniqueness criteria" is set to ".1.3.6.1.2.1.1.5.0", however, the first OID (object id) is then not discovered anymore.
I'm not sure this happens for any OID, but I'm not seeing a reason for this behavior, and couldn't find an explanation in the documentation.
Has anyone else observed this before?
Comment