First the details: Zabbix 3.4.8 for Zabbix Server and Proxies on RHEL7 with MySQL Backend.
We have network discovery rules created that are using both sysName.0 and sysObjectID.0 OID's as the checks, and they do work.
The goal: We are trying to set up discovery actions that use both the sysName.0 and sysObjectID.0 OID from the discovery rule(s) in order to place the discovered host(s) in host groups based on both the environment and device type. A substring of the system name indicates if the device is part of the Corporate, Production or Development environment. The sysObjectID indicates what type of device the discovered host is.
The issue: While the discovery rule(s) work, the discovery actions are only able to work when we use one OID or the other, not both. We have done snmpwalk's to verify what type of information should/is coming back from the OID's, but even when we set the discovery action to '=' rather than 'like' when both OID's are evaluated, they still do not perform the desired action. If this were working correctly we would see something like:
returned values like:
sysName like "ts"
sysObjectID like "9.1.1732"
Operation would send host to "Networking/Corp/ASRxxxx" host group, Remove host from "Discovered hosts" host group and apply the "Template X" template.
What are we doing wrong?
We have network discovery rules created that are using both sysName.0 and sysObjectID.0 OID's as the checks, and they do work.
The goal: We are trying to set up discovery actions that use both the sysName.0 and sysObjectID.0 OID from the discovery rule(s) in order to place the discovered host(s) in host groups based on both the environment and device type. A substring of the system name indicates if the device is part of the Corporate, Production or Development environment. The sysObjectID indicates what type of device the discovered host is.
The issue: While the discovery rule(s) work, the discovery actions are only able to work when we use one OID or the other, not both. We have done snmpwalk's to verify what type of information should/is coming back from the OID's, but even when we set the discovery action to '=' rather than 'like' when both OID's are evaluated, they still do not perform the desired action. If this were working correctly we would see something like:
returned values like:
sysName like "ts"
sysObjectID like "9.1.1732"
Operation would send host to "Networking/Corp/ASRxxxx" host group, Remove host from "Discovered hosts" host group and apply the "Template X" template.
What are we doing wrong?
Comment