Configuring HTTP Operations
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Contents
Configuring IP SLAs HTTP OperationsLast Updated: March 22, 2011
This module describes how to configure an IP Service Level Agreements (SLAs) HTTP operation to monitor the response time between a Cisco device and an HTTP server to retrieve a web page. The IP SLAs HTTP operation supports both the normal GET requests and customer RAW requests. This module also demonstrates how the results of the HTTP operation can be displayed and analyzed to determine how an HTTP server is performing. Finding Feature InformationYour software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required. Restrictions for IP SLAs HTTP Operations
Information About IP SLAs HTTP OperationsHTTP OperationThe HTTP operation measures the round-trip time (RTT) between a Cisco device and an HTTP server to retrieve a web page. The HTTP server response time measurements consist of three types:
The DNS operation is performed first and the DNS RTT is measured. Once the domain name is found, a TCP Connect operation to the appropriate HTTP server is performed and the RTT for this operation is measured. The final operation is an HTTP request and the RTT to retrieve the home HTML page from the HTTP server is measured. One other measurement is made and called the time to first byte which measures the time from the start of the TCP Connect operation to the first HTML byte retrieved by the HTTP operation. The total HTTP RTT is a sum of the DNS RTT, the TCP Connect RTT, and the HTTP RTT. For GET requests, IP SLAs will format the request based on the specified URL. For RAW requests, IP SLAs requires the entire content of the HTTP request. When a RAW request is configured, the raw commands are specified in HTTP RAW configuration mode. A RAW request is flexible and allows you to control fields such as authentication. An HTTP request can be made through a proxy server. The results of an HTTP operation can be useful in monitoring your web server performance levels by determining the RTT taken to retrieve a web page. How to Configure IP SLAs HTTP Operations
Configuring an HTTP GET Operation on the Source Device
Perform only one of the following tasks:
Configuring a Basic HTTP GET Operation on the Source DeviceSUMMARY STEPS
DETAILED STEPS
Configuring an HTTP GET Operation with Optional Parameters on the Source DeviceSUMMARY STEPS
DETAILED STEPS
Configuring an HTTP RAW Operation on the Source Device
SUMMARY STEPS
DETAILED STEPS Scheduling IP SLAs Operations
DETAILED STEPS Troubleshooting Tips
What to Do NextTo add proactive threshold conditions and reactive triggering for generating traps, or for starting another operation, to an IP SLAs operation, see the "Configuring Proactive Threshold Monitoring" section. To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. Configuration Examples for IP SLAs HTTP Operations
Example Configuring an HTTP GET OperationExample Configuring an HTTP RAW OperationThe following example shows how to configure an HTTP RAW operation. To use the RAW commands, enter HTTP RAW configuration mode by using the http-raw-request command in IP SLA configuration mode. The IP SLA HTTP RAW configuration mode is indicated by the (config-ip-sla-http) router prompt. ip sla 8 http raw url http://198.133.219.25 http-raw-request GET /en/US/hmpgs/index.html HTTP/1.0\r\n \r\n end ip sla schedule 8 life forever start-time now Example Configuring an HTTP RAW Operation Through a Proxy ServerThe following example shows how to configure an HTTP RAW operation through a proxy server. The proxy server is www.proxy.cisco.com and the HTTP server is www.yahoo.com. ip sla 8 http raw url http://www.proxy.cisco.com http-raw-request GET http://www.yahoo.com HTTP/1.0\r\n \r\n end ip sla schedule 8 life forever start-time now Additional ReferencesRelated DocumentsMIBsTechnical Assistance
Feature Information for IP SLAs HTTP OperationsThe following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R) Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||