08-13-2014 07:17 AM - edited 03-04-2019 11:32 PM
I have an IP SLA as below, the result is always timeout. have tried debug, but not much information
ip sla 25
icmp-echo 10.255.32.25 source-ip 10.255.32.1
timeout 2000
vrf Corp
frequency 10
RTR01#sh ip sla statistics 25
Round Trip Time (RTT) for Index 25
Latest RTT: NoConnection/Busy/Timeout
Latest operation start time: .14:51:44.215 BST Wed Aug 13 2014
Latest operation return code: Timeout
Number of successes: 0
Number of failures: 28
Operation time to live: Forever
-RTR01#sh ip sla conf 25
IP SLAs, Infrastructure Engine-II.
Entry number: 25
Owner:
Tag:
Type of operation to perform: echo
Target address/Source address: 10.255.32.25/10.255.32.1
Type Of Service parameter: 0x0
Request size (ARR data portion): 28
Operation timeout (milliseconds): 2000
Verify data: No
Vrf Name: Corp
Schedule:
Operation frequency (seconds): 10
Next Scheduled Start Time: Start Time already passed
Group Scheduled : FALSE
Randomly Scheduled : FALSE
Life (seconds): Forever
Entry Ageout (seconds): never
Recurring (Starting Everyday): FALSE
Status of entry (SNMP RowStatus): Active
Threshold (milliseconds): 5000
Distribution Statistics:
Number of statistic hours kept: 2
Number of statistic distribution buckets kept: 1
Statistic distribution interval (milliseconds): 20
History Statistics:
Number of history Lives kept: 0
Number of history Buckets kept: 15
History Filter Type: None
Enhanced History:
-RTR01#ping vrf Corp 10.255.32.25 source 10.255.32.1
IF YOU PING THE DEVICE MANUALLY, ALL SEEMS OK
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.255.32.25, timeout is 2 seconds:
Packet sent with a source address of 10.255.32.1
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 55/56/57 ms
HEX-SBT-RTR01#
08-14-2014 12:20 AM
Have you scheduled it using:
"ip sla schedule 25 start-time now life forever"
BR,
Dragan
08-14-2014 05:41 AM
Hi Dragan,
Yes its been scheduled as you state, but always shows
RTR01#sh ip sla statistics 25
Round Trip Time (RTT) for Index 25
Latest RTT: NoConnection/Busy/Timeout
Latest operation start time: .14:51:44.215 BST Wed Aug 13 2014
Latest operation return code: Timeout
Number of successes: 0
Number of failures: 28
Operation time to live: Forever
08-14-2014 05:48 AM
This:
Schedule:
Operation frequency (seconds): 10
Next Scheduled Start Time: Start Time already passed
Group Scheduled : FALSE
Randomly Scheduled : FALSE
says that it isn't scheduled I think. BTW your count number is not moving from 28???
Check again scheduler please...
BR,
Dragan
08-14-2014 05:52 AM
Hi Dragan,
It is scheduled, i am sure, you would not get success/failure count otherwise
-RTR01#sh ip sla stat 25
Round Trip Time (RTT) for Index 25
Latest RTT: NoConnection/Busy/Timeout
Latest operation start time: .13:41:10.340 BST Thu Aug 14 2014
Latest operation return code: Timeout
Number of successes: 0
Number of failures: 325
Operation time to live: Forever
08-14-2014 06:20 AM
Sorry for requesting that - I just wanted to be sure :)
Well - can you increase timeout value to 5000 or 10000 maybe?
This should work definitely...
BR,
Dragan
08-14-2014 06:25 AM
i have tried various values for freq/timeout/thresh including 5000ms
non of these work as the RTT is 60ms, so these would not come into play
08-14-2014 06:27 AM
Can we see something from debug:
debug ip sla error/event/trace ?
BR,
Dragan
08-14-2014 06:32 AM
RTR01#sh debug
IP SLAs:
TRACE debugging is on for entries:
25
ERROR debugging is on for entries:
25
359097: .Aug 14 14:21:22.291 BST: IP SLAs (25) echo operation: Timeout
359098: .Aug 14 14:21:22.291 BST: IP SLAs (25) Scheduler: Updating result
359099: .Aug 14 14:21:30.291 BST: IP SLAs (25) Scheduler: saaSchedulerEventWakeup
359100: .Aug 14 14:21:30.291 BST: IP SLAs (25) Scheduler: Starting an operation
359101: .Aug 14 14:21:30.291 BST: IP SLAs (25) echo operation: Sending an echo operation
359102: .Aug 14 14:21:30.291 BST: IP SLAs (25) echo operation: VRF: Corp lookup table id: 2
359103: .Aug 14 14:21:32.291 BST: IP SLAs (25) echo operation: Timeout
359104: .Aug 14 14:21:32.291 BST: IP SLAs (25) Scheduler: Updating result
359105: .Aug 14 14:21:40.291 BST: IP SLAs (25) Scheduler: saaSchedulerEventWakeup
359106: .Aug 14 14:21:40.291 BST: IP SLAs (25) Scheduler: Starting an operation
359107: .Aug 14 14:21:40.291 BST: IP SLAs (25) echo operation: Sending an echo operation
359108: .Aug 14 14:21:40.291 BST: IP SLAs (25) echo operation: VRF: Corp lookup table id: 2
359109: .Aug 14 14:21:42.291 BST: IP SLAs (25) echo operation: Timeout
359110: .Aug 14 14:21:42.291 BST: IP SLAs (25) Scheduler: Updating result
359111: .Aug 14 14:21:50.291 BST: IP SLAs (25) Scheduler: saaSchedulerEventWakeup
359112: .Aug 14 14:21:50.291 BST: IP SLAs (25) Scheduler: Starting an operation
359113: .Aug 14 14:21:50.291 BST: IP SLAs (25) echo operation: Sending an echo operation
359114: .Aug 14 14:21:50.291 BST: IP SLAs (25) echo operation: VRF: Corp lookup table id: 2
359115: .Aug 14 14:21:52.291 BST: IP SLAs (25) echo operation: Timeout
359116: .Aug 14 14:21:52.291 BST: IP SLAs (25) Scheduler: Updating result
359117: .Aug 14 14:22:00.291 BST: IP SLAs (25) Scheduler: saaSchedulerEventWakeup
359118: .Aug 14 14:22:00.291 BST: IP SLAs (25) Scheduler: Starting an operation
359119: .Aug 14 14:22:00.291 BST: IP SLAs (25) echo operation: Sending an echo operation
359120: .Aug 14 14:22:00.291 BST: IP SLAs (25) echo operation: VRF: Corp lookup table id: 2
359121: .Aug 14 14:22:02.291 BST: IP SLAs (25) echo operation: Timeout
359122: .Aug 14 14:22:02.291 BST: IP SLAs (25) Scheduler: Updating result
359123: .Aug 14 14:22:10.289 BST: IP SLAs (25) Scheduler: saaSchedulerEventWakeup
359124: .Aug 14 14:22:10.290 BST: IP SLAs (25) Scheduler: Starting an operation
359125: .Aug 14 14:22:10.290 BST: IP SLAs (25) echo operation: Sending an echo operation
359126: .Aug 14 14:22:10.290 BST: IP SLAs (25) echo operation: VRF: Corp lookup table id: 2
359127: .Aug 14 14:22:12.289 BST: IP SLAs (25) echo operation: Timeout
359128: .Aug 14 14:22:12.290 BST: IP SLAs (25) Scheduler: Updating result
359129: .Aug 14 14:22:20.289 BST: IP SLAs (25) Scheduler: saaSchedulerEventWakeup
359130: .Aug 14 14:22:20.290 BST: IP SLAs (25) Scheduler: Starting an operation
359131: .Aug 14 14:22:20.290 BST: IP SLAs (25) echo operation: Sending an echo operation
359132: .Aug 14 14:22:20.290 BST: IP SLAs (25) echo operation: VRF: Corp lookup table id: 2
359133: .Aug 14 14:22:22.289 BST: IP SLAs (25) echo operation: Timeout
359134: .Aug 14 14:22:22.290 BST: IP SLAs (25) Scheduler: Updating result
359135: .Aug 14 14:22:30.290 BST: IP SLAs (25) Scheduler: saaSchedulerEventWakeup
359136: .Aug 14 14:22:30.290 BST: IP SLAs (25) Scheduler: Starting an operation
359137: .Aug 14 14:22:30.290 BST: IP SLAs (25) echo operation: Sending an echo operation
359138: .Aug 14 14:22:30.290 BST: IP SLAs (25) echo operation: VRF: Corp lookup table id: 2
08-14-2014 06:40 AM
What is your IOS version?
BR,
Dragan
08-14-2014 07:20 AM
cisco ASR1002 (2RU) processor with 731313K/6147K bytes of memory.
/asr1000rp1-adventerprisek9.02.04.02.122-33.XND2.bin
08-14-2014 07:37 AM
I think you should upgrade IOS-XE for this to work...
I checked feature navigator quickly and I think you need higher version for this to work...one thing is concerning me also and that is your SLA engine - it's Infrastructure engine II...I think it should be version 3 and you will get that with newer IOS.
HTH,
Dragan
08-14-2014 07:45 AM
We have IP SLA's currently already running on that router including in the Corp VRF.
08-14-2014 07:47 AM
And it's "icmp echo" type?
If it's the same then I can say that I'm out of ideas :)
BR,
Dragan
08-14-2014 08:16 AM
Yes, its a funny issue
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide