Ad Widget

Collapse

Network Discovery Check: Device uniqueness criteria using multiple OIDs

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mrportatoes
    Junior Member
    • Mar 2023
    • 6

    #1

    Network Discovery Check: Device uniqueness criteria using multiple OIDs

    OK so I'm feeling pretty dense on this one but here it goes. Currently running Zabbix 5.0 w/ no proxies. We discover a number of SNMP devices, and for this use case, its mostly printers. The challenge is the printer's names do have the ability to change from time to time if they get reallocated to a different section of the building, get moved to a different building entirely or naming convention change. Likewise, the IP of the devices can change as well for similar reasons, including crappy usb print servers that users like to factory reset to "help"...

    Because of this I am trying to set the devices MAC addresses as the Device uniqueness criteria in the SNMP discovery check. The challenge is that some printers have their mac address at ifPhysAddress.1 (.1.3.6.1.2.1.2.2.1.6.1) while others have it at ifPhysAddress.2 (.1.3.6.1.2.1.2.2.1.6.2). My understanding is that discovery checks perform a get instead of a walk in the way an LLD does, so in turn I can't specify the higher level ifPhysAddress (.1.3.6.1.2.1.2.2.1.6) as it will return an empty value.

    Am I just incorrect on how the Discovery check works and/or am I just specifying ifPhysAddress incorrectly? (Currently added as "IF-MIB::ifPhysAddress" in the discovery check.

    Lastly, I'll add that I believe I could create 2 different rules (not checks) and specify the OID for each to be the device uniqueness criteria, but that would result a bunch of overlap with devices receiving empty values, which may cause more harm than good... Again, could be totally wrong here but that's what I've been able to determine so far. Any and all help is appreciated, esp if the whole way I'm going about this is just dumb & I need to go a different route lol. Thanks.
Working...