Cisco IOS IP SLAs Configuration Guide

Release 12.4T

Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. All other trademarks mentioned in this document or Website 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. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Cisco IOS IP SLAs Configuration Guide © 2008 Cisco Systems, Inc. All rights reserved.

About Cisco IOS and Cisco IOS XE Software Documentation
Last updated: August 6, 2008

This document describes the objectives, audience, conventions, and organization used in Cisco IOS and Cisco IOS XE software documentation, collectively referred to in this document as Cisco IOS documentation. Also included are resources for obtaining technical assistance, additional documentation, and other information from Cisco. This document is organized into the following sections:
• • • • •

Documentation Objectives, page i Audience, page i Documentation Conventions, page ii Documentation Organization, page iii Additional Resources and Documentation Feedback, page xi

Documentation Objectives
Cisco IOS documentation describes the tasks and commands available to configure and maintain Cisco networking devices.

Audience
The Cisco IOS documentation set is i ntended for users who configure and maintain Cisco networking devices (such as routers and switches) but who may not be familiar with the configuration and maintenance tasks, the relationship among tasks, or the Cisco IOS commands necessary to perform particular tasks. The Cisco IOS documentation set is also intended for those users experienced with Cisco IOS who need to know about new features, new configuration options, and new software characteristics in the current Cisco IOS release.

i

About Cisco IOS and Cisco IOS XE Software Documentation Documentation Conventions

Documentation Conventions
In Cisco IOS documentation, the term router may be used to refer to various Cisco products; for example, routers, access servers, and switches. These and other networking devices that support Cisco IOS software are shown interchangeably in examples and are used only for illustrative purposes. An example that shows one product does not necessarily mean that other products are not supported. This section includes the following topics:
• • • •

Typographic Conventions, page ii Command Syntax Conventions, page ii Software Conventions, page iii Reader Alert Conventions, page iii

Typographic Conventions
Cisco IOS documentation uses the following typographic conventions: Convention ^ or Ctrl Description Both the ^ symbol and Ctrl represent the Control (Ctrl) key on a keyboard. For example, the key combination ^D or Ctrl-D means that you hold down the Control key while you press the D key. (Keys are indicated in capital letters but are not case sensitive.) A string is a nonquoted set of characters shown in italics. For example, when setting a Simple Network Management Protocol (SNMP) community string to public, do not use quotation marks around the string; otherwise, the string will include the quotation marks.

string

Command Syntax Conventions
Cisco IOS documentation uses the following command syntax conventions: Convention bold italic [x] | [x | y] {x | y} [x {y | z}] Description Bold text indicates commands and keywords that you enter as shown. Italic text indicates arguments for which you supply values. Square brackets enclose an optional keyword or argument. A vertical line, called a pipe, indicates a choice within a set of keywords or arguments. Square brackets enclosing keywords or arguments separated by a pipe indicate an optional choice. Braces enclosing keywords or arguments separated by a pipe indicate a required choice. Braces and a pipe within square brackets indicate a required choice within an optional element.

ii

About Cisco IOS and Cisco IOS XE Software Documentation Documentation Organization

Software Conventions
Cisco IOS uses the following program code conventions: Convention
Courier font Bold Courier font

Description Courier font is used for information that is displayed on a PC or terminal screen. Bold Courier font indicates text that the user must enter. Angle brackets enclose text that is not displayed, such as a password. Angle brackets also are used in contexts in which the italic font style is not supported; for example, ASCII text. An exclamation point at the beginning of a line indicates that the text that follows is a comment, not a line of code. An exclamation point is also displayed by Cisco IOS software for certain processes.

<

>

!

[

]

Square brackets enclose default responses to system prompts.

Reader Alert Conventions
The Cisco IOS documentation set uses the following conventions for reader alerts:

Caution

Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Note

Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual.

Timesaver

Means the described action saves time. You can save time by performing the action described in the paragraph.

Documentation Organization
This section describes the Cisco IOS documentation set, how it is organized, and how to access it on Cisco.com. Included are lists of configuration guides, command references, and supplementary references and resources that make up the documentation set. The following topics are included:
• • •

Cisco IOS Documentation Set, page iv Cisco IOS Documentation on Cisco.com, page iv Configuration Guides, Command References, and Supplementary Resources, page v

iii

About Cisco IOS and Cisco IOS XE Software Documentation Documentation Organization

Cisco IOS Documentation Set
Cisco IOS documentation consists of the following:

Release notes and caveats provide information about platform, technology, and feature support for a release and describe severity 1 (catastrophic), severity 2 (severe), and severity 3 (moderate) defects in released Cisco IOS code. Review release notes before other documents to learn whether or not updates have been made to a feature. Sets of configuration guides and command references organized by technology and published for each standard Cisco IOS release.
– Configuration guides—Compilations of documents that provide informational and

task-oriented descriptions of Cisco IOS features.
– Command references—Compilations of command pages that provide detailed information

about the commands used in the Cisco IOS features and processes that make up the related configuration guides. For each technology, there is a single command reference that covers all Cisco IOS releases and that is updated at each standard release.
• • •

Lists of all the commands in a specific release and all commands that are new, modified, removed, or replaced in the release. Command reference book for debug commands. Command pages are listed in alphabetical order. Reference book for system messages for all Cisco IOS releases.

Cisco IOS Documentation on Cisco.com
The following sections describe the documentation organization and how to access various document types. Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
New Features List

The New Features List for each release provides a list of all features in the release with hyperlinks to the feature guides in which they are documented.
Feature Guides

Cisco IOS features are documented in feature guides. Feature guides describe one feature or a group of related features that are supported on many different software releases and platforms. Your Cisco IOS software release or platform may not support all the features documented in a feature guide. See the Feature Information table at the end of the feature guide for information about which features in that guide are supported in your software release.
Configuration Guides

Configuration guides are provided by technology and release and comprise a set of individual feature guides relevant to the release and technology.

iv

Cisco IOS and Cisco IOS XE software configuration guides and command references. including brief descriptions of the contents of the documents. v .com/web/psa/products/index.com at http://www. The Cisco IOS command references are comprehensive. For additional information about configuring and operating specific networking devices. The configuration guides and command references support many different software releases and platforms.About Cisco IOS and Cisco IOS XE Software Documentation Documentation Organization Command References Command reference books describe Cisco IOS commands that are supported in many different software releases and on many different platforms. Cisco IOS Supplementary Documents and Resources Supplementary documents and resources are listed in Table 2 on page xi. and Supplementary Resources Table 1 lists. system messages. Table 2 lists documents and resources that supplement the Cisco IOS software configuration guides and command references. in alphabetical order. use the Command Lookup Tool at http://tools. and the debug command reference. Configuration Guides. master command lists.cisco.cisco. new. multiprotocol over ATM (MPoA). Your Cisco IOS software release or platform may not support all these technologies.html. meaning that they include commands for both Cisco IOS software and Cisco IOS XE software. The books are provided by technology. These supplementary resources include release notes and caveats. All Releases.html. and WAN ATM. Table 1 Cisco IOS and Cisco IOS XE Configuration Guides and Command References Configuration Guide and Command Reference Titles Cisco IOS AppleTalk Configuration Guide Cisco IOS XE AppleTalk Configuration Guide Cisco IOS AppleTalk Command Reference Cisco IOS Asynchronous Transfer Mode Configuration Guide Cisco IOS Asynchronous Transfer Mode Command Reference Features/Protocols/Technologies AppleTalk protocol. modified. for all releases. For information about all Cisco IOS commands. go to the Product Support area of Cisco. removed. LAN ATM.com/en/US/docs/ios/mcl/all_release/all_mcl.com/Support/CLILookup or the Cisco IOS Master Command List. and replaced command lists.cisco. Command References. at http://www.

About Cisco IOS and Cisco IOS XE Software Documentation Documentation Organization Table 1 Cisco IOS and Cisco IOS XE Configuration Guides and Command References (continued) Configuration Guide and Command Reference Titles Cisco IOS Bridging and IBM Networking Configuration Guide Cisco IOS Bridging Command Reference Cisco IOS IBM Networking Command Reference Features/Protocols/Technologies • Transparent and source-route transparent (SRT) bridging. serial tunnel (STUN). • Cisco IOS Broadband and DSL Configuration Guide Cisco IOS XE Broadband and DSL Configuration Guide Cisco IOS Broadband and DSL Command Reference Cisco IOS Carrier Ethernet Configuration Guide Cisco IOS Carrier Ethernet Command Reference Point-to-Point Protocol (PPP) over ATM (PPPoA) and PPP over Ethernet (PPPoE). and token ring route switch module (TRRSM). type 2 (LLC2). including Synchronous Data Logical Link Control (SDLLC) and qualified LLC (QLLC). Cisco IOS command-line interface (CLI). vi . administration. and operations.3ad link bundling. dial-on-demand routing. dialer technology. Link Layer Discovery Protocol (LLDP). ISDN. SNA frame relay access. Setup. Token Ring Inter-Switch Link (TRISL). Connectivity fault management (CFM). media endpoint discovery (MED). IEEE 802. logical link control. dialout. modem and resource pooling. block serial tunnel (BSTUN). source-route bridging (SRB). dial backup. Asynchronous communications. and IBM Channel Attach. Systems Network Architecture (SNA) service point. Cisco IOS web browser user interface (UI). synchronous data link control (SDLC). basic file transfer services. Cisco IOS file system (IFS). Flexible NetFlow. virtual private dialup network (VPDN). and file management. PPP. IBM Network Media Translation. downstream physical unit (DSPU). large scale dialout. Autoinstall. dial-in terminal services and AppleTalk remote access (ARA). Ethernet Local Management Interface (ELMI). and maintenance (OAM). Data-link switching plus (DLSw+). advanced peer-to-peer networking (APPN). Cisco IOS Configuration Fundamentals Configuration Guide Cisco IOS XE Configuration Fundamentals Configuration Guide Cisco IOS Configuration Fundamentals Command Reference Cisco IOS DECnet Configuration Guide Cisco IOS XE DECnet Configuration Guide Cisco IOS DECnet Command Reference Cisco IOS Dial Technologies Configuration Guide Cisco IOS XE Dial Technologies Configuration Guide Cisco IOS Dial Technologies Command Reference Cisco IOS Flexible NetFlow Configuration Guide Cisco IOS Flexible NetFlow Command Reference DECnet protocol. native client interface architecture (NCIA) client/server topologies. multilink PPP (MLP).

Mobile ad hoc networks (MANet) and Cisco mobile networks. TCP. session life-cycle management.323 dual tone multifrequency relay. Internet Group Management Protocol (IGMP). virtual interfaces. A VoIP-enabled device that is deployed at the edge of networks. Network Address Translation (NAT) support of H. LAN interfaces. Multicast Source Discovery Protocol (MSDP). Source Specific Multicast (SSM). accounting for access and service usage. Domain Name System (DNS). Gateway Load Balancing Protocol (GLBP). gateway codec order preservation and shutdown control. network-level resiliency. Protocol Independent Multicast (PIM) sparse mode (PIM-SM). Admission. serial interfaces. session state monitoring. Network Address Translation (NAT). Server Load Balancing (SLB). Stream Control Transmission Protocol (SCTP). An SBC is a toolkit of functions. service and policy determination. tokenless call authorization. logical interfaces. Hot Standby Router Protocol (HSRP). H. and Virtual Router Redundancy Protocol (VRRP). and Status (RAS) protocol. A variety of High Availability (HA) features and technologies that are available for different network segments (from enterprise access to service provider core) to facilitate creation of end-to-end highly available networks. Subscriber identification. vii .About Cisco IOS and Cisco IOS XE Software Documentation Documentation Organization Table 1 Cisco IOS and Cisco IOS XE Configuration Guides and Command References (continued) Configuration Guide and Command Reference Titles Cisco IOS H. Dynamic Host Configuration Protocol (DHCP). session creation. bidirectional PIM (bidir-PIM). and quality of service (QoS).323 version 2 enhancements. such as signaling interworking.323 v2 Registration. and Multicast VPN (MVPN). Gatekeeper Transaction Message Protocol. network hiding. and embedded management for resiliency. Cisco IOS High Availability Configuration Guide Cisco IOS XE High Availability Configuration Guide Cisco IOS High Availability Command Reference Cisco IOS Integrated Session Border Controller Command Reference Cisco IOS Intelligent Service Gateway Configuration Guide Cisco IOS Intelligent Service Gateway Command Reference Cisco IOS Interface and Hardware Component Configuration Guide Cisco IOS XE Interface and Hardware Component Configuration Guide Cisco IOS Interface and Hardware Component Command Reference Cisco IOS IP Addressing Services Configuration Guide Cisco IOS XE Addressing Services Configuration Guide Cisco IOS IP Addressing Services Command Reference Cisco IOS IP Application Services Configuration Guide Cisco IOS XE IP Application Services Configuration Guide Cisco IOS IP Application Services Command Reference Cisco IOS IP Mobility Configuration Guide Cisco IOS IP Mobility Command Reference Cisco IOS IP Multicast Configuration Guide Cisco IOS XE IP Multicast Configuration Guide Cisco IOS IP Multicast Command Reference Address Resolution Protocol (ARP). IP Services. User Datagram Protocol (UDP). and VoIP gateway trunk and carrier-based routing. Cisco IOS HA features and technologies can be categorized in three key areas: system-level resiliency. H. Web Cache Communication Protocol (WCCP). session policy enforcement. and Next Hop Address Resolution Protocol (NHRP). and interface configuration. Enhanced Object Tracking (EOT).323 Configuration Guide Features/Protocols/Technologies Gatekeeper enhancements for managed voice services. security.

multiprotocol BGP. IEEE 802. Cisco IOS IP SLAs Configuration Guide Cisco IOS XE IP SLAs Configuration Guide Cisco IOS IP SLAs Command Reference Cisco IOS IP Switching Configuration Guide Cisco IOS XE IP Switching Configuration Guide Cisco IOS IP Switching Command Reference Cisco IOS IPv6 Configuration Guide Cisco IOS XE IPv6 Configuration Guide Cisco IOS IPv6 Command Reference Cisco IOS ISO CLNS Configuration Guide Cisco IOS XE ISO CLNS Configuration Guide Cisco IOS ISO CLNS Command Reference Cisco IOS LAN Switching Configuration Guide Cisco IOS XE LAN Switching Configuration Guide Cisco IOS LAN Switching Command Reference Cisco IOS Mobile Wireless Gateway GPRS Support Node Configuration Guide Cisco IOS Mobile Wireless Gateway GPRS Support Node Command Reference Cisco IOS Mobile Wireless Home Agent Configuration Guide Cisco IOS Mobile Wireless Home Agent Command Reference Cisco IOS Mobile Wireless Packet Data Serving Node Configuration Guide Cisco IOS Mobile Wireless Packet Data Serving Node Command Reference Cisco IOS Mobile Wireless Radio Access Networking Configuration Guide Cisco IOS Mobile Wireless Radio Access Networking Command Reference Cisco Express Forwarding. an anchor point for mobile terminals for which mobile IP or proxy mobile IP services are provided.cisco. and technologies. go to the IPv6 “Start Here” document at the following URL: http://www.html ISO connectionless network service (CLNS).About Cisco IOS and Cisco IOS XE Software Documentation Documentation Organization Table 1 Cisco IOS and Cisco IOS XE Configuration Guides and Command References (continued) Configuration Guide and Command Reference Titles Cisco IOS IP Routing Protocols Configuration Guide Cisco IOS XE IP Routing Protocols Configuration Guide Cisco IOS IP Routing Protocols Command Reference Features/Protocols/Technologies Border Gateway Protocol (BGP). Interior Gateway Routing Protocol (IGRP). protocols. Cisco IOS radio access network products. Intermediate System-to-Intermediate System (IS-IS). Cisco IOS IP Service Level Agreements (IP SLAs). For IPv6 features. Cisco Mobile Wireless Home Agent. and Routing Information Protocol (RIP).1Q encapsulation. on-demand routing (ODR). Enhanced Interior Gateway Routing Protocol (EIGRP). a wireless gateway that is between the mobile infrastructure and standard IP networks and that enables packet data services in a code division multiple access (CDMA) environment.10 encapsulation.com/en/US/docs/ios/ipv6/configuration/ guide/ip6-roadmap.5-generation general packet radio service (GPRS) and 3-generation universal mobile telecommunication system (UMTS) network. Inter-Switch Link (ISL) encapsulation. and Multicast Distributed Switching (MDS). multiprotocol BGP extensions for IP multicast. Cisco IOS Gateway GPRS Support Node (GGSN) in a 2. VLANs. Cisco Packet Data Serving Node (PDSN). Open Shortest Path First (OSPF). fast switching. bidirectional forwarding detection (BFD). and multilayer switching (MLS). viii . IEEE 802.

distributed traffic shaping (DTS). Resource Reservation Protocol (RSVP). and accounting (AAA). Security Device Manager (SDM). Embedded Event Manager (EEM). MPLS Layer 3 VPNs. MPLS Layer 2 VPNs. modular QoS CLI (MQC). public key infrastructure (PKI). low latency queuing (LLQ). logging. routing control. HTTP. and MPLS Embedded Management (EM) and MIBs. custom queuing. weighted fair queuing (WFQ). firewalls. header compression. policy configuration. IP security and encryption. troubleshooting. IP. network data encryption with router authentication. authorization. and VPN Device Manager Client for Cisco IOS Software (XSM Configuration). Network-Based Application Recognition (NBAR). aggregation caches. and network management support. DistributedDirector. Network traffic data analysis. Cisco IOS Novell IPX Configuration Guide Cisco IOS XE Novell IPX Configuration Guide Cisco IOS Novell IPX Command Reference Cisco IOS Optimized Edge Routing Configuration Guide Cisco IOS Optimized Edge Routing Command Reference Optimized edge routing (OER) monitoring. Cisco IOS XE Network Management Configuration Guide Cisco Discovery Protocol. Unicast and multicast topology configurations. SNMP. Cisco networking services (CNS). Cisco IOS Quality of Service Solutions Configuration Guide Cisco IOS XE Quality of Service Solutions Configuration Guide Cisco IOS Quality of Service Solutions Command Reference Cisco IOS Security Configuration Guide Cisco IOS XE Security Configuration Guide Cisco IOS Security Command Reference ix . and fault management. logging and reporting. export features. RADIUS.to-ATM class of service (CoS). and traffic filters. network access security. QoS features for voice. TACACS+. priority queuing. Embedded Syslog Manager (ESM). MPLS Traffic Engineering (TE). and weighted random early detection (WRED). Class-based weighted fair queuing (CBWFQ). system monitoring and logging.About Cisco IOS and Cisco IOS XE Software Documentation Documentation Organization Table 1 Cisco IOS and Cisco IOS XE Configuration Guides and Command References (continued) Configuration Guide and Command Reference Titles Cisco IOS Multiprotocol Label Switching Configuration Guide Cisco IOS XE Multiprotocol Label Switching Configuration Guide Cisco IOS Multiprotocol Label Switching Command Reference Cisco IOS Multi-Topology Routing Configuration Guide Cisco IOS Multi-Topology Routing Command Reference Cisco IOS NetFlow Configuration Guide Cisco IOS XE NetFlow Configuration Guide Cisco IOS NetFlow Command Reference Cisco IOS Network Management Configuration Guide Features/Protocols/Technologies MPLS Label Distribution Protocol (LDP). terminal access security. generic traffic shaping (GTS). Access control lists (ACLs). neighbor router authentication. Remote Monitoring (RMON). Novell Internetwork Packet Exchange (IPX) protocol. AutoQoS. Embedded Resource Manager (ERM). traffic classification. Basic system management. and VPN IPsec/generic routing encapsulation (GRE) tunnel interface optimization. authentication. routing protocol support. Multilink PPP (MLPPP) for QoS. Cisco IOS Scripting with Tool Cisco IOS Network Management Command Reference Control Language (Tcl).

virtual switch link (VSL). Layer 2 Tunneling Protocol (L2TP) dial-out load balancing and redundancy. The library includes documentation for IP telephony applications. tunnel authentication via RADIUS on tunnel terminator. Wi-Fi Multimedia (WMM) required elements. L2TP extended failover.25. IEEE 802. Link Access Procedure. Virtual Switch Link Protocol (VSLP). refer to the product-specific software configuration information for the Cisco Catalyst 6500 series switch or for the Metro Ethernet 6500 series switch. Switched Cisco IOS XE Wide-Area Networking Configuration Guide Multimegabit Data Service (SMDS). L2TP security VPDN. and X. Installation and basic configuration of software modularity images. Layer 2 Tunneling Protocol Version 3 (L2TPv3). software modularity processes and patches. DEC. Cisco IOS Wide-Area Networking Configuration Guide Frame Relay. interoperability. x . Multiple Basic Service Set ID (BSSID). converting between standalone and virtual switch modes. IEEE 802. local-area transport (LAT). and troubleshooting. timer and retry enhancements for L2TP and Layer 2 Forwarding (L2F). installation rollbacks. service access.11x support. high availability. Virtual switch redundancy. Cisco IOS Voice Configuration Library Cisco IOS Voice Command Reference Cisco IOS VPDN Configuration Guide Cisco IOS XE VPDN Configuration Guide Cisco IOS VPDN Command Reference Cisco IOS support for voice call control protocols. and packet handling.25 packet assembler/disassembler (PAD). physical and virtual interface management. Note For information about virtual switch configuration. software modularity binding. and Wi-Fi Protected Access (WPA). Balanced (LAPB). shell-based authentication of VPDN users. IEEE 802. including installations on single and dual route processors. Cisco IOS Wide-Area Networking Command Reference Cisco IOS Wireless LAN Configuration Guide Cisco IOS Wireless LAN Command Reference Broadcast key rotation.1x local authentication service for Extensible Authentication Protocol-Flexible Authentication via Secure Tunneling (EAP-FAST). An orchestrated collection of processes and components to activate Cisco IOS software feature sets by obtaining and validating Cisco software licenses. multihop by Dialed Number Identification Service (DNIS).1x authenticator. RADIUS Attribute 82: tunnel assignment ID. and accounting.About Cisco IOS and Cisco IOS XE Software Documentation Documentation Organization Table 1 Cisco IOS and Cisco IOS XE Configuration Guides and Command References (continued) Configuration Guide and Command Reference Titles Cisco IOS Service Selection Gateway Command Reference Cisco IOS Software Activation Configuration Guide Cisco IOS Software Activation Command Reference Cisco IOS Software Modularity Installation and Configuration Guide Cisco IOS Software Modularity Command Reference Cisco IOS Terminal Services Configuration Guide Cisco IOS Terminal Services Command Reference Cisco IOS XE Terminal Services Command Reference Cisco IOS Virtual Switch Command Reference Features/Protocols/Technologies Cisco IOS Service Selection Gateway Configuration Guide Subscriber authentication. and X.

and replaced commands for a Cisco IOS release.About Cisco IOS and Cisco IOS XE Software Documentation Additional Resources and Documentation Feedback Table 2 Cisco IOS Supplementary Documents and Resources Document Title Cisco IOS Master Command List. The full text of referenced RFCs may be obtained at the following URL: http://www. use Cisco MIB Locator at the following URL: http://www. or the system software.com/go/mibs Standards documents maintained by the Internet Engineering Task Force (IETF) that Cisco IOS documentation references where applicable. and Replaced Commands Cisco IOS Software System Messages Description Alphabetical list of all the commands documented in all Cisco IOS releases.org/ Cisco IOS Debug Command Reference Release Notes and Caveats MIBs RFCs Additional Resources and Documentation Feedback What’s New in Cisco Product Documentation is published monthly and describes all new and revised Cisco technical documentation. Your feedback helps us improve our documentation. be informational only. System messages may indicate problems with your system. All Releases Cisco IOS New. Files used for network monitoring. Cisco IOS releases. Alphabetical list of debug commands including brief descriptions of use. To locate and download MIBs for selected platforms. and other useful information about specific software releases. command syntax. Information about new and changed features. List of Cisco IOS system messages and descriptions. and feature sets. List of all the new. and usage guidelines. Modified. internal hardware. xi . The What’s New in Cisco Product Documentation publication also provides information about obtaining the following resources: • • • • Technical documentation Cisco product security overview Product alerts and field notices Technical assistance Cisco IOS technical documentation includes embedded feedback forms where you can rate documents and provide suggestions for improvement. system requirements. modified. removed. information about defects in specific Cisco IOS software releases.rfc-editor. or may help diagnose problems with communications lines. Removed.cisco.

About Cisco IOS and Cisco IOS XE Software Documentation Additional Resources and Documentation Feedback CCDE. Any examples. Inc. Networking Academy. GigaDrive. ProConnect. All other trademarks mentioned in this document or Website are the property of their respective owners. Cisco. SMARTnet. CCIE. CCNP. Cisco Eos. TransPath. PowerPanels. and Learn and Cisco Store are service marks. Cisco Unity. iQ Expertise. CCSP. Cisco Systems Capital. xii . PCNow. LightStream. Bringing the Meeting To You. Collaboration Without Limitation. and/or its affiliates in the United States and certain other countries. MeetingPlace. MGX. Fast Step. Cisco Nexus. CCNA. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Internet Quotient. Live. Cisco Press. CCDP. and Access Registrar. Event Center. iPhone. IronPort. HomeLink. Cisco StadiumVision. Spectrum Expert. CCENT. the Cisco logo. Any use of actual IP addresses in illustrative content is unintentional and coincidental. CCIP. © 2007–2008 Cisco Systems. Network Registrar. The use of the word partner does not imply a partnership relationship between Cisco and any other company. AsyncOS. iQ Net Readiness Scorecard. MeetingPlace Chime Sound. WebEx. the IronPort logo. EtherFast. MediaTone. StackWise. the iQ logo. Aironet. DCE. Cisco Lumin. Cisco Systems. EtherSwitch. PIX. command display output. SenderBase. and Welcome to the Human Network are trademarks. CCVP. the Cisco Systems logo. ScriptShare. iQuick Study. Cisco TelePresence. The Fastest Way to Increase Your Internet Quotient. All rights reserved. FormShare. and the WebEx logo are registered trademarks of Cisco Systems. CCDA. Cisco IOS. Catalyst. IOS. Networkers. Changing the Way We Work. Linksys. Follow Me Browsing. and figures included in the document are shown for illustrative purposes only. the Cisco Certified Internetwork Expert logo. Play. Inc.

such as Security Device Manager. 2008 This document provides basic information about the command-line interface (CLI) in Cisco IOS and Cisco IOS XE software and how you can use some of the CLI features.html.cisco. you can configure the device by using the console port or a remote access method. page xii For more information about using the CLI.Using the Command-Line Interface in Cisco IOS and Cisco IOS XE Software Last updated: August 6. to access the CLI or by using the configuration method provided on the device. such as Telnet or Secure Shell (SSH). Initially Configuring a Device Initially configuring a device varies by platform.com at http://www. For information about the software documentation set. For information about performing an initial configuration. This document contains the following sections: • • • • Initially Configuring a Device.com/web/psa/products/index. page ii Saving Changes to a Configuration. i . After you have performed the initial configuration and connected the device to your network. see the “Using the Cisco IOS Command-Line Interface” section of the Cisco IOS Configuration Fundamentals Configuration Guide. see the hardware installation documentation that is provided with the original packaging of the product or go to the Product Support area of Cisco. page xii Additional Information. page i Using the CLI. see the “About Cisco IOS and Cisco IOS XE Software Documentation” document.

page ix Using Aliases for CLI Commands. access and exit methods. This section describes the most common of the many modes that exist. by adding a password or changing the timeout value. page viii Abbreviating Commands. Changing the port speed is not recommended. page ii Using the Interactive Help Feature. page viii Using the Command History Feature. ii . Table 1 lists common command modes with associated CLI prompts. page x Filtering Output Using Output Modifiers. page xi Understanding Command Modes The CLI command mode structure is hierarchical. page vi Understanding Enable and Enable Secret Passwords. page x Using the debug Command. and a brief description of how each mode is used. page ix Using the no and default Forms of Commands. page x Understanding CLI Error Messages. for example. Change the behavior of the port. Using the CLI This section describes the following topics: • • • • • • • • • • • Understanding Command Modes. Note The AUX port on the Route Processor (RP) installed in a Cisco ASR1000 series router does not serve any useful customer purpose and should be accessed only under the advisement of a customer support representative. page v Understanding Command Syntax.Using the Command-Line Interface in Cisco IOS and Cisco IOS XE Software Using the CLI Changing the Default Settings for a Console or AUX Port There are only two changes that you can make to a console port and an AUX port: • • Change the port speed with the config-register 0x command. and each mode supports a set of specific commands. The well-known default speed is 9600.

• • • • • Global configuration From privileged EXEC mode.Using the Command-Line Interface in Cisco IOS and Cisco IOS XE Software Using the CLI Table 1 CLI Command Modes Command Mode User EXEC Access Method Log in. Perform basic tests. Issue the exit command Configure individual to return to global interfaces. From global configuration mode. issue the configure terminal command. Interface configuration Router(config-if)# Line configuration Router(config-line)# Issue the exit command Configure individual From global to return to global terminal lines. Manage device configuration files. return to privileged EXEC mode. Router# Issue the disable command or the exit command to return to user EXEC mode. or the end command to return to privileged EXEC mode. iii . Display device status. Manage device file systems. Prompt Router> Exit Method Issue the logout or exit command. configuration mode. issue the interface command. configuration mode or issue the line vty or line the end command to console command. Router(config)# Issue the exit command Configure the device. Reload the device. configuration mode or the end command to return to privileged EXEC mode. Mode Usage • • • Change terminal settings. Issue show and debug commands. issue the enable command. Privileged EXEC From user EXEC mode. Copy images to the device.

or the send break command) was entered. an ESP. issue the reload command. Prompt rommon # > Exit Method Issue the continue command. Ctrl-Shift-6. Reboot hardware. access the router through another port or using a method that is configured to connect to the Cisco IOS CLI. If the RP auxiliary port was used to access the router. • • • • A user-configured access policy was configured using the transport-map command. an RP. which directed the user into diagnostic mode. including the Cisco IOS state. Accessing the router through the auxiliary port is not useful for customer purposes. Mode Usage • The # symbol represents the line number and increments at each prompt. or possibly other hardware components.Using the Command-Line Interface in Cisco IOS and Cisco IOS XE Software Using the CLI Table 1 CLI Command Modes (continued) Command Mode ROM monitor Access Method From privileged EXEC mode. Replace or roll back the configuration. Press the Break key during the first 60 seconds while the system is booting. a SPA. • • Diagnostic (available only on the Cisco ASR1000 series router) Router(diag)# The router boots or enters diagnostic mode in the following scenarios. TFTP. Inspect various states on the router. If the router is in diagnostic mode because of a transport-map configuration. in most scenarios the router will reload. Access the fall-back procedure for loading an image when the device lacks a valid image and cannot be booted. such as the entire router. Perform password recovery when a CTRL-Break sequence is issued within 60 seconds of a power-on or reload event. a SIP. Transfer files into or off of the router using remote access methods such as FTP. and SCP. When a Cisco IOS process or processes fail. • • • • iv . use another port for access. the failure must be resolved and the router must be rebooted to exit diagnostic mode. If a Cisco IOS process failure is the reason for entering diagnostic mode. A break signal (Ctrl-C. Provide methods of restarting the Cisco IOS software or other processes. and the router was configured to enter diagnostic mode when the break signal was received. The router was accessed using an RP auxiliary port. Run as the default operating mode when a valid image cannot be loaded.

rommon 2 > set and display aliases command boot up an external process configuration register utility continue executing a downloaded image display the context of a loaded image display contents of cookie PROM in hex The following example shows how the command prompt changes to indicate a different command mode: Router> enable Router# configure terminal Router(config)# interface ethernet 1/1 Router(config-if)# ethernet Router(config-line)# exit Router(config)# end Router# Note A keyboard alternative to the end command is Ctrl-Z. Using the Interactive Help Feature The CLI includes an interactive Help feature. Provides a list of commands that begin with the character string (no space between the command and the question mark). or both associated with the command (space between the command and the question mark). . Global configuration mode is the highest level of configuration mode. Table 2 CLI Interactive Help Commands Command help ? partial command? partial command<Tab> command ? command keyword ? Purpose Provides a brief description of the help feature in any command mode. you can enter a variety of other configuration modes. If you save the running configuration to the startup configuration. these commands will execute when the software is rebooted. ROM monitor mode is a separate mode that is used when the software cannot load properly. Lists all commands available for a particular command mode.Using the Command-Line Interface in Cisco IOS and Cisco IOS XE Software Using the CLI EXEC commands are not saved when the software reboots. . Commands that you issue in a configuration mode can be saved to the startup configuration. Use the question symbol (?) to view the commands that you can use while the device is in ROM monitor mode. v . Completes a partial command name (no space between the command and <Tab>). From global configuration mode. Lists the keywords. the software might enter ROM monitor mode. Lists the arguments that are associated with the keyword (space between the keyword and the question mark). If a valid software image is not found when the software boots or if the configuration file is corrupted at startup. arguments. including protocol-specific modes. Table 2 describes how to use the Help feature. rommon 1 > ? alias boot confreg cont context cookie .

Partial help is provided when an abbreviated argument is entered and you want to know what arguments match the input (e. and arguments.g. vi . Keywords and arguments may be required or optional.) ? Router# ? Exec commands: access-enable access-profile access-template alps archive <snip> Create a temporary access-List entry Apply user-profile to interface Create a temporary access-List entry ALPS exec commands manage archive files partial command? Router(config)# zo? zone zone-pair partial command<Tab> Router(config)# we<Tab> webvpn command ? Router(config-if)# pppoe ? enable Enable pppoe max-sessions Maximum PPPOE sessions command keyword ? Router(config-if)# pppoe enable ? group attach a BBA group <cr> Understanding Command Syntax Command syntax is the format in which a command should be entered in the CLI. If nothing matches. keywords. Table 3 describes these conventions. Arguments are placeholders for values that a user must supply. Commands include the name of the command. Full help is available when you are ready to enter a command argument (e. Specific conventions convey information about syntax and command elements. the help list will be empty and you must backup until entering a '?' shows the available options. Two styles of help are provided: 1. 'show ?') and describes each possible argument. 'show pr?'. 2. Keywords are alphanumeric strings that are used literally.g.Using the Command-Line Interface in Cisco IOS and Cisco IOS XE Software Using the CLI The following examples show how to use the help commands: help Router> help Help may be requested at any point in a command by entering a question mark '?'.

Angle brackets (< >) are not always used to indicate that a LINE is an argument.C. you have reached the end of the branch or the end of the command if the command has only one branch. The following examples show syntax conventions: Router(config)# ethernet cfm domain ? WORD domain name Router(config)# ethernet cfm domain dname ? level Router(config)# ethernet cfm domain dname level ? <0-7> maintenance level number Router(config)# ethernet cfm domain dname level 7 ? <cr> Router(config)# snmp-server file-transfer access-group 10 ? protocol protocol options <cr> Router(config)# logging host ? Hostname or A. Angle brackets (< >) are not always used to indicate that a WORD is an argument. Notes Sometimes arguments are displayed without angle brackets. Indicates that you must enter more than one word.B. Indicates that you must enter one word.D IP address of the syslog server ipv6 Configure IPv6 syslog server Router(config)# snmp-server file-transfer access-group 10 ? protocol protocol options <cr> vii . and also indicates when keywords and arguments are optional.B. WORD (all capital letters) LINE (all capital letters) <cr> (carriage return) Indicates the end of the list of — available keywords and arguments.D. When <cr> is the only option. Angle brackets (< >) are not always used to indicate that an IP address is an argument. Indicates that you must enter a dotted decimal IP address.Using the Command-Line Interface in Cisco IOS and Cisco IOS XE Software Using the CLI Table 3 CLI Syntax Conventions Symbol/Text < > (angle brackets) A.C. Function Indicate that the option is an argument.

issue the history command: Router(config-line)# history [size num] To recall commands from the history buffer. use the following methods: • Press Ctrl-P or the up arrow key—Recalls commands beginning with the most recent command. enable (not encrypted) and enable secret (encrypted).text file. and it is recommended that you set a password for these commands to prevent unauthorized use. When you use an enable secret password. When you use an enable password. for example. To change the number of commands saved in the history buffer for a terminal session. Leading spaces are ignored. To remove a password. Note Both password commands have numeric keywords that are single integer values. but the number is configurable within the range of 0 to 256. Repeat the key sequence to recall successively older commands. Each type of password is case sensitive.shtml. To set the command history buffer size for a terminal session in line configuration mode. The following commands set these passwords and are issued in global configuration mode: • • enable password enable secret password Using an enable secret password is recommended because it is encrypted and more secure than the enable password. text is encrypted (unreadable) before it is written to the config. the text is written as entered (readable) to the config. “two words” is a valid password. see http://www. If you choose a number for the first character of your password followed by a space. Spaces are also valid password characters. can contain from 1 to 25 uppercase and lowercase alphanumeric characters. Two types of passwords. For more information about password recovery procedures for Cisco products. This command history feature is particularly useful for recalling long or complex commands. can be set.cisco. viii .com/en/US/products/sw/iosswrel/ps1831/ products_tech_note09186a00801746e6. use the no form of the commands: no enable password or no enable secret password. issue the terminal history size command: Router# terminal history size num A command history buffer is also available in line configuration mode with the same default and configuration options. the enable secret password takes precedence over the enable password.Using the Command-Line Interface in Cisco IOS and Cisco IOS XE Software Using the CLI Understanding Enable and Enable Secret Passwords Some privileged EXEC commands are used for actions that impact the system. and can start with a number. the system will read the number as if it were the numeric keyword and not as part of your password. Using the Command History Feature The CLI command history feature saves the commands you enter during a session in a command history buffer. but trailing spaces are recognized.text file. The default number of commands saved is 10. When both passwords are set.

Following are some examples: • • • Router(config)# alias exec prt partition—privileged EXEC mode Router(config)# alias configure sb source-bridge—global configuration mode Router(config)# alias interface rl rate-limit—interface configuration mode ix . Table 4 Default Command Aliases Command Alias h lo p s u or un w Original Command help logout ping show undebug where To create a command alias. For example.Using the Command-Line Interface in Cisco IOS and Cisco IOS XE Software Using the CLI • Press Ctrl-N or the down arrow key—Recalls the most recent commands in the history buffer after they have been recalled using Ctrl-P or the up arrow key. Note • The arrow keys function only on ANSI-compatible terminals such as the VT100. The CLI recognizes an abbreviated command when the abbreviation contains enough characters to uniquely identify the command. Table 4 shows the default command aliases. set. issue the terminal no history command in user EXEC or privileged EXEC mode or the no history command in line configuration mode. The CLI command history feature is enabled by default. Repeat the key sequence to recall successively more recent commands. but an alias cannot move between modes. Issue the show history command in user EXEC or privileged EXEC mode—Lists the most recent commands that you entered. An alias can be configured to do anything that can be done at the command line. issue the alias command in global configuration mode. the show version command can be abbreviated as sh ver. The syntax of the command is alias mode command-alias original-command. or perform any interactive functions.4(13)T. The number of commands that are displayed is determined by the setting of the terminal history size and history commands. It cannot be abbreviated as s ver because s could mean show. type in passwords. you can use a command alias. or systat.) Using Aliases for CLI Commands To save time and the repetition of entering the same command multiple times. (Command and keyword examples from Cisco IOS Release 12. To disable this feature for a terminal session. Abbreviating Commands Typing a complete command name is not always required for the command to execute. The sh v abbreviation also is not valid because the show command has vrrp as a keyword in addition to version.

Use debug commands only to troubleshoot specific problems. Using the no and default Forms of Commands Most configuration commands have a no form that is used to reset a command to its default value or disable a feature or function.html. which returns the command settings to their default values. To re-enable IP routing. see http://www.cisco. For more information about debug commands. For more information about the alias command. To use debug commands during a Telnet session with a device. debug aaa accounting. you can filter this output to show only the information that you want to see. Filtering Output Using Output Modifiers Many commands produce lengthy output that may use several screens to display.Using the Command-Line Interface in Cisco IOS and Cisco IOS XE Software Using the CLI To view both default and user-created aliases. x .html. To disable this command. the default form enables the command and returns the settings to their default values. For commands that are disabled by default. Debugging during these periods decreases the likelihood that the debug command processing overhead will affect network performance or user access or response times. Configuration commands may also have a default form. These commands are available for many features and functions within Cisco IOS and Cisco IOS XE software. Using the debug Command A debug command produces extensive output that helps you troubleshoot problems in your network. Caution Debugging is a high priority and high CPU utilization process that can render your device unusable. For commands that are enabled by default and have default settings.com/en/US/docs/ios/debug/command/reference/db_book. The no and default forms of commands are described in the command pages of command references. see the Cisco IOS Debug Command Reference at http://www. the ip routing command is enabled by default.cisco. issue the show alias command. using the default form has the same effect as using the no form of the command. To turn off debugging completely. Some debug commands are debug all. you must first enter the terminal monitor command. For example. you would issue the ip routing command. exclude regular expression—Displays all lines except those in which a match of the regular expression is found. include regular expression—Displays all lines in which a match of the regular expression is found. you would issue the no ip routing command.com/en/US/docs/ios/fundamentals/command/reference/cf_book. and debug mpls packets. The best times to run debugging are during periods of low network traffic and when few users are interacting with the network. you must enter the undebug all command. Using output modifiers. Three output modifiers are available and are described as follows: • • • begin regular expression—Displays the first line in which a match of the regular expression is found and all lines that follow.

line protocol is up Serial4/1 is up. It can be a single character or number. or a more complex string. The caret (^) marks the point of the error. You did not enter all the keywords or values required by the command. line protocol is up Serial4/2 is administratively down.Using the Command-Line Interface in Cisco IOS and Cisco IOS XE Software Using the CLI To use one of these output modifiers. Table 5 shows the common CLI error messages. type the command followed by the pipe symbol (|).” Router# show interface | include protocol FastEthernet0/0 is up. % Invalid input detected at “^” You entered the command inmarker. % Incomplete command. A regular expression is a case-sensitive alphanumeric pattern. Volume 1 of 2 (Cisco IOS Release 12. For more system error messages. keywords that you are allowed to enter for the command appear. line protocol is up Serial4/0 is up.4) xi . line protocol is down Understanding CLI Error Messages You may encounter some error messages while using the CLI. Volume 2 of 2 (Cisco IOS Release 12. The keywords that you are allowed to enter for the command appear. correctly. Enter a question mark (?) to display all the commands that are available in this command mode. Table 5 Common CLI Error Messages Error Message % Ambiguous command: “show con” Meaning How to Get Help You did not enter enough Reenter the command followed by a characters for the command to space and a question mark (?). The be recognized. Reenter the command followed by a space and a question mark (?). line protocol is down Serial4/3 is administratively down. The following example illustrates how to filter output of the show interface command to display only lines that include the expression “protocol.4) Cisco IOS System Messages. the modifier. and the regular expression that you want to search for or filter. see the following documents: • • • Cisco IOS Release 12. a phrase. The keywords that you are allowed to enter for the command appear.2SR System Message Guide Cisco IOS System Messages.

com/en/US/products/sw/iosswrel/ps1828/products_white_paper09186a00801830 5e. and general information) (requires Cisco. tools.shtml • • • Software Download Center (downloads..com/kobayashi/sw-center/ Error Message Decoder. the configuration is saved to NVRAM.cisco. On platforms with a Class A flash file system.. you must issue the copy running-config startup-config command or the copy system:running-config nvram:startup-config command.com (also search for documentation by task or product) http://www.cisco.com/en/US/docs/ios/fundamentals/configuration/guide/cf_cli-basics. [OK] Router# On most platforms.html White Paper: Cisco IOS Reference Guide http://www.com User ID and password) http://www. Additional Information • “Using the Cisco IOS Command-Line Interface” section of the Cisco IOS Configuration Fundamentals Configuration Guide: http://www.cisco.html Support area on Cisco.com/en/US/docs/routers/asr1000/configuration/guide/chassis/using_cli. The CONFIG_FILE variable defaults to NVRAM. the configuration is saved to the location specified by the CONFIG_FILE environment variable. When you issue these commands.html • Cisco Product Support Resources http://www.com/pcgi-bin/Support/Errordecoder/index.cisco. a tool to help you research and resolve error messages for Cisco IOS software http://www. The following example shows the syntax of the copy running-config startup-config command: Router# copy running-config startup-config Destination filename [startup-config]? You press Enter to accept the startup-config filename (the default).html or “Using Cisco IOS XE Software” chapter of the Cisco ASR1000 Series Aggregation Services Routers Software Configuration Guide: http://www.com/en/US/support/index. licensing. The following output is displayed indicating that the configuration was saved: Building configuration.cisco. the configuration changes that you made are saved to the startup configuration and saved when the software reloads or power to the device is turned off or interrupted. advisory.cgi • xii .cisco.Using the Command-Line Interface in Cisco IOS and Cisco IOS XE Software Saving Changes to a Configuration Saving Changes to a Configuration To save changes that you made to the configuration of a device. registration.cisco.com/web/psa/products/index. or type a new filename and then press Enter to accept that name.

The Fastest Way to Increase Your Internet Quotient. the Cisco Systems logo. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses.com/pcgi-bin/Support/OutputInterpreter/home.pl\ • CCDE. and Access Registrar. a troubleshooting tool that analyzes command output of supported show commands https://www. Changing the Way We Work. CCENT. CCSP. Catalyst. Play. WebEx. CCDA. GigaDrive. the IronPort logo. PowerPanels. Inc. Inc. PIX. a tool to help you find detailed descriptions of Cisco IOS commands (requires Cisco. iQ Net Readiness Scorecard.com/Support/CLILookup Output Interpreter.cisco.cisco. CCIE. Cisco TelePresence. TransPath. and Welcome to the Human Network are trademarks. Cisco Eos. and Learn and Cisco Store are service marks. Spectrum Expert. Internet Quotient. SenderBase. and/or its affiliates in the United States and certain other countries. EtherFast. IOS. MediaTone. Cisco Systems Capital.com user ID and password) http://tools. The use of the word partner does not imply a partnership relationship between Cisco and any other company. © 2007–2008 Cisco Systems. Event Center. All other trademarks mentioned in this document or Website are the property of their respective owners. CCDP. StackWise. AsyncOS. MGX. Bringing the Meeting To You. LightStream. Live. the Cisco Certified Internetwork Expert logo. CCNP. Cisco.Using the Command-Line Interface in Cisco IOS and Cisco IOS XE Software Additional Information • Command Lookup Tool. Cisco Press. Cisco Nexus. Cisco Unity. Cisco StadiumVision. iQuick Study. All rights reserved. Follow Me Browsing. the iQ logo. Fast Step. CCVP. the Cisco logo. xiii . PCNow. and the WebEx logo are registered trademarks of Cisco Systems. Collaboration Without Limitation. and figures included in the document are shown for illustrative purposes only. ScriptShare. command display output. ProConnect. Networkers. MeetingPlace Chime Sound. IronPort. iPhone. CCNA. CCIP. Network Registrar. Any examples. EtherSwitch. Cisco IOS. Networking Academy. iQ Expertise. Aironet. Cisco Lumin. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Cisco Systems. FormShare. SMARTnet. DCE. HomeLink. MeetingPlace. Linksys.

Using the Command-Line Interface in Cisco IOS and Cisco IOS XE Software Additional Information xiv .

.com/go/cfn. Table 1 lists the features in alphabetical order within the release. All rights reserved. feature set.com is not required. or platform. Find the feature name you are searching for and click on the URL in the “Where Documented” column to access the document containing that feature.html http://www. To access Cisco Feature Navigator. go to http://www. San Jose.html Cisco IOS Release 12.Cisco IOS IP SLAs Features Roadmap First Published: July 11.2SR Cisco IOS Release 12.2SR Feature Name Overview Feature Description Overview of the Cisco IOS IP SLAs technology. The roadmap is organized so that you can select your release train and see the features in that release. Table 1 Supported Cisco IOS IP SLAs Features Release 12..2SR DHCP Operation The Cisco IOS IP SLAs Dynamic Host Control Protocol (DHCP) operation allows you to schedule and measure the network response time between a Cisco device and a DHCP server to obtain an IP address.2SX Cisco IOS Release 12. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release. 2008 This feature roadmap lists the Cisco IOS features documented in the Cisco IOS IP SLAs Configuration Guide and maps them to the documents in which they appear.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_overview. Inc. Where Documented http://www.2SR 12. Americas Headquarters: Cisco Systems. 170 West Tasman Drive. Feature and Release Support Table 1 lists IP SLAs feature support for the following Cisco IOS software release trains: • • • Cisco IOS Release 12. An account on Cisco.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_dhcp.cisco.4T Use Cisco Feature Navigator to find information about platform support and software image support. CA 95134-1706 USA © <year> Cisco Systems. Inc. 2008 Last Updated: July 11.cisco.cisco.

com/en/US/d The Cisco IOS IP SLAs Domain Name System ocs/ios/ipsla/configuration/gui (DNS) operation allows you to measure the difference between the time taken to send a DNS de/sla_dns. jitter (interpacket delay variance).html 12.com/en/US/d ocs/ios/ipv6/configuration/gui de/ip6-mng_apps.cisco.html Ethernet-layer network performance metrics.2SR LSP Health Monitor The Cisco IOS IP SLAs label switched path (LSP) http://www.Cisco IOS IP SLAs Features Roadmap Table 1 Supported Cisco IOS IP SLAs Features (continued) Release 12.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_ftp.2SR Feature Name DNS Operation Feature Description Where Documented http://www.2SR http://www.com/en/US/d The Cisco IOS IP SLAs Hypertext Transfer Protocol (HTTP) operation allows you to measure ocs/ios/ipsla/configuration/gui the network response time between a Cisco device de/sla_http. and TCP connect operations are supported for IPv6. The Cisco IOS IP SLAs Internet Control Message http://www. 2 .com/en/US/d Protocol (ICMP) path echo operation allows you ocs/ios/ipsla/configuration/gui de/sla_icmp_pathecho.html request and receive a reply.cisco.2SR ICMP Echo Operation 12.com/en/US/d LSP Health Monitor with This enhancement to the IP SLAs .cisco.2SR ICMP Path Jitter Operation 12.cisco.html Switching (MPLS) Virtual Private Networks (VPNs). The Cisco IOS IP SLAs UDP jitter. Available statistical measurements for the IP SLAs Ethernet operation include round-trip time. and packet loss.html measure end-to-end network response time between a Cisco device and other devices using IP. The Cisco IOS IP SLAs Internet Control Message http://www.com/en/US/d ocs/ios/ipsla/configuration/gui Protocol (ICMP) echo operation allows you to de/sla_icmp_echo.html variance).html all LSPs between the participating Provider Edge (PE) routers. UDP echo.com/en/US/d Health Monitor feature provides the capability to ocs/ios/ipsla/configuration/gui proactively monitor Layer 3 Multiprotocol Label de/sla_lsp_mon_autodisc.com/en/US/d Protocol (ICMP) path jitter operation allows you ocs/ios/ipsla/configuration/gui to measure hop-by-hop jitter (inter-packet delay de/sla_icmp_pathjitter.2SR ICMP Path Echo Operation 12.cisco.cisco. http://www.2SR Ethernet Operation 12.html and an HTTP server to retrieve a web page.cisco.html 12. http://www. 12.LSP Health ocs/ios/ipsla/configuration/gui LSP Discovery Monitor feature provides automated end-to-end verification in the control plane and data plane for de/sla_lsp_mon_autodisc.cisco.html to measure end-to-end and hop-by-hop network response time between a Cisco device and other devices using IP.com/en/US/d The Cisco IOS IP SLAs for Metro-Ethernet ocs/ios/ipsla/configuration/gui feature provides the capability to gather de/sla_metro_ethernet.2SR FTP Operation 12.2SR HTTP Operation http://www. The Cisco IOS IP SLAs Internet Control Message http://www. ICMP echo. http://www.2SR IP SLAs for IPv6 12.cisco.cisco. The Cisco IOS IP SLAs File Transfer Protocol (FTP) operation allows you to measure the network response time between a Cisco device and an FTP server to retrieve a file.

cisco.html 12. one-way delay.cisco.2SX Overview 12.cisco.2SR Feature Name Multioperation Scheduler Feature Description Where Documented http://www. one-way jitter.html for Pseudo-Wire Emulation Edge-to-Edge (PWE3) services across MPLS networks.2SR UDP Echo Operation http://www.com/en/US/d Virtual Circuit Connectivity Verification (VCCV) ocs/ios/ipsla/configuration/gui de/sla_lsp_mon_autodisc.2SX DNS Operation http://www.cisco. Overview of the Cisco IOS IP SLAs technology.html 12.2SX DHCP Operation The Cisco IOS IP SLAs Dynamic Host Control Protocol (DHCP) operation allows you to schedule and measure the network response time between a Cisco device and a DHCP server to obtain an IP address.com/en/US/d ocs/ios/ipsla/configuration/gui Datagram Protocol (UDP)UDP jitter operation de/sla_udp_jitter_voip.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_tcp.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_dhcp.html http://www.com/en/US/d The Cisco IOS IP SLAs Domain Name System ocs/ios/ipsla/configuration/gui (DNS) operation allows you to measure the difference between the time taken to send a DNS de/sla_dns.cisco.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_overview.cisco. 3 .cisco.2SR VCCV Operation Cisco IOS Release 12.2SX 12.html http://www. The Cisco IOS IP SLAs VCCV operation supports http://www.2SR UDP VoIP Operation 12. and connectivity in networks that carry UDP traffic.2SR UDP Jitter Operation The Cisco IOS IP SLAs User Datagram Protocol http://www.html IP SLAs operations using a single command. Cisco IOS IP SLAs proactive threshold monitoring capability allows you to configure an IP SLAs operation to react to certain measured network conditions.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_udp_echo. 12. allowing you to guarantee VoIP quality levels to your users.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_threshold_mon. The Cisco IOS IP SLAs Voice over IP (VoIP) User http://www.cisco.com/en/US/d ocs/ios/ipsla/configuration/gui (UDP) jitter operation allows you to measure de/sla_udp_jitter. one-way packet loss.html 12.html allows you to proactively monitor VoIP quality levels in your network.com/en/US/d The IP SLAs Multioperation Scheduler feature provides a highly scalable infrastructure for Cisco ocs/ios/ipsla/configuration/gui IOS IP SLAs by allowing you to schedule multiple de/sla_multi_scheduler.html request and receive a reply.cisco.2SR TCP Connect Operation 12.cisco. The Cisco IOS IP SLAs Transmission Control Protocol (TCP) connect operation allows you to measure the network response time taken to perform a TCP Connect operation between a Cisco device and other devices using IP. The Cisco IOS IP SLAs User Datagram Protocol (UDP) echo operation allows you to measure end-to-end network response time between a Cisco device and other devices using IP http://www.html round-trip delay.2SR Proactive Threshold Monitoring 12.Cisco IOS IP SLAs Features Roadmap Table 1 Supported Cisco IOS IP SLAs Features (continued) Release 12. http://www.

html and an HTTP server to retrieve a web page.2SX LSP Health Monitor 12. Cisco IOS IP SLAs proactive threshold monitoring capability allows you to configure an IP SLAs operation to react to certain measured network conditions.html IP SLAs operations using a single command. The Cisco IOS IP SLAs Transmission Control Protocol (TCP) connect operation allows you to measure the network response time taken to perform a TCP Connect operation between a Cisco device and other devices using IP.2SX Proactive Threshold Monitoring 12.html 12.2SX ICMP Path Echo Operation 12. Where Documented http://www.cisco.html between a Cisco device and other devices using IP.Cisco IOS IP SLAs Features Roadmap Table 1 Supported Cisco IOS IP SLAs Features (continued) Release 12.2SX UDP Echo Operation http://www.com/en/US/d Health Monitor feature provides the capability to ocs/ios/ipsla/configuration/gui proactively monitor Layer 3 Multiprotocol Label de/sla_lsp_mon_autodisc.2SX Feature Name FTP Operation Feature Description The Cisco IOS IP SLAs File Transfer Protocol (FTP) operation allows you to measure the network response time between a Cisco device and an FTP server to retrieve a file.2SX Multioperation Scheduler 12.html 4 .com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_udp_echo.com/en/US/d Protocol (ICMP) path jitter operation allows you ocs/ios/ipsla/configuration/gui to measure hop-by-hop jitter (inter-packet delay de/sla_icmp_pathjitter.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_ftp.cisco.cisco.2SX HTTP Operation http://www.com/en/US/d Protocol (ICMP) echo operation allows you to ocs/ios/ipsla/configuration/gui measure end-to-end network response time de/sla_icmp_echo. The Cisco IOS IP SLAs User Datagram Protocol (UDP) echo operation allows you to measure end-to-end network response time between a Cisco device and other devices using IP http://www. The Cisco IOS IP SLAs Internet Control Message http://www.html http://www. http://www.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_threshold_mon. The Cisco IOS IP SLAs label switched path (LSP) http://www.cisco.html 12.cisco.cisco.com/en/US/d Protocol (ICMP) path echo operation allows you ocs/ios/ipsla/configuration/gui de/sla_icmp_pathecho.com/en/US/d The IP SLAs Multioperation Scheduler feature provides a highly scalable infrastructure for Cisco ocs/ios/ipsla/configuration/gui IOS IP SLAs by allowing you to schedule multiple de/sla_multi_scheduler. The Cisco IOS IP SLAs Internet Control Message http://www.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_tcp.html to measure end-to-end and hop-by-hop network response time between a Cisco device and other devices using IP.cisco.cisco.com/en/US/d The Cisco IOS IP SLAs Hypertext Transfer Protocol (HTTP) operation allows you to measure ocs/ios/ipsla/configuration/gui the network response time between a Cisco device de/sla_http.cisco.html variance).2SX ICMP Path Jitter Operation 12. The Cisco IOS IP SLAs Internet Control Message http://www.2SX TCP Connect Operation 12.html Switching (MPLS) Virtual Private Networks (VPNs).cisco.2SX ICMP Echo Operation 12.

com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_dhcp.com/en/US/d ocs/ios/ipsla/configuration/gui Datagram Protocol (UDP)UDP jitter operation de/sla_udp_jitter_voip. http://www.com/en/US/d The Cisco IOS IP SLAs for Metro-Ethernet ocs/ios/ipsla/configuration/gui feature provides the capability to gather de/sla_metro_ethernet. jitter (interpacket delay variance).cisco.4T Ethernet Operation 12.com/en/US/d ocs/ios/ipsla/configuration/gui (UDP) jitter operation allows you to measure de/sla_udp_jitter.html allows you to proactively monitor VoIP quality levels in your network. and packet loss. The Cisco IOS IP SLAs File Transfer Protocol (FTP) operation allows you to measure the network response time between a Cisco device and an FTP server to retrieve a file.html request and receive a reply.cisco. http://www.cisco.com/en/US/d The Cisco IOS IP SLAs Hypertext Transfer Protocol (HTTP) operation allows you to measure ocs/ios/ipsla/configuration/gui the network response time between a Cisco device de/sla_http. http://www. http://www.4T DNS Operation 12.4T HTTP Operation http://www.html measure end-to-end network response time between a Cisco device and other devices using IP.4T FTP Operation 12. Overview of the Cisco IOS IP SLAs technology. 12.html response time between DLSw+ peers.4T Overview 12.cisco. one-way jitter.html and an HTTP server to retrieve a web page.4T ICMP Echo Operation 5 . one-way packet loss. allowing you to guarantee VoIP quality levels to your users. The Cisco IOS IP SLAs Voice over IP (VoIP) User http://www. and connectivity in networks that carry UDP traffic.com/en/US/d ocs/ios/ipsla/configuration/gui (DLSw+) operation allows you to schedule and measure the DLSw+ protocol stack and network de/sla_dlsw.cisco.cisco.Cisco IOS IP SLAs Features Roadmap Table 1 Supported Cisco IOS IP SLAs Features (continued) Release 12.2SX Feature Name UDP Jitter Operation Feature Description Where Documented The Cisco IOS IP SLAs User Datagram Protocol http://www.4T DLSw+ Operation The Cisco IOS IP SLAs Data Link Switching Plus http://www.html http://www.html 12.cisco.2SX UDP VoIP Operation Cisco IOS Release 12.html Ethernet-layer network performance metrics.cisco.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_overview. 12. one-way delay.html round-trip delay.cisco.html 12.cisco.com/en/US/d ocs/ios/ipsla/configuration/gui Protocol (ICMP) echo operation allows you to de/sla_icmp_echo. The Cisco IOS IP SLAs Internet Control Message http://www.com/en/US/d The Cisco IOS IP SLAs Domain Name System ocs/ios/ipsla/configuration/gui (DNS) operation allows you to measure the difference between the time taken to send a DNS de/sla_dns.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_ftp.4T DHCP Operation The Cisco IOS IP SLAs Dynamic Host Control Protocol (DHCP) operation allows you to schedule and measure the network response time between a Cisco device and a DHCP server to obtain an IP address. Available statistical measurements for the IP SLAs Ethernet operation include round-trip time.4T 12.

Cisco IOS IP SLAs proactive threshold monitoring capability allows you to configure an IP SLAs operation to react to certain measured network conditions.cisco. The Cisco IOS IP SLAs User Datagram Protocol (UDP) echo operation allows you to measure end-to-end network response time between a Cisco device and other devices using IP http://www.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_tcp. The Cisco IOS IP SLAs Transmission Control Protocol (TCP) connect operation allows you to measure the network response time taken to perform a TCP Connect operation between a Cisco device and other devices using IP.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_threshold_mon.cisco.cisco.4T Multioperation Scheduler 12.cisco.4T UDP Echo Operation http://www.4T ICMP Path Jitter Operation 12.com/en/US/d ocs/ios/ipv6/configuration/gui de/ip6-mng_apps.html Switching (MPLS) Virtual Private Networks (VPNs). and TCP connect operations are supported for IPv6.html to measure end-to-end and hop-by-hop network response time between a Cisco device and other devices using IP.4T LSP Health Monitor The Cisco IOS IP SLAs label switched path (LSP) http://www.com/en/US/d The IP SLAs Multioperation Scheduler feature provides a highly scalable infrastructure for Cisco ocs/ios/ipsla/configuration/gui IOS IP SLAs by allowing you to schedule multiple de/sla_multi_scheduler.com/en/US/d Protocol (ICMP) path echo operation allows you ocs/ios/ipsla/configuration/gui de/sla_icmp_pathecho.4T Proactive Threshold Monitoring 12.4T RTP Based VoIP Operation 12.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_rtp_voip.4T Feature Name ICMP Jitter Operation Feature Description Where Documented The Cisco IOS IP SLAs Internet Control Message http://www.com/en/US/d Health Monitor feature provides the capability to ocs/ios/ipsla/configuration/gui proactively monitor Layer 3 Multiprotocol Label de/sla_lsp_mon_autodisc. The IP SLAs Real-Time Transport Protocol (RTP)-based Voice over IP (VoIP) operation allows you to set up and schedule a test call and use Voice gateway digital signal processors (DSPs) to gather network performance-related statistics for the call.html IP SLAs operations using a single command.cisco.html http://www. The Cisco IOS IP SLAs Internet Control Message http://www.com/en/US/d Protocol (ICMP) path jitter operation allows you ocs/ios/ipsla/configuration/gui to measure hop-by-hop jitter (inter-packet delay de/sla_icmp_pathjitter.cisco.html variance).cisco.4T TCP Connect Operation http://www. http://www.com/en/US/d ocs/ios/ipsla/configuration/gui Protocol (ICMP) Jitter operation allows you to de/sla_icmp_jitter.html 12. The Cisco IOS IP SLAs UDP jitter.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_udp_echo.html generate a stream of ICMP packets between a Cisco IOS device (source) and any other IP device (destination) to gather network performance-related statistics.html 6 .4T ICMP Path Echo Operation 12. http://www. UDP echo.cisco.html 12.4T IP SLAs for IPv6 12.Cisco IOS IP SLAs Features Roadmap Table 1 Supported Cisco IOS IP SLAs Features (continued) Release 12.cisco.html 12. The Cisco IOS IP SLAs Internet Control Message http://www.cisco. ICMP echo.

CCIP. SMARTnet. DCE. HomeLink. the Cisco logo. Networkers. EtherFast. MeetingPlace. Network Registrar. Any examples. one-way packet loss.html 12. IOS. Inc. CCENT. Cisco Systems. The Cisco IOS IP SLAs Voice over IP (VoIP) User http://www. iQ Net Readiness Scorecard. WebEx. Internet Quotient. and the WebEx logo are registered trademarks of Cisco Systems.cisco. and Learn and Cisco Store are service marks. Live. Cisco TelePresence. iQuick Study. The use of the word partner does not imply a partnership relationship between Cisco and any other company. PCNow. ProConnect. CCSP. Follow Me Browsing. iPhone. one-way jitter.4T CCDE. and Access Registrar. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. The Fastest Way to Increase Your Internet Quotient. iQ Expertise. Fast Step. GigaDrive. Linksys. PIX. CCIE. PowerPanels.4T VoIP Call Setup (Post Dial Delay) Monitoring VoIP Gatekeeper Delay Monitoring 12. Catalyst. Aironet.4T Feature Name UDP Jitter Operation Feature Description Where Documented The Cisco IOS IP SLAs User Datagram Protocol http://www. the iQ logo. The Cisco IOS IP SLAs Voice over IP (VoIP) call http://www. Cisco Press. LightStream. and Welcome to the Human Network are trademarks. MeetingPlace Chime Sound.com/en/US/d ocs/ios/ipsla/configuration/gui (UDP) jitter operation allows you to measure de/sla_udp_jitter. and figures included in the document are shown for illustrative purposes only. MediaTone.html allows you to proactively monitor VoIP quality levels in your network.4T UDP VoIP Operation 12. the Cisco Certified Internetwork Expert logo. Cisco StadiumVision.Cisco IOS IP SLAs Features Roadmap Table 1 Supported Cisco IOS IP SLAs Features (continued) Release 12. CCDA. or aggregated network response time of registration attempts from a VoIP gateway to a VoIP gatekeeper device. one-way delay. and connectivity in networks that carry UDP traffic.cisco. Cisco Nexus. http://www. the IronPort logo. EtherSwitch. Spectrum Expert. ScriptShare.com/en/US/d ocs/ios/ipsla/configuration/gui de/sla_gatekpr_voip. Cisco Unity. Inc. TransPath. the Cisco Systems logo. FormShare. Cisco Systems Capital. Cisco.html The Cisco IOS IP SLAs Voice over IP (VoIP) gatekeeper registration delay operation allows you to measure the average.cisco. Any use of actual IP addresses in illustrative content is unintentional and coincidental. allowing you to guarantee VoIP quality levels to your users. © 2008 Cisco Systems.com/en/US/d ocs/ios/ipsla/configuration/gui Datagram Protocol (UDP)UDP jitter operation de/sla_udp_jitter_voip. and/or its affiliates in the United States and certain other countries. Event Center. Changing the Way We Work. IronPort. SenderBase. Cisco IOS. Play. de/sla_call_setup. CCVP.com/en/US/d setup operation allows you to measure network ocs/ios/ipsla/configuration/gui response time for setting up a VoIP call.cisco. Bringing the Meeting To You. All rights reserved. AsyncOS. Collaboration Without Limitation. StackWise. MGX.html round-trip delay. Cisco Lumin. CCNA. median. All other trademarks mentioned in this document or Website are the property of their respective owners. 7 . command display output. Networking Academy. Cisco Eos. CCDP. CCNP.

Cisco IOS IP SLAs Features Roadmap 8 .

CA 95134-1706 USA © 2007 Cisco Systems. Using Cisco IOS IP SLAs. To access Cisco Feature Navigator. Cisco IOS IP SLAs uses active traffic monitoring—the generation of traffic in a continuous.cisco.com/go/cfn. to lower operational costs. and enterprise customers can verify service levels. Inc. to increase productivity.com is not required. and understand network performance. and to reduce the frequency of network outages. Inc. page 9 Additional References. ease the deployment of new services. and predictable manner—for measuring network performance. All rights reserved. Cisco IOS IP SLAs is a core part of the Cisco IOS Software portfolio which allows Cisco customers to analyze IP service levels for IP applications and services. verify quality of service (QOS).Cisco IOS IP SLAs Overview First Published: August 14. 170 West Tasman Drive. go to http://www. page 2 Where to Go Next. verify outsourced service level agreements. reliable. Contents • • • • Prerequisites for Cisco IOS IP SLAs. San Jose.. 2006 Last Updated: June 16. and assist administrators with network troubleshooting. page 9 Americas Headquarters: Cisco Systems. . page 2 Information About Cisco IOS IP SLAs. 2008 This module describes Cisco IOS IP Service Level Agreements (SLAs). Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. Cisco IOS IP SLAs can perform network assessments. service provider customers can measure and provide service level agreements. An account on Cisco. Cisco IOS IP SLAs can be accessed using the Cisco IOS command-line interface (CLI) or Simple Network Management Protocol (SNMP) through the Cisco Round-Trip Time Monitor (RTTMON) and SYSLOG Management Information Bases (MIBs).

a type of service (ToS) byte (including Differentiated Services Code Point [DSCP] and IP Prefix bits). and for designing network topologies. page 7 Cisco IOS IP SLAs Operation Scheduling. packet sequence. voice quality scoring. verify outsourced service level agreements. service provider customers can measure and provide service level agreements.Cisco IOS IP SLAs Overview Prerequisites for Cisco IOS IP SLAs Prerequisites for Cisco IOS IP SLAs Knowledge of general networking protocols and your specific network design is assumed. page 8 Cisco IOS IP SLAs Operation Threshold Monitoring. Measurement statistics provided by the various Cisco IOS IP SLAs operations can be used for troubleshooting. Cisco IOS IP SLAs performs active monitoring by generating and analyzing traffic to measure performance either between Cisco IOS devices or from a Cisco IOS device to a remote IP device such as a network application server. It simulates network data and IP services. precise service level assurance measurements. reliable. Information About Cisco IOS IP SLAs To implement general configuration and scheduling of Cisco IOS IP SLAs. page 4 Network Performance Measurement Using Cisco IOS IP SLAs. jitter (interpacket delay variance). and collects network performance information in real time. network resource availability. packet loss. Familiarity with network management applications is useful. and URL web address. one-way latency. page 3 Benefits of Cisco IOS IP SLAs. statistics of delay. Cisco IOS IP SLAs sends data across the network to measure performance between multiple network locations or across multiple network paths. server response time. Virtual Private Network (VPN) routing/forwarding instance (VRF). and enterprise customers can verify service levels. page 9 Cisco IOS IP SLAs Technology Overview Cisco IOS IP SLAs uses active traffic monitoring—the generation of traffic in a continuous. Depending on the specific Cisco IOS IP SLAs operation. and understand network performance for new or existing IP services and applications. application performance. and server response time. you should understand the following concepts: • • • • • • • • • • Cisco IOS IP SLAs Technology Overview. packet loss. 2 . page 5 Cisco IOS IP SLAs Operation Types. Cisco IOS IP SLAs uses unique service level assurance metrics and methodology to provide highly accurate. connectivity. page 6 Cisco IOS IP SLAs Responder and IP SLAs Control Protocol. User Datagram Protocol (UDP)/TCP port numbers. path. The information collected includes data about response time. page 6 Response Time Computation for Cisco IOS IP SLAs. Using Cisco IOS IP SLAs. page 8 MPLS VPN Awareness. jitter. and predictable manner—for measuring network performance. page 2 Service Level Agreements. The packets have configurable IP and application layer options such as source and destination IP address. and download time can be monitored within the Cisco device and stored in both CLI and SNMP MIBs. for problem analysis.

my file.com/go/ipsla SNMP notifications based on the data gathered by an Cisco IOS IP SLAs operation allow the router to receive alerts when performance drops below a specified level and when problems are corrected. Network administrators are increasingly required to support service level agreements that support application solutions. 3 . Internet service providers (ISPs) and even internal IT departments now offer a defined level of service—a service level agreement—to provide their customers with a degree of predictability. Cisco IOS IP SLAs uses the Cisco RTTMON MIB for interaction between external Network Management System (NMS) applications and the Cisco IOS IP SLAs operations running on the Cisco devices. and VPNs are creating internal pressures on converged IP networks to become optimized for performance levels. including support of applications. More details about network management products that use Cisco IOS IP SLAs can be found at the following URL: http://www. refer to the text of the CISCO-RTTMON-MIB. available from the Cisco MIB website. The latest performance requirements for business-critical applications. Service Level Agreements Internet commerce has grown significantly in the past few years as the technology has advanced to provide faster. Figure 1 shows how Cisco IOS IP SLAs has taken the traditional concept of Layer 2 service level agreements and applied a broader scope to support end-to-end performance measurement.Cisco IOS IP SLAs Overview Information About Cisco IOS IP SLAs Being Layer-2 transport independent.cisco. more reliable access to the Internet. it also can be used by performance monitoring applications like CiscoWorks Internetwork Performance Monitor (IPM) and other third-party Cisco partner performance management products. Many companies now need online access and conduct most of their business online and any loss of service can affect the profitability of the company. audio and visual conferencing. voice over IP (VoIP) networks. Performance metrics collected by Cisco IOS IP SLAs operations include the following: • • • • • • • • Delay (both round-trip and one-way) Jitter (directional) Packet loss (directional) Packet sequencing (packet ordering) Path (per hop) Connectivity (directional) Server or website download time Voice quality scores Because Cisco IOS IP SLAs is accessible using SNMP. Cisco IOS IP SLAs can be configured end-to-end over disparate networks to best reflect the metrics that an end-user is likely to experience. For a complete description of the object variables referenced by the Cisco IOS IP SLAs feature.

Accuracy—Applications that are sensitive to slight changes in network performance require the precision of the sub-millisecond measurement of Cisco IOS IP SLAs. and path and download time that are broken down into bidirectional and round-trip numbers provide more data than just the bandwidth of a Layer 2 link. • Edge-to-edge network availability monitoring 4 . Pervasiveness—Cisco IOS IP SLAs support exists in Cisco networking devices ranging from low-end to high-end routers and switches.Cisco IOS IP SLAs Overview Information About Cisco IOS IP SLAs Figure 1 Scope of Traditional Service Level Agreement Versus Cisco IOS IP SLAs Traditional Layer 2 SLA Customer site 1 Frame Relay ATM Customer site 2 121379 Application-aware IP SLA Cisco IOS IP SLAs provides the following improvements over a traditional service level agreement: • • End-to-end measurements—The ability to measure performance from one end of the network to the other allows a broader reach and more accurate representation of the end-user experience. Application-aware monitoring—Cisco IOS IP SLAs can simulate and measure performance statistics generated by applications running over Layer 3 through Layer 7. – Provides continuous. This wide range of deployment gives Cisco IOS IP SLAs more flexibility over traditional service level agreements. jitter. Ease of deployment—Leveraging the existing Cisco devices in a large network makes Cisco IOS IP SLAs easier and cheaper to implement than the physical probes often required with traditional service level agreements. measurement. latency. Sophistication—Statistics such as delay. Layer 3 connectivity. you can confidently build an end-to-end application-aware service level agreement. packet sequence. or packet loss in the network. and verification. • Network performance monitoring – Measures the jitter. reliable. • • • • When you know the performance expectations for different levels of traffic from the core of your network to the edge of your network. • IP service network health assessment – Verifies that the existing QoS is sufficient for new IP services. Benefits of Cisco IOS IP SLAs • Cisco IOS IP SLAs monitoring – Provides service level agreement monitoring. Traditional service level agreements can only measure Layer 2 performance. and predictable measurements.

indicates the network availability of an NFS server used to store business critical data from a remote site).Cisco IOS IP SLAs Overview Information About Cisco IOS IP SLAs – Provides proactive verification and connectivity testing of network resources (for example. 4. without deploying a physical probe. a network engineer can monitor the performance between any area in the network: core. 3. and depending on the type of Cisco IOS IP SLAs operation. Configure threshold conditions. A Cisco IOS IP SLAs operation performs a network measurement from the source device to a destination in the network using a specific protocol such as UDP. Monitoring can be done anytime. Using Cisco IOS IP SLAs. 2. Figure 2 shows how Cisco IOS IP SLAs starts when the Cisco IOS IP SLAs device sends a generated packet to the destination device. • Troubleshooting of network operation – Provides consistent. Enable the Cisco IOS IP SLAs Responder. the device will respond with time-stamp information for the source to make the calculation on performance metrics. Configure any options available for the specified Cisco IOS IP SLAs operation type. distribution. 5 . and edge. After the destination device receives the packet. anywhere. if appropriate. • • Voice over IP (VoIP) performance monitoring Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) performance monitoring and network verification Network Performance Measurement Using Cisco IOS IP SLAs Cisco IOS IP SLAs is a core part of the Cisco IOS Software portfolio. then let the operation run for a period of time to gather statistics. Schedule the operation to run. Cisco IOS IP SLAs uses generated traffic to measure network performance between two networking devices such as routers. if required. Configure the required Cisco IOS IP SLAs operation type. reliable measurement that immediately identifies problems and saves troubleshooting time. 5. Figure 2 Cisco IOS IP SLAs Operations Any IP device Performance management application IP SLA measurement and IP SLA responder to IP SLA Responder SNMP IP SLA 121381 IP SLA IP network IP SLA responder IP SLA measurement and IP SLA responder to IP SLA Responder IP SLA source To implement Cisco IOS IP SLAs network performance measurement you need to perform these tasks: 1.

Cisco IOS IP SLAs Responder and IP SLAs Control Protocol The Cisco IOS IP SLAs Responder is a component embedded in the destination Cisco routing device that allows the system to anticipate and respond to Cisco IOS IP SLAs request packets. Only a Cisco IOS device can be a source for a destination IP SLAs Responder.Cisco IOS IP SLAs Overview Information About Cisco IOS IP SLAs 6. see the Cisco IOS IP SLAs Features Roadmap. Upon receipt of the control message. The Cisco IOS IP SLAs Responder provides an enormous advantage with accurate measurements without the need for dedicated probes and additional statistics not available via standard ICMP-based measurements. Figure 2 shows where the Cisco IOS IP SLAs Responder fits in relation to the IP network. Conceptual information about the Cisco IOS IP SLAs Responder and Cisco IOS IP SLAs control protocol. To locate the documentation that includes configuration details and information about the options for each Cisco IOS IP SLAs operation type. the responder will enable the specified UDP or 6 . The patented Cisco IOS IP SLAs Control Protocol is used by the Cisco IOS IP SLAs Responder providing a mechanism through which the responder can be notified on which port it should listen and respond. Display and interpret the results of the operation using Cisco IOS CLI or an NMS system with SNMP. The Cisco IOS IP SLAs Responder listens on a specific port for control protocol messages sent by a Cisco IOS IP SLAs operation. and scheduling options are contained in this document. Cisco IOS IP SLAs Operation Types The various types of Cisco IOS IP SLAs operations include the following: • • • • • • • • • • • • • • • • Data Link Switching Plus (DLSw+) Domain Name System (DNS) Dynamic Host Control Protocol (DHCP) File Transfer Protocol (FTP) Hypertext Transfer Protocol (HTTP) ICMP Echo ICMP jitter ICMP Path Echo ICMP Path Jitter Real-Time Transport Protocol (RTP)-based VoIP Transmission Control Protocol (TCP) Connect UDP Echo UDP jitter UDP jitter for VoIP VoIP gatekeeper registration delay VoIP post-dial delay To locate the documentation that includes configuration details and information about the options for each Cisco IOS IP SLAs operation type. see the Cisco IOS IP SLAs Features Roadmap. thresholding options. the various Cisco IOS IP SLAs operation types.

One-way jitter measurements do not require clock synchronization. In this situation. Four time stamps are taken to make the calculation for round-trip time. Enabling the Cisco IOS IP SLAs Responder on the destination device is not required for all Cisco IOS IP SLAs operations. Cisco IOS IP SLAs test packets use time stamping to minimize the processing delays. due to other high priority processes.Cisco IOS IP SLAs Overview Information About Cisco IOS IP SLAs TCP port for the specified duration. MD5 authentication for control messages is available. The responder disables the port after it responds to the Cisco IOS IP SLAs packet. to capture one-way delay measurements the configuration of both the source router and target router with Network Time Protocol (NTP) is required. During this time. This delay affects the response times because the reply to test packets might be sitting on queue while waiting to be processed. the response times would not accurately represent true network delays. and directional packet loss. Response Time Computation for Cisco IOS IP SLAs Routers may take tens of milliseconds to process incoming packets. Cisco IOS IP SLAs minimizes these processing delays on the source router as well as on the target router (if Cisco IOS IP SLAs Responder is being used). This delta value is then subtracted from the overall round-trip time. if services that are already provided by the destination router (such as Telnet or HTTP) are chosen. the responder accepts the requests and responds to them. while an Cisco IOS IP SLAs test shows an accurate response time due to the time stamping on the responder. Both the source and target need to be synchronized to the same clock source. Because much network behavior is asynchronous. However. the Cisco IOS IP SLAs Responder cannot be configured and Cisco IOS IP SLAs can send operational packets only to services native to those devices. with the responder functionality enabled time stamp 2 (TS2) is subtracted from time stamp 3 (TS3) to produce the time spent processing the test packet as represented by delta. When enabled. the Cisco IOS IP SLAs Responder allows the target device to take two time stamps both when the packet arrives on the interface at interrupt level and again just as it is leaving. At the target router. At times of high network activity. Figure 3 Cisco IOS IP SLAs Responder Time Stamping Source router T2 T1 T4 Target router Responder T3 121380 =T3-T2 RTT (Round-trip time) = T4 (Time stamp 4) . For added security. This time stamping is made with a granularity of sub-millisecond (ms). Notice that the same principle is applied by Cisco IOS IP SLAs on the source router where the incoming time stamp 4 (TS4) is also taken at the interrupt level to allow for greater accuracy. 7 . For non-Cisco devices. jitter. or when the specified time expires. For example. it is critical to have these statistics. an ICMP ping test often shows a long and inaccurate response time. in order to determine true round-trip times. eliminating the processing time. the Cisco IOS IP SLAs Responder need not be enabled.T1 (Time stamp 1) - An additional benefit of the two time stamps at the target router is the ability to track one-way delay. Figure 3 demonstrates how the responder works.

it can start immediately or start at a certain month. You can schedule a single Cisco IOS IP SLAs operation or a group of operations at one time. Consistent reliable measurements immediately identify issues and can save troubleshooting time. day. you must schedule the operation to begin capturing statistics and collecting error information. Cisco IOS IP SLAs can send SNMP traps that are triggered by events such as the following: • • • • • • • • Connection loss Timeout Round-trip time threshold Average jitter threshold One-way packet loss One-way jitter One-way mean opinion score (MOS) One-way latency Alternately. This feature allows you to control the amount of IP SLAs monitoring traffic by scheduling the operations to run at evenly distributed times. For more details on using thresholds with Cisco IOS IP SLAs operations. The pending state is also used when an operation is a reaction (threshold) operation waiting to be triggered.Cisco IOS IP SLAs Overview Information About Cisco IOS IP SLAs Cisco IOS IP SLAs Operation Scheduling After an Cisco IOS IP SLAs operation has been configured. 8 . Cisco IOS IP SLAs Operation Threshold Monitoring To support successful service level agreement monitoring or to proactively measure network performance. see the “IP SLAs—Proactive Threshold Monitoring of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. Multioperations scheduling allows you to schedule multiple Cisco IOS IP SLAs operations using a single command through the Cisco IOS CLI or the CISCO RTTMON-MIB. Determining the type of threshold and the level to set can be complex. the frequency could be increased or an ICMP path echo or ICMP path jitter operation could be initiated for troubleshooting. There is a pending option to set the operation to start at a later time. threshold functionality becomes essential. and it depends on the type of IP service being used in the network. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. an Cisco IOS IP SLAs threshold violation can trigger another Cisco IOS IP SLAs operation for further analysis. For example. and hour. This distribution of IP SLAs operations helps minimize the CPU utilization and thereby enhances the scalability of the network. The pending option is also an internal state of the operation visible through SNMP. When scheduling an operation. To confidently roll out a service level agreement you need to have mechanisms that notify you immediately of any possible violation. For more details about the IP SLAs multioperations scheduling functionality.

Cisco IOS releases. and manage IP VPN services according to the service level agreement for a customer. IP SLAs operations can be configured for a specific VPN by specifying a VPN routing and forwarding (VRF) name.com/go/mibs 9 . Using IP SLAs within MPLS VPNs allows service providers to plan.729A Title Pulse code modulation (PCM) of voice frequencies Reduced complexity 8 kbit/s CS-ACELP speech codec MIBs MIBs CISCO-RTTMON-MIB MIBs Link To locate and download MIBs for selected platforms. Related Documents Related Topic Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands Document Title Cisco IOS IP Service Level Agreements Command Line Interface.Cisco IOS IP SLAs Overview Where to Go Next MPLS VPN Awareness The Cisco IOS IP SLAs MPLS VPN Awareness feature provides the capability to monitor IP service levels within Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs). Where to Go Next For configuration details and information about IP SLAs operation types and IP SLAs features.711 a-law ITU-T G. see the Cisco IOS IP SLAs Features Roadmap. use Cisco MIB Locator found at the following URL: http://www. provision.711 u-law and G. and feature sets. Cisco white paper Cisco IOS IP SLAs Command Reference Standards Standards ITU-T G. Additional References The following sections provide references related to Cisco IOS IP SLAs.cisco.

Cisco IOS. GigaDrive. Cisco TelePresence. containing 30. Cisco Lumin. and/or its affiliates in the United States and certain other countries. iQ Expertise. Inc. Fast Step. the Cisco logo. IronPort. technical tips. PCNow. EtherFast. Event Center. The Fastest Way to Increase Your Internet Quotient. Linksys. Networkers. CCSP. TransPath. LightStream. Spectrum Expert. Title — Technical Assistance Description Technical Assistance Center (TAC) home page. Inc. Collaboration Without Limitation. PIX. Any examples. and Learn and Cisco Store are service marks. Any use of actual IP addresses in illustrative content is unintentional and coincidental. and Welcome to the Human Network are trademarks. the iQ logo. CCENT. CCDP. SMARTnet. Follow Me Browsing. FormShare.com/public/support/tac/home. All rights reserved. CCDA. 10 . and Access Registrar. The use of the word partner does not imply a partnership relationship between Cisco and any other company. solutions. HomeLink. Aironet. IOS. iPhone. Cisco Systems. and the WebEx logo are registered trademarks of Cisco Systems. MGX. StackWise. the IronPort logo.000 pages of searchable technical content. AsyncOS.cisco. Catalyst. command display output. iQ Net Readiness Scorecard. Network Registrar. CCIP. Link http://www. SenderBase. DCE. Cisco StadiumVision. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. CCVP. Play. ProConnect. Cisco Press.com users can log in from this page to access even more content. Changing the Way We Work. and figures included in the document are shown for illustrative purposes only. © 2006-2008 Cisco Systems.shtml CCDE. Cisco Eos. MeetingPlace Chime Sound. PowerPanels. ScriptShare. Cisco Nexus. technologies. Cisco. Networking Academy. and tools. Internet Quotient. the Cisco Certified Internetwork Expert logo. the Cisco Systems logo. and support for existing RFCs has not been modified by this feature.Cisco IOS IP SLAs Overview Additional References RFCs RFCs No new or modified RFCs are supported by this feature. Registered Cisco. WebEx. CCNA. All other trademarks mentioned in this document or Website are the property of their respective owners. including links to products. Live. Cisco Unity. Cisco Systems Capital. Bringing the Meeting To You. CCNP. CCIE. iQuick Study. MediaTone. MeetingPlace. EtherSwitch.

com/go/cfn. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. Inc. one-way packet loss. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported. For more information. one-way delay.cisco. and connectivity in networks that carry UDP traffic in IPv4 or IPv6 networks. Note A VoIP-specific implementation of the UDP jitter operation is available to measure performance by simulating specific voice codecs and returned voice quality scores. to lower operational costs. CA 95134-1706 USA © 2006-2008 Cisco Systems. Cisco IOS IP SLAs is an embedded feature set in Cisco IOS software that allows you to analyze IP service levels for IP applications and services. . one-way jitter.. This module also demonstrates how the data gathered using the UDP jitter operation can be displayed and analyzed using the Cisco IOS command-line interface (CLI).IP SLAs—Analyzing IP Service Levels Using the UDP Jitter Operation First Published: August 14. use the “Feature Information for the IP SLAs UDP Jitter Operation” section on page 14. and to reduce occurrences of network congestion or outages. San Jose.com is not required. IP SLAs uses active traffic monitoring—the generation of traffic in a continuous. see the “IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation” chapter of the Cisco IOS IP SLAs Configuration Guide. on the destination device. 2006 Last Updated: July 16. An account on Cisco. All rights reserved. 170 West Tasman Drive. Americas Headquarters: Cisco Systems. and predictable manner—for measuring network performance. To access Cisco Feature Navigator. go to http://www. The accuracy of measured data is enhanced by enabling the IP SLAs Responder. 2008 This document describes how to use the Cisco IOS IP Service Level Agreements (SLAs) UDP jitter operation to analyze round-trip delay. to increase productivity. Inc. reliable. available in Cisco routers. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module.

the UDP jitter operation can be used as a multipurpose data gathering operation. page 12 Feature Information for the IP SLAs UDP Jitter Operation. the per-direction data allow you to more readily identify where congestion or other problems are occurring in the network. As the UDP jitter operation includes the data returned by the IP SLAs UDP operation. the IP SLAs UDP jitter operation does more than just monitor jitter. page 2 IP SLAs UDP Jitter Operation The IP SLAs UDP jitter operation was primarily designed to diagnose network suitability for real-time traffic applications such as voice over IP (VoIP). at a given frequency of F. page 3 Configuration Examples for the IP SLAs UDP Jitter Operation. positive jitter values are undesirable. page 2 How to Configure the IP SLAs UDP Jitter Operation. and sending and receiving time stamps from the source and the operational target. UDP jitter operations are capable of measuring the following: • • • • Per-direction jitter (source to destination and destination to source) Per-direction packet-loss Per-direction delay (one-way delay) Round-trip delay (average round-trip time) As the paths for the sending and receiving of data may be different (asymmetric). a positive jitter value indicates that the packets arrived greater than 10 ms apart. By default. But if there are delays in the network (like queuing. so as to best simulate the IP service you are providing. and a jitter value of 0 is ideal. page 11 Where to Go Next. the destination should be receiving them 10 ms apart. you should understand the following concept: • IP SLAs UDP Jitter Operation. When multiple packets are sent consecutively from source to destination. The packets IP SLAs generates carry packet sending sequence and receiving sequence information. page 11 Additional References. for example. The UDP jitter operation functions by generating synthetic (simulated) UDP traffic. Each of these parameters are user-configurable. The UDP jitter operation sends N UDP packets. and the operation is repeated every 60 seconds (F). 10 ms apart. Based on these. then positive jitter is 2 ms. each with a payload size of 10 bytes (S) are generated every 10 ms (T). from a source router to a target router. However. or real-time conferencing. video over IP.IP SLAs—Analyzing IP Service Levels Using the UDP Jitter Operation Contents Contents • • • • • • Information About the IP SLAs UDP Jitter Operation. If the packets arrive 12 ms apart. ten packet-frames (N). if the packets arrive 8 ms apart. 2 . arriving through alternate routes. each of size S. sent T milliseconds apart. Jitter means inter-packet delay variance. and so on) the arrival delay between packets might be greater than or less than 10 ms. For delay-sensitive networks like VoIP. then negative jitter is 2 ms. or want to provide. Using this example. and if the network is behaving ideally. page 14 Information About the IP SLAs UDP Jitter Operation To perform the tasks required to verify service levels using the IP SLAs UDP jitter operation.

2. Example: Router# configure terminal Step 3 ip sla responder Enables the IP SLAs Responder. depending on whether you want to configure a basic UDP jitter operation or configure a UDP jitter operation with additional characteristics: 3 . page 3 (required) Configuring and Scheduling a UDP Jitter Operation on the Source Device. 4. • Enter your password if prompted. enable configure terminal ip sla responder exit DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. 3. page 3 (required) Configuring the IP SLAs Responder on the Destination Device Before configuring a UDP jitter operation on the source device. Example: Router> enable Step 2 configure terminal Enters global configuration mode. Perform this task to enable the IP SLAs Responder. the IP SLAs Responder must be enabled on the target device (the operational target). SUMMARY STEPS 1. Example: Router(config)# ip sla responder Step 4 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode. The IP SLAs Responder is available only on Cisco IOS software-based devices. Example: Router(config)# exit Configuring and Scheduling a UDP Jitter Operation on the Source Device Perform one of the following tasks in this section.IP SLAs—Analyzing IP Service Levels Using the UDP Jitter Operation How to Configure the IP SLAs UDP Jitter Operation How to Configure the IP SLAs UDP Jitter Operation This section contains the following procedures: • • Configuring the IP SLAs Responder on the Destination Device.

Before configuring any IP SLAs application. enable configure terminal ip sla operation-number udp-jitter {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname}] [source-port port-number] [control {enable | disable}] [num-packets number-of-packets] [interval interpacket-interval] 4 . A single IP SLAs operation (for example. as shown in Table 1. but values of “0” will be returned for the one-way delay measurements provided by the UDP jitter operation. 3. IP SLAs operation 10) will repeat at a given frequency for the lifetime of the operation. each with an RTP payload size of 32 bytes (S). each of size S. from a source router to a target router. To configure NTP on the source and target devices. interval option frequency (IP SLA) command Elapsed time before the operation repeats. and the operation is repeated every 60 seconds (F).2. perform the tasks in the “Performing Basic System Management” chapter of the Cisco IOS Configuration Fundamentals Configuration Guide. Release 12.IP SLAs—Analyzing IP Service Levels Using the UDP Jitter Operation How to Configure the IP SLAs UDP Jitter Operation • • Configuring and Scheduling a Basic UDP Jitter Operation on the Source Device. are generated every 20 ms (T). such as that provided by NTP. A single UDP jitter operation consists of N UDP packets. 4. is required between the source and the target device in order to provide accurate one-way delay (latency) measurements. perform the task in the “Configuring the IP SLAs Responder on the Destination Device” section on page 3. Time synchronization is not required for the one-way jitter and packet loss measurements. Time synchronization. Configuring and Scheduling a Basic UDP Jitter Operation on the Source Device Perform this task to configure and schedule a basic UDP jitter operation. however. sent T milliseconds apart. in milliseconds (T) Default 10 packets 32 bytes 20 ms Configured Using: udp-jitter command. num-packets option request-data-size command udp-jitter command. Table 1 UDP Jitter Operation Parameters UDP Jitter Operation Parameter Number of packets (N) Payload size per packet (S) Time between packets. SUMMARY STEPS 1. 2. page 4 Configuring and Scheduling a UDP Jitter Operation with Additional Characteristics. at a given frequency of F. one-way jitter and packet loss data will be returned. page 6 The IP SLAs operations function by generating synthetic (simulated) network traffic. By default. in 60 seconds seconds (F) Prerequisites Use of the UDP jitter operation requires that the IP SLAs Responder be enabled on the target Cisco device. Each of these parameters are user-configurable. you can use the show ip sla application command to verify that the operation type is supported on your software image. To enable the Responder. If the time is not synchronized between the source and target devices. ten packets (N).

• Enter your password if prompted. Example: Router(config-ip-sla-jitter)# exit Step 7 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation. Example: Router(config-ip-sla-jitter)# frequency 30 Step 6 exit Exits UDP jitter configuration submode and returns to global configuration mode. 7. the command-line interface (CLI) enters IP SLA jitter configuration mode to allow you to specify optional characteristics for the operation. frequency seconds exit ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] exit show ip sla configuration [operation-number] DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. Example: Router(config)# ip sla 10 Step 4 udp-jitter {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname}] [source-port port-number] [control {enable | disable}] [num-packets number-of-packets] [interval interpacket-interval] Configures the IP SLAs operation as a UDP jitter operation and enters UDP jitter configuration submode. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. 9. 8.29. After entering this command.134 5000 Step 5 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats.139. Example: Router> enable Step 2 configure terminal Enters global configuration mode.IP SLAs—Analyzing IP Service Levels Using the UDP Jitter Operation How to Configure the IP SLAs UDP Jitter Operation 5. Example: Router(config)# ip sla schedule 5 start-time now life forever 5 . 6. Example: Router(config-ip-sla)# udp-jitter 172.

and show ip sla history. samples-of-history-kept. 6 . history filter. Restrictions The IP SLAs UDP jitter operation does not support the IP SLAs History feature (statistics history buckets) because of the large data volume involved with UDP jitter operations.29. If you with configure and schedule a UDP jitter operation with additional characteristics. Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation. Use the verify-data command with caution during normal operations because it generates unnecessary overhead. perform the task in the “Configuring and Scheduling a UDP Jitter Operation with Additional Characteristics” section on page 6. each operation response is checked for corruption. Example: Router# show ip sla configuration 10 Examples The following example shows the configuration of the IP SLAs UDP jitter operation number 10 that will start in 5 minutes and run for 5 minutes.IP SLAs—Analyzing IP Service Levels Using the UDP Jitter Operation How to Configure the IP SLAs UDP Jitter Operation Command or Action Step 8 exit Purpose (Optional) Exits global configuration mode and returns to privileged EXEC mode. • What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. Configuring and Scheduling a UDP Jitter Operation with Additional Characteristics Perform this task to configure and schedule a UDP jitter operation with additional parameters. When enabled. history lives-kept. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. Example: Router(config)# exit Step 9 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation.134 5000 num-packets 20 frequency 30 ip sla schedule 1 life 300 start-time after 00:05:00 Troubleshooting Tips • If the IP SLAs operation is not running and generating statistics.139. The MIB used by IP SLAs (CISCO-RTTMON-MIB) limits the hours-of-statistics kept for the UDP jitter operation to two hours. ip sla 1 udp-jitter 172. This means that the following commands are not supported for UDP jitter operations: history buckets-kept. Configuring a larger value using the history hours-of-statistics hours global configuration change will not increase the value beyond two hours. add the verify-data command to the configuration of the operation (while configuring in IP SLA configuration mode) to enable data verification.

10. flow-label number 17. tag text 13. timeout milliseconds 15. tos number or traffic-class number 16. enable configure terminal ip sla operation-number udp-jitter {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname}] [source-port port-number] [control {enable | disable}] [num-packets number-of-packets] [interval interpacket-interval] history distributions-of-statistics-kept size history enhanced [interval seconds] [buckets number-of-buckets] frequency seconds history hours-of-statistics-kept hours owner owner-id 5. verify-data 18. SUMMARY STEPS 1. exit 20. Note The tos command defines the type of service (ToS) byte in the IPv4 header of an IP SLAs operation and is valid only in IPv4 networks. exit 22. See the CISCO-DATA-COLLECTION-MIB (available from http://www.cisco. threshold milliseconds 14. history statistics-distribution-interval milliseconds 12. vrf vrf-name 19. 8. the Data Collection MIB can be used to collect historical data for the operation. 4. The traffic-class command defines the traffic class byte in the IPv6 header for a supported IP SLAs operation. ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] 21. request-data-size bytes 11. 9. The flow-label command defines the value in the flow label field in the IPv6 header for a supported IP SLAs operation and is valid only in IPv6 networks.com/go/mibs). 3. 6. show ip sla configuration [operation-number] 7 . 2. 7.IP SLAs—Analyzing IP Service Levels Using the UDP Jitter Operation How to Configure the IP SLAs UDP Jitter Operation However.

IP SLAs—Analyzing IP Service Levels Using the UDP Jitter Operation How to Configure the IP SLAs UDP Jitter Operation

DETAILED STEPS
Command or Action
Step 1
enable

Purpose Enables privileged EXEC mode.

Enter your password if prompted.

Example:
Router> enable

Step 2

configure terminal

Enters global configuration mode.

Example:
Router# configure terminal

Step 3

ip sla operation-number

Begins configuration for an IP SLAs operation and enters IP SLA configuration mode.

Example:
Router(config)# ip sla 10

Step 4

udp-jitter {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname}] [source-port port-number] [control {enable | disable}] [num-packets number-of-packets] [interval interpacket-interval]

Configures the IP SLAs operation as a UDP jitter operation and enters UDP jitter configuration submode.
• •

The default number of packets (num-packets) sent is 10. The default interval between packets is 20 milliseconds. The control disable keyword combination should only be used if you are disabling the IP SLAs control protocol on both the source and target routers. The IP SLAs control protocol is enabled by default. After entering this command, the command-line interface (CLI) enters IP SLA jitter configuration mode to allow you to specify optional characteristics for the operation.

Example:
Router(config-ip-sla)# udp-jitter 172.29.139.134 5000

Step 5

history distributions-of-statistics-kept size

(Optional) Sets the number of statistics distributions kept per hop during an IP SLAs operation.

Example:
Router(config-ip-sla-jitter)# history distributions-of-statistics-kept 5

Step 6

history enhanced [interval seconds] [buckets number-of-buckets]

(Optional) Enables enhanced history gathering for an IP SLAs operation.

Example:
Router(config-ip-sla-jitter)# history enhanced interval 900 buckets 100

Step 7

frequency seconds

(Optional) Sets the rate at which a specified IP SLAs operation repeats.

Example:
Router(config-ip-sla-jitter)# frequency 30

8

IP SLAs—Analyzing IP Service Levels Using the UDP Jitter Operation How to Configure the IP SLAs UDP Jitter Operation

Command or Action
Step 8
history hours-of-statistics-kept hours

Purpose (Optional) Sets the number of hours for which statistics are maintained for an IP SLAs operation.

Example:
Router(config-ip-sla-jitter)# history hours-of-statistics-kept 4

Step 9

owner owner-id

(Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation.

Example:
Router(config-ip-sla-jitter)# owner admin

Step 10

request-data-size bytes

(Optional) Sets the protocol data size in the payload of an IP SLAs operation's request packet.

Example:
Router(config-ip-sla-jitter)# request-data-size 64

Step 11

history statistics-distribution-interval milliseconds

(Optional) Sets the time interval for each statistics distribution kept for an IP SLAs operation.

Example:
Router(config-ip-sla-jitter)# history statistics-distribution-interval 10

Step 12

tag text

(Optional) Creates a user-specified identifier for an IP SLAs operation.

Example:
Router(config-ip-sla-jitter)# tag TelnetPollServer1

Step 13

threshold milliseconds

Example:
Router(config-ip-sla-jitter)# threshold 10000

(Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. (Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet.

Step 14

timeout milliseconds

Example:
Router(config-ip-sla-jitter)# timeout 10000

Step 15

tos number

or
traffic-class number

(Optional) In an IPv4 network only, defines the ToS byte in the IPv4 header of an IP SLAs operation. or (Optional) In an IPv6 network only, defines the traffic class byte in the IPv6 header for a supported IP SLAs operation.

Example:
Router(config-ip-sla-jitter)# tos 160

or
Example:
Router(config-ip-sla-jitter)# traffic-class 160

9

IP SLAs—Analyzing IP Service Levels Using the UDP Jitter Operation How to Configure the IP SLAs UDP Jitter Operation

Command or Action
Step 16
flow-label number

Purpose (Optional) In an IPv6 network only, defines the flow label field in the IPv6 header for a supported IP SLAs operation.

Example:
Router(config-ip-sla-jitter)# flow-label 112233

Step 17

verify-data

(Optional) Causes an IP SLAs operation to check each reply packet for data corruption.

Example:
Router(config-ip-sla-jitter)# verify-data

Step 18

vrf vrf-name

Example:
Router(config-ip-sla-jitter)# vrf vpn-A

(Optional) Allows monitoring within Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs) using IP SLAs operations. Exits UDP jitter configuration submode and returns to global configuration mode.

Step 19

exit

Example:
Router(config-ip-sla-jitter)# exit

Step 20

ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring]

Configures the scheduling parameters for an individual IP SLAs operation.

Example:
Router(config)# ip sla schedule 5 start-time now life forever

Step 21

exit

(Optional) Exits global configuration mode and returns to privileged EXEC mode.

Example:
Router(config)# exit

Step 22

show ip sla configuration [operation-number]

(Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation.

Example:
Router# show ip sla configuration 10

Examples
In the following example, two operations are configured as UDP jitter operations, with operation 2 starting five seconds after operation 1. Both operations will run indefinitely.
! ip sla 1 udp-jitter 20.0.10.3 65051 num-packets 20 request-data-size 160 tos 128 frequency 30 ip sla schedule 1 start-time after 00:05:00 ip sla 2 udp-jitter 20.0.10.3 65052 num-packets 20 interval 10 request-data-size 20 tos 64 frequency 30

10

IP SLAs—Analyzing IP Service Levels Using the UDP Jitter Operation Configuration Examples for the IP SLAs UDP Jitter Operation

ip sla schedule 2 start-time after 00:05:05 !

Troubleshooting Tips

If the IP SLAs operation is not running and generating statistics, add the verify-data command to the configuration of the operation (while configuring in IP SLA configuration mode) to enable data verification. When enabled, each operation response is checked for corruption. Use the verify-data command with caution during normal operations because it generates unnecessary overhead. Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation.

What to Do Next
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 the IP SLAs UDP Jitter Operation
This section provides the following configuration example:

Configuring a UDP Jitter Operation: Example, page 11

Configuring a UDP Jitter Operation: Example
In the following example, two operations are configured as UDP jitter operations, with operation 2 starting five seconds after the first operation. Both operations will run indefinitely.
ip sla 1 udp-jitter 20.0.10.3 65051 num-packets 20 request-data-size 160 tos 128 frequency 30 ip sla schedule 1 start-time after 00:05:00 ip sla 2 udp-jitter 20.0.10.3 65052 num-packets 20 interval 10 request-data-size 20 tos 64 frequency 30 ip sla schedule 2 start-time after 00:05:05

On the target (destination) device:
ip sla responder

Where to Go Next
For information about other types of IP SLAs operations and IP SLAs features, see the Cisco IOS IP SLAs Features Roadmap.

11

IP SLAs—Analyzing IP Service Levels Using the UDP Jitter Operation Additional References

Additional References
The following sections provide references related to configuring IP SLAs UDP Jitter operations.

Related Documents
Related Topic Document Title Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP Service Level Agreements Command Line Interface, Cisco white paper Cisco IOS IP SLAs commands Cisco IOS IP SLAs Command Reference

Standards
Standards Title No new or modified standards are supported by this feature, — and support for existing standards has not been modified by features in this document.

MIBs
MIBs CISCO-RTTMON-MIB MIBs Link To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: http://www.cisco.com/go/mibs

RFCs
RFCs No specific RFCs are supported by the features in this document. Title —

12

IP SLAs—Analyzing IP Service Levels Using the UDP Jitter Operation Additional References

Technical Assistance
Description The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. Link http://www.cisco.com/techsupport

13

12. TransPath. Play.2(33)SRB1.2(33)SB. HomeLink. CCDP.com is not required. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. see the command reference documentation. CCIP. or platform.2(33)SXH. iQ Net Readiness Scorecard. MediaTone. and Access Registrar. Cisco Systems Capital. and figures included in the document are shown for illustrative purposes only. feature set. iQ Expertise. iQuick Study. UDP Echo. Cisco Lumin. one-way jitter. FormShare. Cisco Eos. 12. Cisco IOS. PIX. 12. IronPort.2(31)SB2. 12. All rights reserved.1 12. and/or its affiliates in the United States and certain other countries. MeetingPlace. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release. CCNA. 14 . Linksys. the Cisco Systems logo. ProConnect. The use of the word partner does not imply a partnership relationship between Cisco and any other company. subsequent releases of that Cisco IOS software release train also support that feature. Fast Step. the IronPort logo. and connectivity in networks that carry UDP traffic. and the WebEx logo are registered trademarks of Cisco Systems. command display output. Inc. © 2006-2008 Cisco Systems. MeetingPlace Chime Sound. Spectrum Expert. CCIE. Internet Quotient. go to http://www. and Welcome to the Human Network are trademarks. SenderBase. Cisco Press.cisco. Cisco IOS XE Release 2. Live.2(33)SRC. DCE. Networking Academy. the iQ logo. StackWise. All other trademarks mentioned in this document or Website are the property of their respective owners. Event Center. PCNow. PowerPanels. Any examples. Unless noted otherwise. Cisco TelePresence. Networkers. the Cisco Certified Internetwork Expert logo. AsyncOS. Network Registrar. the Cisco logo. EtherFast. ICMP Echo.4(20)T Feature Information The Cisco IOS IP SLAs User Datagram Protocol (UDP) jitter operation allows you to measure round-trip delay. Inc. IP SLAs for IPv6 (UDP Jitter. IOS. Bringing the Meeting To You. Any use of actual IP addresses in illustrative content is unintentional and coincidental. LightStream.IP SLAs—Analyzing IP Service Levels Using the UDP Jitter Operation Feature Information for the IP SLAs UDP Jitter Operation Feature Information for the IP SLAs UDP Jitter Operation Table 2 lists the release history for this feature.com/go/cfn. MGX. Use Cisco Feature Navigator to find information about platform support and software image support. and Learn and Cisco Store are service marks. ScriptShare. SMARTnet. CCDE. Collaboration Without Limitation. Catalyst. GigaDrive. CCVP. An account on Cisco. Cisco Systems. iPhone. one-way delay. To access Cisco Feature Navigator. CCSP. Not all commands may be available in your Cisco IOS software release. Cisco Nexus. Cisco. CCENT. WebEx. Follow Me Browsing. 12. For release information about a specific command. Note Table 2 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Table 2 Feature Information for the IP SLAs UDP Jitter Operation Feature Name IP SLAs UDP Jitter Operation Releases 12. CCDA. Cisco StadiumVision. Changing the Way We Work. Cisco Unity. The Fastest Way to Increase Your Internet Quotient. one-way packet loss. Aironet. TCP Connect) Support was added for operability in IPv6 networks. EtherSwitch.3(14)T. CCNP.

page 2 Americas Headquarters: Cisco Systems. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. go to http://www. The accuracy of measured data is enhanced by enabling the IP SLAs Responder. To access Cisco Feature Navigator. allowing you to guarantee VoIP quality levels to your users in IPv4 or IPv6 networks. All rights reserved. An account on Cisco. San Jose.. The IP SLAs VoIP UDP jitter operation accurately simulates VoIP traffic using common codecs. CA 95134-1706 USA © 2006-2008 Cisco Systems. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported. and calculates consistent voice quality scores (MOS and ICPIF) between Cisco IOS devices in the network. 2006 Last Updated: July 16. and to reduce occurrences of network congestion or outages. to lower operational costs.com/go/cfn. to increase productivity. on the destination device. page 2 Information About IP SLAs VoIP UDP Jitter Operations. Inc. Contents • • • Prerequisites for IP SLAs VoIP UDP Jitter Operations. 170 West Tasman Drive. Cisco IOS IP SLAs is an embedded feature set in Cisco IOS software that allows you to analyze IP service levels for IP applications and services.com is not required. use the “Feature Information for the IP SLAs VoIP UDP Jitter Operation” section on page 17. .cisco. Inc.IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation First Published: August 14. IP SLAs uses active traffic monitoring for measuring network performance. page 2 Restrictions for IP SLAs VoIP UDP Jitter Operations. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module. available in Cisco routers. 2008 This document describes how to use the Cisco IOS IP Service Level Agreements (SLAs) UDP jitter operation to proactively monitor Voice over IP (VoIP) quality levels in your network.

page 5 The IP SLAs MOS Value. Cisco IOS IP SLAs is an integrated feature set in Cisco IOS software. page 8 Configuration Examples for IP SLAs VoIP UDP Jitter Operations. page 4 Voice Performance Monitoring Using IP SLAs. page 4 Codec Simulation Within IP SLAs. page 12 Where to Go Next. page 5 The IP SLAs ICPIF Value. page 17 Glossary. ICPIF and MOS values provided by this feature. Note Predictions of customer opinion (such as those listed for the E-Model transmission rating factor R and derived Mean Opinion Scores) determined by any method are intended only for transmission planning and analysis purposes and should not be interpreted as reflecting actual customer opinions. page 15 Feature Information for the IP SLAs VoIP UDP Jitter Operation. Note The term “Voice” in this document should be taken to mean any Internet telephony applications. page 7 2 . Restrictions for IP SLAs VoIP UDP Jitter Operations This feature uses UDP traffic to generate approximate Voice over IP scores. page 18 Prerequisites for IP SLAs VoIP UDP Jitter Operations To use this feature. while consistent within IP SLAs.IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation Prerequisites for IP SLAs VoIP UDP Jitter Operations • • • • • • How to Configure the IP SLAs VoIP UDP Jitter Operation. you should understand the following concepts: • • • • • • The Calculated Planning Impairment Factor (ICPIF). The term “Voice over IP” can include the transmission of multimedia (both voice and video) over IP networks. are estimates only and are intended only for relative comparisons. page 14 Additional References. It does not provide support for the Real-Time Transport Protocol (RTP). your networking devices on both ends of the connection must support Cisco IOS IP SLAs. The values may not match values determined using other methods. Information About IP SLAs VoIP UDP Jitter Operations To use the IP SLAs VoIP UDP Operation feature. page 3 Mean Opinion Scores (MOS).

Instead. The ICPIF is the sum of measured impairment factors (total impairments.107: “The Impairment Factor method. see the 1996 version of the G. Idte represents impairments caused by talker echo. it refers implementers to G. is now recommended. change of network operator) For further details on the ICPIF.113 Recommendation (2001). Table 1 Quality Levels as a Function of Total Impairment Factor ICPIF Upper Limit for ICPIF 5 10 20 30 45 55 Speech Communication Quality Very good Good Adequate Limiting case Exceptional limiting case Customers likely to react strongly (complaints.” While intended to be an objective measure of voice quality. Ie represents impairments caused by equipment effects.” as part of the formula Icpif = Itot – A. based on how the call was placed (for example. “Transmission impairments.107. a mobile call versus a land-line call). shows how sample ICPIF values are expected to correspond to subjective quality judgement. taken from G. no longer includes the ICPIF model. the ICPIF value is also used to predict the subjective effect of combinations of impairments. Note The latest version of the ITU-T G.” 3 .113 (02/96). Table 1. the key impairments to voice quality that are encountered in the network. such as the type of codec used for the call and packet loss.113. Iq represents impairments caused by PCM quantizing distortion. for comparison and planning purposes. ICPIF values are expressed in a typical range of 5 (very low impairment) to 55 (very high impairment). and A represents an access Advantage Factor (also called the user Expectation Factor) that compensates for the fact that users may accept some degradation in quality in return for ease of access. used by the E-model of ITU-T G. or Itot) minus a user-defined access Advantage Factor (A) that is intended to represent the user’s expectations. ICPIF values numerically less than 20 are generally considered “adequate. the full formula is expressed as: Icpif = Io + Iq + Idte + Idd + Ie – A where • • • • • • Io represents impairments caused by non-optimal loudness rating.113 specification.IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation Information About IP SLAs VoIP UDP Jitter Operations The Calculated Planning Impairment Factor (ICPIF) The ICPIF originated in the 1996 version of ITU-T recommendation G. In its expanded form. Idd represents impairments caused by one-way transmission times (one-way delay). The earlier method that used Quantization Distortion Units is no longer recommended. ICPIF is actually an acronym for “(Impairment) Calculated Planning Impairment Factor.” The ICPIF attempts to quantify.” but should be taken to simply mean the “calculated planning impairment factor.

and MOS values. With MOS.800. the two models should not be confused. that is.) Data. Though the ICPIF shares terms for impairments with the E-Model. but does not yet support the E-Model. provides the potential for more accurate measurements of call quality by refining the definitions of impairment factors (see the 2003 version of the G. A common benchmark used to determine the quality of sound produced by specific codecs is MOS.107 for details). Jitter is the name used to indicate the variation in delay between arriving packets (inter-packet delay variance). transmission rating factor R. Table 2 shows MOS ratings and the corresponding description of quality for each value. on a scale of 1 (poor quality) to 5 (excellent quality). Jitter affects voice quality by causing uneven gaps in the speech pattern of the person talking.Is . a wide range of listeners have judged the quality of voice samples sent using particular codecs. IP SLAs uses a simplified ICPIF formula. Mean Opinion Scores (MOS) The quality of transmitted speech is a subjective response of the listener. IP SLAs is an embedded active monitoring feature of Cisco IOS software that provides a means for simulating and measuring these parameters in order to ensure your network is meeting or exceeding service-level agreements with your users. which consists of UDP probe packets sent across the network from an origin device to a specific destination (called the operational target). The IP SLAs VoIP UDP Operation feature takes advantage of observed correspondences between the ICPIF. Voice Performance Monitoring Using IP SLAs One of the key metrics in measuring voice and video quality over an IP network is jitter. defined in more detail later in this document. This synthetic traffic is used to record the amount of jitter for the connection.IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation Information About IP SLAs VoIP UDP Jitter Operations The full E-Model (also called the ITU-T Transmission Rating Model).Id . in the form of collected statistics. per-direction packet loss. (The term “synthetic traffic” indicates that the network traffic is simulated. an estimated MOS can be computed and displayed based on measured impairments. IP SLAs provides a UDP jitter operation. but not annoying Perceptible and slightly annoying Annoying but not objectionable Very annoying and objectionable As the MOS ratings for codecs and other transmission impairments are known. Other key performance parameters for voice and video transmission over IP networks include latency (delay) and packet loss. the traffic is generated by IP SLAs.1 for details). The opinion scores are averaged to provide the mean for each sample. This estimated value is designated as MOS-CQE (Mean Opinion Score. can 4 . as well as the round-trip time. Each codec used for transmission of Voice over IP provides a certain level of quality. Conversational Quality. Estimated) by the ITU in order to distinguish it from objective or subjective MOS values (see P.Ie + A. expressed as R = Ro . and one-way delay time (one-way latency). Table 2 MOS Ratings Score 5 4 3 2 1 Quality Excellent Good Fair Poor Bad Description of Quality Impairment Imperceptible Just perceptible.

the full ICPIF formula. Because packet delay and packet loss can be measured by IP SLAs. you specify the codec type used for the connection when configuring the VoIP UDP jitter operation. from a given source router to a given target router. at a given frequency f.IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation Information About IP SLAs VoIP UDP Jitter Operations be displayed for multiple tests over a user-defined period of time. each of size s.711 mu-Law (g711ulaw) G. sent 20 milliseconds apart (t). Table 3 Default VoIP UDP Jitter Operation Parameters by Codec Codec G. in addition to the metrics already gathered by the UDP jitter operation. Icpif = Io + Iq + Idte + Idd + Ie – A. with each packet containing 180 bytes of synthetic data (s). the number of packets (n). or over the course of a week. The jitter probe has the advantage of utilizing the IP SLAs Responder to provide minimal latency at the receiving end.) However.711 A-Law (g711alaw) G. The IP SLAs ICPIF Value ICPIF value computation with Cisco IOS software is based primarily on the two main factors that can impair voice quality: delayed packets and lost packets. the size of each payload (s). Based on the type of codec you configure for the operation. Codec Simulation Within IP SLAs The IP SLAs VoIP UDP jitter operation computes statistics by sending n UDP packets. by default a probe operation will be sent once a minute (f). and Idte are zero. The target router must be running the IP SLAs Responder in order to process the probe operations. The IP SLAs VoIP UDP jitter operation modifies the standard UDP jitter operation by adding the capability to return MOS and ICPIF scores in the data collected by the operation. Each probe operation would consist of 1000 packets (n). how the network performs at different times of the day. To generate MOS and ICPIF scores. Iq. for example. troubleshooting. you are given the option. is simplified by assuming the values of Io. resulting in the following formula: Total Impairment Factor (Icpif) = Delay Impairment Factor (Idd) + Equipment Impairment Factor (Ie) – Expectation/Advantage Factor (A) 5 . if you configure the VoIP UDP jitter operation to use the characteristics for the g711ulaw codec. if needed. the inter-packet time interval (t). and health monitoring. (See Table 3 for specifics. thereby improving your ability to perform network assessment.729A (g729a) Default Request Size (Packet Payload) (s) 160 + 12 RTP bytes 160 + 12 RTP bytes 20 + 12 RTP bytes Default Interval Default Between Number of Frequency of Probe Packets (t) Packets (n) Operations (f) 20 ms 20 ms 20 ms 1000 1000 1000 Once every 1 minute Once every 1 minute Once every 1 minute For example. allowing you to see. sent t milliseconds apart. to manually configure these parameters in the syntax of the udp-jitter command. This VoIP-specific implementation provides even more useful information in determining the performance of your VoIP network. and the operational frequency (f) will be auto-configured with default values. Table 3 shows the default parameters that are configured for the operation by codec.

and Digital Signal Processing (DSP) Delay. For example. a mobile phone user in a hard-to-reach location may have an expectation that the connection quality will not be as good as a traditional land-line connection.729A) Codec 20 30 38 42 The Expectation Factor. and an Equipment Impairment Factor. an impairment variable (the Expectation Factor) is subtracted to yield the ICPIF. The second value is variable and is based on the measured one-way delay (round-trip time measurement divided by 2). Table 5 shows sample correspondences between the packet loss measured by IP SLAs and Equipment Impairment Factor values. is intended to represent the fact that users may accept some degradation in quality in return for ease of access.711) Codecs 12 22 28 32 Equipment Impairment Value for the CS-ACELP (G. Table 5 Sample Correspondence of Measured Packet Loss to ICPIF Equipment Impairment Packet Loss (as a percentage of total number of packets sent) 2% 4% 6% 8% The Expectation Factor Equipment Impairment Value for PCM (G. This variable is also called the Advantage Dactor (short for Access Advantage Factor) because it attempts to balance an increased access advantage against a decline in voice quality. Table 4 Sample Correspondence of One-Way Delay to ICPIF Delay Impairment One-Way Delay (ms) 50 100 150 200 Delay Impairment Factor 1 2 4 7 The Equipment Impairment Factor The Equipment Impairment Factor (Ie) is a number based on the amount of measured packet loss. also called the Advantage Factor (A). which is based on a measurement of lost packets. Table 4 shows sample correspondences between the one-way delay measured by IP SLAs and Delay Impairment Factor values. Look Ahead Delay. The Delay Impairment Factor The Delay Impairment Factor (Idd) is a number based on two values. which is based on a measurement of delayed packets. From this sum of the total impairments measured in the network. One value is fixed and is derived using the static values (as defined in the ITU standards) for Codec Delay. The one-way delay value is mapped to a number using a mapping table that is based on a G. corresponds an Equipment Impairment Factor that is defined by codec. The amount of measured packet loss. This is the same formula used by Cisco Gateways to calculate the ICPIF for received VoIP data streams. expressed as a percentage of total number of packets sent.IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation Information About IP SLAs VoIP UDP Jitter Operations This means that the ICPIF value is computed by adding a Delay Impairment Factor. 6 .107 (2002 version) analytic expression.

(for example. defines a set of provisional maximum values for A in terms of the service provided. the values in Table 6 should be considered as the absolute upper limits for A. IP SLAs takes advantage of this correspondence by deriving the approximate MOS score from an estimated R Factor. via multi-hop satellite connections) Advantage / Expectation Factor: Maximum value of A 0 5 10 20 These values are only suggestions. the transmission rating factor R (the R Factor).113. Table 6 Advantage Factor Recommended Maximum Values Communication Service Conventional wire-line (land-line) Mobility (cellular connections) within a building Mobility within a Geographical area or moving in a vehicle Access to hard-to-reach location. This rating. which. Table 7 Correspondence of ICPIF Values to MOS Values ICPIF Range 0–3 4 – 13 14 – 23 24 – 33 34 – 43 MOS 5 4 3 2 1 Quality Category Best High Medium Low Poor 7 . Estimated). The IP SLAs MOS Value IP SLAs uses an observed correspondence between ICPIF and MOS values to estimate an MOS value.107 (03/2003). the use of the factor A and its selected value in a specific application should be used consistently in any planning model you adopt. The E model. as defined in G. a modified inverted form can be used to calculate R Factors from MOS values. Usage of the abbreviation MOS within the context of this feature should be taken to represent the MOS-CQE (Mean Opinion Score.IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation Information About IP SLAs VoIP UDP Jitter Operations Table 6. in turn. However. is derived from the ICPIF score. predicts the subjective quality that is experienced by an average listener by combining the impairment caused by transmission parameters (such as loss and delay) into a single rating. such as the MOS. adapted from ITU-T Rec. Conversely. G. Table 7 shows the resulting MOS values that will be generated for corresponding ICPIF values. Specifically. There is also a relationship between the ICPIF value and the R Factor. The default Advantage Factor for IP SLAs VoIP UDP jitter operations is always zero. To be meaningful. expressed in a scale of 0 (worst) to 100 (best) can be used to predict subjective user reactions. the MOS can be obtained from the R Factor with a converting formula. Conversational Quality.

711 A Law (g711alaw: 64 kbps PCM compression method) G. A MOS value of 0 (zero) indicates that MOS data could not be generated for the operation. Restrictions Currently. with 5 being the best quality.IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation How to Configure the IP SLAs VoIP UDP Jitter Operation IP SLAs will always express the estimated MOS value as a number in the range of 1 to 5.711 mu Law (g711ulaw: 64 kbps PCM compression method) G. you are configuring the VoIP-specific implementation of the jitter operation. available in UDP jitter configuration mode. are not valid for UDP jitter (codec) operations: • • • history distributions-of-statistics-kept history statistics-distribution-interval request-data-size The show ip sla configuration command will list the values for the “Number of statistic distribution buckets kept” and “Statistic distribution interval (milliseconds). As soon as you specify the codec keyword in the udp-jitter command syntax. The VoIP-specific implementation of the IP SLAs UDP jitter operation contains different configuration options than the standard UDP jitter operation.729A (g729a: 8 kbps CS-ACELP compression method) The following commands. Note The tos command defines the type of service (ToS) byte in the IPv4 header of an IP SLAs operation and is valid only in IPv4 networks.” but these values do not apply to jitter (codec) operations. IP SLAs supports only the following speech codecs (compression methods): • • • G. The flow-label command defines the value in the flow label field in the IPv6 header for a supported IP SLAs operation and is valid only in IPv6 networks. SUMMARY STEPS 1. How to Configure the IP SLAs VoIP UDP Jitter Operation This section contains the following procedure: • Configuring the IP SLAs VoIP UDP Jitter Operation Configuring the IP SLAs VoIP UDP Jitter Operation Perform this task to return VoIP scores with IP SLAs VoIP UDP jitter operation statistics. 2. The traffic-class command defines the traffic class byte in the IPv6 header for a supported IP SLAs operation. enable configure terminal 8 .

tos number or traffic-class number 13. exit 19. Example: Router(config)# ip sla 10 9 . show ip sla configuration [operation-number] DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. 10. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] 18. vrf vrf-name 16. Example: Router> enable Step 2 configure terminal Enters global configuration mode. flow-label number 14. 6. 9. 4. • Enter your password if prompted. ip sla operation-number udp-jitter {destination-ip-address | destination-hostname} destination-port codec codec-type [codec-numpackets number-of-packets] [codec-size number-of-bytes] [codec-interval milliseconds] [advantage-factor value] [source-ip {ip-address | hostname}] [source-port port-number] [control {enable | disable}] history enhanced [interval seconds] [buckets number-of-buckets] frequency seconds history hours-of-statistics-kept hours owner owner-id tag text 5. 7. threshold milliseconds 11. 8. exit 17.IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation How to Configure the IP SLAs VoIP UDP Jitter Operation 3. timeout milliseconds 12. verify-data 15.

use one of the following keywords: – g711alaw—64 kbps PCM compression method – g711ulaw—64 kbps PCM compression method Example: Router(config-ip-sla)# udp-jitter 209. and packet loss statistics. jitter.200. • • • • Step 5 history enhanced [interval seconds] [buckets number-of-buckets] (Optional) Enables enhanced history gathering for an IP SLAs operation. Example: Router(config-ip-sla-jitter)# frequency 30 10 . the command-line interface (CLI) enters IP SLA jitter configuration mode to allow you to specify optional characteristics for the operation. • For the codec-type argument. The default is control enable. The control disable keyword combination will disable IP SLAs control packets and cause the operation to malfunction. and number of packet options unless you have a specific reason to override the defaults (for example. codec-size. You can use this option to correct the ICPIF and MOS values for network conditions. You should not specify values for the interval. the destination port number should be an even numbered port in the range 16384 to 32766 or 49152 to 65534. The value you specify for the advantage-factor will be subtracted from the measured impairment values. The default advantage factor (expectation factor) is 0. size. Do not use the control keyword with this command.165. When configuring a jitter operation that uses a codec type.225 16384 codec g711alaw advantage-factor 10 – g729a—8 kbps CS-ACELP compression method • Specifying the codec-type will configure the appropriate default values for the codec-interval. and codec-numpacket options. approximating a different codec). Example: Router(config-ip-sla-jitter)# history enhanced interval 900 buckets 100 Step 6 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats.IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation How to Configure the IP SLAs VoIP UDP Jitter Operation Command or Action Step 4 udp-jitter {destination-ip-address | destination-hostname} destination-port codec codec-type [codec-numpackets number-of-packets] [codec-size number-of-bytes] [codec-interval milliseconds] [advantage-factor value] [source-ip {ip-address | hostname}] [source-port port-number] [control {enable | disable}] Purpose Configures the operation as a jitter (codec) operation that will generate VoIP scores in addition to latency. After entering this command.

defines the ToS byte in the IPv4 header of an IP SLAs operation. Example: Router(config-ip-sla-jitter)# tos 160 or Example: Router(config-ip-sla-jitter)# traffic-class 160 Step 13 flow-label number (Optional) In an IPv6 network only. Example: Router(config-ip-sla-jitter)# history hours-of-statistics-kept 4 Step 8 owner owner-id (Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation. Example: Router(config-ip-sla-jitter)# owner admin Step 9 tag text (Optional) Creates a user-specified identifier for an IP SLAs operation. Example: Router(config-ip-sla-jitter)# tag TelnetPollServer1 Step 10 threshold milliseconds Example: Router(config-ip-sla-jitter)# threshold 10000 (Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. 11 . defines the flow label field in the IPv6 header for a supported IP SLAs operation. or (Optional) In an IPv6 network only. Example: Router(config-ip-sla-jitter)# flow-label 112233 Step 14 verify-data (Optional) Causes an IP SLAs operation to check each reply packet for data corruption. Example: Router(config-ip-sla-jitter)# verify-data Step 15 vrf vrf-name Example: Router(config-ip-sla-jitter)# vrf vpn-A (Optional) Allows monitoring within Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs) using IP SLAs operations. (Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet.IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation How to Configure the IP SLAs VoIP UDP Jitter Operation Command or Action Step 7 history hours-of-statistics-kept hours Purpose (Optional) Sets the number of hours for which statistics are maintained for an IP SLAs operation. defines the traffic class byte in the IPv6 header for a supported IP SLAs operation. Step 11 timeout milliseconds Example: Router(config-ip-sla-jitter)# timeout 10000 Step 12 tos number or traffic-class number (Optional) In an IPv4 network only.

Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. • • IP SLAs VoIP UDP Operation Configuration: Example.225.200.165.IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation Configuration Examples for IP SLAs VoIP UDP Jitter Operations Command or Action Step 16 exit Purpose Exits UDP jitter configuration submode and returns to global configuration mode. • What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. add the verify-data command to the configuration of the operation (while configuring in IP SLA configuration mode) to enable data verification. Use the verify-data command with caution during normal operations because it generates unnecessary overhead. Example: Router# show ip sla configuration 10 Troubleshooting Tips • If the IP SLAs operation is not running and generating statistics. Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation. page 14 12 . each operation response is checked for corruption. Example: Router(config)# exit Step 19 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation. Example: Router(config-ip-sla-jitter)# exit Step 17 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation. page 13 IP SLAs VoIP UDP Operation Statistics Output: Example. a VoIP UDP jitter (codec) operation is configured. This example assumes that the IP SLAs Responder is enabled on the device at 209. Example: Router(config)# ip sla schedule 5 start-time now life forever Step 18 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode. Configuration Examples for IP SLAs VoIP UDP Jitter Operations In the following examples. then output from the corresponding show commands is given. When enabled.

200. .200. Router# show ip sla configuration 10 Entry number: 10 Owner: admin_bofh Tag: Type of operation to perform: jitter Target address: 209.200. .225 16384 codec g711alaw advantage-factor 2 owner admin_bofh ip sla schedule 10 start-time now . Router(config)# ip sla 10 Router(config-sla)# udp-jitter 209. End with the end command.225 16384 codec g711alaw advantage-factor 2 Router(config-sla-jitter)# owner admin_bofh Router(config-sla-jitter)# exit Router(config)# ip sla schedule 10 start-time now Router(config)# exit Router# Router# show running-config | begin ip sla 10 ip sla 10 udp-jitter 209. one per line.0.165.225 Source address: 0.IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation Configuration Examples for IP SLAs VoIP UDP Jitter Operations IP SLAs VoIP UDP Operation Configuration: Example Router> enable Password: Router# configure terminal Enter configuration commands.165.0 Target port: 16384 Source port: 0 Operation timeout (milliseconds): 5000 Codec Type: g711alaw Codec Number Of Packets: 1000 Codec Packet Size: 172 Codec Interval (milliseconds): 20 Advantage Factor: 2 Type Of Service parameters: 0x0 Verify data: No Vrf Name: Control Packets: enabled Operation frequency (seconds): 60 Next Scheduled Start Time: Start Time already passed Life (seconds): 3600 Entry Ageout (seconds): never Status of entry (SNMP RowStatus): Active Connection loss reaction enabled: No Timeout reaction enabled: No Verify error enabled: No Threshold reaction type: Never Threshold (milliseconds): 5000 Threshold Falling (milliseconds): 3000 Threshold Count: 5 Threshold Count2: 5 Reaction Type: None Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20 Enhanced History: 13 .165.0.

see the Cisco IOS IP SLAs Features Roadmap.” “Number of packets. Router# show ip sla statistics 10 Entry number: 10 Modification time: 12:57:45.” and “Interval (milliseconds)” parameters will not be displayed in the show ip sla configuration command output. values for “Codec Packet Size.690 UTC Sun Oct 26 2003 Number of operations attempted: 1 Number of operations skipped: 0 Current seconds left in Life: Forever Operational state of entry: Active Last time this entry was reset: Never Connection loss occurred: FALSE Timeout occurred: FALSE Over thresholds occurred: FALSE Latest RTT (milliseconds): 19 Latest operation start time: 12:57:45.20 ! RTT Values: NumOfRTT: 10 RTTAvg: 19 RTTMin: 19 RTTMax: 20 RTTSum: 191 RTTSum2: 3649 Packet Loss Values: PacketLossSD: 0 PacketLossDS: 0 PacketOutOfSequence: 0 PacketMIA: 0 PacketLateArrival: 0 InternalError: 0 Busies: 0 Jitter Values: NumOfJitterSamples: 9 MinOfPositivesSD: 0 MaxOfPositivesSD: 0 NumOfPositivesSD: 0 SumOfPositivesSD: 0 Sum2PositivesSD: MinOfNegativesSD: 0 MaxOfNegativesSD: 0 NumOfNegativesSD: 0 SumOfNegativesSD: 0 Sum2NegativesSD: MinOfPositivesDS: 1 MaxOfPositivesDS: 1 NumOfPositivesDS: 1 SumOfPositivesDS: 1 Sum2PositivesDS: MinOfNegativesDS: 1 MaxOfNegativesDS: 1 NumOfNegativesDS: 1 SumOfNegativesDS: 1 Sum2NegativesDS: Interarrival jitterout: 0 Interarrival jitterin: 0 One Way Values: NumOfOW: 0 OWMinSD: 0 OWMaxSD: 0 OWSumSD: 0 OWSum2SD: 0 OWMinDS: 0 OWMaxDS: 0 OWSumDS: 0 OWSum2DS: 0 0 0 1 1 Where to Go Next For information about other types of IP SLAs operations and IP SLAs features.723 Sun Oct 26 2003 Latest operation return code: OK ! Voice Scores: ICPIF: 20 MOS Score: 3.” “Codec Number of Packets.IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation Where to Go Next When a codec type is configured for a jitter operation.” and “Codec Interval (milliseconds)” are displayed. Instead. the standard jitter “Request size (ARR data portion). IP SLAs VoIP UDP Operation Statistics Output: Example Use the show ip sla statistics command to display Voice scores (ICPIF and MOS values) for the jitter (codec) operation. 14 .

IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation Additional References

Additional References
The following sections provide references related to the IP SLAs VoIP UDP Jitter Operation feature.

Related Documents
Related Topic Voice over IP (VoIP) codecs Document Title “Understanding Codecs: Complexity, Hardware Support, MOS, and Negotiation” http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note0 9186a00800b6710.shtml Jitter in Packet Voice Networks “Understanding Jitter in Packet Voice Networks (Cisco IOS Platforms)” http://www.cisco.com/en/US/tech/tk652/tk698/technologies_tech_ note09186a00800945df.shtml Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands PSTN Fallback for Voice Gateways Cisco IOS IP Service Level Agreements Command Line Interface, Cisco white paper Cisco IOS IP SLAs Command Reference “SIP: Measurement-Based Call Admission Control for SIP” http://www.cisco.com/en/US/docs/ios/12_2t/12_2t15/feature/guide /ftcacsip.html

Standards
Standard ITU-T Recommendation G.107 (2003) ITU-T Recommendation G.113 (1996) ITU-T Recommendation G.113 (2001) ITU-T Recommendation G.711 (1998) ITU-T Recommendation G.729 Annex A (1996) ITU-T Recommendation P.800.1 (2003) Title The E-model, a computation model for use in transmission planning Transmission impairments Transmission impairments due to speech processing Pulse code modulation (PCM) of voice frequencies (also known as the G.711 Voice Codec) Reduced complexity 8 kbit/s CS-ACELP speech codec (also known as the G.729/A/B Speech Codec) Mean Opinion Score (MOS) terminology

Full support for these standards is not claimed. ITU Telecommunication Standards (“ITU-T Recommendations In Force”) can be obtained from http://www.itu.ch. Summary definitions are available from a variety of internet sources.

15

IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation Additional References

MIBs
MIB CISCO-RTTMON-MIB MIB Link To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: http://www.cisco.com/go/mibs

RFCs
RFC1 RFC 768 RFC 1889
1. Full support by this feature for listed RFCs is not claimed.

Title User Datagram Protocol RTP: A Transport Protocol for Real-Time Applications

Technical Assistance
Description The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. Link http://www.cisco.com/techsupport

16

IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation Feature Information for the IP SLAs VoIP UDP Jitter Operation

Feature Information for the IP SLAs VoIP UDP Jitter Operation
Table 8 lists the release history for this feature. Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation. Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Note

Table 8 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.

Table 8

Feature Information for the IP SLAs VoIP UDP Jitter Operation

Feature Name IP SLAs UDP Jitter Operation

Releases 12.3(14)T, 12.2(31)SB2, 12.2(33)SRB1, 12.2(33)SXH, Cisco IOS XE Release 2.1 12.2(33)SRC, 12.2(33)SB, 12.4(20)T

Feature Information The Cisco IOS IP SLAs User Datagram Protocol (UDP) jitter operation allows you to measure round-trip delay, one-way delay, one-way jitter, one-way packet loss, and connectivity in networks that carry UDP traffic.

IP SLAs for IPv6 (UDP Jitter, UDP Echo, ICMP Echo, TCP Connect)

Support was added for operability in IPv6 networks.

17

IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation Glossary

Glossary
codec—In the context of IP Telephony, a codec is a compression and decompression algorithm used to transfer voice and video data more efficiently. Voice codec types are typically referred to using the ITU recommendation number that defines the algorithm (for example, “G.711” instead of “PCM”). CS-ACELP—The codec type defined in the reference documents G.729 and G.729A, Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited linear-prediction (CS-ACELP). ITU—The International Telecommunication Union. The ITU is an international organization within the United Nations System where governments and the private sector coordinate global telecom networks and services. The ITU Telecommunication Standardization Sector (ITU-T), responsible for defining standards (Recommendations) covering all fields of telecommunications, is one of the three operational sectors of the ITU. The ITU web site is at http://www.itu.int. ITU-T—ITU Telecommunication Standardization Sector. The ITU-T is one of the three operational sectors of the ITU, and is responsible for defining standards (called ITU-T Recommendations) covering all fields of telecommunications. MOS-CQE (Mean Opinion Score; Conversational Quality, Estimated)—The score calculated by a network planning model which aims at predicting the quality in a conversational application situation. Estimates of conversational quality carried out according to ITU-T Rec. G.107, when transformed to a mean opinion score (MOS), give results in terms of MOS-CQE.1 PCM—The codec type defined in the reference document G.711, Pulse code modulation (PCM) of voice frequencies.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. All other trademarks mentioned in this document or Website 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. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. © 2006-2008 Cisco Systems, Inc. All rights reserved.

1. Definition from ITU-T Recommendation P.800.1. Used in accordance with the ITU Copyright and Disclaimer Notice.

18

IP SLAs—LSP Health Monitor with LSP Discovery
First Published: February 27, 2007 Last Updated: July 16, 2008

The Cisco IOS IP Service Level Agreements (SLAs) label switched path (LSP) Health Monitor with LSP Discovery feature provides the capability to proactively monitor Layer 3 Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs). This feature provides automated end-to-end verification in the control plane and data plane for all LSPs between the participating Provider Edge (PE) routers. This end-to-end (PE-to-PE router) approach ensures that LSP connectivity is verified along the paths that customer traffic is sent. Consequently, customer-impacting network connectivity issues that occur within the MPLS core will be detected by the LSP Health Monitor. Once configured, the LSP Health Monitor will automatically create and delete IP SLAs LSP ping or LSP traceroute operations based on network topology. The LSP Health Monitor feature also allows you to perform multioperation scheduling of IP SLAs operations and supports proactive threshold monitoring through SNMP trap notifications and syslog messages.
Finding Feature Information in This Module

Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the “Feature Information for the LSP Health Monitor” section on page 42.
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images

Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Contents
• • •

Prerequisites for the LSP Health Monitor, page 2 Restrictions for the LSP Health Monitor, page 2 Information About the LSP Health Monitor, page 2

Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

© 2007-2008 Cisco Systems, Inc. All rights reserved.

IP SLAs—LSP Health Monitor with LSP Discovery Prerequisites for the LSP Health Monitor

• • • • •

How to Use the LSP Health Monitor, page 12 Configuration Examples for the LSP Health Monitor, page 30 Additional References, page 39 Command Reference, page 40 Feature Information for the LSP Health Monitor, page 42

Prerequisites for the LSP Health Monitor

The participating PE routers of an LSP Health Monitor operation must support the MPLS LSP ping feature. It is recommended that the Provider (P) routers also support the MPLS LSP Ping feature in order to obtain complete error reporting and diagnostics information. For more information about the MPLS LSP Ping feature, see the “Related Documents” section on page 39. Ensure that the source PE router has enough memory to support the desired LSP Health Monitor functionality. Enabling the LSP discovery option can potentially have a significant impact on router memory. If there is not enough memory available during the LSP discovery process, the process will gracefully terminate and an error message will be displayed.

Note

The destination PE routers of an LSP Health Monitor operation do not require the IP SLAs Responder to be enabled.

Restrictions for the LSP Health Monitor
• •

The LSP Health Monitor with LSP Discovery feature supports Layer 3 MPLS VPNs only. The LSP discovery process can potentially have a significant impact on the memory and CPU of the source PE router. To prevent unnecessary router performance issues, careful consideration should be taken when configuring the operational and scheduling parameters of an LSP Health Monitor operation. Once an LSP Health Monitor operation is started, its configuration parameters should not be changed until the operation has ended. Changing the configuration parameters while the operation is actively running could cause delays in obtaining network connectivity statistics. The LSP discovery option does not support IP SLAs LSP traceroute operations. The LSP discovery option does not support IP SLAs VCCV operations.

• •

Information About the LSP Health Monitor
To use the LSP Health Monitor feature, you should understand the following concepts:
• • • • •

Benefits of the LSP Health Monitor, page 3 How the LSP Health Monitor Works, page 3 Discovery of Neighboring PE Routers, page 5 The LSP Discovery Process, page 6 LSP Discovery Groups, page 7

2

IP SLAs—LSP Health Monitor with LSP Discovery Information About the LSP Health Monitor • • • • IP SLAs LSP Ping and LSP Traceroute Operations. Note The LSP discovery process can potentially have a significant impact on the memory and CPU of the source PE router. The user configures an LSP Health Monitor operation and the BGP next hop neighbor discovery process is enabled. page 10 Multioperation Scheduling for the LSP Health Monitor. see the “Configuring the LSP Health Monitor Without LSP Discovery” section on page 12 and “Configuring the LSP Health Monitor with LSP Discovery” section on page 17. all operation parameters for an LSP Health Monitor operation are configured after an identification number for the operation is specified. page 9 IP SLAs VCCV Operation. The general process for how the LSP Health Monitor works is as follows: 1. page 9 Proactive Threshold Monitoring for the LSP Health Monitor. with threshold violations and scalable operation scheduling Monitoring and SNMP trap alerts for round-trip time (RTT) threshold violations. However. To prevent unnecessary router performance issues. Configuring an LSP Health Monitor operation is similar to configuring a standard IP SLAs operation. For more information on how to configure the LSP Health Monitor. To illustrate. and command response timeouts How the LSP Health Monitor Works The LSP Health Monitor feature provides the capability to proactively monitor Layer 3 MPLS VPNs. page 11 Benefits of the LSP Health Monitor • • • • • • • • • End-to-end LSP connectivity measurements across equal-cost multipaths for determining network availability or testing network connectivity in MPLS networks Proactive threshold monitoring through SNMP trap notifications and syslog messages Reduced network troubleshooting time for MPLS networks Scalable network error detection using fast retry capability Creation and deletion of IP SLAs operations based on network topology Discovery of Border Gateway Protocol (BGP) next hop neighbors based on local VPN routing and forwarding instances (VRFs) and global routing tables Multioperation scheduling of IP SLAs operations Pseudo-wire connectivity testing between MPLS network edges. connection loss. careful consideration should be taken when configuring the operational and scheduling parameters of an LSP Health Monitor operation. 3 . unlike standard IP SLAs operations. these configured parameters are then used as the base configuration for the individual IP SLAs LSP ping and LSP traceroute operations that will be created by the LSP Health Monitor.

When the IP SLAs access list parameter is configured. For more information about multioperation scheduling. For more information about configuring standard IP access lists. see the “Multioperation Scheduling for the LSP Health Monitor” section on page 11. a single IP SLAs operation is automatically created (based on parameters configured in Step 1) for each applicable PE (BGP next hop) neighbor. If a BGP next hop neighbor is removed from a particular VPN. The start time and frequency of each measurement is based on the multioperation scheduling parameters defined by the user. the LSP Health Monitor will automatically create IP SLAs operations only for those BGP next hop neighbors with source addresses that satisfy the criteria permitted by the standard IP access list. However. The automatic deletion of operations can be disabled. creation of LSP discovery groups for newly discovered BGP next hop neighbors will follow the same process as described in the “The LSP Discovery Process” section on page 6. see the “Discovery of Neighboring PE Routers” section on page 5. Once the LSP Health Monitor operation is started. the equal-cost multipaths between the source and destination PE routers are discovered. Access Lists for Filtering BGP Next Hop Neighbors Standard IP access lists can be configured (using the access-list command in global configuration mode) to restrict the number of IP SLAs operations that are automatically created by the LSP Health Monitor. This information is stored in a queue maintained by the LSP Health Monitor. Depending on the proactive threshold monitoring configuration options chosen. For more information about the BGP next hop neighbor discovery process. disabling this function is not recommended because these operations would then need to be deleted manually. 2. The user configures multioperation scheduling parameters for the LSP Health Monitor operation. For more information on how the LSP discovery process works. SNMP trap notifications or syslog messages will be generated as threshold violations are met. In other words. see the “Related Documents” section on page 39. see the “Proactive Threshold Monitoring for the LSP Health Monitor” section on page 10. Addition and Deletion of IP SLAs Operations The LSP Health Monitor receives periodic notifications about BGP next hop neighbors that have been added to or removed from a particular VPN. new IP SLAs operations are automatically created for newly discovered PE routers and existing IP SLAs operations are automatically deleted for any PE routers that are no longer valid. The IP SLAs operations will measure network connectivity between the source PE router and the discovered destination PE router. Note By default. Based on the information in the queue and user-specified time intervals. the list of BGP next hop neighbors discovered by the LSP Health Monitor is filtered based on the conditions defined by the associated standard IP access list. see “The LSP Discovery Process” section on page 6. If the LSP discovery option is enabled. all the corresponding LSP discovery groups and their associated individual IP SLAs operations and statistics are removed from the LSP discovery group database. 4 . The user configures proactive threshold monitoring parameters for the LSP Health Monitor operation. a database of BGP next hop neighbors in use by any VRF associated with the source PE router is generated based on information from the local VRF and global routing tables.IP SLAs—LSP Health Monitor with LSP Discovery Information About the LSP Health Monitor When the BGP next hop neighbor discovery process is enabled. only a single path between the source and destination PE routers is discovered. If the LSP discovery option is enabled. 3. For more information about proactive threshold monitoring.

12 VPN red VPN blue VPN green ISP LSP ping for IPv4 FEC 12. In this example.VRF: VPN Blue .12. there are three VPNs associated with router PE1: red. see the “Related Documents” section on page 39.13.13.13/32) .12.13.12/32) .12 and PE3 13. For more information about the MPLS LSP Ping feature. Figure 1 BGP Next Hop Neighbor Discovery for a Simple VPN PE2 12.12/32 VPN red VPN blue VPN green LSP ping for IPv4 FEC 13.13).13.12) and PE3 (router ID: 13.13.13.13 (prefix 13. The database in this example contains two BGP next hop router entries: PE2 12.12 (prefix 12. In most cases.13. Discovery of Neighboring PE Routers A BGP next hop neighbor discovery process is used to find the BGP next hop neighbors in use by any VRF associated with the source PE router.12. As routing updates are received. Figure 1 shows how the BGP next hop neighbor discovery process works for a simple VPN scenario for an Internet service provider (ISP). these VPNs are reachable remotely through BGP next hop neighbors PE2 (router ID: 12.12.VRF: VPN Red BGP next hop 13. When the BGP next hop neighbor discovery process is enabled.13.13. blue.12.13. new BGP next hop neighbors are added to and deleted from the database immediately.12.VRF: VPN Green PE1 PE PE3 13. and green. The routing entries are maintained per next hop router to distinguish which next hop routers belong within which particular VRF.13. If the length of the owner field is longer than 255 characters. For each next hop router entry. these neighbors will be PE routers. From the perspective of router PE1.13 5 135838 .12.12.13/32 LSP Discovery on PE1 BGP next hop 12.13.12. a database of BGP next hop neighbors in use by any VRF associated with the source PE router is generated based on information from the local VRF and global routing tables. The owner field of an operation is generated using all the parameters that can be configured for that particular operation.IP SLAs—LSP Health Monitor with LSP Discovery Information About the LSP Health Monitor Unique Identifier for Each Automatically Created IP SLAs Operation The IP SLAs operations automatically created by the LSP Health Monitor are uniquely identified by their owner field. a database is generated based on the local VRF and global routing tables.12. the IPv4 Forward Equivalence Class (FEC) of the BGP next hop router in the global routing table is provided so that it can be used by the MPLS LSP ping operation.12.13. it will be truncated. When the BGP next hop neighbor discovery process is enabled on router PE1.12.

This technique ensures that there is only a single IP SLAs LSP ping operation for each source and destination PE router pair. The parameters that uniquely identify each equal-cost multipath (127/8 destination IP address [LSP selector] and the PE outgoing interface) are added to the associated LSP discovery database. An LSP discovery request is sent by the LSP Health Monitor to the LSP discovery subsystem for each applicable BGP next hop neighbor. and significantly reduces the number of active LSP ping operations sent by the source PE router. The IP SLAs superoperation operates by sending an LSP ping packet to the destination PE router and adjusting the LSP ping 127/8 LSP selector IP address for each discovered equal-cost multipath. Only a single path to each applicable PE neighbor is discovered during this initial step of the LSP discovery process.0. The IP SLAs superoperation would sequentially send three LSP ping packets using the identified LSP selector IP addresses for directing the superoperation across the three paths. 2. the LSP Health Monitor creates an LSP discovery group (that initially consists of only the one discovered path) and assigns the group with a unique identification number.0. If path 1 and path 2 are equal-cost multipaths between router PE1 to router PE2. Network connectivity measurements can then be performed for each of the paths that were discovered. 3. 6 . An IP SLAs LSP ping superoperation would also be created to monitor network availability across each path. a single IP SLAs operation is automatically created for each applicable PE (BGP next hop) neighbor. 127. For more information about the BGP next hop neighbor discovery process. and 127.1. Once the LSP Health Monitor operation is started. For each next hop neighbor in which an appropriate response is received. For information about proactive threshold monitoring and multioperation scheduling of IP SLAs operations created through the LSP discovery process. The general process for LSP discovery is as follows: 1. Figure 2 illustrates a simple VPN scenario. then the LSP discovery process would create an LSP discovery group consisting of path 1 and path 2. For each next hop neighbor.6. Note For a given LSP Health Monitor operation. Suppose router PE1 is the source PE router for an LSP Health Monitor operation with the LSP discovery option enabled and that router PE2 is discovered by the BGP discovery process as a BGP next hop neighbor to router PE1. see the “Proactive Threshold Monitoring for the LSP Health Monitor” section on page 10 and “Multioperation Scheduling for the LSP Health Monitor” section on page 11. This network consists of a core MPLS VPN with two PE routers (router PE1 and router PE2) belonging to the VRF named VPN blue. Each individual IP SLAs operation (created for each applicable PE neighbor) uses an IP SLAs LSP ping superoperation to measure network connectivity across all equal-cost multipaths between the source PE router and discovered destination PE router.0.IP SLAs—LSP Health Monitor with LSP Discovery Information About the LSP Health Monitor The LSP Discovery Process The LSP discovery option of an LSP Health Monitor operation provides the capability to discover the equal-cost multipaths for carrying MPLS traffic between the source and destination PE routers. For example. the user can define the maximum number of BGP next hop neighbors that can be concurrently undergoing LSP discovery.0. see the “LSP Discovery Groups” section on page 7. For more information about LSP discovery groups. MPLS echo requests are sent one-by-one from the source PE router to discover the equal-cost multipaths.5.0. BGP next hop neighbors are discovered using the BGP next hop neighbor discovery process.0. assume that there are three equal-cost multipaths to a destination PE router and the identified LSP selector IP addresses are 127. see the “Discovery of Neighboring PE Routers” section on page 5.

Each LSP discovery group corresponds to one BGP next hop neighbor and is assigned a unique identification number (starting with the number 1). LSP discovery group 1 is created for the equal-cost multipaths between router PE1 to router PE2 and LSP discovery group 2 is created for the equal-cost multipaths between router PE1 to router PE3. Figure 3 illustrates a simple VPN scenario. This network consists of a core MPLS VPN with three PE routers (router PE1.IP SLAs—LSP Health Monitor with LSP Discovery Information About the LSP Health Monitor Figure 2 LSP Discovery for a Simple VPN VPN blue VPN blue PE1 PE2 Path 1 Path 2 LSP Discovery Groups A single LSP Health Monitor operation can be comprised of several LSP discovery groups depending on the number of BGP next hop neighbors discovered by the BGP next hop neighbor discovery process. PE2. Suppose router PE1 is the source PE router for an LSP Health Monitor operation with the LSP discovery option enabled and that router PE2 and PE3 are discovered by the BGP discovery process as BGP next hop neighbors to router PE1. and PE3) belonging to the VRF named VPN blue. 170139 MPLS Core 7 .

The network connectivity statistics collected by each equal-cost multipath is aggregated and stored in one-hour increments (data can be collected for a maximum of two hours). Each equal-cost multipath discovered between the source PE router and a BGP next hop neighbor is uniquely identified with the following parameters: • • 127/8 destination IP address (LSP selector) within the local host IP address range PE outgoing interface The corresponding LSP ping superoperation sends an LSP ping packet. The database for an LSP discovery group is updated if any of the following events occur: • • • 8 170140 . The LSP ping superoperation operates by sending an LSP ping packet to the destination PE router and adjusting the LSP ping 127/8 LSP selector IP address for each discovered equal-cost multipath. Each LSP ping superoperation corresponds to a single LSP discovery group. The user enters the Cisco IOS command to delete all the aggregated statistical data for a particular LSP discovery group.IP SLAs—LSP Health Monitor with LSP Discovery Information About the LSP Health Monitor Figure 3 LSP Discovery Groups for a Simple VPN VPN blue VPN blue PE1 PE2 Group 1 Group 2 PE3 MPLS Core VPN blue Once the LSP Health Monitor operation is started. Results are stored as group averages representative of all the equal-cost multipaths within the LSP discovery group for a given one-hour increment. Each IP SLAs operation (created for each applicable PE neighbor) uses an IP SLAs LSP ping superoperation to measure network connectivity across all equal-cost multipaths between the source PE router and discovered destination PE router. a single IP SLAs operation is automatically created for each applicable PE (BGP next hop) neighbor. An active equal-cost multipath is added to or deleted from the LSP discovery group.

you can schedule an IP SLAs VCCV operation to periodically perform VCCV for PWE3 services. The IP SLAs VCCV operation type is based on the ping mpls pseudowire command. you can use the IP SLA proactive threshold monitoring and multioperation scheduling capabilities: • You can configure an IP SLAs VCCV operation to perform proactive monitoring of PWE3 services and detection of faults in those services. see the “Related Documents” section on page 39. if the connection is lost. • For information about how to configure an IP SLAs VCCV operation using the LSP Health Monitor. Individual IP SLAs LSP ping and LSP traceroute operations can also be manually configured. For more information. Note The LSP discovery option does not support IP SLAs traceroute operations.IP SLAs—LSP Health Monitor with LSP Discovery Information About the LSP Health Monitor IP SLAs LSP Ping and LSP Traceroute Operations This feature introduces support for the IP SLAs LSP ping and IP SLAs LSP traceroute operations. For more information on how to configure IP SLAs operations using the LSP Health Monitor. RTT data is available to be reported as statistics. Note The LSP discovery option does not support the IP SLAs VCCV operation. IP SLAs LSP ping and LSP traceroute operations are automatically created to measure network connectivity between the source PE router and the discovered destination PE routers. which checks MPLS LSP connectivity across an Any Transport over MPLS (AToM) virtual circuit (VC) by sending a series of pseudo-wire ping operations to the specified destination PE router. or if a command response timeout occurs. These operations are useful for troubleshooting network connectivity issues and determining network availability in an MPLS VPN. see the “Configuring the LSP Health Monitor Without LSP Discovery” section on page 12 and the “Configuring the LSP Health Monitor with LSP Discovery” section on page 17. see the “Proactive Threshold Monitoring for the LSP Health Monitor” section on page 10. When using the LSP Health Monitor. An IP SLAs VCCV operation can send out a Simple Network Management Protocol (SNMP) trap if round-trip time (RTT) thresholds are violated. see the “Multioperation Scheduling for the LSP Health Monitor” section on page 11. see the “Manually Configuring an IP SLAs LSP Ping or LSP Traceroute Operation” section on page 21. Through the use of the ip sla schedule command. respectively. 9 . IP SLAs VCCV Operation The IP SLAs VCCV operation supports Virtual Circuit Connectivity Verification (VCCV) for Pseudo-Wire Emulation Edge-to-Edge (PWE3) services across MPLS networks. When MPLS LSP connectivity checking is performed through an IP SLAs VCCV operation (rather than through the ping mpls command with the pseudowire keyword). For more information. for sending and receiving echo reply and request packets to test LSPs. In addition. For more information on how to manually configure an individual IP SLAs LSP ping or LSP traceroute operation. see the “Manually Configuring an IP SLAs VCCV Operation” section on page 25 and the “Manually Configuring an IP SLAs VCCV Operation: Example” section on page 38. Manual configuration of these operations can be useful for troubleshooting a connectivity issue. The IP SLAs LSP ping and IP SLAs LSP traceroute operations are based on the same infrastructure used by the MPLS LSP Ping and MPLS LSP Traceroute features. For more information about the MPLS LSP Ping and MPLS LSP Traceroute management tools.

Broken—Indicates that the LSP is broken. 10 . all paths in the group are Broken or Unexplorable. This may be due to a disruption along the LSP or because the number of 127/8 IP addresses used for LSP selection has been exhausted. Operational status of an LSP discovery group changes. then the group status changes to DOWN. For more information about proactive threshold monitoring for Cisco IOS IP SLAs. Depending on the value of the return code and the current status of the LSP discovery group. Table 1 Conditions for Which an LSP Discovery Group Status Changes Individual IP SLAs Operation Current Group Return Code Status = UP OK No group status change. the group status can change.IP SLAs—LSP Health Monitor with LSP Discovery Information About the LSP Health Monitor Proactive Threshold Monitoring for the LSP Health Monitor Proactive threshold monitoring support for the LSP Health Monitor feature provides the capability for triggering SNMP trap notifications and syslog messages when user-defined reaction conditions (such as a connection loss or timeout) are met. a return code is generated. Possible reasons for which LSP discovery can fail for a particular BGP next hop neighbor are as follows: • • Table 1 describes the conditions for which the operational status of an LSP discovery group can change. If return codes for No group status change. Configuring threshold monitoring for an LSP Health Monitor operation is similar to configuring threshold monitoring for a standard IP SLAs operation. Return code is “Broken” or “Unexplorable” for all paths leading to the BGP next hop neighbor. SNMP trap notifications can be generated when one of the following events occurs: • • LSP discovery for a particular BGP next hop neighbor fails. then PARTIAL. LSP Discovery Option Enabled If the LSP discovery option for an LSP Health Monitor operation is enabled. Unexplorable—Indicates that not all the paths to this PE neighbor have been discovered. The return code for an individual IP SLAs LSP ping operation can be one of the following: • • • OK—Indicates that the LSP is working properly. Expiration of time allowed for a BGP next hop neighbor to respond to an LSP discovery request. see the “Related Documents” section on page 39. Whenever an individual IP SLAs LSP ping operation of an LSP discovery group is executed. Customer VPN traffic will not be sent across this path and may be discarded. The customer VPN traffic will be sent across this path. Current Group Status = PARTIAL Current Group Status = DOWN If return codes for Group status changes to all paths in the group are OK. the group status changes to UP. Broken or Unexplorable Group status changes to PARTIAL.

an SNMP trap and syslog message can be sent and the measurement frequency will return to its original frequency value. Multioperation Scheduling for the LSP Health Monitor Multioperation scheduling support for the LSP Health Monitor feature provides the capability to easily schedule the automatically created IP SLAs operations (for a given LSP Health Monitor operation) to begin at intervals equally distributed over a specified duration of time (schedule period) and to restart at a specified frequency. the frequency at which the path is remeasured will increase to the secondary frequency value (testing at a faster rate). When the configured reaction condition is met (such as N consecutive connection losses or N consecutive timeouts). a new threshold monitoring parameter has been added that allows you to specify a secondary frequency. or DOWN. This initial condition is the same as if an LSP Health Monitor operation was performed without LSP discovery. In other words. therefore. 11 . and network connectivity to each applicable neighbor is monitored using only a single LSP. Multioperation scheduling is particularly useful in cases where the LSP Health Monitor is enabled on a source PE router that has a large number of PE neighbors and. UP—Indicates that all the paths within the group are active and no operation failures have been detected. To prevent too many operations from starting at the same time. initially. of the paths within the group. DOWN—Indicates that an operation failure has been detected for all the paths within the group. Once this initial test is complete. Specific information about the IP SLAs LSP ping operations that are created for newly discovered equal-cost paths during the succeeding iterations of the LSP discovery process are stored in the LSP discovery group database. the multioperation scheduling feature will schedule the operations to begin at random intervals uniformly distributed over the schedule period.IP SLAs—LSP Health Monitor with LSP Discovery Information About the LSP Health Monitor The status of an LSP discovery group can be one of the following: • UNKNOWN—Indicates that group status has not yet been determined and that the paths belonging to the group are in the process of being tested for the first time. PARTIAL—Indicates that an operation failure has been detected for one or more. Configuring a multioperation schedule for the LSP Health Monitor is similar to configuring a standard multioperation schedule for a group of individual IP SLAs operations. If the secondary frequency option is configured and a failure (such as a connection loss or timeout) is detected for a particular path. • • • Secondary Frequency Option With the introduction of the LSP Health Monitor feature. Note Newly created IP SLAs operations (for newly discovered BGP next hop neighbors) are added to the same schedule period as the operations that are currently running. but not all. see the “Related Documents” section on page 39. the BGP next hop neighbors are discovered. LSP Discovery Option Enabled When a multioperation schedule for an LSP Health Monitor operation with LSP discovery is started. PARTIAL. network connectivity between the source PE router and discovered destination PE router is measured across only a single path. the group status will change to UP. a large number of IP SLAs operations running at the same time. For more information about scheduling a group of standard IP SLAs operations. These newly created IP SLAs LSP ping operations will start collecting data at the next iteration of network connectivity measurements for their associated LSP discovery group.

only a single path between the source PE router and each BGP next hop neighbor is discovered. For each LSP discovery group. How to Use the LSP Health Monitor This section contains the following tasks: • • • • • Configuring the LSP Health Monitor Without LSP Discovery. page 28 (optional) Configuring the LSP Health Monitor Without LSP Discovery Perform this task to configure the operation parameters. page 12 (required) Configuring the LSP Health Monitor with LSP Discovery. 3. if three LSP discovery groups (Group 1. The LSP discovery option is disabled by default. page 17 (optional) Manually Configuring an IP SLAs LSP Ping or LSP Traceroute Operation. and scheduling options for an LSP Health Monitor operation without LSP discovery. only one LSP ping operation runs at a time. The schedule period should be set to a relatively large value for large MPLS VPNs. If the LSP discovery option is disabled. Prerequisites The LSP Health Monitor must be configured on a PE router. 5. and the first LSP ping operation of Group 3 will start at 40 seconds. 2. SUMMARY STEPS 1. Note The LSP discovery process can potentially have a significant impact on the memory and CPU of the source PE router. enable configure terminal mpls discovery vpn next-hop mpls discovery vpn interval seconds auto ip sla mpls-lsp-monitor operation-number 12 . Careful consideration should be taken when configuring the scheduling parameters to prevent too many IP SLAs LSP ping operations from running at the same time. the first LSP ping operation of Group 1 will start at 0 seconds. Group 2. page 25 (optional) Verifying and Troubleshooting the LSP Health Monitor. reaction conditions. and Group 3) are scheduled to run over a period of 60 seconds. the first LSP ping operation of Group 2 will start at 20 seconds. For example. The IP SLAs measurement statistics are stored on the source PE router. 4. The remaining individual IP SLAs LSP ping operations for each LSP discovery group will run sequentially after completion of the first LSP ping operation.IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor The start times for the individual IP SLAs LSP ping operations for each LSP discovery group is based on the number of LSP discovery groups and the schedule period of the multioperation schedule. page 21 (optional) Manually Configuring an IP SLAs VCCV Operation.

exit 22. Example: Router# configure terminal Step 3 mpls discovery vpn next-hop (Optional) Enables the MPLS VPN BGP next hop neighbor discovery process. timeout milliseconds 20. ttl time-to-live 21. secondary-frequency {both | connection-loss | timeout} frequency 17. reply-dscp-bits dscp-value 14. Note Example: Router(config)# mpls discovery vpn next-hop This command is automatically enabled when the auto ip sla mpls-lsp-monitor command is entered. lsp-selector ip-address 13. auto ip sla mpls-lsp-monitor schedule operation-number schedule-period seconds [frequency [seconds]] [start-time {after hh:mm:ss | hh:mm[:ss] [month day | day month] | now | pending}] 24. exit DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. reply-mode {ipv4 | router-alert} 15. 13 . 9.IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor 6. tag text 18. 10. 8. force-explicit-null 11. request-data-size bytes 16. Example: Router> enable Step 2 configure terminal Enters global configuration mode. threshold milliseconds 19. type echo [ipsla-vrf-all | vrf vpn-name] or type pathEcho [ipsla-vrf-all | vrf vpn-name] access-list access-list-number scan-interval minutes delete-scan-factor factor 7. auto ip sla mpls-lsp-monitor reaction-configuration operation-number react {connectionLoss | timeout} [action-type option] [threshold-type {consecutive [occurrences] | immediate | never}] 23. exp exp-bits 12. • Enter your password if prompted.

IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor Command or Action Step 4 mpls discovery vpn interval seconds Purpose (Optional) Specifies the time interval at which routing entries that are no longer valid are removed from the BGP next hop neighbor discovery database of an MPLS VPN. Router(config)# mpls discovery vpn interval 120 Note The default interval of time that BGP neighbor statistics are updated is different for the IP SLAs LSP Health Monitor database and the BGP next hop neighbor discovery database. or Enters MPLS parameters configuration submode and allows the user to configure the parameters for an IP SLAs LSP traceroute operation using the LSP Health Monitor. Example: The default time interval is 300 seconds. auto ip sla mpls-lsp-monitor operation-number Step 5 Begins configuration for an LSP Health Monitor operation and enters auto IP SLA MPLS configuration mode. Use the mpls discovery vpn interval command to set the timer for the BGP next hop neighbor discovery database. Use the scan-interval command to set the timer for the IP SLAs LSP Health Monitor database. Step 6 type echo [ipsla-vrf-all | vrf vpn-name] or type pathEcho [ipsla-vrf-all | vrf vpn-name] Enters MPLS parameters configuration submode and allows the user to configure the parameters for an IP SLAs LSP ping operation using the LSP Health Monitor. Note Example: Router(config)# auto ip sla mpls-lsp-monitor 1 Entering this command automatically enables the mpls discovery vpn next-hop command. Example: Router(config-auto-ip-sla-mpls-params)# access-list 10 14 . Example: Router(config-auto-ip-sla-mpls)# type echo ipsla-vrf-all or Example: Router(config-auto-ip-sla-mpls)# type pathEcho ipsla-vrf-all Step 7 access-list access-list-number (Optional) Specifies the access list to apply to an LSP Health Monitor operation.

In other words. At each interval. If the scan factor is set to 0. This configuration is not recommended.0. Step 12 lsp-selector ip-address Example: Router(config-auto-ip-sla-mpls-params)# lsp-selector 127. IP SLAs operations will not be automatically deleted by the LSP Health Monitor. Step 10 force-explicit-null (Optional) Adds an explicit null label to all echo request packets of an IP SLAs operation. Note This command must be used with the scan-interval command. The default time interval is 240 minutes.0.IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor Command or Action Step 8 scan-interval minutes Purpose (Optional) Specifies the time interval (in minutes) at which the LSP Health Monitor checks the scan queue for BGP next hop neighbor updates. Use the scan-interval command to set the timer for the IP SLAs LSP Health Monitor database. Use the mpls discovery vpn interval command to set the timer for the BGP next hop neighbor discovery database.0. it deletes IP SLAs operations for BGP next hop neighbors that are no longer valid.0. (Optional) Specifies the local host IP address used to select the LSP of an IP SLAs operation. a new IP SLAs operation is automatically created for each newly discovered BGP next hop neighbor listed in the LSP Health Monitor scan queue. The default experimental field value is 0. each time the LSP Health Monitor checks the scan queue for updates. Note Example: Router(config-auto-ip-sla-mpls-params)# scan-interval 5 The default interval of time that BGP neighbor statistics are updated is different for the IP SLAs LSP Health Monitor database and the BGP next hop neighbor discovery database. The default scan factor is 1. Step 9 delete-scan-factor factor Example: Router(config-auto-ip-sla-mpls-params)# delete-scan-factor 2 (Optional) Specifies the number of times the LSP Health Monitor should check the scan queue before automatically deleting IP SLAs operations for BGP next hop neighbors that are no longer valid. Example: Router(config-auto-ip-sla-mpls-params)# force-explicit-null Step 11 exp exp-bits Example: Router(config-auto-ip-sla-mpls-params)# exp 5 (Optional) Specifies the experimental field value in the header for an echo request packet of an IP SLAs operation.0.10 15 . The default IP address is 127.

Step 20 ttl time-to-live (Optional) Specifies the maximum hop count for an echo request packet of an IP SLAs operation. The default DSCP value is 0. Note The default timeout values vary by operation type. Example: Router(config-auto-ip-sla-mpls-params)# secondary-frequency connection-loss 10 Step 17 tag text (Optional) Creates a user-specified identifier for an IP SLAs operation. Step 19 timeout milliseconds Example: Router(config-auto-ip-sla-mpls-params)# timeout 7000 (Optional) Specifies the amount of time the IP SLAs operation waits for a response from its request packet. the default is 100 bytes. For an IP SLAs LSP ping operation. Step 15 request-data-size bytes Example: Router(config-auto-ip-sla-mpls-params)# request-data-size 200 (Optional) Specifies the protocol data size for a request packet of an IP SLAs operation. The default timeout value is 5000 ms. The default reply mode is an IPv4 UDP packet. Step 16 secondary-frequency {both | connection-loss | timeout} frequency (Optional) Sets the faster measurement frequency (secondary frequency) to which an IP SLAs operation should change when a reaction condition occurs. Example: Router(config-auto-ip-sla-mpls-params)# exit 16 .IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor Command or Action Step 13 reply-dscp-bits dscp-value Purpose (Optional) Specifies the differentiated services codepoint (DSCP) value for an echo reply packet of an IP SLAs operation. Example: Router(config-auto-ip-sla-mpls-params)# reply-dscp-bits 5 Step 14 reply-mode {ipv4 | router-alert} Example: Router(config-auto-ip-sla-mpls-params)# reply-mode router-alert (Optional) Specifies the reply mode for an echo request packet of an IP SLAs operation. Example: Router(config-auto-ip-sla-mpls-params)# ttl 200 Step 21 exit Exits MPLS parameters configuration submode and returns to global configuration mode. Example: Router(config-auto-ip-sla-mpls-params)# tag testgroup Step 18 threshold milliseconds Example: Router(config-auto-ip-sla-mpls-params)# threshold 6000 (Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation.

Example: Router(config)# auto ip sla mpls-lsp-monitor reaction-configuration 1 react connectionLoss action-type trapOnly threshold-type consecutive 3 Step 23 auto ip sla mpls-lsp-monitor schedule operation-number schedule-period seconds [frequency [seconds]] [start-time {after hh:mm:ss | hh:mm[:ss] [month day | day month] | now | pending}] Configures the scheduling parameters for an LSP Health Monitor operation. Example: Router(config)# exit Troubleshooting Tips Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an individual IP SLAs LSP ping or LSP traceroute operation. Use the debug ip sla mpls-lsp-monitor command to help troubleshoot issues with an IP SLAs LSP Health Monitor operation. Configuring the LSP Health Monitor with LSP Discovery Perform this task to configure the operation parameters. only a single path between the source PE router and each BGP next hop neighbor is discovered. Example: Router(config)# auto ip sla mpls-lsp-monitor schedule 1 schedule-period 60 start-time now Step 24 exit Exits global configuration submode and returns to privileged EXEC mode. 17 . the equal-cost multipaths between the source PE router and each BGP next hop neighbor are discovered. What to Do Next To display the results of an individual IP SLAs operation use the show ip sla statistics and show ip sla statistics aggregated commands. If the LSP discovery option is enabled.IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor Command or Action Step 22 auto ip sla mpls-lsp-monitor reaction-configuration operation-number react {connectionLoss | timeout} [action-type option] [threshold-type {consecutive [occurrences] | immediate | never}] Purpose (Optional) Configures certain actions to occur based on events under the control of the LSP Health Monitor. The IP SLAs measurement statistics are stored on the source PE router. If the LSP discovery option is disabled. Prerequisites The LSP Health Monitor must be configured on a PE router. The LSP discovery option is disabled by default. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. reaction conditions. and scheduling options for an LSP Health Monitor operation with LSP discovery.

3. • Enter your password if prompted. exit DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. 4. scan-period minutes 15. Example: Router> enable Step 2 configure terminal Enters global configuration mode. timeout seconds 17. auto ip sla mpls-lsp-monitor schedule operation-number schedule-period seconds [frequency [seconds]] [start-time {after hh:mm:ss | hh:mm[:ss] [month day | day month] | now | pending}] 22. path-discover hours-of-statistics-kept hours 10. exit 19. 8. session-timeout seconds 16. auto ip sla mpls-lsp-monitor reaction-configuration operation-number react lpd {lpd-group [retry number] | tree-trace} [action-type trapOnly] 20. Example: Router# configure terminal 18 . 2. 6. force-explicit-null 11.IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor SUMMARY STEPS 1. ip sla logging traps 21. maximum-sessions number 14. exit 18. 9. enable configure terminal mpls discovery vpn next-hop mpls discovery vpn interval seconds auto ip sla mpls-lsp-monitor operation-number type echo [ipsla-vrf-all | vrf vpn-name] Configure optional parameters for the IP SLAs LSP echo operation. lsp-selector-base ip-address 13. 7. interval milliseconds 12. 5. See Steps 7 through 21 in the “Configuring the LSP Health Monitor Without LSP Discovery” section on page 12.

Router(config)# mpls discovery vpn interval 120 Note The default interval of time that BGP neighbor statistics are updated is different for the IP SLAs LSP Health Monitor database and the BGP next hop neighbor discovery database. Note Example: Router(config)# mpls discovery vpn next-hop This command is automatically enabled when the auto ip sla mpls-lsp-monitor command is entered. Example: Router(config-auto-ip-sla-mpls-lpd-params)# force-explicit-null 19 . Step 7 Configure optional parameters for the IP SLAs LSP echo operation. Step 10 force-explicit-null (Optional) Adds an explicit null label to all echo request packets of an LSP Health Monitor operation. Step 9 hours-of-statistics-kept hours Example: Router(config-auto-ip-sla-mpls-lpd-params)# hours-of-statistics-kept 1 (Optional) Sets the number of hours for which LSP discovery group statistics are maintained for an LSP Health Monitor operation. Note Example: Router(config)# auto ip sla mpls-lsp-monitor 1 Entering this command automatically enables the mpls discovery vpn next-hop command. Step 4 (Optional) Specifies the time interval at which routing entries that are no longer valid are removed from the BGP next hop neighbor discovery database of an MPLS VPN. Step 8 Example: Router(config-auto-ip-sla-mpls-params)# path-discover Enables the LSP discovery option for an IP SLAs LSP Health Monitor operation and enters LSP discovery parameters configuration submode. mpls discovery vpn interval seconds auto ip sla mpls-lsp-monitor operation-number Step 5 Begins configuration for an LSP Health Monitor operation and enters auto IP SLAs MPLS configuration mode. Step 6 type echo [ipsla-vrf-all | vrf vpn-name] Example: Router(config-auto-ip-sla-mpls)# type echo ipsla-vrf-all Enters MPLS parameters configuration mode and allows the user to configure the parameters for an IP SLAs LSP ping operation using the LSP Health Monitor.IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor Command or Action Step 3 mpls discovery vpn next-hop Purpose (Optional) Enables the MPLS VPN BGP next hop neighbor discovery process. path-discover (Optional) Configures optional parameters for an IP SLAs LSP echo operation. Example: The default time interval is 300 seconds. Use the mpls discovery vpn interval command to set the timer for the BGP next hop neighbor discovery database. Use the scan-interval command to set the timer for the IP SLAs LSP Health Monitor database. See Steps 7 through 21 in the “Configuring the LSP Health Monitor Without LSP Discovery” section on page 12.

Step 14 scan-period minutes Example: Router(config-auto-ip-sla-mpls-lpd-params)# scan-period 30 (Optional) Sets the amount of time after which the LSP discovery process can restart for an LSP Health Monitor operation.0. Example: Router(config-auto-ip-sla-mpls-lpd-params)# interval 2 Step 12 lsp-selector-base ip-address Example: Router(config-auto-ip-sla-mpls-lpd-params)# lsp-selector-base 127. Step 15 session-timeout seconds Example: Router(config-auto-ip-sla-mpls-lpd-params)# session-timeout 60 (Optional) Sets the amount of time the LSP discovery process for an LSP Health Monitor operation waits for a response to its LSP discovery request for a particular BGP next hop neighbor. Example: Router(config-auto-ip-sla-mpls-params)# exit 20 . Note Careful consideration should be used when configuring this parameter to avoid a negative impact on the router’s CPU. Note Step 16 timeout seconds Example: Router(config-auto-ip-sla-mpls-lpd-params)# timeout 4 Careful consideration should be used when configuring this parameter to avoid a negative impact on the router’s CPU. (Optional) Sets the amount of time the LSP discovery process for an LSP Health Monitor operation waits for a response to its echo request packets.IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor Command or Action Step 11 interval milliseconds Purpose (Optional) Specifies the time interval between MPLS echo requests that are sent as part of the LSP discovery process for an LSP Health Monitor operation.2 (Optional) Specifies the base IP address used to select the LSPs belonging to the LSP discovery groups of an LSP Health Monitor operation. Example: Router(config-auto-ip-sla-mpls-lpd-params)# exit Step 18 exit Exits MPLS parameters configuration mode and returns to global configuration mode. Step 13 maximum-sessions number Example: Router(config-auto-ip-sla-mpls-lpd-params)# maximum-sessions 2 (Optional) Specifies the maximum number of BGP next hop neighbors that can be concurrently undergoing LSP discovery for a single LSP Health Monitor operation. Step 17 exit Exits LSP discovery parameters configuration submode and returns to MPLS parameters configuration mode.0.

Manually Configuring an IP SLAs LSP Ping or LSP Traceroute Operation Perform this task to manually configure an IP SLAs LSP ping or LSP traceroute operation. Example: Router(config)# exit Troubleshooting Tips Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an individual IP SLAs LSP ping or LSP traceroute operation. 21 . Example: Router(config)# ip sla logging traps Step 21 auto ip sla mpls-lsp-monitor schedule operation-number schedule-period seconds [frequency [seconds]] [start-time {after hh:mm:ss | hh:mm[:ss] [month day | day month] | now | pending}] Configures the scheduling parameters for an LSP Health Monitor operation. Example: Router(config)# auto ip sla mpls-lsp-monitor schedule 1 schedule-period 60 start-time now Step 22 exit Exits global configuration submode and returns to privileged EXEC mode. What to Do Next To display the results of an individual IP SLAs operation use the show ip sla statistics and show ip sla statistics aggregated commands. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. Note The LSP traceroute operation does not support the secondary-frequency command. Use the debug ip sla mpls-lsp-monitor command to help troubleshoot issues with an IP SLAs LSP Health Monitor operation.IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor Command or Action Step 19 auto ip sla mpls-lsp-monitor reaction-configuration operation-number react lpd {lpd-group [retry number] | tree-trace} [action-type trapOnly] Purpose (Optional) Configures the proactive threshold monitoring parameters for an LSP Health Monitor operation with LSP discovery enabled. Example: Router(config)# auto ip sla mpls-lsp-monitor reaction-configuration 1 react lpd lpd-group retry 3 action-type trapOnly Step 20 ip sla logging traps (Optional) Enables the generation of SNMP system logging messages specific to IP SLAs trap notifications.

• Enter your password if prompted. 7. Example: Router> enable Step 2 configure terminal Enters global configuration mode. 6. ttl time-to-live 12. Example: Router(config)# ip sla 1 22 . 9. ip sla reaction-configuration operation-number [react monitored-element] [threshold-type {never | immediate | consecutive [consecutive-occurrences] | xofy [x-value y-value] | average [number-of-probes]}] [threshold-value upper-threshold lower-threshold] [action-type {none | trapOnly | triggerOnly | trapAndTrigger}] 14. enable configure terminal ip sla operation-number mpls lsp ping ipv4 destination-address destination-mask [force-explicit-null] [lsp-selector ip-address] [src-ip-addr source-address] [reply {dscp dscp-value | mode {ipv4 | router-alert}}] or mpls lsp trace ipv4 destination-address destination-mask [force-explicit-null] [lsp-selector ip-address] [src-ip-addr source-address] [reply {dscp dscp-value | mode {ipv4 | router-alert}}] exp exp-bits request-data-size bytes secondary-frequency {connection-loss | timeout} frequency tag text threshold milliseconds 5. exit DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. ip sla logging traps 15.IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor SUMMARY STEPS 1. ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] 16. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. 10. timeout milliseconds 11. exit 13. 2. 3. 4. 8.

255.1.255. 23 . Step 6 request-data-size bytes Example: Router(config-sla-monitor-lspPing)# request-data-size 200 Step 7 secondary-frequency {connection-loss | timeout} frequency (Optional) Sets the faster measurement frequency (secondary frequency) to which an IP SLAs operation should change when a reaction condition occurs.1 or Example: Router(config-ip-sla)# mpls lsp trace ipv4 192.1. Note Example: Router(config-sla-monitor-lspPing)# secondary-frequency connection-loss 10 The LSP traceroute operation does not support the secondary-frequency command.1 Step 5 exp exp-bits Example: Router(config-sla-monitor-lspPing)# exp 5 (Optional) Specifies the experimental field value in the header for an echo request packet of an IP SLAs operation. or Configures the IP SLAs operation as an LSP trace operation and enters LSP trace configuration mode.1.4 255.4 255. (Optional) Specifies the protocol data size for a request packet of an IP SLAs operation.1.255 lsp-selector 127.255.1. the default is 100 bytes. or mpls lsp trace ipv4 destination-address destination-mask [force-explicit-null] [lsp-selector ip-address] [src-ip-addr source-address] [reply {dscp dscp-value | mode {ipv4 | router-alert}}] Example: Router(config-ip-sla)# mpls lsp ping ipv4 192. Example: Router(config-sla-monitor-lspPing)# tag testgroup Step 9 threshold milliseconds Example: Router(config-sla-monitor-lspPing)# threshold 6000 (Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. The default experimental field value is 0.255.255 lsp-selector 127. Step 8 tag text (Optional) Creates a user-specified identifier for an IP SLAs operation.168.168. For an IP SLAs LSP ping operation.IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor Command or Action Step 4 mpls lsp ping ipv4 destination-address destination-mask [force-explicit-null] [lsp-selector ip-address] [src-ip-addr source-address] [reply {dscp dscp-value | mode {ipv4 | router-alert}}] Purpose Configures the IP SLAs operation as an LSP ping operation and enters LSP ping configuration mode.1.

IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor Command or Action Step 10 timeout milliseconds Purpose (Optional) Specifies the amount of time the IP SLAs operation waits for a response from its request packet. Example: Router(config)# exit Troubleshooting Tips Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an individual IP SLAs LSP ping or LSP traceroute operation. Example: Router(config)# ip sla reaction-configuration 1 react connectionLoss threshold-type consecutive 3 action-type traponly Step 14 ip sla logging traps (Optional) Enables the generation of SNMP system logging messages specific to IP SLAs trap notifications. Example: Router(config-sla-monitor-lspPing)# exit Step 13 ip sla reaction-configuration operation-number [react monitored-element] [threshold-type {never | immediate | consecutive [consecutive-occurrences] | xofy [x-value y-value] | average [number-of-probes]}] [threshold-value upper-threshold lower-threshold] [action-type {none | trapOnly | triggerOnly | trapAndTrigger}] (Optional) Configures certain actions to occur based on events under the control of Cisco IOS IP SLAs. Example: Router(config-sla-monitor-lspPing)# ttl 200 Step 12 exit Exits LSP ping or LSP trace configuration submode and returns to global configuration mode. The default timeout value is 5000 ms. 24 . Example: Router(config)# ip sla logging traps Step 15 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] Configures the scheduling parameters for an IP SLAs operation. Example: Router(config)# ip sla schedule 1 start-time now Step 16 exit Exits global configuration submode and returns to privileged EXEC mode. Step 11 ttl time-to-live (Optional) Specifies the maximum hop count for an echo request packet of an IP SLAs operation. Note Example: Router(config-sla-monitor-lspPing)# timeout 7000 The default timeout values vary by operation type.

7. exit 13. exit 25 .IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor What to Do Next To display the results of an individual IP SLAs operation use the show ip sla statistics and show ip sla statistics aggregated commands. ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] 16. 9. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. ip sla reaction-configuration operation-number [react monitored-element] [threshold-type {never | immediate | consecutive [consecutive-occurrences] | xofy [x-value y-value] | average [number-of-probes]}] [threshold-value upper-threshold lower-threshold] [action-type {none | trapOnly | triggerOnly | trapAndTrigger}] 14. 4. SUMMARY STEPS 1. ip sla logging traps 15. timeout milliseconds 12. threshold milliseconds 11. 8. 5. Manually Configuring an IP SLAs VCCV Operation Perform this task to manually configure an IP SLAs Virtual Circuit Connectivity Verification (VCCV) operation. 3. 2. enable configure terminal ip sla operation-number mpls lsp ping pseudowire peer-ipaddr vc-id [source-ipaddr source-ipaddr] exp exp-bits frequency seconds request-data-size bytes secondary-frequency {both | connection-loss | timeout} frequency tag text 10. 6.

Example: Router(config-ip-sla)# mpls lsp ping pseudowire 192.1. Step 6 frequency seconds Example: Router(config-sla-vccv)# frequency 120 Step 7 request-data-size bytes Example: Router(config-sla-vccv)# request-data-size 200 (Optional) Specifies the protocol data size for a request packet of an IP SLAs operation. Step 8 secondary-frequency {both | connection-loss | timeout} frequency Example: Router(config-sla-vccv)# secondary-frequency connection-loss 10 Step 9 tag text (Optional) Creates a user-specified identifier for an IP SLAs operation. • Enter your password if prompted. Example: Router(config-sla-vccv)# tag testgroup Step 10 threshold milliseconds Router(config-sla-vccv)# threshold 6000 (Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. The default value is 60 seconds.168. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuring an IP SLAs operation and enters IP SLA configuration mode. Example: Router(config)# ip sla 777 Step 4 mpls lsp ping pseudowire peer-ipaddr vc-id [source-ipaddr source-ipaddr] Configures the IP SLAs operation as an LSP pseudo-wire ping and enters VCCV configuration mode.102 Step 5 exp exp-bits Router(config-sla-vccv)# exp 5 (Optional) Specifies the experimental field value in the header for an echo request packet of an IP SLAs operation. (Optional) Sets the faster measurement frequency (secondary frequency) to which an IP SLAs operation should change when a reaction condition occurs.IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. the default is 100 bytes. Example: Router> enable Step 2 configure terminal Enters global configuration mode. For an IP SLAs LSP ping operation. (Optional) Specifies the rate at which a specified IP SLAs operation repeats. 26 .168.103 123 source-ipaddr 192.1. The default experimental field value is 0.

Example: Router(config)# ip sla schedule 777 life forever start-time now Step 16 exit Exits global configuration submode and returns to privileged EXEC mode. Example: Router(config)# exit Troubleshooting Tips Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an individual IP SLAs PWE3 service via VCCV operation. What to Do Next To display the results of an individual IP SLAs operation use the show ip sla statistics and show ip sla statistics aggregated commands. Example: Router(config)# ip sla logging traps Step 15 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] Configures the scheduling parameters for an IP SLAs operation.IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor Command or Action Step 11 timeout milliseconds Purpose (Optional) Specifies the amount of time the IP SLAs operation waits for a response from its request packet. The default timeout value is 5000 ms. Example: Router(config)# ip sla reaction-configuration 777 react connectionLoss threshold-type consecutive 3 action-type traponly Step 14 ip sla logging traps (Optional) Enables the generation of SNMP system logging messages specific to IP SLAs trap notifications. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. 27 . Step 12 exit Exits VCCV configuration mode and returns to global configuration mode. Note Example: Router(config-sla-vccv)# timeout 7000 The default timeout values vary by operation type. Example: Router(config-sla-vccv)# exit Step 13 ip sla reaction-configuration operation-number [react monitored-element] [threshold-type {never | immediate | consecutive [consecutive-occurrences] | xofy [x-value y-value] | average [number-of-probes]}] [threshold-value upper-threshold lower-threshold] [action-type {none | trapOnly | triggerOnly | trapAndTrigger}] (Optional) Configures certain actions to occur based on events under the control of Cisco IOS IP SLAs.

show mpls discovery vpn 28 . SUMMARY STEPS 1. 7. 8.IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor Verifying and Troubleshooting the LSP Health Monitor Perform this task to verify and troubleshoot the LSP Health Monitor. 6. debug ip sla error [operation-number] debug ip sla mpls-lsp-monitor [operation-number] debug ip sla trace [operation-number] show ip sla mpls-lsp-monitor collection-statistics [group-id] show ip sla mpls-lsp-monitor configuration [operation-number] show ip sla mpls-lsp-monitor lpd operational-state [group-id] show ip sla mpls-lsp-monitor neighbors show ip sla mpls-lsp-monitor scan-queue operation-number show ip sla mpls-lsp-monitor summary [operation-number [group [group-id]]] 10. 3. 4. 2. 5. show ip sla statistics aggregated [operation-number] [details] 12. show ip sla statistics [operation-number] [details] 11. 9.

Step 5 show ip sla mpls-lsp-monitor configuration [operation-number] (Optional) Displays configuration settings for LSP Health Monitor operations. Example: Router# show ip sla mpls-lsp-monitor configuration 1 Step 6 show ip sla mpls-lsp-monitor lpd operational-state [group-id] (Optional) Displays the operational status of the LSP discovery groups belonging to an LSP Health Monitor operation. (Optional) Displays information about adding or deleting BGP next hop neighbors from a particular MPLS VPN of an LSP Health Monitor operation. Note Example: Router# show ip sla mpls-lsp-monitor lpd operational-state 100001 This command is applicable only if the LSP discovery option is enabled. Note Example: Router# show ip sla mpls-lsp-monitor collection-statistics 100001 This command is applicable only if the LSP discovery option is enabled. Example: Router# debug ip sla error Step 2 debug ip sla mpls-lsp-monitor [operation-number] (Optional) Enables debugging output of LSP Health Monitor operations. Example: Router# debug ip sla mpls-lsp-monitor Step 3 debug ip sla trace [operation-number] (Optional) Enables debugging output for tracing the execution of IP SLAs operations. Step 8 show ip sla mpls-lsp-monitor scan-queue operation-number Example: Router# show ip sla mpls-lsp-monitor scan-queue 1 29 .IP SLAs—LSP Health Monitor with LSP Discovery How to Use the LSP Health Monitor DETAILED STEPS Command or Action Step 1 debug ip sla error [operation-number] Purpose (Optional) Enables debugging output of IP SLAs operation run-time errors. Example: Router# debug ip sla trace Step 4 show ip sla mpls-lsp-monitor collection-statistics [group-id] (Optional) Displays the statistics for IP SLAs operations belonging to an LSP discovery group of an LSP Health Monitor operation. Step 7 show ip sla mpls-lsp-monitor neighbors Example: Router# show ip sla mpls-lsp-monitor neighbors (Optional) Displays routing and connectivity information about MPLS VPN BGP next hop neighbors discovered by the LSP Health Monitor.

10.IP SLAs—LSP Health Monitor with LSP Discovery Configuration Examples for the LSP Health Monitor Command or Action Step 9 show ip sla mpls-lsp-monitor summary [operation-number [group [group-id]]] Purpose (Optional) Displays BGP next hop neighbor and LSP discovery group information for LSP Health Monitor operations.10. Step 12 show mpls discovery vpn (Optional) Displays routing information relating to the MPLS VPN BGP next hop neighbor discovery process. Note Example: Router# show ip sla mpls-lsp-monitor summary This command is applicable only if the LSP discovery option is enabled. page 30 Configuring and Verifying the LSP Health Monitor with LSP Discovery: Example. page 38 Configuring and Verifying the LSP Health Monitor Without LSP Discovery: Example Figure 4 illustrates a simple VPN scenario for an ISP.10.10. Note Example: Router# show ip sla statistics aggregated 100001 This command applies only to manually configured IP SLAs operations. From the perspective of router PE1. PE3 (router ID: 10. 30 . Example: Router# show mpls discovery vpn Configuration Examples for the LSP Health Monitor This section provides the following configuration examples: • • • • Configuring and Verifying the LSP Health Monitor Without LSP Discovery: Example. these VPNs are reachable remotely through BGP next hop routers PE2 (router ID: 10. Step 10 show ip sla statistics [operation-number] [details] (Optional) Displays the current operational status and statistics of all IP SLAs operations or a specified operation. page 37 Manually Configuring an IP SLAs VCCV Operation: Example. page 34 Manually Configuring an IP SLAs LSP Ping Operation: Example. and PE4 (router ID: 10.10.5). and green. Step 11 show ip sla statistics aggregated [operation-number] [details] (Optional) Displays the aggregated statistical errors and distribution information for all IP SLAs operations or a specified operation.8). This network consists of a core MPLS VPN with four PE routers belonging to three VPNs: red.10. blue. Note Example: Router# show ip sla statistics 100001 This command applies only to manually configured IP SLAs operations.7).

In this example.8 PE1 VPN blue VPN green VPN green 142356 The following example shows how to configure operation parameters. PE3.10.10. and PE4) in use by all VRFs (red. the LSP discovery option is enabled for LSP Health Monitor operation 1. and the time interval at which routing entries that are no longer valid are removed from the BGP next hop neighbor discovery database is set to 60 seconds. The secondary frequency option is enabled for both connection loss and timeout events.10. blue. The time interval at which the LSP Health Monitor checks the scan queue for BGP next hop neighbor updates is set to 1 minute. proactive threshold monitoring. Router PE1 Configuration mpls discovery vpn interval 60 mpls discovery vpn next-hop ! auto ip sla mpls-lsp-monitor 1 type echo ipsla-vrf-all timeout 1000 scan-interval 1 secondary-frequency both 10 ! auto ip sla mpls-lsp-monitor reaction-configuration 1 react connectionLoss threshold-type consecutive 3 action-type trapOnly 31 .10.5 VPN blue VPN green ISP VPN red VPN green VPN red VPN blue PE4 10.10. an SNMP trap notification is sent. Operation 1 is configured to automatically create IP SLAs LSP ping operations for all BGP next hop neighbors (PE2. Multioperation scheduling and the generation of IP SLAs SNMP system logging messages are enabled. and the secondary frequency is set to 10 seconds.7 PE2 10. As specified by the proactive threshold monitoring configuration. when three consecutive connection loss or timeout events occur. and scheduling options on router PE1 (see Figure 4) using the LSP Health Monitor.10. The BGP next hop neighbor process is enabled.IP SLAs—LSP Health Monitor with LSP Discovery Configuration Examples for the LSP Health Monitor Figure 4 Network Used for LSP Health Monitor Example VPN red VPN red VPN blue PE3 10. and green) associated with router PE1.

10.0.10.10.830 PDT Fri Aug 19 2005 echo ipsla-vrf-all 0 1000 5000 Equals schedule period 127.5/32) in use by: red.10.10. blue. green 32 . green Next hop 10. blue.8/32) in use by: red.10.10.10.10.10.10.0.IP SLAs—LSP Health Monitor with LSP Discovery Configuration Examples for the LSP Health Monitor auto ip sla mpls-lsp-monitor reaction-configuration 1 react timeout threshold-type consecutive 3 action-type trapOnly ip sla traps snmp-server enable traps rtr ! auto ip sla mpls-lsp-monitor schedule 1 schedule-period 60 start-time now The following is sample output from the show ip sla mpls-lsp-monitor configuration command for router PE1: PE1# show ip sla mpls-lsp-monitor configuration 1 Entry Number : 1 Modification time : Operation Type : Vrf Name : Tag : EXP Value : Timeout(ms) : Threshold(ms) : Frequency(sec) : LSP Selector : ScanInterval(min) : Delete Scan Factor : Operations List : Schedule Period(sec): Request size : Start Time : SNMP RowStatus : TTL value : Reply Mode : Reply Dscp Bits : Secondary Frequency : Value(sec) : Reaction Configs : Reaction : Threshold Type : Threshold Count : Action Type : Reaction : Threshold Type : Threshold Count : Action Type : *12:18:21.8 (Prefix: 10.10.7/32) in use by: red. green Next hop 10.5 (Prefix: 10. Next refresh in 46 seconds Next hop 10.7 (Prefix: 10.1 1 1 100001-100003 60 100 Start Time already passed Active 255 ipv4 Enabled on Timeout 10 connectionLoss Consecutive 3 Trap Only timeout Consecutive 3 Trap Only The following is sample output from the show mpls discovery vpn command for router PE1: PE1# show mpls discovery vpn Refresh interval set to 60 seconds. blue.

IP SLAs—LSP Health Monitor with LSP Discovery Configuration Examples for the LSP Health Monitor

The following is sample output from the show ip sla mpls-lsp-monitor neighbors command for router PE1:
PE1# show ip sla mpls-lsp-monitor neighbors IP SLA MPLS LSP Monitor BGP Next hop 10.10.10.5 ProbeID: 100001 (red, BGP Next hop 10.10.10.7 ProbeID: 100002 (red, BGP Next hop 10.10.10.8 ProbeID: 100003 (red, Database : 1 (Prefix: 10.10.10.5/32) blue, green) (Prefix: 10.10.10.7/32) blue, green) (Prefix: 10.10.10.8/32) blue, green)

OK OK OK

The following is sample output from the show ip sla mpls-lsp-monitor scan-queue 1 and debug ip sla mpls-lsp-monitor commands when IP connectivity from router PE1 to router PE4 is lost. This output shows that connection loss to each of the VPNs associated with router PE4 (red, blue, and green) was detected and that this information was added to the LSP Health Monitor scan queue. Also, since router PE4 is no longer a valid BGP next hop neighbor, the IP SLAs operation for router PE4 (Probe 10003) is being deleted.
PE1# show ip sla mpls-lsp-monitor scan-queue 1 Next scan Time after: 20 Secs Next Delete scan Time after: 20 Secs BGP Next hop 10.10.10.8 10.10.10.8 10.10.10.8 Prefix 0.0.0.0/0 0.0.0.0/0 0.0.0.0/0 vrf red blue green Add/Delete? Del(100003) Del(100003) Del(100003)

PE1# debug ip sla mpls-lsp-monitor IP SLAs *Aug 19 *Aug 19 *Aug 19 *Aug 19 *Aug 19 *Aug 19 *Aug 19 MPLSLM 19:48: 19:49: 19:56: 19:56: 19:49: 19:49: 19:49: debugging for all entries is on IP SLAs MPLSLM(1):Next hop 10.10.10.8 added in DeleteQ(1) IP SLAs MPLSLM(1):Removing vrf red from tree entry 10.10.10.8 IP SLAs MPLSLM(1):Next hop 10.10.10.8 added in DeleteQ(1) IP SLAs MPLSLM(1):Next hop 10.10.10.8 added in DeleteQ(1) IP SLAs MPLSLM(1):Removing vrf blue from tree entry 10.10.10.8 IP SLAs MPLSLM(1):Removing vrf green from tree entry 10.10.10.8 IP SLAs MPLSLM(1):Removing Probe 100003

The following is sample output from the show ip sla mpls-lsp-monitor scan-queue 1 and debug ip sla mpls-lsp-monitor commands when IP connectivity from router PE1 to router PE4 is restored. This output shows that each of the VPNs associated with router PE4 (red, blue, and green) were discovered and that this information was added to the LSP Health Monitor scan queue. Also, since router PE4 is a newly discovered BGP next hop neighbor, a new IP SLAs operation for router PE4 (Probe 100005) is being created and added to the LSP Health Monitor multioperation schedule. Even though router PE4 belongs to three VPNs, only one IP SLAs operation is being created.
PE1# show ip sla mpls-lsp-monitor scan-queue 1 Next scan Time after: 23 Secs Next Delete scan Time after: 23 Secs BGP Next hop 10.10.10.8 10.10.10.8 10.10.10.8 Prefix 10.10.10.8/32 10.10.10.8/32 10.10.10.8/32 vrf red blue green Add/Delete? Add Add Add

33

IP SLAs—LSP Health Monitor with LSP Discovery Configuration Examples for the LSP Health Monitor

PE1# debug ip sla mpls-lsp-monitor IP SLAs MPLSLM debugging for all entries is on *Aug 19 19:59: IP SLAs MPLSLM(1):Next hop 10.10.10.8 added in AddQ *Aug 19 19:59: IP SLAs MPLSLM(1):Next hop 10.10.10.8 added in AddQ *Aug 19 19:59: IP SLAs MPLSLM(1):Next hop 10.10.10.8 added in AddQ *Aug 19 19:59: IP SLAs MPLSLM(1):Adding vrf red into tree entry 10.10.10.8 *Aug 19 19:59: IP SLAs MPLSLM(1):Adding Probe 100005 *Aug 19 19:59: IP SLAs MPLSLM(1):Adding ProbeID 100005 to tree entry 10.10.10.8 (1) *Aug 19 19:59: IP SLAs MPLSLM(1):Adding vrf blue into tree entry 10.10.10.8 *Aug 19 19:59: IP SLAs MPLSLM(1):Duplicate in AddQ 10.10.10.8 *Aug 19 19:59: IP SLAs MPLSLM(1):Adding vrf green into tree entry 10.10.10.8 *Aug 19 19:59: IP SLAs MPLSLM(1):Duplicate in AddQ 10.10.10.8 *Aug 19 19:59: IP SLAs MPLSLM(1):Added Probe(s) 100005 will be scheduled after 26 secs over schedule period 60

Configuring and Verifying the LSP Health Monitor with LSP Discovery: Example
Figure 5 illustrates a simple VPN scenario for an ISP. This network consists of a core MPLS VPN with two PE routers belonging to a VPN named red. From the perspective of router PE1, there are three equal-cost multipaths available to reach router PE2.
Figure 5 Network Used for LSP Health Monitor with LSP Discovery Example

VPN red

PE1

PE2 192.168.1.11

The following example shows how to configure operation parameters, proactive threshold monitoring, and scheduling options on router PE1 (see Figure 5) using the LSP Health Monitor. In this example, the LSP discovery option is enabled for LSP Health Monitor operation 100. Operation 100 is configured to automatically create IP SLAs LSP ping operations for all equal-cost multipaths between router PE1 and router PE2. The BGP next hop neighbor process is enabled, and the time interval at which routing entries that are no longer valid are removed from the BGP next hop neighbor discovery database is set to 30 seconds. The time interval at which the LSP Health Monitor checks the scan queue for BGP next hop neighbor updates is set to 1 minute. The secondary frequency option is enabled for both connection loss

34

170316

MPLS Core

VPN red

IP SLAs—LSP Health Monitor with LSP Discovery Configuration Examples for the LSP Health Monitor

and timeout events, and the secondary frequency is set to 5 seconds. The explicit null label option for echo request packets is enabled. The LSP rediscovery time period is set to 3 minutes. As specified by the proactive threshold monitoring configuration, an SNMP trap notification will be sent when an LSP discovery group status changes occurs. Multioperation scheduling and the generation of IP SLAs SNMP system logging messages are enabled.
Router PE1 Configuration
mpls discovery vpn next-hop mpls discovery vpn interval 30 ! auto ip sla mpls-lsp-monitor 100 type echo ipsla-vrf-all scan-interval 1 secondary-frequency both 5 ! path-discover force-explicit-null scan-period 3 ! auto ip sla mpls-lsp-monitor reaction-configuration 100 react lpd-group retry 3 action-type trapOnly ! auto ip sla mpls-lsp-monitor schedule 100 schedule-period 30 start-time now ! ip sla logging traps snmp-server enable traps rtr

The following is sample output from the show ip sla mpls-lsp-monitor configuration command for router PE1:
PE1# show ip sla mpls-lsp-monitor configuration Entry Number : 100 Modification time : *21:50:16.411 GMT Tue Jun 20 2006 Operation Type : echo Vrf Name : ipsla-vrf-all Tag : EXP Value : 0 Timeout(ms) : 5000 Threshold(ms) : 50 Frequency(sec) : Equals schedule period ScanInterval(min) : 1 Delete Scan Factor : 1 Operations List : 100002 Schedule Period(sec): 30 Request size : 100 Start Time : Start Time already passed SNMP RowStatus : Active TTL value : 255 Reply Mode : ipv4 Reply Dscp Bits : Path Discover : Enable Maximum sessions : 1 Session Timeout(seconds) : 120 Base LSP Selector : 127.0.0.0 Echo Timeout(seconds) : 5 Send Interval(msec) : 0 Label Shimming Mode : force-explicit-null Number of Stats Hours : 2 Scan Period(minutes) : 3 Secondary Frequency : Enabled on Connection Loss and Timeout

35

IP SLAs—LSP Health Monitor with LSP Discovery Configuration Examples for the LSP Health Monitor

Value(sec) Reaction Configs Reaction Retry Number Action Type

: : : : :

5 Lpd Group 3 Trap Only

The following is sample output from the show mpls discovery vpn command for router PE1:
PE1# show mpls discovery vpn Refresh interval set to 30 seconds. Next refresh in 4 seconds Next hop 192.168.1.11 (Prefix: 192.168.1.11/32) in use by: red

The following is sample output from the show ip sla mpls-lsp-monitor neighbors command for router PE1:
PE1# show ip sla mpls-lsp-monitor neighbors IP SLA MPLS LSP Monitor Database : 100 BGP Next hop 192.168.1.11 (Prefix: 192.168.1.11/32) ProbeID: 100001 (red)

OK Paths: 3

The following is sample output from the show ip sla mpls-lsp-monitor lpd operational-state command for LSP discovery group 100001:
PE1# show ip sla mpls-lsp-monitor lpd operational-state Entry number: 100001 MPLSLM Entry Number: 100 Target FEC Type: LDP IPv4 prefix Target Address: 192.168.1.11 Number of Statistic Hours Kept: 2 Last time LPD Stats were reset: *21:21:18.239 GMT Tue Jun 20 2006 Traps Type: 3 Latest Path Discovery Mode: rediscovery complete Latest Path Discovery Start Time: *21:59:04.475 GMT Tue Jun 20 2006 Latest Path Discovery Return Code: OK Latest Path Discovery Completion Time(ms): 3092 Number of Paths Discovered: 3 Path Information : Path Outgoing Lsp Link Conn Adj Downstream Index Interface Selector Type Id Addr Label Stack 1 Et0/0 127.0.0.8 90 0 10.10.18.30 21 2 Et0/0 127.0.0.2 90 0 10.10.18.30 21 3 Et0/0 127.0.0.1 90 0 10.10.18.30 21

Status OK OK OK

The following is sample output from the show ip sla mpls-lsp-monitor collection-statistics command for LSP discovery group 100001:
PE1# show ip sla mpls-lsp-monitor collection-statistics Entry number: 100001 Start Time Index: *21:52:59.795 GMT Tue Jun 20 2006 Path Discovery Start Time: *22:08:04.507 GMT Tue Jun 20 2006 Target Destination IP address: 192.168.1.11 Path Discovery Status: OK Path Discovery Completion Time: 3052

36

IP SLAs—LSP Health Monitor with LSP Discovery Configuration Examples for the LSP Health Monitor

Path Discovery Minimum Paths: 3 Path Discovery Maximum Paths: 3 LSP Group Index: 100002 LSP Group Status: up Total Pass: 36 Total Timeout: 0 Total Fail: 0 Latest Probe Status: 'up,up,up' Latest Path Identifier: '127.0.0.8-Et0/0-21,127.0.0.2-Et0/0-21,127.0.0.1-Et0/0-21' Minimum RTT: 280 Maximum RTT: 324 Average RTT: 290

The following is sample output from the show ip sla mpls-lsp-monitor summary command for LSP Health Monitor operation 100:
PE1# show ip sla mpls-lsp-monitor summary 100 Index Destination Status LPD Group ID Last Operation Time MPLS LSP Monitor probe index Target IP address of the BGP next hop LPD group status Unique index to identify the LPD group Last time an operation was attempted by a particular probe in the LPD Group LPD Group ID 100001 Last Operation Time *22:20:29.471 GMT Tue Jun 20 2006

Index 100

Destination 192.168.1.11

Status up

The following is sample output from the show ip sla mpls-lsp-monitor summary command for LSP discovery group 100001:
PE1#show ip sla mpls-lsp-monitor summary 100 group 100001 Group ID Lsp-selector Last Operation status Last RTT Last Operation Time Group ID Lsp-Selector 100001 127.0.0.8 Jun 20 2006 100001 127.0.0.2 Jun 20 2006 100001 127.0.0.1 Jun 20 2006 unique number to identify a LPD group Unique 127/8 address used to identify a LPD Latest probe status Latest Round Trip Time Time when the last operation was attempted Status up up up Failures 0 0 0 Successes 55 55 55 RTT 320 376 300 Last Operation Time *22:20:29.471 GMT Tue *22:20:29.851 GMT Tue *22:20:30.531 GMT Tue

Manually Configuring an IP SLAs LSP Ping Operation: Example
The following example shows how to manually configure and schedule an IP SLAs LSP ping operation:
ip sla 1 mpls lsp ping ipv4 192.168.1.4 255.255.255.255 lsp-selector 127.1.1.1 frequency 120 secondary-frequency timeout 30 ! ip sla reaction-configuration 1 react connectionLoss threshold-type consecutive 3 action-type trapOnly ip sla reaction-configuration 1 react timeout threshold-type consecutive 3 action-type trapOnly ip sla logging traps ! ip sla schedule 1 start-time now life forever

37

IP SLAs—LSP Health Monitor with LSP Discovery Configuration Examples for the LSP Health Monitor

Manually Configuring an IP SLAs VCCV Operation: Example
The following example shows how to manually configure an IP SLAs VCCV operation in conjunction with the proactive threshold monitoring and multioperation scheduling capabilities of the LSP Health Monitor.

Note

In this example, a VC with the identifier 123 has already been established between the PE router and its peer at IP address 192.168.1.103. IP SLAs VCCV operation 777 is configured with operation parameters and reaction conditions, and it is scheduled to begin immediately and run indefinitely.
ip sla 777 mpls lsp ping pseudowire 192.168.1.103 123 exp 5 frequency 120 secondary-frequency timeout 30 tag testgroup threshold 6000 timeout 7000 exit ! ip sla reaction-configuration 777 react rtt threshold-value 6000 3000 threshold-type immediate 3 action-type traponly ip sla reaction-configuration 777 react connectionLoss threshold-type immediate action-type traponly ip sla reaction-configuration 777 react timeout threshold-type consecutive 3 action-type traponly ip sla logging traps ! ip sla schedule 777 life forever start-time now exit

RTT Thresholds

The threshold command configures 6000 milliseconds as the amount of time for a rising threshold to be declared on the monitored pseudo-wire. The first ip sla reaction-configuration command specifies that an SNMP logging trap is to be sent immediately if the round-trip time violates the upper threshold of 6000 milliseconds or the lower threshold of 3000 milliseconds.
Connection Loss

The second ip sla reaction-configuration command specifies that an SNMP logging trap is to be sent immediately if a connection loss occurs for the monitored pseudo-wire.
Response Timeout

The timeout command configures 7000 seconds as the amount of time that VCCV operation 777 waits for a response from its request packet before a timeout is declared. The secondary-frequency command specifies that, if a timeout occurs, the measurement frequency of the operation repeats is to be increased from 120 seconds (the initial measurement frequency specified using the frequency command) to a faster rate of 30 seconds. The third ip sla reaction-configuration command specifies that an SNMP logging trap is to be sent if three consecutive timeouts occur.

38

txt draft-ietf-mpls-oam-frmwk-03.com/go/mibs 39 .IP SLAs—LSP Health Monitor with LSP Discovery Additional References Additional References The following sections provide references related to the LSP Health Monitor with LSP Discovery feature.txt Title Detecting MPLS Data Plane Failures A Framework for MPLS Operations and Management (OAM) OAM Requirements for MPLS Networks MIBs MIB CISCO-RTTMON-MIB MIBs Link To locate and download MIBs for selected platforms. and feature sets. Cisco IOS feature MPLS LSP discovery management tool Configuring standard IP access lists Multioperation scheduling for Cisco IOS IP SLAs MPLS EM—MPLS LSP Multipath Tree Trace. Related Documents Related Topic Document Title MPLS LSP ping and LSP traceroute management tools MPLS LSP Ping/Traceroute for LDP/TE. Cisco IOS releases.cisco. use Cisco MIB Locator found at the following URL: http://www. Cisco white paper Cisco IOS IP SLAs Command Reference Standards Standard draft-ietf-mpls-lsp-ping-09.txt draft-ietf-mpls-oam-requirements-06. Cisco IOS feature “Creating an IP Access List and Applying It to an Interface” chapter of the Cisco IOS Security Configuration Guide “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide Proactive threshold monitoring for Cisco IOS IP SLAs “IP SLAs—Proactive Threshold Monitoring of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands Cisco IOS IP Service Level Agreements Command Line Interface. and LSP Ping for VCCV.

To receive security and technical information about your products. such as the Product Alert Tool (accessed from Field Notices). and support for existing RFCs has not been modified by this feature. you can subscribe to various services.com/en/US/docs/ios/ipsla/command/reference/sla_book. go to the Command Lookup Tool at http://tools. the Cisco Technical Services Newsletter.cisco.cisco. For information about all Cisco IOS commands.com/en/US/docs/ios/mcl/allreleasemcl/all_book. Access to most tools on the Cisco Support website requires a Cisco.html. Title — Technical Assistance Description The Cisco Support website provides extensive online resources. For information about these commands. including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. see the Cisco IOS IP SLA Command Reference at http://www.com/Support/CLILookup or to the Cisco IOS Master Commands List at http://www. and Really Simple Syndication (RSS) Feeds.cisco.html.com user ID and password.com/techsupport Command Reference The following commands are introduced or modified in the feature or features documented in this module.cisco. • • • • • • • • • • • • access-list (IP SLA) auto ip sla mpls-lsp-monitor auto ip sla mpls-lsp-monitor reaction-configuration auto ip sla mpls-lsp-monitor reset auto ip sla mpls-lsp-monitor schedule debug ip sla mpls-lsp-monitor delete-scan-factor exp (IP SLA) force-explicit-null frequency (IP SLA) history buckets-kept history distributions-of-statistics-kept 40 .IP SLAs—LSP Health Monitor with LSP Discovery Command Reference RFCs RFC No new or modified RFCs are supported by this feature. Link http://www.

IP SLAs—LSP Health Monitor with LSP Discovery Command Reference • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • history enhanced history filter history hours-of-statistics-kept history lives-kept history statistics-distribution-interval interval (LSP discovery) lsp-selector lsp-selector-base maximum-sessions mpls discovery vpn interval mpls discovery vpn next-hop mpls lsp ping ipv4 mpls lsp ping pseudowire mpls lsp trace ipv4 owner path-discover reply-dscp-bits reply-mode request-data-size scan-interval scan-period secondary-frequency session-timeout (LSP discovery) show ip sla mpls-lsp-monitor collection-statistics show ip sla mpls-lsp-monitor configuration show ip sla mpls-lsp-monitor lpd operational-state show ip sla mpls-lsp-monitor neighbors show ip sla mpls-lsp-monitor scan-queue show ip sla mpls-lsp-monitor summary show mpls discovery vpn tag (IP SLA) threshold (IP SLA) timeout (IP SLA) ttl (IP SLA) type echo (MPLS) type pathEcho (MPLS) 41 .

go to http://www. IronPort. and Access Registrar.4(6)T. Networkers. Cisco TelePresence. PIX. subsequent releases of that Cisco IOS software release train also support that feature. Cisco StadiumVision. Cisco Lumin. 12. Internet Quotient. see the command reference documentation. HomeLink. Collaboration Without Limitation. IOS. Cisco IOS XE Release 2.2(27)SBC.2(33)SRB 12. Aironet. FormShare.cisco. Spectrum Expert. LightStream. CCENT.2(33)SRB. SenderBase. Not all commands may be available in your Cisco IOS software release. CCNA.2(33)SRA. Cisco Nexus. Network Registrar. VCCV 12. CCIE. WebEx. ProConnect. Cisco IOS XE Release 2. and Welcome to the Human Network are trademarks.2(33)SB The IP SLAs VCCV operation was added to support Virtual Circuit Connectivity Verification (VCCV) for Pseudo-Wire Emulation Edge-to-Edge (PWE3) services across MPLS networks. CCDP.2(33)SB. Use Cisco Feature Navigator to find information about platform support and software image support. CCIP.com/go/cfn. Catalyst.com is not required. 12. MediaTone. Inc. Follow Me Browsing. the Cisco Systems logo. Cisco Systems. Cisco Unity.IP SLAs—LSP Health Monitor with LSP Discovery Feature Information for the LSP Health Monitor Feature Information for the LSP Health Monitor Table 2 lists the release history for this feature. For release information about a specific command. DCE. All other trademarks mentioned in this document or Website are the property of their respective owners. and the WebEx logo are registered trademarks of Cisco Systems. Unless noted otherwise. the IronPort logo. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release. CCNP. Cisco Press. iQuick Study. the iQ logo. the Cisco logo. 12. PowerPanels. Networking Academy. (0807R) 42 . StackWise. Linksys.2(28)SB. 12. Cisco IOS. CCDE. CCVP. The LSP discovery capability was added. MeetingPlace Chime Sound. To access Cisco Feature Navigator.2(31)SB2. new command-line interface (CLI) was implemented that replaces the CLI introduced in the earlier releases. GigaDrive. TransPath. the Cisco Certified Internetwork Expert logo. 12. EtherFast. iQ Expertise. An account on Cisco.1 Feature Information The IP SLAs LSP Health Monitor feature provides the capability to proactively monitor Layer 3 MPLS VPNs. feature set. CCDA. MeetingPlace. IP SLAs—LSP Health Monitor For software releases in which this feature was already introduced. Play. Cisco Eos. PCNow. Event Center. The use of the word partner does not imply a partnership relationship between Cisco and any other company. ScriptShare. MGX. EtherSwitch. Table 2 Feature Information for the LSP Health Monitor Feature Name IP SLAs—LSP Health Monitor Releases 12. CCSP. IP SLAs—LSP Health Monitor with LSP Discovery IP SLAs for MPLS Pseudo Wire (PWE3) via 12. Bringing the Meeting To You. Cisco Systems Capital. Live. SMARTnet. The Fastest Way to Increase Your Internet Quotient. and Learn and Cisco Store are service marks. Changing the Way We Work. Cisco.2(33)SRC. iPhone. and/or its affiliates in the United States and certain other countries. iQ Net Readiness Scorecard. 12. Note Table 2 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. AsyncOS.1 12. Fast Step. or platform.2(31)SB2.

and figures included in the document are shown for illustrative purposes only. command display output. 43 . All rights reserved.IP SLAs—LSP Health Monitor with LSP Discovery Feature Information for the LSP Health Monitor Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Any examples. Inc. © 2007-2008 Cisco Systems.

IP SLAs—LSP Health Monitor with LSP Discovery Feature Information for the LSP Health Monitor 44 .

Inc. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported.com/go/cfn. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module. page 6 Where to Go Next. page 6 Additional References. 2006 Last Updated: July 31. 2008 The Cisco IOS IP Service Level Agreements (SLAs) Internet Control Message Protocol (ICMP) Jitter Operation feature provides the capability to generate a stream of ICMP packets between a Cisco IOS device (source) and any other IP device (destination) to gather network performance-related statistics. page 6 Americas Headquarters: Cisco Systems. CA 95134-1706 USA © 2007 Cisco Systems. use the “Feature Information for the ICMP Jitter Operation” section on page 8. page 2 How to Configure the IP SLAs ICMP Jitter Operation. All rights reserved. Inc. An account on Cisco. jitter (interpacket delay variance).. San Jose. go to http://www. Contents • • • • • • Restrictions for the IP SLAs ICMP Jitter Operation. To access Cisco Feature Navigator. . page 2 Information About the IP SLAs ICMP Jitter Operation.com is not required. round-trip time.cisco.IP SLAs—Analyzing IP Service Levels Using the ICMP Jitter Operation First Published: August 14. The destination device can be any network device that supports ICMP such as a server or workstation. page 3 Configuration Examples for the IP SLAs ICMP Jitter Operation. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. 170 West Tasman Drive. The IP SLAs ICMP jitter operation does not require configuration of the IP SLAs Responder feature on the destination device. Available statistical measurements for the IP SLAs ICMP jitter operation include latency. and packet loss.

and round-trip) Late packets Obtaining separate measurements for the source-to-destination and destination-to-source data paths can be useful for identifying problems in your network because the paths may be different (asymmetric). Proactive threshold violation monitoring through Simple Network Management Protocol (SNMP) trap notifications and syslog messages. 2 . you should understand the following concepts: • • Benefits of the IP SLAs ICMP Jitter Operation. Calculated Planning Impairment Factor (ICPIF). page 2 Benefits of the IP SLAs ICMP Jitter Operation The IP SLAs ICMP Jitter Operation feature provides the following key benefits: • • End-to-end performance measurements between a Cisco device (source) and any other IP device (destination) using ICMP. • Information About the IP SLAs ICMP Jitter Operation To configure an IP SLAs ICMP jitter operation. destination-to-source. the IP SLAs ICMP jitter operation may provide less accurate measurements because the accuracy of the measurements provided by a non-Cisco destination device cannot be determined.IP SLAs—Analyzing IP Service Levels Using the ICMP Jitter Operation Restrictions for the IP SLAs ICMP Jitter Operation • Feature Information for the ICMP Jitter Operation. the IP SLAs ICMP jitter operation does not support Mean Opinion Score (MOS). Statistics Measured by the IP SLAs ICMP Jitter Operation The IP SLAs ICMP jitter operation supports the following statistical measurements: • • • • • • • Jitter (source-to-destination and destination-to-source) Latency (source-to-destination and destination-to-source) Round-trip time latency Packet loss Successive packet loss Out-of-sequence packets (source-to-destination. page 2 Statistics Measured by the IP SLAs ICMP Jitter Operation. or estimated transmission rating factor (R) reaction configuration capabilities. Since ICMP packets do not support voice technology. page 8 Restrictions for the IP SLAs ICMP Jitter Operation • When compared to the IP SLAs User Datagram Protocol (UDP) jitter operation.

ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] 16. 8. 9. show ip sla configuration [operation-number] 3 . 6. 4. ip sla reaction-configuration operation-number react monitored-element [action-type option] [threshold-type {average [number-of-measurements] | consecutive [occurrences] | immediate | never | xofy [x-value y-value]}] [threshold-value upper-threshold lower-threshold] 15. timeout milliseconds 11. 5.IP SLAs—Analyzing IP Service Levels Using the ICMP Jitter Operation How to Configure the IP SLAs ICMP Jitter Operation How to Configure the IP SLAs ICMP Jitter Operation This section contains the following task: • Configuring an IP SLAs ICMP Jitter Operation. tos number 12. SUMMARY STEPS 1. enable configure terminal ip sla operation-number icmp-jitter {destination-ip-address | destination-hostname} [interval milliseconds] [num-packets packet-number] [source-ip {ip-address | hostname}] frequency seconds history history-parameter owner owner-id tag text threshold milliseconds 10. 2. exit 14. page 3 Configuring an IP SLAs ICMP Jitter Operation Perform this task to configure and schedule an IP SLAs ICMP jitter operation. 3. vrf vrf-name 13. exit 17. 7.

129 interval 40 num-packets 100 source-ip 10. Example: Router(config-ip-sla)# icmp-jitter 172. Example: Router> enable Step 2 configure terminal Enters global configuration mode. Example: Router(config-ip-sla-icmpjitter)# history hours-of-statistics-kept 3 Step 7 owner owner-id (Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation.1.34 Step 5 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats.2. Example: Router(config)# ip sla 10 Step 4 icmp-jitter {destination-ip-address | destination-hostname} [interval milliseconds] [num-packets packet-number] [source-ip {ip-address | hostname}] Configures the IP SLAs operation as an ICMP jitter operation and enters IP SLAs ICMP jitter configuration mode.IP SLAs—Analyzing IP Service Levels Using the ICMP Jitter Operation How to Configure the IP SLAs ICMP Jitter Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode.1. Example: Router(config-ip-sla-icmpjitter)# frequency 30 Step 6 history history-parameter (Optional) Specifies the parameters used for gathering statistical history information for an IP SLAs operation. Example: Router(config-ip-sla-icmpjitter)# tag TelnetPollServer1 Step 9 threshold milliseconds Example: Router(config-ip-sla-icmpjitter)# threshold 10000 (Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. • Enter your password if prompted. 4 . Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. Example: Router(config-ip-sla-icmpjitter)# owner admin Step 8 tag text (Optional) Creates a user-specified identifier for an IP SLAs operation.18.

Example: Router(config)# exit Step 17 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation. Example: Router# show ip sla configuration 10 5 . Step 13 exit Example: Router(config-ip-sla-icmpjitter)# exit Step 14 ip sla reaction-configuration operation-number react monitored-element [action-type option] [threshold-type {average [number-of-measurements] | consecutive [occurrences] | immediate | never | xofy [x-value y-value]}] [threshold-value upper-threshold lower-threshold] (Optional) Configures certain actions to occur based on events under the control of Cisco IOS IP SLAs. Exits IP SLAs ICMP jitter configuration submode and returns to global configuration mode. Example: Router(config-ip-sla-icmpjitter)# timeout 10000 Step 11 tos number (Optional) Defines a type of service (ToS) byte in the IP header of an IP SLAs operation.IP SLAs—Analyzing IP Service Levels Using the ICMP Jitter Operation How to Configure the IP SLAs ICMP Jitter Operation Command or Action Step 10 timeout milliseconds Purpose (Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet. Example: Router(config-ip-sla-icmpjitter)# tos 160 Step 12 vrf vrf-name Example: Router(config-ip-sla-icmpjitter)# vrf vpn-A (Optional) Allows monitoring within Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs) using IP SLAs operations. Example: Router(config)# ip sla reaction-configuration 1 react jitterAvg threshold-value 5 2 action-type trap threshold-type immediate Step 15 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation. Example: Router(config)# ip sla schedule 10 start-time now life forever Step 16 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode.

Configuration Examples for the IP SLAs ICMP Jitter Operation This section provides the following configuration example: • Configuring an IP SLAs ICMP Jitter Operation: Example. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. Additional References The following sections provide references related to the IP SLAs ICMP Jitter Operation feature. What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics and show ip sla statistics aggregated commands.1. page 6 Configuring an IP SLAs ICMP Jitter Operation: Example The following example shows how to configure an IP SLAs ICMP jitter operation: ip sla 1 icmp-jitter 172.129 interval 40 num-packets 100 source-ip 10.1. Related Documents Related Topic IP SLAs UDP jitter operation Document Title “IP SLAs—Analyzing IP Service Levels Using the UDP Jitter Operation” chapter of the Cisco IOS IP SLAs Configuration Guide 6 .18.2. see the Cisco IOS IP SLAs Features Roadmap.IP SLAs—Analyzing IP Service Levels Using the ICMP Jitter Operation Configuration Examples for the IP SLAs ICMP Jitter Operation Troubleshooting Tips Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation.34 frequency 50 ! ip sla reaction-configuration 1 react jitterAvg threshold-value 5 2 action-type trap threshold-type immediate ! ip sla schedule 1 start-time now life forever Where to Go Next For information about other types of IP SLAs operations and IP SLAs features.

com/go/mibs RFCs RFC No new or modified RFCs are supported by this feature. technical tips. and tools. and support for existing RFCs has not been modified by this feature. use Cisco MIB Locator found at the following URL: http://www.com/techsupport The Cisco Technical Support & Documentation website contains thousands of pages of searchable technical content. Registered Cisco. and feature sets.IP SLAs—Analyzing IP Service Levels Using the ICMP Jitter Operation Additional References Related Topic Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands Document Title Cisco IOS IP Service Level Agreements Command Line Interface. MIBs MIB • • MIBs Link CISCO-RTTMON-MIB CISCO-RTTMON-ICMP-MIB To locate and download MIBs for selected platforms.cisco. Cisco white paper Cisco IOS IP SLAs Command Reference Standards Standard Title No new or modified standards are supported by this — feature.com users can log in from this page to access even more content. solutions.cisco. technologies. Title — Technical Assistance Description Link http://www. 7 . including links to products. Cisco IOS releases. and support for existing standards has not been modified by this feature.

Cisco IOS. Cisco Systems Capital. The Fastest Way to Increase Your Internet Quotient. and Learn and Cisco Store are service marks. CCDE. ScriptShare. and/or its affiliates in the United States and certain other countries. CCVP. the iQ logo. and packet loss. Play. go to http://www. DCE. For release information about a specific command. CCIE. WebEx. Cisco Systems. iQ Expertise.4(6)T Feature Information The Cisco IOS IP Service Level Agreements (SLAs) Internet Control Message Protocol (ICMP) jitter operation provides the capability to generate a stream of ICMP packets between a Cisco IOS device (source) and any other IP device (destination) to gather network performance-related statistics.IP SLAs—Analyzing IP Service Levels Using the ICMP Jitter Operation Feature Information for the ICMP Jitter Operation Feature Information for the ICMP Jitter Operation Table 1 lists the release history for this feature. Cisco StadiumVision. Bringing the Meeting To You. Aironet. Spectrum Expert. Cisco TelePresence. Changing the Way We Work. IOS. Network Registrar. CCDP. CCIP. Collaboration Without Limitation. iQuick Study. Cisco Nexus. All other trademarks mentioned in this document or Website are the property of their respective owners. and Access Registrar. Cisco Press. the Cisco Systems logo. SenderBase. Networking Academy. PCNow. Use Cisco Feature Navigator to find information about platform support and software image support. CCDA. Cisco Eos. CCNA. Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. CCNP. Unless noted otherwise. AsyncOS. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. iQ Net Readiness Scorecard. StackWise. the Cisco logo. Catalyst. MGX. IronPort. Inc. Cisco Lumin. An account on Cisco. Networkers. MediaTone. © 2007-2008 Cisco Systems.cisco. TransPath. Follow Me Browsing. Any examples. To access Cisco Feature Navigator. GigaDrive. SMARTnet. iPhone. ProConnect. Live.com is not required. All rights reserved. Table 1 Feature Information for the ICMP Jitter Operation Feature Name IP SLAs ICMP Jitter Operation Releases 12. subsequent releases of that Cisco IOS software release train also support that feature. HomeLink. Cisco Unity. feature set. and the WebEx logo are registered trademarks of Cisco Systems. MeetingPlace Chime Sound. Any use of actual IP addresses in illustrative content is unintentional and coincidental. MeetingPlace. Fast Step. CCSP. Inc. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release. Internet Quotient. and figures included in the document are shown for illustrative purposes only. Not all commands may be available in your Cisco IOS software release. EtherSwitch. CCENT. Linksys. 8 . see the command reference documentation. LightStream. jitter (interpacket delay variance). the IronPort logo. command display output. round-trip time. and Welcome to the Human Network are trademarks. FormShare. EtherFast. Event Center. Available statistical measurements for the IP SLAs ICMP jitter operation include latency. PowerPanels. The use of the word partner does not imply a partnership relationship between Cisco and any other company. PIX. the Cisco Certified Internetwork Expert logo.com/go/cfn. Cisco. or platform.

All rights reserved.. page 5 Configuration Examples for the IP SLAs RTP-Based VoIP Operation. page 8 Feature Information for the IP SLAs RTP-Based VoIP Operation. Contents • • • • • • • • Prerequisites for the IP SLAs RTP-Based VoIP Operation. Mean Opinion Score for Conversational Quality (MOS-CQ). page 10 Americas Headquarters: Cisco Systems. Inc. To access Cisco Feature Navigator. page 8 Where to Go Next. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported. San Jose.cisco. page 8 Additional References. 2006 Last Updated: July 31. 170 West Tasman Drive. Inc.IP SLAs—Analyzing VoIP Service Levels Using the RTP-Based VoIP Operation First Published: August 14. CA 95134-1706 USA © 2007 Cisco Systems. An account on Cisco. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. frame loss.com/go/cfn.com is not required. page 2 How to Configure an IP SLAs RTP-Based VoIP Operation. go to http://www. and Mean Opinion Score for Listening Quality (MOS-LQ). 2008 The IP Service Level Agreements (SLAs) Real-Time Transport Protocol (RTP)-based Voice over IP (VoIP) Operation feature provides the capability to set up and schedule a test call and use Voice gateway digital signal processors (DSPs) to gather network performance-related statistics for the call. page 2 Information About the IP SLAs RTP-Based VoIP Operation. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module. Available statistical measurements for VoIP networks include jitter. use the “Feature Information for the IP SLAs RTP-Based VoIP Operation” section on page 10. page 2 Restrictions for the IP SLAs RTP-Based VoIP Operation. .

Both the source and destination routers must be running a Cisco IOS image with the Cisco IOS IP Voice or higher grade feature package. Statistics Measured by the IP SLAs RTP-Based VoIP Operation The IP SLAs RTP-based VoIP operation provides an enhanced capability to measure voice quality using DSP-based calculations to determine MOS scores. • Information About the IP SLAs RTP-Based VoIP Operation To configure an IP SLAs RTP-based VoIP operation. the RTP data stream is looped back from the destination to the source gateway.IP SLAs—Analyzing VoIP Service Levels Using the RTP-Based VoIP Operation Prerequisites for the IP SLAs RTP-Based VoIP Operation Prerequisites for the IP SLAs RTP-Based VoIP Operation • • • • Both the source and destination routers must be running Cisco IOS Release 12. you should understand the following concepts: • • Benefits of the IP SLAs RTP-Based VoIP Operation.4(4)T or later releases. 2 . Restrictions for the IP SLAs RTP-Based VoIP Operation • • • The IP SLAs RTP-based VoIP operation gathers statistical information only from the DSP of the source router. For customer scenarios where the destination gateway does not have DSP hardware. see the “Statistics Measured by the IP SLAs RTP-Based VoIP Operation” section on page 2. For source-to-destination measurements. the RTP-based VoIP operation does not obtain statistical information from DSPs. The IP SLAs Responder must be enabled on the destination gateway. Depending on the type of DSP. The destination router need not have a network module with a DSP. statistical information is gathered only from the DSP of the source gateway. page 2 Benefits of the IP SLAs RTP-Based VoIP Operation The IP SLAs RTP-Based VoIP Operation feature provides the following key benefits: • • End-to-end performance measurements using DSPs for determining voice quality in VoIP networks. The voice port used by the IP SLAs RTP-based VoIP operation will not be available for other calls. For more information. The statistics gathered by the IP SLAs RTP-based VoIP operation will vary depending on the type of DSP module (see Table 1 and Table 2). Proactive threshold violation monitoring through Simple Network Management Protocol (SNMP) trap notifications and syslog messages. page 2 Statistics Measured by the IP SLAs RTP-Based VoIP Operation. In this case. The source router must have a network module with a c5510 or c549 DSP. the statistics measured by the IP SLAs RTP-based VoIP operation will vary.

No values are obtained from the DSP for this measurement. see International Telecommunication Union Telecommunication Standardization Sector (ITU-T) Recommendation G. This value is based on one-way transmission delay and standard default values. Packets missing in Number of missing packets. Estimated R factor (destination-to-source and source-to-destination) Estimated transmission rating factor R. a computational model for use in transmission planning). The source-to-destination value is measured by sending RTP packets to the IP SLAs Responder. These values are measured by sending RTP packets to IP SLAs Responder. No values are obtained from the DSP for this measurement. The source-to-destination value is measured by sending RTP packets to the IP SLAs Responder. Packet loss (destination-to-source and source-to-destination) Number of packets lost. One-way latency (destination-to-source and source-to-destination) Average. No values are obtained from the DSP for this measurement. MOS-CQ (destination-to-source and source-to-destination) Mean Opinion Score for Conversational Quality. No values are obtained from the DSP for this measurement. No values are obtained from the DSP to calculate the estimated transmission rating factor R. For more information about the estimated R factor. 3 . Round-trip time (RTT) Round-trip time latency for an RTP packet to travel from the source to the latency destination and back to the source.IP SLAs—Analyzing VoIP Service Levels Using the RTP-Based VoIP Operation Information About the IP SLAs RTP-Based VoIP Operation Table 1 Statistics Gathered by the RTP-Based VoIP Operation for c549 DSPs Statistics Interarrival jitter (destination-to-source and source-to-destination) Description Interarrival jitter is the mean deviation (smoothed absolute value) of the difference in packet spacing for a pair of packets. This value is obtained by conversion of the estimated R factor to Mean Opinion Score (MOS) using ITU-T Recommendation G. action The source-to-destination value is measured by sending RTP packets to the IP (source-to-destination) SLAs Responder. For more information about interarrival jitter. The source-to-destination value is measured by sending RTP packets to the IP SLAs Responder. The RTP data stream is then looped back from the destination to the source gateway. see RFC 3550 (RTP: A Transport Protocol for Real-Time Applications). and maximum latency values. minimum.107 conversion tables.107 (The E-model.

This value is obtained by conversion of the estimated R factor to Mean Opinion Score (MOS) using ITU-T Recommendation G. Packet loss (destination-to-source and source-to-destination) Number of packets lost.107 conversion tables. late packets. a computational model for use in transmission planning). action The source-to-destination value is measured by sending RTP packets to the IP (source-to-destination) SLAs Responder. see International Telecommunication Union Telecommunication Standardization Sector (ITU-T) Recommendation G. Packets missing in Number of missing packets. and maximum latency values. The source-to-destination value is measured by sending RTP packets to the IP SLAs Responder. These values are measured by sending RTP packets to IP SLAs Responder. Round-trip time (RTT) Round-trip time latency for an RTP packet to travel from the source to the latency destination and back to the source. or a jitter buffer error. minimum. No values are obtained from the DSP for this measurement. This value is based on one-way transmission delay and standard default values. MOS-LQ Mean Opinion Score for Listening Quality. The source-to-destination value is measured by sending RTP packets to the IP SLAs Responder. see RFC 1889 (RTP: A Transport Protocol for Real-Time Applications). No values are obtained from the DSP for this measurement. Frame loss Number of DSP frame loss events. One-way latency (destination-to-source and source-to-destination) Average. For more information about how to calculate the estimated R factor. The RTP data stream is then looped back from the destination to the source gateway. The source-to-destination value is measured by sending RTP packets to the IP SLAs Responder. No values are obtained from the DSP for this measurement.107 (The E-model. (destination-to-source) 4 . MOS-CQ (destination-to-source and source-to-destination) Mean Opinion Score for Conversational Quality. Estimated R factor (destination-to-source and source-to-destination) Estimated transmission rating factor R. (destination-to-source) A frame loss can occur due to such events as packet loss. No values are obtained from the DSP for this measurement. For more information on how this value is calculated.IP SLAs—Analyzing VoIP Service Levels Using the RTP-Based VoIP Operation Information About the IP SLAs RTP-Based VoIP Operation Table 2 Statistics Gathered by the RTP-Based VoIP Operation for c5510 DSPs Statistics Interarrival jitter (destination-to-source and source-to-destination) Description Interarrival jitter is the mean deviation (smoothed absolute value) of the difference in packet spacing for a pair of packets. as well as values obtained from the DSP.

4. 2. show ip sla monitor configuration [operation-number] 5 . enable configure terminal ip sla operation-number voip rtp {destination-ip-address | destination-hostname} source-ip {ip-address | hostname} source-voice-port {slot [/subunit/port:ds0-group-number]} [codec codec-type] [duration seconds] [advantage-factor value] frequency seconds history history-parameter owner text tag text threshold milliseconds 5. 10. SUMMARY STEPS 1. 6. exit 12. 3. page 5 Configuring an IP SLAs RTP-Based VoIP Operation Perform this task to configure and schedule an IP SLAs RTP-based VoIP operation. 9. ip sla reaction-configuration operation-number react monitored-element [action-type option] [threshold-type {average [number-of-measurements] | consecutive [occurrences] | immediate | never | xofy [x-value y-value]}] [threshold-value upper-threshold lower-threshold] 13.IP SLAs—Analyzing VoIP Service Levels Using the RTP-Based VoIP Operation How to Configure an IP SLAs RTP-Based VoIP Operation How to Configure an IP SLAs RTP-Based VoIP Operation This section contains the following task: • Configuring an IP SLAs RTP-Based VoIP Operation. 7. exit 15. 8. timeout milliseconds 11. ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] 14.

4 source-ip 10. Example: Router(config-ip-sla-voip-rtp)# tag testoperation 6 . (Optional) Specifies the parameters used for gathering statistical history information for an IP SLAs operation. • Enter your password if prompted.3.5.2. Step 6 history history-parameter Example: Router(config-ip-sla-voip-rtp)# history buckets-kept 25 Step 7 owner text (Optional) Configures the SNMP owner of an IP SLAs operation. Example: Router(config-ip-sla)# voip rtp 10.7 source-voice-port 1/0:1 codec g711alaw duration 30 advantage-factor 5 Step 5 frequency seconds Example: Router(config-ip-sla-voip-rtp)# frequency 90 (Optional) Sets the rate at which a specified IP SLAs operation repeats.6.IP SLAs—Analyzing VoIP Service Levels Using the RTP-Based VoIP Operation How to Configure an IP SLAs RTP-Based VoIP Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode.cisco. Example: Router(config-ip-sla-voip-rtp)# owner 10. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode.1. The default frequency value is 60 seconds.1 cwb.16.com John Doe RTP 555-1212 Step 8 tag text (Optional) Creates a user-specified identifier for an IP SLAs operation. Example: Router> enable Step 2 configure terminal Enters global configuration mode. Example: Router(config)# ip sla 1 Step 4 voip rtp {destination-ip-address | destination-hostname} source-ip {ip-address | hostname} source-voice-port {slot [/subunit/port:ds0-group-number]} [codec codec-type] [duration seconds] [advantage-factor value] Enters IP SLAs VoIP RTP configuration mode and configures the IP SLAs operation as an RTP-based VoIP operation.

Example: Router(config)# ip sla reaction-configuration 1 react frameLossDS action-type traponly threshold-type consecutive 3 Step 13 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] Specifies the scheduling parameters for an IP SLAs operation. (Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet. Example: Router(config)# exit Step 15 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation. Example: Router(config)# ip sla schedule 1 start-time now life forever Step 14 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode.IP SLAs—Analyzing VoIP Service Levels Using the RTP-Based VoIP Operation How to Configure an IP SLAs RTP-Based VoIP Operation Command or Action Step 9 threshold milliseconds Purpose (Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. Example: Router(config-ip-sla-voip-rtp)# exit Step 12 ip sla reaction-configuration operation-number react monitored-element [action-type option] [threshold-type {average [number-of-measurements] | consecutive [occurrences] | immediate | never | xofy [x-value y-value]}] [threshold-value upper-threshold lower-threshold] (Optional) Configures certain actions to occur based on events under the control of Cisco IOS IP SLAs. 7 . Example: Router(config-ip-sla-voip-rtp)# threshold 10000 Step 10 timeout milliseconds Example: Router(config-ip-sla-voip-rtp)# timeout 10000 Step 11 exit Exits IP SLAs VoIP RTP configuration submode and returns to global configuration mode. Example: Router# show ip sla configuration 10 Troubleshooting Tips Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation.

Use the show ip sla statistics aggregated command in privileged EXEC mode to display the aggregated hourly status and statistics for an IP SLAs operation. Where to Go Next For information about other types of IP SLAs operations and IP SLAs features. Additional References The following sections provide references related to the IP SLAs RTP-Based VoIP Operation feature. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable.5. page 8 Configuring an IP SLAs RTP-Based VoIP Operation: Example The following example shows how to configure an IP SLAs RTP-based VoIP operation: ip sla 1 voip rtp 10.3. Configuration Examples for the IP SLAs RTP-Based VoIP Operation This section provides the following configuration example: • Configuring an IP SLAs RTP-Based VoIP Operation: Example.IP SLAs—Analyzing VoIP Service Levels Using the RTP-Based VoIP Operation Configuration Examples for the IP SLAs RTP-Based VoIP Operation What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics and show ip sla statistics aggregated commands. 8 . see the Cisco IOS IP SLAs Features Roadmap.4 source-ip 10.6.7 source-voice-port 1/0:1 codec g711alaw duration 30 advantage-factor 5 ! ip sla reaction-configuration 1 react FrameLossDS action-type traponly threshold-type consecutive 3 ! ip sla schedule 1 start-time now life forever Use the show ip sla statistics command in privileged EXEC mode to display the current operational status and statistics for an IP SLAs operation.2.

technical tips. including links to products.com users can log in from this page to access even more content. and support for existing RFCs has not been modified by this feature. and feature sets. Cisco white paper Cisco IOS IP SLAs Command Reference Standards Standard Title No new or modified standards are supported by this — feature.cisco.com/go/mibs RFCs RFC No new or modified RFCs are supported by this feature. technologies. MIBs MIB CISCO-RTTMON-MIB MIBs Link To locate and download MIBs for selected platforms.IP SLAs—Analyzing VoIP Service Levels Using the RTP-Based VoIP Operation Additional References Related Documents Related Topic Cisco IOS IP SLAs UDP-based VoIP operations for VoIP networks Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands Document Title “IP SLAs—Analyzing VoIP Service Levels Using the UDP Jitter Operation” chapter of the Cisco IOS IP SLAs Configuration Guide Cisco IOS IP Service Level Agreements Command Line Interface. and support for existing standards has not been modified by this feature. Registered Cisco. solutions.com/techsupport The Cisco Technical Support & Documentation website contains thousands of pages of searchable technical content. and tools. Cisco IOS releases. use Cisco MIB Locator found at the following URL: http://www.cisco. Title — Technical Assistance Description Link http://www. 9 .

Cisco Systems Capital. IronPort. iPhone. the Cisco Systems logo. and packet loss between a Cisco device (source) and any other IP device (destination). CCSP. To access Cisco Feature Navigator. Cisco Press. the Cisco Certified Internetwork Expert logo. Cisco Systems. © 2007-2008 Cisco Systems. An account on Cisco. PCNow. subsequent releases of that Cisco IOS software release train also support that feature. EtherFast. and the WebEx logo are registered trademarks of Cisco Systems. command display output. and Welcome to the Human Network are trademarks. LightStream. CCNP. Collaboration Without Limitation. All rights reserved. Network Registrar. Cisco TelePresence. and/or its affiliates in the United States and certain other countries. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Note Table 3 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. IP SLAs RTP-Based VoIP Operation Enhancements 12. Inc. and Learn and Cisco Store are service marks. Cisco Eos. GigaDrive. or platform. MediaTone. Available statistical measurements for the IP SLAs ICMP jitter operation include latency. EtherSwitch.4(6)T CCDE. Changing the Way We Work. Spectrum Expert. Fast Step. All other trademarks mentioned in this document or Website are the property of their respective owners. WebEx. round-trip time. and figures included in the document are shown for illustrative purposes only.cisco. Cisco. New statistical measurement options for the source-to-destination data path were added. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Networking Academy. FormShare. SenderBase. IOS. iQ Net Readiness Scorecard. jitter (interpacket delay variance). Any examples. Linksys. CCENT. Inc.IP SLAs—Analyzing VoIP Service Levels Using the RTP-Based VoIP Operation Feature Information for the IP SLAs RTP-Based VoIP Operation Feature Information for the IP SLAs RTP-Based VoIP Operation Table 3 lists the release history for this feature. and Access Registrar. The use of the word partner does not imply a partnership relationship between Cisco and any other company. Networkers. The Fastest Way to Increase Your Internet Quotient. the IronPort logo. CCIP. iQ Expertise.com is not required. Follow Me Browsing. Cisco IOS. Play. Table 3 Feature Information for the IP SLAs RTP-Based VoIP Operation Feature Name IP SLAs RTP-Based VoIP Operation Releases 12. Cisco Lumin. Catalyst. SMARTnet. CCIE. go to http://www.com/go/cfn. For release information about a specific command. Event Center. StackWise. Cisco StadiumVision. the Cisco logo. CCDA. iQuick Study. TransPath. Use Cisco Feature Navigator to find information about platform support and software image support. Aironet. ProConnect.4(4)T Feature Information The Cisco IOS IP Service Level Agreements (SLAs) Internet Control Message Protocol (ICMP) jitter operation provides the capability to generate a stream of ICMP packets to gather network performance-related statistics. MeetingPlace. the iQ logo. CCNA. Bringing the Meeting To You. DCE. Cisco Nexus. see the command reference documentation. 10 . AsyncOS. CCDP. PIX. Unless noted otherwise. Not all commands may be available in your Cisco IOS software release. ScriptShare. CCVP. Cisco Unity. Internet Quotient. Live. HomeLink. PowerPanels. MeetingPlace Chime Sound. MGX. feature set.

To measure VoIP gatekeeper registration response time.cisco. or aggregated response time (delay) of registration attempts from a Voice over IP (VoIP) gateway to a VoIP gatekeeper device. page 10 Where to Go Next. 2006 Last Updated: July 31. 170 West Tasman Drive.323 gatekeeper (GK). page 3 Configuration Examples for the IP SLAs VoIP Gatekeeper Registration Delay Operation.com is not required. go to http://www. median. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support.IP SLAs—Analyzing VoIP Service Levels Using the Gatekeeper Registration Delay Operation First Published: August 14. . All rights reserved. 2008 This document describes how to use the Cisco IOS IP Service Level Agreements (SLAs) VoIP gatekeeper registration delay operation to determine the average. Inc. San Jose. the gatekeeper registration delay operation functions by sending a lightweight Registration Request (RRQ) from an H. Inc.. To access Cisco Feature Navigator. page 2 How to Configure the IP SLAs VoIP Gatekeeper Registration Delay Operation. Contents • • • • • Restrictions for the IP SLAs VoIP Gatekeeper Registration Delay Operation. use the “Feature Information for the IP SLAs VoIP Gatekeeper Registration Delay Operation” section on page 14. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported. page 10 Americas Headquarters: Cisco Systems.323 gateway (GW) to an H. CA 95134-1706 USA © 2007 Cisco Systems. and recording the amount of time taken to receive the Registration Confirmation (RCF) back from the gatekeeper.com/go/cfn. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module. page 2 Information About the IP SLAs VoIP Gatekeeper Registration Delay Operation. An account on Cisco.

232 is the ITU-T protocol standard used for managing and facilitating packetized voice and video over local-area networks (LANs. and H. page 2 H. page 2 Gateway-to-Gatekeeper Registration Delay Time Monitoring. and Status (RAS) protocols for call routing. IP SLAs was designed to gather information over time. see the “H.323 defines Registration. Video. see the “Glossary” section on page 13 for details on these standardized protocols. particularly intranets) and over the Internet.323 is considered an “umbrella protocol” because it defines all aspects of call transmission. or retrieved from the device by external applications using SNMP. Release 12. or average data can be viewed using the Cisco IOS command-line interface (CLI) on the device running IP SLAs. H.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fvvfax_c/index.323. from call establishment to capabilities exchange to network resource availability. you should understand the following concepts: • • H.htm ]. Gateway-to-Gatekeeper Registration Delay Time Monitoring The IP SLAs VoIP gatekeeper registration delay operation provides statistical data on the amount of time taken to register a gateway to a gatekeeper. H. and Fax Configuration Guide. For an in-depth discussion of H.2) [ http://www. page 10 Glossary.323 Applications” chapter (part of the Cisco IOS Voice.225 protocols for call setup.IP SLAs—Analyzing VoIP Service Levels Using the Gatekeeper Registration Delay Operation Restrictions for the IP SLAs VoIP Gatekeeper Registration Delay Operation • • • Additional References.323. including gatekeeper and gateway functionality.cisco. Gatekeepers. and Gateways. median. 2 . The IP SLAs VoIP Gatekeeper Registration Delay Monitoring feature focuses on the function of the call control H. Gatekeepers. page 14 Restrictions for the IP SLAs VoIP Gatekeeper Registration Delay Operation You cannot configure the IP SLAs VoIP gatekeeper registration delay operation if the gatekeeper has already been registered with the gateway.323 stack. so that statistics can be provided on key metrics often used in Service Level Agreements (SLAs). page 13 Feature Information for the IP SLAs VoIP Gatekeeper Registration Delay Operation.245 protocols for capabilities exchange. at intervals you specify. Aggregated totals. H. Admission.323 consists of several component standards. Information About the IP SLAs VoIP Gatekeeper Registration Delay Operation To configure the IP SLAs VoIP gateway registration delay operation.323. H. and Gateways H.

If the gateway is not registered. If the gateway is not registered. As a best practice. see the Cisco IOS IP SLAs Monitoring Technology Configuration Guide.IP SLAs—Analyzing VoIP Service Levels Using the Gatekeeper Registration Delay Operation How to Configure the IP SLAs VoIP Gatekeeper Registration Delay Operation Cisco IOS IP SLAs also provides notification options based on performance thresholds and reaction triggering. exit 3 . 2. Prerequisites Prior to configuring the IP SLAs VoIP gatekeeper registration delay operation. the gatekeeper must be enabled and the gateway must be preregistered. This operation will measure time from when the RRQ message is sent and when RCF message is received. enable configure terminal gateway exit interface interface-id ip address ip-address subnet-mask h323-gateway voip interface h323-gateway voip id gatekeeper-id {ipaddr ip-address [port-number] | multicast}[priority number] h323-gateway voip h323-id interface-id 10. SUMMARY STEPS 1. page 3 Configuring and Scheduling the IP SLAs VoIP Gatekeeper Registration Delay Operation. 5. 4. For further information on these functions. rather than having to manually examine data. page 6 Configuring the VoIP H. 3. perform the task described in this section. you should confirm the gatekeeper and gateway status first. A timeout may be required if a response is not received in a certain timeframe. 8. 6. select an interface and configure the gatekeeper in the gateway. How to Configure the IP SLAs VoIP Gatekeeper Registration Delay Operation This section contains the following procedures: • • Configuring the VoIP H. 7.323 Gateway.323 Gateway Check the registration status of the gateway to a gatekeeper using the show gateway command. These notification options allow for proactive monitoring in an environment where IT departments can be alerted to potential network problems. 9.

129. Example: Router# configure terminal Step 3 gateway Enables the H. Example: Router(config-if)# h323-gateway voip id zone1 ipaddr 172.29. Example: Router> enable Step 2 configure terminal Enters global configuration mode.323 gateway interface. Example: Router(config-if)# ip address 172. Example: Router(config-gateway)# exit Step 5 interface interface-id Specifies an interface and enters interface configuration mode.129.0 Step 7 h323-gateway voip interface Configures the interface as an H.29.255.255. • Enter your password if prompted.29.IP SLAs—Analyzing VoIP Service Levels Using the Gatekeeper Registration Delay Operation How to Configure the IP SLAs VoIP Gatekeeper Registration Delay Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode.28 1719 4 .129. Example: Router(config)# gateway Step 4 exit Exits gateway configuration mode and returns to global configuration mode. Example: Router(config)# interface Ethernet1/1 Step 6 ip address ip-address subnet-mask Configures the IP address of the interface.124 1719 Router(config-if)# h323-gateway voip id saagk ipaddr 172.323 VoIP gateway and enters gateway configuration mode.123 255. • Repeat as needed for multiple IDs (see example). Example: Router(config-if)# h323-gateway voip interface Step 8 h323-gateway voip id gatekeeper-id {ipaddr ip-address [port-number] | multicast} [priority number] Defines the name and location of the gatekeeper for a specific gateway.

The following example shows sample output from the show gateway command if the gateway (named GW3) is registered to a gatekeeper (named slagk): Router# show gateway H. Example: Router(config-if)# exit Examples Use the show gateway command to verify the registration status of the gateway to a gatekeeper. The following example shows the common output of this command if an endpoint is registered: Router# show gatekeeper endpoint GATEKEEPER ENDPOINT REGISTRATION ================================ CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags 5 .323 service is up Gateway GW3 is registered to Gatekeeper slagk Alias list (CLI configured) E164-ID 2073418 E164-ID 5251212 H323-ID GW3 Alias list (last RCF) E164-ID 2073418 E164-ID 5251212 H323-ID GW3 H323 resource thresholding is Disabled The following example shows sample output for the show gateway command if the gateway is not registered to a gatekeeper: Router# show gateway Gateway gw3 is not registered to any gatekeeper Alias list (CLI configured) E164-ID 2073418 E164-ID 5251212 H323-ID gw3/ww Alias list (last RCF) H323 resource thresholding is Disabled Use the show gatekeeper endpoint command to verify the endpoint’s registration status to the gatekeeper.IP SLAs—Analyzing VoIP Service Levels Using the Gatekeeper Registration Delay Operation How to Configure the IP SLAs VoIP Gatekeeper Registration Delay Operation Command or Action Step 9 h323-gateway voip h323-id interface-id Purpose Configures the H.1 H. Example: Router(config-if)# h323-gateway voip h323-id GWZ Step 10 exit (Optional) Exits interface configuration mode and returns to privileged EXEC mode.0 H323 Stack Version: 0.323 ITU-T Version: 4.323 name of the gateway that identifies this gateway to its associated gatekeeper.

SUMMARY STEPS 1. see the Troubleshooting Gatekeeper Registration Issues technical assistance document for suggestions on resolving the issue.IP SLAs—Analyzing VoIP Service Levels Using the Gatekeeper Registration Delay Operation How to Configure the IP SLAs VoIP Gatekeeper Registration Delay Operation -----------------.16. http://www.0 h323-gateway voip interface h323-gateway voip id zone1 ipaddr 172. As a best practice. Configuring and Scheduling the IP SLAs VoIP Gatekeeper Registration Delay Operation Perform this task to begin gathering IP SLAs VoIP gatekeeper registration delay data.13. If the gateway is not registered. the gatekeeper must be enabled and the gateway must be preregistered.28 1719 h323-gateway voip h323-id GWZ Troubleshooting Tips If there appears to be registration issues.29.16.---------------Total number of active registrations = 0 Zone Name --------- Type ---- Flags ----- The following configuration example shows a properly configured gateway: gateway interface Ethernet1/1 ip address 172.129. Prerequisites Prior to configuring the IP SLAs VoIP gatekeeper registration delay operation.124 1719 h323-gateway voip id saagk ipaddr 172. enable 6 .129.cisco.com/warp/public/788/voip/gk-reg-issues. you should confirm the gatekeeper and gateway status first.129.255.35 50890 E164-ID: 2073418 E164-ID: 5251212 H323-ID: gw3 Total number of active registrations = 1 --------gk -------VOIP-GW The following example shows the common output of the show gatekeeper endpoint command if an endpoint is not registered: Router# show gatekeeper endpoint GATEKEEPER ENDPOINT REGISTRATION ================================ CallSignalAddr Port RASSignalAddr Port -----------------.123 255.---------------172.255.35 1720 172.29.13.html What to Do Next Configure and schedule the IP SLAs VoIP gatekeeper registration delay operation. select an interface and configure the gatekeeper in the gateway.29.

exit 19.IP SLAs—Analyzing VoIP Service Levels Using the Gatekeeper Registration Delay Operation How to Configure the IP SLAs VoIP Gatekeeper Registration Delay Operation 2. 4. owner owner-id 13. history statistics-distribution-interval milliseconds 14. 3. history lives-kept lives 12. 8. 5. configure terminal ip sla operation-number voip delay gatekeeper-registration history buckets-kept size history distributions-of-statistics-kept size history enhanced [interval seconds] [buckets number-of-buckets] history filter {none | all | overThreshold | failures} frequency seconds 10. 6. exit 21. history hours-of-statistics-kept hours 11. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. tag text 15. threshold milliseconds 16. Example: Router> enable Step 2 configure terminal Enters global configuration mode. 9. • Enter your password if prompted. 7. timeout milliseconds 17. Example: Router(config)# ip sla 10 7 . ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] 20. show ip sla configuration [operation-number] DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. verify-data 18.

Example: Router(config-ip-sla-voip)# history hours-of-statistics-kept 4 Step 11 history lives-kept lives (Optional) Sets the number of lives maintained in the history table for an IP SLAs operation. Example: Router(config-ip-sla-voip)# history buckets-kept 25 Step 6 history distributions-of-statistics-kept size (Optional) Sets the number of statistics distributions kept per hop during an IP SLAs operation. Example: Router(config-ip-sla-voip)# frequency 30 Step 10 history hours-of-statistics-kept hours (Optional) Sets the number of hours for which statistics are maintained for an IP SLAs operation. the following error message will be displayed: No gatekeeper has been registered! Step 5 history buckets-kept size (Optional) Sets the number of history buckets that are kept during the lifetime of an IP SLAs operation.IP SLAs—Analyzing VoIP Service Levels Using the Gatekeeper Registration Delay Operation How to Configure the IP SLAs VoIP Gatekeeper Registration Delay Operation Command or Action Step 4 voip delay gatekeeper-registration Purpose Configures the IP SLAs operation as a VoIP gatekeeper registration delay operation and enters IP SLA VoIP configuration mode. Example: Router(config-ip-sla-voip)# history lives-kept 5 8 . Example: Router(config-ip-sla-voip)# history filter failures Step 9 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats. • Example: Router(config-ip-sla)# voip delay gatekeeper-registration If the gatekeeper has not been registered with the gateway prior to entering this command. Example: Router(config-ip-sla-voip)# history enhanced interval 900 buckets 100 Step 8 history filter {none | all | overThreshold | failures} (Optional) Defines the type of information kept in the history table for an IP SLAs operation. Example: Router(config-ip-sla-voip)# history distributions-of-statistics-kept 5 Step 7 history enhanced [interval seconds] [buckets number-of-buckets] (Optional) Enables enhanced history gathering for an IP SLAs operation.

Example: Router(config-ip-sla-voip)# tag TelnetPollServer1 Step 15 threshold milliseconds Example: Router(config-ip-sla-voip)# threshold 10000 (Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. Step 20 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode. Example: Router(config-ip-sla-voip)# owner admin Step 13 history statistics-distribution-interval milliseconds (Optional) Sets the time interval for each statistics distribution kept for an IP SLAs operation.IP SLAs—Analyzing VoIP Service Levels Using the Gatekeeper Registration Delay Operation How to Configure the IP SLAs VoIP Gatekeeper Registration Delay Operation Command or Action Step 12 owner owner-id Purpose (Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation. Example: Router# show ip sla configuration 10 9 . (Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet. Example: Router(config-ip-sla-voip)# history statistics-distribution-interval 10 Step 14 tag text (Optional) Creates a user-specified identifier for an IP SLAs operation. Example: Router(config)# exit Step 21 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation. Example: Router(config-ip-sla-voip)# verify-data Step 18 exit Exits VoIP configuration submode and returns to global configuration mode. Step 16 timeout milliseconds Example: Router(config-ip-sla-voip)# timeout 10000 Step 17 verify-data (Optional) Causes an IP SLAs operation to check each reply packet for data corruption. Example: Router(config-ip-sla-voip)# exit Step 19 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Router(config)# ip sla schedule 5 start-time now life forever Configures the scheduling parameters for an individual IP SLAs operation.

Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. • What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. Additional References The following sections provide references related to the IP SLAs VoIP gatekeeper registration delay operation. see the Cisco IOS IP SLAs Features Roadmap. This example assumes the gateway to gatekeeper relationship has already been configured. When enabled. Use the verify-data command with caution during normal operations because it generates unnecessary overhead. add the verify-data command to the configuration of the operation (while configuring in IP SLA configuration mode) to enable data verification. each operation response is checked for corruption. Router# configure terminal Router(config)# ip sla 1 Router(config-ip-sla)# voip delay gatekeeper-registration Router(config-ip-sla-voip)# exit Router(config)# ip sla schedule 1 start-time now life forever Where to Go Next For information about other types of IP SLAs operations and IP SLAs features. 10 . Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation. page 10 Configuring the IP SLAs VoIP gatekeeper registration delay operation: Example In the following example. a VoIP gatekeeper registration delay operation is configured and scheduled to start immediately. Configuration Examples for the IP SLAs VoIP Gatekeeper Registration Delay Operation This section contains the following configuration example: • Configuring the IP SLAs VoIP gatekeeper registration delay operation: Example.IP SLAs—Analyzing VoIP Service Levels Using the Gatekeeper Registration Delay Operation Configuration Examples for the IP SLAs VoIP Gatekeeper Registration Delay Operation Troubleshooting Tips • If the IP SLAs operation is not running and generating statistics.

cisco.3 and later releases Troubleshooting gatekeeper configurations Document Title Cisco IOS IP Service Level Agreements Command Line Interface. and support for existing RFCs has not been modified by this feature.com/en/US/tech/tk1077/technologies_tech_note0 9186a008011221e.shtml Standards Standard Title No new or modified standards are supported by this — feature.cisco. Cisco white paper Cisco IOS IP SLAs Command Reference Cisco IOS Voice Configuration Library http://www. and support for existing standards has not been modified by this feature. Title — 11 .com/en/US/docs/ios/12_3/vvf_c/cisco_ios_voice _configuration_library_glossary/vcl. MIBs MIB CISCO-RTTMON-MIB MIBs Link To locate and download MIBs for selected platforms. and feature sets.IP SLAs—Analyzing VoIP Service Levels Using the Gatekeeper Registration Delay Operation Additional References Related Documents Related Topic Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands Gateway and gatekeeper configuration using Cisco IOS Release 12.htm Troubleshooting Gatekeeper Registration Issues (Tech Note document) http://www. Cisco IOS releases. use Cisco MIB Locator found at the following URL: http://www.com/go/mibs RFCs RFC No new or modified RFCs are supported by this feature.cisco.

12 . solutions.com users can log in from this page to access even more content.IP SLAs—Analyzing VoIP Service Levels Using the Gatekeeper Registration Delay Operation Additional References Technical Assistance Description Link http://www.com/techsupport The Cisco Technical Support website contains thousands of pages of searchable technical content.cisco. Registered Cisco. and tools. technical tips. including links to products. technologies.

323 endpoints are defined in RAS. H. video conferencing.0 Registration/Admission/Status.323 calls.323—An ITU protocol standard for the transmission of real-time audio (Voice/VoIP). Internet packet exchange-based local-area networks (LANs).323 gateways (endpoints) and H.931. and security policies. call control and routing services to H.323 protocols (Q.SECURE.931. H. Such networks include IP-based (including the Internet) networks.323 calls. H. H. H.225.323 defines a distributed architecture for IP telephony applications. enterprise networks and metropolitan and wide-area networks (WANs).320 ISDN) and packet-based networks (for example. Sometimes used to refer to all IP telephony applications.225. Streams). including multimedia. H. and VoIP.225. H. These services provided by the gatekeeper in communicating between H.245—Protocol standard that defines connection management and negotiation capabilities between H. videoconferencing).235—Protocol standard that defines security solutions for H.323 endpoints. Note See Internetworking Terms and Acronyms for terms not included in this glossary. 13 .323 gatekeepers. codecs. and data information over packet switching-based networks. H.323 LANs). system management. H.323-based voice and video communications across networks.931—Protocol standard that defines the establishment and disconnection of H.323 devices on the network once the call is established by Q.245. and protocols to communicate. Gateways—Network devices that provide translation between circuit-switched networks (particularly. RAS.0 RAS—H. video (for example. allowing endpoints in networks with different transmission formats. Standard that facilitates communication between H. Q. H.0—Protocol standard that defines the establishment and disconnection of H.IP SLAs—Analyzing VoIP Service Levels Using the Gatekeeper Registration Delay Operation Glossary Glossary Gatekeepers—Network devices that help to facilitate and control H. video over the Internet. VoIP—Voice or Video over Internet Protocol.235 was formerly called H. Gatekeepers are responsible for providing address translation between LAN aliases and IP addresses.323 can also be applied to multipoint multimedia communications. H. RTP/RTCP—Real-time Protocol/Real-Time Control Protocol serves as the standardized means for transmitting and receiving audio and video streams across the network once the call is established.

CCNA. CCVP. Cisco StadiumVision. Networkers. FormShare. The Fastest Way to Increase Your Internet Quotient. Inc. and Welcome to the Human Network are trademarks. the Cisco Certified Internetwork Expert logo. the iQ logo. Cisco Systems. Cisco Systems Capital. Cisco Press. Unless noted otherwise. PIX. Changing the Way We Work. CCIE.3(14)T Feature Information The Cisco IOS IP SLAs Voice over IP (VoIP) gatekeeper registration delay operation allows you to measure the average. PowerPanels. Play. Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. All other trademarks mentioned in this document or Website are the property of their respective owners. CCNP. ScriptShare. AsyncOS. Cisco Nexus. Cisco. Aironet. CCDP. Not all commands may be available in your Cisco IOS software release. CCDE. see the command reference documentation. PCNow. GigaDrive. MeetingPlace Chime Sound. IOS. Any examples. Internet Quotient. Networking Academy. MeetingPlace. Fast Step. For release information about a specific command. the Cisco Systems logo.com/go/cfn. All rights reserved. CCSP. Live. and/or its affiliates in the United States and certain other countries. The use of the word partner does not imply a partnership relationship between Cisco and any other company. CCDA. SMARTnet.com is not required. feature set. StackWise. or platform. Any use of actual IP addresses in illustrative content is unintentional and coincidental. An account on Cisco. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release. command display output. Linksys. CCIP. subsequent releases of that Cisco IOS software release train also support that feature. median. Bringing the Meeting To You. iQ Expertise. Spectrum Expert. Cisco TelePresence. SenderBase. go to http://www. LightStream. IronPort. and figures included in the document are shown for illustrative purposes only. ProConnect. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. the Cisco logo. Collaboration Without Limitation. or aggregated network response time of registration attempts from a VoIP gateway to a VoIP gatekeeper device. MGX. MediaTone. WebEx. iQ Net Readiness Scorecard. Follow Me Browsing. Cisco IOS. To access Cisco Feature Navigator. Table 1 Feature Information for the IP SLAs VoIP Gatekeeper Registration Delay Operation Feature Name IP SLAs VoIP Gatekeeper Delay Monitoring Releases 12. CCENT. the IronPort logo. and Learn and Cisco Store are service marks. Use Cisco Feature Navigator to find information about platform support and software image support. Inc. © 2007-2008 Cisco Systems. HomeLink. Cisco Lumin. Cisco Eos. DCE. TransPath. Catalyst. EtherSwitch.cisco. EtherFast. and Access Registrar. Cisco Unity. iPhone. 14 . iQuick Study. and the WebEx logo are registered trademarks of Cisco Systems.IP SLAs—Analyzing VoIP Service Levels Using the Gatekeeper Registration Delay Operation Feature Information for the IP SLAs VoIP Gatekeeper Registration Delay Operation Feature Information for the IP SLAs VoIP Gatekeeper Registration Delay Operation Table 1 lists the release history for this feature. Event Center. Network Registrar.

An account on Cisco.com is not required.. All rights reserved.com/go/cfn. 2008 The Cisco IOS IP Service Level Agreements (SLAs) VoIP Call Setup (Post-Dial Delay) Monitoring feature provides the ability to measure your network’s response time for setting up a Voice over IP (VoIP) call. 2006 Last Updated: July 31. To access Cisco Feature Navigator. the IP SLAs VoIP call setup operation can measure the total time from when an originating gateway sends a call message (containing a call number) to when the originating gateway receives a message from the terminating gateway (destination) indicating that either the called number rang or the called party answered the call. Inc.323 or Session Initiation Protocol (SIP) . 170 West Tasman Drive. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. CA 95134-1706 USA © 2007 Cisco Systems. page 12 Americas Headquarters: Cisco Systems. Contents • • • • • Prerequisites for the IP SLAs VoIP Call Setup Monitoring Operation. .IP SLAs—Analyzing VoIP Service Levels Using the Call Setup Operation First Published: August 14. go to http://www. page 2 How to Configure the IP SLAs VoIP Call Setup Monitoring Operation. use the “Feature Information for the IP SLAs VoIP Call Setup Operation” section on page 14. San Jose. Inc. page 2 Information About the IP SLAs VoIP Call Setup Monitoring Operation.cisco. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module. This document describes how to use the IP SLAs VoIP call setup operation to monitor the call setup performance of your VoIP network. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported. page 3 Configuration Examples for the IP SLAs VoIP Call Setup Monitoring Operation. page 11 Where to Go Next. When using either H.

The configuration for the IP SLAs VoIP call setup operation is essentially the same for both protocols. any additional time required for messages to be sent and received (prior to sending the call message) is included in the VoIP call setup response time measurement. the IP SLAs VoIP call setup operation can measure the total time from when an originating gateway sends a call message (containing a call number) to when the originating gateway receives a message from the terminating gateway (destination) indicating that either the called number rang or the called party answered the call. To determine if your Cisco IOS software image is configured with these applications. for a specified number of repetitions.IP SLAs—Analyzing VoIP Service Levels Using the Call Setup Operation Prerequisites for the IP SLAs VoIP Call Setup Monitoring Operation • • Additional References. Note If a gatekeeper (GK) or directory gatekeeper (DGK) is involved in the H. your Cisco IOS software image must support the IP SLAs VoIP test-call application and IP SLAs VoIP Responder application. When using either H. page 12 Feature Information for the IP SLAs VoIP Call Setup Operation.323 or SIP. additional messages are sent and received between the originating and terminating gateways before the call message (containing a call number) is actually sent.323 or Session Initiation Protocol (SIP) call messages can be sent to and received by the originating and terminating gateways. page 14 Prerequisites for the IP SLAs VoIP Call Setup Monitoring Operation In order to use the IP SLAs VoIP call setup functionality. As with all Cisco IOS IP SLAs operations. With the IP SLAs VoIP test-call application enabled. use the show call application voice command in EXEC mode. you should understand the following concept: • IP SLAs VoIP Call Setup Monitoring Using H. Note The IP SLAs VoIP Responder application is different from the IP SLAs Responder (which is configured using the ip sla responder command in global configuration mode). 2 . page 2 IP SLAs VoIP Call Setup Monitoring Using H.323 or SIP. H. Likewise.323 call signaling. Information About the IP SLAs VoIP Call Setup Monitoring Operation To configure an IP SLAs VoIP call setup operation. The additional time required for these messages is included in the IP SLAs VoIP call setup response time measurement. you can configure the VoIP call setup operation to repeat at specified time intervals. if a proxy server or redirection server is involved in the SIP call signaling.323 or SIP The Cisco IOS IP SLAs VoIP Call Setup Monitoring feature provides the ability to measure your network’s response time for setting up a Voice over IP (VoIP) call. and over a specified duration of time. you must enable the IP SLAs VoIP test-call application on the originating gateway (source). Prior to configuring the IP SLAs VoIP call setup operation.

IP SLAs—Analyzing VoIP Service Levels Using the Call Setup Operation How to Configure the IP SLAs VoIP Call Setup Monitoring Operation A plain old telephone service (POTS) IP phone can be set up at the terminating gateway to respond to an IP SLAs VoIP call setup test call. your Cisco IOS software image must support the IP SLAs VoIP test-call application and IP SLAs VoIP Responder application. 4. | $d$. SUMMARY STEPS 1. Note The IP SLAs VoIP Responder application is different from the IP SLAs Responder (which is configured using the ip sla responder command in global configuration mode). enable show call application voice [name | summary] call application session start instance-name [application-name] configure terminal dial-peer voice tag voip destination-pattern [+] string [T] session target {ipv4:destination-address | dns:[$s$. The IP SLAs VoIP Responder application will respond to incoming call setup messages from the originating gateway using H. you can enable the IP SLAs VoIP Responder application in the terminating gateway. 2. define the VoIP call setup operation. As a convenient alternative to an actual IP phone. 5. page 3 Configuring the Terminating Gateway Using the IP SLAs VoIP Responder Application. set up the dial peer to route the test call. page 8 Configuring the Originating Gateway Perform this task on the originating gateway (source) in order to start the IP SLAs VoIP test-call application.323 or SIP. | $u$. The required configuration for setting up the dial peer will vary slightly depending on whether you are using H. 6. 3. Note The IP SLAs VoIP Responder application is different from the IP SLAs Responder (which is configured using the ip sla responder command in global configuration mode).] host-name | enum:table-num | loopback:rtp | ras | sip-server} 3 . | $e$. and schedule the VoIP call setup operation.323 or SIP. Prerequisites In order to use the IP SLAs VoIP call setup functionality. 7. How to Configure the IP SLAs VoIP Call Setup Monitoring Operation This section contains the following tasks: • • Configuring the Originating Gateway. To determine if your Cisco IOS software image is configured with these applications. use the show call application voice command in EXEC mode.

history buckets-kept size 13. history hours-of-statistics-kept hours 18. frequency seconds 17. owner owner-id 20. tag text 22. 9. exit 25. history enhanced [interval seconds] [buckets number-of-buckets] 15. threshold milliseconds 23. history lives-kept lives 19. timeout milliseconds 24. exit 27. show ip sla configuration [operation-number] 4 . history filter {none | all | overThreshold | failures} 16. history statistics-distribution-interval milliseconds 21. ip sla operation-number 11. session protocol sipv2 exit 10. voip delay post-dial [detect-point {alert-ringing | connect-ok}] destination tag 12. ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] 26.IP SLAs—Analyzing VoIP Service Levels Using the Call Setup Operation How to Configure the IP SLAs VoIP Call Setup Monitoring Operation 8. history distributions-of-statistics-kept size 14.

.. and enters dial-peer configuration mode. the command output displays a one-line summary about each configured voice application.164 telephone number to be used for a dial peer. the ipsla-testcall name is displayed. Example: Router(config-dial-peer)# destination-pattern 6789 5 . Example: Router# call application session start ipsla-testcall ipsla-testcall Step 4 configure terminal Enters global configuration mode. ipsla-testcall Basic app to place a simple call ipsla-responder Basic app to respond to a simple call . • Example: Router(config)# dial-peer voice 6789 voip The tag argument consists of one or more digits identifying the dial peer. • Enter your password if prompted. • Step 3 call application session start instance-name [application-name] Starts a new session of the Cisco IOS IP SLAs VoIP test-call application. • Example: Router# show call application voice summary NAME DESCRIPTION . Example: Router> enable Step 2 show call application voice [name | summary] (Optional) Displays information about configured voice applications.. • Step 6 destination-pattern [+] string [T] Specifies either the prefix or the full E. If the Cisco IOS IP SLAs VoIP test-call application is configured on the currently loaded Cisco IOS software image. Call Treatment Action Application . TCL Script Version 2.Version 1. If the summary keyword is entered. Range is from 1 to 2147483647.. The voip keyword indicates a VoIP dial peer using voice encapsulation on an IP network.IP SLAs—Analyzing VoIP Service Levels Using the Call Setup Operation How to Configure the IP SLAs VoIP Call Setup Monitoring Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. Example: Router# configure terminal Step 5 dial-peer voice tag voip Defines a particular dial peer.0 supported. specifies the method of voice encapsulation.

Example: Router(config-ip-sla-voip)# history enhanced interval 900 buckets 100 6 . Example: Router(config-ip-sla-voip)# history distributions-of-statistics-kept 5 Step 14 history enhanced [interval seconds] [buckets number-of-buckets] (Optional) Enables enhanced history gathering for an IP SLAs operation. Step 12 history buckets-kept size (Optional) Sets the number of history buckets that are kept during the lifetime of an IP SLAs operation.129.IP SLAs—Analyzing VoIP Service Levels Using the Call Setup Operation How to Configure the IP SLAs VoIP Call Setup Monitoring Operation Command or Action Step 7 session target {ipv4:destination-address | dns:[$s$. Example: Router(config)# ip sla 10 Step 11 voip delay post-dial [detect-point {alert-ringing | connect-ok}] destination tag Example: Router(config-ip-sla)# voip delay post-dial detect-point alert-ringing destination 6789 Enters IP SLA VoIP configuration mode and configures the operation as a VoIP call setup (post-dial delay) operation that will generate VoIP call setup response time measurements. | $u$. | $d$. | $e$. Example: Router(config-dial-peer)# session target ipv4:172.29. Example: Router(config-ip-sla-voip)# history buckets-kept 25 Step 13 history distributions-of-statistics-kept size (Optional) Sets the number of statistics distributions kept per hop during an IP SLAs operation. Note Example: Router(config-dial-peer)# session protocol sipv2 Perform this step only if configuring a SIP call.123 Step 8 session protocol sipv2 (Optional) Specifies SIP as the session protocol for the VoIP dial peer.] host-name | enum:table-num | loopback:rtp | ras | sip-server} Purpose Designates a network-specific address to receive calls from a VoIP dial peer. Example: Router(config-dial-peer)# exit Step 10 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. Step 9 exit Exits dial-peer configuration mode and returns to global configuration mode.

Example: Router(config-ip-sla-voip)# history statistics-distribution-interval 10 Step 21 tag text (Optional) Creates a user-specified identifier for an IP SLAs operation. Step 23 timeout milliseconds Example: Router(config-ip-sla-voip)# timeout 10000 7 . Example: Router(config-ip-sla-voip)# history hours-of-statistics-kept 4 Step 18 history lives-kept lives (Optional) Sets the number of lives maintained in the history table for an IP SLAs operation. Example: Router(config-ip-sla-voip)# tag TelnetPollServer1 Step 22 threshold milliseconds Example: Router(config-ip-sla-voip)# threshold 10000 (Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. Example: Router(config-ip-sla-voip)# history lives-kept 5 Step 19 owner owner-id (Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation. (Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet. Example: Router(config-ip-sla-voip)# frequency 30 Step 17 history hours-of-statistics-kept hours (Optional) Sets the number of hours for which statistics are maintained for an IP SLAs operation. Example: Router(config-ip-sla-voip)# history filter failures Step 16 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats.IP SLAs—Analyzing VoIP Service Levels Using the Call Setup Operation How to Configure the IP SLAs VoIP Call Setup Monitoring Operation Command or Action Step 15 history filter {none | all | overThreshold | failures} Purpose (Optional) Defines the type of information kept in the history table for an IP SLAs operation. Example: Router(config-ip-sla-voip)# owner admin Step 20 history statistics-distribution-interval milliseconds (Optional) Sets the time interval for each statistics distribution kept for an IP SLAs operation.

Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. 8 . your Cisco IOS software image must support the IP SLAs VoIP test-call application and IP SLAs VoIP Responder application.IP SLAs—Analyzing VoIP Service Levels Using the Call Setup Operation How to Configure the IP SLAs VoIP Call Setup Monitoring Operation Command or Action Step 24 exit Purpose Exits VoIP configuration submode and returns to global configuration mode. Example: Router(config)# exit Step 27 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation. Step 26 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode. Example: Router(config-ip-sla-voip)# exit Step 25 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Router(config)# ip sla schedule 5 start-time now life forever Configures the scheduling parameters for an individual IP SLAs operation.323 or SIP. Prerequisites In order to use the IP SLAs VoIP call setup functionality. To determine if your Cisco IOS software image is configured with these applications. Configuring the Terminating Gateway Using the IP SLAs VoIP Responder Application Perform this task on the terminating gateway (destination) in order to set up the dial peer and enable the IP SLAs VoIP Responder application to respond to the IP SLAs VoIP test call. What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. use the show call application voice command in EXEC mode. The required configuration for setting up the dial peer will vary slightly depending on whether you are using H. Example: Router# show ip sla configuration 10 Troubleshooting Tips Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation.

6. enable show call application voice [name | summary] configure terminal dial-peer voice tag voip incoming called-number tag application application-name session protocol sipv2 exit 9 . 3. 5.IP SLAs—Analyzing VoIP Service Levels Using the Call Setup Operation How to Configure the IP SLAs VoIP Call Setup Monitoring Operation Note The IP SLAs VoIP Responder application is different from the IP SLAs Responder (which is configured using the ip sla responder command in global configuration mode). SUMMARY STEPS 1. 2. 8. 7. 4.

• Example: Router# show call application voice summary NAME DESCRIPTION . TCL Script Version 2. If the Cisco IOS IP SLAs VoIP Responder application is configured on the currently loaded Cisco IOS software image. specifies the method of voice encapsulation. • Enter your password if prompted. ipsla-testcall Basic app to place a simple call ipsla-responder Basic app to respond to a simple call . Example: Router(config-dial-peer)# incoming called-number 6789 Step 6 application application-name Enables a specific application on a dial peer. 10 .. Call Treatment Action Application . • Example: Router(config)# dial-peer voice 6789 voip The tag argument consists of one or more digits identifying the dial peer. • Step 3 configure terminal Enters global configuration mode. The voip keyword indicates a VoIP dial peer using voice encapsulation on an IP network. the command output displays a one-line summary of each configured voice application.Version 1.. If the summary keyword is entered. • Example: Router(config-dial-peer)# application ipsla-responder To enable the Cisco IOS IP SLAs VoIP Responder application. the ipsla-responder name is displayed. Example: Router# configure terminal Step 4 dial-peer voice tag voip Defines a particular dial peer. Range is from 1 to 2147483647. enter ipsla-responder as the application-name argument. • Step 5 incoming called-number tag Specifies a digit string that can be matched by an incoming call to associate the call with a dial peer.. and enters dial-peer configuration mode. Example: Router> enable Step 2 show call application voice [name | summary] (Optional) Displays information about configured voice applications..IP SLAs—Analyzing VoIP Service Levels Using the Call Setup Operation How to Configure the IP SLAs VoIP Call Setup Monitoring Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode.0 supported.

page 11 Configuring the Originating Gateway: Example The following example shows how to configure an originating gateway to start the IP SLAs VoIP test-call application.123 session protocol sipv2 exit ip sla 1 voip delay post-dial detect-point alert-ringing destination 6789 exit ip sla schedule 1 start-time now life forever Configuring the Terminating Gateway: Example The following example shows how to configure a terminating gateway to set up the dial peer and enable the IP SLAs VoIP Responder application to respond to the IP SLAs VoIP call setup test call. define the VoIP call setup operation. set up the dial peer to route the test call. page 11 Configuring the Terminating Gateway: Example. Note Example: Router(config-dial-peer)# session protocol sipv2 Perform this step only if configuring a SIP call. and schedule the VoIP call setup operation. In this example.129. call application session start ipsla-testcall ipsla-testcall configure terminal dial-peer voice 6789 voip destination-pattern 6789 session target ipv4:172. test-call messages are generated using the Session Initiation Protocol (SIP). test-call messages are generated using the Session Initiation Protocol (SIP). In this example. configure terminal dial-peer voice 6789 voip incoming called-number 6789 application ipsla-responder session protocol sipv2 exit 11 .IP SLAs—Analyzing VoIP Service Levels Using the Call Setup Operation Configuration Examples for the IP SLAs VoIP Call Setup Monitoring Operation Command or Action Step 7 session protocol sipv2 Purpose (Optional) Specifies SIP as the session protocol for the VoIP dial peer. Step 8 exit Exits dial-peer configuration mode and returns to global configuration mode.29. Example: Router(config-dial-peer)# exit Configuration Examples for the IP SLAs VoIP Call Setup Monitoring Operation This section contains the following configuration examples: • • Configuring the Originating Gateway: Example.

use Cisco MIB Locator found at the following URL: http://www.cisco. Cisco IOS releases.IP SLAs—Analyzing VoIP Service Levels Using the Call Setup Operation Where to Go Next Where to Go Next For information about other types of IP SLAs operations and IP SLAs features.com/go/mibs RFCs RFC No new or modified RFCs are supported by this feature. Related Documents Related Topic Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands Document Title Cisco IOS IP Service Level Agreements Command Line Interface. and feature sets. and support for existing RFCs has not been modified by this feature. Title — 12 . and support for existing standards has not been modified by this feature. MIBs MIB CISCO-RTTMON-MIB MIBs Link To locate and download MIBs for selected platforms. Additional References The following sections provide references related to the IP SLAs VoIP Call Setup Monitoring feature. see the Cisco IOS IP SLAs Features Roadmap. Cisco white paper Cisco IOS IP SLAs Command Reference Standards Standard Title No new or modified standards are supported by this — feature.

IP SLAs—Analyzing VoIP Service Levels Using the Call Setup Operation Additional References Technical Assistance Description Link http://www.cisco. and tools. Registered Cisco.com users can log in from this page to access even more content. technologies. 13 . technical tips. solutions. including links to products.com/techsupport The Cisco Technical Support website contains thousands of pages of searchable technical content.

EtherSwitch. StackWise. © 2007-2008 Cisco Systems. iQuick Study. the Cisco Certified Internetwork Expert logo. iQ Net Readiness Scorecard. Aironet. MeetingPlace Chime Sound. Cisco StadiumVision. Cisco Systems Capital. CCNA. Internet Quotient. DCE. ScriptShare. CCDA. Any examples. the iQ logo. Fast Step. Cisco. The use of the word partner does not imply a partnership relationship between Cisco and any other company. Play. CCIP. the Cisco logo. CCENT. An account on Cisco. FormShare. Catalyst. and Access Registrar. and/or its affiliates in the United States and certain other countries. 14 . CCDE. go to http://www. All other trademarks mentioned in this document or Website are the property of their respective owners. Inc. IronPort. SenderBase. IOS. Cisco Systems. CCNP. Cisco IOS. Inc. Table 1 Feature Information for the IP SLAs VoIP Call Setup Operation Feature Name IP SLAs VoIP Call Setup (Post Dial Delay) Monitoring Releases 12. Not all commands may be available in your Cisco IOS software release. Event Center.3(14)T Feature Information The Cisco IOS IP SLAs Voice over IP (VoIP) call setup operation allows you to measure network response time for setting up a VoIP call. Cisco Eos. Unless noted otherwise. Networkers.com/go/cfn. Collaboration Without Limitation. Cisco Press. and Welcome to the Human Network are trademarks. AsyncOS. ProConnect. feature set. SMARTnet. EtherFast. LightStream. GigaDrive. the Cisco Systems logo. MediaTone.com is not required. subsequent releases of that Cisco IOS software release train also support that feature. PCNow. Bringing the Meeting To You. CCVP. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Live. see the command reference documentation. MeetingPlace. Changing the Way We Work. HomeLink. iQ Expertise. MGX.IP SLAs—Analyzing VoIP Service Levels Using the Call Setup Operation Feature Information for the IP SLAs VoIP Call Setup Operation Feature Information for the IP SLAs VoIP Call Setup Operation Table 1 lists the release history for this feature. The Fastest Way to Increase Your Internet Quotient. CCSP. and Learn and Cisco Store are service marks. iPhone. For release information about a specific command. Spectrum Expert. TransPath. Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Cisco Lumin. Linksys. Networking Academy. WebEx. All rights reserved. command display output. Network Registrar. or platform. PIX. CCIE. To access Cisco Feature Navigator. Cisco TelePresence. PowerPanels. CCDP. Follow Me Browsing. Cisco Unity. Cisco Nexus. and the WebEx logo are registered trademarks of Cisco Systems. the IronPort logo. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Use Cisco Feature Navigator to find information about platform support and software image support. and figures included in the document are shown for illustrative purposes only. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release.cisco.

Inc. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported. San Jose. to lower operational costs.. Contents • • • • Prerequisites for the IP SLAs UDP Echo Operation.cisco.IP SLAs—Analyzing IP Service Levels Using the UDP Echo Operation First Published: August 14. page 2 How to Configure the IP SLAs UDP Echo Operation. To access Cisco Feature Navigator. This module also demonstrates how the results of the UDP echo operation can be displayed and analyzed to determine how a UDP application is performing. . 170 West Tasman Drive. CA 95134-1706 USA © 2006-2008 Cisco Systems. UDP echo accuracy is enhanced by using the IP SLAs Responder at the destination Cisco router. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. and to reduce the frequency of network outages.com/go/cfn.com is not required. page 2 Restrictions for the IP SLAs UDP Echo Operation. IP SLAs is a portfolio of technology embedded in most devices that run Cisco IOS software. 2006 Last Updated: July 16. which allows Cisco customers to analyze IP service levels for IP applications and services. and predictable manner—for measuring network performance. 2008 This module describes how to use the Cisco IOS IP Service Level Agreements (SLAs) User Datagram Protocol (UDP) Echo operation to monitor end-to-end response time between a Cisco router and devices using IPv4 or IPv6. go to http://www. use the “Feature Information for the IP SLAs UDP Echo Operation” section on page 14. IP SLAs uses active traffic monitoring—the generation of traffic in a continuous. page 3 Americas Headquarters: Cisco Systems. page 2 Information About the IP SLAs UDP Echo Operation. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module. An account on Cisco. reliable. All rights reserved. Inc. to increase productivity.

UDP echo is used to measure response times and test end-to-end connectivity. can be used. page 2 UDP Echo Operation The UDP echo operation measures end-to-end response time between a Cisco router and devices using IP. page 12 Where to Go Next. page 12 Additional References. page 12 Feature Information for the IP SLAs UDP Echo Operation.IP SLAs—Analyzing IP Service Levels Using the UDP Echo Operation Prerequisites for the IP SLAs UDP Echo Operation • • • • Configuration Examples for the IP SLAs UDP Echo Operation. Echo Protocol. although any networking device that supports RFC 862. page 14 Prerequisites for the IP SLAs UDP Echo Operation Before configuring the IP SLAs UDP echo operation you should be familiar with the “Cisco IOS IP SLAs Overview” chapter of the Cisco IOS IP SLAs Configuration Guide. Information About the IP SLAs UDP Echo Operation To perform the tasks required to monitor UDP performance using IP SLA. In Figure 1 Router A has been configured as an IP SLAs Responder and Router B is configured as the source IP SLAs device. 2 . Restrictions for the IP SLAs UDP Echo Operation We recommend using a Cisco networking device as the destination device. UDP is a network layer (Layer 3) Internet protocol that is used for many IP services. you should understand the following concept: • UDP Echo Operation.

Using the IP SLAs Responder is optional for a UDP echo operation when using Cisco devices. UDP echo accuracy is enhanced by using the IP SLAs Responder at Router A. A UDP echo operation measures round-trip delay times and tests connectivity to Cisco and non-Cisco devices.IP SLAs—Analyzing IP Service Levels Using the UDP Echo Operation How to Configure the IP SLAs UDP Echo Operation Figure 1 UDP Echo Operation Response time (round-trip time) is computed by measuring the time taken between sending a UDP echo request message from Router B to the destination router—Router A—and receiving a UDP echo reply from Router A. page 3 Configuring and Scheduling a UDP Echo Operation on the Source Device. the destination Cisco router. page 4 (required) Configuring the IP SLAs Responder on the Destination Device Perform this task to enable the IP SLAs Responder on the destination Cisco device of a UDP echo operation. then IP SLAs sends a UDP datagram to any port number that you specified. Prerequisites If you are using the IP SLAs Responder. How to Configure the IP SLAs UDP Echo Operation This section contains the following procedures: • • Configuring the IP SLAs Responder on the Destination Device. enable 3 . ensure that the networking device to be used as the responder is a Cisco device and that you have connectivity to that device through the network. SUMMARY STEPS 1. The results of a UDP echo operation can be useful in troubleshooting issues with business-critical applications by determining the round-trip delay times and testing connectivity to both Cisco and non-Cisco devices. The IP SLAs Responder cannot be configured on non-Cisco devices. If the destination router is a Cisco router.

see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. configure terminal ip sla responder exit DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. page 4 Configuring and Scheduling a UDP Echo Operation with Optional Parameters on the Source Device. depending on whether you want to configure a basic UDP echo operation or configure a UDP echo operation with optional parameters: • • Configuring and Scheduling a Basic UDP Echo Operation on the Source Device. Example: Router# configure terminal Step 3 ip sla responder Enables IP SLAs Responder functionality on a Cisco device. Example: Router> enable Step 2 configure terminal Enters global configuration mode. Example: Router(config)# ip sla responder Step 4 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode. Configuring and Scheduling a Basic UDP Echo Operation on the Source Device Perform this task to enable a UDP echo operation without any optional parameters. 4 .IP SLAs—Analyzing IP Service Levels Using the UDP Echo Operation How to Configure the IP SLAs UDP Echo Operation 2. 4. Perform one of the following tasks in this section. ensure that you have completed the “Configuring the IP SLAs Responder on the Destination Device” section on page 3 before you start this task. use the IP SLAs UDP echo operation. page 7 Prerequisites If you are using the IP SLAs Responder. A UDP echo operation measures round-trip delay times and tests connectivity to Cisco and non-Cisco devices. For information on scheduling a group of operations. 3. Example: Router(config)# exit Configuring and Scheduling a UDP Echo Operation on the Source Device To monitor UDP performance on a device. • Enter your password if prompted.

After entering this command.29. 4. 5. • Enter your password if prompted. Example: Router> enable Step 2 configure terminal Enters global configuration mode. 3. 7.134 5000 The control disable keyword combination should only be used if you are disabling the IP SLAs control protocol on both the source and target routers. Example: Router(config)# ip sla 10 Step 4 udp-echo {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname} source-port port-number] [control {enable | disable}] Defines a UDP echo operation and enters IP SLA UDP configuration mode. 2. 9. the command-line interface (CLI) enters IP SLA UDP echo configuration mode to allow you to specify optional characteristics for the operation. 8. The IP SLAs control protocol is enabled by default. 6.139. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. • Step 5 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats. enable configure terminal ip sla operation-number udp-echo {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname} source-port port-number] [control {enable | disable}] frequency seconds exit ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] exit show ip sla configuration [operation-number] DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. Example: Router(config-ip-sla-udp)# frequency 30 5 . • Example: Router(config-ip-sla)# udp-echo 172.IP SLAs—Analyzing IP Service Levels Using the UDP Echo Operation How to Configure the IP SLAs UDP Echo Operation SUMMARY STEPS 1.

139. each operation response is checked for corruption. ip sla 5 udp-echo 172. add the verify-data command to the configuration of the operation (while configuring in IP SLA configuration mode) to enable data verification. Example: Router(config)# ip sla schedule 5 start-time now life forever Step 8 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode. When enabled. Example: Router(config-ip-sla-udp)# exit Step 7 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation.134 5000 frequency 30 ! ip sla schedule 5 start-time now life forever.IP SLAs—Analyzing IP Service Levels Using the UDP Echo Operation How to Configure the IP SLAs UDP Echo Operation Command or Action Step 6 exit Purpose Exits IP SLA UDP configuration mode and returns to global configuration mode. Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation. • What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command.29. Use the verify-data command with caution during normal operations because it generates unnecessary overhead. Example: Router(config)# exit Step 9 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation. Example: Router# show ip sla configuration 10 Examples The following example shows the configuration of an IP SLAs operation type of UDP echo that will start immediately and run indefinitely. Troubleshooting Tips • If the IP SLAs operation is not running and generating statistics. 6 . Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable.

verify-data 22. Note The tos command defines the type of service (ToS) byte in the IPv4 header of an IP SLAs operation and is valid only in IPv4 networks. 5. 6. frequency seconds 11. SUMMARY STEPS 1. enable configure terminal ip sla operation-number udp-echo {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname} source-port port-number] [control {enable | disable}] history buckets-kept size data-pattern hex-pattern history distributions-of-statistics-kept size history enhanced [interval seconds] [buckets number-of-buckets] history filter {none | all | overThreshold | failures} 10. history hours-of-statistics-kept hours 12. history statistics-distribution-interval milliseconds 16. timeout milliseconds 19. tag text 17. threshold milliseconds 18. For information on scheduling a group of operations. 3. tos number or traffic-class number 20. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. request-data-size bytes 15.IP SLAs—Analyzing IP Service Levels Using the UDP Echo Operation How to Configure the IP SLAs UDP Echo Operation Configuring and Scheduling a UDP Echo Operation with Optional Parameters on the Source Device Perform this task to enable a UDP echo operation on the source device and configure some optional IP SLAs parameters. The source device is the location at which the measurement statistics are stored. 8. The traffic-class command defines the traffic class byte in the IPv6 header for a supported IP SLAs operation. flow-label number 21. The flow-label command defines the value in the flow label field in the IPv6 header for a supported IP SLAs operation and is valid only in IPv6 networks. exit 7 . 9. 2. 7. history lives-kept lives 13. 4. owner owner-id 14.

ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] 24.29. Example: Router> enable Step 2 configure terminal Enters global configuration mode. Use the dest-port keyword and port-number value to specify the destination port number in the range from 1 to 65535. Example: Router(config-ip-sla-udp)# history buckets-kept 25 8 . • Enter your password if prompted. show ip sla configuration [operation-number] DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. exit 25. This configuration is useful when IP SLAs packets are to be routed within an IPsec or GRE tunnel.134 5000 Use the dest-ipaddr keyword and associated options to specify an IP address or designated IP name as the destination of the UDP probe. The control protocol is enabled by default. Use the disable keyword when you want to disable the control protocol. • Example: Router(config-ip-sla)# udp-echo 172.139.IP SLAs—Analyzing IP Service Levels Using the UDP Echo Operation How to Configure the IP SLAs UDP Echo Operation 23. • • • • Step 5 history buckets-kept size (Optional) Sets the number of history buckets that are kept during the lifetime of an IP SLAs operation. Use the optional source-ipaddr keyword and associated options to specify an IP address or designated IP name as the source of the UDP operation. The control protocol is required when the target device is a Cisco router that does not natively provide the UDP service. Use the optional control keyword to specify that the IP SLAs control protocol should be used when running this operation. Example: Router(config)# ip sla 10 Step 4 udp-echo {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname} source-port port-number] [control {enable | disable}] Defines a UDP echo operation and enters IP SLA UDP configuration mode. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. Use the optional source-port keyword and port-number value to specify a source port number.

Example: Router(config-ip-sla-udp)# history filter failures Step 10 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats. Example: Router(config-ip-sla-udp)# history enhanced interval 900 buckets 100 Step 9 history filter {none | all | overThreshold | failures} (Optional) Defines the type of information kept in the history table for an IP SLAs operation. Example: Router(config-ip-sla-udp)# frequency 30 Step 11 history hours-of-statistics-kept hours (Optional) Sets the number of hours for which statistics are maintained for an IP SLAs operation. Example: Router(config-ip-sla-udp)# history hours-of-statistics-kept 4 Step 12 history lives-kept lives (Optional) Sets the number of lives maintained in the history table for an IP SLAs operation. Example: Router(config-ip-sla-udp)# history lives-kept 5 Step 13 owner owner-id (Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation. Example: Router(config-ip-sla-udp)# data-pattern Step 7 history distributions-of-statistics-kept size (Optional) Sets the number of statistics distributions kept per hop during an IP SLAs operation. Example: Router(config-ip-sla-udp)# history distributions-of-statistics-kept 5 Step 8 history enhanced [interval seconds] [buckets number-of-buckets] (Optional) Enables enhanced history gathering for an IP SLAs operation. Example: Router(config-ip-sla-udp)# request-data-size 64 9 . Example: Router(config-ip-sla-udp)# owner admin Step 14 request-data-size bytes (Optional) Sets the protocol data size in the payload of an IP SLAs operation's request packet.IP SLAs—Analyzing IP Service Levels Using the UDP Echo Operation How to Configure the IP SLAs UDP Echo Operation Command or Action Step 6 data-pattern hex-pattern Purpose (Optional) Specifies the data pattern in an IP SLAs operation to test for data corruption.

Example: Router(config-ip-sla-udp)# tag TelnetPollServer1 Step 17 threshold milliseconds Example: Router(config-ip-sla-udp)# threshold 10000 (Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. or (Optional) In an IPv6 network only. (Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet. defines the flow label field in the IPv6 header for a supported IP SLAs operation. Example: Router(config-ip-sla-jitter)# tos 160 or Example: Router(config-ip-sla-jitter)# traffic-class 160 Step 20 flow-label number (Optional) In an IPv6 network only. Step 18 timeout milliseconds Example: Router(config-ip-sla-udp)# timeout 10000 Step 19 tos number or traffic-class number (Optional) In an IPv4 network only.IP SLAs—Analyzing IP Service Levels Using the UDP Echo Operation How to Configure the IP SLAs UDP Echo Operation Command or Action Step 15 history statistics-distribution-interval milliseconds Purpose (Optional) Sets the time interval for each statistics distribution kept for an IP SLAs operation. defines the traffic class byte in the IPv6 header for a supported IP SLAs operation. defines the ToS byte in the IPv4 header of an IP SLAs operation. Example: Router(config-ip-sla-udp)# history statistics-distribution-interval 10 Step 16 tag text (Optional) Creates a user-specified identifier for an IP SLAs operation. Example: Router(config-ip-sla-udp)# flow-label 112233 Step 21 verify-data (Optional) Causes an IP SLAs operation to check each reply packet for data corruption. Example: Router(config-ip-sla-udp)# verify-data Step 22 exit Exits UDP configuration submode and returns to global configuration mode. Example: Router(config-ip-sla-udp)# exit 10 .

0. Example: Router# show ip sla configuration 10 Examples The following sample output shows the configuration of all the IP SLAs parameters (including defaults) for the UDP echo operation number 5.139.134 Source address: 0.29.0. Router# show ip sla configuration 5 Complete configuration Table (includes defaults) Entry number: 5 Owner: jdoe Tag: FLL-RO Type of operation to perform: udpEcho Target address: 172. Example: Router(config)# exit Step 25 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation. Example: Router(config)# ip sla schedule 5 start-time now life forever Step 24 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode.IP SLAs—Analyzing IP Service Levels Using the UDP Echo Operation How to Configure the IP SLAs UDP Echo Operation Command or Action Step 23 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] Purpose Configures the scheduling parameters for an individual IP SLAs operation.0 Target port: 5000 Source port: 0 Request size (ARR data portion): 160 Operation timeout (milliseconds): 1000 Type Of Service parameters: 128 Verify data: No Data pattern: Vrf Name: Control Packets: enabled Operation frequency (seconds): 30 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 Threshold (milliseconds): 5000 Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20 Enhanced History: Aggregation Interval:60 Buckets:2 Number of history Lives kept: 0 Number of history Buckets kept: 15 History Filter Type: None 11 .

When enabled. Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation. • What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. Additional References The following sections provide references related to monitoring UDP echo operations using IP SLA. Configuration Examples for the IP SLAs UDP Echo Operation This section contains the following example: • Configuring a UDP Echo Operation: Example. ip sla 5 udp-echo 172. page 12 Configuring a UDP Echo Operation: Example The following example configures an IP SLAs operation type of UDP echo that will start immediately and run indefinitely. Use the verify-data command with caution during normal operations because it generates unnecessary overhead. each operation response is checked for corruption.29.134 5000 frequency 30 request-data-size 160 tos 128 timeout 1000 tag FLL-RO ip sla schedule 5 life forever start-time now Where to Go Next For information about other types of IP SLAs operations and IP SLAs features. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable.139.IP SLAs—Analyzing IP Service Levels Using the UDP Echo Operation Configuration Examples for the IP SLAs UDP Echo Operation Troubleshooting Tips • If the IP SLAs operation is not running and generating statistics. 12 . see the Cisco IOS IP SLAs Features Roadmap. add the verify-data command to the configuration of the operation (while configuring in IP SLA configuration mode) to enable data verification.

Access to most tools on the Cisco Support website requires a Cisco. including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.com/techsupport 13 . Link http://www. Cisco IOS releases. use Cisco MIB Locator found at the following URL: http://www.cisco.com user ID and password. you can subscribe to various services.cisco. Cisco white paper Cisco IOS IP SLAs Command Reference Standards Standards Title No new or modified standards are supported by this — feature. MIBs MIBs CISCO-RTTMON-MIB MIBs Link To locate and download MIBs for selected platforms. such as the Product Alert Tool (accessed from Field Notices).com/go/mibs RFCs RFCs RFC 862 Title Echo Protocol Technical Assistance Description The Cisco Support website provides extensive online resources.IP SLAs—Analyzing IP Service Levels Using the UDP Echo Operation Additional References Related Documents Related Topic Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands Document Title Cisco IOS IP Service Level Agreements Command Line Interface. To receive security and technical information about your products. the Cisco Technical Services Newsletter. and feature sets. and Really Simple Syndication (RSS) Feeds. and support for existing standards has not been modified by this feature.

Use Cisco Feature Navigator to find information about platform support and software image support. CCDA. All other trademarks mentioned in this document or Website are the property of their respective owners. CCVP. LightStream. Linksys. GigaDrive. Any examples. one-way delay. An account on Cisco. UDP Echo. Live. Collaboration Without Limitation. Cisco Lumin. or platform. ProConnect. CCSP. and Access Registrar. MeetingPlace Chime Sound. IP SLAs for IPv6 (UDP Jitter. Unless noted otherwise. MediaTone. All rights reserved. CCNA. PCNow. 12. DCE. the iQ logo. and Learn and Cisco Store are service marks. 14 . 12. StackWise. Bringing the Meeting To You. and the WebEx logo are registered trademarks of Cisco Systems.3(14)T. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release. Cisco Unity. PowerPanels. MGX. 12. The use of the word partner does not imply a partnership relationship between Cisco and any other company. Cisco Systems. Inc.IP SLAs—Analyzing IP Service Levels Using the UDP Echo Operation Feature Information for the IP SLAs UDP Echo Operation Feature Information for the IP SLAs UDP Echo Operation Table 1 lists the release history for this feature.4(20)T Feature Information The Cisco IOS IP SLAs User Datagram Protocol (UDP) jitter operation allows you to measure round-trip delay. 12. the Cisco Systems logo.2(33)SB.cisco.2(33)SXH. Table 1 Feature Information for the IP SLAs UDP Echo Operation Feature Name IP SLAs UDP Jitter Operation Releases 12.1 12. iPhone. Event Center. Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. iQ Expertise. MeetingPlace. ScriptShare. command display output.com is not required. iQ Net Readiness Scorecard. and connectivity in networks that carry UDP traffic. FormShare. Cisco TelePresence. Cisco Nexus. 12. subsequent releases of that Cisco IOS software release train also support that feature. Changing the Way We Work. Catalyst. Cisco IOS XE Release 2. IronPort. EtherFast.com/go/cfn. Spectrum Expert. AsyncOS. To access Cisco Feature Navigator. Cisco IOS. EtherSwitch. Cisco Press. Inc. Networking Academy.2(33)SRB1. Cisco. TransPath. Networkers. For release information about a specific command. Aironet. Cisco StadiumVision. see the command reference documentation. TCP Connect) Support was added for operability in IPv6 networks. the Cisco logo. iQuick Study. and/or its affiliates in the United States and certain other countries. © 2006-2008 Cisco Systems. feature set. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Play. CCDP. CCNP. Follow Me Browsing. CCENT. Cisco Eos. the Cisco Certified Internetwork Expert logo. Internet Quotient. The Fastest Way to Increase Your Internet Quotient. go to http://www.2(33)SRC. Fast Step. ICMP Echo. Any use of actual IP addresses in illustrative content is unintentional and coincidental. SMARTnet. CCIE. the IronPort logo. one-way packet loss. Not all commands may be available in your Cisco IOS software release. and figures included in the document are shown for illustrative purposes only. WebEx. CCDE. Network Registrar. HomeLink. CCIP. IOS. PIX. one-way jitter. Cisco Systems Capital. SenderBase.2(31)SB2. and Welcome to the Human Network are trademarks.

170 West Tasman Drive. To access Cisco Feature Navigator. Inc. . which allows Cisco customers to analyze IP service levels for IP applications and services. and predictable manner—for measuring network performance. page 2 Information About the IP SLAs HTTP Operation.com/go/cfn. 2006 Last Updated: July 16.cisco. page 2 How to Configure the IP SLAs HTTP Operation.IP SLAs—Analyzing IP Service Levels Using the HTTP Operation First Published: August 14. page 14 Americas Headquarters: Cisco Systems. An account on Cisco. CA 95134-1706 USA © 2007 Cisco Systems. All rights reserved. IP SLAs is a portfolio of technology embedded in most devices that run Cisco IOS software. and to reduce the frequency of network outages. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported. go to http://www. 2008 This module describes how to use the Cisco IOS 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. page 3 Configuration Examples for the IP SLAs HTTP Operation. to increase productivity. This module also demonstrates how the results of the HTTP operation can be displayed and analyzed to determine how an HTTP server is performing. use the “Feature Information for the IP SLAs HTTP Operation” section on page 17. Contents • • • • Prerequisites for the IP SLAs HTTP Operation. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. to lower operational costs. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module. reliable.. The IP SLAs HTTP operation supports both the normal GET requests and customer RAW requests. Inc. IP SLAs uses active traffic monitoring—the generation of traffic in a continuous. San Jose.com is not required.

the raw commands are specified in HTTP RAW configuration mode. The DNS operation is performed first and the DNS RTT is measured. see the “Where to Go Next” section on page 16. HTTP transaction time—RTT taken to send a request and get a response from the HTTP server. the TCP Connect RTT. The HTTP server response time measurements consist of three types: • • • DNS lookup—RTT taken to perform domain name lookup. you should understand the following concept: • HTTP Operation. page 17 Prerequisites for the IP SLAs HTTP Operation Before configuring the IP SLAs HTTP operation you should be familiar with the “Cisco IOS IP SLAs Overview” chapter of the Cisco IOS IP SLAs Configuration Guide. TCP Connect—RTT taken to perform a TCP connection to the HTTP server. The final operation is an HTTP request and the RTT to retrieve the home HTML page from the HTTP server is measured. IP SLAs requires the entire content of the HTTP request. a TCP Connect operation to the appropriate HTTP server is performed and the RTT for this operation is measured. page 16 Additional References. An HTTP request can be made through a proxy server. Information About the IP SLAs HTTP Operation To perform the tasks required to monitor the performance of an HTTP server using IP SLA. page 16 Feature Information for the IP SLAs HTTP Operation. For RAW requests. IP SLAs will format the request based on the specified URL. The operation retrieves only the home HTML page. 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. When a RAW request is configured. page 2 HTTP Operation The HTTP operation measures the round-trip time (RTT) between a Cisco device and an HTTP server to retrieve a web page. Note IP SLAs has individual Domain Name Server (DNS) and TCP Connect operations. 2 . For GET requests. For more details.IP SLAs—Analyzing IP Service Levels Using the HTTP Operation Prerequisites for the IP SLAs HTTP Operation • • • Where to Go Next. Once the domain name is found. and the HTTP RTT. 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. A RAW request is flexible and allows you to control fields such as authentication.

A GET request requires only a specified URL. depending on whether you want to configure a basic HTTP GET operation or configure an HTTP GET operation with optional parameters: • • Configuring and Scheduling a Basic HTTP GET Operation on the Source Device. page 3 Configuring and Scheduling an HTTP RAW Operation on the Source Device. enable configure terminal ip sla operation-number http {get | raw} url url [name-server ip-address] [version version-number] [source-ip {ip-address | hostname}] [source-port port-number] [cache {enable | disable}] [proxy proxy-url] frequency seconds exit ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] exit show ip sla configuration [operation-number] 3 . page 11 Configuring and Scheduling an HTTP GET Operation on the Source Device To measure the response time between a Cisco device and an HTTP server to retrieve a web page. 9. 6.IP SLAs—Analyzing IP Service Levels Using the HTTP Operation How to Configure the IP SLAs HTTP Operation How to Configure the IP SLAs HTTP Operation This section contains the following procedures: • • Configuring and Scheduling an HTTP GET Operation on the Source Device. Note For information on scheduling a group of operations. 4. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. SUMMARY STEPS 1. use the IP SLAs HTTP operation. 8. 2. page 5 Configuring and Scheduling a Basic HTTP GET Operation on the Source Device Perform this task to enable an HTTP GET operation without any optional parameters. 5. page 3 Configuring and Scheduling an HTTP GET Operation with Optional Parameters on the Source Device. This operation does not require the IP SLAs Responder to be enabled. 7. 3. Perform one of the following tasks in this section.

Example: Router# show ip sla configuration 10 4 .25 Step 5 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. Use the url keyword and url argument to specify the URL of the destination HTTP server. • • Use the get keyword to specify an HTTP GET operation. • Enter your password if prompted.219. Example: Router(config)# ip sla schedule 5 start-time now life forever Step 8 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode. Example: Router> enable Step 2 configure terminal Enters global configuration mode. Example: Router(config-ip-sla-http)# exit Step 7 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation. Example: Router(config-ip-sla-http)# frequency 30 Step 6 exit Exits HTTP configuration submode and returns to global configuration mode. Example: Router(config)# exit Step 9 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation. Example: Router(config)# ip sla 10 Step 4 http {get | raw} url url [name-server ip-address] [version version-number] [source-ip {ip-address | hostname}] [source-port port-number] [cache {enable | disable}] [proxy proxy-url] Defines an HTTP operation and enters IP SLA configuration mode.IP SLAs—Analyzing IP Service Levels Using the HTTP Operation How to Configure the IP SLAs HTTP Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. Example: Router(config-ip-sla)# http get url http://198.133.

5. 6. enable configure terminal ip sla operation-number http {get | raw} url url [name-server ip-address] [version version-number] [source-ip {ip-address | hostname}] [source-port port-number] [cache {enable | disable}] [proxy proxy-url] history buckets-kept size history distributions-of-statistics-kept size history enhanced [interval seconds] [buckets number-of-buckets] history filter {none | all | overThreshold | failures} frequency seconds 10. 7. SUMMARY STEPS 1.25 frequency 10 ! ip sla schedule 8 life forever start-time now Troubleshooting Tips Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation. This operation will retrieve the home page from the www. history lives-kept lives 13.219. Configuring and Scheduling an HTTP GET Operation with Optional Parameters on the Source Device Perform this task to enable an HTTP GET operation on the source device and configure some optional IP SLAs parameters. http-raw-request 12. 3.com website. Note For information on scheduling a group of operations. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. ip sla 8 http get url http://198.133. owner owner-id 5 .cisco. 8. The source device is the location at which the measurement statistics are stored.IP SLAs—Analyzing IP Service Levels Using the HTTP Operation How to Configure the IP SLAs HTTP Operation Examples The following example shows the configuration of an IP SLAs operation type of HTTP GET that will start immediately and run indefinitely. 9. history hours-of-statistics-kept hours 11. 4. 2. What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command.

tos number 19. tag text 16. ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] 21.IP SLAs—Analyzing IP Service Levels Using the HTTP Operation How to Configure the IP SLAs HTTP Operation 14. show ip sla configuration [operation-number] 6 . exit 22. exit 20. threshold milliseconds 17. history statistics-distribution-interval milliseconds 15. timeout milliseconds 18.

25 • • • • • • Step 5 history buckets-kept size (Optional) Sets the number of history buckets that are kept during the lifetime of an IP SLAs operation.219. Use the disable keyword when you want to disable the download of cached HTTP pages.133. Use the optional cache keyword to specify that cached HTTP pages can be downloaded. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. Example: Router> enable Step 2 configure terminal Enters global configuration mode. • • Use the get keyword to specify an HTTP GET operation. Use the version keyword and version-number argument to specify the version number. Use the optional proxy keyword and proxy-url argument to specify proxy information. Example: Router(config)# ip sla 10 Step 4 http {get | raw} url url [name-server ip-address] [version version-number] [source-ip {ip-address | hostname}] [source-port port-number] [cache {enable | disable}] [proxy proxy-url] Defines an HTTP operation and enters IP SLA configuration mode. Use the optional source-ipaddr keyword and associated options to specify an IP address or designated IP name as the source of the HTTP operation.IP SLAs—Analyzing IP Service Levels Using the HTTP Operation How to Configure the IP SLAs HTTP Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. Example: Router(config-ip-sla)# http get url http://198. Use the name-server keyword and ip-address argument to specify the IP address of the destination DNS. • Enter your password if prompted. This is enabled by default. Example: Router(config-ip-sla-http)# history buckets-kept 25 7 . Use the optional source-port keyword and port-number argument to specify a source port number. Use the url keyword and url argument to specify the URL of the destination HTTP server. This is useful when IP SLAs packets are to be routed within an IPSec or GRE tunnel.

Example: Router(config-ip-sla-http)# history statistics-distribution-interval 10 8 . Example: Router(config-ip-sla-http)# history distributions-of-statistics-kept 5 Step 7 history enhanced [interval seconds] [buckets number-of-buckets] (Optional) Enables enhanced history gathering for an IP SLAs operation. Example: Router(config-ip-sla-http)# frequency 30 Step 10 history hours-of-statistics-kept hours (Optional) Sets the number of hours for which statistics are maintained for an IP SLAs operation. Example: Router(config-ip-sla-http)# http-raw-request Step 12 history lives-kept lives (Optional) Sets the number of lives maintained in the history table for an IP SLAs operation.IP SLAs—Analyzing IP Service Levels Using the HTTP Operation How to Configure the IP SLAs HTTP Operation Command or Action Step 6 history distributions-of-statistics-kept size Purpose (Optional) Sets the number of statistics distributions kept per hop during an IP SLAs operation. Example: Router(config-ip-sla-http)# history lives-kept 5 Step 13 owner owner-id (Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation. Example: Router(config-ip-sla-http)# history hours-of-statistics-kept 4 Step 11 http-raw-request (Optional) Explicitly specifies the options for a GET request for an IP SLAs HTTP operation. Example: Router(config-ip-sla-http)# history filter failures Step 9 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats. Example: Router(config-ip-sla-http)# history enhanced interval 900 buckets 100 Step 8 history filter {none | all | overThreshold | failures} (Optional) Defines the type of information kept in the history table for an IP SLAs operation. Example: Router(config-ip-sla-http)# owner admin Step 14 history statistics-distribution-interval milliseconds (Optional) Sets the time interval for each statistics distribution kept for an IP SLAs operation.

(Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet. Example: Router(config-ip-sla-http)# tag TelnetPollServer1 Step 16 threshold milliseconds Example: Router(config-ip-sla-http)# threshold 10000 (Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. Example: Router# show ip sla configuration 10 Examples The following sample output shows the configuration of all the IP SLAs parameters (including defaults) for the HTTP GET operation number 8. Router# show ip sla configuration 8 Complete Configuration Table (includes defaults) Entry Number: 8 Owner: Tag: FLL-LA 9 .IP SLAs—Analyzing IP Service Levels Using the HTTP Operation How to Configure the IP SLAs HTTP Operation Command or Action Step 15 tag text Purpose (Optional) Creates a user-specified identifier for an IP SLAs operation. Example: Router(config-ip-sla-http)# tos 160 Step 19 exit Exits HTTP configuration submode and returns to global configuration mode. Example: Router(config)# exit Step 22 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation. Example: Router(config-ip-sla-http)# exit Step 20 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation. Step 17 timeout milliseconds Example: Router(config-ip-sla-http)# timeout 10000 Step 18 tos number (Optional) Defines a type of service (ToS) byte in the IP header of an IP SLAs operation. Example: Router(config)# ip sla schedule 5 start-time now life forever Step 21 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode.

0 URL: http://198.runs forever Next Scheduled Start Time: Start Time already passed Entry Ageout (seconds): never Connection Loss Reaction Enabled: FALSE Timeout Reaction Enabled: FALSE Threshold Reaction Type: never Threshold Falling (milliseconds): 3000 Threshold Count: 5 Threshold Count2: 5 Reaction Type: none Verify Error Reaction Enabled: FALSE Number of Statistic Hours kept: 2 Number of Statistic Paths kept: 1 Number of Statistic Hops kept: 1 Number of Statistic Distribution Buckets kept: 1 Statistic Distribution Interval (milliseconds): 20 Number of History Lives kept: 0 Number of History Buckets kept: 15 Number of History Samples kept: 1 History Filter Type: none Troubleshooting Tips Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable.133.0. 10 .25 Proxy: Raw String(s): Cache Control: enabled Life (seconds): infinite .0 Target Port: 0 Source Port: 0 Request Size (ARR data portion): 1 Response Size (ARR data portion): 1 Control Packets: enabled Loose Source Routing: disabled LSR Path: Type of Service Parameters: 0x0 HTTP Operation: get HTTP Server Version: 1.219.IP SLAs—Analyzing IP Service Levels Using the HTTP Operation How to Configure the IP SLAs HTTP Operation Type of Operation to Perform: http Reaction and History Threshold (milliseconds): 5000 Operation Frequency (seconds): 60 Operation Timeout (milliseconds): 5000 Verify Data: FALSE Status of Entry (SNMP RowStatus): active Protocol Type: httpAppl Target Address: Source Address: 0. What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command.0.

3. 6. The source device is the location at which the measurement statistics are stored. To perform a RAW request.IP SLAs—Analyzing IP Service Levels Using the HTTP Operation How to Configure the IP SLAs HTTP Operation Configuring and Scheduling an HTTP RAW Operation on the Source Device To measure the response time between a Cisco device and an HTTP server to retrieve a web page. 8. After entering HTTP RAW configuration mode. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. 9. 5. use the IP SLAs HTTP operation. 2. This operation does not require the IP SLAs Responder to be enabled. enable configure terminal ip sla operation-number http {get | raw} url url [name-server ip-address] [version version-number] [source-ip {ip-address | hostname}] [source-port port-number] [cache {enable | disable}] [proxy proxy-url] http-raw-request Enter the required HTTP 1. SUMMARY STEPS 1. 7. Note For information on scheduling a group of operations. IP SLAs requires you to specify the entire contents of the HTTP request. 4. Perform this task to enable an HTTP RAW operation on the source device and configure some optional IP SLAs parameters. show ip sla configuration [operation-number] 11 .0 commands to complete the HTTP RAW request. exit ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] exit 10. you can specify HTTP 1.0 command syntax.

This is useful when IP SLAs packets are to be routed within an IPSec or GRE tunnel. This is enabled by default. Use the disable keyword when you want to disable the download of cached HTTP pages. Example: Router(config-ip-sla)# http-raw-request 12 .133. Use the name-server keyword and ip-address argument to specify the IP address of the destination DNS. Use the optional proxy keyword and proxy-url argument to specify proxy information. Use the optional source-ipaddr keyword and associated options to specify an IP address or designated IP name as the source of the HTTP operation. • • • Use the raw keyword to specify an HTTP RAW operation. Use the version keyword and version-number argument to specify the version number.25 • • • • • Step 5 http-raw-request Enters HTTP RAW configuration mode. Example: Router> enable Step 2 configure terminal Enters global configuration mode. Use the optional cache keyword to specify that cached HTTP pages can be downloaded.219. Example: Router(config)# ip sla 10 Step 4 http {get | raw} url url [name-server ip-address] [version version-number] [source-ip {ip-address | hostname}] [source-port port-number] [cache {enable | disable}] [proxy proxy-url] Defines an HTTP operation. Use the optional source-port keyword and port-number argument to specify a source port number. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. Use the url keyword and url argument to specify the URL of the destination HTTP server. Example: Router(config-ip-sla)# http raw url http://198. • Enter your password if prompted.IP SLAs—Analyzing IP Service Levels Using the HTTP Operation How to Configure the IP SLAs HTTP Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode.

html HTTP/1.0.IP SLAs—Analyzing IP Service Levels Using the HTTP Operation How to Configure the IP SLAs HTTP Operation Command or Action Step 6 Purpose Specifies all the required HTTP 1. Example: Router(config-ip-sla-http)# GET /en/US/hmpgs/index.0.0 commands. Router# show ip sla configuration 8 Complete Configuration Table (includes defaults) Entry Number: 8 Owner: Tag: Type of Operation to Perform: http Reaction and History Threshold (milliseconds): 5000 Operation Frequency (seconds): 60 Operation Timeout (milliseconds): 5000 Verify Data: FALSE Status of Entry (SNMP RowStatus): active Protocol Type: httpAppl Target Address: Source Address: 0.0\r\n\r\n Step 7 exit Exits HTTP RAW configuration submode and returns to global configuration mode. Example: Router(config)# ip sla schedule 5 start-time now life forever Step 9 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode. Example: Router# show ip sla configuration 10 Examples The following sample output shows the configuration of all the IP SLAs parameters (including defaults) for the HTTP RAW operation number 8. Enter the required HTTP 1.0 Target Port: 0 Source Port: 0 Request Size (ARR data portion): 1 Response Size (ARR data portion): 1 Control Packets: enabled Loose Source Routing: disabled LSR Path: 13 . Example: Router(config-ip-sla-http)# exit Step 8 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation. Example: Router(config)# exit Step 10 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation.0 command syntax.

133.25 Proxy: Raw String(s): GET /en/US/hmpgs/index. page 15 Configuring an HTTP RAW Operation with Authentication: Example. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable.IP SLAs—Analyzing IP Service Levels Using the HTTP Operation Configuration Examples for the IP SLAs HTTP Operation Type of Service Parameters: 0x0 HTTP Operation: raw HTTP Server Version: 1.runs forever Next Scheduled Start Time: Start Time already passed Entry Ageout (seconds): never Connection Loss Reaction Enabled: FALSE Timeout Reaction Enabled: FALSE Threshold Reaction Type: never Threshold Falling (milliseconds): 3000 Threshold Count: 5 Threshold Count2: 5 Reaction Type: none Verify Error Reaction Enabled: FALSE Number of Statistic Hours kept: 2 Number of Statistic Paths kept: 1 Number of Statistic Hops kept: 1 Number of Statistic Distribution Buckets kept: 1 Statistic Distribution Interval (milliseconds): 20 Number of History Lives kept: 0 Number of History Buckets kept: 15 Number of History Samples kept: 1 History Filter Type: none Troubleshooting Tips Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation.0 URL: http://198.html HTTP/1. page 16 14 .219. page 15 Configuring an HTTP RAW Operation Through a Proxy Server: Example. Configuration Examples for the IP SLAs HTTP Operation This section provides the following configuration examples: • • • • Configuring an HTTP GET Operation: Example. What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command.0\r\n\r\n Cache Control: enabled Life (seconds): infinite . page 15 Configuring an HTTP RAW Operation: Example.

ip sla 8 http raw url http://198.25 http-raw-request GET /en/US/hmpgs/index.219. ip sla 8 18170 15 .133.com website. enter HTTP RAW configuration mode by using the http-raw-request command in IP SLA configuration mode. The proxy server is www.0\r\n \r\n end ip sla schedule 8 life forever start-time now Configuring an HTTP RAW Operation Through a Proxy Server: Example The following example shows how to configure an HTTP RAW operation through a proxy server.25 ! ip sla schedule 8 start-time now Configuring an HTTP RAW Operation: Example The following example shows how to configure an HTTP RAW operation.yahoo. Figure 1 depicts the HTTP GET operation.proxy.133.cisco.html HTTP/1. Figure 1 HTTP Operation HTTP server Router A HTTP operation Performance management application Router B Router B Configuration ip sla 8 http get url http://198.IP SLAs—Analyzing IP Service Levels Using the HTTP Operation Configuration Examples for the IP SLAs HTTP Operation Configuring an HTTP GET Operation: Example The following example show how to create and configure operation number 8 as an HTTP GET operation.219. To use the RAW commands. The destination URL IP address represents the www.com and the HTTP server is www. The IP SLA HTTP RAW configuration mode is indicated by the (config-ip-sla-http) router prompt.cisco.com.

com http-raw-request GET /lab/index. Release 12. Related Documents Related Topic Overview of Cisco IOS IP SLAs Cisco IOS IP SLAs commands: complete command syntax.com HTTP/1.IP SLAs—Analyzing IP Service Levels Using the HTTP Operation Where to Go Next http raw url http://www.cisco. ip sla 8 http raw url http://site-test.4T Cisco IOS IP SLAs Command Reference.html HTTP/1. command mode. Additional References The following sections provide references related to monitoring the performance of an HTTP server using IP SLA.yahoo.cisco. defaults. Release 12.0\r\n Authorization: Basic btNpdGT4biNvoZe=\r\n \r\n end ip sla schedule 8 life forever start-time now Where to Go Next For information about other types of IP SLAs operations and IP SLAs features.0\r\n \r\n end ip sla schedule 8 life forever start-time now Configuring an HTTP RAW Operation with Authentication: Example The following example shows how to configure an HTTP RAW operation with authentication. and support for existing standards has not been modified by this feature. 16 .4T Standards Standards Title No new or modified standards are supported by this — feature. see the Cisco IOS IP SLAs Features Roadmap.proxy. command history. and examples Document Title “Cisco IOS IP SLAs Overview” chapter of the Cisco IOS IP SLAs Configuration Guide. usage guidelines.com http-raw-request GET http://www.

An account on Cisco. use Cisco MIB Locator found at the following URL: http://www. solutions. see the “Cisco IOS IP SLAs Features Roadmap.shtml Feature Information for the IP SLAs HTTP Operation Table 1 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12. feature set.cisco. Title — Technical Assistance Description Technical Assistance Center (TAC) home page. containing 30.” Not all commands may be available in your Cisco IOS software release.cisco. including links to products.3(14)T or a later release appear in the table. Unless noted otherwise. For information on a feature in this technology that is not documented here.cisco. and support for existing RFCs has not been modified by this feature. subsequent releases of that Cisco IOS software release train also support that feature. go to http://www. and tools. Cisco IOS releases. Link http://www. technical tips.000 pages of searchable technical content. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release. To access Cisco Feature Navigator.com is not required. 17 . see the command reference documentation.com/go/cfn. Registered Cisco.com users can log in from this page to access even more content. technologies. and feature sets. or platform.IP SLAs—Analyzing IP Service Levels Using the HTTP Operation Feature Information for the IP SLAs HTTP Operation MIBs MIBs CISCO-RTTMON-MIB MIBs Link To locate and download MIBs for selected platforms. Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train.com/go/mibs RFCs RFCs No new or modified RFCs are supported by this feature. For release information about a specific command. Use Cisco Feature Navigator to find information about platform support and software image support.com/public/support/tac/home.

Internet Quotient. Cisco StadiumVision. Event Center. Cisco IOS XE Release 2. © 2006-2008 Cisco Systems. the IronPort logo. Live. ProConnect.2(33)SXH. and Learn and Cisco Store are service marks. CCVP. 18 .2(31)SB2. Inc. SenderBase. iQuick Study. iQ Net Readiness Scorecard. and the WebEx logo are registered trademarks of Cisco Systems. CCIP. the Cisco Certified Internetwork Expert logo. the iQ logo.1 Feature Information The Cisco IOS IP SLAs Hypertext Transfer Protocol (HTTP) operation allows you to measure the network response time between a Cisco device and an HTTP server to retrieve a web page. IronPort. command display output. The Fastest Way to Increase Your Internet Quotient. CCSP. Changing the Way We Work. iPhone. Cisco TelePresence. AsyncOS. Linksys. the Cisco Systems logo. Networking Academy. CCDA. Network Registrar. the Cisco logo. WebEx. PIX. 12. Spectrum Expert. StackWise. HomeLink. All other trademarks mentioned in this document or Website are the property of their respective owners. Cisco Lumin. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. PowerPanels. MediaTone. MeetingPlace. Cisco Press. Cisco Unity. PCNow. IOS. Networkers. Collaboration Without Limitation. TransPath. Cisco IOS. Cisco. EtherFast. Cisco Nexus. Play. and Access Registrar. LightStream. CCIE. CCNP. EtherSwitch. Fast Step. Follow Me Browsing. GigaDrive. and/or its affiliates in the United States and certain other countries. All rights reserved. MGX. Any examples. and Welcome to the Human Network are trademarks. Cisco Systems Capital. Cisco Eos. CCENT. CCDE. 12. Aironet.IP SLAs—Analyzing IP Service Levels Using the HTTP Operation Feature Information for the IP SLAs HTTP Operation Table 1 Feature Information for the IP SLAs HTTP Operation Feature Name IP SLAs HTTP Operation Releases 12. CCDP. iQ Expertise. Catalyst. ScriptShare. DCE.3(14)T. Inc. CCNA. and figures included in the document are shown for illustrative purposes only. Bringing the Meeting To You. Any use of actual IP addresses in illustrative content is unintentional and coincidental. FormShare. MeetingPlace Chime Sound. 12. SMARTnet. Cisco Systems. The use of the word partner does not imply a partnership relationship between Cisco and any other company.2(33)SRB1.

The TCP Connect operation is useful for measuring response times for a server used for a particular application or connectivity testing for server availability. IP SLAs is a portfolio of technology embedded in most devices that run Cisco IOS software. use the “Feature Information for the IP SLAs TCP Connect Operation” section on page 14. and to reduce the frequency of network outages. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module. to increase productivity. San Jose. Contents • • Prerequisites for the IP SLAs TCP Connect Operation. IP SLAs uses active traffic monitoring—the generation of traffic in a continuous. page 2 Americas Headquarters: Cisco Systems. This module also demonstrates how the results of the TCP Connect operation can be displayed and analyzed to determine how the connection times to servers and hosts within your network can affect IP service levels.IP SLAs—Analyzing IP Service Levels Using the TCP Connect Operation First Published: August 14.cisco. and predictable manner—for measuring network performance. page 2 Information About the IP SLAs TCP Connect Operation. 170 West Tasman Drive. go to http://www. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported. reliable. An account on Cisco. Inc. .. to lower operational costs. 2008 This module describes how to use the Cisco IOS IP Service Level Agreements (SLAs) TCP Connect operation to measure the response time taken to perform a TCP Connect operation between a Cisco router and devices using IPv4 or IPv6. Inc.com/go/cfn.com is not required. To access Cisco Feature Navigator. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. 2006 Last Updated: July 16. which allows Cisco customers to analyze IP service levels for IP applications and services. TCP Connect accuracy is enhanced by using the IP SLAs Responder at the destination Cisco router. CA 95134-1706 USA © 2006-2008 Cisco Systems. All rights reserved.

The destination device can be any device using IP or an IP SLAs Responder. Information About the IP SLAs TCP Connect Operation To perform the tasks required to analyze TCP connection times using IP SLA. page 12 Feature Information for the IP SLAs TCP Connect Operation. In Figure 1 Router B is configured as the source IP SLAs device and a TCP Connect operation is configured with the destination device as IP Host 1. you should understand the following concept: • TCP Connect Operation.IP SLAs—Analyzing IP Service Levels Using the TCP Connect Operation Prerequisites for the IP SLAs TCP Connect Operation • • • • • How to Configure the IP SLAs TCP Connect Operation. TCP is a transport layer (Layer 4) Internet protocol that provides reliable full-duplex data transmission. page 11 Where to Go Next. Figure 1 TCP Connect Operation 2 . page 2 TCP Connect Operation The IP SLAs TCP Connect operation measures the response time taken to perform a TCP Connect operation between a Cisco router and devices using IP. page 3 Configuration Examples for the IP SLAs TCP Connect Operation. page 14 Prerequisites for the IP SLAs TCP Connect Operation Before configuring the IP SLAs TCP Connect operation you should be familiar with the “Cisco IOS IP SLAs Overview” chapter of the Cisco IOS IP SLAs Configuration Guide. page 11 Additional References.

TCP Connect is used to test virtual circuit availability or application availability. then IP SLAs makes a TCP connection to any port number that you specified. How to Configure the IP SLAs TCP Connect Operation This section contains the following procedures: • • Configuring the IP SLAs Responder on the Destination Device. or 80 for an HTTP server. ensure that the networking device to be used as the Responder is a Cisco device and that you have connectivity to that device through the network. enable configure terminal ip sla responder exit 3 . page 3 (optional) Configuring and Scheduling a TCP Connect Operation on the Source Device. 4. If the destination router is a Cisco router. 3. page 4 (required) Configuring the IP SLAs Responder on the Destination Device Perform this task to enable the IP SLAs Responder on the destination Cisco device of a TCP Connect operation. then you must specify a known destination port number such as 21 for FTP. A TCP Connect operation measures the response time taken to perform a TCP Connect operation between a Cisco router and devices using IP. Server and application connection performance can be tested by simulating Telnet.IP SLAs—Analyzing IP Service Levels Using the TCP Connect Operation How to Configure the IP SLAs TCP Connect Operation Connection response time is computed by measuring the time taken between sending a TCP request message from Router B to IP Host 1 and receiving a reply from IP Host 1. SQL. and other types of connection to help you verify your IP service levels. 2. TCP Connect accuracy is enhanced by using the IP SLAs Responder at the destination Cisco device. Using the IP SLAs Responder is optional for a TCP Connect operation when using Cisco devices. 23 for Telnet. Prerequisites If you are using the IP SLAs Responder. The IP SLAs Responder cannot be configured on non-Cisco devices. If the destination is not a Cisco IP host. SUMMARY STEPS 1.

• Enter your password if prompted. SUMMARY STEPS 1. enable configure terminal 4 . depending on whether you want to configure a basic TCP Connect operation or configure a TCP Connect operation with optional parameters: • • Configuring and Scheduling a Basic TCP Connect Operation on the Source Device. ensure that you have completed the “Configuring the IP SLAs Responder on the Destination Device” section on page 3 before you start this task. Example: Router(config)# exit Configuring and Scheduling a TCP Connect Operation on the Source Device To measure TCP connection response times between a Cisco IP device and a destination IP device. Example: Router# configure terminal Step 3 ip sla responder Enables IP SLAs Responder functionality on a Cisco device. Example: Router(config)# ip sla responder Step 4 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode. Example: Router> enable Step 2 configure terminal Enters global configuration mode.IP SLAs—Analyzing IP Service Levels Using the TCP Connect Operation How to Configure the IP SLAs TCP Connect Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. page 6 Prerequisites If you are using the IP SLAs Responder. use the IP SLAs TCP Connect operation. 2. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. page 4 Configuring and Scheduling a TCP Connect Operation with Optional Parameters on the Source Device. Perform one of the following tasks in this section. For information on scheduling a group of operations. A TCP Connect operation measures the response time taken to perform a TCP Connect operation between a Cisco router and devices using IP. Configuring and Scheduling a Basic TCP Connect Operation on the Source Device Perform this task to enable a TCP Connect operation without any optional parameters.

29. Example: Router(config-ip-sla)# tcp-connect 172. 7. Example: Router> enable Step 2 configure terminal Enters global configuration mode. • Enter your password if prompted. 8. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. 6.132 5000 Step 5 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats.IP SLAs—Analyzing IP Service Levels Using the TCP Connect Operation How to Configure the IP SLAs TCP Connect Operation 3.139. Example: Router(config-ip-sla-tcp)# exit 5 . 5. 4. ip sla operation-number tcp-connect {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname} source-port port-number] [control {enable | disable}] frequency seconds exit ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] exit DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. Example: Router(config-ip-sla-tcp)# frequency 30 Step 6 exit Exits IP SLA TCP configuration mode and returns to global configuration mode. Example: Router(config)# ip sla 10 Step 4 tcp-connect {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname} source-port port-number] [control {enable | disable}] Defines a TCP Connect operation and enters IP SLA TCP configuration mode.

IP SLAs—Analyzing IP Service Levels Using the TCP Connect Operation How to Configure the IP SLAs TCP Connect Operation Command or Action Step 7 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Purpose Configures the scheduling parameters for an individual IP SLAs operation. The traffic-class command defines the traffic class byte in the IPv6 header for a supported IP SLAs operation. 2.29. Configuring and Scheduling a TCP Connect Operation with Optional Parameters on the Source Device Perform this task to enable a TCP Connect operation on the source device and configure some optional IP SLAs parameters. SUMMARY STEPS 1.139. Note The tos command defines the type of service (ToS) byte in the IPv4 header of an IP SLAs operation and is valid only in IPv4 networks.132 5000 frequency 10 ! ip sla schedule 9 life forever start-time now What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. For information on scheduling a group of operations. Example: Router(config)# ip sla schedule 10 start-time now life forever Step 8 exit (Optional) Exits the global configuration mode and returns to privileged EXEC mode. The flow-label command defines the value in the flow label field in the IPv6 header for a supported IP SLAs operation and is valid only in IPv6 networks. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. The source device is the location at which the measurement statistics are stored. enable configure terminal 6 . ip sla 9 tcp-connect 172. Example: Router(config)# exit Examples The following example shows the configuration of an IP SLAs operation type of TCP Connect that will start immediately and run indefinitely.

ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] 21. 9. 5. • Enter your password if prompted. Example: Router> enable Step 2 configure terminal Enters global configuration mode.IP SLAs—Analyzing IP Service Levels Using the TCP Connect Operation How to Configure the IP SLAs TCP Connect Operation 3. owner owner-id 13. history statistics-distribution-interval milliseconds 14. exit 22. threshold milliseconds 16. show ip sla configuration [operation-number] DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. timeout milliseconds 17. 8. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. tos number or traffic-class number 18. exit 20. history lives-kept lives 12. 7. flow-label number 19. tag text 15. Example: Router(config)# ip sla 10 7 . 4. ip sla operation-number tcp-connect {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname} source-port port-number] [control {enable | disable}] history buckets-kept size history distributions-of-statistics-kept size history enhanced [interval seconds] [buckets number-of-buckets] history filter {none | all | overThreshold | failures} frequency seconds 10. history hours-of-statistics-kept hours 11. 6.

Example: Router(config-ip-sla-tcp)# history lives-kept 5 Step 12 owner owner-id (Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation. Example: Router(config-ip-sla-tcp)# history buckets-kept 25 Step 6 history distributions-of-statistics-kept size (Optional) Sets the number of statistics distributions kept per hop during an IP SLAs operation.132 5000 Step 5 history buckets-kept size (Optional) Sets the number of history buckets that are kept during the lifetime of an IP SLAs operation.IP SLAs—Analyzing IP Service Levels Using the TCP Connect Operation How to Configure the IP SLAs TCP Connect Operation Command or Action Step 4 tcp-connect {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname} source-port port-number] [control {enable | disable}] Purpose Defines a TCP Connect operation and enters IP SLA TCP configuration mode.29. Example: Router(config-ip-sla-tcp)# history enhanced interval 900 buckets 100 Step 8 history filter {none | all | overThreshold | failures} (Optional) Defines the type of information kept in the history table for an IP SLAs operation. Example: Router(config-ip-sla-tcp)# history distributions-of-statistics-kept 5 Step 7 history enhanced [interval seconds] [buckets number-of-buckets] (Optional) Enables enhanced history gathering for an IP SLAs operation. Example: Router(config-ip-sla-tcp)# owner admin 8 . Example: Router(config-ip-sla)# tcp-connect 172.139. Example: Router(config-ip-sla-tcp)# frequency 30 Step 10 history hours-of-statistics-kept hours (Optional) Sets the number of hours for which statistics are maintained for an IP SLAs operation. Example: Router(config-ip-sla-tcp)# history hours-of-statistics-kept 4 Step 11 history lives-kept lives (Optional) Sets the number of lives maintained in the history table for an IP SLAs operation. Example: Router(config-ip-sla-tcp)# history filter failures Step 9 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats.

Example: Router(config-ip-sla-tcp)# exit Step 20 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation. Step 16 timeout milliseconds Example: Router(config-ip-sla-tcp)# timeout 10000 Step 17 tos number or traffic-class number (Optional) In an IPv4 network only. Example: Router(config-ip-sla-jitter)# tos 160 or Example: Router(config-ip-sla-jitter)# traffic-class 160 Step 18 flow-label number (Optional) In an IPv6 network only. defines the ToS byte in the IPv4 header of an IP SLAs operation.IP SLAs—Analyzing IP Service Levels Using the TCP Connect Operation How to Configure the IP SLAs TCP Connect Operation Command or Action Step 13 history statistics-distribution-interval milliseconds Purpose (Optional) Sets the time interval for each statistics distribution kept for an IP SLAs operation. defines the traffic class byte in the IPv6 header for a supported IP SLAs operation. Example: Router(config)# ip sla schedule 10 start-time now life forever 9 . Example: Router(config-ip-sla-tcp)# tag TelnetPollServer1 Step 15 threshold milliseconds Example: Router(config-ip-sla-tcp)# threshold 10000 (Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. Example: Router(config-ip-sla-tcp)# flow-label 112233 Step 19 exit Exits TCP configuration submode and returns to global configuration mode. Example: Router(config-ip-sla-tcp)# history statistics-distribution-interval 10 Step 14 tag text (Optional) Creates a user-specified identifier for an IP SLAs operation. (Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet. or (Optional) In an IPv6 network only. defines the flow label field in the IPv6 header for a supported IP SLAs operation.

Router# show ip sla configuration 9 Complete Configuration Table (includes defaults) Entry Number: 9 Owner: Tag: SL-SGU Type of Operation to Perform: tcpConnect Reaction and History Threshold (milliseconds): 5000 Operation Frequency (seconds): 20 Operation Timeout (milliseconds): 60000 Verify Data: FALSE Status of Entry (SNMP RowStatus): active Protocol Type: ipTcpConn Target Address: 172.0. Example: Router# show ip sla configuration 10 Examples The following sample output shows the configuration of all the IP SLAs parameters (including defaults) for the TCP Connect operation number 9.132 Source Address: 0. Example: Router(config)# exit Step 22 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation.0.29.IP SLAs—Analyzing IP Service Levels Using the TCP Connect Operation How to Configure the IP SLAs TCP Connect Operation Command or Action Step 21 exit Purpose (Optional) Exits global configuration mode and returns to privileged EXEC mode.0 Target Port: 5000 Source Port: 0 Request Size (ARR data portion): 1 Response Size (ARR data portion): 1 Control Packets: enabled Loose Source Routing: disabled LSR Path: Type of Service Parameters: 128 Life (seconds): infinite .139.runs forever Next Scheduled Start Time: Start Time already passed Entry Ageout (seconds): never Connection Loss Reaction Enabled: FALSE Timeout Reaction Enabled: FALSE Threshold Reaction Type: never Threshold Falling (milliseconds): 3000 Threshold Count: 5 Threshold Count2: 5 Reaction Type: none Verify Error Reaction Enabled: FALSE Number of Statistic Hours kept: 2 Number of Statistic Paths kept: 1 Number of Statistic Hops kept: 1 Number of Statistic Distribution Buckets kept: 1 Statistic Distribution Interval (milliseconds): 20 Number of History Lives kept: 0 Number of History Buckets kept: 15 Number of History Samples kept: 1 History Filter Type: none 10 .

29.0.1 23 control disable frequency 30 tos 128 timeout 1000 tag FLL-RO ip sla schedule 9 start-time now The following example shows how to configure a TCP Connect operation with a specific port. and without an IP SLAs Responder. The operation is scheduled to start immediately and run indefinitely.0. This action allows the Responder to reply to the TCP Connect operation. see the Cisco IOS IP SLAs Features Roadmap. Router A Configuration configure terminal ip sla responder Router B Configuration ip sla 9 tcp-connect 10. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. The operation is scheduled to start immediately. What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. IP SLAs uses the control protocol to notify the IP SLAs Responder to enable the target port temporarily.0. Configuration Examples for the IP SLAs TCP Connect Operation This section contains the following configuration example: • Configuring a TCP Connect Operation: Examples.139.0. the control protocol is disabled. because the target is not a router and a well-known TCP port is used. 11 . there is no need to send the control message. In this example. port 23.132 21 control disable frequency 30 ip sla schedule 9 life forever start-time now Where to Go Next For information about other types of IP SLAs operations and IP SLAs features. ip sla 9 tcp-connect 173.1). In this example.IP SLAs—Analyzing IP Service Levels Using the TCP Connect Operation Configuration Examples for the IP SLAs TCP Connect Operation Troubleshooting Tips Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation. page 11 Configuring a TCP Connect Operation: Examples The following example shows how to configure a TCP Connect operation as shown in Figure 1 from Router B to the Telnet port (TCP port 23) of IP Host 1 (IP address 10.

use Cisco MIB Locator found at the following URL: http://www. and support for existing standards has not been modified by this feature. Related Documents Related Topic Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands Document Title Cisco IOS IP Service Level Agreements Command Line Interface.IP SLAs—Analyzing IP Service Levels Using the TCP Connect Operation Additional References Additional References The following sections provide references related to the IP SLAs TCP Connect operation.cisco.com/go/mibs RFCs RFCs No new or modified RFCs are supported by this feature. Title — 12 . and support for existing RFCs has not been modified by this feature. and feature sets. Cisco white paper Cisco IOS IP SLAs Command Reference Standards Standards Title No new or modified standards are supported by this — feature. MIBs MIBs CISCO-RTTMON-MIB MIBs Link To locate and download MIBs for selected platforms. Cisco IOS releases.

cisco. Access to most tools on the Cisco Support website requires a Cisco. such as the Product Alert Tool (accessed from Field Notices). To receive security and technical information about your products. and Really Simple Syndication (RSS) Feeds. you can subscribe to various services.com user ID and password. including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. the Cisco Technical Services Newsletter.com/techsupport 13 . Link http://www.IP SLAs—Analyzing IP Service Levels Using the TCP Connect Operation Additional References Technical Assistance Description The Cisco Support website provides extensive online resources.

the iQ logo. Cisco Eos. ProConnect. Networking Academy. and figures included in the document are shown for illustrative purposes only. CCNA.3(14)T. HomeLink. CCDA. Inc. FormShare. and Welcome to the Human Network are trademarks. Internet Quotient. 12. MediaTone. MGX. 12. Live. Cisco StadiumVision.4(20)T Feature Information The Cisco IOS IP SLAs Transmission Control Protocol (TCP) connect operation allows you to measure the network response time taken to perform a TCP Connect operation between a Cisco device and other devices using IP. MeetingPlace. An account on Cisco. command display output. GigaDrive. Inc. To access Cisco Feature Navigator. Cisco. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release. the Cisco Systems logo. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Cisco Systems. StackWise. the Cisco logo. Support was added for operability in IPv6 networks. WebEx. SMARTnet. iQ Net Readiness Scorecard. iPhone.IP SLAs—Analyzing IP Service Levels Using the TCP Connect Operation Feature Information for the IP SLAs TCP Connect Operation Feature Information for the IP SLAs TCP Connect Operation Table 1 lists the release history for this feature. CCNP. 12. and Learn and Cisco Store are service marks. 12. Table 1 Feature Information for the IP SLAs TCP Connect Operation Feature Name IP SLAs TCP Connect Operation Releases 12. CCSP. and the WebEx logo are registered trademarks of Cisco Systems. Unless noted otherwise. CCDP. PCNow. Changing the Way We Work. TCP Connect) CCDE.2(31)SB2. CCIP. Cisco TelePresence. Cisco IOS XE Release 2. PIX. go to http://www.cisco. Fast Step. Cisco Unity. EtherFast. Networkers. Spectrum Expert. IOS. iQ Expertise. feature set. © 2006-2008 Cisco Systems. Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. DCE. Any examples. The Fastest Way to Increase Your Internet Quotient.1 12. Cisco Lumin. LightStream. Network Registrar. 12. IronPort. Cisco Nexus. Bringing the Meeting To You. All other trademarks mentioned in this document or Website are the property of their respective owners. Cisco Systems Capital. ScriptShare.2(33)SB. PowerPanels. AsyncOS. Follow Me Browsing. Catalyst. For release information about a specific command. or platform. Aironet. the IronPort logo.com is not required. MeetingPlace Chime Sound. Linksys. All rights reserved. see the command reference documentation. IP SLAs for IPv6 (UDP Jitter. UDP Echo. subsequent releases of that Cisco IOS software release train also support that feature.2(33)SXH. the Cisco Certified Internetwork Expert logo. and/or its affiliates in the United States and certain other countries. and Access Registrar. Play.com/go/cfn. EtherSwitch. CCIE. CCENT. ICMP Echo. Cisco IOS. CCVP. Collaboration Without Limitation. Event Center.2(33)SRC. Not all commands may be available in your Cisco IOS software release.2(33)SRB1. Any use of actual IP addresses in illustrative content is unintentional and coincidental. 14 . iQuick Study. The use of the word partner does not imply a partnership relationship between Cisco and any other company. Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Press. SenderBase. TransPath.

which allows Cisco customers to analyze IP service levels for IP applications and services. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support.IP SLAs—Analyzing IP Service Levels Using the ICMP Echo Operation First Published: August 14.cisco.com/go/cfn. 2006 Last Updated: July 16. page 2 How to Configure the IP SLAs ICMP Echo Operation. CA 95134-1706 USA © 2006-2008 Cisco Systems. to lower operational costs. IP SLAs is a portfolio of technology embedded in most devices that run Cisco IOS software. ICMP Echo is useful for troubleshooting network connectivity issues. reliable. page 2 Information About the IP SLAs ICMP Echo Operation. Inc. Contents • • • • Prerequisites for the IP SLAs ICMP Echo Operation. 170 West Tasman Drive. Inc. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module. go to http://www..com is not required. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported. San Jose. . This module also demonstrates how the results of the ICMP Echo operation can be displayed and analyzed to determine how the network IP connections are performing. All rights reserved. page 2 Restrictions for the IP SLAs ICMP Echo Operation. and to reduce the frequency of network outages. to increase productivity. To access Cisco Feature Navigator. An account on Cisco. and predictable manner—for measuring network performance. use the “Feature Information for the IP SLAs ICMP Echo Operation” section on page 13. IP SLAs uses active traffic monitoring—the generation of traffic in a continuous. 2008 This module describes how to use the Cisco IOS IP Service Level Agreements (SLAs) Internet Control Message Protocol (ICMP) Echo operation to monitor end-to-end response time between a Cisco router and devices using IPv4 or IPv6. page 3 Americas Headquarters: Cisco Systems.

Information About the IP SLAs ICMP Echo Operation To perform the tasks required to analyze ICMP Echo performance using IP SLA. page 2 ICMP Echo Operation The ICMP Echo operation measures end-to-end response time between a Cisco router and any devices using IP. page 10 Additional References. Restrictions for the IP SLAs ICMP Echo Operation We recommend using a Cisco networking device as the destination device although any networking device that supports RFC 862. Echo protocol. Response time is computed by measuring the time taken between sending an ICMP Echo request message to the destination and receiving an ICMP Echo reply. In Figure 1 ping is used by the ICMP Echo operation to measure the response time between the source IP SLAs device and the destination IP device. page 11 Feature Information for the IP SLAs ICMP Echo Operation. can be used. in-house ping testing. page 10 Where to Go Next.IP SLAs—Analyzing IP Service Levels Using the ICMP Echo Operation Prerequisites for the IP SLAs ICMP Echo Operation • • • • Configuration Examples for the IP SLAs ICMP Echo Operation. Many customers use IP SLAs ICMP-based operations. you should understand the following concept: • ICMP Echo Operation. or ping-based dedicated probes for response time measurements. 2 . page 13 Prerequisites for the IP SLAs ICMP Echo Operation Before configuring the IP SLAs ICMP Echo operation you should be familiar with the “Cisco IOS IP SLAs Overview” chapter of the Cisco IOS IP SLAs Configuration Guide.

use the IP SLAs ICMP Echo operation. How to Configure the IP SLAs ICMP Echo Operation This section contains the following procedure: • Configuring and Scheduling an ICMP Echo Operation. For information on scheduling a group of operations. 2.IP SLAs—Analyzing IP Service Levels Using the ICMP Echo Operation How to Configure the IP SLAs ICMP Echo Operation Figure 1 ICMP Echo Operation The IP SLAs ICMP Echo operation conforms to the same IETF specifications for ICMP ping testing and the two methods result in the same response times. This operation does not require the IP SLAs Responder to be enabled. An ICMP Echo operation measures end-to-end response times between a Cisco router and devices using IP. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. Perform one of the following procedures in this section. enable configure terminal 3 . ICMP Echo is useful for troubleshooting network connectivity issues. SUMMARY STEPS 1. page 3 Configuring and Scheduling an ICMP Echo Operation with Optional Parameters on the Source Device. page 3 (required) Configuring and Scheduling an ICMP Echo Operation To monitor IP connections on a device. page 5 Configuring and Scheduling a Basic ICMP Echo Operation on the Source Device Perform this task to enable and schedule an ICMP Echo operation without any optional parameters. depending on whether you want to configure and schedule a basic ICMP Echo operation or configure and schedule an ICMP Echo operation with optional parameters: • • Configuring and Scheduling a Basic ICMP Echo Operation on the Source Device.

6.IP SLAs—Analyzing IP Service Levels Using the ICMP Echo Operation How to Configure the IP SLAs ICMP Echo Operation 3. Example: Router(config-ip-sla-echo)# exit 4 . 4. Example: Router(config-ip-sla-echo)# frequency 300 Step 6 exit Exits IP SLA ICMP Echo configuration mode and returns to global configuration mode.134 Step 5 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats. Example: Router(config)# ip sla 10 Step 4 icmp-echo {destination-ip-address | destination-hostname} [source-ip {ip-address | hostname} | source-interface interface-name] Defines an ICMP Echo operation and enters IP SLA ICMP Echo configuration mode. • Enter your password if prompted. 5. ip sla operation-number icmp-echo {destination-ip-address | destination-hostname} [source-ip {ip-address | hostname} | source-interface interface-name] frequency seconds exit ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] exit DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode.29. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. 7. 8.139. Example: Router> enable Step 2 configure terminal Enters global configuration mode. Example: Router(config-ip-sla)# icmp-echo 172.

SUMMARY STEPS 1.IP SLAs—Analyzing IP Service Levels Using the ICMP Echo Operation How to Configure the IP SLAs ICMP Echo Operation Command or Action Step 7 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] Purpose Configures the scheduling parameters for an individual IP SLAs operation. Configuring and Scheduling an ICMP Echo Operation with Optional Parameters on the Source Device Perform this task to enable an ICMP Echo operation on the source device and configure some optional IP SLAs parameters. The traffic-class command defines the traffic class byte in the IPv6 header for a supported IP SLAs operation. The flow-label command defines the value in the flow label field in the IPv6 header for a supported IP SLAs operation and is valid only in IPv6 networks. For information on scheduling a group of operations.139.29. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. 2. Example: Router(config)# ip sla schedule 10 start-time now life forever Step 8 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode. ip sla 6 icmp-echo 172.134 source-ip 172. enable configure terminal 5 .132 frequency 300 ! ip sla schedule 6 life forever start-time now What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide.139.29. Example: Router(config)# exit Example The following example shows the configuration of the IP SLAs ICMP Echo operation number 6 that will start immediately and run indefinitely. Note The tos command defines the type of service (ToS) byte in the IPv4 header of an IP SLAs operation and is valid only in IPv4 networks.

verify-data 21. vrf vrf-name 22. 6. flow-label number 20. exit 23. ip sla operation-number icmp-echo {destination-ip-address | destination-hostname} [source-ip {ip-address | hostname} | source-interface interface-name] history buckets-kept size history distributions-of-statistics-kept size history enhanced [interval seconds] [buckets number-of-buckets] history filter {none | all | overThreshold | failures} frequency seconds 10. ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] 24. 7. Example: Router> enable Step 2 configure terminal Enters global configuration mode. 9. history lives-kept lives 12. Example: Router# configure terminal 6 .IP SLAs—Analyzing IP Service Levels Using the ICMP Echo Operation How to Configure the IP SLAs ICMP Echo Operation 3. 4. history statistics-distribution-interval milliseconds 15. request-data-size bytes 14. exit 25. 8. 5. history hours-of-statistics-kept hours 11. timeout milliseconds 18. show ip sla configuration [operation-number] DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. • Enter your password if prompted. tag text 16. owner owner-id 13. threshold milliseconds 17. tos number or traffic-class number 19.

Example: Router(config-ip-sla-echo)# history hours-of-statistics-kept 4 Step 11 history lives-kept lives (Optional) Sets the number of lives maintained in the history table for an IP SLAs operation. Example: Router(config-ip-sla-echo)# history buckets-kept 25 Step 6 history distributions-of-statistics-kept size (Optional) Sets the number of statistics distributions kept per hop during an IP SLAs operation. Example: Router(config-ip-sla-echo)# history distributions-of-statistics-kept 5 Step 7 history enhanced [interval seconds] [buckets number-of-buckets] (Optional) Enables enhanced history gathering for an IP SLAs operation.29.IP SLAs—Analyzing IP Service Levels Using the ICMP Echo Operation How to Configure the IP SLAs ICMP Echo Operation Command or Action Step 3 ip sla operation-number Purpose Begins configuration for an IP SLAs operation and enters IP SLA configuration mode.132 Step 5 history buckets-kept size (Optional) Sets the number of history buckets that are kept during the lifetime of an IP SLAs operation. Example: Router(config-ip-sla-echo)# history filter failures Step 9 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats.29. Example: Router(config-ip-sla)# icmp-echo 172. Example: Router(config-ip-sla-echo)# frequency 30 Step 10 history hours-of-statistics-kept hours (Optional) Sets the number of hours for which statistics are maintained for an IP SLAs operation.134 source-ip 172.139. Example: Router(config-ip-sla-echo)# history enhanced interval 900 buckets 100 Step 8 history filter {none | all | overThreshold | failures} (Optional) Defines the type of information kept in the history table for an IP SLAs operation.139. Example: Router(config-ip-sla-echo)# history lives-kept 5 7 . Example: Router(config)# ip sla 10 Step 4 icmp-echo {destination-ip-address | destination-hostname} [source-ip {ip-address | hostname} | source-interface interface-name] Defines an Echo operation and enters IP SLA Echo configuration mode.

Example: Router(config-ip-sla-echo)# flow-label 112233 8 . defines the flow label field in the IPv6 header for a supported IP SLAs operation. defines the traffic class byte in the IPv6 header for a supported IP SLAs operation. or (Optional) In an IPv6 network only.IP SLAs—Analyzing IP Service Levels Using the ICMP Echo Operation How to Configure the IP SLAs ICMP Echo Operation Command or Action Step 12 owner owner-id Purpose (Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation. Example: Router(config-ip-sla-echo)# owner admin Step 13 request-data-size bytes (Optional) Sets the protocol data size in the payload of an IP SLAs operation's request packet. Example: Router(config-ip-sla-echo)# history statistics-distribution-interval 10 Step 15 tag text (Optional) Creates a user-specified identifier for an IP SLAs operation. Example: Router(config-ip-sla-echo)# request-data-size 64 Step 14 history statistics-distribution-interval milliseconds (Optional) Sets the time interval for each statistics distribution kept for an IP SLAs operation. defines the ToS byte in the IPv4 header of an IP SLAs operation. Example: Router(config-ip-sla-jitter)# tos 160 or Example: Router(config-ip-sla-jitter)# traffic-class 160 Step 19 flow-label number (Optional) In an IPv6 network only. (Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet. Example: Router(config-ip-sla-echo)# tag TelnetPollServer1 Step 16 threshold milliseconds Example: Router(config-ip-sla-echo)# threshold 10000 (Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. Step 17 timeout milliseconds Example: Router(config-ip-sla-echo)# timeout 10000 Step 18 tos number or traffic-class number (Optional) In an IPv4 network only.

Step 22 exit Example: Router(config-ip-sla-echo)# exit Step 23 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation. Router# show ip sla configuration 6 Entry number: 6 Owner: jdoe Tag: SFO-RO Type of operation to perform: echo Target address: 172. Example: Router(config)# ip sla schedule 10 start-time now life forever Step 24 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode. Example: Router(config-ip-sla-echo)# verify-data Step 21 vrf vrf-name Example: Router(config-ip-sla-echo)# vrf vpn-A (Optional) Allows monitoring within Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs) using IP SLAs operations. Example: Router# show ip sla configuration 10 Examples The following sample output shows the configuration of all the IP SLAs parameters (including defaults) for the ICMP Echo operation number 6.134 Source address: 172. Exits ICMP Echo configuration submode and returns to global configuration mode.IP SLAs—Analyzing IP Service Levels Using the ICMP Echo Operation How to Configure the IP SLAs ICMP Echo Operation Command or Action Step 20 verify-data Purpose (Optional) Causes an IP SLAs operation to check each reply packet for data corruption. Example: Router(config)# exit Step 25 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation.29.139.139.29.132 Request size (ARR data portion): 28 Operation timeout (milliseconds): 2000 Type Of Service parameters: 160 Verify data: No Vrf Name: Operation frequency (seconds): 300 Next Scheduled Start Time: Start Time already passed Group Scheduled: FALSE Life (seconds): Forever Entry Ageout (seconds): never 9 .

134 source-ip 172. page 10 Configuring an ICMP Echo Operation: Example The following example shows how to configure an IP SLAs operation type of ICMP Echo that will start immediately and run indefinitely.29.132 frequency 300 request-data-size 28 tos 160 timeout 2000 tag SFO-RO ip sla schedule 6 life forever start-time now Where to Go Next For information about other types of IP SLAs operations and IP SLAs features. each operation response is checked for corruption. • What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. ip sla 6 icmp-echo 172.IP SLAs—Analyzing IP Service Levels Using the ICMP Echo Operation Configuration Examples for the IP SLAs ICMP Echo Operation Recurring (Starting Everyday): FALSE Status of entry (SNMP RowStatus): Active Threshold (milliseconds): 5000 Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20 Number of history Lives kept: 0 Number of history Buckets kept: 15 History Filter Type: None Enhanced History: Troubleshooting Tips • If the IP SLAs operation is not running and generating statistics. Configuration Examples for the IP SLAs ICMP Echo Operation This section contains the following configuration example: • Configuring an ICMP Echo Operation: Example. When enabled. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. see the Cisco IOS IP SLAs Features Roadmap. 10 . add the verify-data command to the configuration of the operation (while configuring in IP SLA configuration mode) to enable data verification. Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation.29. Use the verify-data command with caution during normal operations because it generates unnecessary overhead.139.139.

cisco. Related Documents Related Topic Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands Document Title Cisco IOS IP Service Level Agreements Command Line Interface. MIBs MIBs CISCO-RTTMON-MIB MIBs Link To locate and download MIBs for selected platforms. and support for existing standards has not been modified by this feature. Cisco IOS releases.com/go/mibs RFCs RFCs RFC 862 Title Echo Protocol 11 . use Cisco MIB Locator found at the following URL: http://www.IP SLAs—Analyzing IP Service Levels Using the ICMP Echo Operation Additional References Additional References The following sections provide references related to monitoring IP connections using an IP SLAs ICMP Echo operation. Cisco white paper Cisco IOS IP SLAs Command Reference Standards Standards Title No new or modified standards are supported by this — feature. and feature sets.

cisco. including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. and Really Simple Syndication (RSS) Feeds. the Cisco Technical Services Newsletter. To receive security and technical information about your products.com user ID and password. Access to most tools on the Cisco Support website requires a Cisco. such as the Product Alert Tool (accessed from Field Notices). you can subscribe to various services. Link http://www.com/techsupport 12 .IP SLAs—Analyzing IP Service Levels Using the ICMP Echo Operation Additional References Technical Assistance Description The Cisco Support website provides extensive online resources.

12. and figures included in the document are shown for illustrative purposes only. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release. Inc.com is not required.2(33)SRC. Linksys. The use of the word partner does not imply a partnership relationship between Cisco and any other company.2(31)SB2. Play. 12. Catalyst. ProConnect. Inc. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Live. Any examples. An account on Cisco. and Welcome to the Human Network are trademarks. CCDP. TransPath. and Access Registrar. CCDA. Follow Me Browsing. GigaDrive.IP SLAs—Analyzing IP Service Levels Using the ICMP Echo Operation Feature Information for the IP SLAs ICMP Echo Operation Feature Information for the IP SLAs ICMP Echo Operation Table 1 lists the release history for this feature. the Cisco Certified Internetwork Expert logo.2(33)SXH. Changing the Way We Work. SenderBase. UDP Echo. MeetingPlace. Cisco StadiumVision. Network Registrar. iPhone. the iQ logo. The Fastest Way to Increase Your Internet Quotient. PIX.cisco. Cisco Systems Capital. CCDE. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. ScriptShare.2(33)SRB1. All rights reserved. EtherSwitch. Table 1 Feature Information for the IP SLAs ICMP Echo Operation Feature Name IP SLAs ICMP Echo Operation Releases 12. EtherFast. WebEx. Cisco IOS XE Release 2. and Learn and Cisco Store are service marks. Event Center. command display output. feature set. iQ Expertise. Fast Step. the IronPort logo. Cisco Nexus. Not all commands may be available in your Cisco IOS software release. iQuick Study. Cisco IOS.2(33)SB. Bringing the Meeting To You. FormShare. Cisco Press. Unless noted otherwise. HomeLink. MeetingPlace Chime Sound. MGX. LightStream. 12. To access Cisco Feature Navigator. CCVP. the Cisco Systems logo.1 12. Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Networking Academy. CCNA. CCIP. SMARTnet. Cisco Lumin. PowerPanels. All other trademarks mentioned in this document or Website are the property of their respective owners. 13 . Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Unity. see the command reference documentation. TCP Connect) Support was added for operability in IPv6 networks. Cisco Systems. the Cisco logo. go to http://www. iQ Net Readiness Scorecard. Cisco. Cisco Eos. Spectrum Expert.4(20)T Feature Information The Cisco IOS IP SLAs Internet Control Message Protocol (ICMP) echo operation allows you to measure end-to-end network response time between a Cisco device and other devices using IP. and the WebEx logo are registered trademarks of Cisco Systems. Collaboration Without Limitation. IOS. Networkers. ICMP Echo. For release information about a specific command. CCNP. CCIE. CCENT. © 2006-2008 Cisco Systems. 12. Aironet. DCE. Internet Quotient. AsyncOS. IronPort. MediaTone. or platform.com/go/cfn. StackWise. and/or its affiliates in the United States and certain other countries. 12.3(14)T. CCSP. PCNow. Cisco TelePresence. IP SLAs for IPv6 (UDP Jitter. subsequent releases of that Cisco IOS software release train also support that feature.

IP SLAs—Analyzing IP Service Levels Using the ICMP Echo Operation Feature Information for the IP SLAs ICMP Echo Operation 14 .

and to reduce the frequency of network outages. IP SLAs uses active traffic monitoring—the generation of traffic in a continuous. and predictable manner—for measuring network performance. which allows Cisco customers to analyze IP service levels for IP applications and services. An account on Cisco. .IP SLAs—Analyzing IP Service Levels Using the ICMP Path Echo Operation First Published: August 14.. To access Cisco Feature Navigator. page 2 Restrictions for the IP SLAs ICMP Path Echo Operation. reliable.com is not required. page 3 Americas Headquarters: Cisco Systems. 170 West Tasman Drive. to lower operational costs. IP SLAs is a portfolio of technology embedded in most devices that run Cisco IOS software. page 2 How to Configure the IP SLAs ICMP Path Echo Operation. San Jose. page 2 Information About the IP SLAs ICMP Path Echo Operation. 2006 Last Updated: July 16. Contents • • • • Prerequisites for the IP SLAs ICMP Path Echo Operation. Inc. CA 95134-1706 USA © 2007 Cisco Systems.cisco. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported. The results of the ICMP Path Echo operation can be displayed and analyzed to determine how ICMP is performing. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. Inc. ICMP Path Echo is useful for determining network availability and for troubleshooting network connectivity issues. to increase productivity.com/go/cfn. use the “Feature Information for the IP SLAs ICMP Path Echo Operation” section on page 14. go to http://www. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module. All rights reserved. 2008 This module describes how to use the Cisco IOS IP Service Level Agreements (SLAs) Internet Control Message Protocol (ICMP) Path Echo operation to monitor end-to-end and hop-by-hop response time between a Cisco router and devices using IP.

page 2 ICMP Path Echo Operation The IP SLAs ICMP Path Echo operation records statistics for each hop along the path that the IP SLAs operation takes to reach its destination. The ICMP Path Echo operation determines this hop-by-hop response time between a Cisco router and any IP device on the network by discovering the path using the traceroute facility. page 12 Feature Information for the IP SLAs ICMP Path Echo Operation. A ping is then used to measure the response time between the source IP SLAs device and each subsequent hop in the path to the destination IP device.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Echo Operation Prerequisites for the IP SLAs ICMP Path Echo Operation • • • • Configuration Examples for the IP SLAs ICMP Path Echo Operation. Echo protocol. Information About the IP SLAs ICMP Path Echo Operation To perform the tasks required to monitor ICMP Path Echo performance using IP SLA. you should understand the following concept: • ICMP Path Echo Operation. page 14 Prerequisites for the IP SLAs ICMP Path Echo Operation Before configuring the IP SLAs ICMP Path Echo operation you should be familiar with the “Cisco IOS IP SLAs Overview” chapter of the Cisco IOS IP SLAs Configuration Guide. can be used. Restrictions for the IP SLAs ICMP Path Echo Operation We recommend using a Cisco networking device as the destination device although any networking device that supports RFC 862. page 11 Where to Go Next. In Figure 1 the source IP SLAs device uses traceroute to discover the path to the destination IP device. 2 . page 12 Additional References.

page 6 Configuring and Scheduling a Basic ICMP Path Echo Operation on the Source Device Perform this task to enable and schedule an ICMP Path Echo operation without any optional parameters. An ICMP Path Echo operation measures end-to-end and hop-by-hop response time between a Cisco router and devices using IP.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Echo Operation How to Configure the IP SLAs ICMP Path Echo Operation Figure 1 ICMP Path Echo Operation ICMP Path Echo operation Hop 1 Source IP SLA device Hop 2 Destination IP device Using the statistics recorded for the response times and availability. Note For information on scheduling a group of operations. depending on whether you want to configure and schedule a basic ICMP Path Echo operation or configure and schedule an ICMP Path Echo operation with optional parameters: • • Configuring and Scheduling a Basic ICMP Path Echo Operation on the Source Device. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. 121420 3 . page 3 (required) Configuring and Scheduling an ICMP Path Echo Operation To monitor ICMP Path Echo performance on a device. the ICMP Path Echo operation can identify a hop in the path that is causing a bottleneck. Perform one of the following procedures in this section. This operation does not require the IP SLAs Responder to be enabled. page 3 Configuring and Scheduling an ICMP Path Echo Operation with Optional Parameters on the Source Device. How to Configure the IP SLAs ICMP Path Echo Operation This section contains the following procedure: • Configuring and Scheduling an ICMP Path Echo Operation. use the IP SLAs ICMP Path Echo operation. ICMP Path Echo is useful for determining network availability and for troubleshooting network connectivity issues.

3. 7. 2. 6.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Echo Operation How to Configure the IP SLAs ICMP Path Echo Operation SUMMARY STEPS 1. enable configure terminal ip sla operation-number path-echo {destination-ip-address | destination-hostname} [source-ip {ip-address | hostname}] frequency seconds exit ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] exit 4 . 4. 8. 5.

Example: Router(config-ip-sla)# path-echo protocol 172. Example: Router# configure terminal Step 3 ip sla operation-id Specifies an ID number for the operation being configured.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Echo Operation How to Configure the IP SLAs ICMP Path Echo Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. Example: Router(config-ip-sla-pathEcho)# exit Step 7 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation.134 Step 5 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats.139. Example: Router(config)# exit Example The following example shows the configuration of the IP SLAs ICMP Path Echo operation number 7 that will start in 30 seconds and run for 5 minutes. and enters IP SLA configuration mode. Example: Router(config-ip-sla-pathEcho)# frequency 30 Step 6 exit Exits IP SLA Path Echo configuration mode and returns to global configuration mode. • Enter your password if prompted. Example: Router(config)# ip sla 7 Step 4 path-echo {destination-ip-address | destination-hostname} [source-ip {ip-address | hostname}] Defines a Path Echo operation and enters IP SLA Path Echo configuration mode. Example: Router(config)# ip sla schedule 10 start-time now life forever Step 8 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode. Example: Router> enable Step 2 configure terminal Enters global configuration mode. ip sla 7 5 .29.

enable configure terminal ip sla operation-number path-echo {destination-ip-address | destination-hostname} [source-ip {ip-address | hostname}] history buckets-kept size history distributions-of-statistics-kept size history enhanced [interval seconds] [buckets number-of-buckets] history filter {none | all | overThreshold | failures} frequency seconds 10. tos number 21.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Echo Operation How to Configure the IP SLAs ICMP Path Echo Operation path-echo 172. 4. 9. 6.29.139. 3. samples-of-history-kept samples 16.134 frequency 30 ! ip sla schedule 7 start-time after 00:00:30 life 300 What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. 2. paths-of-statistics-kept size 14. tag text 18. owner owner-id 13. timeout milliseconds 20. history lives-kept lives 12. history hours-of-statistics-kept hours 11. Configuring and Scheduling an ICMP Path Echo Operation with Optional Parameters on the Source Device Perform this task to enable an ICMP Path Echo operation on the source device and configure some optional IP SLAs parameters. history statistics-distribution-interval milliseconds 17. 5. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. Note For information on scheduling a group of operations. request-data-size bytes 15. 8. verify-data 6 . Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. SUMMARY STEPS 1. threshold milliseconds 19. 7.

show ip sla configuration [operation-number] 7 . exit 26. ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] 25.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Echo Operation How to Configure the IP SLAs ICMP Path Echo Operation 22. exit 24. vrf vrf-name 23.

IP SLAs—Analyzing IP Service Levels Using the ICMP Path Echo Operation How to Configure the IP SLAs ICMP Path Echo Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. Example: Router(config-ip-sla-pathEcho)# history buckets-kept 25 Step 6 history distributions-of-statistics-kept size (Optional) Sets the number of statistics distributions kept per hop during an IP SLAs operation. Example: Router(config)# ip sla 10 Step 4 path-echo {destination-ip-address | destination-hostname} [source-ip {ip-address | hostname}] Defines a Path Echo operation and enters IP SLA Path Echo configuration mode.134 Step 5 history buckets-kept size (Optional) Sets the number of history buckets that are kept during the lifetime of an IP SLAs operation. Example: Router(config-ip-sla-pathEcho)# frequency 30 8 . Example: Router(config-ip-sla-pathEcho)# history distributions-of-statistics-kept 5 Step 7 history enhanced [interval seconds] [buckets number-of-buckets] (Optional) Enables enhanced history gathering for an IP SLAs operation. Example: Router(config-ip-sla-pathEcho)# history filter failures Step 9 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats. Example: Router> enable Step 2 configure terminal Enters global configuration mode. Example: Router(config-ip-sla)# path-echo 172. • Enter your password if prompted. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode.139.29. Example: Router(config-ip-sla-pathEcho)# history enhanced interval 900 buckets 100 Step 8 history filter {none | all | overThreshold | failures} (Optional) Defines the type of information kept in the history table for an IP SLAs operation.

Example: Router(config-ip-sla-pathEcho)# history statistics-distribution-interval 10 Step 17 tag text (Optional) Creates a user-specified identifier for an IP SLAs operation. Example: Router(config-ip-sla-pathEcho)# tag TelnetPollServer1 Step 18 threshold milliseconds Example: Router(config-ip-sla-pathEcho)# threshold 10000 (Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. Example: Router(config-ip-sla-pathEcho)# history lives-kept 5 Step 12 owner owner-id (Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation. 9 . Example: Router(config-ip-sla-pathEcho)# history hours-of-statistics-kept 4 Step 11 history lives-kept lives (Optional) Sets the number of lives maintained in the history table for an IP SLAs operation. Example: Router(config-ip-sla-pathEcho)# samples-of-history-kept 10 Step 16 history statistics-distribution-interval milliseconds (Optional) Sets the time interval for each statistics distribution kept for an IP SLAs operation. Example: Router(config-ip-sla-pathEcho)# request-data-size 64 Step 15 samples-of-history-kept samples (Optional) Sets the number of entries kept in the history table per bucket for an IP SLAs operation. Example: Router(config-ip-sla-pathEcho)# paths-of-statistics-kept 3 Step 14 request-data-size bytes (Optional) Sets the protocol data size in the payload of an IP SLAs operation's request packet. Example: Router(config-ip-sla-pathEcho)# owner admin Step 13 paths-of-statistics-kept size (Optional) Sets the number of paths for which statistics are maintained per hour for an IP SLAs operation.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Echo Operation How to Configure the IP SLAs ICMP Path Echo Operation Command or Action Step 10 history hours-of-statistics-kept hours Purpose (Optional) Sets the number of hours for which statistics are maintained for an IP SLAs operation.

Example: Router(config)# ip sla schedule 10 start-time now life forever Step 25 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode. Router# show ip sla configuration 7 Complete configuration Table (includes defaults) Entry number: 7 Owner: jdoe Tag: SGN-RO Type of operation to perform: pathEcho 10 . Example: Router(config)# exit Step 26 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation. Example: Router(config-ip-sla-pathEcho)# tos 160 Step 21 verify-data (Optional) Causes an IP SLAs operation to check each reply packet for data corruption. Example: Router# show ip sla configuration 10 Examples The following sample output shows the configuration of all the IP SLAs parameters (including defaults) for the ICMP Path Echo operation number 7.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Echo Operation How to Configure the IP SLAs ICMP Path Echo Operation Command or Action Step 19 timeout milliseconds Purpose (Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet. Example: Router(config-ip-sla-pathEcho)# verify-data Step 22 vrf vrf-name Example: Router(config-ip-sla-pathEcho)# vrf vpn-A (Optional) Allows monitoring within Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs) using IP SLAs operations. Step 23 exit Example: Router(config-ip-sla-pathEcho)# exit Step 24 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation. Exits Path Echo configuration submode and returns to global configuration mode. Example: Router(config-ip-sla-pathEcho)# timeout 10000 Step 20 tos number (Optional) Defines a type of service (ToS) byte in the IP header of an IP SLAs operation.

Configuration Examples for the IP SLAs ICMP Path Echo Operation This section contains the following example: • Configuring an ICMP Path Echo Operation: Example.139. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. • What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command.134 Source address: 172. each operation response is checked for corruption. When enabled. add the verify-data command to the configuration of the operation (while configuring in IP SLA configuration mode) to enable data verification. Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation. Use the verify-data command with caution during normal operations because it generates unnecessary overhead.139. page 12 11 .29.132 Request size (ARR data portion): 28 Operation timeout (milliseconds): 1000 Type Of Service parameters: 256 Verify data: No Loose Source Routing: Disabled Vrf Name: LSR Path: Operation frequency (seconds): 30 Next Scheduled Start Time: Start Time already passed Group Scheduled: FALSE Life (seconds): 300 Entry Ageout (seconds): never Recurring (Starting Everyday): FALSE Status of entry (SNMP RowStatus): Active Threshold (milliseconds): 5000 Number of statistic hours kept: 2 Number of statistic paths kept: 5 Number of statistic hops kept: 16 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20 Number of history Lives kept: 0 Number of history Buckets kept: 15 Number of history Samples kept: 16 History Filter Type: None Troubleshooting Tips • If the IP SLAs operation is not running and generating statistics.29.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Echo Operation Configuration Examples for the IP SLAs ICMP Path Echo Operation Target address: 172.

IP SLAs—Analyzing IP Service Levels Using the ICMP Path Echo Operation Where to Go Next Configuring an ICMP Path Echo Operation: Example The following example shows how to configure an IP SLAs operation type of ICMP Path Echo that will start after 30 seconds and run for 5 minutes. 12 47912 . see the Cisco IOS IP SLAs Features Roadmap.139. The operation attempts to execute three times in 25 seconds (first attempt at 0 seconds). Additional References The following sections provide references related to monitoring ICMP Path Echo operations using IP SLA. Figure 2 depicts the ICMP Path Echo operation. Figure 2 ICMP Path Echo Operation Controlling Host 1 Host 2 Router A Operation 3 Router B Performance management application This example sets a Path Echo operation from Router B to Router A using IP/ICMP. Router B Configuration ip sla 3 path-echo 172.29.134 frequency 10 tag SGN-RO timeout 1000 ip sla schedule 3 life 25 Where to Go Next For information about other types of IP SLAs operations and IP SLAs features.

MIBs MIBs CISCO-RTTMON-MIB MIBs Link To locate and download MIBs for selected platforms. Cisco white paper Cisco IOS IP SLAs Command Reference Standards Standards Title No new or modified standards are supported by this — feature. and feature sets. use Cisco MIB Locator found at the following URL: http://www. technical tips.com/go/mibs RFCs RFCs RFC 862 Title Echo Protocol Technical Assistance Description Technical Assistance Center (TAC) home page.000 pages of searchable technical content. including links to products.com users can log in from this page to access even more content. Registered Cisco.com/public/support/tac/home. technologies. containing 30. Link http://www. and support for existing standards has not been modified by this feature.cisco. Cisco IOS releases. solutions.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Echo Operation Additional References Related Documents Related Topic Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands Document Title Cisco IOS IP Service Level Agreements Command Line Interface.cisco. and tools.shtml 13 .

Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release. CCSP. 12. Table 1 Feature Information for the IP SLAs ICMP Path Echo Operation Feature Name IP SLAs ICMP Path Echo Operation Releases 12. Catalyst. Cisco.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Echo Operation Feature Information for the IP SLAs ICMP Path Echo Operation Feature Information for the IP SLAs ICMP Path Echo Operation Table 1 lists the release history for this feature. Use Cisco Feature Navigator to find information about platform support and software image support. MGX. Cisco Systems Capital. Aironet. the Cisco logo. Cisco Eos. Cisco TelePresence. go to http://www. MeetingPlace. WebEx. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses.1 Feature Information The Cisco IOS IP SLAs Internet Control Message Protocol (ICMP) path echo operation allows you to measure end-to-end and hop-by-hop network response time between a Cisco device and other devices using IP. iQ Net Readiness Scorecard. Unless noted otherwise.2(33)SRB1.cisco. Networkers. Cisco Lumin. Network Registrar. The use of the word partner does not imply a partnership relationship between Cisco and any other company. Follow Me Browsing. and Access Registrar.com/go/cfn. CCVP. 14 . Any use of actual IP addresses in illustrative content is unintentional and coincidental. CCDA. Inc. Cisco Unity. or platform. To access Cisco Feature Navigator. Cisco IOS XE Release 2. AsyncOS. EtherFast.3(14)T. command display output. DCE. Live. and Learn and Cisco Store are service marks. Cisco Press. EtherSwitch. subsequent releases of that Cisco IOS software release train also support that feature.2(33)SXH. CCIP. CCIE. and figures included in the document are shown for illustrative purposes only. The Fastest Way to Increase Your Internet Quotient. and the WebEx logo are registered trademarks of Cisco Systems. Cisco Systems. Collaboration Without Limitation. Cisco Nexus. and/or its affiliates in the United States and certain other countries. CCDE. Play. ScriptShare. and Welcome to the Human Network are trademarks. Cisco StadiumVision. Networking Academy. IronPort. Inc.com is not required. CCENT. TransPath. CCNA. iQuick Study. Not all commands may be available in your Cisco IOS software release. MediaTone. © 2006-2008 Cisco Systems. ProConnect. PCNow. SMARTnet. Event Center. the IronPort logo. PowerPanels. iPhone.2(31)SB2. StackWise. All rights reserved. PIX. iQ Expertise. 12. SenderBase. All other trademarks mentioned in this document or Website are the property of their respective owners. Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. FormShare. Changing the Way We Work. Bringing the Meeting To You. Fast Step. CCNP. the Cisco Certified Internetwork Expert logo. the iQ logo. the Cisco Systems logo. MeetingPlace Chime Sound. Internet Quotient. Spectrum Expert. An account on Cisco. Cisco IOS. CCDP. HomeLink. see the command reference documentation. For release information about a specific command. GigaDrive. LightStream. Linksys. 12. feature set. Any examples. IOS.

IP SLAs—Analyzing IP Service Levels Using the ICMP Path Jitter Operation First Published: August 14. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. and to reduce occurrences of network congestion or outages. page 9 Americas Headquarters: Cisco Systems.cisco. on the destination device. and predictable manner—for measuring network performance.com is not required. To access Cisco Feature Navigator. San Jose. Contents • • • • Prerequisites. Inc. All rights reserved. use the “Feature Information for the IP SLAs ICMP Path Jitter Operation” section on page 12. page 2 Information About the IP SLAs ICMP Path Jitter Operation. This document also demonstrates how the data gathered using the Path Jitter operations can be displayed and analyzed using the Cisco IOS CLI. .com/go/cfn.. to lower operational costs. Inc. Cisco IOS IP SLAs is an embedded feature set in Cisco IOS software that allows you to analyze IP service levels for IP applications and services. to increase productivity. CA 95134-1706 USA © 2007 Cisco Systems. page 2 How to Configure the IP SLAs ICMP Path Jitter Operation. IP SLAs uses active traffic monitoring—the generation of traffic in a continuous. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module. 2006 Last Updated: July 16. The accuracy of measured data is enhanced by enabling the IP SLAs responder. 2008 This document describes how to use the Cisco IOS IP Service Level Agreements (SLAs) ICMP Path Jitter operation to monitor hop-by-hop jitter (inter-packet delay variance). 170 West Tasman Drive. page 2 Configuration Examples for the IP SLAs ICMP Path Jitter Operation. available in Cisco routers. go to http://www. reliable. An account on Cisco. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported.

you should understand the following concept: • ICMP Path Jitter Operation. For example. with a time interval of T milliseconds between each Echo probe. packet loss. page 12 Prerequisites Before configuring the IP SLAs ICMP Path Jitter operation you should be familiar with the “Cisco IOS IP SLAs Overview” chapter of the Cisco IOS IP SLAs Configuration Guide. Information About the IP SLAs ICMP Path Jitter Operation To perform the tasks required to monitor ICMP Path Jitter performance using IP SLA.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Jitter Operation Prerequisites • • • Where to Go Next. The ICMP Path Jitter operation can be used a supplement to the standard UDP Jitter operation. as shown here: 2 . The Path Jitter operation functions differently than the standard UDP Jitter operation. page 10 Additional References. then sending N number of Echo probes to each hop along the traced path. The attributes are user-configurable. and then uses ICMP echoes to determine the response times. page 2 ICMP Path Jitter Operation The IP SLAs ICMP Path Jitter operation provides hop-by-hop jitter. the ICMP Path Jitter operation could then be used to troubleshoot the network path and determine if traffic is bottlenecking in a particular segment along the transmission path. and delay measurement statistics in an IP network. page 2 (required) Configuring and Scheduling a ICMP Path Jitter Operation The ICMP Path Jitter operation functions by tracing the IP path from a source device to a specified destination device. The operation first discovers the hop-by-hop IP route from the source to the destination using a traceroute utility. The operation as a whole is repeated at a frequency of once every F seconds. configuration and performance data can only be obtained using the CLI. How to Configure the IP SLAs ICMP Path Jitter Operation This section contains the following procedure: • Configuring and Scheduling a ICMP Path Jitter Operation. which provides total one-way data and total round-trip data. page 10 Feature Information for the IP SLAs ICMP Path Jitter Operation. results from the UDP Jitter operation may indicate unexpected delays or high jitter values. packet loss and approximate jitter values for each hop along the path. The jitter values obtained using the ICMP Path Jitter operation are approximates because ICMP only provides round trip times. The ICMP Path Jitter operation is not supported in the RTTMON MIB.

ICMP performance also can be affected by the configuration of priority queueing on the router and by ping response. • • Configuring and Scheduling a Basic ICMP Path Jitter Operation. ICMP-based operations can compensate for source processing delay but cannot compensate for target processing delay. 3 . page 3 Configuring and Scheduling an ICMP Path Jitter Operation with Additional Parameters. see the “Cisco IOS IP SLAs Overview” chapter of the Cisco IOS IP SLAs Configuration Guide. The jitter values obtained using the ICMP Path Jitter operation are approximates because ICMP does not provide the capability to embed processing times on routers in the packet. and statistics can only be returned using CLI show ip sla commands. Configuring and Scheduling a Basic ICMP Path Jitter Operation Perform the following steps to configure and schedule an ICMP Path Jitter operation using the general default characteristics for the operation. However. num-packets option path-jitter command. the IP SLAs Responder does not have to be enabled on either the target device or intermediate devices for Path Jitter operations.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Jitter Operation How to Configure the IP SLAs ICMP Path Jitter Operation Path Jitter Operation Parameter Number of echo probes (N) Time between Echo probes. If the target router does not place ICMP packets as the highest priority. the ICMP Path Jitter operation is not supported in the RTTMON MIB. once every 60 seconds frequency command Perform one of the following procedures in this section. Start in Privileged Exec mode. Note Before configuring any IP SLAs application. for information about the IP SLAs Responder and the IP SLAs Control Protocol. depending on whether you want to configure and schedule a basic ICMP Path Jitter operation or configure and schedule an ICMP Jitter Operation with additional parameters. page 6 Restrictions • The IP SLAs ICMP Path Jitter operation is ICMP-based. use of the IP SLAs UDP Jitter operation is recommended. For more robust monitoring and verifying. Unlike other IP SLAs operations. interval option Note The operation’s frequency is different than the operation’s interval. • • Note In contrast with other IP SLAs operations. in milliseconds (T) The frequency of how often the operation is repeated (F) Default 10 echos 20 ms Configured Using: path-jitter command. then the router will not respond properly. you can use the show ip sla application command to verify that the operation type is supported on your software image. Path Jitter operations can only be configured using the CLI. the operational efficiency may improve if you enable the IP SLAs Responder.

4. 5. 3. 7.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Jitter Operation How to Configure the IP SLAs ICMP Path Jitter Operation SUMMARY STEPS 1. 6. 2. enable configure terminal ip sla operation-number path-jitter {destination-ip-address | destination-hostname} [source-ip {ip-address | hostname}] [num-packets packet-number] [interval milliseconds] [targetOnly] frequency seconds exit ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] exit 4 . 8.

Example: Router(config)# ip sla schedule 10 start-time now life forever Step 8 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode. echo probes will be sent to the destination only. With this version of the command.129 source-ip 10. 5 . Example: Router(config)# exit Examples In the following example. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. Example: Router(config-ip-sla-pathJitter)# exit Step 7 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation.31.2. • Enter your password if prompted. Example: Router(config-ip-sla-pathJitter)# frequency 30 Step 6 exit Exits path jitter configuration submode and returns to global configuration mode.1 num-packets 12 interval 22 Step 5 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats.30.1. Example: Router(config)# ip sla 10 Step 4 path-jitter {destination-ip-address | destination-hostname} [source-ip {ip-address | hostname}] [num-packets packet-number] [interval milliseconds] [targetOnly] Defines an ICMP Path Jitter operation and enters IP SLA Path Jitter configuration mode. Example: Router> enable Step 2 configure terminal Enters global configuration mode. the targetOnly keyword is used to bypass the hop-by-hop measurements.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Jitter Operation How to Configure the IP SLAs ICMP Path Jitter Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. Example: Router(config-ip-sla)# path-jitter 172.

SUMMARY STEPS 1. samples-of-history-kept. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. Restrictions The IP SLAs Path Jitter operation does not support the IP SLAs History feature (statistics history buckets) because of the large data volume involved with Jitter operations. 3. enable configure terminal ip sla operation-number path-jitter {destination-ip-address | destination-hostname} [source-ip {ip-address | hostname}] [num-packets packet-number] [interval milliseconds] [targetOnly] frequency seconds owner owner-id request-data-size bytes tag text timeout milliseconds 10. 2.17. 9. 8. 6. Configuring and Scheduling an ICMP Path Jitter Operation with Additional Parameters Perform the following steps to configure and schedule an ICMP Path Jitter operation with additional parameters.20 num-packets 50 interval 30 targetOnly What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. This means that the following IP SLAs commands are not supported for Jitter operations: history buckets-kept. Start in Privileged Exec mode.246. using any of the optional commands needed. and show ip sla history. history filter. 5. exit 14. history lives-kept. vrf vrf-name 11. ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] 13.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Jitter Operation How to Configure the IP SLAs ICMP Path Jitter Operation Router(config)# ip sla 1 Router(config-ip-sla)# path-jitter 172. 4. show ip sla configuration [operation-number] 6 . exit 12. 7.

1. Example: Router(config-ip-sla-pathJitter)# tag TelnetPollServer1 Step 9 timeout milliseconds (Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Jitter Operation How to Configure the IP SLAs ICMP Path Jitter Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. Example: Router(config-ip-sla-pathJitter)# frequency 30 Step 6 owner owner-id (Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation. • Enter your password if prompted. Example: Router(config-ip-sla-pathJitter)# owner admin Step 7 request-data-size bytes (Optional) Sets the protocol data size in the payload of an IP SLAs operation's request packet. Example: Router> enable Step 2 configure terminal Enters global configuration mode. Example: Router(config-ip-sla)# path-jitter 172.30.129 source-ip 10.1 num-packets 12 interval 22 Step 5 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats. Example: Router(config)# ip sla 10 Step 4 path-jitter {destination-ip-address | destination-hostname} [source-ip {ip-address | hostname}] [num-packets packet-number] [interval milliseconds] [targetOnly] Defines an ICMP Path Jitter operation and enters IP SLA Path Jitter configuration mode. Example: Router(config-ip-sla-pathJitter)# timeout 10000 7 .31. Example: Router(config-ip-sla-pathJitter)# request-data-size 64 Step 8 tag text (Optional) Creates a user-specified identifier for an IP SLAs operation.2.

Example: Router(config)# ip sla schedule 10 start-time now life forever Step 13 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode. do not apply to Path Jitter operations: • • • • • • • • • • • • history buckets-kept history distributions-of-statistics-kept history enhanced history filter history hours-of-statistics-kept history lives-kept lsr-path samples-of-history-kept history statistics-distribution-interval tos threshold verify-data Examples In the following example.130: 8 . available in Path Jitter configuration mode. Example: Router(config)# exit Step 14 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation. Example: Router# show ip sla configuration 10 The following commands.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Jitter Operation How to Configure the IP SLAs ICMP Path Jitter Operation Command or Action Step 10 vrf vrf-name Purpose (Optional) Allows monitoring within Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs) using IP SLAs operations.3. Example: Router(config-ip-sla-pathJitter)# vrf vpn-A Step 11 exit Example: Router(config-ip-sla-pathJitter)# exit Step 12 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation. Exits Path Jitter configuration submode and returns to global configuration mode. a Path Jitter operation is configured to run over a VPN using the VRF “red” to the CE at 10.30.

17.129 Number of packets: 20 Interval (milliseconds): 20 Target Only: Disabled Request size (ARR data portion): 28 9 .129 num-packets 20 .3.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Jitter Operation Configuration Examples for the IP SLAs ICMP Path Jitter Operation Router# configure terminal Enter configuration commands.165. .1. and the number of packets in each echo is changed to 20. 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 the IP SLAs ICMP Path Jitter Operation This section contains the following examples: • Configuring a Path Jitter Operation: Example.246. one per line. page 9 Configuring a Path Jitter Operation: Example In the following example. .20 num-packets 50 interval 30 targetOnly Troubleshooting Tips Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation. Router(config)# ip sla 1 router(config-ip-sla)# path-jitter 172.225 source-ip 172. the ICMP Path Jitter operation is configured with an explicit source IP address.200.31. With this version of the command. Router# configure terminal Router(config)# ip sla 10 Router(config-ip-sla)# path-jitter 209.1.130 Router(config-ip-sla-pathJitter)# vrf red Router(config-ip-sla-pathJitter)# exit Router(config)# ip sla schedule 7 start-time now life forever In the following example.165.200.30. the targetOnly keyword is used to bypass the hop-by-hop measurements. Router# show ip sla configuration 10 Entry Number: 10 Owner: Tag: Type of operation to perform: pathJitter Destination address: 209.225 Source address: 172. End with the end command. Router(config)# ip sla 7 Router(config-ip-sla)# path-jitter 10. What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. echo probes will be sent to the destination only.31.

471 UTC Tue Sep 14 2004 Diagnostics Text: Last Time this Entry was Reset: Never Number of Octets in use by this Entry: 1882 Number of Operations Attempted: 1 Current Seconds Left in Life: 3586 Operational State of Entry: active Latest Completion Time Average (milliseconds): 4 Latest Operation Start Time: 15:41:43. 10 .112.129 TR 10 10 10 10 10 10 RTT 1 1 1 1 1 1 PL 0 0 0 0 0 0 DS 0 0 0 0 0 0 OS 0 0 0 0 0 0 Jitter(RFC 1889) 0 0 0 0 0 0 Where to Go Next For information about other types of IP SLAs operations and IP SLAs features.TR = Total Receives. OS = Out Of Sequence Echo Replies HopAddress 10.69. PL = Packet Loss.122 171. see the Cisco IOS IP SLAs Features Roadmap.4.1.69.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Jitter Operation Where to Go Next Operation timeout (milliseconds): 5000 Type Of Service parameters: 0x0 Verify data: No Loose Source Routing: Disabled Vrf Name: LSR Path: Operation frequency (seconds): 60 Next Scheduled Start Time: Already Started Group Scheduled : FALSE Life (seconds): 3600 Entry Ageout (seconds): never Recurring (Starting Everyday): FALSE Status of entry (SNMP RowStatus): notInService Threshold (milliseconds): 0 Router# show ip sla statistics Current Operational State Entry Number: 10 Modification Time: 21:12:32.22. DS = Discarded Samples.2.24.21.1 172.000 UTC Tue Sep 19 2000 Path Jitter Statistics: Legend .30.16 171.5.6 171. Additional References The following sections provide references related to monitoring UDP echo operations using IP SLA.69.1 172. RTT = Round Trip Time (Avg).

shtml 11 . MIBs Link To locate and download MIBs for selected platforms.cisco. Cisco white paper Cisco IOS IP SLAs Command Reference Standards Standards Title No new or modified standards are supported by this — feature. technologies. Link http://www. Registered Cisco. including links to products.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Jitter Operation Additional References Related Documents Related Topic Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands Document Title Cisco IOS IP Service Level Agreements Command Line Interface.com/go/mibs RFCs RFCs RFC 1889 1 Title RTP: A Transport Protocol for Real-Time Applications.000 pages of searchable technical content. technical tips. see the section “Estimating the Interarrival Jitter” 1. Technical Assistance Description Technical Assistance Center (TAC) home page.com/public/support/tac/home. Support for the listed RFC is not claimed.com users can log in from this page to access even more content.cisco. solutions. and feature sets. use Cisco MIB Locator found at the following URL: http://www. Cisco IOS releases. and support for existing standards has not been modified by features in this document. MIBs MIBs MIB support for the Path Jitter operation is not provided. and tools. listed as a reference only. containing 30.

Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. FormShare. CCENT.3(14)T. CCVP. Bringing the Meeting To You. All rights reserved. MeetingPlace.2(31)SB2. CCDE. 12. HomeLink. Changing the Way We Work. GigaDrive. Cisco Eos. Cisco.1 Feature Information The Cisco IOS IP SLAs Internet Control Message Protocol (ICMP) path jitter operation allows you to measure hop-by-hop jitter (inter-packet delay variance). CCDA. or platform. IOS. Cisco IOS. Inc. EtherSwitch. CCIP.cisco. © 2006-2008 Cisco Systems. Follow Me Browsing. Network Registrar. iPhone. iQ Net Readiness Scorecard. The use of the word partner does not imply a partnership relationship between Cisco and any other company. CCNA. For release information about a specific command. StackWise. To access Cisco Feature Navigator. the Cisco logo. and the WebEx logo are registered trademarks of Cisco Systems. 12. Play. DCE. SenderBase. MediaTone. CCDP. Cisco Press. MGX. iQ Expertise. and/or its affiliates in the United States and certain other countries. IronPort. the Cisco Systems logo. SMARTnet. Any use of actual IP addresses in illustrative content is unintentional and coincidental. CCIE. Networkers. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses.com/go/cfn. The Fastest Way to Increase Your Internet Quotient. feature set. go to http://www. CCSP. and Welcome to the Human Network are trademarks. TransPath. LightStream. 12. Cisco StadiumVision. Aironet. All other trademarks mentioned in this document or Website are the property of their respective owners. Catalyst. Not all commands may be available in your Cisco IOS software release. Cisco TelePresence. Inc. WebEx. Cisco IOS XE Release 2. Linksys. see the command reference documentation. the IronPort logo. Spectrum Expert. Cisco Systems Capital. 12 . AsyncOS. CCNP. and figures included in the document are shown for illustrative purposes only. the Cisco Certified Internetwork Expert logo. Cisco Unity. iQuick Study. Cisco Lumin. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release. Unless noted otherwise. the iQ logo. EtherFast. command display output. PCNow.2(33)SXH. An account on Cisco. and Learn and Cisco Store are service marks. subsequent releases of that Cisco IOS software release train also support that feature.com is not required.IP SLAs—Analyzing IP Service Levels Using the ICMP Path Jitter Operation Feature Information for the IP SLAs ICMP Path Jitter Operation Feature Information for the IP SLAs ICMP Path Jitter Operation Table 1 lists the release history for this feature. Table 1 Feature Information for the IP SLAs ICMP Path Jitter Operation Feature Name IP SLAs Path Jitter Operation Releases 12. MeetingPlace Chime Sound. ScriptShare. Collaboration Without Limitation.2(33)SRB1. Cisco Nexus. PowerPanels. Fast Step. ProConnect. Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Systems. Event Center. Any examples. and Access Registrar. PIX. Live. Networking Academy. Internet Quotient.

Inc.. page 2 Information About the IP SLAs FTP Operation. use the “Feature Information for the IP SLAs FTP Operation” section on page 11. to increase productivity. which allows Cisco customers to analyze IP service levels for IP applications and services. All rights reserved.cisco. page 2 How to Configure the IP SLAs FTP Operation. An account on Cisco. 2008 This module describes how to use the Cisco IOS IP Service Level Agreements (SLAs) FTP operation to measure the response time between a Cisco device and a File Transfer Protocol (FTP) server to retrieve a file. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module. and to reduce the frequency of network outages. The FTP operation can be used also for troubleshooting FTP server performance. To access Cisco Feature Navigator. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported. Inc. This module also demonstrates how the results of the FTP operation can be displayed and analyzed to determine the capacity of your network. The IP SLAs FTP operation supports an FTP GET request only.IP SLAs—Analyzing IP Service Levels Using the FTP Operation First Published: August 14. to lower operational costs. .com is not required. reliable. page 10 Americas Headquarters: Cisco Systems. CA 95134-1706 USA © 2007 Cisco Systems. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. IP SLAs is a portfolio of technology embedded in most devices that run Cisco IOS software. go to http://www. 170 West Tasman Drive. page 3 Configuration Examples for the IP SLAs FTP Operation. 2006 Last Updated: July 16. Contents • • • • Prerequisites for the IP SLAs FTP Operation. and predictable manner—for measuring network performance. San Jose.com/go/cfn. IP SLAs uses active traffic monitoring—the generation of traffic in a continuous.

In Figure 1 Router B is configured as the source IP SLAs device and an FTP operation is configured with the FTP server as the destination device. use the IP SLAs TCP Connect operation.IP SLAs—Analyzing IP Service Levels Using the FTP Operation Prerequisites for the IP SLAs FTP Operation • • • Where to Go Next. FTP is an application protocol. page 2 FTP Operation The FTP operation measures the round-trip time (RTT) between a Cisco device and an FTP server to retrieve a file. Note To test the response time to connect to an FTP port (Port 21). This operation does not use the IP SLAs Responder. 2 38175 . you should understand the following concept: • FTP Operation. page 10 Feature Information for the IP SLAs FTP Operation. Information About the IP SLAs FTP Operation To perform the tasks required to analyze FTP server response times using IP SLA. used for transferring files between network nodes. part of the Transmission Control Protocol (TCP)/IP protocol stack. page 11 Prerequisites for the IP SLAs FTP Operation Before configuring the IP SLAs FTP operation you should be familiar with the “Cisco IOS IP SLAs Overview” chapter of the Cisco IOS IP SLAs Configuration Guide. Figure 1 FTP Operation FTP server Router A FTP operation Performance management application Router B Connection response time is computed by measuring the time taken to download a file to Router B from the remote FTP server using FTP over TCP. page 10 Additional References.

5. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. enable configure terminal ip sla operation-number ftp get url [source-ip {ip-address | hostname}] [mode {passive | active} frequency seconds 3 . respectively. FTP carries a significant amount of data traffic and can affect the performance of your network. use the IP SLAs FTP operation. The FTP operation also measures your FTP server performance levels by determining the RTT taken to retrieve a file. 2. 4. The results of an IP SLAs FTP operation to retrieve a large file can be used to determine the capacity of the network but retrieve large files with caution because the FTP operation will consume more bandwidth. depending on whether you want to configure a basic FTP operation or configure an FTP operation with optional parameters: • • Configuring and Scheduling a Basic FTP Operation on the Source Device. The passive mode is enabled by default. The IP SLAs FTP operation only supports FTP GET (download) requests. This operation does not require the IP SLAs Responder to be enabled so there are no tasks to be performed on the destination device. page 3 (required) Configuring and Scheduling an FTP Operation on the Source Device To measure the response time between a Cisco device and an FTP server to retrieve a file. the defaults are anonymous and test. The URL specified for the FTP GET operation must be in one of the following formats: • • ftp://username:password@host/filename ftp://host/filename If the username and password are not specified. 3. Perform one of the following tasks in this section. SUMMARY STEPS 1. How to Configure the IP SLAs FTP Operation This section contains the following procedure: • Configuring and Scheduling an FTP Operation on the Source Device. page 3 Configuring and Scheduling an FTP Operation with Optional Parameters on the Source Device. page 6 Configuring and Scheduling a Basic FTP Operation on the Source Device Perform this task to enable an FTP operation without any optional parameters. Note For information on scheduling a group of operations.IP SLAs—Analyzing IP Service Levels Using the FTP Operation How to Configure the IP SLAs FTP Operation Both active and passive FTP transfer modes are supported. Only the FTP GET (download) operation type is supported.

7.IP SLAs—Analyzing IP Service Levels Using the FTP Operation How to Configure the IP SLAs FTP Operation 6. 8. exit ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] exit 4 .

Example: Router(config-ip-sla-ftp)# exit Step 7 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation.IP SLAs—Analyzing IP Service Levels Using the FTP Operation How to Configure the IP SLAs FTP Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. • Enter your password if prompted. Example: Router(config)# ip sla schedule 10 start-time now life forever Step 8 exit (Optional) Exits the global configuration mode and returns to privileged EXEC mode. Example: Router(config)# exit Examples The following example shows the configuration of an IP SLAs operation type of FTP to retrieve a file named test. Example: Router> enable Step 2 configure terminal Enters global configuration mode.cap Step 5 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats. The FTP operation number 10 is scheduled to start immediately and run indefinitely.cap. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. Example: Router(config)# ip sla 10 Step 4 ftp get url [source-ip {ip-address | hostname}] [mode {passive | active} Defines an FTP operation and enters IP SLA FTP configuration mode.cap 5 . Example: Router(config-ip-sla)# ftp get ftp://username:password@hostip/test. Example: Router(config-ip-sla-ftp)# frequency 30 Step 6 exit Exits IP SLA FTP configuration mode and returns to global configuration mode. ip sla 10 ftp get ftp://username:password@hostip/test.

threshold milliseconds 16. enable configure terminal ip sla operation-number ftp get url [source-ip {ip-address | hostname}] [mode {passive | active} history buckets-kept size history distributions-of-statistics-kept size history enhanced [interval seconds] [buckets number-of-buckets] history filter {none | all | overThreshold | failures} frequency seconds 10. Configuring and Scheduling an FTP Operation with Optional Parameters on the Source Device Perform this task to enable an FTP operation on the source device and configure some optional IP SLAs parameters.IP SLAs—Analyzing IP Service Levels Using the FTP Operation How to Configure the IP SLAs FTP Operation frequency 30 ! ip sla schedule 10 life forever start-time now What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. exit 20. history statistics-distribution-interval milliseconds 14. exit 18. 6. 3. owner owner-id 13. timeout milliseconds 17. 4. Note For information on scheduling a group of operations. 5. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. 9. show ip sla configuration [operation-number] 6 . ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] 19. history hours-of-statistics-kept hours 11. The source device is the location at which the measurement statistics are stored. 2. 8. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. SUMMARY STEPS 1. history lives-kept lives 12. tag text 15. 7.

Example: Router(config-ip-sla-ftp)# frequency 30 7 . Example: Router> enable Step 2 configure terminal Enters global configuration mode. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. Example: Router(config-ip-sla-ftp)# history buckets-kept 25 Step 6 history distributions-of-statistics-kept size (Optional) Sets the number of statistics distributions kept per hop during an IP SLAs operation. Example: Router(config-ip-sla-ftp)# history distributions-of-statistics-kept 5 Step 7 history enhanced [interval seconds] [buckets number-of-buckets] (Optional) Enables enhanced history gathering for an IP SLAs operation. Example: Router(config)# ip sla 10 Step 4 ftp get url [source-ip {ip-address | hostname}] [mode {passive | active} Defines an FTP operation and enters IP SLA FTP configuration mode.IP SLAs—Analyzing IP Service Levels Using the FTP Operation How to Configure the IP SLAs FTP Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. Example: Router(config-ip-sla)# ftp get ftp://username:password@hostip/filename Step 5 history buckets-kept size (Optional) Sets the number of history buckets that are kept during the lifetime of an IP SLAs operation. • Enter your password if prompted. Example: Router(config-ip-sla-ftp)# history enhanced interval 900 buckets 100 Step 8 history filter {none | all | overThreshold | failures} (Optional) Defines the type of information kept in the history table for an IP SLAs operation. Example: Router(config-ip-sla-ftp)# history filter failures Step 9 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats.

IP SLAs—Analyzing IP Service Levels Using the FTP Operation How to Configure the IP SLAs FTP Operation Command or Action Step 10 history hours-of-statistics-kept hours Purpose (Optional) Sets the number of hours for which statistics are maintained for an IP SLAs operation. Example: Router(config)# ip sla schedule 10 start-time now life forever 8 . Example: Router(config-ip-sla-ftp)# history hours-of-statistics-kept 4 Step 11 history lives-kept lives (Optional) Sets the number of lives maintained in the history table for an IP SLAs operation. Example: Router(config-ip-sla-ftp)# exit Step 18 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation. Example: Router(config-ip-sla-ftp)# tag TelnetPollServer1 Step 15 threshold milliseconds Example: Router(config-ip-sla-ftp)# threshold 10000 (Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. Step 16 timeout milliseconds Example: Router(config-ip-sla-ftp)# timeout 10000 Step 17 exit Exits FTP configuration submode and returns to global configuration mode. (Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet. Example: Router(config-ip-sla-ftp)# history lives-kept 5 Step 12 owner owner-id (Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation. Example: Router(config-ip-sla-ftp)# owner admin Step 13 history statistics-distribution-interval milliseconds (Optional) Sets the time interval for each statistics distribution kept for an IP SLAs operation. Example: Router(config-ip-sla-ftp)# history statistics-distribution-interval 10 Step 14 tag text (Optional) Creates a user-specified identifier for an IP SLAs operation.

IP SLAs—Analyzing IP Service Levels Using the FTP Operation How to Configure the IP SLAs FTP Operation Command or Action Step 19 exit Purpose (Optional) Exits global configuration mode and returns to privileged EXEC mode. Router# show ip sla configuration 10 Complete Configuration Table (includes defaults) Entry number: 10 Owner: FTP-Test Tag: FTP-Test Type of operation to perform: ftp Source address: 0.0 FTP URL: ftp://username:password@hostip/filename Type Of Service parameters: 128 Operation timeout (milliseconds): 30000 Operation frequency (seconds): 30 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 Threshold (milliseconds): 30000 Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20 Number of history Lives kept: 0 Number of history Buckets kept: 15 Troubleshooting Tips Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with the FTP operation. 9 .0.0. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. Example: Router(config)# exit Step 20 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation. Example: Router# show ip sla configuration 10 Examples The following sample output shows the configuration of all the IP SLAs parameters (including defaults) for the FTP operation number 10. What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command.

m. Router B Configuration ip sla 10 ftp get ftp://user1:abc@test.cap is to be retrieved from the host.IP SLAs—Analyzing IP Service Levels Using the FTP Operation Configuration Examples for the IP SLAs FTP Operation Configuration Examples for the IP SLAs FTP Operation This section contains the following configuration example: • Configuring an FTP Operation: Example.cisco. with a password of abc using FTP in active mode. page 10 Configuring an FTP Operation: Example The following example shows how to configure an FTP operation as shown in Figure 1 from Router B to the FTP server. In this example. Cisco white paper Cisco IOS IP SLAs Command Reference Standards Standards Title No new or modified standards are supported by this — feature. The operation is scheduled to start every day at 1:30 a. cisco. and support for existing standards has not been modified by this feature.cap mode active frequency 20 tos 128 timeout 40000 tag FLL-FTP ip sla schedule 10 start-time 01:30:00 recurring Where to Go Next For information about other types of IP SLAs operations and IP SLAs features. the file named test.com. 10 . see the Cisco IOS IP SLAs Features Roadmap. Related Documents Related Topic Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands Document Title Cisco IOS IP Service Level Agreements Command Line Interface.com/test. Additional References The following sections provide references related to the IP SLAs FTP operation.

use Cisco MIB Locator found at the following URL: http://www. and support for existing RFCs has not been modified by this feature.cisco. For release information about a specific command.com/go/mibs RFCs RFCs No new or modified RFCs are supported by this feature. Cisco IOS releases. subsequent releases of that Cisco IOS software release train also support that feature.com/public/support/tac/home. Title — Technical Assistance Description Technical Assistance Center (TAC) home page.com users can log in from this page to access even more content. solutions. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release. or platform. An account on Cisco.cisco. Use Cisco Feature Navigator to find information about platform support and software image support. 11 . To access Cisco Feature Navigator. Registered Cisco. and tools. see the command reference documentation.com/go/cfn. Link http://www.000 pages of searchable technical content. Not all commands may be available in your Cisco IOS software release. including links to products. containing 30. Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise. go to http://www.shtml Feature Information for the IP SLAs FTP Operation Table 1 lists the release history for this feature. technologies. technical tips. feature set.IP SLAs—Analyzing IP Service Levels Using the FTP Operation Feature Information for the IP SLAs FTP Operation MIBs MIBs CISCO-RTTMON-MIB MIBs Link To locate and download MIBs for selected platforms.com is not required. and feature sets.cisco.

iQ Expertise. GigaDrive. Cisco. MeetingPlace. Cisco Systems Capital. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. CCIE. Cisco Press. StackWise. EtherFast. iQuick Study. SenderBase. PIX. IOS. DCE. Fast Step. Live. Any examples. PCNow. SMARTnet. The use of the word partner does not imply a partnership relationship between Cisco and any other company. 12. Changing the Way We Work. All rights reserved. CCVP. CCENT. Network Registrar. Linksys.2(33)SRB1. CCDA. Cisco Nexus. CCDE. and Access Registrar. Follow Me Browsing. CCDP. CCNA. TransPath. the Cisco Systems logo. CCSP. Catalyst. LightStream. Cisco Unity. and/or its affiliates in the United States and certain other countries. Play. Cisco IOS. MGX. iPhone. ScriptShare. The Fastest Way to Increase Your Internet Quotient. CCIP. the Cisco Certified Internetwork Expert logo. Cisco StadiumVision.3(14)T. FormShare. and Learn and Cisco Store are service marks. MeetingPlace Chime Sound. CCNP. 12 . Cisco TelePresence. Cisco Systems. EtherSwitch.2(33)SXH. Aironet. and figures included in the document are shown for illustrative purposes only.IP SLAs—Analyzing IP Service Levels Using the FTP Operation Feature Information for the IP SLAs FTP Operation Table 1 Feature Information for the IP SLAs FTP Operation Feature Name IP SLAs FTP Operation Releases 12. iQ Net Readiness Scorecard.1 Feature Information The Cisco IOS IP SLAs File Transfer Protocol (FTP) operation allows you to measure the network response time between a Cisco device and an FTP server to retrieve a file. PowerPanels. the iQ logo. Spectrum Expert. © 2006-2008 Cisco Systems. 12. Cisco Lumin. IronPort. Cisco IOS XE Release 2. AsyncOS. and Welcome to the Human Network are trademarks. 12. Event Center. the IronPort logo. MediaTone. Collaboration Without Limitation. Cisco Eos. command display output. Inc. the Cisco logo. WebEx. Networkers. ProConnect. and the WebEx logo are registered trademarks of Cisco Systems.2(31)SB2. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Internet Quotient. Bringing the Meeting To You. Networking Academy. HomeLink. All other trademarks mentioned in this document or Website are the property of their respective owners. Inc.

and to reduce the frequency of network outages. page 2 Information About the IP SLAs DNS Operation. Contents • • • • Prerequisites for the IP SLAs DNS Operation. San Jose. 2008 This module describes how to use the Cisco IOS IP Service Level Agreements (SLAs) DNS operation to measure the difference between the time taken to send a Domain Name System (DNS) request and receive a reply.cisco. IP SLAs is a portfolio of technology embedded in most devices that run Cisco IOS software. Inc. CA 95134-1706 USA © 2007 Cisco Systems. page 2 How to Configure the IP SLAs DNS Operation. and predictable manner—for measuring network performance. . Inc. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported. All rights reserved. page 3 Configuration Examples for the IP SLAs DNS Operation. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module. An account on Cisco. page 9 Americas Headquarters: Cisco Systems. IP SLAs uses active traffic monitoring—the generation of traffic in a continuous.IP SLAs—Analyzing IP Service Levels Using the DNS Operation First Published: August 14..com is not required. go to http://www. 2006 Last Updated: July 16. to increase productivity. reliable. use the “Feature Information for the IP SLAs DNS Operation” section on page 11. This module also demonstrates how the results of the DNS operation can be displayed and analyzed to determine the DNS lookup time which is a critical element for determining the performance of a DNS or web server. 170 West Tasman Drive. which allows Cisco customers to analyze IP service levels for IP applications and services. To access Cisco Feature Navigator. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support.com/go/cfn. to lower operational costs.

Figure 1 DNS Operation DNS server Router A DNS operation Performance management application Router B Connection response time is computed by measuring the difference between the time taken to send a request to the DNS server and the time a reply is received by Router B. 2 18171 . The IP SLAs DNS operation queries for an IP address if you specify a host name. or queries for a host name if you specify an IP address. page 2 DNS Operation The DNS operation measures the difference between the time taken to send a DNS request and receive a reply.IP SLAs—Analyzing IP Service Levels Using the DNS Operation Prerequisites for the IP SLAs DNS Operation • • • Where to Go Next. Faster DNS lookup times translate to a faster web server access experience. page 9 Feature Information for the IP SLAs DNS Operation. The resulting DNS lookup time can help you analyze your DNS performance. page 9 Additional References. you should understand the following concept: • DNS Operation. In Figure 1 Router B is configured as the source IP SLAs device and a DNS operation is configured with the DNS server as the destination device. DNS is used in the Internet for translating names of network nodes into addresses. Information About the IP SLAs DNS Operation To perform the tasks required to analyze DNS lookup times using IP SLA. page 11 Prerequisites for the IP SLAs DNS Operation Before configuring the IP SLAs DNS operation you should be familiar with the “Cisco IOS IP SLAs Overview” chapter of the Cisco IOS IP SLAs Configuration Guide.

Note For information on scheduling a group of operations. page 5 Configuring and Scheduling a Basic DNS Operation on the Source Device Perform this task to enable a DNS operation without any optional parameters. Perform one of the following tasks in this section. SUMMARY STEPS 1. 2. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide.IP SLAs—Analyzing IP Service Levels Using the DNS Operation How to Configure the IP SLAs DNS Operation How to Configure the IP SLAs DNS Operation This section contains the following procedure: • Configuring and Scheduling a DNS Operation on the Source Device. 8. 4. 3. This operation does not require the IP SLAs Responder to be enabled so there are no tasks to be performed on the destination device. depending on whether you want to configure a basic DNS operation or configure a DNS operation with optional parameters: • • Configuring and Scheduling a Basic DNS Operation on the Source Device. enable configure terminal ip sla operation-number dns {destination-ip-address | destination-hostname} name-server ip-address [source-ip {ip-address | hostname} source-port port-number] frequency seconds exit ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] exit 3 . 5. 7. 6. use the IP SLAs DNS operation. page 3 Configuring and Scheduling a DNS Operation with Optional Parameters on the Source Device. page 3 (required) Configuring and Scheduling a DNS Operation on the Source Device To measure the difference between the time taken to send a DNS request and the time a reply is received by a Cisco device.

132 Step 5 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats.IP SLAs—Analyzing IP Service Levels Using the DNS Operation How to Configure the IP SLAs DNS Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. Example: Router(config-ip-sla-dns)# exit Step 7 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation. Example: Router(config)# ip sla 10 Step 4 dns {destination-ip-address | destination-hostname} name-server ip-address [source-ip {ip-address | hostname} source-port port-number] Defines a DNS operation and enters IP SLA DNS configuration mode. 4 . Example: Router(config-ip-sla)# dns host1 name-server 172. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. • Enter your password if prompted. Example: Router(config)# exit Examples The following example shows the configuration of an IP SLAs operation type of DNS to find the IP address of the hostname host1.20. Example: Router(config)# ip sla schedule 10 start-time now life forever Step 8 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode. Example: Router> enable Step 2 configure terminal Enters global configuration mode. Example: Router(config-ip-sla-dns)# frequency 60 Step 6 exit Exits DNS configuration submode and returns to global configuration mode. The DNS operation number 11 is scheduled to start immediately and run indefinitely.2.

history hours-of-statistics-kept hours 11. 3. tag text 15. SUMMARY STEPS 1. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. threshold milliseconds 16. 2. 6. 9. exit 20.20. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. Configuring and Scheduling a DNS Operation with Optional Parameters on the Source Device Perform this task to enable a DNS operation on the source device and configure some optional IP SLAs parameters.IP SLAs—Analyzing IP Service Levels Using the DNS Operation How to Configure the IP SLAs DNS Operation ip sla 11 dns host1 name-server 172. The source device is the location at which the measurement statistics are stored. 7. exit 18. show ip sla configuration [operation-number] 5 .2. history lives-kept lives 12. timeout milliseconds 17. ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] 19. owner owner-id 13.132 frequency 60 ! ip sla schedule 11 life forever start-time now What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. 5. 4. 8. Note For information on scheduling a group of operations. history statistics-distribution-interval milliseconds 14. enable configure terminal ip sla operation-number dns {destination-ip-address | destination-hostname} name-server ip-address [source-ip {ip-address | hostname} source-port port-number] history buckets-kept size history distributions-of-statistics-kept size history enhanced [interval seconds] [buckets number-of-buckets] history filter {none | all | overThreshold | failures} frequency seconds 10.

Example: Router(config-ip-sla-dns)# history distributions-of-statistics-kept 5 Step 7 history enhanced [interval seconds] [buckets number-of-buckets] (Optional) Enables enhanced history gathering for an IP SLAs operation.132 Step 5 history buckets-kept size (Optional) Sets the number of history buckets that are kept during the lifetime of an IP SLAs operation. Example: Router(config-ip-sla)# dns host1 name-server 172.IP SLAs—Analyzing IP Service Levels Using the DNS Operation How to Configure the IP SLAs DNS Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. Example: Router(config-ip-sla-dns)# history enhanced interval 900 buckets 100 Step 8 history filter {none | all | overThreshold | failures} (Optional) Defines the type of information kept in the history table for an IP SLAs operation.20. Example: Router(config-ip-sla-dns)# history buckets-kept 25 Step 6 history distributions-of-statistics-kept size (Optional) Sets the number of statistics distributions kept per hop during an IP SLAs operation. Example: Router(config)# ip sla 10 Step 4 dns {destination-ip-address | destination-hostname} name-server ip-address [source-ip {ip-address | hostname} source-port port-number] Defines a DNS operation and enters IP SLA DNS configuration mode. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. Example: Router(config-ip-sla-dns)# history filter failures 6 . Example: Router> enable Step 2 configure terminal Enters global configuration mode.2. • Enter your password if prompted.

Example: Router(config-ip-sla-dns)# exit 7 . (Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet. Example: Router(config-ip-sla-dns)# history hours-of-statistics-kept 4 Step 11 history lives-kept lives (Optional) Sets the number of lives maintained in the history table for an IP SLAs operation. Example: Router(config-ip-sla-dns)# history statistics-distribution-interval 10 Step 14 tag text (Optional) Creates a user-specified identifier for an IP SLAs operation. Example: Router(config-ip-sla-dns)# tag TelnetPollServer1 Step 15 threshold milliseconds Example: Router(config-ip-sla-dns)# threshold 10000 (Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. Example: Router(config-ip-sla-dns)# history lives-kept 5 Step 12 owner owner-id (Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation. Example: Router(config-ip-sla-dns)# frequency 30 Step 10 history hours-of-statistics-kept hours (Optional) Sets the number of hours for which statistics are maintained for an IP SLAs operation.IP SLAs—Analyzing IP Service Levels Using the DNS Operation How to Configure the IP SLAs DNS Operation Command or Action Step 9 frequency seconds Purpose (Optional) Sets the rate at which a specified IP SLAs operation repeats. Example: Router(config-ip-sla-dns)# owner admin Step 13 history statistics-distribution-interval milliseconds (Optional) Sets the time interval for each statistics distribution kept for an IP SLAs operation. Step 16 timeout milliseconds Example: Router(config-ip-sla-dns)# timeout 10000 Step 17 exit Exits DNS configuration submode and returns to global configuration mode.

8 .0. Example: Router# show ip sla configuration 10 Examples The following sample output shows the configuration of all the IP SLAs parameters (including defaults) for the DNS operation number 11. Example: Router(config)# exit Step 20 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation. Example: Router(config)# ip sla schedule 10 start-time now life forever Step 19 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode.0.cisco. Router# show ip sla configuration 11 Complete Configuration Table (includes defaults) Entry number: 11 Owner: DNS-Test Tag: DNS-Test Type of operation to perform: dns Target address: www.IP SLAs—Analyzing IP Service Levels Using the DNS Operation How to Configure the IP SLAs DNS Operation Command or Action Step 18 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Purpose Configures the scheduling parameters for an individual IP SLAs operation.com Source address: 0.0 Source port: 0 Operation timeout (milliseconds): 9000 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 Threshold (milliseconds): 5000 Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20 Number of history Lives kept: 0 Number of history Buckets kept: 15 History Filter Type: None Troubleshooting Tips Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation.

the target address is a hostname and the DNS operation will query the DNS server for the IP address associated with the hostname host1. In this example. Related Documents Related Topic Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands Document Title Cisco IOS IP Service Level Agreements Command Line Interface.132). The operation is scheduled to start immediately.20. 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 the IP SLAs DNS Operation This section contains the following configuration example: • Configuring a DNS Operation: Example.2.132 frequency 50 timeout 8000 tag DNS-Test ip sla schedule 11 start-time now Where to Go Next For information about other types of IP SLAs operations and IP SLAs features. Router B Configuration ip sla 11 dns host1 name-server 172.20.2. see the Cisco IOS IP SLAs Features Roadmap. Cisco white paper Cisco IOS IP SLAs Command Reference 9 . page 9 Configuring a DNS Operation: Example The following example shows how to configure a DNS operation as shown in Figure 1 from Router B to the DNS server (IP address 172. No configuration is required at the DNS server. Additional References The following sections provide references related to the IP SLAs DNS operation.IP SLAs—Analyzing IP Service Levels Using the DNS Operation Configuration Examples for the IP SLAs DNS Operation What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command.

Registered Cisco. solutions. use Cisco MIB Locator found at the following URL: http://www. containing 30. technical tips.cisco. technologies. Title — Technical Assistance Description Technical Assistance Center (TAC) home page.cisco.com/public/support/tac/home. and support for existing RFCs has not been modified by this feature. including links to products. and support for existing standards has not been modified by this feature. and tools.com/go/mibs RFCs RFCs No new or modified RFCs are supported by this feature.com users can log in from this page to access even more content.IP SLAs—Analyzing IP Service Levels Using the DNS Operation Additional References Standards Standards Title No new or modified standards are supported by this — feature. and feature sets. Link http://www. Cisco IOS releases.000 pages of searchable technical content. MIBs MIBs CISCO-RTTMON-MIB MIBs Link To locate and download MIBs for selected platforms.shtml 10 .

CCSP. To access Cisco Feature Navigator. Follow Me Browsing. Aironet. ProConnect. An account on Cisco. Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release.1 Feature Information The Cisco IOS IP SLAs Domain Name System (DNS) operation allows you to measure the difference between the time taken to send a DNS request and receive a reply. 12.cisco. and/or its affiliates in the United States and certain other countries. GigaDrive. IOS. and Welcome to the Human Network are trademarks.2(31)SB2. For release information about a specific command. Table 1 Feature Information for the IP SLAs DNS Operation Feature Name IP SLAs DNS Operation Releases 12. Not all commands may be available in your Cisco IOS software release. Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. DCE. All other trademarks mentioned in this document or Website are the property of their respective owners. AsyncOS. MGX. MeetingPlace Chime Sound. HomeLink. IronPort. 11 . Cisco Systems. PCNow. subsequent releases of that Cisco IOS software release train also support that feature. Cisco TelePresence. Unless noted otherwise. MediaTone. Cisco StadiumVision. and Access Registrar. go to http://www. PIX. CCDP. CCNP. SMARTnet. or platform. Collaboration Without Limitation. WebEx. EtherSwitch. SenderBase. Catalyst. All rights reserved. © 2006-2008 Cisco Systems. 12.com is not required. Networkers. and Learn and Cisco Store are service marks. Cisco IOS XE Release 2. Cisco Lumin. iPhone. Spectrum Expert. FormShare. iQ Expertise. CCENT. Cisco Systems Capital. CCDE. Inc. StackWise. CCVP. PowerPanels. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Cisco Unity. Cisco Eos. ScriptShare.2(33)SRB1. see the command reference documentation. LightStream. The Fastest Way to Increase Your Internet Quotient. the Cisco logo. Networking Academy. the Cisco Systems logo. Fast Step. iQuick Study. the IronPort logo. Changing the Way We Work.IP SLAs—Analyzing IP Service Levels Using the DNS Operation Feature Information for the IP SLAs DNS Operation Feature Information for the IP SLAs DNS Operation Table 1 lists the release history for this feature. command display output. Cisco Nexus. and figures included in the document are shown for illustrative purposes only. Network Registrar. CCIP.2(33)SXH. CCDA. Cisco. TransPath. CCIE. Event Center. feature set. and the WebEx logo are registered trademarks of Cisco Systems.3(14)T. Live. Any examples. MeetingPlace. Cisco Press. 12. the Cisco Certified Internetwork Expert logo. iQ Net Readiness Scorecard. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Linksys. Inc. Bringing the Meeting To You. Cisco IOS. CCNA. the iQ logo. EtherFast. Play. The use of the word partner does not imply a partnership relationship between Cisco and any other company.com/go/cfn. Internet Quotient.

IP SLAs—Analyzing IP Service Levels Using the DNS Operation Feature Information for the IP SLAs DNS Operation 12 .

or for a specific DHCP server. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported. Inc. 2008 This module describes how to use the Cisco IOS IP Service Level Agreements (SLAs) DHCP operation to measure the response time between a Cisco device and a Dynamic Host Control Protocol (DHCP) server to obtain an IP address. page 2 Information About the IP SLAs DHCP Operation. The DHCP operation can be used also for troubleshooting DHCP server performance. which allows Cisco customers to analyze IP service levels for IP applications and services. All rights reserved.com is not required. reliable. Contents • • • • Prerequisites for the IP SLAs DHCP Operation. . go to http://www. 2006 Last Updated: July 16. IP SLAs uses active traffic monitoring—the generation of traffic in a continuous. IP SLAs is a portfolio of technology embedded in most devices that run Cisco IOS software. and to reduce the frequency of network outages. An account on Cisco. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module. Inc. page 2 How to Configure the IP SLAs DHCP Operation.com/go/cfn.. 170 West Tasman Drive. This module also demonstrates how the results of the DHCP operation can be displayed and analyzed to determine the DHCP response time within your network. page 3 Configuration Examples for the IP SLAs DHCP Operation. and predictable manner—for measuring network performance. use the “Feature Information for the IP SLAs DHCP Operation” section on page 11. to lower operational costs. page 9 Americas Headquarters: Cisco Systems. San Jose. CA 95134-1706 USA © 2007 Cisco Systems. To access Cisco Feature Navigator.IP SLAs—Analyzing IP Service Levels Using the DHCP Operation First Published: August 14. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support.cisco. to increase productivity.

the DHCP operation sends discovery packets on every available IP interface on the router. DHCP provides a mechanism for allocating IP addresses dynamically so that addresses can be reused when hosts no longer need them. Information About the IP SLAs DHCP Operation To perform the tasks required to analyze DHCP server response times using IP SLAs. IP SLAs DHCP Relay Agent Options A DHCP relay agent is any host that forwards DHCP packets between clients and servers. Option 82 includes three suboptions that convey information known by the relay agent: • • circuit-id—identifies the incoming circuit. and the relay agent strips the option before forwarding the reply to the client. Relay agent forwarding is distinct from the normal forwarding of an IP router. There are two modes for the DHCP operation. page 11 Prerequisites for the IP SLAs DHCP Operation Before configuring the IP SLAs DHCP operation you should be familiar with the “Cisco IOS IP SLAs Overview” chapter of the Cisco IOS IP SLAs Configuration Guide. you should understand the following concepts: • • DHCP Operation. page 2 IP SLAs DHCP Relay Agent Options. where IP packets are switched between networks somewhat transparently. Relay agents receive DHCP messages and then generate a new DHCP message to send out on another interface. The IP SLAs DHCP operation contains a relay agent information option—Option 82—which is inserted by the DHCP relay agent when forwarding client-originated DHCP packets to a DHCP server. Servers recognizing the relay agent information option may use the information to implement IP address or other parameter assignment policies. remote-id—provides a trusted identifier for a remote high-speed modem.IP SLAs—Analyzing IP Service Levels Using the DHCP Operation Prerequisites for the IP SLAs DHCP Operation • • • Where to Go Next. Relay agents are used to forward requests and replies between clients and servers when they are not on the same physical subnet. 2 . The DHCP server echoes the option back verbatim to the relay agent in server-to-client replies. discovery packets are sent only to that DHCP server. using the ip dhcp-server command. page 9 Additional References. page 2 DHCP Operation The Dynamic Host Configuration Protocol (DHCP) operation measures the round-trip time (RTT) taken to discover a DHCP server and obtain a leased IP address from it. The DHCP operation also measures your DHCP server performance levels by determining the RTT taken to obtain a leased IP address. If a specific server is configured on the router. IP SLAs releases the leased IP address after the operation. By default. page 9 Feature Information for the IP SLAs DHCP Operation.

enable configure terminal ip sla operation-number dhcp {destination-ip-address | destination-hostname} [source-ip {ip-address | hostname}] [option-82 [circuit-id circuit-id] [remote-id remote-id] [subnet-mask subnet-mask]] frequency seconds exit ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] exit 3 . This operation does not require the IP SLAs responder to be enabled so there are no tasks to be performed on the destination device. 7. SUMMARY STEPS 1. Note For information on scheduling a group of operations. depending on whether you want to configure a basic DHCP operation or configure a DHCP operation with optional parameters: • • Configuring and Scheduling a Basic DHCP Operation on the Source Device. Perform one of the following tasks in this section. 4. page 5 Configuring and Scheduling a Basic DHCP Operation on the Source Device Perform this task to enable a DHCP operation without any optional parameters. page 3 (required) Configuring and Scheduling a DHCP Operation on the Source Device To measure the response time between a Cisco device and a DHCP server to lease an IP address. 6. 3. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. 5. 8. page 3 Configuring and Scheduling a DHCP Operation with Optional Parameters on the Source Device. 2.IP SLAs—Analyzing IP Service Levels Using the DHCP Operation How to Configure the IP SLAs DHCP Operation • subnet-mask—identifies the mask of the logical IP subnet from which the relay agent received the client DHCP packet. How to Configure the IP SLAs DHCP Operation This section contains the following procedure: • Configuring and Scheduling a DHCP Operation on the Source Device. use the IP SLAs DHCP operation.

4 .10. Example: Router(config)# exit What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. Example: Router(config)# ip sla 10 Step 4 dhcp {destination-ip-address | destination-hostname} [source-ip {ip-address | hostname}] [option-82 [circuit-id circuit-id] [remote-id remote-id] [subnet-mask subnet-mask]] Defines a DHCP operation and enters IP SLA DHCP configuration mode. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable.10. Example: Router(config-ip-sla-dhcp)# exit Step 7 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation.IP SLAs—Analyzing IP Service Levels Using the DHCP Operation How to Configure the IP SLAs DHCP Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. Example: Router> enable Step 2 configure terminal Enters global configuration mode. • Enter your password if prompted.3 Step 5 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. Example: Router(config-ip-sla-dhcp)# frequency 30 Step 6 exit Exits IP SLA DHCP configuration mode and returns to global configuration mode. Example: Router(config-ip-sla)# dhcp 10. Example: Router(config)# ip sla schedule 10 start-time now life forever Step 8 exit (Optional) Exits the global configuration mode and returns to privileged EXEC mode.

timeout milliseconds 17. 9. threshold milliseconds 16. Note For information on scheduling a group of operations. 6. The source device is the location at which the measurement statistics are stored. show ip sla configuration [operation-number] 5 . 2. history lives-kept lives 12.IP SLAs—Analyzing IP Service Levels Using the DHCP Operation How to Configure the IP SLAs DHCP Operation Configuring and Scheduling a DHCP Operation with Optional Parameters on the Source Device Perform this task to enable a DHCP operation on the source device and configure some optional IP SLAs parameters. owner owner-id 13. 5. ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] 19. 8. exit 18. history statistics-distribution-interval milliseconds 14. 4. 3. history hours-of-statistics-kept hours 11. enable configure terminal ip sla operation-number dhcp {destination-ip-address | destination-hostname} [source-ip {ip-address | hostname}] [option-82 [circuit-id circuit-id] [remote-id remote-id] [subnet-mask subnet-mask]] history buckets-kept size history distributions-of-statistics-kept size history enhanced [interval seconds] [buckets number-of-buckets] history filter {none | all | overThreshold | failures} frequency seconds 10. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. 7. exit 20. tag text 15. SUMMARY STEPS 1.

Example: Router(config)# ip sla 10 Step 4 dhcp {destination-ip-address | destination-hostname} [source-ip {ip-address | hostname}] [option-82 [circuit-id circuit-id] [remote-id remote-id] [subnet-mask subnet-mask]] Defines a DHCP operation and enters IP SLA DHCP configuration mode.3 option-82 circuit-id 10005A6F1234 Step 5 history buckets-kept size (Optional) Sets the number of history buckets that are kept during the lifetime of an IP SLAs operation. • Enter your password if prompted. Example: Router(config-ip-sla-dhcp)# history buckets-kept 25 Step 6 history distributions-of-statistics-kept size (Optional) Sets the number of statistics distributions kept per hop during an IP SLAs operation. Example: Router(config-ip-sla)# dhcp 10. Example: Router(config-ip-sla-dhcp)# history enhanced interval 900 buckets 100 Step 8 history filter {none | all | overThreshold | failures} (Optional) Defines the type of information kept in the history table for an IP SLAs operation. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode.IP SLAs—Analyzing IP Service Levels Using the DHCP Operation How to Configure the IP SLAs DHCP Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode.10. Example: Router> enable Step 2 configure terminal Enters global configuration mode. Example: Router(config-ip-sla-dhcp)# history filter failures 6 . Example: Router(config-ip-sla-dhcp)# history distributions-of-statistics-kept 5 Step 7 history enhanced [interval seconds] [buckets number-of-buckets] (Optional) Enables enhanced history gathering for an IP SLAs operation.10.

IP SLAs—Analyzing IP Service Levels Using the DHCP Operation How to Configure the IP SLAs DHCP Operation

Command or Action
Step 9
frequency seconds

Purpose (Optional) Sets the rate at which a specified IP SLAs operation repeats.

Example:
Router(config-ip-sla-dhcp)# frequency 30

Step 10

history hours-of-statistics-kept hours

(Optional) Sets the number of hours for which statistics are maintained for an IP SLAs operation.

Example:
Router(config-ip-sla-dhcp)# history hours-of-statistics-kept 4

Step 11

history lives-kept lives

(Optional) Sets the number of lives maintained in the history table for an IP SLAs operation.

Example:
Router(config-ip-sla-dhcp)# history lives-kept 5

Step 12

owner owner-id

(Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation.

Example:
Router(config-ip-sla-dhcp)# owner admin

Step 13

history statistics-distribution-interval milliseconds

(Optional) Sets the time interval for each statistics distribution kept for an IP SLAs operation.

Example:
Router(config-ip-sla-dhcp)# history statistics-distribution-interval 10

Step 14

tag text

(Optional) Creates a user-specified identifier for an IP SLAs operation.

Example:
Router(config-ip-sla-dhcp)# tag TelnetPollServer1

Step 15

threshold milliseconds

Example:
Router(config-ip-sla-dhcp)# threshold 10000

(Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. (Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet.

Step 16

timeout milliseconds

Example:
Router(config-ip-sla-dhcp)# timeout 10000

Step 17

exit

Exits DHCP configuration submode and returns to global configuration mode.

Example:
Router(config-ip-sla-dhcp)# exit

7

IP SLAs—Analyzing IP Service Levels Using the DHCP Operation How to Configure the IP SLAs DHCP Operation

Command or Action
Step 18
ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring]

Purpose Configures the scheduling parameters for an individual IP SLAs operation.

Example:
Router(config)# ip sla schedule 10 start-time now life forever

Step 19

exit

(Optional) Exits global configuration mode and returns to privileged EXEC mode.

Example:
Router(config)# exit

Step 20

show ip sla configuration [operation-number]

(Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation.

Example:
Router# show ip sla configuration 10

Examples
The following sample output shows the configuration of all the IP SLAs parameters (including defaults) for the DHCP operation number 12.
Router# show ip sla configuration 12 Complete Configuration Table (includes defaults) Entry number: 12 Owner: DHCP-Test Tag: DHCP-Test Type of operation to perform: dhcp Target address: 10.10.10.3 Source address: 0.0.0.0 Operation timeout (milliseconds): 5000 Dhcp option: Operation frequency (seconds): 30 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 Threshold (milliseconds): 5000 Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20 Number of history Lives kept: 0 Number of history Buckets kept: 15 History Filter Type: None

Troubleshooting Tips
Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation.

8

IP SLAs—Analyzing IP Service Levels Using the DHCP Operation Configuration Examples for the IP SLAs DHCP Operation

What to Do Next
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 the IP SLAs DHCP Operation
This section contains the following configuration example:

Configuring a DHCP Operation: Example, page 9

Configuring a DHCP Operation: Example
In the following example, IP SLAs operation number 12 is configured as a DHCP operation enabled for DHCP server 172.16.20.3. Note that DHCP option 82 is used to specify the circuit ID.
Router B Configuration
ip dhcp-server 172.16.20.3 ! ip sla 12 dhcp 10.10.10.3 option-82 circuit-id 10005A6F1234 frequency 30 timeout 5000 tag DHCP_Test ! ip sla schedule 12 start-time now

Where to Go Next
For information about other types of IP SLAs operations and IP SLAs features, see the Cisco IOS IP SLAs Features Roadmap.

Additional References
The following sections provide references related to the IP SLAs DHCP operation.

9

IP SLAs—Analyzing IP Service Levels Using the DHCP Operation Additional References

Related Documents
Related Topic Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands Document Title Cisco IOS IP Service Level Agreements Command Line Interface, Cisco white paper Cisco IOS IP SLAs Command Reference

Standards
Standards Title No new or modified standards are supported by this — feature, and support for existing standards has not been modified by this feature.

MIBs
MIBs CISCO-RTTMON-MIB MIBs Link To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: http://www.cisco.com/go/mibs

RFCs
RFCs No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. Title —

Technical Assistance
Description Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content. Link http://www.cisco.com/public/support/tac/home.shtml

10

IP SLAs—Analyzing IP Service Levels Using the DHCP Operation Feature Information for the IP SLAs DHCP Operation

Feature Information for the IP SLAs DHCP Operation
Table 1 lists the release history for this feature. Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation. Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Note

Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.

Table 1

Feature Information for the IP SLAs DHCP Operation

Feature Name IP SLAs DHCP Operation

Releases 12.3(14)T, 12.2(31)SB2, 12.2(33)SRB1, 12.2(33)SXH, Cisco IOS XE Release 2.1

Feature Information The Cisco IOS IP SLAs Dynamic Host Control Protocol (DHCP) operation allows you to schedule and measure the network response time between a Cisco device and a DHCP server to obtain an IP address.

CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. All other trademarks mentioned in this document or Website 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. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. © 2006-2008 Cisco Systems, Inc. All rights reserved.

11

IP SLAs—Analyzing IP Service Levels Using the DHCP Operation Feature Information for the IP SLAs DHCP Operation

12

To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported. reliable. Inc. Inc. page 2 Information About the IP SLAs DLSw+ Operation. which allows Cisco customers to analyze IP service levels for IP applications and services. San Jose. 2006 This module describes how to use the Cisco IOS IP Service Level Agreements (SLAs) DLSw+ operation to measure the Data Link Switching Plus (DLSw+) protocol stack and network response time between DLSw+ peers. 2006 Last Updated: August 29. CA 95134-1706 USA © 2007 Cisco Systems. All rights reserved. An account on Cisco.com is not required..com/go/cfn. to lower operational costs. page 2 Configuration Examples for the IP SLAs DLSw+ Operation. and predictable manner—for measuring network performance. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. page 9 Where to Go Next. to increase productivity. page 10 Americas Headquarters: Cisco Systems. To access Cisco Feature Navigator.IP SLAs—Analyzing IP Service Levels Using the DLSw+ Operation First Published: August 14. IP SLAs is a portfolio of technology embedded in most devices that run Cisco IOS software.cisco. Contents • • • • • Prerequisites for the IP SLAs DLSw+ Operation. go to http://www. use the “Feature Information for the IP SLAs DLSw+ Operation” section on page 12. . page 2 How to Configure the IP SLAs DLSw+ Operation. This module also demonstrates how the results of the DLSw+ operation can be displayed and analyzed to determine the DLSw+ peer tunnel response time. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module. 170 West Tasman Drive. IP SLAs uses active traffic monitoring—the generation of traffic in a continuous. and to reduce the frequency of network outages.

Router A and Router B are configured as connected DLSw+ peers. Information About the IP SLAs DLSw+ Operation To perform the tasks required to analyze DLSw+ peer response times using IP SLA. In Figure 1. you should understand the following concept: • DLSw+ Operation. Figure 1 DLSw+ Operation DLSw+ operation Router A 172. Router A is configured as the source IP SLAs device and a DLSw+ operation is configured with Router B as the remote DLSw+ peer. DLSw+ peers normally communicate through TCP port 2065.26. The peer (destination device) does not have to run a Cisco IOS IP SLA-capable image.IP SLAs—Analyzing IP Service Levels Using the DLSw+ Operation Prerequisites for the IP SLAs DLSw+ Operation • • Additional References. page 2 DLSw+ Operation The Cisco IOS IP SLAs DLSw+ operation measures the DLSw+ protocol stack and network response time between DLSw+ peers.20. The networking devices performing the tunneling of non-routable traffic into TCP/IP are referred to as DLSw+ peers. The destination networking device does not have to be a Cisco router if it supports RFC 1795.10 Router B 172. DLSw+ tunnels non-routable Layer 2 traffic such as Systems Network Architecture (SNA) traffic over IP backbones via TCP. This operation does not use the IP SLAs Responder.27.21. DLSw+ is the enhanced Cisco version of RFC 1795. page 12 Prerequisites for the IP SLAs DLSw+ Operation Before configuring the IP SLAs DLSw+ operation you should be familiar with the “Cisco IOS IP SLAs Overview” chapter of the Cisco IOS IP SLAs Configuration Guide. page 3 (required) 2 127029 . page 10 Feature Information for the IP SLAs DLSw+ Operation. How to Configure the IP SLAs DLSw+ Operation This section contains the following procedure: • Configuring and Scheduling a DLSw+ Operation on the Source Device.11 Network response time is computed by measuring the round-trip time (RTT) taken to connect to the remote DLSw+ peer using TCP.

Perform one of the following tasks in this section. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. 3. 7. 6. page 3 Configuring and Scheduling a DLSw+ Operation with Optional Parameters on the Source Device. enable configure terminal ip sla operation-number dlsw peer-ipaddr ip-address frequency seconds exit ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] exit 3 . 5. 2. page 5 Configuring and Scheduling a Basic DLSw+ Operation on the Source Device Perform this task to enable a DLSw+ operation without any optional parameters.IP SLAs—Analyzing IP Service Levels Using the DLSw+ Operation How to Configure the IP SLAs DLSw+ Operation Configuring and Scheduling a DLSw+ Operation on the Source Device To measure the response time between a Cisco device and a DLSw+ peer. 4. 8. SUMMARY STEPS 1. Prerequisites Before enabling the IP SLAs DLSw+ operation you must configure a connected DLSw+ peer between the source and destination networking devices. This operation does not require the IP SLAs Responder to be enabled so there are no tasks to be performed on the destination device. use the IP SLAs DLSw+ operation. depending on whether you want to configure a basic DLSw+ operation or configure a DLSw+ operation with optional parameters: • • Configuring and Scheduling a Basic DLSw+ Operation on the Source Device. Note For information on scheduling a group of operations.

Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. • Enter your password if prompted. Example: Router(config)# exit What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. 4 . Example: Router(config-ip-sla-dlsw)# frequency 30 Step 6 exit Exits IP SLA DLSw+ configuration mode and returns to global configuration mode.21.IP SLAs—Analyzing IP Service Levels Using the DLSw+ Operation How to Configure the IP SLAs DLSw+ Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode.11 Step 5 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats. Example: Router(config)# ip sla schedule 10 start-time now life forever Step 8 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode. Example: Router(config-ip-sla-dlsw)# exit Step 7 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Configures the scheduling parameters for an individual IP SLAs operation. Example: Router(config-ip-sla)# dlsw peer-ipaddr 172. Example: Router> enable Step 2 configure terminal Enters global configuration mode. Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode.27. Example: Router(config)# ip sla 10 Step 4 dlsw peer-ipaddr ip-address Defines a DLSw+ operation and enters IP SLA DLSw+ configuration mode.

2. history statistics-distribution-interval milliseconds 15. Prerequisites Before enabling the IP SLAs DLSw+ operation you must configure a connected DLSw+ peer between the source and destination networking devices. 9. 5. SUMMARY STEPS 1. request-data-size bytes 14. history hours-of-statistics-kept hours 11.IP SLAs—Analyzing IP Service Levels Using the DLSw+ Operation How to Configure the IP SLAs DLSw+ Operation Configuring and Scheduling a DLSw+ Operation with Optional Parameters on the Source Device Perform this task to enable a DLSw+ operation on the source device and configure some optional IP SLAs parameters. exit 21. history lives-kept lives 12. 8. ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] 20. Note For information on scheduling a group of operations. enable configure terminal ip sla operation-number dlsw peer-ipaddr ip-address history buckets-kept size history distributions-of-statistics-kept size history enhanced [interval seconds] [buckets number-of-buckets] history filter {none | all | overThreshold | failures} frequency seconds 10. see the “IP SLAs—Multioperation Scheduling of IP SLAs Operations” chapter of the Cisco IOS IP SLAs Configuration Guide. tag text 16. 3. timeout milliseconds 18. 4. 6. threshold milliseconds 17. owner owner-id 13. 7. exit 19. show ip sla configuration [operation-number] 5 . The source device is the location at which the measurement statistics are stored.

Example: Router(config-ip-sla-dlsw)# history distributions-of-statistics-kept 5 Step 7 history enhanced [interval seconds] [buckets number-of-buckets] (Optional) Enables enhanced history gathering for an IP SLAs operation.21. Example: Router(config-ip-sla-dlsw)# frequency 30 6 . Example: Router# configure terminal Step 3 ip sla operation-number Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. Example: Router(config)# ip sla 10 Step 4 dlsw peer-ipaddr ip-address Defines a DLSw+ operation and enters IP SLA DLSw configuration mode. Example: Router(config-ip-sla)# dlsw peer-ipaddr 172. • Enter your password if prompted. Example: Router(config-ip-sla-dlsw)# history buckets-kept 25 Step 6 history distributions-of-statistics-kept size (Optional) Sets the number of statistics distributions kept per hop during an IP SLAs operation. Example: Router(config-ip-sla-dlsw)# history filter failures Step 9 frequency seconds (Optional) Sets the rate at which a specified IP SLAs operation repeats.11 Step 5 history buckets-kept size (Optional) Sets the number of history buckets that are kept during the lifetime of an IP SLAs operation. Example: Router(config-ip-sla-dlsw)# history enhanced interval 900 buckets 100 Step 8 history filter {none | all | overThreshold | failures} (Optional) Defines the type of information kept in the history table for an IP SLAs operation. Example: Router> enable Step 2 configure terminal Enters global configuration mode.27.IP SLAs—Analyzing IP Service Levels Using the DLSw+ Operation How to Configure the IP SLAs DLSw+ Operation DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode.

Example: Router(config-ip-sla-dlsw)# history lives-kept 5 Step 12 owner owner-id (Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation. Example: Router(config-ip-sla-dlsw)# hours-of-statistics-kept 4 Step 11 history lives-kept lives (Optional) Sets the number of lives maintained in the history table for an IP SLAs operation. Example: Router(config-ip-sla-dlsw)# history statistics-distribution-interval 10 Step 15 tag text (Optional) Creates a user-specified identifier for an IP SLAs operation. (Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet. Example: Router(config-ip-sla-dlsw)# tag TelnetPollServer1 Step 16 threshold milliseconds Example: Router(config-ip-sla-dlsw)# threshold 10000 (Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation.IP SLAs—Analyzing IP Service Levels Using the DLSw+ Operation How to Configure the IP SLAs DLSw+ Operation Command or Action Step 10 history hours-of-statistics-kept hours Purpose (Optional) Sets the number of hours for which statistics are maintained for an IP SLAs operation. Example: Router(config-ip-sla-dlsw)# request-data-size 64 Step 14 history statistics-distribution-interval milliseconds (Optional) Sets the time interval for each statistics distribution kept for an IP SLAs operation. Step 17 timeout milliseconds Example: Router(config-ip-sla-dlsw)# timeout 10000 Step 18 exit Exits DLSw configuration submode and returns to global configuration mode. Example: Router(config-ip-sla-dlsw)# owner admin Step 13 request-data-size bytes (Optional) Sets the protocol data size in the payload of an IP SLAs operation's request packet. Example: Router(config-ip-sla-dlsw)# exit 7 .

Example: Router# show ip sla configuration 10 Examples The following sample output shows the configuration of all the IP SLAs parameters (including defaults) for the DLSw+ operation number 14.11 Request size (ARR data portion): 0 Operation timeout (milliseconds): 50000 Operation frequency (seconds): 50 Next Scheduled Start Time: Start Time already passed Group Scheduled: FALSE Life (seconds): 50 Entry Ageout (seconds): never Recurring (Starting Everyday): FALSE Status of entry (SNMP RowStatus): Active Threshold (milliseconds): 5000 Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20 Number of history Lives kept: 0 Number of history Buckets kept: 15 History Filter Type: None Troubleshooting Tips Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation. Example: Router(config)# exit Step 21 show ip sla configuration [operation-number] (Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation.27. Router# show ip sla configuration 14 Complete Configuration Table (includes defaults) Entry number: 14 Owner: Tag: DLSw-Test Type of operation to perform: dlsw Peer address: 172.21. 8 . Example: Router(config)# ip sla schedule 10 start-time now life forever Step 20 exit (Optional) Exits global configuration mode and returns to privileged EXEC mode.IP SLAs—Analyzing IP Service Levels Using the DLSw+ Operation How to Configure the IP SLAs DLSw+ Operation Command or Action Step 19 ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring] Purpose Configures the scheduling parameters for an individual IP SLAs operation.

a remote DLSw+ peer. page 9 Configuring a DLSw+ Operation: Example The following example shows how to configure a DLSw+ operation as shown in Figure 1 from Router A to Router B. Router B is configured as a DLSw+ peer and Router A is specified as the remote (connected) DLSw+ peer. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable.IP SLAs—Analyzing IP Service Levels Using the DLSw+ Operation Configuration Examples for the IP SLAs DLSw+ Operation What to Do Next To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. and the IP SLAs DLSw+ operation parameters are configured. Router A is then configured as a DLSw+ peer with Router B as the connected DLSw+ peer. Configuration Examples for the IP SLAs DLSw+ Operation This section contains the following configuration example: • Configuring a DLSw+ Operation: Example. 9 . The operation is scheduled to start immediately and run for 7200 seconds (2 hours).

see the Cisco IOS IP SLAs Features Roadmap. Additional References The following sections provide references related to the IP SLAs DLSw+ operation.27. and support for existing standards has not been modified by this feature.20. Cisco white paper Cisco IOS IP SLAs Command Reference Standards Standards Title No new or modified standards are supported by this — feature.27.11 ip sla 14 dlsw peer-ipaddr 172.21.26.21.11 dlsw remote-peer 0 tcp 172.10 dlsw remote-peer 0 tcp 172. Related Documents Related Topic Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands Document Title Cisco IOS IP Service Level Agreements Command Line Interface.IP SLAs—Analyzing IP Service Levels Using the DLSw+ Operation Where to Go Next Router B Configuration configure terminal dlsw local-peer peer-id 172.26.21. 10 .20.11 frequency 50 timeout 50000 tag DLSw-Test exit ip sla schedule 14 life 7200 start-time now Where to Go Next For information about other types of IP SLAs operations and IP SLAs features.10 Router A Configuration dlsw local-peer peer-id 172.27.

solutions.com users can log in from this page to access even more content. technologies. Cisco IOS releases. use Cisco MIB Locator found at the following URL: http://www.shtml 11 . containing 30.cisco. including links to products. and tools.IP SLAs—Analyzing IP Service Levels Using the DLSw+ Operation Additional References MIBs MIBs CISCO-RTTMON-MIB MIBs Link To locate and download MIBs for selected platforms. Registered Cisco.cisco. technical tips. Link http://www.com/public/support/tac/home.com/go/mibs RFCs RFCs RFC 1795 Title Data Link Switching: Switch-to-Switch Protocol Technical Assistance Description Technical Assistance Center (TAC) home page. and feature sets.000 pages of searchable technical content.

the Cisco Certified Internetwork Expert logo. An account on Cisco. iQuick Study. PCNow. the IronPort logo. The use of the word partner does not imply a partnership relationship between Cisco and any other company. PIX. Changing the Way We Work.com is not required. Use Cisco Feature Navigator to find information about platform support and software image support. Network Registrar. and the WebEx logo are registered trademarks of Cisco Systems. Inc. Cisco Nexus. the Cisco Systems logo. CCDA. Cisco StadiumVision. Catalyst. All rights reserved. Unless noted otherwise. MediaTone. WebEx. CCIE. TransPath. SenderBase. Cisco TelePresence. LightStream. the Cisco logo. subsequent releases of that Cisco IOS software release train also support that feature. Aironet. Networking Academy. Event Center. Spectrum Expert. Internet Quotient. EtherFast. and Access Registrar. IronPort. StackWise. Live. MeetingPlace. ScriptShare. Cisco Systems. The Fastest Way to Increase Your Internet Quotient. Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. EtherSwitch. All other trademarks mentioned in this document or Website are the property of their respective owners.com/go/cfn. Inc. Any use of actual IP addresses in illustrative content is unintentional and coincidental. and figures included in the document are shown for illustrative purposes only. For release information about a specific command. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release. CCENT. Any examples. AsyncOS. Follow Me Browsing. and Welcome to the Human Network are trademarks. Fast Step. Cisco Systems Capital. see the command reference documentation. Collaboration Without Limitation. and Learn and Cisco Store are service marks. feature set. Cisco. MGX. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Cisco Lumin. iPhone. DCE. Cisco Press. ProConnect. Linksys. command display output. Cisco IOS.3(14)T Feature Information The Cisco IOS IP SLAs Data Link Switching Plus (DLSw+) operation allows you to schedule and measure the DLSw+ protocol stack and network response time between DLSw+ peers CCDE. HomeLink. 12 . CCSP. SMARTnet. Networkers.cisco. Not all commands may be available in your Cisco IOS software release. FormShare. iQ Net Readiness Scorecard. To access Cisco Feature Navigator. and/or its affiliates in the United States and certain other countries.IP SLAs—Analyzing IP Service Levels Using the DLSw+ Operation Feature Information for the IP SLAs DLSw+ Operation Feature Information for the IP SLAs DLSw+ Operation Table 1 lists the release history for this feature. Cisco Unity. GigaDrive. iQ Expertise. CCIP. CCVP. PowerPanels. go to http://www. Cisco Eos. MeetingPlace Chime Sound. Table 1 Feature Information for the IP SLAs DLSw+ Operation Feature Name IP SLAs DLSw+ Operation Releases 12. CCDP. or platform. CCNA. IOS. © 2006-2008 Cisco Systems. Play. the iQ logo. CCNP. Bringing the Meeting To You.

network assessment. Cisco IOS IP SLAs allows you to analyze IP service levels for IP applications and services. CA 95134-1706 USA © 2006-2008 Cisco Systems. The ability to schedule hundreds of operations at once allows service providers with large networks to monitor service levels for multiple environments. use the “Feature Information for Multioperation Scheduling of IP SLAs Operations” section on page 17. In addition to allowing you to schedule multiple IP SLAs operations with a single command. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported. and predictable manner with proactive notification capabilities—for measuring network performance. An account on Cisco. go to http://www. to lower operational costs. Americas Headquarters: Cisco Systems. reliable. IP SLAs uses active traffic monitoring—the generation of traffic in a continuous. To access Cisco Feature Navigator.cisco. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module. All rights reserved. 170 West Tasman Drive. thereby enhancing the scalability of the IP SLAs monitoring solution.. 2008 This document describes how to schedule multiple operations at once using the Cisco IOS IP Service Level Agreements (SLAs) group-scheduling feature. Inc. IP SLAs can be used for network troubleshooting. This distribution helps to minimize the CPU utilization. 2006 Last Updated: July 16.com is not required.com/go/cfn. IP SLAs can be used to schedule operations to run at equal intervals. and health monitoring. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support.IP SLAs—Multioperation Scheduling of IP SLAs Operations First Published: August 14. automatically distributing the operations over a specified time frame. San Jose. to increase productivity. Inc. and to reduce occurences of network congestion or outages. .

This feature allows you to control the amount of IP SLAs monitoring traffic by scheduling the operations to run at evenly distributed times. Identify the network traffic type and the location of your network management station. Determine the IP SLAs operations you want to schedule as a single group. page 15 Additional References. page 15 Feature Information for Multioperation Scheduling of IP SLAs Operations. This feature automatically distributes the IP SLAs operations at equal intervals over a specified time frame. This distribution of IP SLAs operations helps minimize the CPU utilization and thereby enhances the scalability of the network. page 2 How to Schedule Multiple and Recurring IP SLAs Operations. Identify the topology and the types of devices in your network. You must specify the operation ID numbers to be scheduled and the time range over which all the IP SLAs operations should start. Multiple operations scheduling allows you to schedule multiple IP SLAs operations using a single command through the command line interface (CLI) or the CISCO-RTTMON-MIB. page 2 IP SLAs Random Scheduler. page 14 Where to Go Next. page 9 Configuration Examples for Multioperation Scheduling of IP SLAs Operations. If you have large networks with thousands of IP SLAs operations to monitor network performance.IP SLAs—Multioperation Scheduling of IP SLAs Operations Contents Contents • • • • • • • Prerequisites for Multioperation Scheduling of IP SLAs Operations. page 2 Information About Scheduling Multiple and Recurring IP SLAs Operations. normal scheduling (scheduling each operation individually) will be inefficient and time-consuming. Information About Scheduling Multiple and Recurring IP SLAs Operations To schedule IP SLAs as multiple or recurring operations. page 9 Scheduling of Multiple IP SLAs Operations Normal scheduling of IP SLAs operations allows you to schedule one operation at a time. 2 . Decide on the frequency of testing for each operation. The spacing between the operations (start interval) is calculated and the operations are started. you should understand the following concept: • • Scheduling of Multiple IP SLAs Operations. page 17 Prerequisites for Multioperation Scheduling of IP SLAs Operations • • • • • Configure the IP SLAs operations before group scheduling those operations.

page 7 Note The examples that follow focus on the interaction of the schedule period and frequency values. Start time—Time when the operation starts collecting information. Schedule period—Amount of time for which the IP SLAs operation group is scheduled. it overwrites the operation frequency of all operations belonging to the group. The IP SLAs multiple operations scheduling functionality displays a message showing the number of active and missing operations. the default frequency will be the same as that of the schedule period. The schedule period is the period of time in which all the specified operations should run. is not included in the illustrations. and month. The operation can be configured to run indefinitely. The following sections explain the IP SLAs multiple operations scheduling process: • • • • Default Behavior of IP SLAs Multiple Operations Scheduling. this functionality skips those IP SLAs operations that are already running or those that are not configured and hence do not exist. the lifetime of an operation is one hour. The following parameters can be configured with this command: • • • • • Group operation number—Group configuration or group schedule number of the IP SLAs operation to be scheduled. then some of the operations would detect the network failure. 3 . Operations of the same type and same frequency should be used for IP SLAs multiple operations scheduling. then this failure would never be detected by any of the 60 operations. Operation ID numbers—A list of IP SLAs operation ID numbers in the scheduled operation group. • • The IP SLAs multiple operations scheduling functionality schedules the maximum number of operations possible without aborting. the frequency for each operation is set to the value of the schedule period. consider configuring 60 operations to start during the same 1-second interval over a 60-second schedule period. these messages are displayed only if you schedule operations that are not configured or are already running. page 4 Multiple Operations Scheduling When the Number of IP SLAs Operations Are Greater Than the Schedule Period. However. minutes. The total number of operations will be calculated based on the number of operations specified in the command. day. Life—Amount of time the operation actively collects information. Frequency—Amount of time after which each IP SLAs operation is restarted. However. You can specify an operation to start immediately or at an absolute start time using hours. However. Ageout—Amount of time to keep the operation in memory when it is not actively collecting information. By default. seconds. if a network failure occurs when all 60 operations are active. Conversely.IP SLAs—Multioperation Scheduling of IP SLAs Operations Information About Scheduling Multiple and Recurring IP SLAs Operations The IP SLAs multiple operations scheduling functionality allows you to schedule multiple IP SLAs operations as a group using the ip sla group schedule command. Note that when the frequency option is not specified. so the additional command syntax. If a network failure occurs 30 seconds after all 60 operations have started and the network is restored before the operations are due to start again (in another 30 seconds). indicating that the failure is possibly more severe than it really is. such as start time and lifetime values. irrespective of the number of operations that are missing or already running. When the frequency option is specified. A main benefit for scheduling multiple IP SLAs operations is that the load on the network is reduced by distributing the operations equally over a scheduled period. To illustrate this scenario. page 6 IP SLAs Multiple Operations Scheduling with Scheduling Period Greater Than Frequency. the operation remains in memory indefinitely. if the 60 operations are distributed equally at 1-second intervals over a 60-second schedule period. This distribution helps you to achieve more consistent monitoring coverage. By default. page 4 IP SLAs Multiple Operations Scheduling with Scheduling Period Less Than Frequency. then all 60 operations would fail. If you do not specify a frequency.

By default. This example schedules operation 1 to operation 10 within operation group 1. As shown in Figure 1. The start time of each IP SLAs operation is evenly distributed over the schedule period by dividing the schedule period by the number of operations (20 seconds divided by 10 operations). 2nd iteration = operation x starts 170556 ys = timeline. 1st iteration = operation ID number. In the example shown in Figure 1. Figure 1 Schedule Period Equals Frequency—Default Behavior ip sla group schedule 1 1-10 schedule-period 20 [frequency 20] 1 2 3 4 5 6 7 8 9 10 1 2 0s 2s 4s 6s 8s 10s 12s 14s 16s 18s 20s 22s schedule-period (10 operations in 20 seconds) frequency (restart group every 20 seconds) x x = operation ID number. which means that all operations in the group will be started at equal intervals within a 20-second period. the first operation (operation 1) in operation group 1 will start at 0 seconds. the ip sla group schedule 1 1-10 schedule-period 20 frequency 30 command is configured. Operation group 2 has a schedule period of 20 seconds and a frequency of 30 seconds. All 10 operations in operation group 1 (operation 1 to operation 10) must be started in the schedule period of 20 seconds. The frequency is the period of time that passes before the operation group is started again (repeated). operation group 1 will start again every 20 seconds. there will be a period of time in which no operations are started. each operation will start 2 seconds after the previous operation. In the example shown in Figure 1. This configuration provides optimal division (spacing) of operations over the specified schedule period. IP SLAs Multiple Operations Scheduling with Scheduling Period Less Than Frequency As the frequency value in the ip sla group schedule configuration is the amount of time that passes before the schedule group is restarted. if the schedule period is less than the frequency. Therefore. If the frequency is not specified. This example schedules operation 1 to operation 10 within operation group 2. configuring the frequency is optional because 20 is the default. 4 . continues until the lifetime value is reached = y seconds In this example. Operation group 1 has a schedule period of 20 seconds. the frequency is set to the value of the schedule period. the frequency is set to the same value as the configured schedule period. In the example shown in Figure 2.IP SLAs—Multioperation Scheduling of IP SLAs Operations Information About Scheduling Multiple and Recurring IP SLAs Operations Default Behavior of IP SLAs Multiple Operations Scheduling The IP SLAs Multiple Operations Scheduling feature allows you to schedule multiple IP SLAs operations as a group using the ip sla group schedule command. the ip sla group schedule 1 1-10 schedule-period 20 [frequency 20] command is configured.

The lifetime can be configured using the ip sla group schedule command. 1st iteration = operation ID number. 3rd iteration = operation x starts 170558 ys = timeline. continues until the lifetime value is reached = y seconds In this example. there is a gap of 10 seconds as no operations are started in the time from 19 seconds to 29 seconds. At 30 seconds. All 10 operations in operation group 2 (operation 1 to operation 10) must be started in the schedule period of 20 seconds. However. From 19 to 29 seconds. the first operation (operation 1) in operation group 2 is started. the last operation (operation 10) in operation group 2 is started. Hence. the second iteration of operation group 2 starts. In the first iteration of operation group 2. the first operation (operation 1) in operation group 2 is started again. each operation will start 2 seconds after the previous operation. and the second iteration of operation group 2 ends. At 18 seconds. So.IP SLAs—Multioperation Scheduling of IP SLAs Operations Information About Scheduling Multiple and Recurring IP SLAs Operations Figure 2 Schedule Period Is Less Than Frequency ip sla group schedule 2 1-10 schedule-period 20 frequency 30 1 2 3 4 5 6 7 8 9 10 1 2 3 4 5 6 7 8 9 10 1 2 0s 2s 4s 6s 8s 10s 12s 14s 16s 18s 20s 22s 24s 26s 28s 30s 32s 34s 36s 38s 40s 42s 44s 46s 48s 50s 52s 54s 56s 58s 60s 62s schedule-period (20 seconds) frequency (restart every 30 seconds) x x x schedule period (20 seconds) frequency (restart every 30 seconds) = operation ID number. As shown in Figure 2. the last operation (operation 10) in the operation group 2 will always start 18 seconds after the first operation (operation 1). no operations are started. at 30 seconds. The default lifetime for an operation group is forever. the first operation (operation 1) in operation group 2 will start at 0 seconds. This process continues until the lifetime of operation group 2 ends. At 48 seconds (18 seconds after the second iteration started) the last operation (operation 10) in operation group 2 is started. because the group frequency has been configured to 30 seconds each operation in the operation group is restarted every 30 seconds. 2nd iteration = operation ID number. Therefore. The start time of each IP SLAs operation is evenly distributed over the schedule period by dividing the schedule period by the number of operations (20 seconds divided by 10 operations). and the last operation (operation 10) starts at 18 seconds. This means that the first iteration (schedule period) of operation group 1 ends here. operation 1 starts at 0 seconds. after 18 seconds. the third iteration of operation group 2 starts. The second iteration of operation group 2 starts here. the following events occur when the ip sla group schedule 1 1-10 schedule-period 20 frequency 30 command is configured: • • • • • • At 0 seconds. At 60 seconds. 5 . As all ten operations in the operation group 2 must start at an evenly distributed interval in the configured schedule period of 20 seconds.

In the example shown in Figure 3. then the operations are equally divided at the start of the schedule period with the remaining operations to start at the last 1-second interval. Therefore. However. Therefore. Figure 3 Number of IP SLAs Operations Is Greater Than the Schedule Period—Even Distribution ip sla group schedule 3 1-10 schedule-period 5 frequency 10 1 2 3 4 5 6 7 8 9 10 1 2 3 4 0s 1s 2s 3s 4s 5s 6s 7s 8s 9s 10s 12s schedule-period (5 seconds) frequency (10 seconds) x x = operation ID number. 6 . continues until the lifetime value is reached = y seconds In this example. which equals one operation every 0. the IP SLAs multiple operations scheduling functionality will schedule more than one operation to start within the same 1-second interval. Operation group 3 has a schedule period of 5 seconds and a frequency of 10 seconds. 2nd iteration = operation x starts 170560 ys = timeline.5 seconds) the start time of each IP SLAs operation is less than 1 second. when dividing the schedule period by the number of operations (5 seconds divided by 10 operations. Since the minimum time interval between the start of IP SLAs operations in a group operation is 1 second. if the number of operations to be multiple scheduled is greater than the schedule period. as shown in Figure 3. each iteration of operation group 3 will start 10 seconds after the start of the previous iteration. the ip sla group schedule 3 1-10 schedule-period 5 frequency 10 command is configured. As the frequency is set to 10 in this example. If the number of operations getting scheduled does not equally divide into 1-second intervals. the IP SLAs multiple operations scheduling functionality instead calculates how many operations it should start in each 1-second interval by dividing the number of operations by the schedule period (10 operations divided by 5 seconds). two operations will be started every 1 second. If the number of operations getting scheduled does not equally divide into 1-second intervals.IP SLAs—Multioperation Scheduling of IP SLAs Operations Information About Scheduling Multiple and Recurring IP SLAs Operations Multiple Operations Scheduling When the Number of IP SLAs Operations Are Greater Than the Schedule Period The minimum time interval between the start of IP SLAs operations in a group operation is 1 second. this distribution is not optimal as there is a gap of 5 seconds (frequency minus schedule period) between the cycles. This example schedules operation 1 to operation 10 within operation group 3. then the operations are equally divided at the start of the schedule period with the remaining operations to start at the last 1-second interval. 1st iteration = operation ID number.

2nd iteration = operation x starts 170562 ys = timeline. there will be a period of time in which the operations in one iteration of an operation group overlap with the operations of the following iteration. the ip sla group schedule 4 1-10 schedule-period 4 frequency 5 command is configured. 1st iteration = operation ID number. This example schedules operation 1 to operation 10 within operation group 4. Figure 4 Number of IP SLAs Operations Is Greater Than the Schedule Period—Uneven Distribution ip sla group schedule 4 1-10 schedule-period 4 frequency 5 1 2 3 4 5 6 7 8 9 10 1 2 3 0s 1s 2s 3s 4s 5s schedule-period (4 seconds) frequency (5 seconds) x x = operation ID number. Since the number of operations does not equally divide into 1-second intervals. IP SLAs Multiple Operations Scheduling with Scheduling Period Greater Than Frequency As the frequency value in the ip sla group schedule configuration is the amount of time that passes before the schedule group is restarted. the IP SLAs multiple operations scheduling functionality calculates how many operations it should start in each 1-second interval by dividing the number of operations by the schedule period (10 operations divided by 4 seconds. This example schedules operation 1 to operation 10 within operation group 5. Operation group 4 has a schedule period of 4 seconds and a frequency of 5 seconds. 7 . In the example shown in Figure 5. the ip sla group schedule 5 1-10 schedule-period 20 frequency 10 command is configured. which equals 2. if the schedule period is greater than the frequency. this number will be rounded off to the next whole number (see Figure 4) with the remaining operations to start at the last 1-second interval.IP SLAs—Multioperation Scheduling of IP SLAs Operations Information About Scheduling Multiple and Recurring IP SLAs Operations In the example shown in Figure 4. continues until the lifetime value is reached = y seconds In this example.5 operations every 1 second). Operation group 5 has a schedule period of 20 seconds and a frequency of 10 seconds.

but will be within the same 2-second interval. 3rd iteration = operation ID number. page 6). the second iteration of operation group 5 starts again at 10 seconds. Therefore. the last operation in the operation group. there is an overlap of operations 6 to 10 of the second iteration with operations 1 to 5 of the third iteration during the time period of 20 to 28 seconds. Similarly. continues until the lifetime value is reached = y seconds In this example. 1st iteration = operation ID number. The configuration described in this section is not recommended as you can configure multiple operations to start within the same 1-second interval by configuring the number of operations greater than the schedule period (see the Multiple Operations Scheduling When the Number of IP SLAs Operations Are Greater Than the Schedule Period. each operation will start 2 seconds after the previous operation. 2nd iteration = operation ID number. operation 1 starts at 0 seconds. 8 . Therefore. All 10 operations in operation group 5 (operation 1 to operation 10) must be started in the schedule period of 20 seconds. starts at 18 seconds. the start time of operation 1 and operation 6 need not be at exactly the same time. Because the operation group is configured to restart every 10 seconds (frequency 10). an overlap of operations 6 to 10 of the first iteration occurs with operations 1 to 5 of the second iteration during the time period of 10 to 18 seconds (see Figure 5).IP SLAs—Multioperation Scheduling of IP SLAs Operations Information About Scheduling Multiple and Recurring IP SLAs Operations Figure 5 IP SLAs Group Scheduling with Schedule Period Greater Than Frequency ip sla group schedule 5 1-10 schedule-period 20 frequency 10 1 2 3 4 5 6 1 7 2 8 3 9 4 10 5 6 1 7 2 8 3 9 4 10 5 6 1 7 2 8 3 0s 2s 4s 6s 8s 10s 12s 14s 16s 18s 20s 22s 24s 26s 28s 30s 32s 34s schedule-period (20 seconds) schedule-period (20 seconds) schedule-period (20 seconds) frequency (restart every 10 seconds) frequency (restart every 10 seconds) x x x x frequency (restart every 10 seconds) = operation ID number. 4th iteration = operation x starts 170564 ys = timeline. the first operation (operation 1) in operation group 5 will start at 0 seconds. In the first iteration of operation group 5. In this example. before the first iteration is completed. The start time of each IP SLAs operation is evenly distributed over the schedule period by dividing the schedule period by the number of operations (20 seconds divided by 10 operations). and operation 10.

If the random scheduler option is disabled. The IP SLAs random scheduler option is disabled by default.3(8)T. The minimum time interval between the start of each operation in a group operation is 100 milliseconds (0. The first operation will always begin at 0 milliseconds of the schedule period. The individual operations in a group operation will be uniformly distributed to begin at random intervals over the schedule period. The starting value of the frequency range should be greater than the schedule period (amount of time for which the group operation is scheduled). With the IP SLAs Random Scheduler feature. multiple operations can begin at the same time. Only one operation can be scheduled to begin at any given time.1 seconds). To enable the random scheduler option. Each task in the list is identified as either required or optional. If the random scheduler option is disabled. The IP SLAs Multioperation Scheduling feature provides the capability to easily schedule multiple IP SLAs operations to begin at intervals equally distributed over a specified duration of time and to restart at a specified frequency. the minimum time interval is 1 second. • • • Scheduling Multiple IP SLAs Operations. The group of operations restarts at uniformly distributed random frequencies within the specified frequency range. The order in which each operation in a group operation begins is random. page 11 (optional) Verifying IP SLAs Multiple Operations Scheduling. page 10 (required) Enabling the IP SLAs Random Scheduler. page 12 (optional) 9 . The group of operations restarts at uniformly distributed random frequencies within the specified frequency range. This guideline ensures that the same operation does not get scheduled more than once within the schedule period.IP SLAs—Multioperation Scheduling of IP SLAs Operations How to Schedule Multiple and Recurring IP SLAs Operations IP SLAs Random Scheduler The IP SLAs Random Scheduler feature is an enhancement to the existing IP SLAs Multioperation Scheduling feature introduced in Cisco IOS Release 12. Note The IP SLAs Random Scheduler feature is not in compliance with RFC2330. The following guidelines apply for setting the frequency range: • • The starting value of the frequency range should be greater than the timeout values of all the operations in the group operation. you can now schedule multiple IP SLAs operations to begin at random intervals uniformly distributed over a specified duration of time and to restart at uniformly distributed random frequencies within a specified frequency range. Random scheduling improves the statistical metrics for assessing network performance. you must set a frequency range when configuring the ip sla group schedule command in global configuration mode. because it does not account for inter-packet randomness. The following guidelines apply if the random scheduler option is enabled: • • • • • • How to Schedule Multiple and Recurring IP SLAs Operations This section contains the following tasks.

The operation ID numbers are limited to a maximum of 125 characters. enable configure terminal ip sla group schedule group-operation-number operation-id-numbers schedule-period schedule-period-range [ageout seconds] [frequency group-operation-frequency] [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] exit show ip sla group schedule show ip sla configuration 4.IP SLAs—Multioperation Scheduling of IP SLAs Operations How to Schedule Multiple and Recurring IP SLAs Operations Scheduling Multiple IP SLAs Operations Perform this task to schedule multiple IP SLAs operations using a single command. you should configure all the IP SLAs operations that will be used in that group. • Enter your password if prompted. 5. 2. 3. see the Cisco IOS IP SLAs Features Roadmap. Example: Router> enable Step 2 configure terminal Enters global configuration mode. DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged Exec mode. SUMMARY STEPS 1. Restrictions • • The frequency of all operations scheduled in the operation group should be the same. Prerequisites Before scheduling a group of operations. Example: Router# configure terminal 10 . 6. For information about configuring specific IP SLAs operation types. Do not give large integer values as operation ID numbers.

2. • • The group-operation-number argument identifies the IP SLAs operation ID to be group scheduled. Example: Router# show ip sla configuration Enabling the IP SLAs Random Scheduler Perform this task to schedule multiple IP SLAs operations to begin at random intervals uniformly distributed over a specified duration of time and to restart at uniformly distributed random frequencies within a specified frequency range.IP SLAs—Multioperation Scheduling of IP SLAs Operations How to Schedule Multiple and Recurring IP SLAs Operations Command or Action Step 3 ip sla group schedule group-operation-number operation-id-numbers schedule-period schedule-period-range [ageout seconds] [frequency group-operation-frequency] [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] Purpose Specifies an IP SLAs operation group number and the range of operation numbers to be scheduled in global configuration mode. 11 . Example: Router# ip sla group schedule 1 3. Example: Router# show ip sla group schedule Step 6 show ip sla configuration (Optional) Displays the IP SLAs configuration details.4. Example: Router# end Step 5 show ip sla group schedule (Optional) Displays the IP SLAs group schedule details. The operation-id-numbers argument specifies the number of operations that need to be group scheduled. enable configure terminal ip sla group schedule group-operation-number operation-id-numbers schedule-period seconds [ageout seconds] [frequency [seconds | range random-frequency-range]] [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] exit 4. 3.6-9 Step 4 end Returns to the privileged Exec mode. Prerequisites Before scheduling a group of operations. you should configure all the IP SLAs operations that will be used in that group. SUMMARY STEPS 1. see the Cisco IOS IP SLAs Features Roadmap. For information about configuring specific IP SLAs operation types.

• To enable the IP SLAs random scheduler option. show ip sla group schedule.IP SLAs—Multioperation Scheduling of IP SLAs Operations How to Schedule Multiple and Recurring IP SLAs Operations DETAILED STEPS Command or Action Step 1 enable Purpose Enables privileged EXEC mode. Example: Router# configure terminal Step 3 ip sla group schedule group-operation-number operation-id-numbers schedule-period seconds [ageout seconds] [frequency [seconds | range random-frequency-range]] [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] Specifies the scheduling parameters of a group of IP SLAs operations. Example: Router# exit Verifying IP SLAs Multiple Operations Scheduling To verify and analyze the scheduled operation. Example: Router> enable Step 2 configure terminal Enters global configuration mode. SUMMARY STEPS 1. use the show ip sla statistics. • Enter your password if prompted. and show ip sla configuration commands. 2. show ip sla statistics show ip sla group schedule show ip sla configuration 12 . you must configure the frequency range random-frequency-range keywords and argument. 3. Example: Router# ip sla group schedule 2 1-3 schedule-period 50 frequency range 80-100 Step 4 exit Exits global configuration mode and returns to privileged EXEC mode.

Example: Router# show ip sla group schedule Step 3 show ip sla configuration (Optional) Displays the IP SLAs configuration details. the frequency is equivalent to the schedule period.0. Example: Router# show ip sla configuration Examples After you have scheduled the multiple IP SLAs operations.31.2. The following example schedules IP SLAs operations 1 through 20 in the operation group 1 with a schedule period of 60 seconds and a life value of 1200 seconds. The last line in the example indicates that the IP SLAs operations are multiple scheduled (TRUE). Router# show ip sla configuration 1 Entry number: 1 Owner: Tag: Type of operation to perform: udpEcho Target address: 10. By default.121 Source address: 0. Example: Router# show ip sla statistics Step 2 show ip sla group schedule (Optional) Displays the IP SLAs group schedule details.0 Target port: 9001 Source port: 0 13 .IP SLAs—Multioperation Scheduling of IP SLAs Operations How to Schedule Multiple and Recurring IP SLAs Operations DETAILED STEPS Command or Action Step 1 show ip sla statistics Purpose (Optional) Displays the IP SLAs operation details. Router# ip sla group schedule 1 1-20 schedule-period 60 life 1200 The following example shows the details of the scheduled multiple IP SLAs operation using the show ip sla group schedule command. you can verify the latest operation details using the above show commands.0. In this example. Router# show ip sla group schedule Group Entry Number: 1 Probes to be scheduled: 1-20 Total number of probes: 20 Schedule period: 60 Group operation frequency: Equals schedule period Status of entry (SNMP RowStatus): Active Next Scheduled Start Time: Start Time already passed Life (seconds): 1200 Entry Ageout (seconds): never The following example shows the details of the scheduled multiple IP SLAs operation using the show ip sla configuration command. the start interval is 3 seconds (schedule period divided by number of operations).

755 *03:06:48.752 *03:07:12.755 *03:06:57.755 *03:06:39.752 *03:06:42.754 *03:06:27.753 *03:07:03.752 *03:07:09.760 *03:06:24. when the operations are scheduled at equal intervals.754 *03:07:06.753 *03:06:45. using the show ip sla statistics command: Router# show ip sla statistics | include Latest operation start time Latest Latest Latest Latest Latest Latest Latest Latest Latest Latest Latest Latest Latest Latest Latest Latest Latest Latest Latest Latest operation operation operation operation operation operation operation operation operation operation operation operation operation operation operation operation operation operation operation operation start start start start start start start start start start start start start start start start start start start start time: time: time: time: time: time: time: time: time: time: time: time: time: time: time: time: time: time: time: time: *03:06:21.751 *03:06:30.IP SLAs—Multioperation Scheduling of IP SLAs Operations Configuration Examples for Multioperation Scheduling of IP SLAs Operations Request size (ARR data portion): 16 Operation timeout (milliseconds): 5000 Type Of Service parameters: 0x0 Verify data: No Data pattern: Vrf Name: Control Packets: enabled Operation frequency (seconds): 60 Next Scheduled Start Time: Start Time already passed Life (seconds): 1200 Entry Ageout (seconds): never Recurring (Starting Everyday): FALSE Status of entry (SNMP RowStatus): Active Threshold (milliseconds): 5000 Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20 Enhanced History: Number of history Lives kept: 0 Number of history Buckets kept: 15 History Filter Type: None Group Scheduled : TRUE The following example shows the latest operation start time of the scheduled multiple IP SLAs operation.752 UTC UTC UTC UTC UTC UTC UTC UTC UTC UTC UTC UTC UTC UTC UTC UTC UTC UTC UTC UTC Tue Tue Tue Tue Tue Tue Tue Tue Tue Tue Tue Tue Tue Tue Tue Tue Tue Tue Tue Tue Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct 21 21 21 21 21 21 21 21 21 21 21 21 21 21 21 21 21 21 21 21 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 Configuration Examples for Multioperation Scheduling of IP SLAs Operations This section provides the following configuration examples: • • Scheduling Multiple IP SLAs Operations: Example. page 15 Enabling the IP SLAs Random Scheduler: Example.752 *03:06:51.754 *03:06:36.752 *03:06:33.755 *03:07:18. page 15 14 .753 *03:07:15.752 *03:07:00.753 *03:06:54.

The last line in the example indicates that the IP SLAs operations are multiple scheduled (TRUE). Router# ip sla group schedule 1 1-10 schedule-period 20 The following example shows the details of the scheduled multiple IP SLAs operation using the show ip sla group schedule command. The random scheduler option is enabled and the uniformly distributed random frequencies at which the group of operations will restart is chosen within the range of 80-100 seconds. By default. Router# show ip sla group schedule Multi-Scheduling Configuration: Group Entry Number: 1 Probes to be scheduled: 1-10 Schedule period :20 Group operation frequency: 20 Multi-scheduled: TRUE Enabling the IP SLAs Random Scheduler: Example The following example shows how to schedule IP SLAs operations 1 to 3 as a group (identified as group 2). see the Cisco IOS IP SLAs Features Roadmap. ip sla group schedule 2 1-3 schedule-period 50 frequency range 80-100 start-time now Where to Go Next For information about other types of IP SLAs operations and IP SLAs features.IP SLAs—Multioperation Scheduling of IP SLAs Operations Where to Go Next Scheduling Multiple IP SLAs Operations: Example The following example schedules IP SLAs operations 1 to 10 in the operation group 1 with a schedule period of 20 seconds. Additional References The following sections provide references related to IP SLAs group scheduling. Related Documents Related Topic Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands Document Title Cisco IOS IP Service Level Agreements Command Line Interface. The first operation is scheduled to start immediately. In this example. the frequency is equivalent to the schedule period. Cisco white paper Cisco IOS IP SLAs Command Reference 15 . the operations are scheduled to begin at uniformly distributed random intervals over a schedule period of 50 seconds.

com/techsupport 16 . Link http://www. use Cisco MIB Locator found at the following URL: http://www.IP SLAs—Multioperation Scheduling of IP SLAs Operations Additional References Standards Standards No new or modified standards are supported by this feature. and feature sets. To receive security and technical information about your products. Title — MIBs MIBs CISCO-RTTMON-MIB MIBs Link To locate and download MIBs for selected platforms. such as the Product Alert Tool (accessed from Field Notices).cisco. Title — Technical Assistance Description The Cisco Support website provides extensive online resources. Access to most tools on the Cisco Support website requires a Cisco.cisco.com user ID and password. the Cisco Technical Services Newsletter. and Really Simple Syndication (RSS) Feeds.com/go/mibs RFCs RFCs No new or modified RFCs are supported by this feature. you can subscribe to various services. Cisco IOS releases. including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

Aironet. Cisco StadiumVision. MeetingPlace Chime Sound. CCDA. Networking Academy. PCNow. the Cisco Systems logo.IP SLAs—Multioperation Scheduling of IP SLAs Operations Feature Information for Multioperation Scheduling of IP SLAs Operations Feature Information for Multioperation Scheduling of IP SLAs Operations Table 1 lists the release history for this feature. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release. Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. page 15 CCDE. Fast Step. Cisco Press.2(33)SRB1. ProConnect. Internet Quotient. Spectrum Expert. Live. Bringing the Meeting To You. page 11 Enabling the IP SLAs Random Scheduler: Example. 12. Event Center. GigaDrive. The following sections provide information about this feature: • • • IP SLAs Random Scheduler. AsyncOS. and/or its affiliates in the United States and certain other countries. MeetingPlace. Changing the Way We Work. CCNA. and Access Registrar. ScriptShare.1 Feature Information The IP SLAs Multioperation Scheduler feature provides a highly scalable infrastructure for Cisco IOS IP SLAs by allowing you to schedule multiple IP SLAs operations using a single command. SenderBase. iPhone. CCIE. The Fastest Way to Increase Your Internet Quotient. The use of the word partner does not imply a partnership relationship between Cisco and any other company. To access Cisco Feature Navigator. Cisco IOS XE Release 2. WebEx. (0807R) 17 . iQ Expertise. IP SLAs Random Scheduler The IP SLAs Random Scheduler feature provides the capability to schedule multiple IP SLAs operations to begin at random intervals uniformly distributed over a specified duration of time and to restart at uniformly distributed random frequencies within a specified frequency range.2(33)SB. CCSP. Cisco. feature set. FormShare. PowerPanels. Catalyst. Cisco IOS. Inc. Cisco Eos. For release information about a specific command. 12. CCIP.cisco. HomeLink. Play. and Welcome to the Human Network are trademarks. DCE. the Cisco logo. Cisco Systems. Cisco Nexus. page 9 Enabling the IP SLAs Random Scheduler. CCVP. Use Cisco Feature Navigator to find information about platform support and software image support. Follow Me Browsing. LightStream. IronPort. Network Registrar. StackWise. Unless noted otherwise. or platform. PIX.2(31)SB2. iQuick Study. the Cisco Certified Internetwork Expert logo. 12.com/go/cfn. MGX. the IronPort logo. subsequent releases of that Cisco IOS software release train also support that feature. CCENT. CCNP. the iQ logo. Cisco Lumin. CCDP. and the WebEx logo are registered trademarks of Cisco Systems. see the command reference documentation. iQ Net Readiness Scorecard. Linksys. go to http://www.2(33)SXH. MediaTone. EtherFast. SMARTnet.4(2)T. All other trademarks mentioned in this document or Website are the property of their respective owners. 12. Table 1 Feature Information for IP SLAs Multiple Operation Scheduling Feature Name IP SLAs Multioperation Scheduler Releases 12. EtherSwitch. Not all commands may be available in your Cisco IOS software release.1 12.com is not required. Cisco Systems Capital. An account on Cisco. Cisco IOS XE Release 2. IOS. Networkers. Cisco TelePresence.3(14)T. Cisco Unity. TransPath. and Learn and Cisco Store are service marks. Collaboration Without Limitation.

and figures included in the document are shown for illustrative purposes only. 18 .IP SLAs—Multioperation Scheduling of IP SLAs Operations Feature Information for Multioperation Scheduling of IP SLAs Operations Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any use of actual IP addresses in illustrative content is unintentional and coincidental. © 2006-2008 Cisco Systems. All rights reserved. Inc. Any examples. command display output.

Inc. 170 West Tasman Drive. page 3 Examples of Proactive Threshold Monitoring Using IP SLA. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported. Cisco IOS IP SLAs allows you to montior. to increase productivity.com is not required.. page 11 Americas Headquarters: Cisco Systems. Contents • • • • • • Information About Proactive Threshold Monitoring for IP SLAs. page 6 Where to Go Next.com/go/cfn. 2008 This document describes the proactive monitoring capabilities of Cisco IOS IP Service Level Agreements (SLAs) using thresholds and reaction triggering. . page 9 Additional References. go to http://www. All rights reserved. page 2 How to Configure IP SLAs Reactions and Threshold Monitoring. An account on Cisco. to lower operational costs. IP SLAs uses active traffic monitoring for measuring network performance. 2006 Last Updated: July 16. analyze and verify IP service levels for IP applications and services. use the “Feature Information for IP SLAs Proactive Threshold Monitoring” section on page 11. CA 95134-1706 USA © 2007 Cisco Systems. page 9 Feature Information for IP SLAs Proactive Threshold Monitoring. To access Cisco Feature Navigator.IP SLAs—Proactive Threshold Monitoring of IP SLAs Operations First Published: August 14. San Jose. and to reduce occurances of network congestion or outages. Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. Inc. Finding Feature Information in This Module Your Cisco IOS software release may not support all of the features documented in this module.cisco.

notifications can be generated for violations in either direction (source to destination and destination to source) or for round trip values. IP SLAs reaction configuration is performed using the ip sla reaction-configuration command. These system logging messages can then be sent as SNMP notifications (traps) using the CISCO-RTTMON-MIB. Packet loss. issuing the no ip sla reaction-configuration operation-number will clear all reactions for the specified operation. to be sent when monitored values exceed an upper threshold or fall below a lower threshold. an SNMP trap can be triggered by 5 consecutive timeouts during an IP SLAs operation. You can check the configuration of the IP SLAs reaction configuration using the show ip sla reaction-configuration command. for most IP SLAs monitoring operations. Notifications can also be triggered for other events. page 2 IP SLAs Threshold Monitoring and Notifications. unidirectional latency and bidirectional round trip time and connectivity. IP SLAs can generate system logging (syslog) messages when a reaction condition occurs. However. jitter and MOS statistics are specific to IP SLAs Jitter operations. and also configuring MOS thresholds for same operation). This proactive monitoring capability provides options for configuring reaction thresholds for important VoIP related parameters including unidirectional jitter. the threshold type. so as to provide backwards compatibility with the earlier version of this command. IP SLAs supports threshold monitoring for performance parameters such as average jitter. or trigger another IP SLAs operation to gather more data. disabling of granular reaction elements (no ip sla reaction-configuration operation-number react monitored-element) is not currently supported. For example. 2 . The sending of SNMP traps is one of the options for triggered actions that can be configured for IP SLAs violations. or when a set of defined conditions are met. page 2 IP SLAs Reaction Configuration IP SLAs can be configured to react to certain measured network conditions. if IP SLAs measures too much jitter on a connection. For example. This allows for proactive monitoring in an environment where IT departments can be alerted to potential network problems. unidirectional packet loss. IP SLAs Threshold Monitoring and Notifications IP SLAs includes the capability for triggering SNMP notifications based on defined thresholds. In other words. and the triggered action are configured using the ip sla reaction-configuration global configuration mode command. The monitored values (also called monitored elements). you should understand the following concepts: • • IP SLAs Reaction Configuration. For packet loss and jitter.IP SLAs—Proactive Threshold Monitoring of IP SLAs Operations Information About Proactive Threshold Monitoring for IP SLAs Information About Proactive Threshold Monitoring for IP SLAs To perform the tasks required to configure proactive threshold monitoring using IP SLA. configuring thresholds for operation 1 for destination-to-source packet loss. and unidirectional VoIP voice quality scoring (MOS scores). IP SLAs can generate a notification to a network management application. You can configure the ip sla reaction-configuration command multiple times so as to allow reactions for multiple monitored elements (for example. SNMP notifications (traps) for IP SLAs can be configured as a triggered action. rather than having to manually examine data. such as round-trip-time violations.

3 . alert(2). How to Configure IP SLAs Reactions and Threshold Monitoring IP SLAs Reactions are configured using the ip sla reaction-configuration command. error(4). error (3). informational (6). and also configuring a MOS threshold for the same operation). but are sent as level 7 (info) traps from the CISCO-SYSLOG-MIB. critical(3). critical (2). entering the no ip sla reaction-configuration operation-number command will clear all reactions for the specified operation (in other words. info(7). However. so as to provide backwards compatibility with the earlier version of this command). Note Severity levels in the CISCO-SYSLOG-MIB are defined as follows: SyslogSeverity INTEGER { emergency(1). Use the snmp-server enable traps rtr command to enable the sending of IP SLAs SNMP trap notifications. This means that IP SLAs Threshold violations are logged as level 6 (informational) within the logging process. warning(5). warning (4). disabling of granular reaction elements is not currently supported. notice (5). Descriptions of some of the types of monitored elements available are described in the following sections: • • • • Configuring Triggers for Round-Trip-Time Violations Configuring Triggers for Jitter Violations Configuring Triggers for Packet Loss Violations Configuring Triggers for Mean Opinion Score Violations You can configure the ip sla reaction-configuration command multiple times so as to allow reactions for multiple monitored elements (for example. These monitored values and events are called monitored elements. or when a monitored event (such as a timeout or connection loss) occurs. alert (1).IP SLAs—Proactive Threshold Monitoring of IP SLAs Operations How to Configure IP SLAs Reactions and Threshold Monitoring SNMP traps for IP SLAs are supported by the CISCO-RTTMON-MIB and CISCO-SYSLOG-MIB. Use the ip sla logging traps command to enable the generation of SNMP system logging messages specific to IP SLAs trap notifications. The elements of this command are described in the following sections • • • Configuring Monitored Elements for IP SLAs Reactions [ react monitored-element ] Configuring Threshold Violation Types for IP SLAs Reactions [ threshold-type violation-condition] Specifying Reaction Events [action-type trap-or-trigger] Configuring Monitored Elements for IP SLAs Reactions IP SLAs reactions are configured to be triggered when a monitored value exceeds or falls below a specified level. debugging (7) }. notice(6). debug(8) } The values for severity levels are defined differently for the system logging process in Cisco IOS software: { emergency (0). configuring a threshold for operation 1 for destination-to-source packet loss.

To configure average destination-to-source jitter as the monitored element. rises above a specified threshold.IP SLAs—Proactive Threshold Monitoring of IP SLAs Operations How to Configure IP SLAs Reactions and Threshold Monitoring Configuring Triggers for Round-Trip-Time Violations Round-trip-time (rtt) is one of the monitored values of all IP SLAs operations. use the react jitterDSAvg keyword combination. destination-to-source. Jitter values are computed as source-to-destination. Example: Router# ip sla reaction-configuration 10 react rtt threshold-type immediate threshold-value 5000 3000 action-type trapAndTrigger Configuring Triggers for Jitter Violations Jitter (interpacket delay variance) is one of the monitored values of IP SLAs UDP Jitter operations. Events (such as traps) can be triggered when the average jitter value in either direction. To configure rtt as the monitored element. • Example: Router# ip sla reaction-configuration 10 react jitterAvg threshold-type immediate threshold-value 5000 3000 action-type trapAndTrigger To configure the average source-to-destination jitter as the monitored element. or when it falls below a specified threshold. Command or Action ip sla reaction-configuration operation-number react {jitterAvg | jitterDSAvg | jitterSDAvg} [threshold-type violation-type] threshold-value upper-threshold lower-threshold [action-type {trapOnly | triggerOnly | trapAndTrigger}] Purpose Configures an action (SNMP trap or IP SLAs trigger) to occur based on violations of thresholds for average round-trip jitter values. To configure average round-trip jitter as the monitored element. use the react jitterSDAvg keyword combination. or when it falls below a specified threshold. • • Configuring Triggers for Packet Loss Violations Pactket loss is one of the monitored values of IP SLAs UDP Jitter operations. 4 . Events (such as traps) can be triggered when the jitter value in either direction rises above a specified threshold. use the react jitterAvg keyword combination. Jitter values are computed as source-to-destination and destination-to-source values. Events (such as traps) can be triggered when the rtt value rises above a specified threshold. and combined round-trip values. or when it falls below a specified threshold. use the following version of the ip sla reaction-configuration command: Command or Action ip sla reaction-configuration operation-number react rtt [threshold-type violation-condition] threshold-value upper-threshold lower-threshold [action-type {trapOnly | triggerOnly | trapAndTrigger}] Purpose Configures an action (SNMP trap or IP SLAs trigger) to occur based on violations of thresholds for round-trip-time (rtt). or in both directions.

averaged—Triggers an event when the averaged totals of a value for x number of probe operations exceeds the specied upper-threshold value. To configure destination-to-source jitter as the monitored element . use the consecutive keyword with the optional number-of-occurrences argument: ip sla reaction-configuration operation-number react reaction-condition threshold-type consecutive [number-of-occurances] threshold-value raising-value falling-value action-type action-value The default value for number-of-occurances is 5. from a value of 1. or when the round-trip-time exceeds the upper threshold value 5 times in a row. the consecutive violation type could be used to configure an action to occur after a timeout occurs 5 times in a row. use the immediate threshold-type keyword: ip sla reaction-configuration operation-number react data-type threshold-type immediate threshold-value raising-value falling-value action-type action-value Generating Events for Consecutive Violations To generate a trap (or trigger another operation) after a certain number (x) of consecutive violations. consecutive—Triggers an event only after a violation occurs a specified number of times consecutively. connectionLoss. Configuring Triggers for Mean Opinion Score Violations Mean opinion score (MOS) is one of the monitored values of IP SLAs Jitter VoIP operations.IP SLAs—Proactive Threshold Monitoring of IP SLAs Operations How to Configure IP SLAs Reactions and Threshold Monitoring To configure source-to-destination packet loss as the monitored element. use the react PacketLossSD syntax in the ip sla reaction-configuration command. For example.00 (worst quality) to 5. or verifyError event occurs. or when it falls below a specified threshold. or when a timeout. use the react mos syntax in the ip sla reaction-configuration command. Generating Events for Each Violation To generate a trap (or trigger another operation) each time a specified condition is met. Threshold violation types are as follows: • immediate—Triggers an event immediately when the value for a reaction type (such as response time) exceeds the upper threshold value or falls below the lower threshold value. • • • Configuring these threshold violation types is described in the following sections.00 (best quality). Configuring Threshold Violation Types for IP SLAs Reactions The threhold-type syntax of the ip sla reaction-configuration command defines the type of threshold violation (or combination of threshold violations) that will trigger an event. Events (such as traps) can be triggered when the MOS value in either direction rises above a specified threshold. MOS values are computed as numbers to two decimal places. use the react PacketLossDS syntax in the ip sla reaction-configuration command. or falls below the lower-threshold value. x of y—Triggers an event after some number (x) of violations within some other number (y) of probe operations (x of y). 5 . To configure destination-to-source jitter as the monitored element .

The target operations to be triggered are specified using the ip sla reaction-trigger command. page 7 Triggering SNMP Notifications: Example. IP SLAs operation 10 (a UDP Jitter operation) is configured to send an SNMP logging trap when the MOS value exceeds 4. including the snmp-server enable traps syslog command. Generating Events for Averaged Violations To generate a trap (or trigger another operation) when the averaged totals of x number of probe operations violate a falling-threshold or rising-threshold.IP SLAs—Proactive Threshold Monitoring of IP SLAs Operations Examples of Proactive Threshold Monitoring Using IP SLA Generating Events for x of y Violations To generate a trap (or trigger another operation) after some number (x) of violations within some other number (y) of probe operations (x of y). triggerOnly—Have one or more target operation's operational state make the transition from "pending" to "active" when the violation conditions are met. A target operation will continue until its life expires.9 (best quality) of falls below 2. page 6 Verifying an IP SLAs Reaction Configuraiton: Example. as specified by the target operation's configured lifetime value). IP SLAs logging traps are enabled using the ip sla logging traps command. Examples of Proactive Threshold Monitoring Using IP SLA This section contains the following examples: • • • Configuring an IP SLAs Reaction Configuration: Example. Specifying Reaction Events Action type options for the ip sla reaction-configuration command are as follows: none—No action is taken. trapAndTrigger—Trigger both an SNMP trap and start another IP SLAs operation when the violation conditions are met.5 (poor quality): 6 . SNMP logging must be enabled using the appropriate SNMP commands. use the average [attempts] syntax: ip sla reaction-configuration operation-number react reaction-condition threshold-type average [attempts] threshold-value raising-value falling-value action-type action-value The default value for attempts is 5. trapOnly—Send an SNMP logging trap when the specified violation type occurs for the monitored element. A triggered target operation must finish its life before it can be triggered again. page 8 Configuring an IP SLAs Reaction Configuration: Example In the following example. For SNMP logging traps to be sent. as defined in the trapOnly and triggerOnly options above. use the xofy [x-value y-value] syntax: ip sla reaction-configuration operation-number react reaction-condition threshold-type xofy x-value y-value threshold-value raising-value falling-value action-type action-value The default x-value and y-value is 5 (xofy 5 5).

IP SLAs—Proactive Threshold Monitoring of IP SLAs Operations Examples of Proactive Threshold Monitoring Using IP SLA Router(config)# ip sla reaction-configuration 10 react mos threshold-type immediate threshold-value 490 250 action-type trapOnly The following example shows the default settings for the ip sla reaction-configuration command when none of the optional syntax is used: Router# show ip sla reaction-configuration 1 Entry number: 1 Reaction Configuration not configured Router# configure terminal Enter configuration commands. one per line. multiple monitored elements (indicated by the Reaction: value) are configured for a single IP SLAs operation: Router# show ip sla reaction-configuration Entry Number: 1 Reaction: RTT Threshold type: Never Rising (milliseconds): 5000 Falling (milliseconds): 3000 Threshold Count: 5 Threshold Count2: 5 Action Type: None Reaction: jitterDSAvg Threshold type: average Rising (milliseconds): 5 Falling (milliseconds): 3 Threshold Count: 5 Threshold Count2: 5 Action Type: triggerOnly Reaction: jitterDSAvg Threshold type: immediate Rising (milliseconds): 5 Falling (milliseconds): 3 Threshold Count: 5 Threshold Count2: 5 Action Type: trapOnly Reaction: PacketLossSD Threshold type: immediate Rising (milliseconds): 5 7 . Router(config)# ip sla reaction-configuration 1 Router(config)# do show ip sla reaction-configuration 1 Entry number: 1 Reaction: rtt Threshold Type: Never Rising (milliseconds): 5000 Falling (milliseconds): 3000 Threshold Count: 5 Threshold Count2: 5 Action Type: None Verifying an IP SLAs Reaction Configuraiton: Example In the following example. End with CNTL/Z.

165.202. or the number-of-probes value for average threshold-type. Threshold type The configured theshold type. The lower-threshold value. as configured by the threshold-value upper-threshold lower-threshold syntax in the ip sla reaction-configuration command. Corresponds to the react { connectionLoss | jitterAvg | jitterDSAvg | jitterSDAvg | mos | PacketLossDS | PacketLossSD | rtt | timeout | verifyError } syntax in the ip sla reaction-configuration command. as configured by the action-type { none | trapOnly | triggerOnly | trapAndTrigger } syntax in the ip sla reaction-configuration command. Corresponds to the threshold-type { never | immediate | consecutive | xofy | average } syntax in the ip sla reaction-configuration command. The x-value in the xofy threshold-type. CISCO-SYSLOG-MIB traps will be sent to the remote host at 209.IP SLAs—Proactive Threshold Monitoring of IP SLAs Operations Examples of Proactive Threshold Monitoring Using IP SLA Threshold Falling (milliseconds): 3 Threshold Count: 5 Threshold Count2: 5 Action Type: trapOnly Table 1 describes the significant fields shown in this output. The y-value in the xofy threshold-type.200. Rising (milliseconds) The upper-threshold value.225 3000 codec g711alaw Router(config-ip-sla-jitter)# default frequency Router(config-ip-sla-jitter)# exit Router(config)# Router(config)# threshold-value Router(config)# threshold-value ip sla schedule 1 start now life forever ip sla reaction-configuration 1 react rtt threshold-type immediate 3000 2000 action-type trapOnly ip sla reaction-configuration 1 react MOS threshold-type consecutive 4 390 220 action-type trapOnly 8 .129 if the threshold values for round-trip-time (rtt) or VoIP mean opion score (MOS) are violated: Router(config)# ip sla 1 Router(config-ip-sla)# udp-jitter 209.165. Threshold Falling (milliseconds) Threshold Count Threshold Count2 Action Type Triggering SNMP Notifications: Example In the following example. The reaction to be performed when the violation conditions are met. Table 1 show ip sla reaction-configuration Field Descriptions Field Reaction Description The configured monitored element for IP SLAs reactions. as configured by the threshold-value upper-threshold lower-threshold syntax in the ip sla reaction-configuration command.

4.71 = SAATHRESHOLD clogHistoryEntry. see the Cisco IOS IP SLAs Features Roadmap.6.5. the IP SLAs Threshold violations are generated as level 6 (informational) in the Cisco IOS system logging process: 3d18h:%RTT-6-SAATHRESHOLD:RTR(11):Threshold exceeded for MOS but are sent as level 7 (info) notifications from the CISCO-SYSLOG-MIB: 3d18h:SNMP:V2 Trap. erridx 0 sysUpTime.71 = RTT clogHistoryEntry.0.71 = RTR(11):Threshold exceeded for MOS clogHistoryEntry. snmp-server enable traps syslog As shown in the following example. reqid 2.165.0 = 32613038 snmpTrapOID.IP SLAs—Proactive Threshold Monitoring of IP SLAs Operations Where to Go Next Router(config)# Router(config)# Router(config)# ! The following Router(config)# ip sla logging traps snmp-server host 209.3. errstat 0.2.0 = ciscoSyslogMIB.71 = 7 clogHistoryEntry. Additional References The following sections provide references related to configuring Cisco IOS IP SLAs. 9 .71 = 32613037 Where to Go Next For information about other types of IP SLAs operations and IP SLAs features.129 version 2c public syslog command is needed for the system to generate CISCO-SYSLOG-MIB traps.2.1 clogHistoryEntry.202.

including links to products. and support for existing standards has not been modified by features in this document.com users can log in from this page to access even more content. and feature sets.cisco. and tools. MIBs MIBs CISCO-RTTMON-MIB MIBs Link To locate and download MIBs for selected platforms. Cisco white paper Cisco IOS IP SLAs Command Reference Standards Standards Title No new or modified standards are supported by this — feature. Technical Assistance Description Technical Assistance Center (TAC) home page. solutions. technical tips.com/public/support/tac/home.cisco. Link http://www.IP SLAs—Proactive Threshold Monitoring of IP SLAs Operations Additional References Related Documents Related Topic Cisco IOS IP SLAs command-line interface enhancements Cisco IOS IP SLAs commands Document Title Cisco IOS IP Service Level Agreements Command Line Interface.shtml 10 . Registered Cisco.000 pages of searchable technical content. containing 30. Cisco IOS releases. technologies. use Cisco MIB Locator found at the following URL: http://www.com/go/mibs RFCs RFCs Title No specific RFCs are supported by the features in this — document.

Changing the Way We Work. and Welcome to the Human Network are trademarks. Use Cisco Feature Navigator to find information about platform support and software image support. Cisco IOS XE Release 2. Play. EtherSwitch. Cisco Eos. and Learn and Cisco Store are service marks. TransPath. Catalyst. MGX. Inc. CCSP. DCE.2(31)SB2.2(31)SB2. 12. Collaboration Without Limitation. The Fastest Way to Increase Your Internet Quotient.IP SLAs—Proactive Threshold Monitoring of IP SLAs Operations Feature Information for IP SLAs Proactive Threshold Monitoring Feature Information for IP SLAs Proactive Threshold Monitoring Table 2 lists the release history for this feature. Cisco. 12. iPhone. EtherFast. see the command reference documentation. Any use of actual IP addresses in illustrative content is unintentional and coincidental. CCENT. the Cisco Systems logo. 11 . Spectrum Expert. Cisco Press. command display output.1 Feature Information Cisco IOS IP SLAs proactive threshold monitoring capability allows you to configure an IP SLAs operation to react to certain measured network conditions. Networking Academy. PIX.1 12. HomeLink. Cisco Systems. Cisco StadiumVision. Aironet. Follow Me Browsing. and/or its affiliates in the United States and certain other countries. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release. GigaDrive. SenderBase. 12. CCIE. Live. Note Table 2 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. MediaTone. Cisco IOS XE Release 2. Cisco Systems Capital. go to http://www. Event Center. Any examples.2(33)SXH. AsyncOS. CCNP. © 2006-2008 Cisco Systems. 12.2(33)SRB1.com is not required. CCDP. Linksys. feature set. Cisco TelePresence. Internet Quotient.3(14)T. CCDE. iQ Expertise. Unless noted otherwise. IP SLAs VoIP Threshold Traps Cisco IOS IP SLAs VoIP proactive threshold monitoring capability allows you to configure an IP SLAs operation to react to certain measured network conditions. subsequent releases of that Cisco IOS software release train also support that feature. Cisco IOS. ProConnect.3(14)T. 12. Network Registrar. Cisco Lumin.2(33)SXH. the IronPort logo. iQuick Study. ScriptShare. PowerPanels. (0807R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. CCVP. and Access Registrar. All other trademarks mentioned in this document or Website are the property of their respective owners. WebEx. the Cisco logo. Networkers. CCIP. the iQ logo. IronPort. 12. MeetingPlace Chime Sound. Inc. To access Cisco Feature Navigator. Cisco Nexus. LightStream. For release information about a specific command. SMARTnet. the Cisco Certified Internetwork Expert logo. Cisco Unity. MeetingPlace. or platform.cisco. CCNA. and figures included in the document are shown for illustrative purposes only. All rights reserved. iQ Net Readiness Scorecard. Table 2 Feature Information for IP SLAs Proactive Threshold Monitoring Feature Name IP SLAs Reaction Threshold Releases 12. The use of the word partner does not imply a partnership relationship between Cisco and any other company. FormShare. StackWise. Fast Step. and the WebEx logo are registered trademarks of Cisco Systems. An account on Cisco.2(33)SRB1. IOS. PCNow. Not all commands may be available in your Cisco IOS software release.com/go/cfn. CCDA. Bringing the Meeting To You.

IP SLAs—Proactive Threshold Monitoring of IP SLAs Operations Feature Information for IP SLAs Proactive Threshold Monitoring 12 .

Sign up to vote on this title
UsefulNot useful