Looks like there're very fews EIGRP traps possible :
http://www.cisco.com/en/US/docs/ios/12_3t/12_3t14/feature/guide/gteigmib.html#wp1067306
EIGRP Notifications
The EIGRP MIB provides limited notification (TRAP) support for stuck-in-active (SIA) and neighbor authentication failure events. The snmp-server enable traps eigrp command is used to enable EIGRP notifications on a Cisco router. Support for TRAP events is not activated until a trap destination is configured with the snmp-server host command and a community string is defined with the snmp-server community command. EIGRP notifications are described in Table 6.
Table 6 EIGRP Notifications
EIGRP Traps (Notifications) | Description |
cEigrpAuthFailureEvent | When EIGRP MD5 authentication is enabled on any interface and neighbor adjacencies are formed, a notification is sent if any adjacency goes down as a result of an authentication failure. This notification will be sent once per down event. This notification includes the source IP address of the neighbor from which the authentication failure occurred. |
cEigrpRouteStuckInActive | During the query phase for a new route to a destination network, the route is placed in the active state (an alternate path is actively being sought) and a query packet is broadcast to the network. If no replies are received to the query, an SIA query packets are broadcast. If a reply is not received for the SIA queries, the neighbor adjacency is dropped, the route is declared SIA, and this notification is sent. |
However, your router would have generated the pertinent syslog messages:
%DUAL-5-NBRCHANGE: IP-EIGRP : Neighbor X.X.X.X () is down: K-value mismatch error message
I'd simply monitor such events with a syslog analysis tool. But if you must receive such notification as an SNMP trap on 10.10.10.1, you could either
1) configure:
add
snmp-server enable traps syslog
change
snmp-server host 10.10.10.1 public eigrp snmp
to
snmp-server host 10.10.10.1 public eigrp snmp syslog
or 2) configure an EEM applet to generate an SNMP trap catching the "DUAL-5-NBRCHANGE: Neighbor X.X.X.X () is down" syslog pattern.
