cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Join Customer Connection to register!
323
Views
5
Helpful
11
Replies
Hamidsattarrana
Beginner

IP SLA Issue

Hi All!

I am having this issue. When I reconfigure this SLA it works fine. But after 1 day or sometime 2 or more days it did not work. Even I am able to ping 178.35.8.163 from source IP 198.59.65.65. What is the issue?

 

Configurations are follow:

ip sla 2
icmp-echo 178.35.8.163 source-ip 198.59.65.65
timeout 1000
threshold 170
frequency 3

 

 

show ip sla configuration 2
IP SLAs, Infrastructure Engine-II.
Entry number: 2
Owner:
Tag:
Type of operation to perform: icmp-echo
Target address/Source address: 178.35.8.163/198.59.65.65
Type Of Service parameter: 0x0
Request size (ARR data portion): 28
Operation timeout (milliseconds): 1000
Verify data: No
Vrf Name:
Schedule:
Operation frequency (seconds): 3 (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): 170 (not considered if react RTT is configured)
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:

11 REPLIES 11
Giuseppe Larosa
Hall of Fame Master

Hello @Hamidsattarrana ,

can you post a

show version

to understand router / switch model and IOS / IOS XE version.

 

At first sight your configuration looks like correct and the IP SLA is scheduled for running forever.

 

Hope to help

Giuseppe

 

 

Hi!

Please see the below output.

 

show version
Cisco IOS Software, 3800 Software (C3845-ADVENTERPRISEK9-M), Version 12.4(24)T6, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Tue 23-Aug-11 03:38 by prod_rel_team

ROM: System Bootstrap, Version 12.4(13r)T15, RELEASE SOFTWARE (fc1)

Core-Router uptime is 5 weeks, 2 days, 2 hours, 27 minutes
System returned to ROM by power-on
System restarted at 14:26:19 UTC Sun Jan 31 2021
System image file is "flash:c3845-adventerprisek9-mz.124-24.T6.bin"


This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

Cisco 3845 (revision 1.0) with 222208K/39936K bytes of memory.
Processor board ID FCZ144622PP
2 Gigabit Ethernet interfaces
1 Virtual Private Network (VPN) Module
DRAM configuration is 64 bits wide with parity enabled.
479K bytes of NVRAM.
126976K bytes of ATA System CompactFlash (Read/Write)

Configuration register is 0x2102

Georg Pauwen
VIP Expert

Hello,

 

do you have a static route configured for the SLA target ?

 

ip route 178.35.8.163 255.255.255.255 interface/ip_address

Yes I have static route configured.

Hello,

 

you are (obviously) running a very old IOS image on a router that has been end of life for 10 years. That alone could explain your issue. Do you have the 'debug ip sla error 2' command available ? If so, run that and check if anything is logged.

The debug IP Sla error 2 does not show any output. Please check the Debug IP SLA trace 2 Output:

 

Mar 9 2021 12:42:02.993 UTC: IP SLAs(2) Scheduler: saaSchedulerEventWakeup
Mar 9 2021 12:42:02.993 UTC: IP SLAs(2) Scheduler: Starting an operation
Mar 9 2021 12:42:02.993 UTC: IP SLAs(2) echo operation: source IP:198.59.65.65
Mar 9 2021 12:42:02.993 UTC: IP SLAs(2) echo operation: Sending an echo operation - destAddr=178.35.8.163, sAddr=198.59.65.65
Mar 9 2021 12:42:02.993 UTC: IP SLAs(2) echo operation: Sending ID: 2
Mar 9 2021 12:42:03.993 UTC: IP SLAs(2) echo operation: Timeout - destAddr=178.35.8.163, sAddr=198.59.65.65
Mar 9 2021 12:42:03.993 UTC: IP SLAs(2) Scheduler: Updating result
Mar 9 2021 12:42:03.993 UTC: IP SLAs(2) Scheduler: start wakeup timer, delay = 2000

Your Ping is success ?
then we can use the ping RTT to config your ICMP-Echo IP Sla.
timeout>threshold "RTT"

this way we can use IP Sla and also be sure that your WAN not effect it. 

Yes ping is working. If I delete that SLA entry and reconfigured it it works fine. But after sometime request timed out even I am able to ping.

use the RTT from success ping to config the Ip Sla

friend can we see the static route you config and use for IP SLA?

ip route 178.35.8.163 255.255.255.255 198.59.65.66 (Next Hop Address)