Ad Widget

Collapse

Snmp-trap triggering the same trigger multiple times on the same device.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Snmp-trap triggering the same trigger multiple times on the same device.

    Zabbix 4.2.4 on Centos7

    Hi everyone.

    I monitored dozens of juniper network devices and used the snmp-trap items to collect trap information from these devices, I recently noticed that some snmp-trap alert messages were not handled correctly.
    That is when multiple snmp-traps of different events but same type are generated on one device sent to zabbix-server, but treated as same event by zabbix-server , and given the same event-id , but clearly this is not same event.

    Here are my item-key settings and others:

    Item
    Name:ospfNbrStateChange-test
    Type:SNMP trap
    Key:snmptrap["ospfNbrStateChange"]
    Click image for larger version  Name:	Items.jpg Views:	1 Size:	46.9 KB ID:	384537

    Output information after preprocessing
    title:ospfNbrStateChange
    nbrouteId: xxx.xxx.12.255
    localRID: xxx.xxx.12.253
    nbif: xxx.xxx.12.235
    status:full⑧
    Click image for larger version  Name:	Latest data.jpg Views:	1 Size:	85.6 KB ID:	384538

    Triggers
    Name:ospf-Staus-test
    Problem expression:{SNMP traps:snmptrap["ospfNbrStateChange"].str(full⑧)}=0
    Recovery expression:{SNMP traps::snmptrap["ospfNbrStateChange"].str(full⑧)}=1
    Click image for larger version  Name:	Triggers.jpg Views:	1 Size:	71.8 KB ID:	384539
    Click image for larger version  Name:	Actions.jpg Views:	1 Size:	61.2 KB ID:	384540
    Click image for larger version  Name:	Action log.jpg Views:	1 Size:	61.8 KB ID:	384541



    Am I setting the trigger incorrectly? Or what else?
    Any suggestions? Or should I report a bug?

    Best regards
    Last edited by Gary.W; 19-08-2019, 14:40.

Announcement

Collapse
No announcement yet.
Working...
X