Odd Discovery issue

[ddougan]

I've been working to use Discovery Actions to help populate inventory. As part of testing this, I removed the firewall entry for a client site as I wanted Discovery to pick it up again and set it via a new Action I created:


The device has SNMP enabled, and if I run an snmpget from the Zabbix proxy for the OID containing the received value, it responds correctly. I have the same Discovery rule at another client, and the firewall there (same model) was picked up by discovery. The only difference between the two is that the problem one has an IP address of 192.168.0.254, and the found one's IP is 192.168.100.0. The Discovery rule for the problem client is:


I''ve restarted the proxy in case it had hung, but no improvement. I feel I am missing something obvious here, but I can't see what. I'd appreciate any thoughts.


Thanks,

Des

[ddougan]

I've increased the log level on the proxy at this site, and I see this during discovery:

80179:20210424:220252.441 In get_values_snmp() host:'' addr:'192.168.0.254' num:1
80179:20210424:220252.441 SNMP [[email protected]:161]

For some reason, the host name is blank in the discovery; however if I query the device, I get:

snmpwalk -v 2c -c public -Os 192.168.0.254 system
sysDescr.0 = STRING: Calyptix AccessEnforcer
sysObjectID.0 = OID: enterprises.18105
sysUpTimeInstance = Timeticks: (17070186) 1 day, 23:25:01.86
sysContact.0 = STRING:
sysName.0 = STRING: ae800-smiles.smilesbypocock.com

I've checked the GUI for the firewall, and see the name there, too. I viewed the same information on another firewall on another site, and the host field is what is contained in sysName.0. I changed it as a test (from ae800 to ae800-smiles), but as can be seen above, it makes no difference.

Anyone seen this kind of behaviour with SNMP?



Thanks,

Des