EIGRP support

This request is rather vague (and old), so I'm not sure what it's looking to achieve.  That could be why it hasn't garnered a qualified response.

To add 2-cents on version 12.2, it does appear NPM recognizes the node is participating in "Cisco EIGRP" and has neighbors (indicated by IP).  However, it doesn't look like it's parsing/recognizing the EIGRP AS Number(s) of which the node is a member.  I have a ticket open on the issue now, but it's unknown whether or not this is a part of the current feature set.

By contrast, a node participating in BGP does indicate the Autonomous System (AS) number.  While I haven't checked all the routing protocols, it appears OSPF doesn't collect the AS number (or Area) either.  Sounds like this may be a can of worms for SolarWinds to address, but competing products do this already (and have for years).

This request is rather vague (and old), so I'm not sure what it's looking to achieve.  That could be why it hasn't garnered a qualified response.

To add 2-cents on version 12.2, it does appear NPM recognizes the node is participating in "Cisco EIGRP" and has neighbors (indicated by IP).  However, it doesn't look like it's parsing/recognizing the EIGRP AS Number(s) of which the node is a member.  I have a ticket open on the issue now, but it's unknown whether or not this is a part of the current feature set.

By contrast, a node participating in BGP does indicate the Autonomous System (AS) number.  While I haven't checked all the routing protocols, it appears OSPF doesn't collect the AS number (or Area) either.  Sounds like this may be a can of worms for SolarWinds to address, but competing products do this already (and have for years).

Routers report EIGRP neighbor changes to my NPM via syslog.  They could also report via traps.  And either could cause NPM to fire off an e-mail, send a text or a pager message, or even perform a script.

I wonder what specific functionality the original requestor familyofcrowes​ imagined?