09-03-2010 05:36 AM - edited 03-04-2019 09:39 AM
Hi,
please see my setup attached.
I have static routing between MY SITE and the CUSTOMER SITE. There are IPSec VPN Tunnels with "tunnel protection" between the routers. Yet I would like to have automatic failover, when either the Internet connection or the MPLS connection goes down.
The 1st option would be to implement tracking via sla monitoring:
R03 has two static routes, one with metric 99:
1. ip route <CUSTOMER_LAN> <TUNNEL_IF_R01> track 10
2. ip route <CUSTOMER_LAN> <LAN_IF_R04> 99
R03 pings tunnel interface from R01, if it gets no reply, then tracking fails, and the 1st route gets deleted from the routing table. The 2nd route is used then. Same configs on the other routers vice versa.
This 1st option works fine. But I am searching for a second option. If I had a tunnel interface on the routers, that wents down, when the peer isn't reachable, then the primary static route would go down without tracking. This would be a much more smart and scalable solution to the problem. But how do I implement this?
Thanks for your help!
Solved! Go to Solution.
09-03-2010 06:31 AM
Hello,
Route tracking is the easiest and better option to configure failover. In
your case, if you are looking for events like VPN tunnel going down, then
you could try EEM (Embedded Event Management). But, I would think route
tracking is an easier option as, in either case, you need to know that you
are not able to reach the remote destination and that is the reason the
tunnel went down.
EEM information:
http://www.cisco.com/en/US/docs/ios/netmgmt/configuration/guide/nm_eem_polic
y_cli_ps6441_TSD_Products_Configuration_Guide_Chapter.html
Hope this helps.
Regards,
NT
09-03-2010 06:31 AM
Hello,
Route tracking is the easiest and better option to configure failover. In
your case, if you are looking for events like VPN tunnel going down, then
you could try EEM (Embedded Event Management). But, I would think route
tracking is an easier option as, in either case, you need to know that you
are not able to reach the remote destination and that is the reason the
tunnel went down.
EEM information:
http://www.cisco.com/en/US/docs/ios/netmgmt/configuration/guide/nm_eem_polic
y_cli_ps6441_TSD_Products_Configuration_Guide_Chapter.html
Hope this helps.
Regards,
NT
09-14-2010 07:18 AM
Thanks for your help!
I finally came to the conclusion, that tracking is the best solution....
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide