Table Of Contents
IP Service Level Agreement Commands on Cisco IOS XR Software
action (IP SLA)
ageout
buckets (history command)
buckets (hourly)
buckets (interval)
control disable
datasize request
destination address (IP SLA)
destination port
distribution count
distribution interval
filter
frequency (IP SLA)
history
ipsla key-chain
ipsla low-memory
ipsla operation
ipsla reaction operation
ipsla reaction trigger
ipsla responder
ipsla schedule operation
life
lives
lsr-path
maximum hops
maximum paths (IP SLA)
packet count
packet interval
react
recurring
samples
show ipsla application
show ipsla history
show ipsla responder statistics ports
show ipsla statistics
show ipsla statistics aggregated
show ipsla statistics aggregated detail
show ipsla statistics enhanced aggregated
source address
source port
start-time
statistics
tag (IP SLA)
threshold
threshold type average
threshold type consecutive
threshold type immediate
threshold type xofy
timeout
tos
type icmp echo
type icmp path-echo
type icmp path-jitter
type udp echo
type udp jitter
type udp ipv4 address
verify-data
IP Service Level Agreement Commands on Cisco IOS XR Software
This module describes the Cisco IOS XR software commands used to configure IP Service Level Agreements (IP SLAs). For detailed information about IP SLA concepts, configuration tasks, and examples, see the Implementing IP Service Level Agreements on Cisco IOS XR Software configuration module of the Cisco IOS XR System Management Configuration Guide.
action (IP SLA)
To specify what action or combination of actions the operation performs when you configure the react command or when threshold events occur, use the action command in IP SLA reaction condition configuration mode. To clear action or combination of actions (no action can happen), use the no form of this command.
action {logging | trigger}
no action {logging | trigger}
Syntax Description
logging
|
Sends a logging message when the specified violation type occurs for the monitored element. The IP SLA agent generates a syslog and informs SNMP. Then, it is up to the SNMP agent to generate a trap or not.
|
trigger
|
Determines that the operation state of one or more target operations makes the transition from pending to active when the violation conditions are met. The target operations to be triggered are specified using the ipsla reaction trigger command. A target operation continues until its life expires, as specified by the lifetime value of the target operation. A triggered target operation must finish its life before it can be triggered again.
|
Defaults
No default behavior or values
Command Modes
IP SLA reaction condition configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
For the action command to occur for threshold events, the threshold type must be defined. Absence of threshold type configuration is considered if the threshold check is not activated.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the action command with the logging keyword:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla reaction operation 432
RP/0/RP0/CPU0:router(config-ipsla-react)# react connection-loss
RP/0/RP0/CPU0:router(config-ipsla-react-cond)# action logging
Related Commands
ageout
To specify the number of seconds to keep the operation in memory when it is not actively collecting information, use the ageout command in IP SLA schedule configuration mode. To use the default value and the operation will never age out, use the no form of this command.
ageout seconds
no ageout
Syntax Description
seconds
|
Age-out interval in seconds. The value 0 seconds means that the collected data is not aged out.The range is 0 to 2073600.
|
Defaults
The default value is 0 seconds (never aged out).
Command Modes
IP SLA schedule configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the ageout command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla schedule operation 1
RP/0/RP0/CPU0:router(config-ipsla-sched)# ageout 3600
Related Commands
buckets (history command)
To set the number of history buckets that are kept during the lifetime of the IP SLA operation, use the buckets command in IP SLA operation history configuration mode. To use the default value, use the no form of this command.
buckets buckets
no buckets
Syntax Description
buckets
|
Number of history buckets that are kept during the lifetime of an IP SLA operation. The range is 1 to 60.
|
Defaults
The default value is 15 buckets.
Command Modes
IP SLA operation history configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The buckets command is available only to IP SLA ICMP Path-Echo operation, IP SLA ICMP Echo operation, and IP SLA UDP Echo operation.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the buckets command in IP SLA UDP Echo configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp echo
RP/0/RP0/CPU0:router(config-ipsla-udp-echo)# history
RP/0/RP0/CPU0:router(config-ipsla-op-hist)# buckets 30
Related Commands
buckets (hourly)
To set the number of hours in which statistics are kept, use the bucket command in IP SLA operation statistics configuration mode. To use the default value, use the no form of this command.
buckets hours
no buckets
Syntax Description
hours
|
Sets the number of hours in which statistics are maintained for the IP SLA operations. The range is 0 to 25.
|
Defaults
The default value is 2.
Command Modes
IP SLA operation statistics configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The buckets command with the hours argument is valid only for the statistics command with the hourly keyword.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to set the number of hours in which statistics are maintained for the IP SLA UDP Jitter operation for the buckets command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# statistics hourly
RP/0/RP0/CPU0:router(config-ipsla-op-stats)# buckets 10
Related Commands
Command
|
Description
|
statistics
|
Sets the statistics collection parameters for the operation.
|
buckets (interval)
To refer to the data buckets in which the enhanced history statistics are kept, use the buckets command in IP SLA operation statistics configuration mode. To remove the statistics collection of the specified interval, use the no form of this command.
buckets bucket-size
no buckets
Syntax Description
bucket-size
|
bucket-size is when the configured bucket limit is reached. Therefore, statistics gathering for the operation ends. The range is 1 to 100. The default value is 100.
|
Defaults
No default behavior or values
Command Modes
IP SLA operation statistics configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The buckets command with the bucket-size argument is valid only for the statistics command with the interval keyword.
Examples
The following example shows how to collect statistics for a given time interval for the IP SLA UDP Jitter operation for the buckets command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# statistics interval 60
RP/0/RP0/CPU0:router(config-ipsla-op-stats)# buckets 50
Related Commands
Command
|
Description
|
statistics
|
Sets the statistics collection parameters for the operation.
|
control disable
To disable the control packets, use the control disable command in IP SLA UDP Echo configuration mode or IP SLA UDP Jitter configuration mode. To use the control packets again, use the no form of this command.
control disable
no control disable
Syntax Description
This command has no arguments or keywords.
Defaults
Control packets are enabled by default.
Command Modes
IP SLA UDP Echo configuration
IP SLA UDP Jitter configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When you configure the control disable command on the agent side, you need to configure a permanent port on the responder side or the operation returns a timeout error. If you configure the control disable command, a permanent port of the IP SLA Responder or some other functionality, such as the UDP echo server, is required on the remote device.
The control disable command is valid for operations that require a responder.
The IP SLA control protocol is disabled, which is used to send a control message to the IP SLA Responder prior to sending an operation packet. By default, IP SLA control messages are sent to the destination device to establish a connection with the IP SLA Responder.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the control disable command in IP SLA UDP Jitter configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)#ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# control disable
Related Commands
datasize request
To set the protocol data size in the request packet in the payload of an operation, use the datasize request command in IP SLA ICMP Path-Jitter configuration mode, IP SLA ICMP Path-Echo configuration mode, IP SLA ICMP Echo configuration mode, IP SLA UDP Echo configuration mode, or IP SLA UDP Jitter configuration mode. To use the default value, use the no form of this command.
datasize request size
no datasize request
Syntax Description
size
|
Specifies the following ranges and default values that are protocol dependent.
• For UDP Jitter operation, the range is 16 to 1500 B.
• For UDP Echo operation, the range is 4 to 1500 B.
• For ICMP Echo operation, the range is 0 to 16384 B.
• For ICMP Path-Echo operation, the range is 0 to 16384 B.
• For ICMP Path-Jitter operation, the range is 0 to 16384 B.
|
Defaults
For UDP Jitter operation, the default value is 32 B.
For UDP Echo operation, the default value is 16 B.
For ICMP Echo operation, the default value is 36 B.
For ICMP Path-Echo operation, the default value is 36 B.
For ICMP Path-Jitter operation, the default value is 36 B.
Command Modes
IP SLA UDP Echo configuration
IP SLA UDP Jitter configuration
IP SLA ICMP Path-Jitter configuration
IP SLA Path-Echo configuration
IP SLA ICMP Echo configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the datasize request command in IP SLA UDP Jitter configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# datasize request 512
Related Commands
destination address (IP SLA)
To identify the address of the target device, use the destination address command in IP SLA ICMP Path-Jitter configuration mode, IP SLA ICMP Path-Echo configuration mode, IP SLA ICMP Echo configuration mode, IP SLA UDP Echo configuration mode, or IP SLA UDP Jitter configuration mode. To unset the destination address, use the no form of this command.
destination address ipv4 address
no destination address
Syntax Description
ipv4 address
|
IP address of the target device.
|
Defaults
No default behavior or values
Command Modes
IP SLA UDP Echo configuration
IP SLA UDP Jitter configuration
IP SLA ICMP Path-Jitter configuration
IP SLA ICMP Path-Echo configuration
IP SLA ICMP Echo configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
You must specify the address of the target device. The configuration for the destination address command is mandatory for all operations.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to designate an IP address for the destination address command in IP SLA UDP Jitter configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# destination address 12.25.26.10
Related Commands
destination port
To identify the port of the target device, use the destination port command in IP SLA UDP Echo configuration mode or IP SLA UDP Jitter configuration mode. To unset the destination port, use the no form of this command.
destination port port
no destination port
Syntax Description
port
|
Port number of the target device. The range is 1 to 65355.
|
Defaults
No default behavior or values
Command Modes
IP SLA UDP Echo configuration
IP SLA UDP Jitter configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The destination port command is not available in ICMP operations and applies only to UDP operations.
You must specify the port of the target device. The configuration for the destination port command is mandatory for both IP SLA UDP Echo and IP SLA UDP Jitter configurations.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to designate a port for the destination port command in IP SLA UDP Jitter configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# destination port 11111
Related Commands
distribution count
To set the number of statistics distributions that are kept for each hop during the lifetime of the IP SLA operation, use the distribution count command in IP SLA operation statistics configuration mode. To use the default value, use the no form of this command.
distribution count slot
no distribution count
Syntax Description
slot
|
Number of statistics distributions that are kept The range is 1 to 20. The default value is 1.
|
Defaults
The default value is 1.
Command Modes
IP SLA operation statistics configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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 distribution interval command in IP SLA operation statistics configuration mode. The total number of statistics distributions captured is the value set by the distribution count command times the value set by the maximum hops command times the value set by the maximum path command times the value set by the buckets command.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to set the number of statistics distribution for the distribution count command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# statistics hourly
RP/0/RP0/CPU0:router(config-ipsla-op-stats)# distribution count 15
Related Commands
Command
|
Description
|
buckets (hourly)
|
Sets the number of hours in which statistics are kept.
|
distribution interval
|
Sets the time interval (in milliseconds) for each statistical distribution.
|
maximum hops
|
Sets the number of hops in which statistics are maintained for each path for the IP SLA operation.
|
maximum paths (IP SLA)
|
Sets the number of paths in which statistics are maintained for each hour for an IP SLA operation.
|
statistics
|
Sets the statistics collection parameters for the operation.
|
distribution interval
To set the time interval (in milliseconds) for each statistical distribution, use the distribution interval command in IP SLA operation statistics configuration mode. To use the default value, use the no form of this command.
distribution interval interval
no distribution interval
Syntax Description
interval
|
Number of milliseconds used for each statistics distribution that is kept. The range is 1 to 100. The default value is 20.
|
Defaults
The default value is 20.
Command Modes
IP SLA operation statistics configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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 count, use the distribution count command in IP SLA operation statistics configuration mode. The total number of statistics distributions captured is the value set by the distribution count command times the value set by the maximum hops command times the value set by the maximum path command times the value set by the buckets command.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to set the time interval for the distribution interval command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# statistics hourly
RP/0/RP0/CPU0:router(config-ipsla-op-stats)# distribution interval 50
Related Commands
Command
|
Description
|
buckets (hourly)
|
Sets the number of hours in which statistics are kept.
|
distribution count
|
Sets the number of statistics distributions that are kept for each hop during the lifetime of the IP SLA operation.
|
maximum hops
|
Sets the number of hops in which statistics are maintained for each path for the IP SLA operation.
|
maximum paths (IP SLA)
|
Sets the number of paths in which statistics are maintained for each hour for an IP SLA operation.
|
statistics
|
Sets the statistics collection parameters for the operation.
|
filter
To define the type of information that are kept in the history table for the IP SLA operation, use the filter command in IP SLA operation history configuration mode. To unset the history filter, use the no form of this command.
filter {all | failures}
no filter
Syntax Description
all
|
Stores history data for all operations, if set.
|
failures
|
Stores data for operations that failed, if set.
|
Defaults
The default is not to collect the history unless the filter command is enabled.
Command Modes
IP SLA operation history configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The filter command is available only to IP SLA ICMP Path-Echo operation, IP SLA ICMP Echo operation, and IP SLA UDP Echo operation.
If you use the no form of the filter command, the history statistics are not collected.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the filter command in IP SLA UDP Echo configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp echo
RP/0/RP0/CPU0:router(config-ipsla-udp-echo)# history
RP/0/RP0/CPU0:router(config-ipsla-op-hist)# filter all
Related Commands
frequency (IP SLA)
To set the frequency for probing, use the frequency command in IP SLA ICMP Path-Jitter configuration mode, IP SLA ICMP Path-Echo configuration mode, IP SLA ICMP Echo configuration mode, IP SLA UDP Echo configuration mode, or IP SLA UDP Jitter configuration mode. To use the default value, use the no form of this command.
frequency seconds
no frequency
Syntax Description
seconds
|
Rate at which the specific IP SLA operation is sent into the network. The range is from 1 to 604800.
|
Defaults
If the frequency command is not used, the default value is 60 seconds.
Command Modes
IP SLA UDP Echo configuration
IP SLA UDP Jitter configuration
IP SLA ICMP Path-Jitter configuration
IP SLA ICMP Path-Echo configuration
IP SLA ICMP Echo configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the frequency command in IP SLA UDP Jitter configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# frequency 300
Related Commands
history
To configure the history parameters for the IP SLA operation, use the history command in IP SLA ICMP Path-Jitter configuration mode, IP SLA ICMP Path-Echo configuration mode, IP SLA ICMP Echo configuration mode, IP SLA UDP Echo configuration mode, or IP SLA UDP Jitter configuration mode. To use the default value, use the no form of this command.
history
no history
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
IP SLA UDP Echo configuration
IP SLA UDP Jitter configuration
IP SLA ICMP Path-Jitter configuration
IP SLA ICMP Path-Echo configuration
IP SLA ICMP Echo configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The history command enters IP SLA operation history configuration mode in which you can configure more history configuration parameters.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the history command in IP SLA UDP Echo configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp echo
RP/0/RP0/CPU0:router(config-ipsla-udp-echo)# history
RP/0/RP0/CPU0:router(config-ipsla-op-hist)#
Related Commands
Command
|
Description
|
buckets (history command)
|
Sets the number of history buckets that are kept during the lifetime of the IP SLA operation.
|
filter
|
Defines the type of information that are kept in the history table for the IP SLA operation.
|
ipsla operation
|
Configures an IP SLA operation.
|
ipsla schedule operation
|
Schedules an IP SLA operation.
|
lives
|
Sets the number of lives that are maintained in the history table for an IP SLA operation.
|
samples
|
Sets the number of hop entries that are kept in the history table for an IP SLA ICMP Path-Echo operation.
|
ipsla key-chain
To configure the MD5 authentication for the IP SLA control message, use the ipsla key-chain command in configuration mode. To unset the key chain name and not use MD5 authentication, use the no form of this command.
ipsla key-chain key-chain name
no ipsla key-chain key-chain name
Syntax Description
key-chain name
|
Name of the key chain.
|
Defaults
No default values are defined. No authentication is used.
Command Modes
Global configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When you configure the ipsla key-chain command, you must also configure the key chain command to provide MD5 authentication.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the ipsla key-chain command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla key-chain ipsla-keys
Related Commands
Command
|
Description
|
key chain
|
Creates or modifies a key chain. For more information, see Cisco IOS XR System Security Command Reference.
|
ipsla operation
|
Configures an IP SLA operation.
|
ipsla schedule operation
|
Schedules an IP SLA operation.
|
ipsla low-memory
To configure a low-water memory mark, use the ipsla low-memory command in global configuration mode. To use the default value, use the no form of this command.
ipsla low-memory value
no ipsla low-memory
Syntax Description
value
|
Low-water memory mark value. The range is from 0 to 4294967295.
|
Defaults
The default value is 20 MB (free memory).
Command Modes
Global configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
IP SLA ensures that the system provides the specified memory before adding new operations or scheduling the pending operation.
When the 0 value is used, no memory limitation is enforced.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the ipsla low-memory command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla low-memory 102400
Related Commands
ipsla operation
To configure an IP SLA operation, use the ipsla operation command in global configuration mode. To remove the operation, use the no form of this command.
ipsla operation operation-number
no ipsla operation operation-number
Syntax Description
operation-number
|
Operation number. The range is from 1 to 2048.
|
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the ipsla operation command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)#
Related Commands
ipsla reaction operation
To configure certain actions that are based on events under the control of the IP SLA agent, use the ipsla reaction operation command in global configuration mode.To remove the reaction so no reaction will occur, use the no form of this command.
ipsla reaction operation operation-number
no ipsla reaction operation operation-number
Syntax Description
operation-number
|
Number of the IP SLA operations for the reactions to be configured. The range is from 1 to 2048.
|
Defaults
No reaction is configured.
Command Modes
Global configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the ipsla reaction operation command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla reaction operation 1
RP/0/RP0/CPU0:router(config-ipsla-react)#
Related Commands
ipsla reaction trigger
To define a second IP SLA operation to make the transition from a pending state to an active state when one of the trigger-type options is defined with the ipsla reaction operation command, use the ipsla reaction trigger command in global configuration mode. To remove the reaction trigger and the triggering-operation argument does not trigger any other operation, use the no form of this command.
ipsla reaction trigger [triggering-operation] [triggered-operation]
no ipsla reaction trigger [triggering-operation] [triggered-operation]
Syntax Description
triggering-operation
|
Operation that contains a configured action-type trigger and can generate reaction events. The range is from 1 to 2048.
|
triggered-operation
|
Operation that is started when the triggering-operation argument generates a trigger reaction event. The range is from 1 to 2048.
|
Defaults
No triggered operation is configured.
Command Modes
Global configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Both the triggering-operation and triggered-operation arguments must be configured. The triggered operation must be in the pending state.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the ipsla reaction trigger command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla reaction trigger 1 2
Related Commands
ipsla responder
To enable the IP SLA responder for UDP echo or jitter operations, use the ipsla responder command in global configuration mode. To disable the responder, use the no form of this command.
ipsla responder
no ipsla responder
Syntax Description
This command has no arguments or keywords.
Defaults
The ipsla responder command is disabled.
Command Modes
Global configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
An IP address and port are configured and identified as a permanent port (for example, a port to which the responder is permanently listening). If no IP address and port are configured, the responder handles only dynamic ports (for example, ports that are listened to when requested by a remote operation).
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to enable the IP SLA responder for the ipsla responder command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla responder
RP/0/RP0/CPU0:router(config-ipsla-resp)#
Related Commands
Command
|
Description
|
type udp ipv4 address
|
Configures a permanent port in the IP SLA Responder for UDP echo or jitter operations
|
ipsla schedule operation
To enter schedule configuration mode, use the ipsla schedule operation command in IP SLA schedule configuration mode. To remove the scheduler, use the no form of this command.
ipsla schedule operation operation-number
no ipsla schedule operation operation-number
Syntax Description
operation-number
|
Configuration number or schedule number that is used to schedule an IP SLA operation. The range is from 1 to 2048.
|
Defaults
No default behavior or values
Command Modes
IP SLA schedule configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The ipsla schedule operation command enters the IP SLA schedule configuration mode. You can configure more schedule configuration parameters to schedule the operation.When an operation is scheduled, it continues collecting information until the configured life expires.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the ipsla schedule operation command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla schedule operation 1
RP/0/RP0/CPU0:router(config-ipsla-sched)#
Related Commands
Command
|
Description
|
ipsla operation
|
Configures an IP SLA operation.
|
life
|
Specifies the length of time to execute.
|
recurring
|
Indicates that the operation starts automatically at the specified time and for the specified duration every day.
|
start-time
|
Determines the time when the operation starts.
|
life
To specify the length of time to execute, use the life command in IP SLA schedule configuration mode. To use the default value, use the no form of this command.
life {forever | seconds}
no life
Syntax Description
forever
|
Schedules the operation to run indefinitely.
|
seconds
|
Determines the number of seconds the operation actively collects information. The range is one second to 2147483647 seconds. The default value is 3600 seconds or one hour.
|
Defaults
The default value is 3600 seconds.
Command Modes
IP SLA schedule configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the life command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla schedule operation 1
RP/0/RP0/CPU0:router(config-ipsla-sched)# life forever
Related Commands
lives
To set the number of lives that are maintained in the history table for an IP SLA operation, use the lives command in IP SLA operation history configuration mode. To use the default value, use the no form of this command.
lives lives
no lives
Syntax Description
lives
|
Number of lives that are maintained in the history table for an IP SLA operation. The range is 0 to 2.
|
Defaults
The default value is 0 lives.
Command Modes
IP SLA operation history configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The lives command is available only to IP SLA ICMP Path-Echo operation, IP SLA ICMP Echo operation, and IP SLA UDP Echo operation.
If you use the no form of the lives command, the history statistics are not collected.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the lives command in IP SLA UDP Echo configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp echo
RP/0/RP0/CPU0:router(config-ipsla-udp-echo)# history
RP/0/RP0/CPU0:router(config-ipsla-op-hist)# lives 2
Related Commands
Command
|
Description
|
buckets (history command)
|
Sets the number of history buckets that are kept during the lifetime of the IP SLA operation.
|
filter
|
Defines the type of information that are kept in the history table for the IP SLA operation.
|
ipsla operation
|
Configures an IP SLA operation.
|
ipsla schedule operation
|
Schedules an IP SLA operation.
|
samples
|
Sets the number of hop entries that are kept in the history table for an IP SLA ICMP Path-Echo operation.
|
lsr-path
To specify a loose source routing path in which to measure the ICMP, use the lsr-path command in IP SLA ICMP Path-Jitter configuration mode or IP SLA ICMP Path-Echo configuration mode. To not use the specified path, use the no form of this command.
lsr-path ipaddress1 {ipaddress2 {... {ipaddress8}}}
no lsr-path
Syntax Description
ip address
|
IP address of the intermediate node.
|
Defaults
No path is configured.
Command Modes
IP SLA ICMP Path-Jitter configuration
IP SLA ICMP Path-Echo configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The lsr-path command applies only to ICMP Path-Echo and ICMP Path-Jitter operation types.
You can configure up to a maximum of eight hop addresses by using the lsr-path command, as shown in the following example:
lsr-path ipaddress1 {ipaddress2 {... {ipaddress8}}}
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the lsr-path command in IP SLA ICMP Path Echo configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type icmp path-echo
RP/0/RP0/CPU0:router((config-ipsla-icmp-path-echo)# lsr-path 20.25.22.1
Related Commands
maximum hops
To set the number of hops in which statistics are maintained for each path for the IP SLA operation, use the maximum hops command in IP SLA operation statistics configuration mode. To use the default value, use the no form of this command.
maximum hops hops
no maximum hops
Syntax Description
hops
|
Number of hops for which statistics are maintained for each path. The range is 1 to 30. The default value is 16 for path operations; for example, pathecho.
|
Defaults
The default value is 16 hops.
Command Modes
IP SLA operation statistics configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The maximum hops command is available only in path operations and for the IP SLA ICMP Path-Echo configuration.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to set the number of hops for the statistics for the maximum command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type icmp path-echo
RP/0/RP0/CPU0:router(config-ipsla-icmp-path-echo)# statistics hourly
RP/0/RP0/CPU0:router(config-ipsla-op-stats)# maximum hops 20
Related Commands
Command
|
Description
|
buckets (hourly)
|
Sets the number of hours in which statistics are kept.
|
distribution count
|
Sets the number of statistics distributions that are kept for each hop during the lifetime of the IP SLA operation.
|
distribution interval
|
Sets the time interval (in milliseconds) for each statistical distribution.
|
maximum paths (IP SLA)
|
Sets the number of paths in which statistics are maintained for each hour for an IP SLA operation.
|
statistics
|
Sets the statistics collection parameters for the operation.
|
maximum paths (IP SLA)
To set the number of paths in which statistics are maintained for each hour for an IP SLA operation, use the maximum paths command in IP SLA operation statistics configuration mode. To use the default value, use the no form of this command.
maximum paths paths
no maximum paths
Syntax Description
paths
|
Number of paths for which statistics are maintained for each hour. The range is 1-128. The default value is 5 for path operations; for example, pathecho.
|
Defaults
The default value is 5 paths.
Command Modes
IP SLA operation statistics configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The maximum paths command is available only in path operations and for the IP SLA ICMP Path-Echo configuration.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to set the number of paths for the statistics for the maximum paths command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type icmp path-echo
RP/0/RP0/CPU0:router(config-ipsla-icmp-path-echo)# statistics hourly
RP/0/RP0/CPU0:router(config-ipsla-op-stats)# maximum paths 20
Related Commands
Command
|
Description
|
buckets (hourly)
|
Sets the number of hours in which statistics are kept.
|
distribution count
|
Sets the number of statistics distributions that are kept for each hop during the lifetime of the IP SLA operation.
|
distribution interval
|
Sets the time interval (in milliseconds) for each statistical distribution.
|
maximum hops
|
Sets the number of hops in which statistics are maintained for each path for the IP SLA operation.
|
statistics
|
Sets the statistics collection parameters for the operation.
|
packet count
To specify the number of packets that are to be transmitted during a probe, such as a sequence of packets being transmitted for a jitter probe, use the packet count command in IP SLA ICMP Path-Jitter configuration mode or IP SLA UDP Jitter configuration mode. To use the default value, use the no form of this command.
packet count count
no packet count
Syntax Description
count
|
Number of packets to be transmitted in each operation. For UDP Jitter operation, the range is 1 to 60000. For ICMP Path-Jitter operation, the range is 1 to 100.
|
Defaults
The default packet count is 10.
Command Modes
IP SLA UDP Jitter configuration
IP SLA ICMP Path-Jitter configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the packet count command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# packet count 30
Related Commands
packet interval
To specify the interval between packets, use the packet interval command in IP SLA ICMP Path-Jitter configuration mode or IP SLA UDP Jitter configuration mode. To use the default value, use the no form of this command.
packet interval interval
no packet interval
Syntax Description
interval
|
Interpacket interval in milliseconds. The range is 1 to 60000 (in milliseconds).
|
Defaults
The default packet interval is 20 ms.
Command Modes
IP SLA UDP Jitter configuration
IP SLA ICMP Path-Jitter configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the packet interval command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# packet interval 30
Related Commands
react
To specify an element to be monitored for a reaction, use the react command in IP SLA reaction configuration mode. To remove the specified reaction type, use the no form of this command.
react [connection-loss | jitter-average {dest-to-source | source-to-dest}| packet-loss
[dest-to-source | source-to-dest] | rtt | timeout | verify-error]
no react [connection-loss | jitter-average {dest-to-source | source-to-dest}| packet-loss
{dest-to-source | source-to-dest}| rtt | timeout | verify-error]
Syntax Description
connection-loss
|
Specifies that a reaction occurs if there is a connection-loss for the monitored operation.
|
jitter-average {dest-to-source | source-to-dest}
|
Specifies that a reaction occurs if the average round-trip jitter value violates the upper threshold or lower threshold. The following options are listed for the jitter-average keyword:
• dest-to-source—Specifies the jitter average destination to source (DS).
• source-to-dest—Specifies the jitter average source to destination (SD).
|
packet-loss [dest-to-source | source-to-dest]
|
Specifies the reaction on packet loss value violation. The following options are listed for the packet-loss keyword:
• dest-to-source—Specifies the packet loss destination to source (DS) violation.
• source-to-dest—Specifies the packet loss source to destination (SD) violation.
|
rtt
|
Specifies that a reaction occurs if the round-trip value violates the upper threshold or lower threshold.
|
timeout
|
Specifies that a reaction occurs if there is a timeout for the monitored operation.
|
verify-error
|
Specifies that a reaction occurs if there is an error verification violation
|
Defaults
If there is no default value, no reaction is configured.
Command Modes
IP SLA reaction configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
For the connection-loss keyword, jitter-average keyword, and rtt keyword, the reaction does not occur when the value violates the upper or the lower threshold. The reaction condition is set when the upper threshold is passed, and it is cleared when values go below the lower threshold.
For the connection-loss keyword and verify-error keyword, thresholds do not apply to the monitored element.
For the jitter-average keyword, packet-loss keyword, and rtt keyword, if the upper threshold for react threshold type average 3 is configured as 5000 ms and the last three results of the operation are 6000, 6000, and 5000 ms, the average is 6000 + 6000 + 5000=17000/3 = 5667—therefore violating the 5000-ms upper threshold. The threshold type average must be configured when setting the type. These keywords are not available if connection-loss, timeout, or verify-error is specified as the monitored element, because upper and lower thresholds do not apply to these options.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the react command with the connection-loss keyword:
The following example shows how to use the react connection-loss command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla reaction operation 432
RP/0/RP0/CPU0:router(config-ipsla-react)# react connection-loss
RP/0/RP0/CPU0:router(config-ipsla-react-cond)#
The following example shows how to use the react command with the jitter-average keyword:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla reaction operation 432
RP/0/RP0/CPU0:router(config-ipsla-react)# react jitter-average
RP/0/RP0/CPU0:router(config-ipsla-react-cond)#
The following example shows how to use the react command with the packet-loss keyword:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla reaction operation 432
RP/0/RP0/CPU0:router(config-ipsla-react)# react packet-loss dest-to-source
RP/0/RP0/CPU0:router(config-ipsla-react-cond)#
The following example shows how to use the react command with the rtt keyword:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla reaction operation 432
RP/0/RP0/CPU0:router(config-ipsla-react)# react rtt
RP/0/RP0/CPU0:router(config-ipsla-react-cond)#
The following example shows how to use the react command with the timeout keyword:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla reaction operation 432
RP/0/RP0/CPU0:router(config-ipsla-react)# react timeout
RP/0/RP0/CPU0:router(config-ipsla-react-cond)#
The following example shows how to use the react command with the verify-error keyword:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla reaction operation 432
RP/0/RP0/CPU0:router(config-ipsla-react)# react verify-error
RP/0/RP0/CPU0:router(config-ipsla-react-cond)#
Related Commands
recurring
To indicate that the operation starts automatically at the specified time and for the specified duration every day, use the recurring command in IP SLA schedule configuration mode. To not start the operation everyday, use the no form of this command.
recurring
no recurring
Syntax Description
This command has no arguments or keywords.
Defaults
Recurring is disabled.
Command Modes
IP SLA schedule configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the recurring command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla schedule operation 1
RP/0/RP0/CPU0:router(config-ipsla-sched)# recurring
Related Commands
samples
To set the number of hop entries that are kept in the history table for an IP SLA ICMP Path-Echo operation, use the samples command in IP SLA operation history configuration mode. To use the default value, use the no form of this command.
samples sample count
no samples
Syntax Description
sample count
|
Number of history samples that are kept in the history table for an IP SLA ICMP Path-Echo operation. The range is from 1 to 30.
|
Defaults
The default value is 16.
Command Modes
IP SLA operation history configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The samples command is available only to IP SLA ICMP Path-Echo operation.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the samples command in IP SLA ICMP Path-Echo configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp echo
RP/0/RP0/CPU0:router(config-ipsla-icmp-path-echo)# history
RP/0/RP0/CPU0:router(config-ipsla-op-hist)# samples 30
Related Commands
Command
|
Description
|
buckets (history command)
|
Sets the number of history buckets that are kept during the lifetime of the IP SLA operation.
|
filter
|
Defines the type of information that are kept in the history table for the IP SLA operation.
|
history
|
Configures the history parameters for the IP SLA operation.
|
ipsla operation
|
Configures an IP SLA operation.
|
ipsla schedule operation
|
Schedules an IP SLA operation.
|
show ipsla application
To display the information for the IP SLA application, use the show ipsla application command in EXEC mode.
show ipsla application
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read
|
Examples
The following sample output is from the show ipsla application command:
RP/0/RP0/CPU0:router# show ipsla application
IP Service Level Aggrement Agent Version: 1.0.0
Estimated system max number of entries: 2048
Number of Entries configured: 1
Number of active Entries : 0
Number of pending Entries : 0
Number of inactive Entries : 1
Supported Operation Types: 5
Type of Operation: ICMP ECHO
Type of Operation: ICMP PATH JITTER
Type of Operation: ICMP PATH ECHO
Type of Operation: UDP JITTER
Type of Operation: UDP ECHO
Number of configurable probes : 2047
SA Agent low memory water mark: 20480 (KB)
Table 1 describes the significant fields shown in the display.
Table 1 show ipsla application Field Descriptions
Field
|
Description
|
Version
|
Version of the IP SLA.
|
Estimated system max number of entries
|
Maximum number of operations that are configured in the system. The low-memory configured parameter and the available memory in the system are given.
|
Number of Entries configured
|
Total number of entries that are configured, such as active state, pending state, and inactive state.
|
Number of active Entries
|
Number of entries that are in the active state. The active entries are scheduled and have already started a life period.
|
Number of pending Entries
|
Number of entries that are in pending state. The pending entries have a start-time scheduled in the future. These entries either have not started the first life, or the entries are configured as recurring and completed one of its life.
|
Number of inactive Entries
|
Number of entries that are in the inactive state. The inactive entries do not have a start-time scheduled. Either the start-time has never been scheduled or life has expired. In addition, the entries are not configured as recurring.
|
Supported Operation Types
|
Types of operations that are supported by the system.
|
Number of configurable probes
|
Number of remaining entries that can be configured. The number is just an estimated value and it may vary over time according to the available resources.
|
SA Agent low memory water mark
|
Available memory for the minimum system below which the IP SLA feature does not configure any more operations.
|
Related Commands
show ipsla history
To display the history collected for all IP SLA operations or for a specified operation, use the show ipsla history command in EXEC mode.
show ipsla history [op_num]
Syntax Description
op_num
|
(Optional) Number of the IP SLA operation.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
By default, history statistics are not collected. To have any data displayed by using the show ipsla history command, you must configure the history collection.
Table 2 lists the response return values that are used in the show ipsla history command.
Table 2 Response Return Values for the show ipsla history Command
Code
|
Description
|
1
|
Okay
|
2
|
Disconnected
|
3
|
Over Threshold
|
4
|
Timeout
|
5
|
Busy
|
6
|
Not Connected
|
7
|
Dropped
|
8
|
Sequence Error
|
9
|
Verify Error
|
10
|
Application Specific
|
If the default tabular format is used, the response return description is displayed as code in the Sense column. The Sense field is always used as a return code.
Task ID
Task ID
|
Operations
|
monitor
|
read
|
Examples
The following sample output is from the show ipsla history command:
RP/0/RP0/CPU0:router# show ipsla history 1
SampleT = Sample start time
CompT = RTT (milliseconds)
Sense = Response return code
Line 2 has the Target Address
Entry LifeI BucketI SampleI SampleT CompT Sense
1 0 0 0 1134419252539 9 1
1 0 1 0 1134419312509 6 1
1 0 2 0 1134419372510 6 1
1 0 3 0 1134419432510 5 1
Table 3 describes the significant fields shown in the display.
Table 3 show ipsla history Field Descriptions
Field
|
Description
|
Entry number
|
Entry number.
|
LifeI
|
Life index.
|
BucketI
|
Bucket index.
|
SampleI
|
Sample index.
|
SampleT
|
Sample start time.
|
CompT
|
Completion time in milliseconds.
|
Sense
|
Response return code.
|
TargetAddr
|
IP address of intermediate hop device or destination device.
|
Related Commands
show ipsla responder statistics ports
To display the number of probes that are received or handled by the currently active ports on the responder, use the show ipsla responder statistics ports command in EXEC mode.
show ipsla responder statistics ports
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The output of the show ipsla responder statistics port command is available only for specific intervals of time in which only nonpermanent ports are being used at the responder. The reason is that the responder closes the nonpermanent ports after each operation cycle. However, if both permanent and nonpermanent ports are used, the output always contains rows for the permanent ports. The rows for the nonpermanent ports are displayed only if those nonpermanent ports are enabled at the instant the command is issued.
Task ID
Task ID
|
Operations
|
monitor
|
read
|
Examples
The following sample output is from the show ipsla responder statistics port command:
RP/0/RP0/CPU0:router# show ipsla responder statistics port
Port 12709 Local Address 12.29.11.21
Port 12213 Local Address 12.29.11.21
Port 55690 Local Address 12.29.11.21
Table 4 describes the significant fields shown in the display.
Table 4 show ipsla responder statistics port Field Descriptions
Field
|
Description
|
Port
|
Port number at which the responder is waiting for probe packets.
|
Local Address
|
IP address at which the responder is waiting for probe packets.
|
NumberOfProbes
|
Number of packets at which the responder has received for both control packets and probe packets.
|
show ipsla statistics
To display the operational data and the latest statistics for the IP SLA operation in tabular format, use the show ipsla statistics command in EXEC mode.
show ipsla statistics [operation-number]
Syntax Description
operation-number
|
(Optional) Operation for which the latest statistics are to be displayed. The range is from 1 to 2048.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read
|
Examples
The output of the show ipsla statistics command varies depending on the operation type. The following sample output is from the show ipsla statistics command for an ICMP echo operation:
RP/0/RP0/CPU0:router# show ipsla statistics 1
Modification time: 20:27:30.989 UTC Mon Dec 12 2005
Start time : 20:27:30.992 UTC Mon Dec 12 2005
Number of operations attempted: 10
Number of operations skipped : 0
Current seconds left in Life : 3047
Operational state of entry : Active
Connection loss occurred : FALSE
Latest RTT (milliseconds) : 5
Latest operation start time : 20:36:32.510 UTC Mon Dec 12 2005
Latest operation return code : OK
RTTAvg : 5 RTTMin: 5 RTTMax : 5
NumOfRTT: 1 RTTSum: 5 RTTSum2: 25
Table 5 describes the significant fields shown in the display.
Table 5 show ipsla statistics Field Descriptions
Field
|
Description
|
Entry number
|
Entry number.
|
Modification time
|
Latest time the operation was modified.
|
Start time
|
Time the operation was started.
|
Number of operations attempted
|
Number of operation cycles that were issued.
|
Number of operations skipped
|
Number of operation cycles that were not issued because one of the cycles extended over the configured time interval.
|
Current seconds left in Life
|
Time remaining until the operation stops execution.
|
Operational state of entry
|
State of the operation, such as active state, pending state, or inactive state.
|
Connection loss occurred
|
Whether or not a connection-loss error happened.
|
Timeout occurred
|
Whether or not a timeout error happened.
|
Latest RTT (milliseconds)
|
Value of the latest RTT sample.
|
Latest operation start time
|
Time the latest operation cycle was issued.
|
Latest operation return code
|
Return code of the latest operation cycle
|
RTTAvg
|
Average RTT value that is observed in the last cycle.
|
RTTMin
|
Minimum RTT value that is observed in the last cycle.
|
RTTMax
|
Maximum RTT value that is observed in the last cycle.
|
NumOfRTT
|
Number of successful round trips.
|
RTTSum
|
Sum of all successful round-trip values in milliseconds.
|
RTTSum2
|
Sum of squares of the round-trip values in milliseconds.
|
Related Commands
show ipsla statistics aggregated
To display the hourly statistical errors and the hourly statistics for all the IP SLA operations or specified operation, use the show ipsla statistics aggregated command in EXEC mode.
show ipsla statistics aggregated [operation-number]
Syntax Description
operation-number
|
(Optional) Number of IP SLA operations. The range is from 1 to 2048.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The show ipsla statistics aggregated command displays information such as the number of failed operations and the reason for failure. Unless you configured a different amount of time for the buckets command (statistics command with hourly keyword), the show ipsla statistics aggregated command displays the information collected over the past two hours.
For one-way delay and jitter operations to be computed for UDP Jitter operations, the clocks on local and target devices must be synchronized using NTP or GPS systems. If the clocks are not synchronized, one-way measurements are discarded. If the sum of the source to destination (SD) and the destination to source (DS) values is not within 10 percent of the round-trip time, the one-way measurement values are assumed to be faulty, and are discarded.
Task ID
Task ID
|
Operations
|
monitor
|
read
|
Examples
The output of the show ipsla statistics aggregated command varies depending on operation type. The following sample output shows the aggregated statistics for UDP echo operation from the show ipsla statistics aggregated command:
RP/0/RP0/CPU0:router# show ipsla statistics aggregated 1
Start Time Index: 21:02:32.510 UTC Mon Dec 12 2005
Number of Failed Operations due to a Disconnect : 0
Number of Failed Operations due to a Timeout : 0
Number of Failed Operations due to a Busy : 0
Number of Failed Operations due to a No Connection : 0
Number of Failed Operations due to an Internal Error: 0
Number of Failed Operations due to a Sequence Error : 0
Number of Failed Operations due to a Verify Error : 0
RTTAvg : 6 RTTMin: 4 RTTMax : 38
NumOfRTT: 36 RTTSum: 229 RTTSum2: 2563
Table 6 describes the show ipsla statistics aggregated command field descriptions.
The following sample output is from the show ipsla statistics aggregated command in which operation 10 is a UDP Jitter operation:
RP/0/RP0/CPU0:router# show ipsla statistics aggregated 10
Start Time Index: 00:35:07.895 UTC Thu Mar 16 2006
Number of Failed Operations due to a Disconnect : 0
Number of Failed Operations due to a Timeout : 0
Number of Failed Operations due to a Busy : 0
Number of Failed Operations due to a No Connection : 0
Number of Failed Operations due to an Internal Error: 0
Number of Failed Operations due to a Sequence Error : 0
Number of Failed Operations due to a Verify Error : 0
RTTAvg : 14 RTTMin: 2 RTTMax : 99
NumOfRTT: 70 RTTSum: 1034 RTTSum2: 60610
PacketLossSD : 0 PacketLossDS: 0
PacketOutOfSequence: 0 PacketMIA : 0
MinOfPositivesSD: 1 MaxOfPositivesSD: 19
NumOfPositivesSD: 17 SumOfPositivesSD: 65
MinOfNegativesSD: 1 MaxOfNegativesSD: 16
NumOfNegativesSD: 24 SumOfNegativesSD: 106
MinOfPositivesDS: 1 MaxOfPositivesDS: 7
NumOfPositivesDS: 17 SumOfPositivesDS: 44
MinOfNegativesDS: 1 MaxOfNegativesDS: 8
NumOfNegativesDS: 24 SumOfNegativesDS: 63
Interarrival jitterout: 0 Interarrival jitterin: 0
OWMinSD : 0 OWMaxSD: 0 OWSumSD: 0
OWMinDS : 0 OWMaxDS: 0 OWSumDS: 0
Table 6 describes the significant fields shown in the display.
Table 6 show ipsla statistics aggregated Field Descriptions
Field
|
Description
|
Busies
|
Number of times that the operation cannot be started because the previously scheduled run was not finished.
|
Entry Number
|
Entry number.
|
Hop in Path Index
|
Hop in path index.
|
Errors
|
Number of internal errors.
|
Jitter Values
|
Jitter statistics appear on the specified lines. Jitter is defined as interpacket delay variance.
|
NumOfJitterSamples
|
Number of jitter samples that are collected. The number of samples are used to calculate the jitter statistics.
|
Number of Failed Operations due to a Disconnect
|
Number of failed operations due to a disconnect.
|
Number of Failed Operations due to a Timeout
|
Number of failed operations due to a timeout.
|
Number of Failed Operations due to a Busy
|
Number of failed operations due to a busy error.
|
Number of Failed Operations due to a No Connection
|
Error that refers to the case in which the control connection cannot be established.
|
Number of Failed Operations due to an Internal Error
|
Number of failed operations due to an internal error.
|
Number of Failed Operations due to a Sequence Error
|
Number of failed operations due to a sequence error.
|
Number of Failed Operations due to a Verify Error
|
Number of failed operations due to a verify error.
|
MaxOfNegativesSD
|
Maximum negative jitter values from the source to the destination. The absolute value is given.
|
MaxOfPositivesSD
|
Maximum jitter values from the source to the destination in milliseconds.
|
MaxOfPositivesDS
|
Maximum jitter values from the destination to the source in milliseconds.
|
MaxOfNegativesDS
|
Maximum negative jitter values from destination-to-source. The absolute value is given.
|
MinOfPositivesDS
|
Minimum jitter values from the destination to the source in milliseconds.
|
MinOfNegativesSD
|
Minimum negative jitter values from the source to the destination. The absolute value is given.
|
MinOfPositivesSD
|
Minimum jitter values from the source to the destination in milliseconds.
|
MinOfNegativesDS
|
Minimum negative jitter values from the destination to the source. The absolute value is given.
|
NumOfOW
|
Number of successful one-way time measurements.
|
NumOfNegativesDS
|
Number of jitter values from the destination to the source that are negative; for example, network latency decreases for two consecutive test packets.
|
NumOfNegativesSD
|
Number of jitter values from the source to the destination that are negative; for example, network latency decreases for two consecutive test packets.
|
NumOfPositivesDS
|
Number of jitter values from the destination to the source that are positive; for example, network latency increases for two consecutive test packets.
|
NumOfPositivesSD
|
Number of jitter values from the source to the destination that are positive; for example, network latency increases for two consecutive test packets.
|
NumOfRTT
|
Number of successful round trips.
|
One Way Values
|
One-way measurement statistics appear on the specified lines. One Way (OW) values are the amount of time that it took the packet to travel from the source router to the target router or from the target router to the source router.
|
OWMaxDS
|
Maximum time from the destination to the source.
|
OWMaxSD
|
Maximum time from the source to the destination.
|
OWMinDS
|
Minimum time from the destination to the source.
|
OWMinSD
|
Minimum time from the source to the destination.
|
OWSumDS
|
Sum of one-way delay values from the destination to the source.
|
OWSumSD
|
Sum of one-way delay values from the source to the destination.
|
OWSum2DS
|
Sum of squares of one-way delay values from the destination to the source.
|
OWSum2SD
|
Sum of squares of one-way delay values from the source to the destination.
|
PacketLateArrival
|
Number of packets that arrived after the timeout.
|
PacketLossDS
|
Number of packets lost from the destination to the source (DS).
|
PacketLossSD
|
Number of packets lost from the source to the destination (SD).
|
PacketMIA
|
Number of packets lost in which the SD direction or DS direction cannot be determined.
|
PacketOutOfSequence
|
Number of packets that are returned out of order.
|
Path Index
|
Path index.
|
Port Number
|
Target port number.
|
RTTSum
|
Sum of all successful round-trip values in milliseconds.
|
RTTSum2
|
Sum of squares of the round-trip values in milliseconds.
|
RTT Values
|
Round-trip time statistics appear on the specified lines.
|
Start Time
|
Start time, in milliseconds.
|
Start Time Index
|
Statistics that are aggregated for over 1-hour intervals. The value indicates the start time for the 1-hour interval that is displayed.
|
SumOfPositivesDS
|
Sum of the positive jitter values from the destination to the source.
|
SumOfPositivesSD
|
Sum of the positive jitter values from the source to the destination.
|
SumOfNegativesDS
|
Sum of the negative jitter values from the destination to the source.
|
SumOfNegativesSD
|
Sum of the negative jitter values from the source to the destination.
|
Sum2PositivesDS
|
Sum of squares of the positive jitter values from the destination to the source.
|
Sum2PositivesSD
|
Sum of squares of the positive jitter values from the source to the destination.
|
Sum2NegativesDS
|
Sum of squares of the negative jitter values from the destination to the source.
|
Sum2NegativesSD
|
Sum of squares of the negative jitter values from the source to the destination.
|
Target Address
|
Target IP address.
|
Related Commands
show ipsla statistics aggregated detail
To display the statistics distribution information that is captured for response times for all IP SLA operations or the specified operation, use the show ipsla statistics aggregated detail command in EXEC mode.
show ipsla statistics aggregated detail [operation-number]
Syntax Description
operation-number
|
(Optional) Number of IP SLA operations. The range is from 1 to 2048.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read
|
Examples
The output of the show ipsla statistics aggregated detail command varies depending on operation type. The following sample output is from the show ipsla statistics aggregated detail command in tabular format, when the output is split over multiple lines:
RP/0/RP0/CPU0:router# show ipsla statistics aggregated detail 2
StartT = Start time of entry (hundredths of seconds)
Dst = Time distribution index
Comps = Operations completed
SumCmp = Sum of RTT (milliseconds)
SumCmp2H = Sum of RTT squared high 32 bits (milliseconds)
SumCmp2L = Sum of RTT squared low 32 bits (milliseconds)
TMax = RTT maximum (milliseconds)
TMin = RTT minimum (milliseconds)
Entry StartT Pth Hop Dst Comps SumCmp
SumCmp2H SumCmp2L TMax TMin
2 1134423910701 1 1 0 12 367
2 1134423851116 1 1 1 2 129
2 1134423070733 1 1 2 1 101
Table 7 describes the significant fields shown in the display.
Table 7 show ipsla statistics aggregated detail Field Descriptions
Field
|
Description
|
Entry
|
Entry number.
|
StartT
|
Start time of entry, in hundredths of seconds.
|
Pth
|
Path index.
|
Hop
|
Hop in path index.
|
Dst
|
Time distribution index.
|
Comps
|
Operations completed.
|
SumCmp
|
Sum of completion times, in milliseconds.
|
SumCmp2L
|
Sum of completion times squared low 32 bits, in milliseconds.
|
SumCmp2H
|
Sum of completion times squared high 32 bits, in milliseconds.
|
TMax
|
Completion time maximum, in milliseconds.
|
TMin
|
Completion time minimum, in milliseconds.
|
Related Commands
show ipsla statistics enhanced aggregated
To display the enhanced history statistics for all collected enhanced history buckets for the specified IP SLA operation, use the show ipsla statistics enhanced aggregated command in EXEC mode.
show ipsla statistics enhanced aggregated [operation-number] [interval seconds]
Syntax Description
operation-number
|
(Optional) Operation number for which to display the enhanced history distribution statistics.
|
interval seconds
|
(Optional) Specifies the aggregation interval in seconds for which to display the enhanced history distribution statistics.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The show ipsla statistics enhanced aggregated command displays data for each bucket of enhanced history data shown individually; for example, one after the other. The number of buckets and the collection interval is set using the interval keyword, seconds argument, buckets keyword, and number-of-buckets argument.
Task ID
Task ID
|
Operations
|
monitor
|
read
|
Examples
The output of the show ipsla statistics enhanced aggregated command varies depending on the operation type. The following sample output is from the show ipsla statistics enhanced aggregated command for the UDP echo operation:
RP/0/RP0/CPU0:router# show ipsla statistics enhanced aggregated 20
Bucket : 1 (0 - 300 seconds)
Start Time Index: 00:38:14.286 UTC Thu Mar 16 2006
Number of Failed Operations due to a Disconnect : 0
Number of Failed Operations due to a Timeout : 0
Number of Failed Operations due to a Busy : 0
Number of Failed Operations due to a No Connection : 0
Number of Failed Operations due to an Internal Error: 0
Number of Failed Operations due to a Sequence Error : 0
Number of Failed Operations due to a Verify Error : 0
RTTAvg : 2 RTTMin: 2 RTTMax : 5
NumOfRTT: 5 RTTSum: 13 RTTSum2: 41
Bucket : 2 (300 - 600 seconds)
Start Time Index: 00:43:12.747 UTC Thu Mar 16 2006
Number of Failed Operations due to a Disconnect : 0
Number of Failed Operations due to a Timeout : 0
Number of Failed Operations due to a Busy : 0
Number of Failed Operations due to a No Connection : 0
Number of Failed Operations due to an Internal Error: 0
Number of Failed Operations due to a Sequence Error : 0
Number of Failed Operations due to a Verify Error : 0
RTTAvg : 2 RTTMin: 2 RTTMax : 2
NumOfRTT: 1 RTTSum: 2 RTTSum2: 4
Table 8 describes the significant fields shown in the display.
Table 8 show ipsla statistics enhanced aggregated Field Descriptions
Field
|
Description
|
Entry Number
|
Entry number.
|
Interval
|
Multiple of the frequency of the operation. The Enhanced interval field defines the interval in which statistics displayed by the show ipsla statistics enhanced aggregated command are aggregated. This field must be configured so that the enhanced aggregated statistics are displayed.
|
Bucket
|
Bucket index.
|
Start Time Index
|
Statistics that are aggregated depends on the interval configuration. The value depends on the interval configuration that is displayed.
|
RTT Values
|
Round-trip time statistics appear on the specified lines.
|
RTT Min/Avg/Max
|
Maximum values of the RTT that are observed in the latest cycle (*).
|
NumOfRTT
|
Number of successful round trips.
|
RTT Sum
|
Sum of all successful round-trip values, in milliseconds.
|
RTT Sum2
|
Sum of squares of the round-trip values, in milliseconds.
|
Number of Failed Operations due to a Disconnect
|
Number of failed operations due to a disconnect.
|
Number of Failed Operations due to a Timeout
|
Number of failed operations due to a timeout.
|
Number of Failed Operations due to a Busy
|
Number of failed operations due to a busy error.
|
Number of Failed Operations due to a No Connection
|
Error that refers to the case in which the control connection cannot be established.
|
Number of Failed Operations due to an Internal Error
|
Number of failed operations due to an internal error.
|
Number of Failed Operations due to a Sequence Error
|
Number of failed operations due to a sequence error.
|
Number of Failed Operations due to a Verify Error
|
Number of failed operations due to a verify error.
|
Related Commands
source address
To identify the address of the source device, use the source address command in IP SLA ICMP Path-Jitter configuration mode, IP SLA ICMP Path-Echo configuration mode, IP SLA ICMP Echo configuration mode, IP SLA UDP Echo configuration mode, or IP SLA UDP Jitter configuration mode. To use the best local address, use the no form of this command.
source address [ipv4 address]
no source address
Syntax Description
ipv4 address
|
(Optional) IP address or hostname of the source device.
|
Defaults
IP SLA finds the best local address to the destination and uses it as the source address.
Command Modes
IP SLA UDP Echo configuration
IP SLA UDP Jitter configuration
IP SLA ICMP Path-Jitter configuration
IP SLA ICMP Path-Echo configuration
IP SLA ICMP Echo configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to designate an IP address for the source address command in IP SLA UDP Jitter configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# source address 12.7.34.10
Related Commands
source port
To identify the port of the source device, use the source port command in IP SLA UDP Echo configuration mode or IP SLA UDP Jitter configuration mode. To use the unused port number, use the no form of this command.
source port [port]
no source port
Syntax Description
port port
|
(Optional) Identifies the port number of the source device. The range is from 1 to 65535.
|
Defaults
IP SLA uses an unused port that is allocated by system.
Command Modes
IP SLA UDP Echo configuration
IP SLA UDP Jitter configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The source port command is not available in ICMP operations and applies only to UDP operations.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to designate a port for the source port command in IP SLA UDP Jitter configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# source port 11111
Related Commands
start-time
To determine the time when the operation starts, use the start-time command in IP SLA schedule configuration mode. To stop the operation and place it in the default state, such as inactive, use the no form of this command.
start-time [hh:mm:ss {day | month day} | now | pending | after hh:mm:ss]
no start-time [hh:mm:ss {day | month day} | now | pending | after hh:mm:ss]
Syntax Description
hh:mm:ss
|
Absolute start time in hours, minutes, and seconds. You can use the 24-hour clock notation. For example, the start-time 01:02 is defined as 1:02 am, or start-time 13:01:30 is defined as start at 1:01 pm. and 30 seconds. The current day is used; unless, you specify a month and day.
|
month
|
(Optional) Name of the month to start the operation. When you use the month argument, you are required to specify a day. You can specify the month by using the full English name or the first three letters of the month.
|
day
|
Number of the day, in the range of 1 to 31, to start the operation. In addition, you must specify a month.
|
now
|
(Optional) Specifies that the operation should start immediately.
|
pending
|
(Optional) Specifies that no information is collected. The default value is the pending keyword.
|
after hh:mm:ss
|
(Optional) Specifies that the operation starts at hh hours, mm minutes, and ss seconds after the ipsla schedule operation command was used.
|
Defaults
If a month and day are not specified, the current month and day are used.
Command Modes
IP SLA schedule configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the start-time command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla schedule operation 1
RP/0/RP0/CPU0:router(config-ipsla-sched)# start-time after 01:00:00
Related Commands
Command
|
Description
|
ipsla operation
|
Configures an IP SLA operation.
|
ipsla schedule operation
|
Schedules an IP SLA operation.
|
life
|
Specifies the length of time to execute.
|
recurring
|
Indicates that the operation starts automatically at the specified time and for the specified duration every day.
|
statistics
To set the statistics collection parameters for the operation, use the statistics command in IP SLA operation statistics configuration mode. To remove the statistics collection or use the default value, use the no form of this command.
statistics {hourly| interval seconds}
no statistics {hourly | interval seconds}
Syntax Description
hourly
|
Sets the distribution for statistics configuration that is aggregated for over an hour.
|
interval seconds
|
Collects statistics over a specified time interval. Interval (in seconds) over which to collect statistics. The range is 1 to 3600 seconds.
|
Defaults
interval keyword: No default behavior or values
Command Modes
IP SLA operation statistics configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Both ICMP Path-Echo and ICMP Path-Jitter operations do not support statistics interval.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to set the number of hours in which statistics are maintained for the IP SLA UDP Jitter operation for the statistics command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# statistics hourly
RP/0/RP0/CPU0:router(config-ipsla-op-stats)#
The following example shows how to collect statistics for a given time interval for the IP SLA UDP Jitter operation for the statistics command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# statistics interval 60
RP/0/RP0/CPU0:router(config-ipsla-op-stats)#
Related Commands
Command
|
Description
|
buckets (hourly)
|
Sets the number of hours in which statistics are kept.
|
buckets (interval)
|
Refers to the data buckets in which the enhanced history statistics are kept,
|
distribution count
|
Sets the number of statistics distributions that are kept for each hop during the lifetime of the IP SLA operation.
|
distribution interval
|
Sets the time interval (in milliseconds) for each statistical distribution.
|
ipsla operation
|
Configures an IP SLA operation.
|
ipsla schedule operation
|
Schedules an IP SLA operation.
|
maximum hops
|
Sets the number of hops in which statistics are maintained for each path for the IP SLA operation.
|
maximum paths (IP SLA)
|
Sets the number of paths in which statistics are maintained for each hour for an IP SLA operation.
|
tag (IP SLA)
To create a user-specified identifier for an IP SLA operation, use the tag command in IP SLA ICMP Path-Jitter configuration mode, IP SLA ICMP Path-Echo configuration mode, IP SLA ICMP Echo configuration mode, IP SLA UDP Echo configuration mode, or IP SLA UDP Jitter configuration mode. To unset the tag string, use the no form of this command.
tag [text]
no tag
Syntax Description
text
|
(Optional) Specifies a string label for the IP SLA operation.
|
Defaults
No tag string is configured.
Command Modes
IP SLA UDP Echo configuration
IP SLA UDP Jitter configuration
IP SLA ICMP Path-Jitter configuration
IP SLA ICMP Path-Echo configuration
IP SLA ICMP Echo configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the tag command in IP SLA UDP Jitter configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# tag ipsla
Related Commands
threshold
To set the lower-limit and upper-limit values, use the threshold command in IP SLA reaction condition configuration mode. To use the default value, use the no form of this command.
threshold lower-limit value upper-limit value
no threshold lower-limit value upper-limit value
Syntax Description
lower-limit value
|
Specifies the threshold lower-limit value. The range is from 1 to 4294967295 ms. The default lower-limit value is 3000 ms.
|
upper-limit value
|
Specifies the threshold upper-limit value. The range is from 5000 to 4294967295 ms. The default upper-limit value is 5000 ms.
|
Defaults
The default lower-limit is 3000 ms.
The default upper-limit is 5000 ms.
Command Modes
IP SLA reaction condition configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The threshold command is available only for the react command with the jitter-average and packet-loss keywords.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to set the lower-limit and upper-limit values for the react command with the jitter-average keyword for the threshold command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla reaction operation 432
RP/0/RP0/CPU0:router(config-ipsla-react)# react jitter-average
RP/0/RP0/CPU0:router(config-ipsla-react-cond)# threshold lower-limit 8000 upper-limit
10000
The following example shows how to set the lower-limit and upper-limit values for the react command with the packet-loss keyword for the threshold command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla reaction operation 432
RP/0/RP0/CPU0:router(config-ipsla-react)# react packet-loss dest-to-source
RP/0/RP0/CPU0:router(config-ipsla-react-cond)# threshold lower-limit 8000 upper-limit
10000
Related Commands
threshold type average
To take action on average values to violate a threshold, use the threshold type average command in IP SLA reaction condition configuration mode. To clear the threshold type (reaction will never happen), use the no form of this command.
threshold type average number-of-probes
no threshold type
Syntax Description
number-of-probes
|
When the average of the last five values for the monitored element exceeds the upper threshold or the average of the last five values for the monitored element drops below the lower threshold, the action is performed as defined by the action command.
|
Defaults
If there is no default value, no threshold type is configured.
Command Modes
IP SLA reaction condition configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The threshold type average command is available only for the react command with the jitter-average, packet-loss, and rtt keywords.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to set the number of probes for the react command with the jitter-average keyword for the threshold type average command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla reaction operation 432
RP/0/RP0/CPU0:router(config-ipsla-react)# react jitter-average
RP/0/RP0/CPU0:router(config-ipsla-react-cond)# threshold type average 8
The following example shows how to set the number of probes for the react command with the packet-loss keyword for the threshold type average command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla reaction operation 432
RP/0/RP0/CPU0:router(config-ipsla-react)# react packet-loss dest-to-source
RP/0/RP0/CPU0:router(config-ipsla-react-cond)# threshold type average 8
Related Commands
threshold type consecutive
To take action after a number of consecutive violations, use the threshold type consecutive command in IP SLA reaction condition configuration mode. To clear the threshold type (reaction will never happen), use the no form of this command.
threshold type consecutive occurrences
no threshold type
Syntax Description
occurrences
|
When the reaction condition is set for a consecutive number of occurrences, there is no default value. The number of occurrences is set when specifying the threshold type. The number of consecutive violations is from 1 to 16.
|
Defaults
No default behavior or values
Command Modes
IP SLA reaction condition configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the threshold type consecutive command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla reaction operation 432
RP/0/RP0/CPU0:router(config-ipsla-react)# react connection-loss
RP/0/RP0/CPU0:router(config-ipsla-react-cond)# threshold type consecutive 8
Related Commands
threshold type immediate
To take action immediately upon a threshold violation, use the threshold type immediate command in IP SLA reaction condition configuration mode. To clear the threshold type (reaction will never happen), use the no form of this command.
threshold type immediate
no threshold type
Syntax Description
This command has no arguments or keywords.
Defaults
If there is no default value, no threshold type is configured.
Command Modes
IP SLA reaction condition configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When the reaction conditions, such as threshold violations, are met for the monitored element, the action is immediately performed as defined by the action command.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the threshold type immediate command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla reaction operation 432
RP/0/RP0/CPU0:router(config-ipsla-react)# react timeout
RP/0/RP0/CPU0:router(config-ipsla-react-cond)# threshold type immediate
Related Commands
threshold type xofy
To take action upon X violations in Y probe operations, use the threshold type xofy command in IP SLA reaction condition configuration mode. To clear the threshold type (reaction will never happen), use the no form of this command.
threshold type xofy X value Y value
no threshold type
Syntax Description
X value Y value
|
When the reaction conditions, such as threshold violations, are met for the monitored element after some x number of violations within some other y number of probe operations (for example, x of y), the action is performed as defined by the action command. The default is 5 for both x-value and y-value; for example, xofy 5 5. The valid range for each value is from 1 to 16.
|
Defaults
If there is no default value, no threshold type is configured.
Command Modes
IP SLA reaction condition configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the threshold type xofy command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla reaction operation 432
RP/0/RP0/CPU0:router(config-ipsla-react)# react verify-error
RP/0/RP0/CPU0:router(config-ipsla-react-cond)# threshold type xofy 1 5
Related Commands
timeout
To set the probe or control timeout interval, use the timeout command in IP SLA ICMP Path-Jitter configuration mode, IP SLA ICMP Path-Echo configuration mode, IP SLA ICMP Echo configuration mode, IP SLA UDP Echo configuration mode, or IP SLA UDP Jitter configuration mode. To use the default value, use the no form of this command.
timeout milliseconds
no timeout
Syntax Description
milliseconds
|
Sets the amount of time (in milliseconds) that the IP SLA operation waits for a response from the request packet. The range is 1 to 604800000.
|
Defaults
The default value is 5000 ms.
Command Modes
IP SLA UDP Echo configuration
IP SLA UDP Jitter configuration
IP SLA ICMP Path-Jitter configuration
IP SLA ICMP Path-Echo configuration
IP SLA ICMP Echo configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the timeout command in IP SLA UDP Jitter configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# timeout 10000
Related Commands
tos
To set the type of service (ToS) in a probe packet, use the tos command in IP SLA ICMP Path-Jitter configuration mode, IP SLA ICMP Path-Echo configuration mode, IP SLA ICMP Echo configuration mode, IP SLA UDP Echo configuration mode, or IP SLA UDP Jitter configuration mode. To use the default value, use the no form of this command.
tos number
no tos
Syntax Description
number
|
Type of service number. The range is 0 to 255.
|
Defaults
The type of service number is 0.
Command Modes
IP SLA UDP Echo configuration
IP SLA UDP Jitter configuration
IP SLA ICMP Path-Jitter configuration
IP SLA ICMP Path-Echo configuration
IP SLA ICMP Echo configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The ToS value is an 8-bit field in IP headers. The field contains information, such as precedence and ToS. The information is useful for policy routing and for features like Committed Access Rate (CAR) in which routers examine ToS values. When the type of service is defined for an operation, the IP SLA probe packet contains the configured tos value in the IP header.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the tos command in IP SLA UDP Jitter configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# tos 60
Related Commands
type icmp echo
To use the ICMP echo operation type, use the type icmp echo command in IP SLA operation configuration mode. To remove the operation, use the no form of this command.
type icmp echo
no type icmp echo
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
IP SLA operation configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the type icmp echo command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type icmp echo
RP/0/RP0/CPU0:router(config-ipsla-icmp-echo)#
Related Commands
type icmp path-echo
To use the ICMP path-echo operation type, use the type icmp path-echo command in IP SLA operation configuration mode. To remove the operation, use the no form of this command.
type icmp path-echo
no type icmp path-echo
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
IP SLA operation configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the type icmp path-echo command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type icmp path-echo
RP/0/RP0/CPU0:router(config-ipsla-icmp-path-echo)#
Related Commands
type icmp path-jitter
To use the ICMP path-jitter operation type, use the type icmp path-jitter command in IP SLA operation configuration mode. To remove the operation, use the no form of this command.
type icmp path-jitter
no type icmp path-jitter
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
IP SLA operation configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the type icmp path-jitter command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type icmp path-jitter
RP/0/RP0/CPU0:router(config-ipsla-icmp-path-jitter)#
Related Commands
type udp echo
To use the UDP echo operation type, use the type udp echo command in IP SLA operation configuration mode. To remove the operation, use the no form of this command.
type udp echo
no type udp echo
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
IP SLA operation configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the type udp echo command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp echo
RP/0/RP0/CPU0:router(config-ipsla-udp-echo)#
Related Commands
type udp jitter
To use the UDP jitter operation type, use the type udp jitter command in IP SLA operation configuration mode. To remove the operation, use the no form of this command.
type udp jitter
no type udp jitter
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
IP SLA operation configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the type udp jitter command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)#
Related Commands
type udp ipv4 address
To configure a permanent port in the IP SLA Responder for UDP Echo or Jitter operations, use the type udp ipv4 address command in IP SLA Responder configuration mode. To remove the specified permanent port, use the no form of this command.
type udp ipv4 address ipaddress port port
no type udp {ipv4 address ipaddress {port port}}
Syntax Description
ipaddress
|
Specifies the IPv4 address at which the operation is received.
|
port port
|
Specifies the port number at which the operation is received. The range is identical to the one used for the subagent that is, 1 to 65355.
|
Defaults
If there is no default value, no permanent port is configured.
Command Modes
IP SLA Responder configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to configure a permanent port for the type udp ipv4 address command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla responder
RP/0/RP0/CPU0:router(config-ipsla-resp)# type udp ipv4 address 12.25.26.10 port 10001
Related Commands
Command
|
Description
|
ipsla responder
|
Enables the IP SLA responder for UDP Echo or Jitter operations.
|
verify-data
To check each IP SLA response for corruption, use the verify-data command in IP SLA UDP Echo configuration mode or IP SLA UDP Jitter configuration mode. To disable data corruption checking, use the no form of this command.
verify-data
no verify-data
Syntax Description
This command has no arguments or keywords.
Defaults
The verify-data command is disabled.
Command Modes
IP SLA UDP Echo configuration
IP SLA UDP Jitter configuration
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
monitor
|
read, write
|
Examples
The following example shows how to use the verify-data command in IP SLA UDP Jitter configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type udp jitter
RP/0/RP0/CPU0:router(config-ipsla-udp-jitter)# verify-data
Related Commands