Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
Step-by-Step Configuration and Troubleshooting Best Practices for the NGFW, NGIPS and AMP Technologies A Visual Guide to the Cisco Firepower Threat Defense (FTD)
Community Member

IP SLA Detail Question on ASA 9.0


I have an ASA 5525 connected to an ISP. I've configured a static default route, and tracking the ISP gateway with IP SLA, and using the IP SLA default tracking metrics:

route outside 1 track 1

sla monitor 1

type echo protocol ipIcmpEcho interface outside

sla monitor schedule 1 life forever start-time now           

track 1 rtr 1 reachability

If I do an 'show ip sla monitor configuration', we get some details:

asa1-5525#  sho sla monitor configuration

SA Agent, Infrastructure Engine-II

Entry number: 1



Type of operation to perform: echo

Target address:

Interface: outside

Number of packets: 1

Request size (ARR data portion): 28

Operation timeout (milliseconds): 5000

Type Of Service parameters: 0x0

Verify data: No

Operation frequency (seconds): 60

Next Scheduled Start Time: Start Time already passed

Group Scheduled : FALSE

Life (seconds): Forever

Entry Ageout (seconds): never

Recurring (Starting Everyday): FALSE

Status of entry (SNMP RowStatus): Active

Enhanced History:

So far, so good. Well... not really. I have several complaints that the default route drops frequently. I've confirmed with the ISP that the circuit is healthy, albeit a bit congested at times. My theory is that the SLA traffic is getting dropped during the times of congestion, resulting in the drop of the defaut route. I've pretty much confirmed this with the 'show track' output:

asa1-5525#  sho track

Track 1

  Response Time Reporter 1 reachability

  Reachability is Up

  281 changes, last change 1d01h

  Latest operation return code: OK

  Latest RTT (millisecs) 1

  Tracked by:


So, let's get back to the IP SLA metrics. If I'm reading the output correctly, I'm sending one ping every 60 seconds. That said, this is my question: does this mean that if I don't receive back that single ping, the route gets dropped?! From a single packet loss? If that's true, that is clearly unacceptable. What I would like to know is how to setup IP SLA where I 'send 3 pings over 30 seconds, and if I get back an echo response from at least one of those pings, I keep the default route active.' Is there a way to configure this?


Everyone's tags (3)
Super Bronze

IP SLA Detail Question on ASA 9.0


I have personally only used IP SLA on Routers and on the ASA only for testing purposes here on the CSC so I have not really had to do that much modification in the settings

You might however want to change the "num-packets" setting and perhaps change the "timeout" setting though that by default is already 5000ms

You would be entering these values when  you enter the following command

type echo protocol ipIcmpEcho interface outside

You will be entered into a new configuration mode where you can use the "?" to check your options on what values to use. But the main thing you probably want to test out is change the "num-packets" value to something higher than the default value of 1

Here is links to Command Reference for the "num-packets" and "timeout" commands



- Jouni

Community Member

IP SLA Detail Question on ASA 9.0

Jouni, thanks for the recommendation. That said, like the documentation, this somewhat avoids directly answering my question. Let me ask this way: if I increased the "num-packets" to 6, how many of those packets need to sucessfully reply in order to maintain the route in the routing table? All of them? One of them? 3 of them? This information, for some reason, seems allusive.

Community Member

Did you ever solve this issue

Did you ever solve this issue? I have similar problems with my ASA and my ISP.

Community Member

I have yet to get a specific

I have yet to get a specific answer.

CreatePlease to create content