ip sla for routing failover

[tfletcher]

I am using the following config for routing failover.

track 1 rtr 1

ip sla 1

icmp-echo 64.80.115.1

ip sla schedule 1 life forever start-time now

ip route 0.0.0.0 0.0.0.0 Serial0 track 1

ip route 0.0.0.0 0.0.0.0 10.0.0.1 10

ip route 64.80.115.1 255.255.255.255 64.80.42.2

It's working fine, but it fails over after missing a single ping. Is there a way to delay the failover until it's missed 2 or 3 pings?

[Edison Ortiz]

You need to play around with the timeout and frequency values.

Please check out the documentation for more details:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124cg/hsla_c/hsicmp.htm

HTH,

__

Edison.

[tfletcher]

The timeout affects how long it waits for the ping response. The frequency affects how often it sends pings. You cannot set the timeout longer than the frequency, so no matter how you set these values, it still changes state on the 1st ping failure.

[mohammedmahmoud]

Hi Tim,

I believe that the only IP SLA that considers packet loss is the ICMP Path Jitter, i haven't used it before, but it is a nice idea to try it:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124cg/hsla_c/hspthjit.htm

BR,

Mohammed Mahmoud.

[pnicolette]

From http://www.cisco.com/en/US/docs/ios/12_4t/ip_sla/configuration/guide/htthresh.html#wp1082328

Generating Events for Consecutive Violations

To generate a trap (or trigger another operation) after a certain number (x) of consecutive violations, use the consecutive keyword with the optional number-of-occurrences argument:

ip sla reaction-configuration operation-number react reaction-condition threshold-type consecutive [number-of-occurrences] threshold-value rising-value falling-value action-type action-value

The default value for number-of-occurrences is 5.