Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.

During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.

We apologize for the inconvenience while we perform important updates to the Community.

New Member

Routing via Core

Guys,

 

I need a little advice and expertise, I am new to this.

I have a point to point 1Gb link, from my location to another location, every now and then it goes down, at that remote location is dead in the water.

So we have added a VPN in the picture, so I am going to use IPsec site to site VPN as a failover.

I am wondering what is a good way to remove the route from the core to forward the traffic when the line becomes unavailable.

I was thinking about IP SLA monitoring and maybe ICMP the other interface on the core switch, and when it stops replying forward the traffic to the ASA, and do the same thing at the remote location? I am wondering how that will work when the link comes back up also? I am really confused please help and provide your expertise.

 

Thanks,

Chad

2 ACCEPTED SOLUTIONS

Accepted Solutions

Hello chad,Ip sla could work

Hello chad,

Ip sla could work depending on your setup the below would work for static routing -

ip sla 10
icmp-echo (dst-ip) source-ip x.x.x.

freq 5
timeout 2000 (2secs)

ip sla scheduled 10 life forever start now

ip route (remote location_nework subnetmask primary nexthop track 10 1
ip route (remote location_nework subnetmask secondary nexthop 2

 

res

Paul

Please don't forget to rate any posts that have been helpful. Thanks.

hello If the inferface is

hello

 

If the inferface is down then the ip sla sourced address isn't available and it will failover to the higher admin of the secondary static.

 

You can also invoke object tracking with ip sla

track 10 rtr 10 reachability
 delay down 30 up 30

 

or just use object tracking without ip sla:

 

Track 10 interface x/x ip routing | line-protocol
delay down 30 up 30

 

 

res

Paul

Please don't forget to rate any posts that have been helpful. Thanks.
4 REPLIES

Hello chad,Ip sla could work

Hello chad,

Ip sla could work depending on your setup the below would work for static routing -

ip sla 10
icmp-echo (dst-ip) source-ip x.x.x.

freq 5
timeout 2000 (2secs)

ip sla scheduled 10 life forever start now

ip route (remote location_nework subnetmask primary nexthop track 10 1
ip route (remote location_nework subnetmask secondary nexthop 2

 

res

Paul

Please don't forget to rate any posts that have been helpful. Thanks.
New Member

Thanks Paul this is exactly

Thanks Paul this is exactly what I was looking for, now say for instance this route is now active, and the MPLS connection comes back online, what happens? Is that route still forwarding the traffic over the site to site VPN? or does it know when that interface changes from down to up?

hello If the inferface is

hello

 

If the inferface is down then the ip sla sourced address isn't available and it will failover to the higher admin of the secondary static.

 

You can also invoke object tracking with ip sla

track 10 rtr 10 reachability
 delay down 30 up 30

 

or just use object tracking without ip sla:

 

Track 10 interface x/x ip routing | line-protocol
delay down 30 up 30

 

 

res

Paul

Please don't forget to rate any posts that have been helpful. Thanks.
New Member

Paul,Another question, so I

Paul,

Another question, so I setup track 10 on int 4/4 on line protocol status, but is even necessary? Could I just add a second route, ie 10.120.1.1 255.255.0.0 10.200.0.10 2? What direction would you go?

52
Views
0
Helpful
4
Replies
CreatePlease to create content