"BGP Routing Neighbors Defined But Not Peering" -- need EIGRP equivalent

"BGP Routing Neighbors Defined But Not Peering" ... is an out of the box alert that comes with NPM. I need to do the same thing but with EIGRP neighbors, not with BGP.

There are several historical threads in the forums here that seem to match discussions on EIGRP but are locked and archived and I cannot see them.

If I have Tunnel X, and the eigrp neighbor on that tunnel goes down / unreachable, I need to generate an alert. (These are Cisco 4221 routers)

Thanks in advance for your help!

Find more posts tagged with

neighbors

eigrp_neighbors

Comments

stuartd

Have you tried the advice here: https://solarwindscore.my.site.com/SuccessCenter/s/article/How-to-create-alert-for-EIGRP-neighbor-status-change?language=en_US ?

Chris-S

Stuart - thanks for replying.

Chris-S

Stuart - Thank you for replying.

I looked at that example and tried multiple variants of it on our network. Nothing ever triggered an EIGRP neighbor missing on any interface on any node. I specifically blocked neighbors on some test routers while keeping the tunnel interfaces up which should have triggered the alert.

Would you have any other ideas?

stuartd

EIGRP and BGP seem to be problematical no matter what NMS you use.

What I do see folks doing is using SNMP Traps. But unless you are paying for OLA then be aware that the built-in version of 'traps' is restricted in performance and capabilities. In reality it could mean your message about neighbour changes doesn't get seen for some time, or the message could even just get dropped.