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
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.
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.
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.