I've been struggling to get the auto discovery process in Zabbix v7 to create SNMPv3 interfaces on my MikroTik devices.
SNMP Walk functions with the same OIDs from the Zabbix VM:
AzureAdmin@node1-c-zabbix01-dev01:~$ snmpwalk -v3 -l authPriv -u ***** -a SHA -A ***** -x AES -X ***** 100.96.6.193 1.3.6.1.2.1.1.1.0
iso.3.6.1.2.1.1.1.0 = STRING: "RouterOS CCR2116-12G-4S+"
AzureAdmin@node1-c-zabbix01-dev01:~$ snmpwalk -v3 -l authPriv -u ***** -a SHA -A ***** -x AES -X ***** 100.96.6.193 1.3.6.1.2.1.1.2.0
iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.14988.1
AzureAdmin@node1-c-zabbix01-dev01:~$ snmpwalk -v3 -l authPriv -u ***** -a SHA -A ***** -x AES -X ***** 100.96.6.193 1.3.6.1.2.1.1.5.0
iso.3.6.1.2.1.1.5.0 = STRING: "*****" AzureAdmin@node1-c-zabbix01-dev01:~$
The default Zabbix logs were not providing anything relevant. I ended up increasing the verbosity from 3(default) to 4, and I get this for all 3 OIDs that I'm checking:
718337:20240709:130513.993 [20] In process_snmp_result() key:'1.3.6.1.2.1.1.1.0' host:'' addr:'100.96.6.193' ret:TIMEOUT_ERROR
718337:20240709:130514.609 [20] End of discovery_net_check_range() druleid:7 type:13 state.count:0 first ip:100.96.6.193 last ip:100.96.6.222 abort:0 ret:0
When I saw this, I increased the timeout from 3 (default) to the max of 30. I'm still getting the same TIMEOUT_ERRORs in the logs.
When I go through the Zabbix GUI to add the interface one at a time to a single host it works without issues, but this is not feasible for the size of the network I plan on monitoring. The discovery rule is using the exact same AuthPriv credentials as my manual SNMP walk and manual interface creation, I've verified that multiple times over.
Interestingly enough, this is only happening with my MikroTik devices - my devices from other vendors work without issue using the exact same discovery rule.
Anyone encounter anything like this or have ideas on what I can try?
SNMP Walk functions with the same OIDs from the Zabbix VM:
AzureAdmin@node1-c-zabbix01-dev01:~$ snmpwalk -v3 -l authPriv -u ***** -a SHA -A ***** -x AES -X ***** 100.96.6.193 1.3.6.1.2.1.1.1.0
iso.3.6.1.2.1.1.1.0 = STRING: "RouterOS CCR2116-12G-4S+"
AzureAdmin@node1-c-zabbix01-dev01:~$ snmpwalk -v3 -l authPriv -u ***** -a SHA -A ***** -x AES -X ***** 100.96.6.193 1.3.6.1.2.1.1.2.0
iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.14988.1
AzureAdmin@node1-c-zabbix01-dev01:~$ snmpwalk -v3 -l authPriv -u ***** -a SHA -A ***** -x AES -X ***** 100.96.6.193 1.3.6.1.2.1.1.5.0
iso.3.6.1.2.1.1.5.0 = STRING: "*****" AzureAdmin@node1-c-zabbix01-dev01:~$
The default Zabbix logs were not providing anything relevant. I ended up increasing the verbosity from 3(default) to 4, and I get this for all 3 OIDs that I'm checking:
718337:20240709:130513.993 [20] In process_snmp_result() key:'1.3.6.1.2.1.1.1.0' host:'' addr:'100.96.6.193' ret:TIMEOUT_ERROR
718337:20240709:130514.609 [20] End of discovery_net_check_range() druleid:7 type:13 state.count:0 first ip:100.96.6.193 last ip:100.96.6.222 abort:0 ret:0
When I saw this, I increased the timeout from 3 (default) to the max of 30. I'm still getting the same TIMEOUT_ERRORs in the logs.
When I go through the Zabbix GUI to add the interface one at a time to a single host it works without issues, but this is not feasible for the size of the network I plan on monitoring. The discovery rule is using the exact same AuthPriv credentials as my manual SNMP walk and manual interface creation, I've verified that multiple times over.
Interestingly enough, this is only happening with my MikroTik devices - my devices from other vendors work without issue using the exact same discovery rule.
Anyone encounter anything like this or have ideas on what I can try?