System Monitoring Command Reference for Cisco NCS 5500 Series, Cisco NCS 540 Series, and Cisco NCS 560 Series Routers

access-list

To specify an access-list name to filter provider edge (PE) addresses to restrict operations that are automatically created by MPLS LSP monitor (MPLSLM) instance, use the access-list command in the appropriate configuration mode. To return to the default value, use the no form of this command.

access-list acl-name

no access-list

Syntax Description


`acl-name`	Filters an access-list name.

Command Default

No access list is configured by default.

Command Modes

IP SLA MPLS LSP monitor ping configuration

IP SLA MPLS LSP monitor trace configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

Access-list changes are processed before the scan interval expires to display a planned list of changes in the scan-queue.

Note

There is no verification check between the access list and the IPSLA configuration.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to use the access-list command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# mpls lsp-monitor
RP/0/RP0/CPU0:router(config-ipsla-mplslm)# monitor 1
RP/0/RP0/CPU0:router(config-ipsla-mplslm-def)# type mpls lsp ping
RP/0/RP0/CPU0:router(config-ipsla-mplslm-lsp-ping)# access-list ipsla

Related Commands


Command	Description
scan interval	Specifies the frequency at which the MPLS LSP monitor instance checks the scan queue for updates.
type mpls lsp ping	Tests connectivity in an LSP path in an MPLS VPN.
type mpls lsp trace	Traces the hop-by-hop route of an LSP path in an MPLS VPN.

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

Command Default

None

Command Modes

IP SLA reaction condition configuration

IP SLA MPLS LSP monitor reaction configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

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.

When the action command is used from IP SLA MPLS LSP monitor reaction configuration mode, only the logging keyword is available.

If the action command is used in IP SLA operation mode, the action defined applies to the specific operation being configured. If the action command is used in IP SLA MPLS LSP monitor mode, the action defined applies to all operations associated with the monitored provider edge (PE) routers. This configuration is inherited by all LSP operations that are created automatically.

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

The following example shows how to use the action command from the IP SLA MPLS LSP monitor reaction configuration mode:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# mpls lsp-monitor
RP/0/RP0/CPU0:router(config-ipsla-mplslm)# reaction monitor 1
RP/0/RP0/CPU0:router(config-ipsla-mplslm-react)# react connection-loss
RP/0/RP0/CPU0:router(config-ipsla-mplslm-react-cond)# action logging

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.
reaction monitor	Configures MPLS LSP monitoring reactions.
reaction operation	Configures certain actions that are based on events under the control of the IP SLA agent.
react	Specifies an element to be monitored for a reaction.
threshold	Sets the lower-limit and upper-limit values.
threshold type average	Takes action on average values to violate a threshold.
threshold type consecutive	Takes action after a number of consecutive violations.
threshold type immediate	Takes action immediately upon a threshold violation.
threshold type xofy	Takes action upon X violations in Y probe operations.

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 so that 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. Range is 0 to 2073600.

Command Default

The default value is 0 seconds (never aged out).

Command Modes

IP SLA schedule configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

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 
RP/0/RP0/CPU0:router(config-ipsla)# schedule operation 1
RP/0/RP0/CPU0:router(config-ipsla-sched)# ageout 3600

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.

buckets (history)

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. Range is 1 to 60.

Command Default

The default value is 15 buckets.

Command Modes

IP SLA operation history configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

The buckets command is supported only to configure the following operations:

IP SLA ICMP path-echo
IP SLA ICMP echo
IP SLA UDP echo

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


Command	Description
history	Configures the history parameters for the IP SLA operation.
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.

buckets (statistics hourly)

To set the number of hours for which statistics are kept, use the bucket command in the appropriate configuration mode. To use the default value, use the no form of this command.

buckets hours

no buckets

Syntax Description


`hours`	Number of hours for which statistics are maintained for the IP SLA operations. Range is 0 to 25 in IP SLA operation statistics configuration mode, and 0 to 2 in IP SLA MPLS LSP monitor statistics configuration mode.

Command Default

The default value is 2.

Command Modes

IP SLA operation statistics configuration

IP SLA MPLS LSP monitor statistics configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

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 
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 (statistics interval)

To specify the maximum number of 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`	The bucket size is when the configured bucket limit is reached. Therefore, statistics gathering for the operation ends. Range is 1 to 100. Default is 100.

Command Default

The default value is 100.

Command Modes

IP SLA operation statistics configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

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 
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 the appropriate 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 keywords or arguments.

Command Default

Control packets are enabled by default.

Command Modes

IP SLA UDP echo configuration

IP SLA UDP jitter configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

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


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.

datasize request

To set the protocol data size in the request packet in the payload of an operation, use the datasize request command in the appropriate configuration mode. To reset the default data size, 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 a UDP jitter operation, range is 16 to 1500 B. For a UDP echo operation, range is 4 to 1500 B. For an ICMP echo operation, range is 0 to 16384 B. For an ICMP path-echo operation, range is 0 to 16384 B. For an ICMP path-jitter operation, range is 0 to 16384 B. For an MPLS LSP ping operation, range is 100 to 17986 B.

Command Default

For a UDP jitter operation, the default value is 32 B.

For a UDP echo operation, the default value is 16 B.

For an ICMP echo operation, the default value is 36 B.

For an ICMP path-echo operation, the default value is 36 B.

For an ICMP path-jitter operation, the default value is 36 B.

For an MPLS LSP ping operation, the default value is 100 B.

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

IP SLA MPLS LSP ping configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

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


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.
type icmp echo	Configures an IP SLA ICMP echo operation.
type icmp path-echo	Configures an IP SLA ICMP path-echo operation.
type icmp path-jitter	Configures an IP SLA ICMP path-jitter operation.
type udp jitter	Configures an IP SLA UDP jitter operation.

destination address (IP SLA)

To identify the address of the target device, use the destination address command in the appropriate 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.

Command Default

None

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 6.0	This command was introduced.

Usage Guidelines

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

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.

destination port

To identify the port of the target device, use the destination port command in the appropriate 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. Range is 1 to 65355.

Command Default

None

Command Modes

IP SLA UDP echo configuration

IP SLA UDP jitter configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

The destination port command is not supported when you configure an ICMP operation; it is supported only to configure 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 
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


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.

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. Range is 1 to 20. Default is 1.

Command Default

The default value is 1.

Command Modes

IP SLA operation statistics configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

In most situations, you do not need to change the number of statistics distributions kept or the time interval for each distribution. Only change these parameters when distributions are needed, for example, when performing statistical modeling of your network. To set the statistics distributions interval, use the 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 
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 (statistics 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. Range is 1 to 100. Default is 20.

Command Default

The default value is 20.

Command Modes

IP SLA operation statistics configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

In most situations, you do not need to change the number of statistics distributions kept or the time interval for each distribution. Only change these parameters when distributions are needed, for example, when performing statistical modeling of your network. To set the statistics distributions 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 
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 (statistics 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.

exp

To specify the MPLS experimental field (EXP) value in the header of echo request packets, use the exp command in the appropriate configuration mode. To return to the default value, use the no form of this command.

exp exp-bits

no exp

Syntax Description


`exp-bits`	Experimental field value in the header of an echo request packet. Valid values are from 0 to 7. Default is 0.

Command Default

The experimental field value is set to 0.

Command Modes

IP SLA MPLS LSP ping configuration

IP SLA MPLS LSP trace configuration

IP SLA MPLS LSP monitor ping configuration

IP SLA MPLS LSP monitor trace configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

Use the exp command to set the MPLS experimental field in the headers of echo request packets in an MPLS LSP ping or MPLS LSP trace operation. The experimental (EXP) field allows for eight different quality-of-service (QoS) markings that determine the treatment (per-hop behavior) that a transit LSR node gives to a request packet. You can configure different MPLS EXP levels for different operations to create differentiated levels of response.

If the exp command is used in IP SLA operation mode, it acts on the headers of echo request packets for the specific operation being configured. If the exp command is used in IP SLA MPLS LSP monitor mode, it acts on the headers of echo request packets for all operations associated with the monitored provider edge (PE) routers. This configuration is inherited by all LSP operations that are created automatically.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to use the exp command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type mpls lsp trace
RP/0/RP0/CPU0:router(config-ipsla-mpls-lsp-trace)# exp 5

The following example shows how to use the exp command in MPLS LSP monitor mode:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# mpls lsp-monitor
RP/0/RP0/CPU0:router(config-ipsla-mplslm)# monitor 1
RP/0/RP0/CPU0:router(config-ipsla-mplslm-def)# type mpls lsp trace
RP/0/RP0/CPU0:router(config-ipsla-mplslm-lsp-trace)# exp 5

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.
type mpls lsp ping	Tests connectivity in an LSP path in an MPLS VPN.
type mpls lsp trace	Traces the hop-by-hop route of an LSP path in an MPLS VPN.

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.

Command Default

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 6.0	This command was introduced.

Usage Guidelines

The filter command is supported only to configure the following operations:

IP SLA ICMP path-echo
IP SLA ICMP echo
IP SLA UDP echo

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


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.

force explicit-null

To add an explicit null label to the label stack of an LSP when an echo request is sent, use the force explicit-null command in the appropriate configuration mode. To return to the default value, use the no form of this command.

force explicit-null

no force explicit-null

Syntax Description

This command has no keywords or arguments.

Command Default

An explicit null label is not added.

Command Modes

IP SLA MPLS LSP ping configuration

IP SLA MPLS LSP trace configuration

IP SLA MPLS LSP monitor ping configuration

IP SLA MPLS LSP monitor trace configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

Use the force explicit-null command to force an unsolicited explicit null label to be added to the MPLS label stack of the LSP when an echo request packet is sent in an MPLS LSP ping or MPLS LSP trace operation.

If the force explicit-null command is used in IP SLA operation mode, it acts on the label stack of the LSP for the specific operation being configured. If the force explicit-null command is used in IP SLA MPLS LSP monitor mode, it acts on the label stack of all operations associated with the monitored provider edge (PE) routers. This configuration is inherited by all LSP operations that are created automatically.

You cannot use the force explicit-null command if pseudowire is specified as the target to be used in an MPLS LSP ping operation.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to use the force explicit-null command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type mpls lsp trace
RP/0/RP0/CPU0:router(config-ipsla-mpls-lsp-trace)# force explicit-null

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.
type mpls lsp ping	Tests connectivity in an LSP path in an MPLS VPN.
type mpls lsp trace	Traces the hop-by-hop route of an LSP path in an MPLS VPN.

frequency (IP SLA)

To set the frequency for probing, use the frequency command in the appropriate 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. Range is 1 to 604800.

Command Default

If the frequency command is not used, the default value is 60 seconds.

In IP SLA MPLS LSP monitor schedule configuration mode, the default value is equal to the schedule period that is set using the schedule period command.

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

IP SLA MPLS LSP ping configuration

IP SLA MPLS LSP trace configuration

IP SLA MPLS LSP monitor schedule configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

If this command is used in IP SLA MPLS LSP monitor schedule configuration mode, it represents the frequency for the schedule period. In other words, if the frequency is set to 1000 seconds and the schedule period is set to 600 seconds, every 1000 seconds the LSP operations are run. Each run takes 600 seconds. Use the schedule period command to specify the schedule period.

The frequency value must be greater than or equal to the schedule period.

This configuration is inherited automatically by all LSP operations that are created.

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

The following example shows how to use the frequency command in IP SLA MPLS LSP monitor schedule configuration mode:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# mpls lsp-monitor
RP/0/RP0/CPU0:router(config-ipsla-mplslm)# schedule monitor 1
RP/0/RP0/CPU0:router(config-ipsla-mplslm-sched)# frequency 1200
RP/0/RP0/CPU0:router(config-ipsla-mplslm-sched)# schedule period 600

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.
schedule period	Configures the amount of time during which all LSP operations are scheduled to start or run.

history

To configure the history parameters for the IP SLA operation, use the history command in the appropriate configuration mode. To use the default value, use the no form of this command.

history [buckets buckets | filter {all | failures} | lives lives]

no history

Syntax Description


buckets	Sets the number of history buckets that are kept during the lifetime of the IP SLA operation.
`buckets`	Number of history buckets that are kept during the lifetime of an IP SLA operation. Range is 1 to 60.
filter	Defines the type of information that is kept in the history table for the IP SLA operation.
all	Stores history data for all operations, if set.
failures	Stores data for operations that failed, if set.
lives	Sets the number of lives that are maintained in the history table for an IP SLA operation.
`lives`	Number of lives that are maintained in the history table for an IP SLA operation. Range is 0 to 2.

Command Default

None

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

IP SLA MPLS LSP ping configuration

IP SLA MPLS LSP trace configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

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 
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)	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.
operation	Configures an IP SLA operation.
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.

hw-timestamp disable

To disable hardware time stamp configuration, use the hw-timestamp disable command in the IP SLA configuration mode.

hw-timestamp disable

Syntax Description

This command has no keywords or arguments.

Command Default

None

Command Modes

IP SLA configuration

Command History


Release	Modification
Release 6.0.1	This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID


Task ID	Operation
monitor	read, write

Examples

The following example shows how to disable hardware time stamping:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# hw-timestamp disable

interval

To configure the refresh interval for MPLS label switched path (LSP) monitoring, use the interval command in IP SLA MPLS discovery VPN configuration mode. To use the default value, use the no form of this command.

interval refresh-interval

no interval

Syntax Description


`refresh-interval`	Specifies the time interval, in minutes, after which routing entries that are no longer valid are removed from the Layer 3 VPN discovery database. Range is 30 to 70560.

Command Default

The default refresh interval is 60 minutes.

Command Modes

IP SLA MPLS discovery VPN configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

Note

If the total number of routes is large, there is a negative impact on the performance during the refresh of the discovery database. Therefore, the value of the refresh-interval argument should be large enough that router performance is not affected. If there are a very large number of routes, we recommend that you set the value of the refresh-interval argument to be several hours.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to use the interval command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# mpls discovery vpn
RP/0/RP0/CPU0:router(config-ipsla-mpls-discovery-vpn)# interval 120

Related Commands


Command	Description
mpls discovery vpn	Configures MPLS label switched path (LSP) provider edge (PE) router discovery.

ipsla

To enter IP SLA configuration mode and configure IP Service Level Agreements, use the ipsla command in XR Config mode. To return to the default setting, use the no form of this command.

ipsla

no ipsla

Syntax Description

This command has no keywords or arguments.

Command Default

None

Command Modes

XR Config mode

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

The ipsla command enters IP SLA configuration mode where you can configure the various IP service level agreement options.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to enter IP SLA configuration mode:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)#

key-chain

To configure the MD5 authentication for the IP SLA control message, use the key-chain command in IP SLA configuration mode. To unset the keychain name and not use MD5 authentication, use the no form of this command.

key-chain key-chain-name

no key-chain

Syntax Description


`key-chain-name`	Name of the keychain.

Command Default

No default values are defined. No authentication is used.

Command Modes

IP SLA configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

When you configure the key-chain command, you must also configure the key chain command in global configuration mode 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 
RP/0/RP0/CPU0:router(config-ipsla)# key-chain ipsla-keys

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.

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. Range is 1 to 2147483647. Default value is 3600 seconds (one hour).

Command Default

The default value is 3600 seconds.

Command Modes

IP SLA schedule configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

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 
RP/0/RP0/CPU0:router(config-ipsla)# schedule operation 1
RP/0/RP0/CPU0:router(config-ipsla-sched)# life forever

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.

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. Range is 0 to 2.

Command Default

The default value is 0 lives.

Command Modes

IP SLA operation history configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

The lives command is supported only to configure the following operations:

IP SLA ICMP path-echo
IP SLA ICMP echo
IP SLA UDP echo

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 
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)	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.
operation	Configures an IP SLA operation.
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.

local-ip

To configure the test-session parameters for TWAMP-light responder, use the local-ip command in the ipsla responder twamp-light mode. To remove the set configuration, use the no form of the command.

local-ip local-ip-address local-port local-port remote-ip remote-ip-address remote-port remote-port vrf [ default| vrf-name]

Syntax Description


local-ip `local-ip-address`	Configure IPv4/IPv6 address of the interface on the local router
local-port `local-port`	Configure the UDP port number of the local router. Range is 1 - 65535
remote-ip `remote-ip-address`	Configure IPv4/IPv6 address of the interface on the remote router
remote-port `remote-port`	Configure the UDP port number of the remote router. Range is 1 - 65535
vrf [default \| `vrf-name` ]	Configure the VRF that the interface on the local router is part of

Command Default

None

Command Modes

IPSLA responder TWAMP-light configuration mode

Command History


Release	Modification
Release 6.6.1	This command is introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Examples

This example shows how to run the responder command in order to configure TWAMP responder:

Router(config)# ipsla
Router(config-ipsla)# responder twamp-light test-session 1
Router(config-twamp-light-def)# local-ip 192.0.2.10 local-port 13001 remote-ip 192.0.2.186 remote-port 13002 vrf default

low-memory

low-memory value

no low-memory

Syntax Description


`value`	Low-water memory mark value. Range is 0 to 4294967295.

Command Default

The default value is 20 MB (free memory).

Command Modes

IP SLA configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

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 low-memory command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# low-memory 102400

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.
show ipsla application	Displays the information for the IP SLA application.

lsp selector ipv4

To specify the local host IPv4 address used to select an LSP, use the lsp selector ipv4 command in the appropriate configuration mode. To clear the host address, use the no form of this command.

lsp selector ipv4 ip-address

no lsp selector ipv4

Syntax Description


`ip-address`	A local host IPv4 address used to select the LSP.

Command Default

The local host IP address used to select the LSP is 127.0.0.1.

Command Modes

IP SLA MPLS LSP ping configuration

IP SLA MPLS LSP trace configuration

IP SLA MPLS LSP monitor ping configuration

IP SLA MPLS LSP monitor trace configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

Use the lsp selector ipv4 command to force an MPLS LSP ping or MPLS LSP trace operation to use a specific LSP when there are multiple equal cost paths between provider edge (PE) routers. This situation occurs when transit label switching routers (LSRs) use the destination address in IP packet headers for load balancing.

The IPv4 address configured with the lsp selector ipv4 command is the destination address in the User Datagram Protocol (UDP) packet sent as the MPLS echo request. Valid IPv4 addresses are defined in the subnet 127.0.0.0/8 and used to:

Force the packet to be consumed by the router where an LSP breakage occurs.
Force processing of the packet at the terminal point of the LSP if the LSP is intact.
Influence load balancing during forwarding when the transit routers use the destination address in the IP header for load balancing.

If the lsp selector ipv4 command is used in IP SLA operation mode, it acts on the MPLS echo requests for the specific operation being configured. If the lsp selector ipv4 command is used in IP SLA MPLS LSP monitor mode, it acts on the MPLS echo requests for all operations associated with the monitored provider edge (PE) routers.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to use the lsp selector ipv4 command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type mpls lsp trace
RP/0/RP0/CPU0:router(config-ipsla-mpls-lsp-trace)# lsp selector ipv4 127.10.10.1

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.
type mpls lsp ping	Tests connectivity in an LSP path in an MPLS VPN.
type mpls lsp trace	Traces the hop-by-hop route of an LSP path in an MPLS VPN.

lsr-path

To specify a loose source routing path in which to measure the ICMP, use the lsr-path command in the appropriate configuration mode. To use a path other than the specified one, use the no form of this command.

lsr-path ipaddress1 [ipaddress2 [. . . [ipaddress8]]]

no lsr-path

Syntax Description


`ip address`	IPv4 address of the intermediate node. Up to eight addresses can be entered.

Command Default

No path is configured.

Command Modes

IP SLA ICMP path-jitter configuration

IP SLA ICMP path-echo configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

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

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.

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. Range is 1 to 30. Default value is 16 for path operations; for example, `pathecho` .

Command Default

The default value is 16 hops.

Command Modes

IP SLA operation statistics configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

The maximum hops command is supported only when you configure path operations and the IP SLA ICMP path-echo operation.

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 
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 (statistics 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. Range is 1 to 128. Default value is 5 for path operations; for example, `pathecho` .

Command Default

The default value is 5 paths.

Command Modes

IP SLA operation statistics configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

The maximum paths command is supported only when you configure path operations and the IP SLA ICMP path-echo operation.

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

monitor

To configure an MPLS LSP monitor instance, use the monitor command in IP SLA LSP monitor configuration mode. To remove the monitor instance, use the no form of this command.

monitor monitor-id

no monitor [monitor-id]

Syntax Description


`monitor-id`	Number of the IP SLA LSP monitor instance to be configured. Range is 1 to 2048.

Command Default

No monitor instance is configured.

Command Modes

IP SLA LSP monitor configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

The monitor command enters IP SLA MPLS LSP monitor configuration mode so that you can set the desired monitor type for all operations associated with the monitored provider edge (PE) routers.

To remove all monitor instances, use the no monitor command with no argument.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to use the monitor command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# mpls lsp-monitor
RP/0/RP0/CPU0:router(config-ipsla-mplslm)# monitor 1
RP/0/RP0/CPU0:router(config-ipsla-mplslm-def)#

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.

mpls discovery vpn

To configure MPLS label switched path (LSP) provider edge (PE) router discovery, use the mpls discovery vpn command in IP SLA configuration mode. To use the default value, use the no form of this command.

mpls discovery vpn [interval interval]

no mpls discovery vpn

Syntax Description


interval	Configures the refresh interval for MPLS label switched path (LSP) monitoring.

Command Default

None

Command Modes

IP SLA configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

Use the mpls discovery vpn command to configure provider edge (PE) router discovery. PE Discovery discovers the LSPs used to reach every routing next hop. Routing entities are stored in a Layer 3 VPN discover database.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to enter IP SLA MPLS discovery VPN mode:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# mpls discovery vpn
RP/0/RP0/CPU0:router(config-ipsla-mpls-discovery-vpn)#

Related Commands


Command	Description
interval	Configures the refresh interval for MPLS label switched path (LSP) monitoring.

mpls lsp-monitor

To configure MPLS label switched path (LSP) monitoring, use the mpls lsp-monitor command in IP SLA configuration mode. To use the default value, use the no form of this command.

mpls lsp-monitor

no mpls lsp-monitor

Syntax Description

This command has no keywords or arguments.

Command Default

None

Command Modes

IP SLA configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

Use the mpls lsp-monitor command to configure MPLS LSP PE monitoring on the router. This provides a means to configure all operations associated with the monitored provider edge (PE) routers. The configuration is inherited by all LSP operations that are created automatically by the PE discovery.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to enter IP SLA MPLS LSP monitor mode:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla  
RP/0/RP0/CPU0:router(config-ipsla)# mpls lsp-monitor 
RP/0/RP0/CPU0:router(config-ipsla-mplslm)#

Related Commands


Command	Description
mpls discovery vpn	Configures MPLS label switched path (LSP) provider edge (PE) router discovery.

operation

To configure an IP SLA operation, use the operation command in IP SLA configuration mode. To remove the operation, use the no form of this command.

operation operation-number

no operation operation-number

Syntax Description


`operation-number`	Operation number. Range is 1 to 2048.

Command Default

None

Command Modes

IP SLA configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to use the IP SLA operation command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)#

Related Commands


Command	Description
schedule operation	Schedules an IP SLA operation.

output interface

To specify the echo request output interface to be used for LSP ping or LSP trace operations, use the output interface command in IP SLA MPLS LSP ping or IP SLA MPLS LSP trace configuration mode. To return the output interface to the default, use the no form of this command.

output interface type interface-path-id

no output interface

Syntax Description

type

Interface type. For more information, use the question mark (? ) online help function.

interface-path-id

Physical interface or virtual interface.

Note

Use the show interfaces command to see a list of all interfaces currently configured on the router.

For more information about the syntax for the router, use the question mark (? ) online help function.

Command Default

No default behavior or values.

Command Modes

IP SLA MPLS LSP ping configuration

IP SLA MPLS LSP trace configuration

IP SLA MPLS LSP monitor ping configuration

IP SLA MPLS LSP monitor trace configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

Use the output interface command to help monitor path-to-target over the path if there are some ECMP routes in a topology.

You cannot use the output interface command if pseudowire is specified as the target to be used in an MPLS LSP ping operation.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to use the output interface command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type mpls ls output interface pos 0/1/0/0

Related Commands


Command	Description
operation	Configures an IP SLA operation.
output nexthop	Configures the next-hop address to be used for LSP ping or LSP trace operations.
schedule operation	Schedules an IP SLA operation.
type mpls lsp ping	Tests connectivity in an LSP path in an MPLS VPN.
type mpls lsp trace	Traces the hop-by-hop route of an LSP path in an MPLS VPN.

output nexthop

To specify the next-hop address to be used for a Label Switched Path (LSP) ping or LSP trace operations, use the output nexthop command in the appropriate configuration mode. To return the output next hop to the default, use the no form of this command.

output nexthop ip-address

no output nexthop

Syntax Description


`ip-address`	IP address of the next hop.

Command Default

No default behavior or values

Command Modes

IP SLA MPLS LSP ping configuration

IP SLA MPLS LSP trace configuration

IP SLA MPLS LSP monitor ping configuration

IP SLA MPLS LSP monitor trace configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

When LSP Path Discovery (LPD) is enabled, the next-hop IP address is also used to filter out the paths that are not associated with the specified next-hop address.

Note

After you configure the output next hop, you must also configure the output interface.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to use the output nexthop command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type mpls lsp trace
RP/0/RP0/CPU0:router(config-ipsla-mpls-lsp-trace)# output nexthop 10.1.1.1

Related Commands


Command	Description
operation	Configures an IP SLA operation.
output interface	Configures the echo request output interface to be used for LSP ping or LSP trace operations.
schedule operation	Schedules an IP SLA operation.
type mpls lsp ping	Tests connectivity in an LSP path in an MPLS VPN.
type mpls lsp trace	Traces the hop-by-hop route of an LSP path in an MPLS VPN.

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 the appropriate 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. Range for a UDP jitter operation is 1 to 60000. Range for an ICMP path-jitter operation is 1 to 100.

Command Default

The default packet count is 10.

Command Modes

IP SLA UDP jitter configuration

IP SLA ICMP path-jitter configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

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


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.
packet interval	Specifies the interval between packets.

packet interval

To specify the interval between packets, use the packet interval command in the appropriate 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. Range is 1 to 60000 (in milliseconds).

Command Default

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 6.0	This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

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


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.
packet count	Specifies the number of packets that are to be transmitted during a probe.

path discover

To enable path discovery and enter MPLS LSP monitor (MPLSLM) LPD submode, use the path discover command in IP SLA MPLS LSP monitor ping configuration mode. To use the default value, use the no form of this command.

path discover

no path discover

Syntax Description

None

Command Default

No default behavior or values

Command Modes

IP SLA MPLS LSP monitor ping configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to enter path discover submode:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla
RP/0/RP0/CPU0:router(config-ipsla)# mpls lsp-monitor 
RP/0/RP0/CPU0:router(config-ipsla-mplslm)# monitor 1 
RP/0/RP0/CPU0:router(config-ipsla-mplslm-def)# type mpls lsp ping 
RP/0/RP0/CPU0:router(config-ipsla-mplslm-lsp-ping)# path discover 
RP/0/RP0/CPU0:router(config-ipsla-mplslm-lpd)#

path discover echo

To configure MPLS LSP echo parameters, use the path discover command in the appropriate configuration mode. To use the default value, use the no form of this command.

path discover echo {interval time | maximum lsp selector ipv4 host address | multipath bitmap size size | retry count | timeout value}

no path discover echo {interval time | maximum lsp selector ipv4 host address | multipath bitmap size size | retry count | timeout value}

Syntax Description


interval `time`	Configures the interval (in milliseconds) between MPLS LSP echo requests sent during path discovery. Range is 0 to 3600000. Default is 0.
maximum lsp selector ipv4 `host-address`	Configures a local host IP address (127`.x.x.x` ) that is the maximum selector value to be used during path discovery. Default is 127.255.255.255.
multipath bitmap size `size`	Configures the maximum number of selectors sent in the downstream mapping of an MPLS LSP echo request during path discovery. Range is 1 to 256. Default is 32.
retry `count`	Configures the number of timeout retry attempts for MPLS LSP echo requests sent during path discovery. Range is 0 to 10. Default is 3.
timeout `value`	Configures the timeout value (in seconds) for MPLS LSP echo requests sent during path discovery. Range is 1 to 3600. Default is 5.

Command Default

interval time : 0

maximum lsp selector ipv4 host address : 127.255.255.255

multipath bitmap size size : 32

retry count : 3

timeout value : 5

Command Modes

Path discover configuration

MPLS LSP ping configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

A retry occurs when either an echo reply was not received on time for an outstanding echo request, or when no selectors are found for a given path by a transit router.

When a selector value is configured in MPLSLM configuration mode, the maximum selector specified must be larger than that value. In such a scenario, the range of selectors used for path discovery is set by the two values.

When the interval time is zero, a new echo request is sent after the previous echo retry was received.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to configure the path discover echo interval:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla
RP/0/RP0/CPU0:router(config-ipsla)# mpls lsp-monitor
RP/0/RP0/CPU0:router(config-ipsla-mplslm)# monitor 1
RP/0/RP0/CPU0:router(config-ipsla-mplslm-def)# type mpls lsp ping
RP/0/RP0/CPU0:router(config-ipsla-mplslm-lsp-ping)# path discover
RP/0/RP0/CPU0:router(config-ipsla-mplslm-lsp-lpd)# echo interval 777

Related Commands


Command	Description
path discover path	Configures MPLS LSP path parameters.
path discover scan	Configures MPLS LSP scan parameters.
path discover session	Configures MPLS LSP session parameters.

path discover path

To configure MPLS LSP path parameters, use the path discover path command in MPLS LSP monitor (MPLSLM) LPD configuration submode. To use the default value, use the no form of this command.

path discover path {retry range | secondary frequency {both | connection-loss | timeout} value}

no path-discover path

Syntax Description


retry `range`	Configures the number of attempts to be performed before declaring a path as down. Default is 1 (LSP group will not retry to perform the echo request if the previous attempt fails). Range is 1 to 16.
secondary frequency	Configures a secondary frequency to use after a failure condition (that is, a connection-loss or timeout) occurs.
both	Enable secondary frequency for a timeout and connection loss.
connection-loss	Enable secondary frequency for only a connection loss.
timeout	Enable secondary frequency for only a timeout.
`value`	Frequency value range is 1 to 604800.

Command Default

None

Command Modes

MPLSLM LPD configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

In the event of a path failure, the secondary frequency value is used instead of the normal frequency value. The normal frequency value is determined by a frequency value or schedule period value, and the LSP operations are scheduled to start periodically at this interval. By default, the secondary frequency value is disabled. When failure condition disappears, probing resumes at the regular frequency.

Note

The secondary command works in tandem with the retry keyword. Both must be configured.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to configure MPLS LSP path parameters:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla
RP/0/RP0/CPU0:router(config-ipsla)# mpls lsp-monitor
RP/0/RP0/CPU0:router(config-ipsla-mplslm)# monitor 1
RP/0/RP0/CPU0:router(config-ipsla-mplslm-def)# type mpls lsp ping
RP/0/RP0/CPU0:router(config-ipsla-mplslm-lsp-ping)# path discover
RP/0/RP0/CPU0:router(config-ipsla-mplslm-lsp-lpd)# path retry 12
RP/0/RP0/CPU0:router(config-ipsla-mplslm-lsp-lpd)# path secondary frequency both 10

Related Commands


Command	Description
path discover echo	Configures MPLS LSP echo parameters.
path discover scan	Configures MPLS LSP scan parameters.
path discover session	Configures MPLS LSP session parameters.

path discover scan

To configure MPLS LSP scan parameters, use the path discover scan command in MPLS LSP monitor (MPLSLM) LPD configuration submode. To use the default value, use the no form of this command.

path discover scan period value

no path discover scan period value

Syntax Description


period `value`	Configures the time (in minutes) between consecutive cycles of path discovery requests per MPLSLM instance. Range is 0 to 7200. Default is 5.

Command Default

period value : 5

Command Modes

MPLSLM LPD configuration submode

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

MPLSLM instances periodically trigger path discovery requests for LSP groups. At certain intervals, an MPLSLM instance begins triggering path discovery requests for each group in ascending order (determined by group ID). By default, the path discovery requests are triggered sequentially, although some concurrency may occur if the session limit value is greater than 1. The cycle concludes when the last LSP group finishes path discovery.

If the duration of the discovery cycle is larger than the scan period, a new cycle starts as soon as the previous one completes.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to configure the path discovery scan period value:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla
RP/0/RP0/CPU0:router(config-ipsla)# mpls lsp-monitor
RP/0/RP0/CPU0:router(config-ipsla-mplslm)# monitor 1
RP/0/RP0/CPU0:router(config-ipsla-mplslm-def)# type mpls lsp ping
RP/0/RP0/CPU0:router(config-ipsla-mplslm-lsp-ping)# path discover
RP/0/RP0/CPU0:router(config-ipsla-mplslm-lsp-lpd)# scan period 2

Related Commands


Command	Description
path discover echo	Configures MPLS LSP echo parameters.
path discover path	Configures MPLS LSP path parameters.
path discover session	Configures MPLS LSP session parameters.

path discover session

To configure MPLS LSP session parameters, use the path discover session command in MPLS LSP monitor (MPLSLM) LPD configuration submode. To use the default value, use the no form of this command.

path discover session {limit value | timeout value}

no path discover session {limit value | timeout value}

Syntax Description


limit `value`	Configures the number of concurrent active path discovery requests the MPLSLM instance submits to the LSPV server. Range is 1 to 15. Default is 1.
timeout `value`	Configures the time (in seconds) the MPLSLM instance will wait for the result of a path discovery request submitted to the LSPV server. Range is 1 to 900. Default is 120.

Command Default

limit value : 1

timeout value : 120

Command Modes

MPLSLM LPD configuration submode

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

An MPLSLM instance considers the path discovery as a failure when it receives no response within the configured timeout configuration value.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to configure the path discovery session timeout value:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla
RP/0/RP0/CPU0:router(config-ipsla)# mpls lsp-monitor
RP/0/RP0/CPU0:router(config-ipsla-mplslm)# monitor 1
RP/0/RP0/CPU0:router(config-ipsla-mplslm-def)# type mpls lsp ping
RP/0/RP0/CPU0:router(config-ipsla-mplslm-lsp-ping)# path discover
RP/0/RP0/CPU0:router(config-ipsla-mplslm-lsp-lpd)# session timeout 22

Related Commands


Command	Description
path discover echo	Configures MPLS LSP echo parameters.
path discover path	Configures MPLS LSP path parameters.
path discover scan	Configures MPLS LSP scan parameters.

react

To specify an element to be monitored for a reaction, use the react command in the appropriate 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 —(Optional) Specifies the jitter average destination to source (DS). source-to-dest —(Optional) 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 —(Optional) Specifies the packet loss destination to source (DS) violation. source-to-dest —(Optional) 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.

Command Default

If there is no default value, no reaction is configured.

Command Modes

IP SLA reaction configuration

IP SLA MPLS LSP monitor reaction configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

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.

In IP SLA MPLS LSP monitor reaction configuration mode, only the connection-loss and timeout keywords are available. If the react command is used in IP SLA MPLS LSP monitor reaction configuration mode, it configures all operations associated with the monitored provider edge (PE) routers. The configuration is inherited by all LSP operations that are created automatically by the PE discovery.

This table lists the Supported Reaction Configuration, by IP SLA Operation.

Table 1. Supported Reaction Configuration, by IP SLA Operation
Operation	ICMP Echo	Path Echo	UDP Jitter	UDP Echo	ICMP Path Jitter	MPLS LSP Ping	MPLS LSP Trace
Failure	--	--	--	--	--	--	--
RTT	Y	Y	Y	Y	Y	Y	Y
RTTAvg	--	--	--	--	--	--	--
Timeout	Y	Y	Y	Y	Y	Y	Y
connectionLoss	--	--	Y	Y	--	Y	Y
verifyError	--	--	Y	Y	--	--	--
jitterSDAvg	--	--	Y	--	--	--	--
jitterDSAvg	--	--	Y	--	--	--	--
jitterAvg	--	--	Y	--	--	--	--
PacketLossDS	--	--	Y	--	--	--	--
PacketLossSD	--	--	Y	--	--	--	--
PacketLoss	--	--	Y	--	--	--	--

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to use the react command with the connection-loss keyword:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
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 
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 
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 
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 
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 
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


Command	Description
action (IP SLA)	Specifies what action or combination of actions the operation performs when you configure the react command or when threshold events occur.
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.
threshold	Sets the lower-limit and upper-limit values.
threshold type average	Takes action on average values to violate a threshold.
threshold type consecutive	Takes action after a number of consecutive violations.
threshold type immediate	Takes action immediately upon a threshold violation.
threshold type xofy	Takes action upon X violations in Y probe operations.

react lpd

To specify that a reaction should occur if there is an LSP Path Discovery (LPD) violation, use the react lpd command in the appropriate configuration mode. To use the default value, use the no form of this command.

react lpd {lpd-group | tree-trace} action logging

no react lpd {lpd-group | tree-trace}

Syntax Description


lpd-group	Specifies that a reaction should occur if there is a status violation for the monitored LPD group.
tree-trace	Specifies that a reaction should occur if there is a path discovery violation for the monitored LPD group.
action	Configures the action to be taken on threshold violation.
logging	Specifies the generation of a syslog alarm on threshold violation.

Command Default

None

Command Modes

IP SLA MPLS LSP monitor configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

A status violation for a monitored LPD group happens when the Label Switched Path (LSP) group status changes (with the exception of the status change from the initial state).

A path discovery violation for the monitored LPD group happens when path discovery to the target PE fails, or successful path discovery clears such a failure condition.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to specify that a reaction should occur if there is a status violation for the monitored LPD group:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# mpls lsp-monitor
RP/0/RP0/CPU0:router(config-ipsla-mplslm)# reaction monitor 1
RP/0/RP0/CPU0:router(config-ipsla-mplslm-react)# react lpd lpd-group action logging

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.

reaction monitor

To configure MPLS label switched path (LSP) monitoring reactions, use the reaction monitor command in IP SLA MPLS LSP monitor configuration mode. To remove the reaction so that no reaction occurs, use the no form of this command.

reaction monitor monitor-id

no reaction monitor [monitor-id]

Syntax Description


`monitor-id`	Number of the IP SLA MPLS LSP monitor instance for the reactions to be configured. Range is 1 to 2048.

Command Default

No reaction is configured.

Command Modes

IP SLA MPLS LSP monitor configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

The reaction monitor command enters IP SLA LSP monitor reaction configuration mode so that you can set the desired threshold and action in the event of a connection loss or timeout.

To remove all reactions, use the no reaction monitor command with no monitor-id argument.

The reaction monitor command configures reactions for all operations associated with the monitored provider edge (PE) routers. This configuration is inherited by all LSP operations that are created automatically.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to use the reaction operation command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# mpls lsp-monitor
RP/0/RP0/CPU0:router(config-ipsla-mplslm)# reaction monitor 1 
RP/0/RP0/CPU0:router(config-ipsla-mplslm-react)#

Related Commands


Command	Description
action (IP SLA)	Specifies what action or combination of actions the operation performs when you configure the react command or when threshold events occur.
monitor	Configures an IP SLA MPLS LSP monitor instance.
react	Specifies an element to be monitored for a reaction.
schedule monitor	Schedules an IP SLA MPLS LSP monitor instance.
threshold type consecutive	Specifies to take action after a number of consecutive violations.
threshold type immediate	Specifies to take action immediately upon a threshold violation.

reaction operation

To configure certain actions that are based on events under the control of the IP SLA agent, use the reaction operation command in IP SLA configuration mode.To remove the reaction so that no reaction occurs, use the no form of this command.

reaction operation operation-id

no reaction operation operation-id

Syntax Description


`operation-id`	Number of the IP SLA operation for the reactions to be configured. Range is 1 to 2048.

Command Default

No reaction is configured.

Command Modes

IP SLA configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to use the reaction operation command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# reaction operation 1 
RP/0/RP0/CPU0:router(config-ipsla-react)#

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.

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 reaction operation command, use the reaction trigger command in IP SLA configuration mode. To remove the reaction trigger when the triggering-operation argument does not trigger any other operation, use the no form of this command.

reaction trigger triggering-operation triggered-operation

no reaction trigger triggering-operation triggered-operation

Syntax Description


`triggering-operation`	Operation that contains a configured action-type trigger and can generate reaction events. Range is 1 to 2048.
`triggered-operation`	Operation that is started when the `triggering-operation` argument generates a trigger reaction event. Range is 1 to 2048.

Command Default

No triggered operation is configured.

Command Modes

IP SLA configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

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 
RP/0/RP0/CPU0:router(config-ipsla)# reaction trigger 1 2

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.

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 keywords or arguments.

Command Default

Recurring is disabled.

Command Modes

IP SLA schedule configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

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 
RP/0/RP0/CPU0:router(config-ipsla)# schedule operation 1
RP/0/RP0/CPU0:router(config-ipsla-sched)# recurring

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.

reply dscp

To specify the differentiated services codepoint (DSCP) value used in echo reply packets, use the reply dscp command in the appropriate configuration mode. To return to the default value, use the no form of this command.

reply dscp dscp-bits

no reply dscp

Syntax Description


`dscp-bits`	Differentiated services codepoint (DSCP) value for an echo reply packet. Valid values are from 0 to 63. Reserved keywords such as EF (expedited forwarding) and AF11 (assured forwarding class AF11) can be specified instead of numeric values.

Command Default

No default behavior or values

Command Modes

IP SLA MPLS LSP ping configuration

IP SLA MPLS LSP trace configuration

IP SLA MPLS LSP monitor ping configuration

IP SLA MPLS LSP monitor trace configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

Use the reply dscp command to set the DCSP value used in the headers of IPv4 UDP packets sent as echo replies in an MPLS LSP ping or MPLS LSP trace operation.

The DSCP value consists of the six most significant bits of the 1-byte IP type of service (ToS) field. These bits determine the quality-of-service (QoS) treatment (per-hop behavior) that an transit LSR node gives to an echo reply packet. For information about how packets are classified and processed depending on the value you assign to the 6-bit DSCP field, refer to “The Differentiated Services Model (DiffServ)” at the following URL:

http://www.cisco.com/en/US/products/ps6610/products_data_sheet09186a00800a3e30.html

If the reply dscp command is used in IP SLA operation mode, it acts on the headers of echo replies for the specific operation being configured. If the reply dscp command is used in IP SLA MPLS LSP monitor mode, it acts on the headers of echo replies for all operations associated with the monitored provider edge (PE) routers. This configuration is inherited by all LSP operations that are created automatically.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to use the reply dscp command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type mpls lsp ping
RP/0/RP0/CPU0:router(config-ipsla-mpls-lsp-ping)# reply dscp 5

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.
type mpls lsp ping	Tests connectivity in an LSP path in an MPLS VPN.
type mpls lsp trace	Traces the hop-by-hop route of an LSP path in an MPLS VPN.

reply mode

To specify how to reply to echo requests, use the reply mode command in the appropriate configuration mode. To return to the default value, use the no form of this command.

reply mode {control-channel | router-alert}

no reply mode

Syntax Description

control-channel

Sets echo requests to reply by way of a control channel.

Note

This option is available only in IP SLA MPLS LSP ping configuration mode.

router-alert

Sets echo requests to reply as an IPv4 UDP packet with IP router alert.

Command Default

The default reply mode for an echo request packet is an IPv4 UDP packet without IP router alert set.

Command Modes

IP SLA MPLS LSP ping configuration

IP SLA MPLS LSP trace configuration

IP SLA MPLS LSP monitor ping configuration

IP SLA MPLS LSP monitor trace configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

Use the reply mode command with the control-channel keyword to send echo reply packets by way of a control channel in an MPLS LSP ping operation. If the target is not set to pseudowire, the configuration of the control-channel keyword is rejected. Refer to the target pseudowire command for information about setting the target.

Use the reply mode command with the router-alert keyword to set the reply mode of echo reply packets in an MPLS LSP ping or MPLS LSP trace operation. After you enter this command, echo reply packets are set to reply as an IPv4 UDP packet with the IP router alert option in the UDP packet header.

If the reply mode command is used in IP SLA operation mode, it sets the reply mode of echo reply packets for the specific operation being configured. If the reply mode command is used in IP SLA MPLS LSP monitor mode, it sets the reply mode of echo reply packets for all operations associated with the monitored provider edge (PE) routers. This configuration is inherited by all LSP operations that are created automatically.

The router-alert reply mode forces an echo reply packet to be specially handled by the transit LSR router at each intermediate hop as it moves back to the destination. Because this reply mode is more expensive, it is recommended only if the headend router does not receive echo replies using the default reply mode.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to use the reply mode command with the router-alert keyword:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type mpls lsp trace
RP/0/RP0/CPU0:router(config-ipsla-mpls-lsp-trace)# reply mode router-alert

The following example shows how to use the reply mode command with the control-channel keyword:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# operation 1
RP/0/RP0/CPU0:router(config-ipsla-op)# type mpls lsp ping
RP/0/RP0/CPU0:router(config-ipsla-mpls-lsp-ping)# target pseudowire 192.168.1.4 4211
RP/0/RP0/CPU0:router(config-ipsla-mpls-lsp-ping)# reply mode control-channel

Related Commands


Command	Description
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.
type mpls lsp ping	Tests connectivity in an LSP path in an MPLS VPN.
type mpls lsp trace	Traces the hop-by-hop route of an LSP path in an MPLS VPN.

responder

To configure the responder for IP SLA, use the responder command in the ipsla mode. To remove the set configuration, use the no form of the command.

responder [ twamp| [ twamp-light test-session test-session-id] ] [ timeout timeout-value]

Syntax Description


twamp	Configure TWAMP responder
twamp-light	Configure TWAMP-light responder
test-session `test-session-id`	Configure TWAMP-light test-session id. Range is 1 - 65535
timeout `timeout-value`	Configure the inactivity timeout period (in seconds) For TWAMP, the range is 1 - 604800. For TWAMP-light, the range is 60 - 86400

Command Default

Default timeout for TWAMP responder is 900 seconds.

By default, there is no timeout for TWAMP-light responder.

Command Modes

IPSLA configuration mode

Command History


Release	Modification
Release 6.3.1	This command is introduced for TWAMP responder.
Release 6.6.1	This command is introduced for TWAMP-light responder.

Usage Guidelines

No specific guidelines impact the use of this command.

Examples

This example shows how to configure the TWAMP responder:

Router(config)# ipsla
Router(config-ipsla)# responder twamp timeout 100

This example shows how to configure the TWAMP-light responder:

Router(config)# ipsla
Router(config-ipsla)# responder twamp-light test-session 1 timeout 100

responder twamp light

To configure the TWAMP-light responder, use the responder twamp-light command in the ipsla configuration mode.

responder twamp-light test-session test-session-id [ local-ip { local-ip-address | any { ipv4 | ipv6 } } local-port local-port-number remote-ip { remote-ip-address | any { ipv4 | ipv6 } } remote-port { remote-port-number | any } vrf { vrf-name | any | default } | timeout timeout-value ]

Syntax Description


test-session `test-session-id`	Configure TWAMP-light test-session id. Range: 1 - 65535
local-ip`{` `local-ip-address\|` any`{` ipv4`\|` ipv6`}` `}`	Configure the local ip-address or allow any local IPv4 or IPv6 address
local-port `local-port-number`	Configure the local UDP port number. Range: 1 - 65535
remote-ip`{` `remote-ip-address\|` any`{` ipv4`\|` ipv6`}` `}`	Configure the remote client's ip-address or allow connection from any remote IPv4 or IPv6 address
remote-port`{` `remote-port-number\|` any`}`	Configure the UDP port number of the remote client or allow connection from any remote port. Range: 1 - 65535
vrf`{` `vrf-name\|` any`\|` default`}`	Configure vrf for the local ip-address. Possible values for vrf: `vrf-name` of the vrf of the local ip-address any: use this only when local-ip is configured as any default: use this when the local ip-address belongs to default vrf
timeout `timeout-value`	Configure the inactivity timeout period (in seconds) For TWAMP-light, the range is 60 - 86400

Command Default

Default timeout is 900 seconds.

Command Modes

IPSLA configuration mode

Command History


Release	Modification
Release 7.4.1	The any option was included for local-ip, remote-ip, remote-port and vrf .
Release 6.6.1	This command was introduced.

Usage Guidelines

Caution must be taken by the administrator when using any option as this configuration opens up the specified local-port for packets from any IP address.
Configure vrf as any only when you configure local-ip as any .
Configure vrf with a valid vrf value, when you configure local-ip with a valid IPv4/IPv6 address.

Task ID


Task ID	Operation
monitor	read, write

Examples

This example shows how to configure the twamp-light responder:

Router# configure
Router(config)# ipsla
Router(config-ipsla)# responder twamp-light test-session 1 local-ip 192.0.2.10 local-port 13001 remote-ip 192.0.2.186 remote-port 13002 vrf default
Router(config-ipsla)# responder twamp-light test-session 1 timeout 60
Router(config-ipsla)# commit

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 ICMP path-echo 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. Range is 1 to 30.

Command Default

The default value is 16.

Command Modes

IP SLA operation ICMP path-echo history configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

The samples command is supported only when you configure an 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:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
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)# history 
RP/0/RP0/CPU0:router(config-ipsla-op-hist)# samples 30

Related Commands


Command	Description
buckets (history)	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.
operation	Configures an IP SLA operation.
schedule operation	Schedules an IP SLA operation.

scan delete-factor

To specify the frequency with which the MPLS LSP monitor (MPLSLM) instance searches for provider edge (PE) routers to delete, use the scan delete-factor command in the appropriate configuration mode. To return to the default value, use the no form of this command.

scan delete-factor factor-value

no scan delete-factor

Syntax Description


`factor-value`	Specifies a factor that is multiplied by the scan interval to determine the frequency at which the MPLS LSP monitor instance deletes the provider edge (PE) routers that are no longer valid. Range is 0 to 2147483647.

Command Default

factor-value : 1

Command Modes

IP SLA MPLS LSP monitor ping configuration

IP SLA MPLS LSP monitor trace configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

The scan delete-factor command specifies a factor value for automatic PE deletion. The specified factor-value is multiplied by the scan interval to acquire the frequency at which the MPLS LSP monitoring instance deletes not-found PEs. A scan delete factor of zero (0) means that provider edge (PE) routers that are no longer valid are never removed.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to use the scan delete-factor command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# mpls lsp-monitor
RP/0/RP0/CPU0:router(config-ipsla-mplslm)# monitor 1
RP/0/RP0/CPU0:router(config-ipsla-mplslm-def)# type mpls lsp ping
RP/0/RP0/CPU0:router(config-ipsla-mplslm-lsp-ping)# scan delete-factor 214

Related Commands


Command	Description
monitor	Configures an IP SLA MPLS LSP monitor instance.
scan interval	Specifies the frequency at which the MPLSLM instance checks the scan queue for updates.
type mpls lsp ping	Tests connectivity in an LSP path in an MPLS VPN.
type mpls lsp trace	Traces the hop-by-hop route of an LSP path in an MPLS VPN.

scan interval

To specify the frequency at which the MPLS LSP monitor (MPLSLM) instance checks the scan queue for updates, use the scan interval command in the appropriate configuration mode. To return to the default value, use the no form of this command.

scan interval scan-interval

no scan interval

Syntax Description


`scan-interval`	Time interval between provider edge (PE) router updates. Range is 1 to 70560.

Command Default

interval : 240 minutes

Command Modes

IP SLA MPLS LSP monitor ping configuration

IP SLA MPLS LSP monitor trace configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

Use the scan interval command to specify a frequency value in minutes at which the MPLS LSP monitoring instance checks the scan queue for PE updates. Updates from PE discovery are not processed immediately, but rather stored in a scan queue for batched processing at periodic intervals, specified by this value.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to use the scan command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# mpls lsp-monitor
RP/0/RP0/CPU0:router(config-ipsla-mplslm)# monitor 1
RP/0/RP0/CPU0:router(config-ipsla-mplslm-def)# type mpls lsp ping
RP/0/RP0/CPU0:router(config-ipsla-mplslm-lsp-ping)# scan interval 120

Related Commands


Command	Description
operation	Configures an IP SLA operation.
scan delete-factor	Specifies the frequency with which the MPLSLM instance searches for PE routers to delete.
schedule operation	Schedules an IP SLA operation.
type mpls lsp ping	Tests connectivity in an LSP path in an MPLS VPN.
type mpls lsp trace	Traces the hop-by-hop route of an LSP path in an MPLS VPN.

schedule monitor

To schedule MPLS LSP monitoring instances, use the schedule monitor command in IP SLA LSP monitor configuration mode. To unschedule the monitoring instances, use the no form of this command.

schedule monitor monitor-id

no schedule monitor [monitor-id]

Syntax Description


`monitor-id`	Number of the monitoring instance to schedule. Range is 1 to 2048.

Command Default

No schedule is configured.

Command Modes

IP SLA MPLS LSP monitor configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

The schedule monitor command enters IP SLA MPLS LSP monitor schedule configuration mode so that you can set the desired schedule parameters for the MPLS LSP monitor instance. This schedules the running of all operations created for the specified monitor instance.

To remove all configured schedulers, use the no schedule monitor command with no monitor-id argument.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to access and use the schedule monitor command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# mpls lsp-monitor
RP/0/RP0/CPU0:router(config-ipsla-mplslm)# schedule monitor 1
RP/0/RP0/CPU0:router(config-ipsla-mplslm-sched)#

Related Commands


Command	Description
frequency (IP SLA)	Configures the frequency interval during which LSP groups and operations are scheduled to start.
schedule period	Configures the amount of time during which all LSP operations are scheduled to start or run.
start-time	Determines the time when an operation starts.

schedule operation

To enter schedule configuration mode, use the schedule operation command in IP SLA configuration mode. To remove the scheduler, use the no form of this command.

schedule operation operation-number

no schedule operation operation-number

Syntax Description


operation-number	Configuration number or schedule number that is used to schedule an IP SLA operation. Range is 1 to 2048.

Command Default

None

Command Modes

IP SLA configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

The 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 schedule operation command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# schedule operation 1
RP/0/RP0/CPU0:router(config-ipsla-sched)#

Related Commands


Command	Description
ageout	Specifies the number of seconds to keep the operation in memory when it is not actively collecting information.
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.

schedule period

To configure the amount of time during which all LSP operations are scheduled to start or run, use the schedule period command in IP SLA MPLS LSP monitor schedule configuration mode. To remove the scheduler, use the no form of this command.

schedule period seconds

no schedule period

Syntax Description


`seconds`	Amount of time in seconds for which label switched path (LSP) operations are scheduled to run. Range is 1 to 604800.

Command Default

None

Command Modes

IP SLA MPLS LSP monitor schedule configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

Use the schedule period command to specify the amount of time in seconds during which all LSP operations are scheduled to start running. All LSP operations are scheduled equally spaced throughout the schedule period.

For example, if the schedule period is 600 seconds and there are 60 operations to be scheduled, they are scheduled at 10-second intervals.

Use the frequency command to specify how often the entire set of operations is performed. The frequency value must be greater than or equal to the schedule period.

You must configure the schedule period before you can start MPLS LSP monitoring. Start MPLS LSP monitoring using the start-time command.

Task ID


Task ID	Operations
monitor	read, write

Examples

The following example shows how to use the schedule period command:


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipsla 
RP/0/RP0/CPU0:router(config-ipsla)# mpls lsp-monitor
RP/0/RP0/CPU0:router(config-ipsla-mplslm)# schedule monitor 20
RP/0/RP0/CPU0:router(config-ipsla-mplslm-sched)# schedule period 6000

Related Commands


Command	Description
frequency (IP SLA)	Configures the frequency interval during which LSP groups and operations are scheduled to start.
start-time	Determines the time when the operation starts.

server twamp

To configure the TWAMP server, use the server twamp command in the appropriate mode. To remove the set configuration, use the no form of the command.

server twamp [ port number | timer inactivity value ]

no server twamp [ port number | timer inactivity value ]

Syntax Description


port	Configures the port for the server.
`number`	Port number. Range is 1 to 65535.
timer	Configures the timer for the server.
inactivity `value`	Inactivity timer value in seconds. Range is 1 to 6000.

Command Default

Default port is 862.

Default timer value is 900 seconds.

Command Modes

IPSLA configuration mode

Command History


Release	Modification
Release 6.3.1	This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID


Task ID	Operation
monitor	read, write

Examples

This example shows how to use the server twamp command:

RP/0/RP0/CPU0:router (config-ipsla) #  server twamp timer inactivity 100

show ipsla application

To display the information for the IP SLA application, use the show ipsla application command in XR EXEC mode.

show ipsla application

Syntax Description

This command has no keywords or arguments.

Command Default

None

Command Modes

XR EXEC mode

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

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 

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

        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
        Type of Operation: MPLS LSP PING
        Type of Operation: MPLS LSP TRACE

Number of configurable probes : 2047
SA Agent low memory water mark: 20480 (KB)

This table describes the significant fields shown in the display.

Table 2. show ipsla application Field Descriptions
Field	Description
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


Command	Description
low-memory	Configures a low-water memory mark.
operation	Configures an IP SLA operation.

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

Bias-Free Language

Results

Chapter: IP Service Level Agreement Commands

IP Service Level Agreement Commands

access-list

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Task ID

Examples

Related Commands

action (IP SLA)

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Task ID

Examples

Related Commands

ageout

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Task ID

Examples

Related Commands

buckets (history)

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Task ID

Examples

Related Commands

buckets (statistics hourly)

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Task ID

Examples

Related Commands

buckets (statistics interval)

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

control disable

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Task ID

Examples

Related Commands

datasize request

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Task ID

Examples

Related Commands

destination address (IP SLA)

Syntax Description

Command Default

Command Modes