Ad Widget

Collapse

SNMP Trap Link Up/Down Multiple interfaces flagged

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mistercertified
    Junior Member
    • Apr 2015
    • 1

    #1

    SNMP Trap Link Up/Down Multiple interfaces flagged

    We implemented an SNMP Trap trigger prototype for Link UP/DOWN status on 3 Switches and We receive one trap from one switch in our log (which has correct interface) when we pull the cable but we receive 10 warnings (1actual,9 being other ports down) from different interfaces on that same switch, we receive same interface numbers being down (some ports are not down and they are connected) every time, even we use different switches Always shows 1-2-4-5-6-7-9-10-49 down (we disconnected the cable from port 25 in this example):

    Host Issue Last change Age Info Ack Actions
    HP Procurve SW1
    Interface 1 on HP Procurve SW1 is down 2015-04-02 11:51:13 8s No
    HP Procurve SW1
    Interface 2 on HP Procurve SW1 is down 2015-04-02 11:51:13 8s No
    HP Procurve SW1
    Interface 4 on HP Procurve SW1 is down 2015-04-02 11:51:13 8s No
    HP Procurve SW1
    Interface 5 on HP Procurve SW1 is down 2015-04-02 11:51:13 8s No
    HP Procurve SW1
    Interface 6 on HP Procurve SW1 is down 2015-04-02 11:51:13 8s No
    HP Procurve SW1
    Interface 7 on HP Procurve SW1 is down 2015-04-02 11:51:13 8s No
    HP Procurve SW1
    Interface 9 on HP Procurve SW1 is down 2015-04-02 11:51:13 8s No
    HP Procurve SW1
    Interface 10 on HP Procurve SW1 is down 2015-04-02 11:51:13 8s No
    HP Procurve SW1
    Interface 25 on HP Procurve SW1 is down 2015-04-02 11:51:13 8s No
    HP Procurve SW1
    Interface 49 on HP Procurve SW1 is down 2015-04-02 11:51:13 8s No


    PDU INFO:
    notificationtype TRAP
    version 0
    receivedfrom UDP: [10.77.77.8]:161->[10.77.77.229]
    errorstatus 0
    messageid 0
    community public
    transactionid 8
    errorindex 0
    requestid 0
    VARBINDS:
    DISMAN-EVENT-MIB::sysUpTimeInstance type=67 value=Timeticks: (25644078) 2 days, 23:14:00.78
    SNMPv2-MIB::snmpTrapOID.0 type=6 value=OID: IF-MIB::linkDown
    IF-MIB::ifIndex.25 type=2 value=INTEGER: 25
    SNMP-COMMUNITY-MIB::snmpTrapAddress.0 type=64 value=IpAddress: 10.77.77.8
    SNMP-COMMUNITY-MIB::snmpTrapCommunity.0 type=4 value=STRING: "public"
    SNMPv2-MIB::snmpTrapEnterprise.0 type=6 value=OID: HP-ICF-OID::hpSwitchJ4906A

    What happens is we receive only 1 Trap for the right interface but on zabbix there are 10 other interfaces show up that they are being down.

    When we plug the cable back in all warnings are cleared including 9 others.

    We receive only one notification (which is correct) about status change for the interface.

    This is what we have in trigger prototype:
    {Template SNMP Device:snmptrap["(IF-MIB::linkDown|IF-MIB::linkUp)((.|[[:space:]])*)({#SNMPVALUE})"].str(linkDown)}=1

    We used this guide here:

    Join the friendly and open Zabbix community on our forums and social media platforms.


    We are using Zabbix 2.4 (Latest) on Centos 6.5

    And this is how trigger looks like after prototype applied:

    Network interfaces: Interface 25 on {HOST.NAME} is down {sw1.mrccs.local:snmptrap["(IF-MIB::linkDown|IF-MIB::linkUp)((.|[[:space:]])*)(25)"].str(linkDown)}=1

    Thanks,
  • romale
    Member
    • Mar 2013
    • 53

    #2
    Using space
    {Template SNMP Device:snmptrap["(IF-MIB::linkDown|IF-MIB::linkUp)((.|[[:space:]])*)({#SNMPVALUE})[[:space:]]"].str(linkDown)}=1
    can help

    Comment

    Working...