ip slas configuration guide 15.2t

7/31/2019 IP SLAs Configuration Guide 15.2T

1/407

IP SLAs Configuration Guide, Cisco IOSRelease 15.2MT

Americas HeadquartersCisco Systems, Inc.170 West Tasman Drive

San Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883


2/407

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 SHIPPEDWITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITEDWARRANTY, 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 UCBs public domain versionof 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 ALLFAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADEPRACTICE.

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 ORITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:www.cisco.com/go/trademarks . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship

between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output,network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative contentis unintentional and coincidental.

2012 Cisco Systems, Inc. All rights reserved.
http://www.cisco.com/go/trademarks


3/407

C O N T E N T S

IP SLAs Overview 1

Finding Feature Information 1

Information About IP SLAs 1

IP SLAs Technology Overvi ew 2

Service Level Agreements 3

Benefits of IP SLAs 3

Network Performance Meas urement Using IP SLAs 4

IP SLAs Operation Types 5

IP SLAs Responder and IP S LAs Control Protocol 5

Response Time Computation for IP SLAs 6

IP SLAs Operation Scheduli ng 6

IP SLAs Operation Threshol d Monitoring 7

MPLS VPN Awareness 7

History Statistics 7

Additional References 8

Configuring Auto IP SLAs in IP S LAs Engine 3.0 11


Prerequisites for Auto IP SLAs i n IP SLAs Engine 3.0 11

Restrictions for Auto IP SLAs in IP SLAs Engine 3.0 12

General Restrictions 12

UDP Jitter Operations Restri ctions 12

UDP Jitter Codec Operations Restrictions 12

Proactive Threshold Measuri ng Restrictions 13

Auto-Measure Group Restric tions 13

Information About Auto IP SLAs in IP SLAs Engine 3.0 13

Auto IP SLAs for Analyzing IP SLAs Operations 13

QoS Integration for Auto IP SLAs 14

Automatic Registration of Destinations for Auto IP SLAs Operations 14

How to Configure Auto IP SLAs in IP SLAs Engine 3.0 14

IP SLAs Configuration Guide, Cisco IOS Release 15.2MT iii


4/407

Configuring Automatic Registration of Responder on the Destination Device 15

Configuring an Endpoint List on the Source Device 15

Using Automatic Registration to Configure an Endpoint List 16

Manually Configuring an Endpoint List 18Configuring a Scheduler on t he Source Device 19

Configuring a Template on t he Source Device 21

Configuring an ICMP Ec ho Operation 21

Configuring a Templ ate for a Basic ICMP Echo Operation 21

What to Do Next 23

Configuring an ICMP Echo Operation Template with Additional Characteristics 23

What to Do Next 27

Configuring an ICMP Jit ter Operation 27

Configuring a Templ ate for a Basic ICMP Jitter Operation 27

What to Do Next 29

Configuring an ICMP Jitter Operation Template with Additional Characteristics 29

What to Do Next 33

Configuring a TCP Conn ect Operation 33

Configuring a Templ ate for a Basic TCP Connect Operation 33

What to Do Next 34

Configuring a TCP C onnect Operation Template with Additional Characteristics 35

What to Do Next 38Configuring a UDP Echo Operation 38

Configuring a Templ ate for a Basic UDP Echo Operation 38

What to Do Next 40

Configuring a UDP E cho Operation Template with Additional Characteristics 40

What to Do Next 44

Configuring a UDP Jitter Operation on the Source Device 44

Configuring a Templ ate for a Basic UDP Jitter Operation 45

What to Do Next 46

Configuring a Templ ate for a Basic VoIP SLAs UDP Operation 46

What to Do Next 48

Configuring a UDP Ji tter Operation Template with or without Codec with

Additional Characteri stics 48

What to Do Next 53

Adding Proactive Threshold Monitoring to a Template on the Source Device 54

Contents

IP SLAs Configuration Guide, Cisco IOS Release 15.2MTiv


5/407

Configuring an Auto-Measure Group on the Source Device 56

Configuration Examples for Auto IP SLAs in IP SLAs Engine 3.0 58

Example IP SLAs Auto-Measure Group 58

Example Configuring Auto IP SLAs Using SNMP 58Example MIB Strings for Auto IP SLAs Template 58

Example MIB Strings for Auto IP SLAs Endpoint List 59

Example MIB Strings for Auto IP SLAs Scheduler 60

Example MIB Strings for an Auto-Measure Group 61

Example Using SNMP C ommands to Create an Auto IP SLAs Operation 62


Feature Information for Auto IP SLAs in IP SLAs Engine 3.0 65

Configuring IP SLAs Video Oper ations 69


Prerequisites for IP SLAs Video Operations 69

Restrictions for IP SLAs Video Operations 69

Information About IP SLAs Vid eo Operations 70

How to Configure IP SLAs Vide o Operations 71

Configuring an IP SLAs Res ponder 71

Configuring an IP SLAs Vid eo Profile 72

Configuring Proactive Thres hold Monitoring 75

Scheduling IP SLAs Operati ons 78Displaying Statistics for IP S LAs 81

Troubleshooting Tips 82

Configuration Examples for IP S LAs Video Operations 82

Example: Basic IP SLAs Vid eo Profile for Cisco TelePresence 1080P Traffic 82

Example: Basic IP SLAs Vid eo Profile for IP Television Traffic 82

Example: Basic IP SLAs Vid eo Profile for IP Surveillance Camera Traffic 83

Example: SNMP Commands for Configuring a Video Operation 83


Feature Information for IP SLAs Video Operations 85

Configuring IP SLAs UDP Jitter Operations 87


Prerequisites 87

Information About IP SLAs UD P Jitter Operations 88

IP SLAs UDP Jitter Operatio n 88

Contents

IP SLAs Configuration Guide, Cisco IOS Release 15.2MT v


6/407

How to Configure IP SLAs UDP Jitter Operations 89

Configuring the IP SLAs Responder on the Destination Device 89

Configuring and Scheduling a UDP Jitter Operation on the Source Device 90

Configuring and Scheduling a Basic UDP Jitter Operation on the Source Device 90Troubleshooting Tips 92

What to Do Next 92

Configuring and Schedul ing a UDP Jitter Operation with Additional Characteristics 92


What to Do Next 98

Configuration Examples for IP S LAs UDP Jitter Operations 98

Example Configuring a UDP Jitter Operation 98


Feature Information for IP SLAs UDP Jitter Operations 100

Configuring IP SLAs UDP Jitter Operations for VoIP 103


Restrictions for IP SLAs UDP Ji tter Operations for VoIP 103

Information About IP SLAs UD P Jitter Operations for VoIP 104

The Calculated Planning Imp airment Factor (ICPIF) 104

Mean Opinion Scores (MOS ) 105

Voice Performance Monitori ng Using IP SLAs 106

Codec Simulation Within IP SLAs 106The IP SLAs ICPIF Value 107

The IP SLAs MOS Value 109

How to Configure IP SLAs UDP Jitter Operations for VoIP 109

Configuring and Scheduling an IP SLAs VoIP UDP Jitter Operation 110


What to Do Next 115

Configuration Examples for IP S LAs UDP Jitter Operations for VoIP 115

Example IP SLAs VoIP UD P Operation Configuration 115

Example IP SLAs VoIP UD P Operation Statistics Output 116


Feature Information for IP SLAs UDP Jitter Operations for VoIP 118

Glossary 119

Configuring IP SLAs LSP Health Monitor Operations 121


Contents

IP SLAs Configuration Guide, Cisco IOS Release 15.2MTvi


7/407

Prerequisites for LSP Health Monitor Operations 121

Restrictions for LSP Health Monitor Operations 122

Information About LSP Health Monitor Operations 122

Benefits of the LSP Health Monitor 122How the LSP Health Monito r Works 123

Discovery of Neighboring P E Devices 124

LSP Discovery 125

LSP Discovery Groups 126

IP SLAs LSP Ping and LSP Traceroute 128

Proactive Threshold Monitor ing for the LSP Health Monitor 128

Multioperation Scheduling f or an LSP Health Monitor 129

How to Configure LSP Health M onitor Operations 130

Configuring an LSP Health Monitor Operation 130

Configuring an LSP Heal th Monitor Operation without LSP Discovery on a PE Device 130

Configuring the LSP Hea lth Monitor Operation with LSP Discovery on a PE Device 135

Scheduling LSP Health Mon itor Operations 140


What to Do Next 141

Manually Configuring and S cheduling an IP SLAs LSP Ping or LSP Traceroute Operation 142


What to Do Next 145Verifying and Troubleshooti ng LSP Health Monitor Operations 146

Configuration Examples for LSP Health Monitors 148

Example Configuring and V erifying the LSP Health Monitor Without LSP Discovery 148

Example Configuring and V erifying the LSP Health Monitor with LSP Discovery 152

Example Manually Configur ing an IP SLAs LSP Ping Operation 155


Feature Information for LSP He alth Monitor Operations 156

Configuring IP SLAs for Metro-E thernet 159


Prerequisites for IP SLAs for M etro-Ethernet 159

Restrictions for IP SLAs for Me tro-Ethernet 159

Information About IP SLAs for Metro-Ethernet 160

IP SLAs Ethernet Operation Basics 160

How to Configure IP SLAs for Metro-Ethernet 160

Contents

IP SLAs Configuration Guide, Cisco IOS Release 15.2MT vii


8/407


9/407


What to Do Next 191

Configuration Examples for IP SLAs RTP-Based VoIP Operations 191

Example Configuring an IP SLAs RTP-Based VoIP Operation 191Additional References 191

Feature Information for IP SLAs RTP-Based VoIP Operations 192

Configuring VoIP Gatekeeper Re gistration Delay Operations 195


Restrictions for IP SLAs VoIP G atekeeper Registration Delay Operations 195

Information About IP SLAs VoI P Gatekeeper Registration Delay Operations 196

H.323 Gatekeepers and Gate ways 196

Gateway-to-Gatekeeper Reg istration Delay Time Monitoring 196

How to Configure IP SLAs VoI P Gatekeeper Registration Delay Operations 196

Configuring the VoIP H.323 Gateway 197


Configuring and Scheduling a VoIP Gatekeeper Registration Delay Operation 200


What to Do Next 204

Configuration Examples for IP S LAs VoIP Gatekeeper Registration Delay Operations 204

Example Configuring the IP SLAs VoIP gatekeeper registration delay operation 205

Additional References 205Feature Information for the IP S LAs VoIP Gatekeeper Registration Delay Operation 206

Glossary 207

Configuring VoIP Call Setup Mon itoring 209


Prerequisites for VoIP Call Setu p Monitoring 209

Information About VoIP Call Se tup Monitoring 210

IP SLAs VoIP Call Setup M onitoring Using H.323 or SIP 210

How to Configure VoIP Call Set up Monitoring 210

Configuring the Source Gate way 211

Configuring a VoIP Call Set up Montioring Operation 213

Scheduling IP SLAs Operati ons 216

Enabling the IP SLAs VoIP Responder Application on the Destination Gateway 218


What to Do Next 219

Contents

IP SLAs Configuration Guide, Cisco IOS Release 15.2MT ix


10/407

Configuration Examples for VoIP Call Setup Monitoring 219

Example VoIP Call Setup Configuration on the Source Gateway 220

Example VoIP Responder Application on Destination Gateway 220

Additional References 220Feature Information for VoIP Ca ll Setup Monitoring 221

Configuring IP SLAs UDP Echo Operations 223


Restrictions for IP SLAs UDP E cho Operations 223

Information About IP SLAs UD P Echo Operations 223

UDP Echo Operation 224

How to Configure IP SLAs UDP Echo Operations 224

Configuring the IP SLAs Re sponder on the Destination Device 224

Configuring a UDP Echo Op eration on the Source Device 226

Configuring a Basic UDP Echo Operation on the Source Device 226

Configuring a UDP Echo Operation with Optional Parameters on the Source Device 227



What to Do Next 234

Configuration Examples for IP S LAs UDP Echo Operations 234

Example Configuring a UDP Echo Operation 234

Additional References 234Feature Information for the IP S LAs UDP Echo Operation 235

Configuring IP SLAs HTTP Oper ations 237


Restrictions for IP SLAs HTTP Operations 237

Information About IP SLAs HT TP Operations 237

HTTP Operation 238

How to Configure IP SLAs HTT P Operations 238

Configuring an HTTP GET Operation on the Source Device 238

Configuring a Basic HTT P GET Operation on the Source Device 238

Configuring an HTTP G ET Operation with Optional Parameters on the Source Device 240

Configuring an HTTP RAW Operation on the Source Device 243



What to Do Next 247

Contents

IP SLAs Configuration Guide, Cisco IOS Release 15.2MTx


11/407

Configuration Examples for IP SLAs HTTP Operations 247

Example Configuring an HTTP GET Operation 248

Example Configuring an HTTP RAW Operation 248

Example Configuring an HTTP RAW Operation Through a Proxy Server 248Example Configuring an HT TP RAW Operation with Authentication 249


Feature Information for IP SLAs HTTP Operations 250

Configuring IP SLAs TCP Conne ct Operations 253


Information About the IP SLAs TCP Connect Operation 253

TCP Connect Operation 253

How to Configure the IP SLAs TCP Connect Operation 254

Configuring the IP SLAs Re sponder on the Destination Device 254

Configuring and Scheduling a TCP Connect Operation on the Source Device 256

Prerequisites 256

Configuring and Schedul ing a Basic TCP Connect Operation on the Source Device 256


What to Do Next 258

Configuring and Schedul ing a TCP Connect Operation with Optional Parameters on the

Source Device 258

Troubleshooting Tips 263What to Do Next 264

Configuration Examples for IP S LAs TCP Connect Operations 264

Example Configuring a TCP Connect Operation 264


Feature Information for the IP S LAs TCP Connect Operation 266

Configuring IP SLAs ICMP Echo Operations 267


Restrictions for IP SLAs ICMP Echo Operations 267

Information About IP SLAs ICM P Echo Operations 267

ICMP Echo Operation 268

How to Configure IP SLAs ICM P Echo Operations 268

Configuring an ICMP Echo Operation 268

Configuring a Basic ICM P Echo Operation on the Source Device 268

Configuring an ICMP Ec ho Operation with Optional Parameters 270

Contents

IP SLAs Configuration Guide, Cisco IOS Release 15.2MT xi


12/407

Scheduling IP SLAs Operations 274


What to Do Next 276

Configuration Examples for IP SLAs ICMP Echo Operations 276Example Configuring an IC MP Echo Operation 276


Feature Information for IP SLAs ICMP Echo Operations 278

Configuring IP SLAs ICMP Path Echo Operations 279


Restrictions for IP SLAs ICMP Path Echo Operations 279

Information About IP SLAs ICM P Path Echo Operations 279

ICMP Path Echo Operation 280

How to Configure IP SLAs ICM P Path Echo Operations 280

Configuring an ICMP Path E cho Operation on the Source Device 280

Configuring a Basic ICM P Path Echo Operation on the Source Device 281

Configuring an ICMP Pa th Echo Operation with Optional Parameters on the Source

Device 282



What to Do Next 289

Configuration Examples for IP S LAs ICMP Path Echo Operations 289Example Configuring an IC MP Path Echo Operation 289


Feature Information for IP SLAs ICMP Path Echo Operations 291

Configuring IP SLAs ICMP Path Jitter Operations 293


Prerequisites for ICMP Path Jitt er Operations 293

Restrictions for ICMP Path Jitte r Operations 294

Information About IP SLAs ICM P Path Jitter Operations 294

ICMP Path Jitter Operation 294

How to Configure the IP SLAs I CMP Path Jitter Operation 295

Configuring the IP SLAs Re sponder on a Destination Device 295

Configuring an ICMP Path J itter Operation on the Source Device 296

Configuring a Basic ICM P Path Jitter Operation 296

Configuring an ICMP Pa th Jitter Operation with Additional Parameters 298

Contents

IP SLAs Configuration Guide, Cisco IOS Release 15.2MTxii


13/407

Scheduling IP SLAs Operations 300


What to Do Next 302

Configuration Examples for IP SLAs ICMP Path Jitter Operations 302Example Configuring a Path Jitter Operation 302


Feature Information for IP SLAs ICMP Path Jitter Operations 304

Configuring IP SLAs FTP Operat ions 307


Restrictions for IP SLAs FTP O perations 307

Information About IP SLAs FTP Operations 307

FTP Operation 308

How to Configure IP SLAs FTP Operations 308

Configuring an FTP Operati on on a Source Device 309

Configuring a Basic FTP Operation on the Source Device 309

Configuring an FTP Ope ration with Optional Parameters on the Source Device 310



What to Do Next 315

Configuration Examples for IP S LAs FTP Operations 315

Example Configuring an FT P Operation 315Additional References 316

Feature Information for IP SLAs FTP Operations 317

Configuring IP SLAs DNS Opera tions 319


Information About IP SLAs DN S Operations 319

DNS Operation 319

How to Configure IP SLAs DNS Operations 320

Configuring an IP SLAs DN S Operation on the Source Device 320

Configuring a Basic DNS Operation on the Source Device 320

Configuring a DNS Oper ation with Optional Parameters on the Source Device 322



What to Do Next 327

Configuration Examples for IP S LAs DNS Operations 327

Contents

IP SLAs Configuration Guide, Cisco IOS Release 15.2MT xiii


14/407

Example Configuring a DNS Operation 327

DNS Operation in IPv6 Network 328


Feature Information for IP SLAs DNS Operations 329Configuring IP SLAs DHCP Oper ations 331


Information About IP SLAs DH CP Operations 331

DHCP Operation 331

IP SLAs DHCP Relay Agent Options 332

How to Configure IP SLAs DH CP Operations 332

Configuring a DHCP Operat ion on the Source Device 332

Configuring a Basic DH CP Operation 332

Configuring a DHCP Op eration with Optional Parameters 333



What to Do Next 339

Configuration Examples for IP S LAs DHCP Operations 339

Example Configuration for a n IP SLAs DHCP Operation 339


Feature Information for IP SLAs DHCP Operations 340

Configuring IP SLAs DLSw+ Ope rations 343Finding Feature Information 343

Prerequisites 343

Information About IP SLAs DL Sw+ Operations 343

DLSw+ Operation 343

How to Configure IP SLAs DLS w+ Operations 344

Configuring IP SLAs DLSw + Operations 344

Configuring a Basic DLS w+ Operation on the Source Device 344

Configuring an IP SLAs DLSw+ Operation with Optional Parameters on the Source

Device 345



What to Do Next 351

Configuration Examples for IP S LAs DLSw+ Operations 351

Example IP SLAs DLSw+ O peration Configuration 351

Contents

IP SLAs Configuration Guide, Cisco IOS Release 15.2MTxiv


15/407


Feature Information for Cisco IOS IP SLAs DLSw+ Operations 353

Configuring an IP SLAs Multioperation Scheduler 355

Finding Feature Information 355Prerequisites for an IP SLAs Mu ltioperation Scheduler 355

Information About an IP SLAs Multioperation Scheduler 355

IP SLAs Multioperations Sc heduler 356

Default Behavior of IP S LAs Multiple Operations Scheduling 357

IP SLAs Multiple Operat ions Scheduling with Scheduling Period Less Than Frequency 358

Multiple Operations Sche duling When the Number of IP SLAs Operations Are Greater

Than the Schedule Period 359

IP SLAs Multiple Operat ions Scheduling with Scheduling Period Greater Than Frequency 360

IP SLAs Random Scheduler 362

How to Configure an IP SLAs M ultioperation Scheduler 362

Scheduling Multiple IP SLA s Operations 363

Enabling the IP SLAs Rando m Scheduler 364

Verifying IP SLAs Multiple Operations Scheduling 365

Configuration Examples for an I P SLAs Multioperation Scheduler 367

Example Scheduling Multipl e IP SLAs Operations 367

Example Enabling the IP SL As Random Scheduler 368

Additional References 368Feature Information for a IP SL As Multioperation Scheduler 369

Configuring Proactive Threshold Monitoring for IP SLAs Operations 371


Information About Proactive Th reshold Monitoring 371

IP SLAs Reaction Configura tion 371

Supported Reactions by I P SLAs Operation 372

IP SLAs Threshold Monitori ng and Notifications 375

RTT Reactions for Jitter Operations 377

How to Configure Proactive Thr eshold Monitoring 377

Configuring Proactive Thres hold Monitoring 377

Configuration Examples for Pro active Threshold Monitoring 380

Example Configuring an IP SLAs Reaction Configuration 380

Example Verifying an IP SL As Reaction Configuration 380

Example Triggering SNMP Notifications 381

Contents

IP SLAs Configuration Guide, Cisco IOS Release 15.2MT xv


16/407


Feature Information for IP SLAs Proactive Threshold Monitoring 383

IP SLAs TWAMP Responder 385

Finding Feature Information 385Prerequisites for IP SLAs TWAMP Responder 385

Restrictions for IP SLAs TWAMP Responder 385

Information About IP SLAs TWAMP Responder 386

TWAMP 386

IP SLAs TWAMP Responder v1.0 386

How to Configure an IP SLAs TWAMP Responder 387

Configuring the TWAMP Server 387

Configuring the Session-Reflector 389

Configuration Examples for IP SLAs TWAMP Responder 390

IP SLAs TWAMP Responder v1.0 Example 390


Feature Information for IP SLAs TWAMP Responder 391

Contents

IP SLAs Configuration Guide, Cisco IOS Release 15.2MTxvi


17/407

IP SLAsOverview

This module descr ibes IP Service Level Agreeme nts (SLAs). IP SLAs allows Cisco customers to analyzeIP service levels for IP applications and services, to increase productivity, to lower operational costs, andto reduce the frequency of network outages. IP SLAs uses active traffic monitoring--the generation of traffic in a continuous, reliable, and predictable manner--for measuring network performance. Using IPSLAs, service provider customers can measure and provide service level agreements, and enterprisecustomers can verify service levels, verify outsourced service level agreemen ts, and understand network performance. IP SLAs can perform network assessments, verify quality of service (QoS), ease thedeployment of new services, and assist administrators with network troubleshooting. IP SLAs can beaccessed using the Cisco software commands or Simple Network Management Protocol (SNMP) throughthe Cisco Round-Trip Time Monitor (RTTMON) and syslog Management Information Bases (MIBs).

Finding Feature Information, page 1 Information About IP SLAs, page 1 Additional References, page 8

Finding Feature InformationYour software re lease may not support all the features documented in this module. For the latest featureinformation and caveats, see the release notes for your platform and software release. To find informationabout the features documented in this module, and to see a list of the releases in which each feature issupported, see the Feature Information Table at the end of this document.

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

Information About IP SLAs IP SLAs Technology Overview, page 2 Service Level Agreements, page 3 Benefits of IP SLAs, page 3 Network Performance Measurement Using IP SLAs, page 4 IP SLAs Operation Types, page 5 IP SLAs Responder and IP SLAs Control Protocol, page 5 Response Time Computation for IP SLAs, page 6 IP SLAs Operation Scheduling, page 6 IP SLAs Operation Threshold Monitoring, page 7

IP SLAs Configuration Guide, Cisco IOS Release 15.2MT 1
http://www.cisco.com/go/cfnhttp://www.cisco.com/go/cfn


18/407

MPLS VPN Awareness, page 7 History Statistics, page 7

IP SLAs Technology OverviewCisco IP SLAs uses active traffic monitoring--the generation of traffic in a continuous, reliable, andpredictable manner--for measuring network performance. IP SLAs sends data across the network tomeasure performance between multiple network locations or across multiple network paths. It simulatesnetwork data and IP services, and collects network performance information in real time. The informationcollected includes data about response time, one-way latency, jitter (interpacket delay variance), packetloss, voice quality scoring, network resource availability, application performance, and server responsetime. IP SLAs performs active monitoring by generating and analyzing traffic to measure performanceeither between Cisco devices or from a Cisco device to a remote IP device such as a network applicationserver. M easurement statistics pro vided by the various IP SLAs operations can be used for troubleshooting,for problem analysis, and for designing network topologies.

Using IP SLAs, service provider customers can measure and provide service level agreements, andenterprise customers can verify service levels, verify outsourced service level agreements, and understandnetwork performance for new or existing IP services and applications. IP SLAs uses unique service levelassurance metrics and methodology to provide highly accurate, precise service level assurancemeasurements.

Depending on the specific IP SLAs operation, statistics of delay, packet loss, jitter, packet sequence,connectivity, path, server response time, and download time can be monitored within the Cisco device andstored in both CLI and SNMP MIBs. The packets have configurable IP and application layer options suchas a source and destination IP address, User Datagram Protocol (UDP)/TCP port numbers, a type of service(ToS) byte (including Differentiated Services Code Point [DSCP] and IP Prefix bits), a Virtual PrivateNetwork (VPN) routing/forwarding instance (VRF), and a URL web address.

Being Layer-2 transport independent, IP SLAs can be configured end-to-end over disparate networks tobest reflect the metrics that an end-user is likely to experience. Performance metrics collected by IP SLAsoperations 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 IP SLAs is accessible using SNMP, it also can be used by performance monitoring applicationslike CiscoWorks Internetwork Performance Monitor (IPM) and other third-party Cisco partner performance

management products. For details about network management products that use IP SLAs, see http:// www.cisco.com/go/ipsla .

SNMP notifications based on the data gathered by an IP SLAs operation allow the router to receive alertswhen performance drops below a specified level and when problems are corrected. IP SLAs uses the CiscoRTTMON MIB for interaction between external Network Management System (NMS) applications and theIP SLAs operations running on the Cisco devices. For a complete description of the object variablesreferenced by the IP SLAs feature, refer to the text of the CISCO-RTTMON-MIB.my file, available fromthe Cisco MIB website .

IP SLAs Technology OverviewInformation About IP SLAs

IP SLAs Configuration Guide, Cisco IOS Release 15.2MT2
http://www.cisco.com/go/ipslahttp://www.cisco.com/go/ipslahttp://www.cisco.com/go/ipsla


19/407

Service Level AgreementsInternet commerce has grown significantly in the past few years as the technology has advanced to providefaster, more reliable access to the Internet. 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. Internet serviceproviders (ISPs) and even internal IT departments now offer a defined level of service--a service levelagreement--to provide their customers with a degree of predictability.

The latest performance requirements for business-critical applications, voice over IP (VoIP) networks,audio and visual conferencing, and VPNs are creating internal pressures on converged IP networks tobecome optimized for performance levels. Network administrators are increasingly required to supportservice level agreements that support application solutions. The figure below shows how IP SLAs has takenthe traditional concept of Layer 2 service level agreements and applied a broader scope to support end-to-end performance measurement, including support of applications.

Figure 1 Scope of Traditional Service Level Agreement Versus IP SLAs

TraditionalLayer 2 SLA

Application-awareIP SLA

Customersite 1

Customersite 2

ATMFrameRelay

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 theother allows a broader reach and more accurate representation of the end-user experience.

Sophistication--Statistics such as delay, jitter, packet sequence, Layer 3 connectivity, and path anddownload time that are broken down into bidirectional and round-trip numbers provide more data than

just the bandwidth of a Layer 2 link. Ease of deployment--Leveraging the existing Cisco devices in a large network makes IP SLAs easier

and cheaper to implement than the physical probes often required with traditional service levelagreements.

Application-aware monitoring--IP SLAs can simulate and measure performance statistics generated byapplications running over Layer 3 through Layer 7. Traditional service level agreements can onlymeasure Layer 2 performance.

Pervasiveness--IP SLAs support exists in Cisco networking devices ranging from low-end to high-endrouters and switches. This wide range of deployment gives IP SLAs more flexibility over traditionalservice level agreements.

When you know the performance expectations for different levels of traffic from the core of your network to the edge of your network, you can confidently build an end-to-end application-aware service levelagreement.

Benefits of IP SLAs IP SLAs monitoring

Service Level AgreementsInformation About IP SLAs



20/407

Provides service level agreement monitoring, measurement, and verification. Network performance monitoring

Measures the jitter, latency, or packet loss in the network. Provides continuous, reliable, and predictable measurements.

IP service network health assessment Verifies that the existing QoS is sufficient for new IP services.

Edge-to-edge network availability monitoring

Provides proactive verification and connectivity testing of network resources (for example,indicates the network availability of a Network File System (NFS) server used to store businesscritical data from a remote site).

Troubleshooting of network operation

Provides consistent, reliable measurement that immediately identifies problems and savestroubleshooting time.

Voice over IP (VoIP) performance monitoring Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) performance monitoring and

network verification

Network Performance Measurement Using IP SLAsUsing IP SLAs, a network engineer can monitor the performance between any area in the network: core,distribution, and edge. Monitoring can be done anytime, anywhere, without deploying a physical probe.

IP SLAs uses generated traffic to measure network performance between two networking devices such asrouters. The figure below shows how IP SLAs starts when the IP SLAs device sends a generated packet tothe destination device. After the destination device receives the packet, and depending on the type of IPSLAs operation, the device will respond with time-stamp information for the source to make the calculationon performance metrics. An IP SLAs operation performs a network measurement from the source device toa destination in the network using a specific protocol such as UDP.

Figure 2 IP SLAs Operations

1 2 1 3 8 1

IP SLA sourceIP SLA responder

IP SLA

Any IP device

SNMP

Performancemanagement

application

IP network IP SLA

IP SLA measurementand IP SLA responder to

IP SLA Responder


IP SLA Responder


IP SLA Responder

To implement IP SLAs network performance measurement you need to perform these tasks:

Network Performance Measurement Using IP SLAsInformation About IP SLAs



21/407

1 Enable the IP SLAs Responder, if appropriate.2 Configure the required IP SLAs operation type.3 Configure any options available for the specified IP SLAs operation type.4 Configure threshold conditions, if required.5 Schedule the operation to run, then let the operation run for a period of time to gather statistics.6 Display and interpret the results of the operation using Cisco software commands or an NMS system

with SNMP.

Conceptual information about the IP SLAs Responder and IP SLAs control protocol, the various IP SLAsoperation types, thresholding options, and scheduling options are contained in this document.

IP SLAs Operation TypesThe various types of 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

IP SLAs Responder and IP SLAs Control ProtocolThe IP SLAs Responder is a component embedded in the destination Cisco routing device that allows thesystem to anticipate and respond to IP SLAs request packets. The IP SLAs Responder provides anenormous advantage with accurate measurements without the need for dedicated probes and additionalstatistics not available via standard ICMP-based measurements. The patented IP SLAs Control Protocol isused by the IP SLAs Responder providing a mechanism through which the responder can be notified onwhich port it should listen and respond. Only a Cisco device can be a source for a destination IP SLAsResponder.

The figure "Cisco IOS XE IP SLAs Operations" in the "Network Performance Measurement Using CiscoIOS XE IP SLAs" section shows where the IP SLAs Responder fits in relation to the IP network. The IPSLAs Responder listens on a specific port for control protocol messages sent by an IP SLAs operation.Upon receipt of the control message, the responder will enable the specified UDP or TCP port for thespecified duration. During this time, the responder accepts the requests and responds to them. Theresponder disables the port after it responds to the IP SLAs packet, or when the specified time expires. Foradded security, MD5 authentication for control messages is available.

Enabling the IP SLAs Responder on the destination device is not required for all IP SLAs operations. Forexample, if services that are already provided by the destination router (such as Telnet or HTTP) are

IP SLAs Operation TypesInformation About IP SLAs



22/407

chosen, the IP SLAs Responder need not be enabled. For non-Cisco devices, the IP SLAs Respondercannot be configured and IP SLAs can send operational packets only to services native to those devices.

Response Time Computation for IP SLAsRouters may take tens of milliseconds to process incoming packets, due to other high-priority processes.This delay affects the response times because the reply to test packets might be sitting on queue whilewaiting to be processed. In this situation, the response times would not accurately represent true network delays. IP SLAs minimizes these processing delays on the source router as well as on the target router (if IPSLAs Responder is being used), in order to determine true round-trip times. IP SLAs test packets use timestamping to minimize the processing delays.

When enabled, the IP SLAs Responder allows the target device to take two time stamps both when thepacket arrives on the interface at interrupt level and again just as it is leaving, eliminating the processingtime. At times of high network activity, an ICMP ping test often shows a long and inaccurate responsetime, while an IP SLAs test shows an accurate response time due to the time stamping on the responder.

The figure below demonstrates how the responder works. Four time stamps are taken to make thecalculation for round-trip time. At the target router, 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 asrepresented by delta. This delta value is then subtracted from the overall round-trip time. Notice that thesame principle is applied by IP SLAs on the source router where the incoming time stamp 4 (TS4) is alsotaken at the interrupt level to allow for greater accuracy.

Figure 3 IP SLAs Responder Time Stamping

1

2 1 3 8 0

T1

Source router

RTT (Round-trip time) = T4 (Time stamp 4) - T1 (Time stamp 1) -

Target routerResponder

=T3-T2T4

T2T3

An additional benefit of the two time stamps at the target router is the ability to track one-way delay, jitter,and directional packet loss. Because much network behavior is asynchronous, it is critical to have thesestatistics. However, to capture one-way delay measurements the configuration of both the source router andtarget router with Network Time Protocol (NTP) is required. Both the source and target need to besynchronized to the same clock source. One-way jitter measurements do not require clock synchronization.

IP SLAs Operation SchedulingAfter an IP SLAs operation has been configured, you must schedule the operation to begin capturingstatistics and collecting error information. When scheduling an operation, it can start immediately or start ata certain month, day, and hour. There is a pending option to set the operation to start at a later time. Thepending option is also an internal state of the operation visible through SNMP. The pending state is alsoused when an operation is a reaction (threshold) operation waiting to be triggered. You can schedule asingle IP SLAs operation or a group of operations at one time.

Multioperations scheduling allows you to schedule multiple IP SLAs operations using a single Ciscosoftware command or the CISCO RTTMON-MIB. This feature allows you to control the amount of IPSLAs monitoring traffic by scheduling the operations to run at evenly distributed times. This distribution of IP SLAs operations helps minimize the CPU utilization and thereby enhances the scalability of thenetwork.

Response Time Computation for IP SLAsInformation About IP SLAs



23/407

For more details about the IP SLAs multioperations scheduling functionality, see the IP SLAs-Multioperation Scheduling of IP SLAs Operations module of the IP SLAs Configuration Guide .

IP SLAs Operation Threshold MonitoringTo support successful service level agreement monitoring or to proactively measure network performance,threshold functionality becomes essential. Consistent reliable measurements immediately identify issuesand can save troubleshooting time. To confidently roll out a service level agreement you need to havemechanisms that notify you immediately of any possible violation. IP SLAs can send SNMP traps that aretriggered 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, an IP SLAs threshold violation can trigger another IP SLAs operation for further analysis. Forexample, the frequency could be increased or an ICMP path echo or ICMP path jitter operation could beinitiated for troubleshooting.

Determining the type of threshold and the level to set can be complex, and it depends on the type of IPservice being used in the network. For more details on using thresholds with IP SLAs operations, see theIP SLAs-Proactive Threshold Monitoring of IP SLAs Operations module of the IP SLAs ConfigurationGuide .

MPLS VPN AwarenessThe IP SLAs MPLS VPN Awareness feature provides the capability to monitor IP service levels withinMultiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs). Using IP SLAs within MPLSVPNs allows service providers to plan, provision, and manage IP VPN services according to the servicelevel agreement for a customer. IP SLAs operations can be configured for a specific VPN by specifying aVPN routing and forwarding (VRF) name.

History StatisticsIP SLAs maintains the following three types of history statistics:

Aggregated statistics--By default, IP SLAs maintains two hours of aggregated statistics for eachoperation. Value from each operation cycle is aggregated with the previously available data within agiven hour. The Enhanced History feature in IP SLAs allows for the aggregation interval to be shorterthan an hour.

Operation snapshot history--IP SLAs maintains a snapshot of data for each operation instance thatmatches a configurable filter, such as all, over threshold, or failures. The entire set of data is availableand no aggregation takes place.

Distribution statistics--IP SLAs maintains a frequency distribution over configurable intervals. Eachtime IP SLAs starts an operation, a new history bucket is created until the number of history bucketsmatches the specified size or the lifetime of the operation expires. By default, the history for an IP

IP SLAs Operation Threshold MonitoringInformation About IP SLAs



24/407

SLAs operation is not collected. If history is collected, each bucket contains one or more historyentries from the operation. History buckets do not wrap.

Additional ReferencesRelated Documents

Related Topic Document Title

Cisco IOS commands Cisco IOS Master Commands List, All Releases

Cisco IOS IP SLAs commands Cisco IOS IP SLAs Command Reference

Standards

Standards Title

ITU-T G.711 u-law and G.711 a-law Pulse code modulation (PCM) of voice frequencies

ITU-T G.729A Reduced complexity 8 kbit/s CS-ACELP speechcodec

MIBs

MIBs MIBs Link

CISCO-RTTMON-MIB To locate and download MIBs for selectedplatforms, Cisco IOS releases, and feature sets, useCisco MIB Locator found at the following URL:

http://www.cisco.com/go/mibs

RFCs

RFCs Title

No new or modified RFCs are supported by thisfeature, and support for existing RFCs has not beenmodified by this feature.

--

IP SLAs OverviewAdditional References

http://www.cisco.com/go/mibshttp://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html


25/407

Technical Assistance

Description Link

The Cisco Support and Documentation websiteprovides online resources to downloaddocumentation, software, and tools. Use theseresources to install and configure the software andto troubleshoot and resolve technical issues withCisco products and technologies. Access to mosttools on the Cisco Support and Documentationwebsite requires a Cisco.com user ID andpassword.

http://www.cisco.com/cisco/web/support/ index.html

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks .Third-party trademarks mentioned are the property of their respective owners. The use of the word partnerdoes not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to beactual addresses and phone numbers. Any examples, command display output, network topology diagrams,and other figures included in the document are shown for illustrative purposes only. Any use of actual IPaddresses or phone numbers in illustrative content is unintentional and coincidental.

IP SLAs Overview

http://www.cisco.com/go/trademarkshttp://www.cisco.com/cisco/web/support/index.htmlhttp://www.cisco.com/cisco/web/support/index.html


26/407

History Statistics



27/407

Configuring Auto IP SLAs in IP SLAs Engine 3.

This document describes the auto IP Service Level Agreements (SLAs) function in IP SLAs Engine 3.0,including the following:

Auto-measure groups--Each template, endpoint li st, and scheduler can be configured once and thencombined to create auto-measure groups for multiple operations, including operations for proactivethreshold monitoring.

Automatic registration--Cisco devices can be configured to automatically register with the source,which enables the source to discover the destinations address for building an endpoint list. Quality of service (QoS) performance--Support for active measurement of QoS.

Finding Feature Information, page 11 Prerequisites for Auto IP SLAs in IP SLAs Engine 3.0, page 11 Restrictions for Auto IP SLAs in IP SLAs Engine 3.0, page 12 Information About Auto IP SLAs in IP SLAs Engine 3.0, page 13 How to Configure Auto IP SLAs in IP SLAs Engine 3.0, page 14 Configuration Examples for Auto IP SLAs in IP SLAs Engine 3.0, page 58 Additional References, page 64 Feature Information for Auto IP SLAs in IP SLAs Engine 3.0, page 65

Finding Feature InformationYour software release may not support all the features documented in this module. For the latest featureinformation and caveats, see the release notes for your platform and software release. To find informationabout the features documented in this module, and to see a list of the releases in which each feature issupported, see the Feature Information Table at the end of this document.

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

Prerequisites for Auto IP SLAs in IP SLAs Engine 3.0 Your IP network is operational and you can access the destination device. If you are using a Cisco IP SLAs Responder on the destination device for any auto IP SLAs operation,

the responder must be enabled before you configure the IP SLAs operation. The following operationsrequire that an IP SLAs responder be enabled on the destination device:

UDP Echo UPD Jitter

http://www.cisco.com/go/cfnhttp://www.cisco.com/go/cfn


28/407

VoIP UDP

Restrictions for Auto IP SLAs in IP SLAs Engine 3.0 General Restrictions, page 12 UDP Jitter Operations Restrictions, page 12 UDP Jitter Codec Operations Restrictions, page 12 Proactive Threshold Measuring Restrictions, page 13 Auto-Measure Group Restrictions, page 13

General Restrictions Auto IP SLAs is supported in IPv4 networks only. Only the following operation types are supported by auto IP SLAs in Cisco IP SLAs Engine 3.0:

Internet Control Message Protocol (ICMP) Echo ICMP Jitter TCP Connect Internet User Datagram Protocol (UDP) Echo UDP Jitter

If you do not configure and apply a template to an auto-measure group, the default type of operationfor the group is ICMP jitter.

UDP Jitter Operations Restrictions The responder should not configure a permanent port for the same sender. If the responder configures

the permanent port for the same sender, even if the packets are successfully sent (no timeout or packetloss issues), the jitter values will be zero.

Time synchronization is required between the source and the destination in order to provide accurateone-way delay (latency) measurements. To configure Network Time Protocol (NTP) on the source anddestination, perform the tasks in the Performing Basic System Management chapter of the Cisco IOS

Network Management Configuration Guide . Time synchronization is not required for one-way jitterand packet loss measurements. If the time is not synchronized between the source and destination,one-way jitter and packet loss data are returned but values of 0 are returned for the one-way delaymeasurements provided by the UDP jitter operation.

The IP SLAs UDP jitter operation does not support the IP SLAs History feature (statistics historybuckets) because of the large data volume involved with UDP jitter operations.

CISCO-RTTMON-MIB limits the hours of statistics kept for the UDP jitter operation to two hours.Configuring a larger value using the history hours-of-statistics command change does not increasethe value beyond two hours.

The CISCO-DATA-COLLECTION-MIB can be used to collect historical data for the operation. Forinformation about the CISCO-DATA-COLLECTION-MIB, see http://www.cisco.com/go/mibs .

UDP Jitter Codec Operations Restrictions Cisco IO S IP SLAs Engine 3.0 supports only the following speech codecs:

General RestrictionsRestrictions for Auto IP SLAs in IP SLAs Engine 3.0

http://www.cisco.com/go/mibs


29/407

G.711 a-law, 64 kbps PCM compression method G.711 mu-law, 64 kbps PCM compression method G.729A, 8 kbps CS-ACELP compression method

An IP SLAs UDP jitter codec operation for analyzing VoIP SLAs will fail if control protocol isdisabled.

The show auto template command for UDP jitter lists the values for the Number of statisticdistribution buckets kept and Statistic distribution interval (milliseconds), but these values do notapply to UDP jitter codec operations.

Proactive Threshold Measuring Restrictions RTT reaction s for jitter operations are triggered only at the end of the operation and use the latest

value for the return-trip time (LatestRTT). SNMP traps for RTT for jitter operations are based on the average value for the return-trip time

(RTTAvg) for the whole operation only and do not include return-trip time values for individualpackets sent during the operation. Only syslog messages are supported for RTTAvg threshold

violations. Only syslog messages are supported for RTT violations during Jitter operations. Only SNMP traps are supported for RTT violations during non-Jitter operations. Only syslog messages are supported for non-RTT violations other than timeout, connectionLoss, or

verifyError. Both SNMP traps and syslog messages are supported for timeout, connectionLoss, or verifyError

violations only.

Auto-Measure Group Restrictions Only one auto IP SLAs template can be specified for each auto-measure group. Each template can be

referenced by more than one group. If no template is specified for an auto-measure group, theoperation type for the group is ICMP jitter by default.

Only one auto IP SLAs endpoint list can be specified for each auto-measure group. Each endpoint listcan be referenced by more than one group.

Only one auto IP SLAs scheduler can be specified for each auto-measure group. Each scheduler can bereferenced by more than one group to create a multioperations schedule.

You cannot modify the configuration of an auto-measure group if the scheduler specified for the groupis configured with a start time other than the default (pending). To avoid conflicts when you configurean auto-measure group, issue the schedule command last.

Information About Auto IP SLAs in IP SLAs Engine 3.0 Auto IP SLAs for Analyzing IP SLAs Operations, page 13 QoS Integration for Auto IP SLAs, page 14 Automatic Registration of Destinations for Auto IP SLAs Operations, page 14

Auto IP SLAs for Analyzing IP SLAs OperationsAuto IP SLAs in Cisco IOS IP SLAs Engine 3.0 consists of the following components:

Proactive Threshold Measuring RestrictionsInformation About Auto IP SLAs in IP SLAs Engine 3.0



30/407

Endpoint list--A collection of destination endpoint addresses that can be manually configured orautomatically discovered.

Template--A set of parameters that define a single operation. You can combine any template with anyendpoint list and apply the combination across many groups.

Scheduler--Defines parameters for scheduling an operation including start time, frequency, life, age

out, and probe interval. The scheduler can be associated with one or more groups. Auto-measure group--Created by combining one auto IP SLAs endpoint list, template, and scheduler.

You can combine any template with any endpoint list and any scheduler and apply the combinationacross many groups.

When the group is scheduled to run, based on the scheduler, one IP SLAs operation is created for eachdestination address in the endpoint list. The operation type depends on the template in the group. If thegroup is deleted or unscheduled, the created IP SLAs operations are removed.

For configuration information, see the "How to Configure Auto IP SLAs in Cisco IOS IP SLAs Engine 3.0"section.

QoS Integration for Auto IP SLAsQoS integration allows for active measurement of QoS performance and enables customers to test network readiness for t he deployment of high priority, low latency traffic that is generated by applic ations such asvoice and vide o. Auto IP SLAs traffic is marked with the app ropriate Differentiated Services Code Point(DSCP) marke r and then sends out the required interface.

Automatic Registration of Destinations for Auto IP SLAs OperationsDestination Cisco devices and Cisco IOS IP SLAs Responders in Cisco devices can be configured toautomatically register with the source. The source will discover the destinations address and put it in anendpoint list.

How to Configure Auto IP SLAs in IP SLAs Engine 3.0 Configuring Automatic Registration of Responder on the Destination Device, page 15 Configuring an Endpoint List on the Source Device, page 15 Configuring a Scheduler on the Source Device, page 19 Configuring a Template on the Source Device, page 21 Adding Proactive Threshold Monitoring to a Template on the Source Device, page 54 Configuring an Auto-Measure Group on the Source Device, page 56

QoS Integration for Auto IP SLAsHow to Configure Auto IP SLAs in IP SLAs Engine 3.0



31/407

Configuring Automatic Registration of Responder on the Destination Device

SUMMARY STEPS

1. enable2. configure terminal3. ip sla responder auto-register {source-ipaddress |source-hostname } [client-id client-id ] [endpoint-list

template-name ] [retry-timer minutes ]4. exit

DETAILED STEPS

Command or Action Purpose

Step 1 enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 ip sla responder auto-register {source-ipaddress |source-hostname }[client-id client-id ] [endpoint-list template-name ] [retry-timer minutes ]

Example:

Router(config)# ip sla responder auto-register 10.1.1.23endpoint-list autolist

Enables destination to register with source.

Step 4 exit

Example:

Router(config)# exit

Exits global configuration mode and returns toprivileged EXEC mode.

Configuring an Endpoint List on the Source DevicePerform one of the following tasks:

Using Automatic Registration to Configure an Endpoint List, page 16 Manually Configuring an Endpoint List, page 18

Configuring Automatic Registration of Responder on the Destination DeviceHow to Configure Auto IP SLAs in IP SLAs Engine 3.0



32/407

Using Automatic Registration to Configure an Endpoint ListXThe destination device or responder must be configured for auto registration. For configurationinformation, see the Configuring Automatic Registration of Responder on the Destination Device

section.

SUMMARY STEPS

1. enable2. configure terminal3. ip sla auto discovery4. ip sla auto endpoint-list type ip template-name5. description description6. discover [port port ]7. access-list {standard-range | expanded-range }8. ageout seconds9. measurement-retry number-of-retries10.end11.show ip sla auto discovery

DETAILED STEPS


Step 1 enable

Example:

Router> enable




Example:



Step 3 ip sla auto discovery

Example:

Router(config)# ip sla auto discovery

Enables the source to discover the responderendpoints.

Configuring Auto IP SLAs in IP SLAs Engine 3.0Using Automatic Registration to Configure an Endpoint List



33/407


Step 4 ip sla auto endpoint-list type ip template-name

Example:

Router(config)# ip sla auto endpoint-list type ipautolist

Begins configuring an endpoint list and entersendpoint-list configuration mode.

Step 5 description description

Example:

Router(config-epl)# description testing discovery

(Optional) Adds descriptive text to the template beingconfigured.

Step 6 discover [port port ]

Example:

Router(config-epl)# discover

Automatically discovers the IP addresses and portnumbers of endpoints on the destination and entersendpoint-list auto-discovery configuration mode.

Step 7 access-list {standard-range | expanded-range }

Example:

Router(config-epl-disc)# access-list 1

Names and adds the list of discovered IP addresses tothe endpoint list being configured.

Step 8 ageout seconds

Example:

Router(config-epl-disc)# ageout 10

(Optional) Sets an ageout timer.

Step 9 measurement-retry number-of-retries

Example:

Router(config-epl-disc)# measurement-retry 10

(Optional) Specifies the number of times to retry afteran operation fails.

Step 10 end

Example:

Router(config-ep-disc)# end

Returns to privileged EXEC mode.

Configuring Auto IP SLAs in IP SLAs Engine 3.0Using Automatic Registration to Configure an Endpoint List



34/407


Step 11 show ip sla auto discovery

Example:

Router# show ip sla auto discovery

(Optional) Displays status of auto-discovery.

Manually Configuring an Endpoint List

SUMMARY STEPS

1. enable2. configure terminal

3. ip sla auto endpoint-list type ip template-name4. description description5. ip-address address [- address | , ... , address ] port port 6. end7. show ip sla auto [type ip [template-name ]]

DETAILED STEPS


Step 1 enable

Example:

Router> enable




Example:



Step 3 ip sla auto endpoint-list type ip template-name

Example:

Router(config)# ip sla auto endpoint-list type ipedgehosts-epl

Begins configuring an endpoint list and enters endpoint-list configuration mode.

Configuring Auto IP SLAs in IP SLAs Engine 3.0Manually Configuring an Endpoint List



35/407



Example:

Router(config-epl)# description manual config


Step 5 ip-address address [- address | , ... , address ] port port

Example:

Router(config-epl)# ip-address 10.1.1.1-13 port 6500

Adds the IP addresses of endpoints to the endpoint listbeing configured.

Use the no from of this command to modify theendpoint list by removing one or more addresses.

Repeat this command until all desired addresses areconfigured.

Step 6 end

Example:

Router(config-epl)# end


Step 7 show ip sla auto [type ip [template-name ]]

Example:

Router# show ip sla auto type ip edgehosts-epl

(Optional) Displays the configuration of the endpoint list.

Configuring a Scheduler on the Source DeviceSUMMARY STEPS

1. enable2. configure terminal3. ip sla auto schedule schedule-id 4. ageout seconds5. frequency {seconds | range random-frequency-range }6. life {forever | seconds }

7. probe-interval milliseconds8. start-time {hh : mm[:ss] [month day | day month ] | pending | now | after hh : mm : ss}9. end10.show ip sla auto schedule [schedule-id ]

Configuring a Scheduler on the Source DeviceManually Configuring an Endpoint List



36/407

DETAILED STEPS


Step 1 enable

Example:

Router> enable




Example:



Step 3 ip sla auto schedule schedule-id

Example:

Router(config)# ip sla auto schedule theschedule

Begins configuring a scheduler and enters IP

SLA auto-measure schedule configuration mode.

Step 4 ageout seconds

Example:

Router(config-am-schedule)# ageout 43200

(Optional) Sets an ageout timer for inactiveoperations.

Step 5 frequency {seconds | range random-frequency-range }

Example:

Router(config-am-schedule)# frequency 60

(Optional) Specifies either the frequency timer

or random frequency range for multipleoperations.

Step 6 life {forever | seconds }

Example:

Router(config-am-schedule)# life 43200

(Optional) Defines the lifetime of the operation.

Step 7 probe-interval milliseconds

Example:

Router(config-am-schedule)# probe-interval 20

(Optional) Specifies the interval for multiple

operations.

Configuring Auto IP SLAs in IP SLAs Engine 3.0Manually Configuring an Endpoint List



37/407


Step 8 start-time {hh : mm[:ss] [month day | day month ] | pending | now |after hh : mm : ss}

Example:

Router(config-am-schedule)# start-time now

(Optional) Specifies the start time of anoperation.

Step 9 end

Example:

Router(config-am-schedule)# end


Step 10 show ip sla auto schedule [schedule-id ]

Example:

Router# show ip sla auto schedule

(Optional) Displays the configuration of thescheduler.

Configuring a Template on the Source Device

Note If you do not configure and apply a template to an auto-measure group, the default type of operation for thegroup is ICMP jitter.

Configuring an ICMP Echo Operation, page 21 Configuring an ICMP Jitter Operation, page 27 Configuring a TCP Connect Operation, page 33 Configuring a UDP Echo Operation, page 38 Configuring a UDP Jitter Operation on the Source Device, page 44

Configuring an ICMP Echo OperationPerform one of the following tasks:

Configuring a Template for a Basic ICMP Echo Operation, page 21

Configuring an ICMP Echo Operation Template with Additional Characteristics, page 23

Configuring a Template for a Basic ICMP Echo Operation

Configuring a Template on the Source DeviceConfiguring an ICMP Echo Operation



38/407

Note We recommend using a Cisco networking device as the destination device although any networking devicethat supports RFC 862, Echo protocol , can be used.

SUMMARY STEPS

1. enable2. configure terminal3. ip sla auto template type ip icmp-echo template-name4. description description5. end

DETAILED STEPS


Step 1 enable

Example:

Router> enable




Example:



Step 3 ip sla auto template type ip icmp-echo template-name

Example:

Router(config)# ip sla auto template type ip icmp-echo tmp-icmpecho

Begins configuring a template and enters IP SLAtemplate configuration mode.


Example:

Router(config-tplt-icmp-ech)# description default oper

temp for icmp echo

(Optional) Adds descriptive text to the templatebeing configured.

Step 5 end

Example:

Router(config-tplt-icmp-ech)# end

Returns to global configuration mode.

Configuring Auto IP SLAs in IP SLAs Engine 3.0Configuring a Template for a Basic ICMP Echo Operation



39/407

Example

The following output shows the configuration, including default values, of a template for an ICMP echooperation:

Router# show

ip sla auto template type ip icmp-echoIP SLAs Auto Template: tpl-icmplechoMeasure Type: icmp-echo (control enabled)Description: default oper temp for icmp echoIP options:

Source IP: 0.0.0.0 Source Port: 0VRF: TOS: 0x0

Operation Parameters:Request Data Size: 16 Verify Data: falseTimeout: 5000 Threshold: 5000

Statistics Aggregation option:Hours of statistics kept: 2

History options:History filter: noneMax number of history records kept: 15Lives of history kept: 0

Statistics Distributions options:Distributions characteristics: RTT

Distributions bucket size: 20Max number of distributions buckets: 1

Reaction Configuration: None

What to Do Next, page 23

What to Do Next

To configure this auto IP SLAs template for proactive threshold monitoring, see the Adding ProactiveThreshold Monitoring to a Template on the Source Device section. Otherwise, see the Configuring anAuto-Measure Group on the Source Device section.

Configuring an ICMP Echo Operation Template with Additional Characteristics

Note We recommend using a Cisco networking device as the destination device although any networking devicethat supports RFC 862, Echo Protocol , can be used.

Configuring Auto IP SLAs in IP SLAs Engine 3.0 What to Do Next



40/407

SUMMARY STEPS


3. ip sla auto template type ip icmp-echo template-name4. description description5. source-ip {ip-address | hostname }6. tos number 7. vrf vrf-name8. parameters9. history buckets-kept size10.history distributions-of-statistics-kept size11.history enhanced [interval seconds ] [buckets number-of-buckets ]12.history filter {none | all | overThreshold | failures }

13.history hours-of-statistics-kept hours14.history lives-kept lives15.history statistics-distribution-interval milliseconds16.request-data-size bytes17.threshold milliseconds18.timeout milliseconds19.verify-data20.end

DETAILED STEPS

Command or Action PurposeStep 1 enable

Example:

Router> enable




Example:



Step 3 ip sla auto template type ip icmp-echo template-name

Example:

Router(config)# ip sla auto template type ip icmp-echo icmp_echo_2

Begins configuring a template and enters IP SLA templateconfiguration mode.

Configuring Auto IP SLAs in IP SLAs Engine 3.0Configuring an ICMP Echo Operation Template with Additional Characteristics



41/407



Example:

Router(config-tplt-icmp-ech)# description customicmp echo template


Step 5 source-ip {ip-address | hostname }

Example:

Router(config-tplt-icmp-ech)# source-ip172.29.139.132

(Optional) Specifies the source for the operation.

Step 6 tos number

Example:

Router(config-tplt-icmp-ech)# tos 160

(Optional) Defines the Type of Service (ToS) byte in the

IPv4 header of an IP SLAs operation.

Step 7 vrf vrf-name

Example:

Router(config-tplt-icmp-ech)# vrf vpn-A

(Optional) Allows monitoring within MultiProtocol LabelSwitching (MPLS) VPNs using IP SLAs operations.

Step 8 parameters

Example:

Router(config-tplt-icmp-ech)# parameters

(Optional) Enters IP SLA template parameters

configuration mode.

Step 9 history buckets-kept size

Example:

Router(config-icmp-ech-params)# history buckets-kept 25

(Optional) Sets the number of history buckets that are keptduring the lifetime of an IP SLAs operation.

Step 10 history distributions-of-statistics-kept size

Example:

Router(config-icmp-ech-params)# historydistributions-of-statistics-kept 5

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




42/407


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

Example:

Router(config-icmp-ech-params)# history enhancedinterval 900 buckets 100

(Optional) Enables enhanced history gathering for an IPSLAs operation.

Step 12 history filter {none | all | overThreshold | failures }

Example:

Router(config-icmp-ech-params)# history filterfailures

(Optional) Defines the type of information kept in thehistory table for an IP SLAs operation.

Step 13 history hours-of-statistics-kept hours

Example:

Router(config-icmp-ech-params)# history hours-of-statistics-kept 4

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

Step 14 history lives-kept lives

Example:

Router(config-icmp-ech-params)# history lives-

kept 5

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

Step 15 history statistics-distribution-interval milliseconds

Example:

Router(config-icmp-ech-params)# historystatistics-distribution-interval 10

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

Step 16 request-data-size bytes

Example:

Router(config-icmp-ech-params)# request-data-size64

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




43/407


Step 17 threshold milliseconds

Example:

Router(config-icmp-ech-params)# threshold 10000

(Optional) Sets the upper threshold value for calculatingnetwork monitoring statistics created by an IP SLAsoperation.

Step 18 timeout milliseconds

Example:

Router(config-icmp-ech-params)# timeout 10000

(Optional) Sets the amount of time an IP SLAs operationwaits for a response from its request packet.

Step 19 verify-data

Example:

Router(config-icmp-ech-params)# verify-data

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

Note Use this command with caution during normaloperations.

Step 20 end

Example:

Router(config-icmp-ech-params)# end



What to Do Next

To configure this auto IP SLAs template for proactive threshold monitoring, see the Adding ProactiveThreshold Monitoring to a Template on the Source Device section. Otherwise, see the Configuring anAuto-Measure Group on the Source Device section.

Configuring an ICMP Jitter OperationPerform one of the following tasks:

Configuring a Template for a Basic ICMP Jitter Operation, page 27 Configuring an ICMP Jitter Operation Template with Additional Characteristics, page 29

Configuring a Template for a Basic ICMP Jitter Operation




44/407

Note When compared to the IP SLAs UDP jitter operation, the IP SLAs ICMP jitter operation may provide

less accurate measurements because the accuracy of the measurements provided by a non-Ciscodestination device cannot be determined.

Because ICMP packets do not support voice technology, the IP SLAs ICMP jitter operation does notsupport Mean Operation Sore (MOS), Calculated Planning Impairment Factor (ICPIF), or estimatedtransmission rating factor (R-factor) reaction configuration capabilities.

SUMMARY STEPS

1. enable2. configure terminal3. ip sla auto template type ip icmp-jitter template-name4. description description

5. end

DETAILED STEPS


Step 1 enable

Example:

Router> enable




Example:



Step 3 ip sla auto template type ip icmp-jitter template-name

Example:

Router(config)# ip sla auto template type ip icmp-jitterbasic_icmp_jitter

Begins configuring the template and enters IPSLA template configuration mode.


Example:

Router(config-tplt-icmp-jtr)# description default opertemp for icmp-jitter

(Optional) Adds descriptive text to the templatebeing configured.

Configuring Auto IP SLAs in IP SLAs Engine 3.0Configuring a Template for a Basic ICMP Jitter Operation



45/407


Step 5 end

Example:

Router(config-tplt-icmp-jtr)# end


Example

The following output shows the configuration, including default values, of a template for a basic ICMP jitter operation:

Router# show ip sla auto template type ip icmp-jitterIP SLAs Auto Template: basic_icmp_jitter

Measure Type: icmp-jitterDescription: default oper temp for icmp jitterIP options:

Source IP: 0.0.0.0VRF: TOS: 0x0

Operation Parameters:Number of Packets: 10 Inter packet interval: 20Timeout: 5000 Threshold: 5000

Statistics Aggregation option:Hours of statistics kept: 2

Statistics Distributions options:Distributions characteristics: RTTDistributions bucket size: 20Max number of distributions buckets: 1

Reaction Configuration: None


What to Do Next

To configure this auto IP SLAs tem plate for proactive threshold monitoring, see the Adding ProactiveThreshold Monitoring to a Template on the Source Device section. Otherwise, see the Configuring anAuto-Measure Group on the Source Device section.

Configuring an ICMP Jitter Operation Template with Additional Characteristics

Note When compared to the IP SLAs UDP jitter operation, the IP SLAs ICMP jitter operation may provide

less accurate measurements because the accuracy of the measurements provided by a non-Ciscodestination device cannot be determined.

Because ICMP packets do not support voice technology, the IP SLAs ICMP jitter operation does not

support MOS, ICPIF, or estimated R-factor reaction configuration capabilities.




46/407

SUMMARY STEPS


3. ip sla auto template type ip icmp-jitter template-name4. description description5. source-ip {ip-address | hostname }6. tos number 7. vrf vrf-name8. parameters9. history distributions-of-statistics-kept size10.history enhanced [interval seconds ] [buckets number-of-buckets ]11.history filter {none | all | overThreshold | failures }12.history hours-of-statistics-kept hours

13.history statistics-distribution-interval milliseconds14.interval milliseconds15.num-packet packet-number 16.threshold milliseconds17.timeout milliseconds18.verify-data19.end

DETAILED STEPS


Step 1 enable

Example:

Router> enable




Example:



Step 3 ip sla auto template type ip icmp-jitter template-name

Example:

Router(config)# ip sla auto template type ip icmp-jitter custom_imcp_jitter

Begins configuring a template and enters IP SLAtemplate configuration mode.

Configuring Auto IP SLAs in IP SLAs Engine 3.0Configuring an ICMP Jitter Operation Template with Additional Characteristics



47/407



Example:

Router(config-tplt-icmp-jtr)# description customicmp jitter template


Step 5 source-ip {ip-address | hostname }

Example:

Router(config-tplt-icmp-jtr)# source-ip 10.1.2.34

(Optional) Specifies the source for the operation.

Step 6 tos number

Example:

Router(config-tplt-icmp-jtr)# tos 160

(Optional) In an IPv4 network only, defines the ToS bytein the IPv4 header of an IP SLAs operation.

Step 7 vrf vrf-name

Example:

Router(config-tplt-icmp-jtr)# vrf vpn-A

(Optional) Allows monitoring within MPLS VPNs usingIP SLAs operations.

Step 8 parameters

Example:

Router(config-tplt-icmp-jtr)# parameters

(Optional) Enters IP SLA template parametersconfiguration mode.

Step 9 history distributions-of-statistics-kept size

Example:

Router(config-icmp-jtr-params)# historydistributions-of-statistics-kept 5

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

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

buckets ]

Example:

Router(config-icmp-jtr-params)# history enhancedinterval 900 buckets 100

(Optional) Enables enhanced history gathering for an IP

SLAs operation.

Configuring Auto IP SLAs in IP SLAs Engine 3.0Configuring an ICMP Jitter Operation Template with Additional Characteristics



48/407


Step 11 history filter {none | all | overThreshold | failures }

Example:

Router(config-icmp-jtr-params)# history filterfailures

(Optional) Defines the type of information kept in thehistory table for an IP SLAs operation.

Step 12 history hours-of-statistics-kept hours

Example:

Router(config-icmp-jtr-params)# history hours-of-statistics-kept 4

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

Step 13 history statistics-distribution-interval milliseconds

Example:

Router(config-icmp-jtr-params)# history statistics-distribution-interval 10

(Optional) Sets the time interval for each statistics

distribution kept for an IP SLAs operation.

Step 14 interval milliseconds

Example:

Router(config-icmp-jtr-params)# interval 40

(Optional) Sets number of milliseconds between sentpackets.

Step 15 num-packet packet-number

Example:

Router(config-icmp-jtr-params)# num-packets 100

(Optional) Sets number of packets to be sent.

Step 16 threshold milliseconds

Example:

Router(config-icmp-jtr-params)# threshold 10000

(Optional) Sets the upper threshold value for calculatingnetwork monitoring statistics created by an IP SLAsoperation.