Configuring IP SLAs UDP Echo Operations

Last Updated: July 18, 2011

This module describes how to configure an IP Service Level Agreements (SLAs) User Datagram Protocol (UDP) Echo operation to monitor end-to-end response time between a Cisco router and devices using IPv4 or IPv6. UDP echo accuracy is enhanced by using the IP SLAs Responder at the destination Cisco router. This module also demonstrates how the results of the UDP echo operation can be displayed and analyzed to determine how a UDP application is performing.

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.

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

Restrictions for IP SLAs UDP Echo Operations

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

Information About IP SLAs UDP Echo Operations

UDP Echo Operation

The UDP echo operation measures end-to-end response time between a Cisco router and devices using IP. UDP is a transport layer (Layer 4) Internet protocol that is used for many IP services. UDP echo is used to measure response times and test end-to-end connectivity.

In the figure below Router A has been configured as an IP SLAs Responder and Router B is configured as the source IP SLAs device.

Figure 1 UDP Echo Operation


Response time (round-trip time) is computed by measuring the time taken between sending a UDP echo request message from Router B to the destination router--Router A--and receiving a UDP echo reply from Router A. UDP echo accuracy is enhanced by using the IP SLAs Responder at Router A, the destination Cisco router. If the destination router is a Cisco router, then IP SLAs sends a UDP datagram to any port number that you specified. Using the IP SLAs Responder is optional for a UDP echo operation when using Cisco devices. The IP SLAs Responder cannot be configured on non-Cisco devices.

The results of a UDP echo operation can be useful in troubleshooting issues with business-critical applications by determining the round-trip delay times and testing connectivity to both Cisco and non-Cisco devices.

How to Configure IP SLAs UDP Echo Operations

Configuring the IP SLAs Responder on the Destination Device

Before You Begin

If you are using the IP SLAs Responder, ensure that the networking device to be used as the responder is a Cisco device and that you have connectivity to that device through the network.


SUMMARY STEPS

1.    enable

2.    configure terminal

3.   Do one of the following:

  • ip sla responder
  • ip sla responder udp-echo ipaddress ip-address port port

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
Do one of the following:
  • ip sla responder
  • ip sla responder udp-echo ipaddress ip-address port port


Example:

Router(config)# ip sla responder



Example:

Router(config)# ip sla responder udp-echo ipaddress 172.29.139.132 port 5000

 

(Optional) Temporarily enables IP SLAs Responder functionality on a Cisco device in response to control messages from source.

or

(Optional) Required only if protocol control is disabled on source. Permanently enables IP SLAs Responder functionality on specified IP address and port.

  • Control is enabled by default.
 
Step 4
exit


Example:

Router(config)# exit

 

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

 

Configuring a UDP Echo Operation on the Source Device

Perform only one of the following tasks:

Configuring a Basic UDP Echo Operation on the Source Device

Before You Begin

If you are using the IP SLAs Responder, ensure that you have completed the "Configuring the IP SLAs Responder on the Destination Device" section before you start this task.


SUMMARY STEPS

1.    enable

2.    configure terminal

3.    ip sla operation-number

4.    udp-echo {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname} source-port port-number] [control {enable | disable}]

5.    frequency seconds

6.    end


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
udp-echo {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname} source-port port-number] [control {enable | disable}]


Example:

Router(config-ip-sla)# udp-echo 172.29.139.134 5000

 

Defines a UDP echo operation and enters IP SLA UDP configuration mode.

  • Use the control disable keyword combination only if you disable the IP SLAs control protocol on both the source and target routers.
 
Step 5
frequency seconds


Example:

Router(config-ip-sla-udp)# frequency 30

 

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

 
Step 6
end


Example:

Router(config-ip-sla-udp)# end

 

Returns to prileged EXEC mode.

 
What to Do Next

To add proactive threshold conditions and reactive triggering for generating traps, or for starting another operation, to an IP SLAs operation, see the "Configuring Proactive Threshold Monitoring" section.

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

Before You Begin

If you are using an IP SLAs Responder in this operation, the responder must be configured on the destination device. See the "Configuring the IP SLAs Responder on the Destination Device."


SUMMARY STEPS

1.    enable

2.    configure terminal

3.    ip sla operation-number

4.    udp-echo {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname} source-port port-number] [control {enable | disable}]

5.    history buckets-kept size

6.    data-pattern hex-pattern

7.    history distributions-of-statistics-kept size

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

9.    history filter {none | all | overThreshold | failures}

10.    frequency seconds

11.    history hours-of-statistics-kept hours

12.    history lives-kept lives

13.    owner owner-id

14.    request-data-size bytes

15.    history statistics-distribution-interval milliseconds

16.    tag text

17.    threshold milliseconds

18.    timeout milliseconds

19.   Do one of the following:

  • tos number
  • traffic-class number

20.    flow-label number

21.    verify-data

22.    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
udp-echo {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname} source-port port-number] [control {enable | disable}]


Example:

Router(config-ip-sla)# udp-echo 172.29.139.134 5000

 

Defines a UDP echo operation and enters IP SLA UDP configuration mode.

  • Use the control disable keyword combination only if you disable the IP SLAs control protocol on both the source and target routers.
 
Step 5
history buckets-kept size


Example:

Router(config-ip-sla-udp)# history buckets-kept 25

 

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

 
Step 6
data-pattern hex-pattern


Example:

Router(config-ip-sla-udp)# data-pattern

 

(Optional) Specifies the data pattern in an IP SLAs operation to test for data corruption.

 
Step 7
history distributions-of-statistics-kept size


Example:

Router(config-ip-sla-udp)# history distributions-of-statistics-kept 5

 

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

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


Example:

Router(config-ip-sla-udp)# history enhanced interval 900 buckets 100

 

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

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


Example:

Router(config-ip-sla-udp)# history filter failures

 

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

 
Step 10
frequency seconds


Example:

Router(config-ip-sla-udp)# frequency 30

 

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

 
Step 11
history hours-of-statistics-kept hours


Example:

Router(config-ip-sla-udp)# history hours-of-statistics-kept 4

 

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

 
Step 12
history lives-kept lives


Example:

Router(config-ip-sla-udp)# history lives-kept 5

 

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

 
Step 13
owner owner-id


Example:

Router(config-ip-sla-udp)# owner admin

 

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

 
Step 14
request-data-size bytes


Example:

Router(config-ip-sla-udp)# request-data-size 64

 

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

 
Step 15
history statistics-distribution-interval milliseconds


Example:

Router(config-ip-sla-udp)# history statistics-distribution-interval 10

 

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

 
Step 16
tag text


Example:

Router(config-ip-sla-udp)# tag TelnetPollServer1

 

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

 
Step 17
threshold milliseconds


Example:

Router(config-ip-sla-udp)# threshold 10000

 

(Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation.

 
Step 18
timeout milliseconds


Example:

Router(config-ip-sla-udp)# timeout 10000

 

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

 
Step 19
Do one of the following:
  • tos number
  • traffic-class number


Example:

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



Example:

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

 

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

or

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

 
Step 20
flow-label number


Example:

Router(config-ip-sla-udp)# flow-label 112233

 

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

 
Step 21
verify-data


Example:

Router(config-ip-sla-udp)# verify-data

 

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

 
Step 22
exit


Example:

Router(config-ip-sla-udp)# exit

 

Exits UDP configuration submode and returns to global configuration mode.

 
What to Do Next

To add proactive threshold conditions and reactive triggering for generating traps, or for starting another operation, to an IP SLAs operation, see the "Configuring Proactive Threshold Monitoring" section.

Scheduling IP SLAs Operations


Note
  • All IP SLAs operations to be scheduled must be already configured.
  • The frequency of all operations scheduled in a multioperation group must be the same.
  • List of one or more operation ID numbers to be added to a multioperation group is limited to a maximum of 125 characters, including commas (,).
SUMMARY STEPS

1.    enable

2.    configure terminal

3.    Do one of the following:

  • 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]
  • ip sla group schedule group-operation-number operation-id-numbers schedule-period schedule-period-range [ageout seconds] [frequency group-operation-frequency] [life{forever | seconds}] [start-time{hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}]

4.    exit

5.    show ip sla group schedule

6.    show ip sla configuration


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
Do one of the following:
  • 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]
  • ip sla group schedule group-operation-number operation-id-numbers schedule-period schedule-period-range [ageout seconds] [frequency group-operation-frequency] [life{forever | seconds}] [start-time{hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}]


Example:

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



Example:

Router(config)# ip sla group schedule 1 3,4,6-9

 

For individual IP SLAs operations only:

Configures the scheduling parameters for an individual IP SLAs operation.

or

For multioperation scheduler only:

Specifies an IP SLAs operation group number and the range of operation numbers to be scheduled in global configuration mode.

 
Step 4
exit


Example:

Router(config)# exit

 

Exits to privileged EXEC mode.

 
Step 5
show ip sla group schedule


Example:

Router# show ip sla group schedule

 

(Optional) Displays the IP SLAs group schedule details.

 
Step 6
show ip sla configuration


Example:

Router# show ip sla configuration

 

(Optional) Displays the IP SLAs configuration details.

 

Troubleshooting Tips

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

What to Do Next

To add proactive threshold conditions and reactive triggering for generating traps, or for starting another operation, to an IP SLAs operation, see the "Configuring Proactive Threshold Monitoring" section.

To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable.

Configuration Examples for IP SLAs UDP Echo Operations

Example Configuring a UDP Echo Operation

The following example configures an IP SLAs operation type of UDP echo that will start immediately and run indefinitely.

ip sla 5
 udp-echo 172.29.139.134 5000
 frequency 30
 request-data-size 160
 tos 128
 timeout 1000
 tag FLL-RO
ip sla schedule 5 life forever start-time now

Additional References

Related 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

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 862

Echo Protocol

Technical Assistance

Description

Link

The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password.

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

Feature Information for the IP SLAs UDP Echo Operation

The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.

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

Table 1 Feature Information for the IP SLAs UDP Echo Operation

Feature Name

Releases

Feature Information

IP SLAs UDP Jitter Operation

12.2(31)SB2

12.2(33)SRB1

12.2(33)SXH

12.3(14)T

15.0(1)S

Cisco IOS XE 3.1.0SG

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

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

12.2(33)SRC

12.2(33)SB

12.4(20)T

Cisco IOS XE 3.1.0SG

12.2(50SY

Support was added for operability in IPv6 networks.

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)

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