This documentation has been moved
Configuring ICMP Jitter Operations
Downloads: This chapterpdf (PDF - 168.0KB) The complete bookPDF (PDF - 1.82MB) | Feedback

Configuring Cisco IP SLAs ICMP Jitter Operations

Table Of Contents

Configuring Cisco IP SLAs ICMP Jitter Operations

Finding Feature Information

Contents

Restrictions for IP SLAs ICMP Jitter Operations

Information About IP SLAs ICMP Jitter Operations

Benefits of the IP SLAs ICMP Jitter Operation

Statistics Measured by the IP SLAs ICMP Jitter Operation

How to Configure IP SLAs ICMP Jitter Operations

Configuring an IP SLAs ICMP Jitter Operation

Scheduling IP SLAs Operations

Restrictions

Troubleshooting Tips

What to Do Next

Configuration Examples for IP SLAs ICMP Jitter Operations

Example: Configuring an IP SLAs ICMP Jitter Operation

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Feature Information for IP SLAs ICMP Jitter Operations


Configuring Cisco IP SLAs ICMP Jitter Operations


First Published: August 14, 2006
Last Updated: January 7, 2011

This module describes how to configure a Cisco IOS IP Service Level Agreements (SLAs) Internet Control Message Protocol (ICMP) Jitter operation for generating a stream of ICMP packets between a Cisco IOS device (source) and any other IP device (destination) to gather network performance-related statistics. The destination device can be any network device that supports ICMP such as a server or workstation. Available statistical measurements for IP SLAs ICMP jitter operations include latency, round-trip time, jitter (interpacket delay variance), and packet loss. The IP SLAs ICMP jitter operation does not require an IP SLAs Responder on the destination device.

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 for IP SLAs ICMP Jitter Operations" section.

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

Contents

Restrictions for IP SLAs ICMP Jitter Operations

Information About IP SLAs ICMP Jitter Operations

How to Configure IP SLAs ICMP Jitter Operations

Configuration Examples for IP SLAs ICMP Jitter Operations

Additional References

Feature Information for IP SLAs ICMP Jitter Operations

Restrictions for IP SLAs ICMP Jitter Operations

When compared to the IP SLAs User Datagram Protocol (UDP) jitter operation, the IP SLAs ICMP jitter operation may provide less accurate measurements because the accuracy of the measurements provided by a non-Cisco destination device cannot be determined.

Because ICMP packets do not support voice technology, the IP SLAs ICMP jitter operation does not support Mean Opinion Score (MOS), Calculated Planning Impairment Factor (ICPIF), or estimated transmission rating factor (R) reaction configuration capabilities.

Information About IP SLAs ICMP Jitter Operations

Benefits of the IP SLAs ICMP Jitter Operation

Statistics Measured by the IP SLAs ICMP Jitter Operation

Benefits of the IP SLAs ICMP Jitter Operation

The IP SLAs ICMP Jitter Operation feature provides the following key benefits:

End-to-end performance measurements between a Cisco device (source) and any other IP device (destination) using ICMP.

Proactive threshold violation monitoring through Simple Network Management Protocol (SNMP) trap notifications and syslog messages.

Statistics Measured by the IP SLAs ICMP Jitter Operation

The IP SLAs ICMP jitter operation supports the following statistical measurements:

Jitter (source-to-destination and destination-to-source)

Latency (source-to-destination and destination-to-source)

Round-trip time latency

Packet loss

Successive packet loss

Out-of-sequence packets (source-to-destination, destination-to-source, and round-trip)

Late packets

IP SLAs ICMP jitter uses a two ICMP time stamp messages, an ICMP Timestamp Request (Type 13) and an ICMP Timestamp Reply (Type 14), to provide jitter, packet loss, and latency. IP SLAs ICMP jitter operations differ from IP SLAs ICMP echo operations in that ICMP echo uses ICMP Echo request and reply (ping). Devices that are fully compliant with RFC 792, Internet Control Message Protocol, must be able to respond to the time stamp messages without requiring an IP SLA responder at the destination. Cisco devices support RFC 792.

The ICMP API sends a configurable number of request message packets out of the interface. The data (time stamp) that is received in the request is returned in a reply message packet along with another time stamp. Every packet includes three time stamps: an Originate (sent) Timestamp, a Receive Timestamp, and a Transmit (reply) Timestamp.

IP SLAs utilizes the time stamps to calculate jitter for each direction, based on the difference between interarrival and interdeparture delay for two successive packets. If the difference is positive, it is counted in positive jitter. A negative value is counted in negative jitter. Separate measurements for the source-to-destination and destination-to-source data paths can be used to identify problems in your network because the paths can be different (asymmetric).

Each ICMP packet includes a sequence number in its header that is used to count the number of packets received out of sequence on the sender. Both the sequence number and the receive timestamps can be used to calculate out-of-sequence packets on the source-to-destination path. If the receive time stamp for a packet is greater than that of the next packet, the first packet was delivered out of order on the source-to-destination path. For the destination-to-source path, the same method can be applied. Note that if the packet is out of order on the source-to-destination path, it should be returned out of order to the sender unless there is also misordering on the destination-to-source path.

If any packet cannot be sent due to an internal or unexpected error, or because the timerwheel slot containing the packet is missed, it is counted as Packet Skipped. This metric is very important because statistics are measured on sent packets only.

All timed-out packets are counted towards Packet Loss. Successive packet loss is calculated by counting, and adding, the number of successive dropped packets. Successive packet loss is reported as minimum of successive packet drop and maximum of successive packet drop.

All other statistics are calculated using the same logic as a UDP jitter operation.

How to Configure IP SLAs ICMP Jitter Operations

Configuring an IP SLAs ICMP Jitter Operation (required)

Scheduling IP SLAs Operations

Configuring an IP SLAs ICMP Jitter Operation


Note This operation does not require an IP SLAs Responder on the destination device.


SUMMARY STEPS

1. enable

2. configure terminal

3. ip sla operation-number

4. icmp-jitter {destination-ip-address | destination-hostname} [interval milliseconds] [num-packets packet-number] [source-ip {ip-address | hostname}]

5. frequency seconds

6. history history-parameter

7. owner owner-id

8. tag text

9. threshold milliseconds

10. timeout milliseconds

11. tos number

12. vrf vrf-name

13. 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 

icmp-jitter {destination-ip-address | destination-hostname} [interval milliseconds] [num-packets packet-number] [source-ip {ip-address | hostname}]

Example:

Router(config-ip-sla)# icmp-jitter 172.18.1.129 interval 40 num-packets 100 source-ip 10.1.2.34

Configures the IP SLAs operation as an ICMP jitter operation and enters IP SLAs ICMP jitter configuration mode.

Step 5 

frequency seconds

Example:

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

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

Step 6 

history history-parameter

Example:

Router(config-ip-sla-icmpjitter)# history hours-of-statistics-kept 3

(Optional) Specifies the parameters used for gathering statistical history information for an IP SLAs operation.

Step 7 

owner owner-id

Example:

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

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

Step 8 

tag text

Example:

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

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

Step 9 

threshold milliseconds

Example:

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

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

Step 10 

timeout milliseconds

Example:

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

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

Step 11 

tos number

Example:

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

(Optional) Defines a type of service (ToS) byte in the IP header of an IP SLAs operation.

Step 12 

vrf vrf-name

Example:

Router(config-ip-sla-icmpjitter)# vrf vpn-A

(Optional) Allows monitoring within Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs) using IP SLAs operations.

Step 13 

end

Example:

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

Exits to privileged EXEC mode.

Scheduling IP SLAs Operations

Restrictions

The frequency of all operations scheduled in a multioperation group must be the same.

Operation ID numbers are limited to a maximum of 125 characters. Do not give large integer values as operation ID numbers.

SUMMARY STEPS

1. enable

2. configure terminal

For individual IP SLAs operations only:

3. 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]

For multioperation scheduler only:

4. 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}]

5. exit

6. show ip sla group schedule

7. 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 

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

For individual IP SLAs operations only:

Configures the scheduling parameters for an individual IP SLAs operation.

Step 4 

ip sla group schedule group-operation-number 
operation-id-numbers 
schedule-period schedule-period-range [ageout  
seconds] [frequency group-operation-frequency] 
[life {foreverseconds}] 
[start-time {hh:mm[:ss] 
[month day | day month] | pending | now | 
after hh:mm:ss}]
Example:

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

For multioperation scheduler only:

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

The frequency of all operations scheduled in the operation group should be the same.

The operation ID numbers are limited to a maximum of 125 characters. Do not use large integer values as operation ID numbers.

Step 5 

exit

Example:

Router(config)# exit

Exits to privileged EXEC mode.

Step 6 

show ip sla group schedule

Example:
Router# show ip sla group schedule

(Optional) Displays the IP SLAs group schedule details.

Step 7 

show ip sla configuration
Example:
Router# show ip sla configuration

(Optional) Displays the IP SLAs configuration details.

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 add proactive threshold conditions and reactive triggering for generating traps, or for starting another operation, to an IP SLAs operation, see Configuring Proactive Threshold Monitoring.

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

Configuration Examples for IP SLAs ICMP Jitter Operations

Example: Configuring an IP SLAs ICMP Jitter Operation

Example: Configuring an IP SLAs ICMP Jitter Operation

The following example shows how to configure an IP SLAs ICMP jitter operation:

ip sla 10
 icmp-jitter 172.18.1.129 interval 40 num-packets 100 source-ip 10.1.2.34
 frequency 50
!
ip sla reaction-configuration 1 react jitterAvg threshold-value 5 2 action-type trap 
threshold-type immediate
!
ip sla schedule 1 start-time now life forever
 

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

Cisco IOS IP SLAs: general information

"Cisco IOS IP SLAs Overview" chapter of the Cisco IP SLAs Configuration Guide.


Standards

Standard
Title

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


MIBs

MIB
MIBs Link

CISCO-RTTMON-MIB

CISCO-RTTMON-ICMP-MIB

To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL:

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


RFCs

RFC
Title

RFC 792

Internet Control Message 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 IP SLAs ICMP Jitter Operations

Table 1 lists the features in this module and provides links to specific configuration information.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which 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 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.


Table 1 Feature Information for ICMP Jitter Operations 

Feature Name
Releases
Feature Information

IP SLAs ICMP Jitter Operation

12.4(6)T

The Cisco IOS IP Service Level Agreements (SLAs) Internet Control Message Protocol (ICMP) jitter operation provides the capability to generate a stream of ICMP packets between a Cisco IOS device (source) and any other IP device (destination) to gather network performance-related statistics. Available statistical measurements for the IP SLAs ICMP jitter operation include latency, round-trip time, jitter (interpacket delay variance), and packet loss.