How do I get started using PI 3.1 to monitor non-preferred routes.

[hetteldorf]

We have several locations running with redundanct connections via a DMVPN connection and a MPLS connection.   Almost all traffic is from a remote location to corporate.   Several time a week our phone traffic (which should be on MPLS) fails over to DMVPN.    We would like to fail back automatically or at least get an email indicating we are no longer running the preferred route.

The (Windstream) MPLS routes are learned via BGP, the DMVPN via eigrp.

Can we get PI 3.1 to fail back to the preferred routes when they return?

Can we get notification when the routes fail to the non-preferred routes?

Is PI the place to do this or do we need to configure metrics in the routers?   Or both?

Is bgp causing restrictions in our options?

Any hints? comments? or links to docs?

[Georg Pauwen]

Hello,

admin distance for eBGP is 20 and for EIGRP 90, so your BGP route should always be preferred, and EIGRP should be the backup. I understand the fail back doesn't work...can you post the configuration of the corporate and one of the remote routers ?

I guess you could use PI to custom MIB poll the routing table (oid is 1.3.6.1.2.1.4.21 - ipRouteTable), but a simple IP SLA tracking would probably work better. Or an EEM script, which could also send an email in case a preferred route is in use (or not)...