IP SLA revisions?

[DrVoIP]

I use a simple IP SLA to track status of a next hop router on an ip route using icmp-echo.  When the interface is down, the next ip route is used which has a highe metric.  Simple enough.   Here is my issue, in the configuration mode my 2811 no longer accepts the command "IP SLA 1"  which I use to describe my echo interface,timeout, threshold, frequency.   If I type IP SLA ?   I get this list:

Keychain blah blah

Responder blah blah

Server blah blah

Which one replaced the way I have been doing it?

Peter Buswell (aka DrVoIP)
http://blog.drvoip.com       

[singhaam007]

hello,

try like this

ip sla monitor 1
  type echo protocol ipIcmpEcho 12.34.45.1 (1st ISP)
  threshold 3
  frequency 5

ip sla monitor schedule 1 life forever start-time now

ip sla monitor 2
  type echo protocol ipIcmpEcho 23.34.56.1 (second ISP)
  threshold 3
  frequency 5

ip sla monitor schedule 2 life forever start-time now

!

track 101 rtr 1 reachability
!
track 102 rtr 2 reachability

please see this link for detail information about ip sla Keychain,Responder and Server

http://www.cisco.com/en/US/technologies/tk648/tk362/tk920/technologies_white_paper09186a00802d5efe.html

please rate if this helps,

thanaks

[DrVoIP]

Unfortunately I can not type the command "IP SLA Monitor" 

As I indicated before, the only option I can enter after "IP SLA" is Keychain, Server or Responder

I am running (C2900-UniversalK9-M) Versioin 15.1(4)M2 Release Software (fc1)

Peter Buswell (aka DrVoIP)
http://blog.drvoip.com

[singhaam007]

hello,

check this like it will help you.

its same issue.

https://learningnetwork.cisco.com/thread/46219

please rate if this help

thanks

[DrVoIP]

Researching this through CISCO I now udnerstand that the capbility is still there, but in Version 15 it has changed substantially.   This document outlines the new process:

http://http://www.cisco.com/en/US/docs/ios-xml/ios/ipsla/configuration/15-2mt/sla_udp_echo.html

I hope this helps those that invested in trying to help me.  Thanks all!

Peter Buswell (aka DrVoIP)
http://blog.drvoip.com

[DrVoIP]

Amrinder - Thinkng about your configuration some more:

What we were using this for, is to ping next hop router to determin reachability;

We set an ip route 0.0.0.0 0.0.0.0 1.1.1.1 Track 1

then added ip route 0.0.0.0 0.0.0.0 2.2.2.2 10

under the older IP SLA configuration you would indicate the source interface and then ping the next hop to death.  If it failed, the higher metric route would take over;

Not seeing how the source interface is specified in your suggested configuration?  Nor how you would apply the Track to the default route?

[DrVoIP]

To be clear - Version 15 of IOS makes substantial changes in how IP SLA is  configured and opens up an entirely new feature set.   Great progress!   As to my original post, the problem was two fold, the first being that the router did not have a DATA license.  The IP SLA features needed to do what I wanted to do require the DATA license.  If you do a Show Version you will see what licenses your router has.   Amrinder above did have the best answer as to how the new configuration would look in the new version.

Thanks all!

Peter Buswell (aka DrVoIP)
http://blog.drvoip.com

[gduvall]

I realize this is old but I ran into the same issue with a router I inherited that did not have a data license.

This seems to work for me:

track 1 ip route 5.6.7.1 255.255.255.255 reachability

ip route 0.0.0.0 0.0.0.0 5.6.7.1 track 1

ip route 0.0.0.0 0.0.0.0 10.11.12.13 10