cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
687
Views
0
Helpful
1
Replies

ip sla isn't work properly

unfraget
Level 1
Level 1

hi everybody!

I've two cisco router
one 2901 with Version 15.2(4)M1
another 1841 Version 15.1(4)M

1841 send probe to 2901 by icmp echo operations, sometime ip sla it stops working, from output sh ip sla statistics i see that operations is timeout

IPSLA operation id: 3826 
        Latest RTT: NoConnection/Busy/Timeout
Latest operation start time: 17:06:50 MSK Wed Oct 2 2019
Latest operation return code: Timeout
Number of successes: 0
Number of failures: 10
Operation time to live: Forever

sla configuration

IP SLAs Infrastructure Engine-III
Entry number: 3826
Owner:
Tag: Client
Operation timeout (milliseconds): 5000
Type of operation to perform: icmp-echo
Target address/Source address: 1.1.1.1/2.2.2.2
Type Of Service parameter: 0x0
Request size (ARR data portion): 28
Verify data: No
Vrf Name:
Schedule:
   Operation frequency (seconds): 180  (not considered if randomly scheduled)
   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): 2500
Distribution Statistics:
   Number of statistic hours kept: 2
   Number of statistic distribution buckets kept: 1
   Statistic distribution interval (milliseconds): 20
Enhanced History:
History Statistics:
   Number of history Lives kept: 0
   Number of history Buckets kept: 15
   History Filter Type: None

ip sla 3826
 icmp-echo 1.1.1.1 source-ip 2.2.2.2
 tag Client
 frequency 180
 threshold 2500
ip sla schedule 3826 life forever start-time now

Oct  2 17:00:50: IPSLA-INFRA_TRACE:OPER:3826 slaSchedulerEventWakeup
Oct  2 17:00:50: IPSLA-INFRA_TRACE:OPER:3826 Starting an operation
Oct  2 17:00:50: IPSLA-OPER_TRACE:OPER:3826 source IP:2.2.2.2
Oct  2 17:00:50: IPSLA-OPER_TRACE:OPER:3826 Starting icmpecho operation - destAddr=1.1.1.1, sAddr=2.2.2.2
Oct  2 17:00:50: IPSLA-OPER_TRACE:OPER:3826 Sending ID: 27781
Oct  2 17:00:55: IPSLA-OPER_TRACE:OPER:3826 Timeout - destAddr=1.1.1.1, sAddr=2.2.2.2
Oct  2 17:00:55: IPSLA-INFRA_TRACE:OPER:3826 Updating result
Oct  2 17:03:50: IPSLA-INFRA_TRACE:OPER:3826 slaSchedulerEventWakeup
Oct  2 17:03:50: IPSLA-INFRA_TRACE:OPER:3826 Starting an operation
Oct  2 17:03:50: IPSLA-OPER_TRACE:OPER:3826 source IP:2.2.2.2
Oct  2 17:03:50: IPSLA-OPER_TRACE:OPER:3826 Starting icmpecho operation - destAddr=1.1.1.1, sAddr=2.2.2.2
Oct  2 17:03:50: IPSLA-OPER_TRACE:OPER:3826 Sending ID: 28023


however if i do ping command
ping 1.1.1.1 source 2.2.2.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:
Packet sent with a source address of 2.2.2.2
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 116/118/120 ms
ping is successful.

my questions what happened with SKA probe?

if i recreate test, test start workingip sla isn't work properly

1 Reply 1

Hello,

 

try and lower the frequency of your SLA:

 

ip sla 3826
icmp-echo 1.1.1.1 source-ip 2.2.2.2
tag Client
frequency 5
threshold 300
ip sla schedule 3826 life forever start-time now

!

track 1 ip sla 3826 reachability