SNMP Trap to Monitor EIGRP Adjacency Change in Nexus 7000

Available Languages

Download Options

  • PDF     (139.1 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (164.9 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (274.8 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:August 23, 2017
Document ID:211527

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

    Introduction 

    This document describes the Simple Network Management Protocol (SNMP) trap to monitor Enhanced Interior Gateway Routing Protocol (EIGRP) adjacency change in Nexus 7000. The Nexus only supports two traps for EIGRP-MIB, cEigrpAuthFailureEvent and cEigrpRouteStuckInActive, but no SNMP traps for EIGRP neighbors up/down (cEigrpNbrDownEvent). 
    A viable workaround to generate SNMP traps to monitor EIGRP adjacency changes would be to configure two EEM scripts - one for Neighbor Up and one for Neighbor Down - triggered based on the syslog pattern.

    Example

    event manager applet EIGRP_TRAP_nbr_dwn
  event syslog pattern "EIGRP-5-NBRCHANGE_DUAL.*down"
  action 1.1 snmp-trap strdata "EIGRP Neighbor Down"
event manager applet EIGRP_TRAP_nbr_up
  event syslog pattern "EIGRP-5-NBRCHANGE_DUAL.*up"
  action 1.1 snmp-trap strdata "EIGRP Neighbor Up"
    You can then test by flapping a Layer 3 interface (you can create a test Switch Virtual Interface (SVI) to verify as to not disrupt connectivity):
    2017 Jul 12 15:51:06 N7K-AGG2 %EIGRP-5-NBRCHANGE_DUAL:  eigrp-10 [4049] (default-base) IP-EIGRP(0) 10: Neighbor 10.10.10.84
     (Vlan1064) is down: holding time expired
2017 Jul 12 15:51:10 N7K-AGG2 %EIGRP-5-NBRCHANGE_DUAL:  eigrp-10 [4049] (default-base) IP-EIGRP(0) 10: Neighbor 10.10.10.84
     (Vlan1064) is up: new adjacency
    Confirm that the Nexus sends these out correctly and check your SNMP monitoring tool - output might differ slightly and it depends on the tool used:
    You can also review these SNMP traps via a Wireshark capture:

    Note: It depends on the version of Wireshark, the string will not be in human readable text but can be filtered via "snmp.value.octets contains "EIGRP".

    You can also verify that the Nexus sends these upon the Embedded Event Manager (EEM) triggering with Ethanalyzer. See the example:
    N7K-A-Admin# ethanalyzer local interface mgmt display-filter snmp limit-c 0

Capturing on mgmt0
2017-07-12 15:43:37.431067 10.122.140.96 -> 172.18.121.3 SNMP 278 snmpV2-trap 1.3.6.1.2.1.1.3.0 1.3.6.1.6.3.1.1.4.1.0 1.3.6.1.4.1.9.10.134.1.2.3.1.2.1 1.3.6.1.4.1.9.10.134.1.2.3.1.6.1 1.3.6.1.4.1.
9.10.134.1.2.3.1.7.1 1.3.6.1.4.1.9.10.134.1.2.3.1.9.1 1.3.6.1.4.1.9.10.134.1.2.3.1.10.1 1.3.6.1.4.1.9.10.134.1.2.3.1.11.1

    Note: Pre NX-OS 7.x does not give us the option to configure snmp-server enable traps syslog which will in turn allow you to monitor the entire logging log itself then filter for the EIGRP messages. This feature was added in releases, 7.x and later.

    TAC Authored

    Contributed by Cisco Engineers

    • Andrea Testino
      Cisco TAC Engineer

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco

    This Document Applies to These Products