Problems with IP SLA on Cisco 2921

[Luis Diego Gonzalez Briones]

Hello there, i have a quick question about ip sla on a 2921 Router, i'm configuring it with the following parameters in order to test track. At the beggining traffic is up and it puts status on track with UP. If i take down the remote ip, SLA remains with status UP and the Track UP. Any idea about this behavior? I supposed other end goes down ip sla has to reporte it and track has to go down, but in this case is not working... here the configuration:

ip sla 1

icmp-echo x.x.x.18 source-interface GigabitEthernet0/0

timeout 1000

threshold 2

verify-data

frequency 15

ip sla schedule 1 life forever start-time now

track 1 ip sla 1 reachability

Take a look of the debug:

RTR-GTM2(config)#

*Oct 22 05:21:29.055: IP SLAs(1) Scheduler: saaSchedulerEventWakeup

*Oct 22 05:21:29.055: IP SLAs(1) Scheduler: Starting an operation

*Oct 22 05:21:29.055: IP SLAs(1) echo operation: source IP:x.x.x.10

*Oct 22 05:21:29.055: IP SLAs(1) echo operation: Sending an echo operation - destAddr=x.x.x.18, sAddr=x.x.x.10

*Oct 22 05:21:29.055: IP SLAs(1) echo operation: Sending ID: 30

*Oct 22 05:21:29.055: IP SLAs(1) echo operation: RTT=1

*Oct 22 05:21:29.055: IP SLAs(1) Scheduler: Updating result

*Oct 22 05:21:29.055: IP SLAs(1) Scheduler: start wakeup timer, delay = 15000

*Oct 22 05:21:44.055: IP SLAs(1) Scheduler: saaSchedulerEventWakeup

*Oct 22 05:21:44.055: IP SLAs(1) Scheduler: Starting an operation

*Oct 22 05:21:44.055: IP SLAs(1) echo operation: source IP:x.x.x.10

*Oct 22 05:21:44.055: IP SLAs(1) echo operation: Sending an echo operation - destAddr=x.x.x.18, sAddr=x.x.x.10

*Oct 22 05:21:44.055: IP SLAs(1) echo operation: Sending ID: 30

*Oct 22 05:21:44.055: IP SLAs(1) echo operation: RTT=1

*Oct 22 05:21:44.055: IP SLAs(1) Scheduler: Updating result

*Oct 22 05:21:44.055: IP SLAs(1) Scheduler: start wakeup timer, delay = 15000

*Oct 22 05:21:59.055: IP SLAs(1) Scheduler: saaSchedulerEventWakeup

*Oct 22 05:21:59.055: IP SLAs(1) Scheduler: Starting an operation

*Oct 22 05:21:59.055: IP SLAs(1) echo operation: source IP:x.x.x.10

*Oct 22 05:21:59.055: IP SLAs(1) echo operation: Sending an echo operation - destAddr=x.x.x.18, sAddr=x.x.x.10

*Oct 22 05:21:59.055: IP SLAs(1) echo operation: Sending ID: 30

*Oct 22 05:21:59.055: IP SLAs(1) echo operation: RTT=1

*Oct 22 05:21:59.055: IP SLAs(1) Scheduler: Updating result

*Oct 22 05:21:59.055: IP SLAs(1) Scheduler: start wakeup timer, delay = 15000

*Oct 22 05:22:14.055: IP SLAs(1) Scheduler: saaSchedulerEventWakeup

*Oct 22 05:22:14.055: IP SLAs(1) Scheduler: Starting an operation

*Oct 22 05:22:14.055: IP SLAs(1) echo operation: source IP:x.x.x.10

*Oct 22 05:22:14.055: IP SLAs(1) echo operation: Sending an echo operation - destAddr=x.x.x.18, sAddr=x.x.x.10

*Oct 22 05:22:14.055: IP SLAs(1) echo operation: Sending ID: 30

*Oct 22 05:22:14.055: IP SLAs(1) echo operation: RTT=1

*Oct 22 05:22:14.055: IP SLAs(1) Scheduler: Updating result

*Oct 22 05:22:14.055: IP SLAs(1) Scheduler: start wakeup timer, delay = 15000

RTR-GTM2(config)#

RTR-GTM2(config)#

RTR-GTM2(config)#

RTR-GTM2(config)#

RTR-GTM2(config)#

RTR-GTM2(config)#

RTR-GTM2(config)#

I took the other end down

RTR-GTM2(config)#! other end down

RTR-GTM2(config)#

RTR-GTM2(config)#

RTR-GTM2(config)#

RTR-GTM2(config)#do ping x.x.x.1

*Oct 22 05:22:29.055: IP SLAs(1) Scheduler: saaSchedulerEventWakeup

*Oct 22 05:22:29.055: IP SLAs(1) Scheduler: Starting an operation

*Oct 22 05:22:29.055: IP SLAs(1) echo operation: source IP:x.x.x.10

*Oct 22 05:22:29.055: IP SLAs(1) echo operation: Sending an echo operation - destAddr=x.x.x.18, sAddr=x.x.x.10

*Oct 22 05:22:29.055: IP SLAs(1) echo operation: Sending ID: 30

*Oct 22 05:22:29.055: IP SLAs(1) echo operation: RTT=1

*Oct 22 05:22:29.055: IP SLAs(1) Scheduler: Updating result

*Oct 22 05:22:29.055: IP SLAs(1) Scheduler: start wakeup timer, delay = 150008

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to x.x.x.18, timeout is 2 seconds:

.....

Success rate is 0 percent (0/5)

! Ping not responding but IP SLA still shows up.

RTR-GTM2(config)#

RTR-GTM2(config)#

RTR-GTM2(config)#

RTR-GTM2(config)#

RTR-GTM2(config)#

RTR-GTM2(config)#

RTR-GTM2(config)#

RTR-GTM2(config)#

RTR-GTM2(config)#

RTR-GTM2(config)#

*Oct 22 05:22:44.055: IP SLAs(1) Scheduler: saaSchedulerEventWakeup

*Oct 22 05:22:44.055: IP SLAs(1) Scheduler: Starting an operation

*Oct 22 05:22:44.055: IP SLAs(1) echo operation: source IP:x.x.x.10

*Oct 22 05:22:44.055: IP SLAs(1) echo operation: Sending an echo operation - destAddr=x.x.x.18, sAddr=x.x.x.10

*Oct 22 05:22:44.055: IP SLAs(1) echo operation: Sending ID: 30

*Oct 22 05:22:44.055: IP SLAs(1) echo operation: RTT=1

*Oct 22 05:22:44.055: IP SLAs(1) Scheduler: Updating result

*Oct 22 05:22:44.055: IP SLAs(1) Scheduler: start wakeup timer, delay = 15000

RTR-GTM2(config)#

RTR-GTM2(config)#

Other end is connected on a different segment, but icmp is full open between the two zones.

Any help appreciated.

[Luis Diego Gonzalez Briones]

Hi, I am making some tests, if i try to put an sla on the interlan lan interface, SLA detects the flapping and move the status to down, when other end goes up the sla passes status to up again.

Currently Outside interface, where i'm having trouble, has nat outside and a crypto map applied to it, but not even ip sla is detecting down of the default gateway.

The most interesting thing is that if i remove the ip sla from configuration, track detects other end is down or up.

RTR-GTM2(config)#no ip sla 1

RTR-GTM2(config)#

Oct 22 01:34:34.647: Track: 1 Change #3 ip sla 1, state Up->Down

Oct 22 01:34:34.647: %TRACKING-5-STATE: 1 ip sla 1 state Up->Down

Any help welcome.

[Luis Diego Gonzalez Briones]

IOS Version 15.0 running on Router was the problem. Upgraded to 15.2.1. Bug fixed with this upgrade: CSCsy37122.

Related documentation is found in this link:

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsy37122&from=summary