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

ip sla - requiring two failed tests

I would like to require ip sla (here http get test) to fail two tests in a row before being considered "down" (and triggering a route change). Is it possible to do this with IP SLA? I'm on 12.4 IOS. Thank-you.

-------current ip sla config------

track 113 rtr 3

ip sla 3

http get

ip sla schedule 3 life forever start-time now

ip route track 113

ip route 150

Community Member

Re: ip sla - requiring two failed tests


Good question!

Have a same problem with icmp-ech sla.

One fault is not fault!!!

Any idea ??

Community Member

Re: ip sla - requiring two failed tests

I have found lots of information such as the URL below. But I have not been able to dial this in in my tests. It still winds up failing on a single ping loss. We use Speak Easy at some of our sites and they do not support BGP (or any routing protocol.) It would be so helpful to be able to fail traffic to our MPLS circuit if say 3 out of 5 pings are lost (and restore when better.) You can see in this doc the IP SLA understands "xofy". I just have not been able to put it all together so that "rtr x" fails based on the xofy pings. Of anyone gets this cookin' in their lab - please share the mojo!

Hall of Fame Super Bronze

Re: ip sla - requiring two failed tests

I don't have any equipment to test with at the moment, but you can look into the commands:

ip sla monitor reaction-configuration and ip sla monitor reaction-trigger




Community Member

Re: ip sla - requiring two failed tests

This is what I have done, hope it helps someone.


track 1 interface FastEthernet0/0 line-protocol
track 10 rtr 10 reachability

interface FastEthernet0/1
standby 1 priority 110
standby 1 preempt
standby 1 track 1 decrement 30
standby 1 track 10 decrement 15

ip sla 10
icmp-echo ***next hop***
frequency 10
ip sla schedule 10 life forever start-time now

Secondary router has a priority of 90 so if line goes down it fails over straight away (track 1) but if ping fails (track 10) the priority only drops to 95 so primary stays up. If next ping fails, it drops to 80 and fails over, but if next ping OK then goes back to priority 110. So it requires two consequtive ping drops to fail.

Community Member

Re: ip sla - requiring two failed tests


Our solution for same problem is the following.

track 100 ip sla 1 reachability

delay down 70

ip sla 1


frequency 30

ip sla schedule 1 life forever start-time now

it is working well,


CreatePlease to create content