SNMP trap based trigger generates a lot of events

[chojin]

I'm monitoring some EMC clariion devices who send snmp traps to Zabbix (2.0.2).
I have seperate items configured to catch Informational, Warning, Error and Critical traps and I have a trigger configured as such:

({TRIGGER.VALUE}=0 & {Template SNMP Clariion:snmptrap["Error Trap"].str("2580 - Storage Array Faulted")}=1) | 
({TRIGGER.VALUE}=1 & {Template SNMP Clariion:snmptrap["Informational Trap"].str("2500 - Storage Array is not Faulted")}=0)

This trigger should get PROBLEM state when the storage array is faulted for any reason and should return to OK state when an informational trap 'Storage array is not Faulted' is received.
At first sight this seems to work, however I noticed the duration time of the trigger constantly resetting.

These clariion boxes send a lot of informational traps, and each time an informational trap is received, the trigger is triggered again, generating a new event and resetting the duration time.

Is there a way to prevent this trigger to re-trigger on every informational trap received, but reset it when the 'Storage array is not faulted' trap is received.

[chojin]

The solution seems to be as simple as unchecking the "Multiple PROBLEM even generation" checkbox of the snmptrap items.

[ludanda]

I have the same problem

I recieve a lots of traps of my device, and I don't know if this is problem at zabbix or problem at my device. I try with another device but the problem is almost the same. I catch more than 3 or 4 traps for every alarm.... And the rest of the zabbix it's ok.. but How Can I recive only one trap for alarm?? help ..... plis I can tell you how configure my zabbix if you need it.

[nexgeniter]

The same thing happens, my equipments send a lot of traps for each event, the trigger is fired again and again, sending multiple messages by email erroneous.

They know how to fix it?

Trigger:

({Template_MEI.ACC.1.01:snmptrap.fallback.str(.1.3 .6.1.4.1.5961.4.99.0.4)}=1 & {TRIGGER.VALUE}=0) |({Template_MEI.ACC.1.01:snmptrap.fallback.str(.1. 3.6.1.4.1.5961.4.99.0.4)}#1 & {TRIGGER.VALUE}=1)

Capture of a trap:

14:48:38 20140812 .1.3.6.1.4.1.5961.3.99.0.15 Normal "EVENT MEI PCC 48 VCD" 10.25.228.205 - ZBXTRAP 10.25.228.205 0
14:48:38 20140812 .1.3.6.1.4.1.5961.3.99.0.15 Normal "EVENT MEI PCC 48 VCD" 10.25.228.205 - ZBXTRAP 10.25.228.205 0
14:48:38 20140812 .1.3.6.1.4.1.5961.3.99.0.15 Normal "EVENT MEI PCC 48 VCD" 10.25.228.205 - ZBXTRAP 10.25.228.205 0
14:48:38 20140812 .1.3.6.1.4.1.5961.3.99.0.15 Normal "EVENT MEI PCC 48 VCD" 10.25.228.205 - ZBXTRAP 10.25.228.205 1
14:48:38 20140812 .1.3.6.1.4.1.5961.3.99.0.15 Normal "EVENT MEI PCC 48 VCD" 10.25.228.205 - ZBXTRAP 10.25.228.205 1
14:48:38 20140812 .1.3.6.1.4.1.5961.3.99.0.15 Normal "EVENT MEI PCC 48 VCD" 10.25.228.205 - ZBXTRAP 10.25.228.205 1
14:49:36 20140812 .1.3.6.1.4.1.5961.4.99.0.18 Normal "EVENT MEI ACC 48 VCD" 10.25.200.201 - ZBXTRAP 10.25.200.201 1
14:49:36 20140812 .1.3.6.1.4.1.5961.4.99.0.18 Normal "EVENT MEI ACC 48 VCD" 10.25.200.201 - ZBXTRAP 10.25.200.201 1
14:49:36 20140812 .1.3.6.1.4.1.5961.4.99.0.18 Normal "EVENT MEI ACC 48 VCD" 10.25.200.201 - ZBXTRAP 10.25.200.201 1
14:49:36 20140812 .1.3.6.1.4.1.5961.4.99.0.18 Normal "EVENT MEI ACC 48 VCD" 10.25.200.201 - ZBXTRAP 10.25.200.201 1

[chojin]

Did you try unchecking the checkbox "Multiple PROBLEM event generation" for the trigger?

Also I noticed that you are missing a closing parenthesis at the end of your trigger definition, but I assume that is a typo here and doesn't have anything to do with your problem.