Restrictions for IP SLAs ICMP Path 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.
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This module describes how to configure an IP Service Level Agreements (SLAs) Internet Control Message Protocol (ICMP) Path Echo operation to monitor end-to-end and hop-by-hop response time between a Cisco device and other devices using IP. ICMP Path Echo is useful for determining network availability and for troubleshooting network connectivity issues. The results of the ICMP Path Echo operation can be displayed and analyzed to determine how ICMP is performing.
We recommend using a Cisco networking device as the destination device although any networking device that supports RFC 862, Echo protocol, can be used.
To monitor ICMP Path Echo performance on a device, use the IP SLAs ICMP Path Echo operation. An ICMP Path Echo operation measures end-to-end and hop-by-hop response time between a Cisco device and other devices using IP. ICMP Path Echo is useful for determining network availability and for troubleshooting network connectivity issues.
The IP SLAs ICMP Path Echo operation records statistics for each hop along the path that the IP SLAs operation takes to reach its destination. The ICMP Path Echo operation determines this hop-by-hop response time between a Cisco device and any IP device on the network by discovering the path using the traceroute facility.
In the figure below the source IP SLAs device uses traceroute to discover the path to the destination IP device. A ping is then used to measure the response time between the source IP SLAs device and each subsequent hop in the path to the destination IP device.
Using the statistics recorded for the response times and availability, the ICMP Path Echo operation can identify a hop in the path that is causing a bottleneck.
Note |
This operation does not require an IP SLAs Responder on the destination device. |
Perform only one of the following tasks:
Command or Action | Purpose | |
---|---|---|
Step 1 |
enable Example:
|
Enables privileged EXEC mode.
|
Step 2 |
configure terminal Example:
|
Enters global configuration mode. |
Step 3 |
ip sla operation-id Example:
|
Specifies an ID number for the operation being configured, and enters IP SLA configuration mode. |
Step 4 |
path-echo {destination-ip-address | destination-hostname } [source-ip {ip-address | hostname }] Example:
|
Defines a Path Echo operation and enters IP SLA Path Echo configuration mode. |
Step 5 |
frequency seconds Example:
|
(Optional) Sets the rate at which a specified IP SLAs operation repeats. |
Step 6 |
end Example:
|
Exits to privileged EXEC mode. |
The following example shows the configuration of the IP SLAs ICMP Path Echo operation number 7 that will start in 30 seconds and run for 5 minutes.
ip sla 7
path-echo 172.29.139.134
frequency 30
!
ip sla schedule 7 start-time after 00:00:30 life 300
Command or Action | Purpose | |
---|---|---|
Step 1 |
enable Example:
|
Enables privileged EXEC mode.
|
Step 2 |
configure terminal Example:
|
Enters global configuration mode. |
Step 3 |
ip sla operation-number Example:
|
Begins configuration for an IP SLAs operation and enters IP SLA configuration mode. |
Step 4 |
path-echo {destination-ip-address | destination-hostname } [source-ip {ip-address | hostname }] Example:
|
Defines a Path Echo operation and enters IP SLA Path Echo configuration mode. |
Step 5 |
history buckets-kept size Example:
|
(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:
|
(Optional) Sets the number of statistics distributions kept per hop during an IP SLAs operation. |
Step 7 |
history filter {none | all | overThreshold | failures } Example:
|
(Optional) Defines the type of information kept in the history table for an IP SLAs operation. |
Step 8 |
frequency seconds Example:
|
(Optional) Sets the rate at which a specified IP SLAs operation repeats. |
Step 9 |
history hours-of-statistics-kept hours Example:
|
(Optional) Sets the number of hours for which statistics are maintained for an IP SLAs operation. |
Step 10 |
history lives-kept lives Example:
|
(Optional) Sets the number of lives maintained in the history table for an IP SLAs operation. |
Step 11 |
owner owner-id Example:
|
(Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation. |
Step 12 |
paths-of-statistics-kept size Example:
|
(Optional) Sets the number of paths for which statistics are maintained per hour for an IP SLAs operation. |
Step 13 |
request-data-size bytes Example:
|
(Optional) Sets the protocol data size in the payload of an IP SLAs operation's request packet. |
Step 14 |
samples-of-history-kept samples Example:
|
(Optional) Sets the number of entries kept in the history table per bucket for an IP SLAs operation. |
Step 15 |
history statistics-distribution-interval milliseconds Example:
|
(Optional) Sets the time interval for each statistics distribution kept for an IP SLAs operation. |
Step 16 |
tag text Example:
|
(Optional) Creates a user-specified identifier for an IP SLAs operation. |
Step 17 |
threshold milliseconds Example:
|
(Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation. |
Step 18 |
timeout milliseconds Example:
|
(Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet. |
Step 19 |
tos number Example:
|
(Optional) Defines a type of service (ToS) byte in the IP header of an IP SLAs operation. |
Step 20 |
verify-data Example:
|
(Optional) Causes an IP SLAs operation to check each reply packet for data corruption. |
Step 21 |
vrf vrf-name Example:
|
(Optional) Allows monitoring within Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs) using IP SLAs operations. |
Step 22 |
end Example:
|
Exits to privileged EXEC mode. |
Command or Action | Purpose | |
---|---|---|
Step 1 |
enable Example:
|
Enables privileged EXEC mode.
|
Step 2 |
configure terminal Example:
|
Enters global configuration mode. |
Step 3 |
Enter one of the following commands:
Example:
|
|
Step 4 |
end Example:
|
Exits global configuration mode and returns to privileged EXEC mode. |
Step 5 |
show ip sla group schedule Example:
|
(Optional) Displays IP SLAs group schedule details. |
Step 6 |
show ip sla configuration Example:
|
(Optional) Displays IP SLAs configuration details. |
If the IP Service Level Agreements (SLAs) operation is not running and not generating statistics, add the verify-data command to the configuration (while configuring in IP SLA configuration mode) to enable data verification. When data verification is enabled, each operation response is checked for corruption. Use the verify-data command with caution during normal operations because it generates unnecessary overhead.
Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation.
To add proactive threshold conditions and reactive triggering for generating traps (or for starting another operation) to an IP Service Level Agreements (SLAs) operation, see the “Configuring Proactive Threshold Monitoring” section.
The following example shows how to configure an IP SLAs operation type of ICMP Path Echo that will start after 30 seconds and run for 5 minutes. The figure below depicts the ICMP Path Echo operation.
This example sets a Path Echo operation (ip sla 3) from Device B to Device A using IP/ICMP. The operation attempts to execute three times in 25 seconds (first attempt at 0 seconds).
ip sla 3
path-echo 172.29.139.134
frequency 10
tag SGN-RO
timeout 1000
ip sla schedule 3 life 25
Related Topic |
Document Title |
---|---|
Cisco IOS commands |
|
IP SLAs commands |
|
Information about Cisco IP SLAs |
“Cisco IOS IP SLAs Overview” module of the IP SLAs Configuration Guide |
Standard/RFC |
Title |
---|---|
RFC 862 |
Echo Protocol |
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: |
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. |
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.
Feature Name |
Releases |
Feature Information |
---|---|---|
IP SLAs ICMP Path Echo Operation |
12.2(31)SB2 12.2(33)SRB1 12.2(33)SXH 12.3(14)T Cisco IOS XE Release 2.1 15.0(1)S Cisco IOS XE 3.1.0SG |
The Cisco IOS IP SLAs Internet Control Message Protocol (ICMP) path echo operation allows you to measure end-to-end and hop-by-hop network response time between a Cisco device and other devices using IP. |
IP SLA 4.0 - IP v6 phase2 |
15.2(3)T Cisco IOS XE Release 3.7S 15.1(2)SG Cisco IOS XE Release 3.4SG |
Support was added for operability in IPv6 networks. The following commands are introduced or modified: path-echo (IP SLA), show ip sla configuration , show ip sla summary . |