I've searched high and low for an answer to this but haven't found anything specific for my situation. We have 7 remote sites and one headquarter site. All sites are connected via a primary MPLS cloud and all remote sites have a local Comcast cable circuit terminated on an ASA for internet failover. IP SLA for the internet connection works as expected. Now, I understand how to configure IP SLA to track the availability of static default routes, but we use EIGRP at our remote locations for enterprise traffic. The idea is that we want to track our MPLS neighbor from the core switch at each remote site, in the event that the MPLS neighbor is no longer reachable, we want to install a static route for all LAN traffic to go through a VPN I have set up on the ASA back to the headquarter office. This static route would replace all redistributed EIGRP routes pointing out towards the MPLS provider until such time as the MPLS neighbor is once again reachable. I feel I'm missing something very simple but I just can't pinpoint it.
Any help is greatly appreciated,
Is the above from a remote site ?
If so you have nothing to do because you already have a default route for internet anyway. If the MPLS network goes down the EIGRP routes are lost so the default route would be used not just for internet but also the other sites connected to the MPLS network.
So does each remote site have it's own internet connection ?
Sorry about all the questions,, just want to make sure i fully understand the current setup.