Table Of Contents
IP SLAs—Analyzing IP Service Levels Using the DLSw+ Operation
Contents
Prerequisites for the IP SLAs DLSw+ Operation
Information About the IP SLAs DLSw+ Operation
DLSw+ Operation
How to Configure the IP SLAs DLSw+ Operation
Configuring and Scheduling a DLSw+ Operation on the Source Device
Configuring and Scheduling a Basic DLSw+ Operation on the Source Device
Configuring and Scheduling a DLSw+ Operation with Optional Parameters on the Source Device
Configuration Examples for the IP SLAs DLSw+ Operation
Configuring a DLSw+ Operation: Example
Where to Go Next
Additional References
Related Documents
Standards
MIBs
RFCs
Technical Assistance
Feature Information for the IP SLAs DLSw+ Operation
IP SLAs—Analyzing IP Service Levels Using the DLSw+ Operation
First Published: August 14, 2006
Last Updated: August 29, 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. IP SLAs is a portfolio of technology embedded in most devices that run Cisco IOS software, which allows Cisco customers to analyze IP service levels for IP applications and services, to increase productivity, to lower operational costs, and to 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. 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. 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 IP SLAs DLSw+ Operation" section.
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 IP SLAs DLSw+ Operation
•
Information About the IP SLAs DLSw+ Operation
•
How to Configure the IP SLAs DLSw+ Operation
•
Configuration Examples for the IP SLAs DLSw+ Operation
•
Where to Go Next
•
Additional References
•
Feature Information for the IP SLAs DLSw+ Operation
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.
Information About the IP SLAs DLSw+ Operation
To perform the tasks required to analyze DLSw+ peer response times using IP SLA, you should understand the following concept:
•
DLSw+ Operation
DLSw+ Operation
The Cisco IOS IP SLAs DLSw+ operation measures the DLSw+ protocol stack and network response time between DLSw+ peers. DLSw+ is the enhanced Cisco version of RFC 1795. DLSw+ tunnels non-routable Layer 2 traffic such as Systems Network Architecture (SNA) traffic over IP backbones via TCP. The networking devices performing the tunneling of non-routable traffic into TCP/IP are referred to as DLSw+ peers. DLSw+ peers normally communicate through TCP port 2065. The destination networking device does not have to be a Cisco router if it supports RFC 1795.
In Figure 1, Router A is configured as the source IP SLAs device and a DLSw+ operation is configured with Router B as the remote DLSw+ peer. Router A and Router B are configured as connected DLSw+ peers. The peer (destination device) does not have to run a Cisco IOS IP SLA-capable image.
Figure 1 DLSw+ Operation
Network response time is computed by measuring the round-trip time (RTT) taken to connect to the remote DLSw+ peer using TCP. This operation does not use the IP SLAs Responder.
How to Configure the IP SLAs DLSw+ Operation
This section contains the following procedure:
•
Configuring and Scheduling a DLSw+ Operation on the Source Device (required)
Configuring and Scheduling a DLSw+ Operation on the Source Device
To measure the response time between a Cisco device and a DLSw+ peer, use the IP SLAs DLSw+ operation. This operation does not require the IP SLAs Responder to be enabled so there are no tasks to be performed on the destination device.
Perform one of the following tasks in this section, 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
•
Configuring and Scheduling a DLSw+ Operation with Optional Parameters on the Source Device
Configuring and Scheduling a Basic DLSw+ Operation on the Source Device
Perform this task to enable a DLSw+ operation without any optional parameters.
Note
For information on scheduling a group of operations, see the "IP SLAs—Multioperation Scheduling of IP SLAs Operations" chapter of the Cisco IOS IP SLAs Configuration Guide.
Prerequisites
Before enabling the IP SLAs DLSw+ operation you must configure a connected DLSw+ peer between the source and destination networking devices.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip sla operation-number
4.
dlsw peer-ipaddr ip-address
5.
frequency seconds
6.
exit
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]
8.
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 operation-number
Example:
Router(config)# ip sla 10
|
Begins configuration for an IP SLAs operation and enters IP SLA configuration mode.
|
Step 4
|
dlsw peer-ipaddr ip-address
Example:
Router(config-ip-sla)# dlsw peer-ipaddr
172.21.27.11
|
Defines a DLSw+ operation and enters IP SLA DLSw+ configuration mode.
|
Step 5
|
frequency seconds
Example:
Router(config-ip-sla-dlsw)# frequency 30
|
(Optional) Sets the rate at which a specified IP SLAs operation repeats.
|
Step 6
|
exit
Example:
Router(config-ip-sla-dlsw)# exit
|
Exits IP SLA DLSw+ configuration mode and returns to global configuration mode.
|
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]
Example:
Router(config)# ip sla schedule 10 start-time
now life forever
|
Configures the scheduling parameters for an individual IP SLAs operation.
|
Step 8
|
exit
Example:
Router(config)# exit
|
(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. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable.
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. The source device is the location at which the measurement statistics are stored.
Note
For information on scheduling a group of operations, see the "IP SLAs—Multioperation Scheduling of IP SLAs Operations" chapter of the Cisco IOS IP SLAs Configuration Guide.
Prerequisites
Before enabling the IP SLAs DLSw+ operation you must configure a connected DLSw+ peer between the source and destination networking devices.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip sla operation-number
4.
dlsw peer-ipaddr ip-address
5.
history buckets-kept size
6.
history distributions-of-statistics-kept size
7.
history enhanced [interval seconds] [buckets number-of-buckets]
8.
history filter {none | all | overThreshold | failures}
9.
frequency seconds
10.
history hours-of-statistics-kept hours
11.
history lives-kept lives
12.
owner owner-id
13.
request-data-size bytes
14.
history statistics-distribution-interval milliseconds
15.
tag text
16.
threshold milliseconds
17.
timeout milliseconds
18.
exit
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]
20.
exit
21.
show ip sla configuration [operation-number]
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 operation-number
Example:
Router(config)# ip sla 10
|
Begins configuration for an IP SLAs operation and enters IP SLA configuration mode.
|
Step 4
|
dlsw peer-ipaddr ip-address
Example:
Router(config-ip-sla)# dlsw peer-ipaddr
172.21.27.11
|
Defines a DLSw+ operation and enters IP SLA DLSw configuration mode.
|
Step 5
|
history buckets-kept size
Example:
Router(config-ip-sla-dlsw)# history
buckets-kept 25
|
(Optional) Sets the number of history buckets that are kept during the lifetime of an IP SLAs operation.
|
Step 6
|
history distributions-of-statistics-kept size
Example:
Router(config-ip-sla-dlsw)# history
distributions-of-statistics-kept 5
|
(Optional) Sets the number of statistics distributions kept per hop during an IP SLAs operation.
|
Step 7
|
history enhanced [interval seconds] [buckets
number-of-buckets]
Example:
Router(config-ip-sla-dlsw)# history enhanced
interval 900 buckets 100
|
(Optional) Enables enhanced history gathering for an IP SLAs operation.
|
Step 8
|
history filter {none | all | overThreshold |
failures}
Example:
Router(config-ip-sla-dlsw)# history filter
failures
|
(Optional) Defines the type of information kept in the history table for an IP SLAs operation.
|
Step 9
|
frequency seconds
Example:
Router(config-ip-sla-dlsw)# frequency 30
|
(Optional) Sets the rate at which a specified IP SLAs operation repeats.
|
Step 10
|
history hours-of-statistics-kept hours
Example:
Router(config-ip-sla-dlsw)#
hours-of-statistics-kept 4
|
(Optional) Sets the number of hours for which statistics are maintained for an IP SLAs operation.
|
Step 11
|
history lives-kept lives
Example:
Router(config-ip-sla-dlsw)# history lives-kept
5
|
(Optional) Sets the number of lives maintained in the history table for an IP SLAs operation.
|
Step 12
|
owner owner-id
Example:
Router(config-ip-sla-dlsw)# owner admin
|
(Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation.
|
Step 13
|
request-data-size bytes
Example:
Router(config-ip-sla-dlsw)# request-data-size
64
|
(Optional) Sets the protocol data size in the payload of an IP SLAs operation's request packet.
|
Step 14
|
history statistics-distribution-interval
milliseconds
Example:
Router(config-ip-sla-dlsw)# history
statistics-distribution-interval 10
|
(Optional) Sets the time interval for each statistics distribution kept for an IP SLAs operation.
|
Step 15
|
tag text
Example:
Router(config-ip-sla-dlsw)# tag
TelnetPollServer1
|
(Optional) Creates a user-specified identifier for an IP SLAs operation.
|
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.
|
Step 17
|
timeout milliseconds
Example:
Router(config-ip-sla-dlsw)# timeout 10000
|
(Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet.
|
Step 18
|
exit
Example:
Router(config-ip-sla-dlsw)# exit
|
Exits DLSw configuration submode and returns to global configuration mode.
|
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]
Example:
Router(config)# ip sla schedule 10 start-time
now life forever
|
Configures the scheduling parameters for an individual IP SLAs operation.
|
Step 20
|
exit
Example:
Router(config)# exit
|
(Optional) Exits global configuration mode and returns to privileged EXEC mode.
|
Step 21
|
show ip sla configuration [operation-number]
Example:
Router# show ip sla configuration 10
|
(Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation.
|
Examples
The following sample output shows the configuration of all the IP SLAs parameters (including defaults) for the DLSw+ operation number 14.
Router# show ip sla configuration 14
Complete Configuration Table (includes defaults)
Type of operation to perform: dlsw
Peer address: 172.21.27.11
Request size (ARR data portion): 0
Operation timeout (milliseconds): 50000
Operation frequency (seconds): 50
Next Scheduled Start Time: Start Time already passed
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.
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 DLSw+ Operation
This section contains the following configuration example:
•
Configuring a DLSw+ Operation: Example
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, a remote DLSw+ peer. Router B is configured as a DLSw+ peer and Router A is specified as the remote (connected) DLSw+ peer. Router A is then configured as a DLSw+ peer with Router B as the connected DLSw+ peer, and the IP SLAs DLSw+ operation parameters are configured. The operation is scheduled to start immediately and run for 7200 seconds (2 hours).
Router B Configuration
dlsw local-peer peer-id 172.21.27.11
dlsw remote-peer 0 tcp 172.20.26.10
Router A Configuration
dlsw local-peer peer-id 172.20.26.10
dlsw remote-peer 0 tcp 172.21.27.11
dlsw peer-ipaddr 172.21.27.11
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, see the Cisco IOS IP SLAs Features Roadmap.
Additional References
The following sections provide references related to the IP SLAs DLSw+ operation.
Related Documents
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
|
MIBs Link
|
CISCO-RTTMON-MIB
|
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
|
Title
|
RFC 1795
|
Data Link Switching: Switch-to-Switch Protocol
|
Technical Assistance
Description
|
Link
|
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.
|
http://www.cisco.com/public/support/tac/home.shtml
|
Feature Information for the IP SLAs DLSw+ 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 DLSw+ Operation
Feature Name
|
Releases
|
Feature Information
|
IP SLAs DLSw+ Operation
|
12.3(14)T
|
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, 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.