I generated a Cisco 4506 Template, which had 586 Items, plus Triggers and Graphs. The retrieval of ifOperStatus, ifAdminStatus, ifInOctets, and ifOutOctets data worked fine. Items keys were of the form ifOperStatus.n.
The problem came with I tried setting up a SNMP Trap Receiver for linkUp and linkDown via zabbix_sender. I wanted to set the same keys as the SNMP Agent, ie., ifOperStatus.n and ifAdminStatus.n, but the zabbix_sender input host:key is checked by the server that it is Item Type of Zabber Trapper or Zabbix Active. If not the traps data is silently discarded. (These need to be logged to reduce debugging time.)
You cannot create a separate Zabbix Trapper Item with the same key as the original SNMP Agent Type. I wanted a single key containing the current interface status and wanted the Triggers expression to reference only one key. Two keys can be out of sync for half a poll period at a status change.
Is it reasonable to allow zabbix_sender input to update non-Zabbix Trapper Items? Is there something I am missing that allows multiple updaters?
Attached is a patch to 1.8.4 to allow SNMP Traps (via zabbix_sender) to also update SNMP Agent keys. This worked successfully in our Zabbix evaluation platform.
The problem came with I tried setting up a SNMP Trap Receiver for linkUp and linkDown via zabbix_sender. I wanted to set the same keys as the SNMP Agent, ie., ifOperStatus.n and ifAdminStatus.n, but the zabbix_sender input host:key is checked by the server that it is Item Type of Zabber Trapper or Zabbix Active. If not the traps data is silently discarded. (These need to be logged to reduce debugging time.)
You cannot create a separate Zabbix Trapper Item with the same key as the original SNMP Agent Type. I wanted a single key containing the current interface status and wanted the Triggers expression to reference only one key. Two keys can be out of sync for half a poll period at a status change.
Is it reasonable to allow zabbix_sender input to update non-Zabbix Trapper Items? Is there something I am missing that allows multiple updaters?
Attached is a patch to 1.8.4 to allow SNMP Traps (via zabbix_sender) to also update SNMP Agent keys. This worked successfully in our Zabbix evaluation platform.