Following all of the useful SNMP information in the forums I am successfully receiving SNMP traps in Zabbix. However, I have a sort of complex scenario that I hope I can handle in Zabbix.
I have a climate monitor that has a few dry contact inputs. It sends traps that Zabbix catches whenever those alarms are activated. It also sends traps when any of those alarms are cleared. Here's the deal: when an alarm is set, the OID is always the same: enterprises.850.100.2.0.3, and the value sent is the ID number of the alarm. Additional values in the variable bindings of the trap provide a description of the alarm (i.e. which of the dry contracts has been activated). When an alarm is cleared, the OID is always enterprises.850.100.2.0.4, and the value sent is the ID number of the particular alarm that was cleared. The ID number does not identify the sensor -- it is a unique identifier for the particular alarm (it is incremented by one each time the device sends an alarm). As you can see, there can be many different alarms that are set at any given time, and any of those alarms (not just the most recent one set) can be cleared.
So... any thoughts on how to support this is Zabbix? Ideally, I would like the device to be "in alert" when there are any active alarms, then "normal" when they're all gone. Right now I have an "Alarm Set" zabbix trapper item on the host (OID enterprises.850.100.2.0.3) and an "Alarm Clear" item (enterprises.850.100.2.0.4) but that doesn't really do what I want. Is there a way for Zabbix to keep track of the ID #'s of the alarms that were set, and then clear those ID #'s as the clear traps come in? I suspect not, but perhaps there's a clever way of "unpacking" the trap in the snmptrap.sh script...
Thank you!!!
I have a climate monitor that has a few dry contact inputs. It sends traps that Zabbix catches whenever those alarms are activated. It also sends traps when any of those alarms are cleared. Here's the deal: when an alarm is set, the OID is always the same: enterprises.850.100.2.0.3, and the value sent is the ID number of the alarm. Additional values in the variable bindings of the trap provide a description of the alarm (i.e. which of the dry contracts has been activated). When an alarm is cleared, the OID is always enterprises.850.100.2.0.4, and the value sent is the ID number of the particular alarm that was cleared. The ID number does not identify the sensor -- it is a unique identifier for the particular alarm (it is incremented by one each time the device sends an alarm). As you can see, there can be many different alarms that are set at any given time, and any of those alarms (not just the most recent one set) can be cleared.
So... any thoughts on how to support this is Zabbix? Ideally, I would like the device to be "in alert" when there are any active alarms, then "normal" when they're all gone. Right now I have an "Alarm Set" zabbix trapper item on the host (OID enterprises.850.100.2.0.3) and an "Alarm Clear" item (enterprises.850.100.2.0.4) but that doesn't really do what I want. Is there a way for Zabbix to keep track of the ID #'s of the alarms that were set, and then clear those ID #'s as the clear traps come in? I suspect not, but perhaps there's a clever way of "unpacking" the trap in the snmptrap.sh script...
Thank you!!!
Comment