Table Of Contents
auto ip sla mpls-lsp-monitor reaction-configuration
auto ip sla mpls-lsp-monitor reset
auto ip sla mpls-lsp-monitor schedule
distributions-of-statistics-kept
history distributions-of-statistics-kept
history hours-of-statistics-kept
history statistics-distribution-interval
hours-of-statistics-kept (LSP discovery)
Cisco IOS IP SLAs Commands
access-list (IP SLA)
To specify the access list to apply to a Cisco IOS IP Service Level Agreements (SLAs) label switched path (LSP) Health Monitor operation, use the access-list command in auto IP SLA MPLS parameters configuration mode. To remove the access list, use the no form of this command.
access-list access-list-number
no access-list access-list-number
Syntax Description
access-list-number
Number of an access list. This value is a decimal number from 1 to 99 or from 1300 to 1999.
Command Default
No access list is specified.
Command Modes
Auto IP SLA MPLS parameters configuration (config-auto-ip-sla-mpls-params)
Command History
Usage Guidelines
Standard IP access lists can be configured (using the access-list [IP standard] command in global configuration mode) to restrict the number of IP SLAs operations that are automatically created by the IP SLAs LSP Health Monitor. When the IP SLAs access list parameter is configured, the list of Border Gateway Protocol (BGP) next hop neighbors discovered by the LSP Health Monitor is filtered based on the conditions defined by the associated standard IP access list. In other words, the LSP Health Monitor will automatically create IP SLAs operations only for those BGP next hop neighbors with source addresses that satisfy the criteria permitted by the standard IP access list.
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 BGP next hop neighbors in use by all VPN routing and forwarding (VRF) instances associated with the source Provider Edge (PE) router. Standard IP access list 10 is specified to restrict the number of IP SLAs operations to be created by LSP Health Monitor operation 1.
!Configure standard IP access list in global configuration modeaccess-list 10 permit 10.10.10.8!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 10access-list 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
To begin configuration for an IP Service Level Agreements (SLAs) label switched path (LSP) Health Monitor operation and enter auto IP SLA MPLS configuration mode, use the auto ip sla mpls-lsp-monitor command in global configuration mode. To remove all configuration information for an LSP Health Monitor operation, use the no form of this command.
auto ip sla mpls-lsp-monitor operation-number
no auto ip sla mpls-lsp-monitor operation-number
Syntax Description
operation-number
Number used for the identification of the LSP Health Monitor operation you want to configure.
Command Default
No LSP Health Monitor operation is configured.
Command Modes
Global configuration
Command History
Usage Guidelines
Entering this command automatically enables the mpls discovery vpn next-hop command.
After you configure an LSP Health Monitor operation, you must schedule the operation. To schedule an LSP Health Monitor operation, use the auto ip sla mpls-lsp-monitor schedule command in global configuration mode. You can also optionally set reaction configuration for the operation (see the auto ip sla mpls-lsp-monitor reaction-configuration command).
To display the current configuration settings of an LSP Health Monitor operation, use the show ip sla mpls-lsp-monitor configuration command in EXEC 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.
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 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 reaction-configuration
To configure proactive threshold monitoring parameters for a Cisco IOS IP Service Level Agreements (SLAs) label switched path (LSP) Health Monitor operation, use the auto ip sla mpls-lsp-monitor reaction-configuration command in global configuration mode. To clear all threshold monitoring configuration for a specified LSP Health Monitor operation, use the no form of this command.
LSP Health Monitor Without LSP Discovery
auto ip sla mpls-lsp-monitor reaction-configuration operation-number react {connectionLoss | timeout} [action-type option] [threshold-type {consecutive [occurrences] | immediate | never}]
no auto ip sla mpls-lsp-monitor reaction-configuration operation-number
LSP Health Monitor with LSP Discovery
auto ip sla mpls-lsp-monitor reaction-configuration operation-number react lpd {lpd-group [retry number] | tree-trace} [action-type trapOnly]
no auto ip sla mpls-lsp-monitor reaction-configuration operation-number
Syntax Description
Command Default
IP SLAs proactive threshold monitoring is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
You can configure the auto ip sla mpls-lsp-monitor reaction-configuration command multiple times to enable proactive threshold monitoring for multiple elements for the same operation. However, disabling of individual monitored elements is not supported. In other words, the no auto ip sla mpls-lsp-monitor reaction-configuration command will disable all proactive threshold monitoring configuration for the specified IP SLAs operation.
SNMP traps for IP SLAs are supported by the CISCO-RTTMON-MIB and CISCO-SYSLOG-MIB. Depending on the Cisco IOS software release that you are running, use the ip sla logging traps or ip sla monitor logging traps command to enable the generation of SNMP system logging messages specific to IP SLAs trap notifications. Use the snmp-server enable traps rtr command to enable the sending of IP SLAs SNMP trap notifications.
To display the current threshold monitoring configuration settings for an LSP Health Monitor operation, use the show ip sla mpls-lsp-monitor configuration command.
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. As specified by the proactive threshold monitoring configuration, when three consecutive connection loss or timeout events occur, an SNMP trap notification is sent.
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 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 trapsauto ip sla mpls-lsp-monitor schedule 1 schedule-period 60 start-time nowRelated Commands
auto ip sla mpls-lsp-monitor reset
To remove all IP Service Level Agreements (SLAs) label switched path (LSP) Health Monitor configuration from the running configuration, use the auto ip sla mpls-lsp-monitor reset command in global configuration mode.
auto ip sla mpls-lsp-monitor reset [lpd group-number]
Syntax Description
lpd group-number
(Optional) Specifies the number used to identify the LSP discovery group you want to configure.
Command Default
None
Command Modes
Global configuration
Command History
Usage Guidelines
Use the auto ip sla mpls-lsp-monitor reset lpd group-number command to remove all the stored network connectivity statistics for the specified LSP discovery group from the LSP discovery group database. The non-statistical LSP discovery group data will be set to default values or zero. However, the IP address of the associated Border Gateway Protocol (BGP) next hop neighbor, the list of LSP discovery group IP SLAs operations, and the list of LSP selector IP addresses will be preserved. After the auto ip sla mpls-lsp-monitor reset lpd group-number command is entered, statistical data for the group will start aggregating again with new data only.
To clear IP SLAs configuration information (not including IP SLAs LSP Health Monitor configuration) from the running configuration, use the ip sla reset command in global configuration mode.
Examples
The following example shows how to remove all the LSP Health Monitor configurations from the running configuration:
auto ip sla mpls-lsp-monitor resetRelated Commands
ip sla reset
Stops all IP SLAs operations, clears IP SLAs configuration information, and returns the IP SLAs feature to the startup condition.
auto ip sla mpls-lsp-monitor schedule
To configure the scheduling parameters for an IP Service Level Agreements (SLAs) label switched path (LSP) Health Monitor operation, use the auto ip sla mpls-lsp-monitor schedule command in global configuration mode. To stop the operation and place it in the default state (pending), use the no form of this command.
auto ip sla mpls-lsp-monitor schedule operation-number schedule-period seconds [frequency [seconds]] [start-time {after hh:mm:ss | hh:mm[:ss] [month day | day month] | now | pending}]
no auto ip sla mpls-lsp-monitor schedule operation-number
Syntax Description
Command Default
The LSP Health Monitor operation is placed in a pending state (that is, the operation is enabled but is not actively collecting information).
Command Modes
Global configuration
Command History
Usage Guidelines
After you schedule an LSP Health Monitor operation with the auto ip sla mpls-lsp-monitor schedule command, you cannot change the configuration of the operation. To change the configuration of the operation, use the no auto ip sla mpls-lsp-monitor operation-number command in global configuration mode and then enter the new configuration information.
To display the current configuration settings of an LSP Health Monitor operation, use the show ip sla mpls-lsp-monitor configuration command in user EXEC or privileged EXEC 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 schedule period for LSP Health Monitor operation 1 is set to 60 seconds and the operation is scheduled to start immediately.
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 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
buckets-of-history-kept
Note
Effective with Cisco IOS Release 12.4(4)T, 12.2(33)SRB, 12.2(33)SB, and 12.2(33)SXI, the buckets-of-history-kept command is replaced by the history buckets-kept command. See the history buckets-kept command for more information.
To set the number of history buckets that are kept during the lifetime of a Cisco IOS IP Service Level Agreements (SLAs) operation, use the buckets-of-history-kept command in the appropriate submode of IP SLA monitor configuration mode. To return to the default value, use the no form of this command.
buckets-of-history-kept size
no buckets-of-history-kept
Syntax Description
Defaults
50 buckets
Command Modes
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)
VoIP configuration (config-sla-monitor-voip)Command History
Usage Guidelines
Each time IP SLAs starts an operation, a new bucket is created until the number of history buckets matches the specified size or the operation's lifetime expires. History buckets do not wrap (that is, the oldest information is not replaced by newer information). The operation's lifetime is defined by the ip sla monitor schedule global configuration command.
Note
An IP SLAs operation can collect history and capture statistics. By default, the history for an IP SLAs operation is not collected. If history is collected, each history bucket contains one or more history entries from the operation. When the operation type is ICMP path echo, an entry is created for each hop along the path that the operation takes to reach its destination. The type of entry stored in the history table is controlled by the filter-for-history command. The total number of entries stored in the history table is controlled by the combination of the samples-of-history-kept, buckets-of-history-kept, and lives-of-history-kept commands.
Note
Note
Examples
The following example shows how to configure IP SLAs ICMP echo operation 1 to keep 25 history buckets during the operation lifetime.
ip sla monitor 1type echo protocol ipIcmpEcho 172.16.161.21buckets-of-history-kept 25lives-of-history-kept 1!ip sla monitor schedule 1 start-time now life foreverRelated Commands
clock-tolerance ntp oneway
To set the acceptable Network-Time Protocol (NTP) clock synchronization tolerance for a one-way Cisco IOS IP Service Level Agreements (SLAs) operation measurement, use the clock-tolerance ntp oneway 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.
clock-tolerance ntp oneway {absolute value | percent value}
no clock-tolerance ntp oneway
Syntax Description
Command Default
The NTP clock synchronization tolerance is set to 0 percent.
Command Modes
IP SLA Configuration
UDP jitter configuration (config-ip-sla-jitter)
IP SLA Monitor Configuration
UDP jitter configuration (config-sla-monitor-jitter)
Note
Command History
Usage Guidelines
The precision microseconds command must be configured before the clock-tolerance ntp oneway command is used.
Note
If the NTP running state is true and the total offset (sum of the offset for the sender and responder) is within the specified tolerance value (defined using the clock-tolerance ntp oneway command) of a one-way IP SLAs operation measurement for all the packets in a stream, the NTP synchronization status is determined to be synchronized. If these conditions are not met, the status is determined to be not synchronized.
The following guidelines apply to the displayed output:
•
•
•
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 1). 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 clock-tolerance ntp oneway command varies depending on the Cisco IOS release you are running (see Table 1) and the operation type configured. For example, if you are running Cisco IOS Release 12.4 and the UDP jitter operation type is configured, you would enter the clock-tolerance ntp oneway command in UDP jitter configuration mode (config-sla-monitor-jitter) within IP SLA monitor configuration mode.
Examples
The following examples show how to enable microsecond precision, configure the NTP synchronization offset tolerance to 10 percent, and set the packet priority to high for IP SLAs UDP jitter operation 1. 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 1).
IP SLA Configuration
ip sla 1udp-jitter 205.199.199.2 dest-port 9006precision microsecondsclock-tolerance ntp oneway percent 10probe-packet priority highfrequency 300!ip sla schedule 1 life forever start-time after 00:00:06IP SLA Monitor Configuration
ip sla monitor 1type jitter dest-ipaddr 205.199.199.2 dest-port 9006precision microsecondsclock-tolerance ntp oneway percent 10probe-packet priority highfrequency 300!ip sla monitor schedule 1 life forever start-time after 00:00:06Related Commands
cos
To set the class of service (CoS) for a Cisco IOS IP Service Level Agreements (SLAs) Ethernet operation, use the cos command in the appropriate submode of IP SLA configuration or IP SLA Ethernet monitor configuration mode. To return to the default value, use the no form of this command.
cos cos-value
no cos
Syntax Description
Command Default
The class of service value for the IP SLAs Ethernet operation is set to 0.
Command Modes
IP SLA configuration
Ethernet echo configuration (config-ip-sla-ethernet-echo)
Ethernet jitter configuration (config-ip-sla-ethernet-jitter)IP SLA Ethernet monitor configuration
Ethernet parameters configuration (config-ip-sla-ethernet-params)
Note
Command History
Usage Guidelines
You must configure the type of IP SLAs operation (such as Ethernet ping) before you can configure any of the other parameters of the operation.
The configuration mode for the cos command varies depending on the operation type configured. For example, if you are running Cisco IOS Release 12.2(33)SRB and the Ethernet ping operation type is configured using the ethernet echo mpid command in IP SLA configuration mode, you would enter the cos command in Ethernet echo configuration mode (config-ip-sla-ethernet-echo).
Examples
The following example shows how to configure operation parameters, proactive threshold monitoring, and scheduling options using an IP SLAs auto Ethernet operation. In this example, operation 10 is configured to automatically create IP SLAs Ethernet ping operations for all the discovered maintenance endpoints in the domain named testdomain and VLAN identification number 34. The class of service for each Ethernet ping operation is set to 3. As specified by the proactive threshold monitoring configuration, when three consecutive connection loss events occur, a Simple Network Management Protocol (SNMP) trap notification should be sent. The schedule period for operation 10 is 60 seconds, and the operation is scheduled to start immediately.
ip sla ethernet-monitor 10type echo domain testdomain vlan 34cos 3!ip sla ethernet-monitor reaction-configuration 10 react connectionLoss threshold-type consecutive 3 action-type trapOnly!ip sla ethernet-monitor schedule 10 schedule-period 60 start-time nowRelated Commands
data-pattern
To specify the data pattern in a Cisco IOS IP Service Level Agreements (SLAs) operation to test for data corruption, use the data pattern command in the appropriate submode of IP SLA configuration or IP SLA monitor configuration mode. To remove the data pattern specification, use the no form of this command.
data-pattern hex-pattern
no data-pattern hex-pattern
Syntax Description
Defaults
The default hex-pattern is ABCD.
Command Modes
IP SLA Configuration
UDP echo configuration (config-ip-sla-udp)
IP SLA Monitor Configuration
UDP echo configuration (config-sla-monitor-udp)
Note
Command History
Usage Guidelines
The data-pattern command allows users to specify an alphanumeric character string to verify that operation payload does not get corrupted in either direction (source-to-destination [SD] or destination-to-source [DS]).
Note
This command is supported in IPv4 networks and in IPv6 networks.
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 2). 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 data-pattern command varies depending on the Cisco IOS release you are running (see Table 2) and the operation type configured. For example, if you are running Cisco IOS Release 12.4 and the UDP echo operation type is configured, you would enter the data-pattern command in UDP echo configuration mode (config-sla-monitor-udp) within IP SLA monitor configuration mode.
Examples
The following examples show how to specify 1234ABCD5678 as the data pattern. 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 2).
The examples show the data-pattern command being used in an IPv4 network.
IP SLA Configuration
ip sla 1udp-echo 10.0.54.205 dest-port 101data-pattern 1234ABCD5678!ip sla schedule 1 life forever start-time nowIP SLA Monitor Configuration
ip sla monitor 1type udpEcho dest-ipaddr 10.0.54.205 dest-port 101data-pattern 1234ABCD5678!ip sla monitor schedule 1 life forever start-time nowRelated Commands
delete-scan-factor
To specify the number of times the IP Service Level Agreements (SLAs) label switched path (LSP) Health Monitor should check the scan queue before automatically deleting IP SLAs operations for Border Gateway Protocol (BGP) next hop neighbors that are no longer valid, use the delete-scan-factor command in auto IP SLA MPLS parameters configuration mode. To return to the default value, use the no form of this command.
delete-scan-factor factor
no delete-scan-factor
Syntax Description
factor
Number of times the LSP Health Monitor should check the scan queue before automatically deleting IP SLAs operations for BGP next hop neighbors that are no longer valid.
Command Default
The default scan factor is 1. In other words, each time the LSP Health Monitor checks the scan queue for updates, it deletes IP SLAs operations for BGP next hop neighbors that are no longer valid.
Command Modes
Auto IP SLA MPLS parameters configuration (config-auto-ip-sla-mpls-params)
Command History
Usage Guidelines
This command must be used with the scan-interval command. Use the scan-interval command to specify the time interval at which the LSP Health Monitor checks the scan queue for BGP next hop neighbor updates.
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 Provider Edge (PE) router. The delete scan factor is set to 2. In other words, every other time the LSP Health Monitor checks the scan queue for updates, it deletes IP SLAs operations for BGP next hop neighbors that are no longer valid.
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
dhcp (IP SLA)
To configure a Cisco IOS IP Service Level Agreements (SLAs) Dynamic Host Configuration Protocol (DHCP) operation, use the dhcp command in IP SLA configuration mode.
dhcp {destination-ip-address | destination-hostname} [source-ip {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 configuration (config-ip-sla)
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 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 4dhcp option-82 circuit-id 10005A6F1234ip dhcp-server 172.16.20.3!ip sla schedule 4 start-time nowRelated Commands
distributions-of-statistics-kept
Note
To set the number of statistics distributions kept per hop during a Cisco IOS IP Service Level Agreements (SLAs) operation, use the distributions-of-statistics-kept command in the appropriate submode of IP SLA monitor configuration mode. To return to the default value, use the no form of this command.
distributions-of-statistics-kept size
no distributions-of-statistics-kept
Syntax Description
Defaults
1 distribution
Command Modes
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)Command History
Usage Guidelines
In most situations, you do not need to change the number of statistics distributions kept or the time interval for each distribution. Only change these parameters when distributions are needed, for example, when performing statistical modeling of your network. To set the statistics distributions interval, use the statistics-distribution-interval command.
When the number of distributions reaches the size specified, no further distribution-based information is stored.
For the IP SLAs Internet Control Message Protocol (ICMP) path echo operation, the amount of router memory required to maintain the distribution statistics table is based on multiplying all of the values set by the following four commands:
•
•
•
•
The general equation used to calculate the memory requirement to maintain the distribution statistics table for an ICMP path echo operation is as follows:
Memory allocation = (160 bytes) * (distributions-of-statistics-kept size) * (hops-of-statistics-kept size) * (paths-of-statistics-kept size) * (hours-of-statistics-kept hours)
Note
Note
Examples
The following example shows how to set the statistics distribution to 5 and the distribution interval to 10 ms for IP SLAs ICMP echo operation 1. Consequently, the first distribution will contain statistics from 0 to 9 ms, the second distribution will contain statistics from 10 to 19 ms, the third distribution will contain statistics from 20 to 29 ms, the fourth distribution will contain statistics from 30 to 39 ms, and the fifth distribution will contain statistics from 40 ms to infinity.
ip sla monitor 1type echo protocol ipIcmpEcho 172.16.161.21distributions-of-statistics-kept 5statistics-distribution-interval 10!ip sla monitor schedule 1 life forever start-time nowRelated Commands
dlsw peer-ipaddr
To configure a Cisco IOS IP Service Level Agreements (SLAs) Data Link Switching Plus (DLSw+) operation, use the dlsw peer-ipaddr command in IP SLA configuration mode.
dlsw peer-ipaddr ip-address
Syntax Description
Defaults
No IP SLAs operation type is configured for the operation being configured.
Command Modes
IP SLA configuration (config-ip-sla)
Command History
12.4(4)T
This command was introduced. This command replaces the type dlsw peer-ipaddr command.
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 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 10dlsw peer-ipaddr 172.21.27.11request-data-size 15!ip sla schedule 4 start-time nowRelated Commands
dns (IP SLA)
To configure a Cisco IOS IP Service Level Agreements (SLAs) Domain Name System (DNS) operation, use the dns command in IP SLA configuration mode.
dns {destination-ip-address | destination-hostname} name-server ip-address [source-ip {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 configuration (config-ip-sla)
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 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 7dns host1 name-server 172.20.2.132!ip sla schedule 7 start-time nowRelated Commands
ip sla
Begins configuration for an IP SLAs operation and enters IP SLA configuration mode.
enhanced-history
Note
To enable enhanced history gathering for a Cisco IOS IP Service Level Agreements (SLAs) operation, use the enhanced-history command in the appropriate submode of IP SLA monitor configuration mode.
enhanced-history [interval seconds] [buckets number-of-buckets]
Syntax Description
Defaults
900 seconds and 100 buckets
Command Modes
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)Command History
Usage Guidelines
Performance statistics are stored in "buckets" that separate the accumulated data. Each bucket consists of data accumulated over the specified time interval.
Note
Examples
In the following example, Internet Control Message Protocol (ICMP) echo operation 3 is configured with the standard enhanced history characteristics.
ip sla monitor 3type echo protocol ipIcmpEcho 172.16.1.175enhanced-history interval 900 buckets 100!ip sla monitor schedule 3 start-time now life foreverRelated Commands
ethernet echo mpid
To manually configure an individual Cisco IOS IP Service Level Agreements (SLAs) Ethernet ping operation, use the ethernet echo mpid command in IP SLA configuration mode.
ethernet echo mpid mp-id domain domain-name {evc evc-id | vlan vlan-id}
Syntax Description
Command Default
No IP SLAs Ethernet ping operation is configured.
Command Modes
IP SLA configuration (config-ip-sla)
Command History
Usage Guidelines
You must configure the type of IP SLAs operation (such as Ethernet 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 global configuration command) and then reconfigure the operation with the new operation type.
Examples
The following example shows how to configure an IP SLAs Ethernet ping operation. In this example, the maintenance endpoint identification number is 23, the maintenance domain name is testdomain, and the VLAN identification number is 34. Operation 1 is scheduled to start immediately.
ip sla 1ethernet echo mpid 23 domain testdomain vlan 34!ip sla schedule 1 start-time nowRelated Commands
ip sla
Begins configuration for an IP SLAs operation and enters IP SLA configuration mode.
ethernet jitter mpid
To manually configure an individual Cisco IOS IP Service Level Agreements (SLAs) Ethernet jitter operation, use the ethernet jitter mpid command in IP SLA configuration mode.
ethernet jitter mpid mp-id domain domain-name {evc evc-id | vlan vlan-id} [interval interframe-interval] [num-frames frames-number]
Syntax Description
Command Default
No IP SLAs Ethernet jitter operation is configured.
Command Modes
IP SLA configuration (config-ip-sla)
Command History
Usage Guidelines
You must configure the type of IP SLAs operation (such as Ethernet jitter) 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 global configuration command) and then reconfigure the operation with the new operation type.
Examples
The following example shows how to configure an IP SLAs Ethernet jitter operation. In this example, the maintenance endpoint identification number is 23, the maintenance domain name is testdomain, the VLAN identification number is 34, the interframe interval is 20 ms, and the number of frames to be sent is 30. Operation 2 is scheduled to start immediately.
ip sla 2ethernet jitter mpid 23 domain testdomain vlan 34 interval 20 num-frames 30!ip sla schedule 2 start-time nowRelated Commands
ip sla
Begins configuration for an IP SLAs operation and enters IP SLA configuration mode.
exp (IP SLA)
To specify the experimental field value in the header for an echo request packet of a Cisco IOS IP Service Level Agreements (SLAs) operation, use the exp command in the appropriate submode of auto IP SLA MPLS configuration, IP SLA configuration, or IP SLA monitor configuration mode. To return to the default value, use the no form of this command.
exp exp-bits
no exp
Syntax Description
exp-bits
Specifies the experimental field value in the header for an echo request packet. The range is from 0 to 7. The default is 0.
Command Default
The experimental field value is set to 0.
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)
VCCV configuration (config-sla-vccv)
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 3). Note that if you are configuring an IP SLAs label switched path (LSP) Health Monitor operation, see Table 4 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 exp (IP SLA) 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 exp (IP SLA) 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 experimental field value for each IP SLAs operations created by LSP Health Monitor operation 1 is set to 5.
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 2exp 5!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
filter-for-history
Note
To define the type of information kept in the history table for a Cisco IOS IP Service Level Agreements (SLAs) operation, use the filter-for-history command in the appropriate submode of IP SLA monitor configuration mode. To return to the default value, use the no form of this command.
filter-for-history {none | all | overThreshold | failures}
no filter-for-history {none | all | overThreshold | failures}
Syntax Description
Defaults
No IP SLAs history is kept for an operation.
Command Modes
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)
VoIP configuration (config-sla-monitor-voip)Command History
Usage Guidelines
Use the filter-for-history command to control what gets stored in the history table for an IP SLAs operation. To control how much history gets saved in the history table, use the lives-of-history-kept, buckets-of-history-kept, and the samples-of-history-kept commands.
Note
An IP SLAs operation can collect history and capture statistics. By default, the history for an IP SLAs operation is not collected. If history is collected, each history bucket contains one or more history entries from the operation. When the operation type is ICMP path echo, an entry is created for each hop along the path that the operation takes to reach its destination. The type of entry stored in the history table is controlled by the filter-for-history command. The total number of entries stored in the history table is controlled by the combination of the samples-of-history-kept, buckets-of-history-kept, and lives-of-history-kept commands.
Note
Note
Examples
In the following example, only operation packets that fail are kept in the history table.
ip sla monitor 1type echo protocol ipIcmpEcho 172.16.161.21lives-of-history-kept 1filter-for-history failures!ip sla monitor schedule 1 life forever start-time nowRelated Commands
flow-label (IP SLA)
To define the flow label field in the IPv6 header of a Cisco IOS IP Service Level Agreements (SLAs) operation, use the flow-label (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.
flow-label number
no flow-label
Syntax Description
Defaults
The default flow label value is 0.
Command Modes
ICMP echo configuration (config-ip-sla-echo)
TCP connect configuration (config-ip-sla-tcp)
UDP echo configuration (config-ip-sla-udp)
UDP jitter configuration (config-ip-sla-jitter)
Note
Command History
Usage Guidelines
The flow label value is stored in a a 20-bit field in the IPv6 packet header and is used by a source to label packets of a flow.
A flow label value of zero is used to indicate packets that are not part of any flow.
When the flow label is defined for an operation, the IP SLAs Responder will reflect the flow-label value it receives.
Note
To display the flow label value for all Cisco IOS IP SLAs operations or a specified operation, use the show ip sla configuration command.
Examples
In the following example, IP SLAs operation 1 is configured as an Internet Control Message Protocol (ICMP) echo operation with destination IPv6 address 2001:DB8:100::1. The value in the flow label field of the IPv6 header is set to 0x1B669.
ip sla 1icmp-echo 2001:DB8:100::1flow-label 0x1B669!ip sla schedule 1 start-time nowRelated Commands
force-explicit-null
To add an explicit null label to all echo request packets of a Cisco IOS IP Service Level Agreements (SLAs) LSP Health Monitor operation, use the force-explicit-null command in the appropriate submode of auto IP SLA MPLS configuration mode. To return to the default value, use the no form of this command.
force-explicit-null
no force-explicit-null
Syntax Description
This command has no arguments or keywords.
Command Default
An explicit null label is not added.
Command Modes
Auto IP SLA MPLS Configuration
MPLS parameters configuration (config-auto-ip-sla-mpls-params)
LSP discovery parameters configuration (config-auto-ip-sla-mpls-lpd-params)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.
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. In this example, an explicit null label will be added to all the echo request packets of IP SLAs operations created by LSP Health Monitor operation 1.
mpls discovery vpn interval 60mpls discovery vpn next-hop!auto ip sla mpls-lsp-monitor 1type echo ipsla-vrf-allforce-explicit-nulltimeout 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.
frequency (IP SLA)
To set the rate at which a specified IP Service Level Agreements (SLAs) operation repeats, use the frequency (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.
frequency seconds
no frequency
Syntax Description
Defaults
60 seconds
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)
VCCV configuration (config-sla-vccv)
VoIP configuration (config-ip-sla-voip)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
A single IP SLAs operation will repeat at a given frequency for the lifetime of the operation. For example, a User Datagram Protocol (UDP) jitter operation with a frequency of 60 sends a collection of data packets (simulated network traffic) once every 60 seconds, for the lifetime of the operation. The default simulated traffic for a UDP jitter operation consists of ten packets sent 20 milliseconds apart. This "payload" is sent when the operation is started, then is sent again 60 seconds later.
If an individual IP SLAs operation takes longer to execute than the specified frequency value, a statistics counter called "busy" is incremented rather than immediately repeating the operation.
Consider the following guidelines before configuring the frequency (IP SLA), timeout (IP SLA), and threshold (IP SLA) commands. For the IP SLAs UDP jitter operation, the following guidelines are recommended:
•
•
where N = (num-packets number-of-packets) * (interval interpacket-interval). Use the udp-jitter command to configure the num-packets number-of-packets and interval interpacket-interval values.
For all other IP SLAs operations, the following configuration guideline is recommended:
(frequency seconds) > (timeout milliseconds) > (threshold milliseconds)
Note
The frequency (IP SLA) command is supported in IPv4 networks. This command is also supported in IPv6 networks when configuring an IP SLAs operation that supports IPv6 addresses.
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 5). 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 frequency (IP SLA) command varies depending on the Cisco IOS release you are running (see Table 5) 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 frequency (IP SLA) command in ICMP echo configuration mode (config-sla-monitor-echo) within IP SLA monitor configuration mode.
Examples
The following examples show how to configure an IP SLAs ICMP echo operation (operation 10) to repeat every 90 seconds. 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 5).
IP SLA Configuration
This example shows the frequency (IP SLA) command being used in an IPv4 network in ICMP echo configuration mode within IP SLA configuration mode:
ip sla 10icmp-echo 172.16.1.175frequency 90!ip sla schedule 10 life 300 start-time after 00:05:00IP SLA Monitor Configuration
This example shows the frequency (IP SLA) command being used in an IPv4 network in ICMP echo configuration mode within IP SLA monitor configuration mode:
ip sla monitor 10type echo protocol ipIcmpEcho 172.16.1.175frequency 90!ip sla monitor schedule 10 life 300 start-time after 00:05:00Related Commands
ftp get
To configure a Cisco IOS IP Service Level Agreements (SLAs) File Transfer Protocol (FTP) GET operation, use the ftp get command in IP SLA configuration mode.
ftp get url [source-ip {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 configuration (config-ip-sla)
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 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 3ftp get ftp://user1:password1@host1/file1!ip sla schedule 3 start-time nowRelated Commands
ip sla
Begins configuration for an IP SLAs operation and enters IP SLA configuration mode.
history buckets-kept
To set the number of history buckets that are kept during the lifetime of a Cisco IOS IP Service Level Agreements (SLAs) operation, use the history buckets-kept command in the appropriate submode of IP SLA configuration mode. To return to the default value, use the no form of this command.
history buckets-kept size
no history buckets-kept
Syntax Description
Defaults
50 buckets
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 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)
VCCV configuration (config-sla-vccv)
VoIP configuration (config-ip-sla-voip)Command History
Usage Guidelines
Each time IP SLAs starts an operation, a new bucket is created until the number of history buckets matches the specified size or the operation's lifetime expires. History buckets do not wrap. The operation's lifetime is defined by the ip sla schedule global configuration command.
The history buckets-kept command is supported in IPv4 networks. This command is also supported in IPv6 networks when configuring an IP SLAs operation that supports IPv6 addresses.
Note
By default, the history for an IP SLAs operation is not collected. If history is collected, each bucket contains one or more history entries from the operation. When the operation type is Internet Control Message Protocol (ICMP) path echo, an entry is created for each hop along the path that the operation takes to reach its destination. The type of entry stored in the history table is controlled by the history filter command. The total number of entries stored in the history table is controlled by the combination of the samples-of-history-kept, history buckets-kept, and history lives-kept commands.
Note
Examples
The following example shows how to configure IP SLAs ICMP echo operation 1 to keep 25 history buckets during the operation lifetime. The example shows the history buckets-kept command being used in an IPv4 network.
ip sla 1icmp-echo 172.16.161.21history buckets-kept 25history lives-kept 1!ip sla schedule 1 start-time now life foreverRelated Commands
history distributions-of-statistics-kept
To set the number of statistics distributions kept per hop during a Cisco IOS IP Service Level Agreements (SLAs) operation, use the history distributions-of-statistics-kept command in the appropriate submode of IP SLA configuration mode. To return to the default value, use the no form of this command.
history distributions-of-statistics-kept size
no history distributions-of-statistics-kept
Syntax Description
Defaults
1 distribution
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)
VCCV configuration (config-sla-vccv)
VoIP configuration (config-ip-sla-voip)Command History
Usage Guidelines
In most situations, you do not need to change the number of statistics distributions kept or the time interval for each distribution. Only change these parameters when distributions are needed, for example, when performing statistical modeling of your network. To set the statistics distributions interval, use the history statistics-distribution-interval command.
When the number of distributions reaches the size specified, no further distribution-based information is stored.
The history distributions-of-statistics-kept command is supported in IPv4 networks. This command is also supported in IPv6 networks when configuring an IP SLAs operation that supports IPv6 addresses.
For the IP SLAs Internet Control Message Protocol (ICMP) path echo operation, the amount of router memory required to maintain the distribution statistics table is based on multiplying all of the values set by the following four commands:
•
•
•
•
The general equation used to calculate the memory requirement to maintain the distribution statistics table for an ICMP path echo operation is as follows:
Memory allocation = (160 bytes) * (history distributions-of-statistics-kept size) * (hops-of-statistics-kept size) * (paths-of-statistics-kept size) * (history hours-of-statistics-kept hours)
Note
Examples
In the following example, the statistics distribution is set to five and the distribution interval is set to 10 ms for IP SLAs ICMP echo operation 1. Consequently, the first distribution will contain statistics from 0 to 9 ms, the second distribution will contain statistics from 10 to 19 ms, the third distribution will contain statistics from 20 to 29 ms, the fourth distribution will contain statistics from 30 to 39 ms, and the fifth distribution will contain statistics from 40 ms to infinity. The example shows the history distributions-of-statistics-kept command being used in an IPv4 network.
ip sla 1icmp-echo 172.16.161.21history distributions-of-statistics-kept 5history statistics-distribution-interval 10!ip sla schedule 1 life forever start-time nowRelated Commands
history enhanced
To enable enhanced history gathering for a Cisco IOS IP Service Level Agreements (SLAs) operation, use the history enhanced command in the appropriate submode of IP SLA configuration mode.
history enhanced [interval seconds] [buckets number-of-buckets]
Syntax Description
Defaults
900 seconds and 100 buckets
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 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)
VCCV configuration (config-sla-vccv)
VoIP configuration (config-ip-sla-voip)Command History
Usage Guidelines
Performance statistics are stored in "buckets" that separate the accumulated data. Each bucket consists of data accumulated over the specified time interval.
The history enhanced command is supported in IPv4 networks. This command is also supported in IPv6 networks when configuring an IP SLAs operation that supports IPv6 addresses.
Examples
In the following example, Internet Control Message Protocol (ICMP) echo operation 3 is configured with the standard enhanced history characteristics. The example shows the history enhanced command being used in an IPv4 network.
ip sla 3icmp-echo 172.16.1.175history enhanced interval 900 buckets 100!ip sla schedule 3 start-time now life foreverRelated Commands
history filter
To define the type of information kept in the history table for a Cisco IOS IP Service Level Agreements (SLAs) operation, use the history filter command in the appropriate submode of IP SLA configuration mode. To return to the default value, use the no form of this command.
history filter {none | all | overThreshold | failures}
no history filter {none | all | overThreshold | failures}
Syntax Description
Defaults
No IP SLAs history is kept for an operation.
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 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)
VCCV configuration (config-sla-vccv)
VoIP configuration (config-ip-sla-voip)Command History
Usage Guidelines
Use the history filter command to control what gets stored in the history table for an IP SLAs operation. To control how much history gets saved in the history table, use the history lives-kept, history buckets-kept, and the samples-of-history-kept commands.
The history filter command is supported in IPv4 networks. This command is also supported in IPv6 networks when configuring an IP SLAs operation that supports IPv6 addresses.
Note
An IP SLAs operation can collect history and capture statistics. By default, the history for an IP SLAs operation is not collected. When a problem arises where history is useful (for example, a large number of timeouts are occurring), use the history lives-kept command to enable history collection.
Note
Examples
In the following example, only operation packets that fail are kept in the history table. The example shows the history filter command being used in an IPv4 network.
ip sla 1icmp-echo 172.16.161.21history lives-kept 1history filter failures!ip sla schedule 1 life forever start-time nowRelated Commands
history hours-of-statistics-kept
To set the number of hours for which statistics are maintained for a Cisco IOS IP Service Level Agreements (SLAs) operation, use the history hours-of-statistics-kept command in the appropriate submode of IP SLA configuration mode. To return to the default value, use the no form of this command.
history hours-of-statistics-kept hours
no history hours-of-statistics-kept
Syntax Description
Defaults
2 hours
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)
VCCV configuration (config-sla-vccv)
VoIP configuration (config-ip-sla-voip)Command History
Usage Guidelines
When the number of hours exceeds the specified value, the statistics table wraps (that is, the oldest information is replaced by newer information).
For the IP SLAs Internet Control Message Protocol (ICMP) path echo operation, the amount of router memory required to maintain the distribution statistics table is based on multiplying all of the values set by the following four commands:
•
•
•
•
The general equation used to calculate the memory requirement to maintain the distribution statistics table for an ICMP path echo operation is as follows:
Memory allocation = (160 bytes) * (history distributions-of-statistics-kept size) * (hops-of-statistics-kept size) * (paths-of-statistics-kept size) * (history hours-of-statistics-kept hours)
Note
The history hours-of-statistics-kept command is supported in IPv4 networks. This command is also supported in IPv6 networks when configuring an IP SLAs operation that supports IPv6 addresses.
Examples
The following example shows how to maintain 3 hours of statistics for IP SLAs ICMP path echo operation 2. The example shows the history hours-of-statistics-kept command being used in an IPv4 network.
ip sla 2path-echo 172.16.1.177history hours-of-statistics-kept 3!ip sla schedule 2 life forever start-time nowRelated Commands
history lives-kept
To set the number of lives maintained in the history table for a Cisco IOS IP Service Level Agreements (SLAs) operation, use the history lives-kept command in the appropriate submode of IP SLA configuration mode. To return to the default value, use the no form of this command.
history lives-kept lives
no history lives-kept
Syntax Description
lives
Number of lives maintained in the history table for the operation. If you specify 0 lives, history is not collected for the operation.
Defaults
0 lives
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 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)
VCCV configuration (config-sla-vccv)
VoIP configuration (config-ip-sla-voip)Command History
Usage Guidelines
The following rules apply to the history lives-kept command:
•
•
•
•
The history lives-kept command is supported in IPv4 networks. This command is also supported in IPv6 networks when configuring an IP SLAs operation that supports IPv6 addresses.
Note
To disable history collection, use the no history lives-kept command rather than the history filter none command. The no history lives-kept command disables history collection before an IP SLAs operation is attempted. The history filter command checks for history inclusion after the operation attempt is made.
Examples
The following example shows how to maintain the history for five lives of IP SLAs ICMP echo operation 1. The example shows the history lives-kept command being used in an IPv4 network.
ip sla 1icmp-echo 172.16.1.176history lives-kept 5!ip sla schedule 1 life forever start-time nowRelated Commands
history statistics-distribution-interval
To set the time interval for each statistics distribution kept for a Cisco IOS IP Service Level Agreements (SLAs) operation, use the history statistics-distribution-interval command in the appropriate submode of IP SLA configuration mode. To return to the default value, use the no form of this command.
history statistics-distribution-interval milliseconds
no history statistics-distribution-interval
Syntax Description
milliseconds
Number of milliseconds (ms) used for each statistics distribution kept. The default is 20.
Defaults
20 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)
VCCV configuration (config-sla-vccv)
VoIP configuration (config-ip-sla-voip)Command History
Usage Guidelines
In most situations, you do not need to change the time interval for each statistics distribution or number of distributions kept. Only change these parameters when distributions are needed, for example, when performing statistical modeling of your network. To set the number of statistics distributions kept, use the history statistics-distribution-interval command.
The history statistics-distribution-interval command is supported in IPv4 networks. This command is also supported in IPv6 networks when configuring an IP SLAs operation that supports IPv6 addresses.
Examples
In the following example, the statistics distribution is set to five and the distribution interval is set to 10 ms for IP SLAs ICMP echo operation 1. Consequently, the first distribution will contain statistics from 0 to 9 ms, the second distribution will contain statistics from 10 to 19 ms, the third distribution will contain statistics from 20 to 29 ms, the fourth distribution will contain statistics from 30 to 39 ms, and the fifth distribution will contain statistics from 40 ms to infinity.
The example shows the history statistics-distribution-interval command being used in an IPv4 network.
ip sla 1icmp-echo 172.16.161.21history distributions-of-statistics-kept 5history statistics-distribution-interval 10!ip sla schedule 1 life forever start-time nowRelated Commands
hops-of-statistics-kept
To set the number of hops for which statistics are maintained per path for a Cisco IOS IP Service Level Agreements (SLAs) operation, use the hops-of-statistics-kept 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.
hops-of-statistics-kept size
no hops-of-statistics-kept
Syntax Description
Defaults
16 hops
Command Modes
IP SLA Configuration
ICMP path echo configuration (config-ip-sla-pathEcho)
IP SLA Monitor Configuration
ICMP path echo configuration (config-sla-monitor-pathEcho)
Note
Command History
Usage Guidelines
When the number of hops reaches the size specified, no further hop-based information is stored.
Note
For the IP SLAs ICMP path echo operation, the amount of router memory required to maintain the distribution statistics table is based on multiplying all of the values set by the following four commands:
•
•
•
•
The general equation used to calculate the memory requirement to maintain the distribution statistics table for an ICMP path echo operation is as follows:
Memory allocation = (160 bytes) * (distributions-of-statistics-kept size) * (hops-of-statistics-kept size) * (paths-of-statistics-kept size) * (hours-of-statistics-kept hours)
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 6). 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 hops-of-statistics-kept command varies depending on the Cisco IOS release you are running (see Table 6) and the operation type configured. For example, if you are running Cisco IOS Release 12.4 and the ICMP path echo operation type is configured, you would enter the hops-of-statistics-kept command in ICMP path echo configuration mode (config-sla-monitor-pathEcho) within IP SLA monitor configuration mode.
Examples
The following examples show how to monitor the statistics of IP SLAs ICMP path echo operation 2 for ten hops only. 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 6).
IP SLA Configuration
ip sla 2path-echo 172.16.1.177hops-of-statistics-kept 10!ip sla schedule 2 life forever start-time nowIP SLA Monitor Configuration
ip sla monitor 2type pathecho protocol ipIcmpEcho 172.16.1.177hops-of-statistics-kept 10!ip sla monitor schedule 2 life forever start-time nowRelated Commands
hours-of-statistics-kept
Note
To set the number of hours for which statistics are maintained for a Cisco IOS IP Service Level Agreements (SLAs) operation, use the hours-of-statistics-kept command in the appropriate submode of IP SLA monitor configuration mode. To return to the default value, use the no form of this command.
hours-of-statistics-kept hours
no hours-of-statistics-kept
Syntax Description
Defaults
2 hours
Command Modes
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)Command History
Usage Guidelines
When the number of hours exceeds the specified value, the statistics table wraps (that is, the oldest information is replaced by newer information).
For the IP SLAs Internet Control Message Protocol (ICMP) path echo operation, the amount of router memory required to maintain the distribution statistics table is based on multiplying all of the values set by the following four commands:
•
•
•
•
The general equation used to calculate the memory requirement to maintain the distribution statistics table for an ICMP path echo operation is as follows:
Memory allocation = (160 bytes) * (distributions-of-statistics-kept size) * (hops-of-statistics-kept size) * (paths-of-statistics-kept size) * (hours-of-statistics-kept hours)
Note
Note
Examples
The following example shows how to maintain 3 hours of statistics for IP SLAs ICMP path echo operation 2.
ip sla monitor 2type pathecho protocol ipIcmpEcho 172.16.1.177hours-of-statistics-kept 3!ip sla monitor schedule 2 life forever start-time nowRelated Commands
hours-of-statistics-kept (LSP discovery)
To set the number of hours for which label switched path (LSP) discovery group statistics are maintained for a Cisco IOS IP Service Level Agreements (SLAs) LSP Health Monitor operation, use the hours-of-statistics-kept command in auto IP SLA MPLS LSP discovery parameters configuration mode. To return to the default value, use the no form of this command.
hours-of-statistics-kept hours
no hours-of-statistics-kept
Syntax Description
Command Default
2 hours
Command Modes
Auto IP SLA MPLS LSP discovery parameters configuration (config-auto-ip-sla-mpls-lpd-params)
Command History
12.2(31)SB2
This command was introduced.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
The LSP discovery group statistics are distributed in one-hour increments. Since the number of LSP discovery groups for a single LSP Health Monitor operation can be significantly large, the collection of group statistics is restricted to a maximum of 2 hours. If the number argument is set to zero, no LSP discovery group statistics are maintained.
Use the path-discover command to enable the LSP discovery option for an IP SLAs LSP Health Monitor operation and enter auto IP SLA MPLS LSP discovery parameters 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, the LSP discovery option is enabled for LSP Health Monitor operation 1. Operation 1 is configured to automatically create IP SLAs LSP ping operations for the equal-cost multipaths to 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. LSP discovery group statistics are collected every 1 hour.
auto ip sla mpls-lsp-monitor 1type echo ipsla-vrf-allpath-discover!maximum-sessions 2session-timeout 60interval 2timeout 4force-explicit-nullhours-of-statistics-kept 1scan-period 30!auto ip sla mpls-lsp-monitor schedule 1 schedule-period 60 frequency 100 start-time now!auto ip sla mpls-lsp-monitor reaction-configuration 1 react lpd tree-trace action-type trapOnlyauto ip sla mpls-lsp-monitor reaction-configuration 1 react lpd lpd-group retry 3 action-type trapOnlyRelated Commands
http (IP SLA)
To configure a Cisco IOS IP Service Level Agreements (SLAs) HTTP operation, use the http command in IP SLA configuration mode.
http {get | raw} url url [name-server ip-address] [version version-number] [source-ip {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 configuration (config-ip-sla)
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 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 6http raw url http://www.cisco.comhttp-raw-requestGET /index.html HTTP/1.0\r\n\r\n!ip sla schedule 6 start-time nowRelated Commands
ip sla
Begins configuration for an IP SLAs operation and enters IP SLA configuration mode.
http-raw-request
To explicitly specify the options for a GET request for a Cisco IOS IP Service Level Agreements (SLAs) Hypertext Transfer Protocol (HTTP) operation, use the http-raw-request command in the appropriate submode of IP SLA configuration or IP SLA monitor configuration mode.
http-raw-request
Syntax Description
This command has no arguments or keywords.
Defaults
No options are specified for a GET request.
Command Modes
IP SLA Configuration
HTTP configuration (config-ip-sla-http)
IP SLA Monitor Configuration
HTTP configuration (config-sla-monitor-http)
Note
Command History
Usage Guidelines
Use the http-raw-request command to explicitly specify the content of an HTTP request. Use HTTP version 1.0 commands after entering the http-raw-request command.
IP SLAs will specify the content of an HTTP request if you use the type http operation get command. IP SLAs will send the HTTP request, receive the reply, and report round-trip time (RTT) statistics (including the size of the page returned).
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 7). 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 http-raw-request command varies depending on the Cisco IOS release you are running (see Table 7) and the operation type configured. For example, if you are running Cisco IOS Release 12.4 and the HTTP operation type is configured, you would enter the http-raw-request command in HTTP configuration mode (config-sla-monitor-http) within IP SLA monitor configuration mode.
Examples
In the following examples, IP SLAs operation 6 is created and configured as an HTTP operation. The HTTP GET command is explicitly specified. 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 7).
IP SLA Configuration
ip sla 6http raw http://www.cisco.comhttp-raw-requestGET /index.html HTTP/1.0\r\n\r\n!ip sla schedule 6 start-time nowIP SLA Monitor Configuration
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
