Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

ip sla track problem with static routes

Unanswered Question
Mar 22nd, 2014
User Badges:

IOS 12.2(33)SXI5

Cisco 6500 Sup 720



Every guide I read says this tracking ip sla stuff should be so easy.


This doesn't work.

The commands I'm running are:


ip sla 1


timeout 500

threshold 200

frequency 5


ip sla schedule 1 life forever start-time now


track 1 ip sla 1 reachability


ip route track 1

ip route 100

----------------------------------------------------------------------------------------------------- is my sonicwall for my primary site is my 6500 at my secondary site going across a MetroE


This configuration does not work. If I add a third route

ip route (without the track 1 at the end)

internet works, but if I disconnect the internet my reachability goes down, but running a "show ip route" doesn't point my new gateway of last resort over to


I'm not sure what I'm going wrong.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
paul driver Sun, 03/23/2014 - 01:56
User Badges:
  • Green, 3000 points or more
Hello All that stands out from your post is your sla statement. your floating statice and track statements seem fine. Provide a destination AND source address in you sla statement No ip sla 1 Ip sla 1 Icmp-echo source-ip x.x.x.x Freq 5 Exit Ip sla schedule 1 start now life forever Res Paul
paul driver Sun, 03/23/2014 - 01:58
User Badges:
  • Green, 3000 points or more

Apologies for the default formattting

cyr0nk0r1 Sun, 03/23/2014 - 09:58
User Badges:

I've tried that.


icmp-echo source ip

( is vlan 1 of management ip of the 6500 I'm working on)


same problem.

If the default route that im trying to use (the one pointing to has the track statement at the end of it, internet goes down for all my clients.

Richard Burts Sun, 03/23/2014 - 12:00
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

I am not clear whether the problem here is that track and ip sla are not working or whether it is that your backup static default route is not working. Perhaps you can clarify.?


The output of show commands for  track and ip sla might shed some light on the issue. And the output of show ip route while you are having the problem might also be helpful.





cyr0nk0r1 Sun, 03/23/2014 - 13:04
User Badges:

The problem is not the ip sla. Doing show ip sla track-table shows me that the tracking is working properly. The 6500 is pinging and getting responses and showing the status as [ok].

The problem is the INTERNET for the clients.

Having only these 2 routes static defined

ip route track 1

ip route 100

doesn't work. Having the "ip route track 1" with the track 1 statement after it casues internet to fail for my clients behind the 6500.

paul driver Sun, 03/23/2014 - 12:16
User Badges:
  • Green, 3000 points or more



do you have multiple paths to this destination and source if so then the  sla tracking won't kick in


as suggested by Richard what does the traciking and sla stats show.




cyr0nk0r1 Sun, 03/23/2014 - 10:26
User Badges:

I'm not sure what you wanted me to gleen from that thread since you didn't provide any information.

However if you're suggesting that I have a permanent route

ip route permanent

this doesn't solve the problem. Yes, pings to still work from all my clients, but the rest of the internet is STILL down unless that third all zero's route to without the track statement is there.

Vishesh Verma Sun, 03/23/2014 - 12:08
User Badges:
  • Bronze, 100 points or more

Please check and share the results of the show ip sla statistics and show track?

Check for the return code for ip sla and track state.



cyr0nk0r1 Sun, 03/23/2014 - 19:03
User Badges:

Fixed by adding a third route with a higher admin cost.


ip route 10 track 1

ip route 20

ip route 30

svansteensel Mon, 03/24/2014 - 05:22
User Badges:

This is a long shot, but are you using NAT/PAT in your configuration? That might cause some issues with dual default route as well.

I also have "ip sla auto discovery" command in my config. Dont know if this is mandatory or maybe a default.

For all I see your IP SLA looks good, so it might be NAT or other routing protocols running that prevent failover of default route to


This Discussion