Ubuntu 14.04 LTS 64-bit, running as a virtual machine under VMWare Workstation v9, on Windows 7 pro 64-bit
I have setup a discovery rule. The check are :
type: SMNPv2 agent, port: 161, community: : public, OID: .220.127.116.11.18.104.22.168.0
type: SMNPv2 agent, port: 161, community: : public, OID: .22.214.171.124.126.96.36.199.0
type: SMNPv2 agent, port: 161, community: : public, OID: .188.8.131.52.184.108.40.206.0
type: SMNPv2 agent, port: 161, community: : public, OID: .220.127.116.11.18.104.22.168.0
Then, I go in Monitoring->Discovery
I only see the detection of
.22.214.171.124.126.96.36.199.0, .188.8.131.52.184.108.40.206.0 and .220.127.116.11.18.104.22.168.0
If, on the command line, I use snmpwalk or snmpget with the same "addresses", i can read the 4 values.
The standard address .22.214.171.124.126.96.36.199.0 contains the OID of the device which I want to use to select the templates,...
I believe that Zabbix choke on the type of this field which is OID. Just modify the case in order to consider OID field as a string should fix the problem and make Zabbix easier to use.
ZBX-4054 Discovery of sysObjectID doesn't work