Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.


Troubleshooting sluggish web browsing issue with IP SLA

IP SLA is the first thing to come to mind for identifying the trouble point(s) in the LAN space when experiencing sluggish response browsing an external website. I assume a basic "http get" is ok for simulating the web browsing, but what is the best option with IP SLA for identifying where the trouble spot is within the LAN space? Would that be the ICMP Path Echo Operation? If I use a third-party tool that measures web site response, would it be possible to kick off ICMP Path Echo Operation on-demand only when there's an identified slow response by that other tool? Is issuing snmpset to the IP SLA router(s) the only means of doing that?

Is CiscoWorks IPM a frontend performing the same steps in the background as outlined in these examples? Is it performing these configs on the routers only with snmpsets? Is it possible to trigger another IP SLA operation upon the "http get" operation hitting a certain response, via IPM or on the router directly, without the benefit of facilities such as EEM?

Cisco Employee

Re: Troubleshooting sluggish web browsing issue with IP SLA

This post re-appeared high up in the list, but I thought you said you figured it out. If this is not longer an issue, please mark this as resvoled, so the forum doesn't keep trying to escalate it.


Re: Troubleshooting sluggish web browsing issue with IP SLA

The forum software must have a bug or something. I think I've seen this behavior before.

The question is still open.

Cisco Employee

Re: Troubleshooting sluggish web browsing issue with IP SLA

The IP SLA HTTP operation is actually pretty robust. Yes, it does a simple HTTP GET by default, but what it does behind the scenes in terms of measurement will show you where your low-hanging fruit lies.

The HTTP operation will break down into three components: resolution of the hostname in the URL, time taken to establish the TCP connection, and time take to download the page. Based on this, you can descide where to focus your optimization or troubleshooting efforts.

If you want to isolate where in the network a slow-down is occurring, consider using the Path Echo operation. While it doesn't use TCP probes like the HTTP operation, it will show you a hop-by-hop picture of the IP latency in your network. It can also give you rough idea of where slow-downs are occurring.

Yes, IPM is a frontend for configuring an monitoring IP SLA Collectors (a Collector is an IP SLA source device, target, and operation). IPM uses SNMP to configure and monitor all of its Collectors, and can even be told to put the Collector config in the device's running configuration.

While IP SLA allows you to trigger another operation on a threshold violation, IPM does not support configuring this currently.