Downloads |
 Feedback
|
Table Of Contents
type jitter dest-ipaddr (codec)
type pathEcho protocol ipIcmpEcho
tag (IP SLA)
To create a user-specified identifier for a Cisco IOS IP Service Level Agreements (SLAs) operation, use the tag (IP SLA) command in the appropriate submode of IP SLA configuration, auto IP SLA MPLS configuration, or IP SLA monitor configuration mode. To remove a tag from an operation, use the no form of this command.
tag text
no tag
Syntax Description
Defaults
No tag identifier is specified.
Command Modes
IP SLA Configuration
DHCP configuration (config-ip-sla-dhcp)
DLSw configuration (config-ip-sla-dlsw)
DNS configuration (config-ip-sla-dns)
Ethernet echo (config-ip-sla-ethernet-echo)
Ethernet jitter (config-ip-sla-ethernet-jitter)
FTP configuration (config-ip-sla-ftp)
HTTP configuration (config-ip-sla-http)
ICMP echo configuration (config-ip-sla-echo)
ICMP jitter configuration (config-ip-sla-icmpjitter)
ICMP path echo configuration (config-ip-sla-pathEcho)
ICMP path jitter configuration (config-ip-sla-pathJitter)
TCP connect configuration (config-ip-sla-tcp)
UDP echo configuration (config-ip-sla-udp)
UDP jitter configuration (config-ip-sla-jitter)
VoIP configuration (config-ip-sla-voip)Auto IP SLA MPLS Configuration
MPLS parameters configuration (config-auto-ip-sla-mpls-params)
IP SLA Auto Ethernet Configuration
Ethernet parameters configuration (config-ip-sla-ethernet-params)
IP SLA Monitor Configuration
DHCP configuration (config-sla-monitor-dhcp)
DLSw configuration (config-sla-monitor-dlsw)
DNS configuration (config-sla-monitor-dns)
FTP configuration (config-sla-monitor-ftp)
HTTP configuration (config-sla-monitor-http)
ICMP echo configuration (config-sla-monitor-echo)
ICMP path echo configuration (config-sla-monitor-pathEcho)
ICMP path jitter configuration (config-sla-monitor-pathJitter)
TCP connect configuration (config-sla-monitor-tcp)
UDP echo configuration (config-sla-monitor-udp)
UDP jitter configuration (config-sla-monitor-jitter)
VoIP configuration (config-sla-monitor-voip)
Note
The configuration mode varies depending on the Cisco IOS release you are running and the operation type configured. See the "Usage Guidelines" section for more information.
Command History
Usage Guidelines
An operation tag is normally used to logically link operations in a group.
Tags can be used to support automation (for example, by using the same tag for two different operations on two different routers echoing the same target).
IP SLAs Operation Configuration Dependence on Cisco IOS Release
The Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 27). Note that if you are configuring an IP SLAs LSP Health Monitor operation, see Table 28 for information on Cisco IOS release dependencies. You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation.
The configuration mode for the tag command varies depending on the Cisco IOS release you are running and the operation type configured. For example, if you are running Cisco IOS Release 12.4 and the ICMP echo operation type is configured, you would enter the tag command in ICMP echo configuration mode (config-sla-monitor-echo) within IP SLA monitor configuration mode.
Examples
In the following examples, IP SLAs ICMP echo operation 1 is tagged with the label testoperation. Note that the Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 27).
IP SLA Configuration
ip sla 1icmp-echo 172.16.1.176tag testoperation!ip sla schedule 1 life forever start-time nowIP SLA Monitor Configuration
ip sla monitor 1type echo protocol ipIcmpEcho 172.16.1.176tag testoperation!ip sla monitor schedule 1 life forever start-time nowRelated Commands
threshold (IP SLA)
To set the upper threshold value for calculating network monitoring statistics created by a Cisco IOS IP Service Level Agreements (SLAs) operation, use the threshold (IP SLA) command in the appropriate submode of IP SLA configuration, auto IP SLA MPLS configuration, or IP SLA monitor configuration mode. To return to the default value, use the no form of this command.
threshold milliseconds
no threshold
Syntax Description
milliseconds
Number of milliseconds required for a rising threshold to be declared. The default is 5000.
Defaults
5000 ms
Command Modes
IP SLA Configuration
DHCP configuration (config-ip-sla-dhcp)
DLSw configuration (config-ip-sla-dlsw)
DNS configuration (config-ip-sla-dns)
Ethernet echo (config-ip-sla-ethernet-echo)
Ethernet jitter (config-ip-sla-ethernet-jitter)
FTP configuration (config-ip-sla-ftp)
HTTP configuration (config-ip-sla-http)
ICMP echo configuration (config-ip-sla-echo)
ICMP jitter configuration (config-ip-sla-icmpjitter)
ICMP path echo configuration (config-ip-sla-pathEcho)
ICMP path jitter configuration (config-ip-sla-pathJitter)
TCP connect configuration (config-ip-sla-tcp)
UDP echo configuration (config-ip-sla-udp)
UDP jitter configuration (config-ip-sla-jitter)
VoIP configuration (config-ip-sla-voip)Auto IP SLA MPLS Configuration
MPLS parameters configuration (config-auto-ip-sla-mpls-params)
IP SLA Auto Ethernet Configuration
Ethernet parameters configuration (config-ip-sla-ethernet-params)
IP SLA Monitor Configuration
DHCP configuration (config-sla-monitor-dhcp)
DLSw configuration (config-sla-monitor-dlsw)
DNS configuration (config-sla-monitor-dns)
FTP configuration (config-sla-monitor-ftp)
HTTP configuration (config-sla-monitor-http)
ICMP echo configuration (config-sla-monitor-echo)
ICMP path echo configuration (config-sla-monitor-pathEcho)
ICMP path jitter configuration (config-sla-monitor-pathJitter)
TCP connect configuration (config-sla-monitor-tcp)
UDP echo configuration (config-sla-monitor-udp)
UDP jitter configuration (config-sla-monitor-jitter)
VoIP configuration (config-sla-monitor-voip)
Note
Command History
Usage Guidelines
The value specified for the threshold command must not exceed the value specified for the timeout command.
The threshold value configured by the threshold command is used only to calculate network monitoring statistics created by a Cisco IOS IP SLAs operation. This value is not used for generating Simple Network Management Protocol (SNMP) trap notifications. Use the ip sla reaction-configuration command in global configuration mode to configure the thresholds for generating IP SLAs SNMP trap notifications.
For the IP SLAs UDP jitter operation, the threshold command sets the upper threshold value for the average jitter calculation. For all other IP SLAs operations, the threshold command sets the upper threshold value for the round-trip time (RTT) measurement. IP SLAs will calculate the number of times the average jitter or RTT measurement exceeds the specified threshold value.
IP SLAs Operation Configuration Dependence on Cisco IOS Release
The Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 27). Note that if you are configuring an IP SLAs LSP Health Monitor operation, see Table 28 for information on Cisco IOS release dependencies. You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation.
The configuration mode for the threshold command varies depending on the Cisco IOS release you are running and the operation type configured. For example, if you are running Cisco IOS Release 12.4 and the ICMP echo operation type is configured, you would enter the threshold command in ICMP echo configuration mode (config-sla-monitor-echo) within IP SLA monitor configuration mode.
Examples
In the following examples, the threshold of IP SLAs ICMP echo operation 1 is set to 2500 ms. Note that the Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 27).
IP SLA Configuration
ip sla 1icmp-echo 172.16.1.176threshold 2500!ip sla schedule 1 start-time nowIP SLA Monitor Configuration
ip sla monitor 1type echo protocol ipIcmpEcho 172.16.1.176threshold 2500!ip sla monitor schedule 1 start-time nowRelated Commands
timeout (IP SLA)
To set the amount of time a Cisco IOS IP Service Level Agreements (SLAs) operation waits for a response from its request packet, use the timeout (IP SLA) command in the appropriate submode of IP SLA configuration, auto IP SLA MPLS configuration, or IP SLA monitor configuration mode. To return to the default value, use the no form of this command.
timeout milliseconds
no timeout
Syntax Description
Defaults
The default timeout value will vary depending on the type of IP SLAs operation you are configuring.
Command Modes
IP SLA Configuration
DHCP configuration (config-ip-sla-dhcp)
DLSw configuration (config-ip-sla-dlsw)
DNS configuration (config-ip-sla-dns)
Ethernet echo (config-ip-sla-ethernet-echo)
Ethernet jitter (config-ip-sla-ethernet-jitter)
FTP configuration (config-ip-sla-ftp)
HTTP configuration (config-ip-sla-http)
ICMP echo configuration (config-ip-sla-echo)
ICMP jitter configuration (config-ip-sla-icmpjitter)
ICMP path echo configuration (config-ip-sla-pathEcho)
ICMP path jitter configuration (config-ip-sla-pathJitter)
TCP connect configuration (config-ip-sla-tcp)
UDP echo configuration (config-ip-sla-udp)
UDP jitter configuration (config-ip-sla-jitter)
VoIP configuration (config-ip-sla-voip)Auto IP SLA MPLS Configuration
MPLS parameters configuration (config-auto-ip-sla-mpls-params)
IP SLA Auto Ethernet Configuration
Ethernet parameters configuration (config-ip-sla-ethernet-params)
IP SLA Monitor Configuration
DHCP configuration (config-sla-monitor-dhcp)
DLSw configuration (config-sla-monitor-dlsw)
DNS configuration (config-sla-monitor-dns)
FTP configuration (config-sla-monitor-ftp)
HTTP configuration (config-sla-monitor-http)
ICMP echo configuration (config-sla-monitor-echo)
ICMP path echo configuration (config-sla-monitor-pathEcho)
ICMP path jitter configuration (config-sla-monitor-pathJitter)
TCP connect configuration (config-sla-monitor-tcp)
UDP echo configuration (config-sla-monitor-udp)
UDP jitter configuration (config-sla-monitor-jitter)
VoIP configuration (config-sla-monitor-voip)
Note
Command History
Usage Guidelines
We recommend that the value of the milliseconds argument for the timeout command be based on the sum of both the maximum round-trip time (RTT) value for the packets and the processing time of the IP SLAs operation.
Use the timeout command to set how long the operation waits to receive a response from its request packet, and use the frequency command to set the rate at which the IP SLAs operation restarts. The value specified for the timeout command cannot be greater than the value specified for the frequency command.
IP SLAs Operation Configuration Dependence on Cisco IOS Release
The Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 27). Note that if you are configuring an IP SLAs LSP Health Monitor operation, see Table 28 for information on Cisco IOS release dependencies. You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation.
The configuration mode for the timeout command varies depending on the Cisco IOS release you are running and the operation type configured. For example, if you are running Cisco IOS Release 12.4 and the ICMP echo operation type is configured, you would enter the timeout command in ICMP echo configuration mode (config-sla-monitor-echo) within IP SLA monitor configuration mode.
Examples
In the following examples, the timeout value for IP SLAs ICMP echo operation 1 is set for 2500 ms. Note that the Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 27).
IP SLA Configuration
ip sla 1icmp-echo 172.16.1.176timeout 2500!ip sla schedule 1 start-time nowIP SLA Monitor Configuration
ip sla monitor 1type echo protocol ipIcmpEcho 172.16.1.176timeout 2500!ip sla monitor schedule 1 start-time nowRelated Commands
tos (IP SLA)
To define a type of service (ToS) byte in the IP header of a Cisco IOS IP Service Level Agreements (SLAs) operation, use the tos (IP SLA) command in the appropriate submode of IP SLA configuration or IP SLA monitor configuration mode. To return to the default value, use the no form of this command.
tos number
no tos
Syntax Description
Defaults
The default type-of-service value is 0.
Command Modes
IP SLA Configuration
HTTP configuration (config-ip-sla-http)
ICMP echo configuration (config-ip-sla-echo)
ICMP jitter configuration (config-ip-sla-icmpjitter)
ICMP path echo configuration (config-ip-sla-pathEcho)
ICMP path jitter configuration (config-ip-sla-pathJitter)
TCP connect configuration (config-ip-sla-tcp)
UDP echo configuration (config-ip-sla-udp)
UDP jitter configuration (config-ip-sla-jitter)IP SLA Monitor Configuration
HTTP configuration (config-sla-monitor-http)
ICMP echo configuration (config-sla-monitor-echo)
ICMP path echo configuration (config-sla-monitor-pathEcho)
ICMP path jitter configuration (config-sla-monitor-pathJitter)
TCP connect configuration (config-sla-monitor-tcp)
UDP echo configuration (config-sla-monitor-udp)
UDP jitter configuration (config-sla-monitor-jitter)
Note
Command History
12.0(3)T
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
The ToS value is an 8-bit field in IP headers. This field contains information such as precedence and ToS. This information is useful for policy routing and for features like Committed Access Rate (CAR), where routers examine ToS values.
When the type of service is defined for an operation, the IP SLAs Responder will reflect the ToS value it receives.
IP SLAs Operation Configuration Dependence on Cisco IOS Release
The Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 33). You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation.
The configuration mode for the tos command varies depending on the Cisco IOS release you are running (see Table 33) and the operation type configured. For example, if you are running Cisco IOS Release 12.4 and the ICMP echo operation type is configured, you would enter the tos command in ICMP echo configuration mode (config-sla-monitor-echo) within IP SLA monitor configuration mode.
Examples
In the following examples, IP SLAs operation 1 is configured as an ICMP echo operation with destination IP address 172.16.1.176. The ToS value is set to 0x80. Note that the Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 33).
IP SLA Configuration
ip sla 1icmp-echo 172.16.1.176tos 0x80!ip sla schedule 1 start-time nowIP SLA Monitor Configuration
ip sla monitor 1type echo protocol ipIcmpEcho 172.16.1.176tos 0x80!ip sla monitor schedule 1 start-time nowRelated Commands
track rtr
To track the state of a Cisco IOS IP Service Level Agreements (SLAs) operation and to enter tracking configuration mode, use the track rtr command in global configuration mode. To remove the tracking, use the no form of this command.
track object-number rtr operation-number {state | reachability}
no track object-number rtr operation-number {state | reachability}
Syntax Description
Defaults
IP SLAs tracking is disabled.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Every IP SLAs operation maintains an operation return-code value. This return code is interpreted by the tracking process. The return code may return OK, OverThreshold, and several other return codes. Different operations may have different return-code values, so only values common to all operation types are used.
Two aspects of an IP SLAs operation can be tracked: state and reachability. The difference between these aspects relates to the acceptance of the OverThreshold return code. Table 34 shows the state and reachability aspects of IP SLAs operations that can be tracked.
Table 34 Comparison of State and Reachability Operations
State
OK
(all other return codes)
Up
Down
Reachability
OK or over threshold
(all other return codes)
Up
Down
Examples
The following example shows how to configure the tracking process to track the state of IP SLAs operation 2:
track 1 rtr 2 stateThe following example shows how to configure the tracking process to track the reachability of IP SLAs operation 3:
track 2 rtr 3 reachabilityttl (IP SLA)
To specify the maximum hop count for an echo request packet of a Cisco IOS IP Service Level Agreements (SLAs) operation, use the ttl command in the appropriate submode of auto IP SLA MPLS configuration or IP SLA configuration mode. To return to the default value, use the no form of this command.
ttl time-to-live
no ttl
Syntax Description
Command Default
For IP SLAs LSP ping operations, the default time-to-live value is 255.
For IP SLAs LSP traceroute operations, the default time-to-live value is 30.Command Modes
Auto IP SLA MPLS Configuration
MPLS parameters configuration (config-auto-ip-sla-mpls-params)
IP SLA Configuration and IP SLA Monitor Configuration
LSP ping configuration (config-sla-monitor-lspPing)
LSP trace configuration (config-sla-monitor-lspTrace)
Note
Command History
Usage Guidelines
IP SLAs Operation Configuration Dependence on Cisco IOS Release
The Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 35). Note that if you are configuring an IP SLAs LSP Health Monitor operation, see Table 36 for information on Cisco IOS release dependencies. You must configure the type of IP SLAs operation (such as LSP ping) before you can configure any of the other parameters of the operation.
The configuration mode for the ttl command varies depending on the Cisco IOS release you are running and the operation type configured. For example, if you are running Cisco IOS Release 12.4(6)T and the LSP ping operation type is configured (without using the LSP Health Monitor), you would enter the ttl command in LSP ping configuration mode (config-sla-monitor-lspPing) within IP SLA configuration mode.
Examples
The following example shows how to configure operation parameters, proactive threshold monitoring, and scheduling options using the LSP Health Monitor. In this example, LSP Health Monitor operation 1 is configured to automatically create IP SLAs LSP ping operations for all Border Gateway Protocol (BGP) next hop neighbors in use by all VPN routing and forwarding (VRF) instances associated with the source Provider Edge (PE) router. The maximum hop count for echo request packets of IP SLAs operations created by LSP Health Monitor operation 1 is set to 200 hops.
mpls discovery vpn interval 60mpls discovery vpn next-hop!auto ip sla mpls-lsp-monitor 1type echo ipsla-vrf-alltimeout 1000scan-interval 1secondary-frequency connection-loss 10secondary-frequency timeout 10delete-scan-factor 2ttl 200!auto ip sla mpls-lsp-monitor reaction-configuration 1 react connectionLoss threshold-type consecutive 3 action-type trapOnlyauto ip sla mpls-lsp-monitor reaction-configuration 1 react timeout threshold-type consecutive 3 action-type trapOnlyip sla logging traps!auto ip sla mpls-lsp-monitor schedule 1 schedule-period 60 start-time nowRelated Commands
type dhcp
Note
To configure a Cisco IOS IP Service Level Agreements (SLAs) Dynamic Host Configuration Protocol (DHCP) operation, use the type dhcp command in IP SLA monitor configuration mode.
type dhcp [source-ipaddr {ip-address | hostname}] [dest-ipaddr {ip-address | hostname}] [option 82 [circuit-id circuit-id] [remote-id remote-id] [subnet-mask subnet-mask]]
Syntax Description
Defaults
No IP SLAs operation type is configured for the operation being configured.
Command Modes
IP SLA monitor configuration (config-sla-monitor)
Command History
Usage Guidelines
If the source IP address is configured, then packets will be sent with that source address.
You may configure the ip dhcp-server global configuration command to identify the DHCP server that the DHCP operation will measure. If the target IP address is configured, then only that device will be measured. If the ip dhcp-server command is not configured and the target IP address is not configured, then DHCP discover packets will be sent on every available IP interface.
Option 82 is called the Relay Agent Information option and is inserted by the DHCP relay agent when client-originated DHCP packets are forwarded to a DHCP server. Servers recognizing the Relay Agent Information option may use the information to implement IP address or other parameter assignment policies. The DHCP server echoes the option back verbatim to the relay agent in server-to-client replies, and the relay agent strips the option before forwarding the reply to the client.
The Relay Agent Information option is organized as a single DHCP option that contains one or more suboptions that convey information known by the relay agent. The initial suboptions are defined for a relay agent that is colocated in a public circuit access unit. These suboptions are as follows: a circuit ID for the incoming circuit, a remote ID that provides a trusted identifier for the remote high-speed modem, and a subnet mask designation for the logical IP subnet from which the relay agent received the client DHCP packet.
Note
You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation. To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla monitor global configuration command) and then reconfigure the operation with the new operation type.
Examples
In the following example, IP SLAs operation number 4 is configured as a DHCP operation enabled for DHCP server 172.16.20.3.
ip sla monitor 4type dhcp option 82 circuit-id 10005A6F1234ip dhcp-server 172.16.20.3!ip sla monitor schedule 4 start-time nowRelated Commands
type dlsw peer-ipaddr
Note
To configure a Cisco IOS IP Service Level Agreements (SLAs) Data Link Switching Plus (DLSw+) operation, use the type dlsw peer-ipaddr command in IP SLA monitor configuration mode.
type dlsw peer-ipaddr ip-address
Syntax Description
Defaults
No IP SLAs operation type is configured for the operation being configured.
Command Modes
IP SLA monitor configuration (config-sla-monitor)
Command History
Usage Guidelines
To configure an IP SLAs DLSw+ operation, the DLSw feature must be configured on the local and target routers.
For DLSw+ operations, the default request packet data size is 0 bytes (use the request-data-size command to modify this value) and the default amount of time the operation waits for a response from the request packet is 30 seconds (use the timeout command to modify this value).
You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation. To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla monitor global configuration command) and then reconfigure the operation with the new operation type.
Examples
In the following example, IP SLAs operation number 10 is configured as a DLSw+ operation enabled for remote peer IP address 172.21.27.11. The data size is 15 bytes.
ip sla monitor 10type dlsw peer-ipaddr 172.21.27.11request-data-size 15!ip sla monitor schedule 10 start-time nowRelated Commands
type dns target-addr
Note
To configure a Cisco IOS IP Service Level Agreements (SLAs) Domain Name System (DNS) operation, use the type dns target-addr command in IP SLA monitor configuration mode.
type dns target-addr {target-hostname | target-ip-address} name-server ip-address [source-ipaddr {ip-address | hostname} source-port port-number]
Syntax Description
Defaults
No IP SLAs operation type is configured for the operation being configured.
Command Modes
IP SLA monitor configuration (config-sla-monitor)
Command History
Usage Guidelines
You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation. To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla monitor global configuration command) and then reconfigure the operation with the new operation type.
Examples
In the following example, IP SLAs operation 7 is configured as a DNS operation using the target IP address 172.20.2.132.
ip sla monitor 7type dns target-addr host1 name-server 172.20.2.132!ip sla monitor schedule 7 start-time nowRelated Commands
ip sla monitor
Begins configuration for an IP SLAs operation and enters IP SLA monitor configuration mode.
type echo (MPLS)
To configure Cisco IOS IP Service Level Agreements (SLAs) label switched path (LSP) ping operations using the LSP Health Monitor, use the type echo command in auto IP SLA MPLS configuration mode.
type echo [ipsla-vrf-all | vrf vpn-name]
Syntax Description
Command Default
No IP SLAs operation type is configured for the operation being configured.
Command Modes
Auto IP SLA MPLS configuration (config-auto-ip-sla-mpls)
Command History
Usage Guidelines
You must configure the type of LSP Health Monitor operation (such as LSP ping) before you can configure any of the other parameters of the operation.
Note
Examples
The following example shows how to configure operation parameters, proactive threshold monitoring, and scheduling options using the LSP Health Monitor. In this example, LSP Health Monitor operation 1 is configured to automatically create IP SLAs LSP ping operations for all Border Gateway Protocol (BGP) next hop neighbors in use by all VPN routing and forwarding (VRF) instances associated with the source PE router.
mpls discovery vpn interval 60mpls discovery vpn next-hop!auto ip sla mpls-lsp-monitor 1type echo ipsla-vrf-alltimeout 1000scan-interval 1secondary-frequency connection-loss 10secondary-frequency timeout 10delete-scan-factor 2!auto ip sla mpls-lsp-monitor reaction-configuration 1 react connectionLoss threshold-type consecutive 3 action-type trapOnlyauto ip sla mpls-lsp-monitor reaction-configuration 1 react timeout threshold-type consecutive 3 action-type trapOnlyip sla logging traps!auto ip sla mpls-lsp-monitor schedule 1 schedule-period 60 start-time nowRelated Commands
auto ip sla mpls-lsp-monitor
Begins configuration for an IP SLAs LSP Health Monitor operation and enters auto IP SLA MPLS configuration mode.
type echo protocol ipIcmpEcho
Note
To configure an IP Service Level Agreements (SLAs) Internet Control Message Protocol (ICMP) echo operation, use the type echo protocol ipIcmpEcho command in IP SLA monitor configuration mode.
type echo protocol ipIcmpEcho {destination-ip-address | destination-hostname} [source-ipaddr {ip-address | hostname} | source-interface interface-name]
Syntax Description
Defaults
No IP SLAs operation type is configured for the operation being configured.
Command Modes
IP SLA monitor configuration (config-sla-monitor)
Command History
Usage Guidelines
The default request packet data size for an ICMP echo operation is 28 bytes. Use the request-data-size command to modify this value. This data size is the payload portion of the ICMP packet, which makes a 64-byte IP packet.
You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation. To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla monitor global configuration command) and then reconfigure the operation with the new operation type.
Examples
In the following example, IP SLAs operation 10 is created and configured as an echo operation using the IP/ICMP protocol and the destination IP address 172.16.1.175.
ip sla monitor 10type echo protocol ipIcmpEcho 172.16.1.175!ip sla monitor schedule 10 start-time nowRelated Commands
ip sla monitor
Begins configuration for an IP SLAs operation and enters IP SLA monitor configuration mode.
type ftp operation get url
Note
To configure a Cisco IOS IP Service Level Agreements (SLAs) File Transfer Protocol (FTP) GET operation, use the type ftp operation get url command in IP SLA monitor configuration mode.
type ftp operation get url url [source-ipaddr {ip-address | hostname}] [mode {passive | active}
Syntax Description
Defaults
No IP SLAs operation type is configured for the operation being configured.
Command Modes
IP SLA monitor configuration (config-sla-monitor)
Command History
Usage Guidelines
The url argument must be in one of the following formats:
•
•
If the username and password are not specified, the defaults are anonymous and test, respectively.
You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation. To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla monitor global configuration command) and then reconfigure the operation with the new operation type.
Examples
In the following example, an FTP operation is configured. User1 is the username and password1 is the password; host1 is the host and file1 is the filename.
ip sla monitor 3type ftp operation get url ftp://user1:password1@host1/file1!ip sla monitor schedule 3 start-time nowRelated Commands
ip sla monitor
Begins configuration for an IP SLAs operation and enters IP SLA monitor configuration mode.
type http operation
Note
To configure a Cisco IOS IP Service Level Agreements (SLAs) HTTP operation, use the type http operation command in IP SLA monitor configuration mode.
type http operation {get | raw} url url [name-server ip-address] [version version-number] [source-ipaddr {ip-address | hostname}] [source-port port-number] [cache {enable | disable}] [proxy proxy-url]
Syntax Description
Defaults
No IP SLAs operation type is configured for the operation being configured.
Command Modes
IP SLA monitor configuration (config-sla-monitor)
Command History
Usage Guidelines
You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation. To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla monitor global configuration command) and then reconfigure the operation with the new operation type.
Examples
In the following example, IP SLAs HTTP operation 6 is configured as an HTTP RAW operation. The destination URL is http://www.cisco.com.
ip sla monitor 6type http operation raw url http://www.cisco.comhttp-raw-requestGET /index.html HTTP/1.0\r\n\r\n!ip sla monitor schedule 6 start-time nowRelated Commands
ip sla monitor
Begins configuration for an IP SLAs operation and enters IP SLA monitor configuration mode.
type jitter dest-ipaddr
Note
To configure a Cisco IOS IP Service Level Agreements (SLAs) User Datagram Protocol (UDP) jitter operation, use the type jitter dest-ipaddr command in IP SLA monitor configuration mode.
type jitter dest-ipaddr {destination-ip-address | destination-hostname} dest-port port-number [source-ipaddr {ip-address | hostname}] [source-port port-number] [control {enable | disable}] [num-packets number-of-packets] [interval interpacket-interval]
Syntax Description
Defaults
No IP SLAs operation type is configured for the operation being configured.
Command Modes
IP SLA monitor configuration (config-sla-monitor)
Command History
Usage Guidelines
The type jitter dest-ipaddr command configures an IP SLAs UDP Plus operation. The UDP Plus operation is a superset of the UDP echo operation. In addition to measuring UDP round-trip time, the UDP Plus operation measures per-direction packet loss and jitter. Jitter is interpacket delay variance. Jitter statistics are useful for analyzing traffic in a Voice over IP (VoIP) network.
You must enable the IP SLAs Responder on the target router before you can configure a UDP jitter operation. Prior to sending an operation packet to the target router, IP SLAs sends a control message to the IP SLAs Responder to enable the destination port.
The default request packet data size for an IP SLAs UDP jitter operation is 32 bytes. Use the request-data-size command to modify this value.
Note
IP SLAs VoIP UDP Jitter (codec) Operation
When you specify the codec in the command syntax of the type jitter dest-ipaddr command, the standard configuration options are replaced with codec-specific keywords and arguments. The codec-specific command syntax is documented separately from the command syntax for the standard implementation of the type jitter dest-ipaddr command. For information about the codec-specific command syntax, see the documentation for the type jitter dest-ipaddr (codec) command.
Examples
In the following example, operation 6 is configured as a UDP jitter operation with the destination IP address 172.30.125.15, the destination port number 2000, 20 packets, and an interpacket interval of 20 ms.
ip sla monitor 6type jitter dest-ipaddr 172.30.125.15 dest-port 2000 num-packets 20 interval 20!ip sla monitor schedule 6 start-time nowRelated Commands
type jitter dest-ipaddr (codec)
Note
To configure a Cisco IOS IP Service Level Agreements (SLAs) User Datagram Protocol (UDP) jitter operation that returns Voice over IP (VoIP) scores, use the type jitter dest-ipaddr command in IP SLA monitor configuration mode.
type jitter dest-ipaddr {destination-ip-address | destination-hostname} dest-port port-number codec codec-type [codec-numpackets number-of-packets] [codec-size number-of-bytes] [codec-interval milliseconds] [advantage-factor value] [source-ipaddr {ip-address | hostname}] [source-port port-number] [control {enable | disable}]
Syntax Description
destination-ip-address | destination-hostname
Specifies the destination IP address or hostname.
dest-port port-number
Specifies the destination port number. For UDP jitter (codec) operations, the port number should be an even number in the range of 16384 to 32766 or 49152 to 65534.
codec codec-type
Enables the generation of estimated voice-quality scores in the form of Calculated Planning Impairment Factor (ICPIF) and Mean Opinion Score (MOS) values. The codec type should match the encoding algorithm you are using for VoIP transmissions.
The following codec-type keywords are available:
•
•
•
Configuring the codec type sets default values for the variables codec-numpackets, codec-size, and codec-interval in this command. See Table 37 for details.
codec-numpackets number-of-packets
(Optional) Specifies the number of packets to be transmitted per operation. The valid range is from 1 to 60000 packets. The default is 1000 packets.
codec-size number-of-bytes
(Optional) Specifies the number of bytes in each packet transmitted. (Also called the payload size or request size.) The valid range is from 16 to 1500 packets. The default varies by codec (see Table 37).
codec-interval milliseconds
Specifies the interval (delay) between packets that should be used for the operation, in milliseconds (ms). The valid range is from 1 to 60000 ms. By default, packets are sent 20 ms apart.
advantage-factor value
Specifies the expectation factor to be used for ICPIF calculations. This value is subtracted from the measured impairments to yield the final ICPIF value (and corresponding MOS value). See the "Usage Guidelines" section for recommended values. The valid range is from 0 to 20. The default is 0.
source-ipaddr {ip-address | hostname}
(Optional) Specifies the source IP address or hostname. When a source IP address or hostname is not specified, IP SLAs chooses the IP address nearest to the destination.
source-port port-number
(Optional) Specifies the source port number. When a port number is not specified, IP SLAs chooses an available port.
control {enable | disable}
(Optional) Enables or disables the sending of IP SLAs control messages to the IP SLAs Responder.
By default, IP SLAs control messages are sent to the destination device to establish a connection with the IP SLAs Responder.
Note
Defaults
No IP SLAs operation type is associated with the operation number being configured.
Command Modes
IP SLA monitor configuration (config-sla-monitor)
Command History
Usage Guidelines
When you specify the codec in the command syntax of the type jitter dest-ipaddr command, the standard configuration options are replaced with codec-specific keywords and arguments. The codec-specific command syntax is documented separately from the command syntax for the standard implementation of the type jitter dest-ipaddr command. For information about the command syntax for the standard implementation, see the documentation for the type jitter dest-ipaddr command.
You must enable the IP SLAs Responder on the target router before you can configure a UDP jitter (codec) operation. Prior to sending an operation packet to the target router, IP SLAs sends a control message to the IP SLAs Responder to enable the destination port.
Note
IP SLAs VoIP UDP Jitter (codec) Statistics
The IP SLAs UDP jitter operation computes statistics by sending n UDP packets, each of size s, sent t milliseconds apart, from a given source router to a given target router, at a given frequency f.
To generate MOS and ICPIF scores, you specify the codec type used for the connection when configuring the UDP jitter operation. Based on the type of codec you configure for the operation, the number of packets (n), the size of each payload (s), the inter-packet time interval (t), and the operational frequency (f) will be auto-configured with default values. (See Table 37 for specific information.) However, you are given the option, if needed, to manually configure these parameters in the syntax of the type jitter dest-ipaddr (codec) command.
Table 37 shows the default parameters that are configured for the operation by codec.
Table 37 Default UDP Jitter Operation Parameters by Codec
G.711 mu-law (g711ulaw)
1000
160 bytes
20 ms
Once every 60 seconds
G.711 a-law (g711alaw)
1000
160 bytes
20 ms
Once every 60 seconds
G.729A (g729a)
1000
20 bytes
20 ms
Once every 60 seconds
1 The actual data size of each request packet will contain an additional 12 bytes of Real-Time Transport Protocol (RTP) header data in order to simulate the RTP/UDP/IP/Layer 2 protocol stack.
For example, if you configure the UDP jitter operation to use the characteristics for the g711ulaw codec, by default an operation will be sent once a minute (f). Each operation would consist of 1000 packets (n), with each packet containing 160 bytes (plus 12 header bytes) of synthetic data (s), sent 20 ms apart (t).
The advantage-factor value keyword and argument allow you to specify an access Advantage Factor (also called the Expectation Factor). Table 38, adapted from ITU-T Rec. G.113, defines a set of provisional maximum values for Advantage Factors in terms of the service provided.
These values are only suggestions. To be meaningful, the use of the Advantage/Expectation factor (A) and its selected value in a specific application should be used consistently in any planning model you adopt. However, the values in Table 38 should be considered as the absolute upper limits for A. The default Advantage/Expectation factor for IP SLAs UDP jitter operations is always zero.
Examples
In the following example, IP SLAs operation 10 is configured as a UDP jitter (codec) operation with the destination IP address 209.165.200.225 and the destination port number 3000. The operation is configured to use the characteristics of the G.711 a-law codec, which means the operation will consist of 1000 packets, each of 172 bytes (160 plus 12 header bytes), sent 20 ms apart. The default value for the Advantage Factor and operation frequency is used.
ip sla monitor 10type jitter dest-ipaddr 209.165.200.225 dest-port 3000 codec g711alaw!ip sla monitor schedule 10 start-time nowRelated Commands
ip sla monitor
Begins configuration for an IP SLAs operation and enters IP SLA monitor configuration mode.
type jitter dest-ipaddr
Configures an IP SLAs UDP jitter operation.
type mpls lsp ping ipv4
Note
To manually configure an individual Cisco IOS IP Service Level Agreements (SLAs) label switched path (LSP) ping IPv4 operation, use the type mpls lsp ping ipv4 command in IP SLA monitor configuration mode.
type mpls lsp ping ipv4 destination-address destination-mask [force-explicit-null] [lsp-selector ip-address] [src-ip-addr source-address] [reply {dscp dscp-value | mode {ipv4 | router-alert}}]
Syntax Description
Command Default
No IP SLAs operation type is configured for the operation being configured.
Command Modes
IP SLA monitor configuration (config-sla-monitor)
Command History
Usage Guidelines
The lsp-selector keyword is used to force an IP SLAs operation to use a specific LSP to obtain its response time measurement. This option is useful if there are multiple equal cost paths between Provider Edge (PE) routers.
You must configure the type of IP SLAs operation (such as LSP ping) before you can configure any of the other parameters of the operation. To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla monitor global configuration command) and then reconfigure the operation with the new operation type.
Note
Examples
The following examples show how to manually configure operation parameters, proactive threshold monitoring, and scheduling options for IP SLAs LSP ping operation 1.
ip sla monitor 1type mpls lsp ping ipv4 192.168.1.4 255.255.255.255 lsp-selector 127.1.1.1frequency 120secondary-frequency connection-loss 30secondary-frequency timeout 30!ip sla monitor reaction-configuration 1 react connectionLoss threshold-type consecutive 3 action-type trapOnlyip sla monitor reaction-configuration 1 react timeout threshold-type consecutive 3 action-type trapOnlyip sla monitor logging traps!ip sla monitor schedule 1 start-time now life foreverRelated Commands
ip sla monitor
Begins configuration for an IP SLAs operation and enters IP SLA monitor configuration mode.
type mpls lsp trace ipv4
Note
To manually configure an individual Cisco IOS IP Service Level Agreements (SLAs) label switched path (LSP) traceroute IPv4 operation, use the type mpls lsp trace ipv4 command in IP SLA monitor configuration mode.
type mpls lsp trace ipv4 destination-address destination-mask [force-explicit-null] [lsp-selector ip-address] [src-ip-addr source-address] [reply {dscp dscp-value | mode {ipv4 | router-alert}}]
Syntax Description
Command Default
No IP SLAs operation type is configured for the operation being configured.
Command Modes
IP SLA monitor configuration (config-sla-monitor)
Command History
Usage Guidelines
The lsp-selector keyword is used to force an IP SLAs operation to use a specific LSP to obtain its response time measurement. This option is useful if there are multiple equal cost paths between Provider Edge (PE) routers.
You must configure the type of IP SLAs operation (such as LSP ping) before you can configure any of the other parameters of the operation. To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla monitor global configuration command) and then reconfigure the operation with the new operation type.
Note
Examples
The following examples show how to manually configure operation parameters, proactive threshold monitoring, and scheduling options for IP SLAs LSP traceroute operation 1.
ip sla monitor 1type mpls lsp trace ipv4 192.168.1.4 255.255.255.255 lsp-selector 127.1.1.1frequency 120secondary-frequency connection-loss 30secondary-frequency timeout 30!ip sla monitor reaction-configuration 1 react connectionLoss threshold-type consecutive 3 action-type trapOnlyip sla monitor reaction-configuration 1 react timeout threshold-type consecutive 3 action-type trapOnlyip sla monitor logging traps!ip sla monitor schedule 1 start-time now life foreverRelated Commands
ip sla monitor
Begins configuration for an IP SLAs operation and enters IP SLA monitor configuration mode.
type pathEcho (MPLS)
To configure Cisco IOS IP Service Level Agreements (SLAs) label switched path (LSP) LSP traceroute operations using the LSP Health Monitor, use the type pathEcho command in auto IP SLA MPLS configuration mode.
type pathEcho [ipsla-vrf-all | vrf vpn-name]
Syntax Description
Command Default
No IP SLAs operation type is configured for the operation being configured.
Command Modes
Auto IP SLA MPLS configuration (config-auto-ip-sla-mpls)
Command History
Usage Guidelines
You must configure the type of LSP Health Monitor operation (such as LSP ping) before you can configure any of the other parameters of the operation.
You must configure the type of IP SLAs operation (such as LSP ping) before you can configure any of the other parameters of the operation. To change the operation type of an existing LSP Health Monitor operation, you must first delete the operation (using the no auto ip sla mpls-lsp-monitor global configuration command) and then reconfigure the operation with the new operation type.
Note
Note
Examples
The following example shows how to configure operation parameters, proactive threshold monitoring, and scheduling options using the LSP Health Monitor. In this example, LSP Health Monitor operation 1 is configured to automatically create IP SLAs LSP traceroute operations for all BGP next hop neighbors in use by all VRFs associated with the source PE router.
mpls discovery vpn interval 60mpls discovery vpn next-hop!auto ip sla mpls-lsp-monitor 1type pathEcho ipsla-vrf-alltimeout 1000scan-interval 1secondary-frequency connection-loss 10secondary-frequency timeout 10!auto ip sla mpls-lsp-monitor reaction-configuration 1 react connectionLoss threshold-type consecutive 3 action-type trapOnlyauto ip sla mpls-lsp-monitor reaction-configuration 1 react timeout threshold-type consecutive 3 action-type trapOnlyip sla logging traps!auto ip sla mpls-lsp-monitor schedule 1 schedule-period 60 start-time nowRelated Commands
auto ip sla mpls-lsp-monitor
Begins configuration for an IP SLAs LSP Health Monitor operation and enters auto IP SLA MPLS configuration mode.
type pathEcho protocol ipIcmpEcho
Note
To configure a Cisco IOS IP Service Level Agreements (SLAs) Internet Control Message Protocol (ICMP) path echo operation, use the type pathEcho protocol ipIcmpEcho command in IP SLA monitor configuration mode.
type pathEcho protocol ipIcmpEcho {destination-ip-address | destination-hostname} [source-ipaddr {ip-address | hostname}]
Syntax Description
Defaults
No IP SLAs operation type is configured for the operation being configured.
Command Modes
IP SLA monitor configuration (config-sla-monitor)
Command History
Usage Guidelines
You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation. To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla monitor global configuration command) and then reconfigure the operation with the new operation type.
Examples
In the following example, IP SLAs operation 10 is configured as an ICMP path echo operation using the IP/ICMP protocol and the destination IP address 172.16.1.175.
ip sla monitor 10type pathEcho protocol ipIcmpEcho 172.16.1.175!ip sla monitor schedule 10 start-time nowRelated Commands
ip sla monitor
Begins configuration for an IP SLAs operation and enters IP SLA monitor configuration mode.
type pathJitter dest-ipaddr
Note
To configure a Cisco IOS IP Service Level Agreements (SLAs) Internet Control Message Protocol (ICMP) path jitter operation, use the type pathJitter dest-ipaddr command in IP SLA monitor configuration mode.
type pathJitter dest-ipaddr {destination-ip-address | destination-hostname} [source-ipaddr {ip-address | hostname}] [num-packets packet-number] [interval milliseconds] [targetOnly]
Syntax Description
Defaults
No IP SLAs operation type is configured for the operation number being configured.
Command Modes
IP SLA monitor configuration (config-sla-monitor)
Command History
Usage Guidelines
If the targetOnly keyword is used, the ICMP path jitter operation will send echoes to the destination only (the path from the source to the destination is not traced).
If the targetOnly keyword is not used, the IP SLAs ICMP path jitter operation will trace a "hop-by-hop" IP path from the source to the destination and then send a user-specified number of test packets to each hop along the traced path at user-specified time intervals.
You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation. To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla monitor global configuration command) and then reconfigure the operation with the new operation type.
Examples
The following example shows how to enable the ICMP path jitter operation to trace the IP path to the destination 172.69.5.6 and send 50 test packets to each hop with an interval of 30 ms between each test packet.
ip sla monitor 2type pathJitter dest-ipaddress 172.69.5.6 num-packets 50 interval 30!ip sla monitor schedule 2 start-time nowRelated Commands
ip sla monitor
Begins configuration for an IP SLAs operation and enters IP SLA monitor configuration mode.
type tcpConnect dest-ipaddr
Note
To define a Cisco IOS IP Service Level Agreements (SLAs) Transmission Control Protocol (TCP) connection operation, use the type tcpConnect dest-ipaddr command in IP SLA monitor configuration mode.
type tcpConnect dest-ipaddr {destination-ip-address | destination-hostname} dest-port port-number [source-ipaddr {ip-address | hostname} source-port port-number] [control {enable | disable}]
Syntax Description
Defaults
No IP SLAs operation type is associated with the operation number being configured.
Command Modes
IP SLA monitor configuration (config-sla-monitor)
Command History
Usage Guidelines
The TCP connection operation is used to discover the time required to connect to the target device. This operation can be used to test virtual circuit availability or application availability. If the target is a Cisco router, then IP SLAs makes a TCP connection to any port number specified by the user. If the destination is a non-Cisco IP host, then the user must specify a known target port number (for example, 21 for FTP, 23 for Telnet, or 80 for HTTP server). This operation is useful in testing Telnet or HTTP connection times.
You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation. To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla monitor global configuration command) and then reconfigure the operation with the new operation type.
Examples
In the following example, IP SLAs operation 11 is configured as a TCP connection operation using the destination IP address 172.16.1.175 and the destination port 2400.
ip sla monitor 11type tcpConnect dest-ipaddr 172.16.1.175 dest-port 2400!ip sla monitor schedule 11 start-time now life foreverRelated Commands
ip sla monitor
Begins configuration for an IP SLAs operation and enters IP SLA monitor configuration mode.
type udpEcho dest-ipaddr
Note
To define a Cisco IOS IP Service Level Agreements (SLAs) User Datagram Protocol (UDP) echo operation, use the type udpEcho dest-ipaddr command in IP SLA monitor configuration mode.
type udpEcho dest-ipaddr {ip-address | hostname} dest-port port-number [source-ipaddr {ip-address | hostname} source-port port-number] [control {enable | disable}]
Syntax Description
Defaults
No IP SLAs operation type is associated with the operation number being configured.
Command Modes
IP SLA monitor configuration (config-sla-monitor)
Command History
Usage Guidelines
You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation. To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla monitor global configuration command) and then reconfigure the operation with the new operation type.
Examples
In the following example, IP SLAs operation 12 is configured as a UDP echo operation using the destination IP address 172.16.1.175 and destination port 2400.
ip sla monitor 12type udpEcho dest-ipaddr 172.16.1.175 dest-port 2400!ip sla monitor schedule 12 start-time now life foreverRelated Commands
ip sla monitor
Begins configuration for an IP SLAs operation and enters IP SLA monitor configuration mode.
verify-data (IP SLA)
To cause a Cisco IOS IP Service Level Agreements (SLAs) operation to check each reply packet for data corruption, use the verify-data (IP SLA) command in the appropriate submode of IP SLA configuration or IP SLA monitor configuration mode. To return to the default value, use the no form of this command.
verify-data
no verify-data
Syntax Description
This command has no arguments or keywords.
Defaults
Data is not checked for corruption.
Command Modes
IP SLA Configuration
ICMP echo configuration (config-ip-sla-echo)
ICMP path echo configuration (config-ip-sla-pathEcho)
ICMP path jitter configuration (config-ip-sla-pathJitter)
UDP echo configuration (config-ip-sla-udp)
UDP jitter configuration (config-ip-sla-jitter)IP SLA Monitor Configuration
ICMP echo configuration (config-sla-monitor-echo)
ICMP path echo configuration (config-sla-monitor-pathEcho)
ICMP path jitter configuration (config-sla-monitor-pathJitter)
UDP echo configuration (config-sla-monitor-udp)
UDP jitter configuration (config-sla-monitor-jitter)
Note
Command History
11.2
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Use the verify-data (IP SLA) command only when data corruption may be an issue.
Note
IP SLAs Operation Configuration Dependence on Cisco IOS Release
The Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 39). You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation.
The configuration mode for the verify-data command varies depending on the Cisco IOS release you are running (see Table 39) and the operation type configured. For example, if you are running Cisco IOS Release 12.4 and the ICMP echo operation type is configured, you would enter the verify-data command in ICMP echo configuration mode (config-sla-monitor-echo) within IP SLA monitor configuration mode.
Examples
In the following examples, IP SLAs ICMP echo operation 5 is configured to verify each reply packet for data corruption. Note that the Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 39).
IP SLA Configuration
ip sla 5icmp-echo 172.16.1.174verify-data!ip sla schedule 5 start-time now life foreverIP SLA Monitor Configuration
ip sla monitor 5type echo protocol ipIcmpEcho 172.16.1.174verify-data!ip sla monitor schedule 5 start-time now life foreverRelated Commands
vrf (IP SLA)
To allow monitoring within Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs) using Cisco IOS IP Service Level Agreements (SLAs) operations, use the vrf (IP SLA) command in the appropriate submode of IP SLA configuration or IP SLA monitor configuration mode.
vrf vrf-name
Syntax Description
Defaults
The MPLS VPN parameter is not configured for the IP SLAs operation.
Command Modes
IP SLA Configuration
ICMP echo configuration (config-ip-sla-echo)
ICMP jitter configuration (config-ip-sla-icmpjitter)
ICMP path echo configuration (config-ip-sla-pathEcho)
ICMP path jitter configuration (config-ip-sla-pathJitter)
UDP echo configuration (config-ip-sla-udp)
UDP jitter configuration (config-ip-sla-jitter)IP SLA Monitor Configuration
ICMP echo configuration (config-sla-monitor-echo)
ICMP path echo configuration (config-sla-monitor-pathEcho)
ICMP path jitter configuration (config-sla-monitor-pathJitter)
UDP echo configuration (config-sla-monitor-udp)
UDP jitter configuration (config-sla-monitor-jitter)
Note
Command History
Usage Guidelines
A VPN is commonly identified using the VPN routing and forwarding (VRF) name. If the vrf vrf-name command is configured for an IP SLAs operation, IP SLAs uses the vrf-name value to identify the VPN for this operation. This command should be used only if it is necessary to measure the response time over the VPN tunnel.
This command is supported only for the following operation types:
•
•
•
•
•
•
IP SLAs Operation Configuration Dependence on Cisco IOS Release
The Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 40). You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation.
The configuration mode for the vrf (IP SLA) command varies depending on the Cisco IOS release you are running (see Table 40) and the operation type configured. For example, if you are running Cisco IOS Release 12.4 and the ICMP echo operation type is configured, you would enter the vrf (IP SLA) command in ICMP echo configuration mode (config-sla-monitor-echo) within IP SLA monitor configuration mode.
Examples
The following examples illustrate how to configure an IP SLAs ICMP echo operation for an MPLS VPN. These examples show how test traffic can be sent in an already existing VPN tunnel between two endpoints. Note that the Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 40).
Note
IP SLA Configuration
ip sla 1icmp-echo 10.1.1.1vrf vpn1!ip sla schedule 1 start nowIP SLA Monitor Configuration
ip sla monitor 1type echo protocol ipIcmpEcho 10.1.1.1vrf vpn1!ip sla monitor schedule 1 start nowRelated Commands
