Cisco IOS XR System Monitoring Command Reference for the Cisco

OL-26517-02

IP Service Level Agreement Commands

This module describes the Cisco IOS XR software commands to configure IP Service Level Agreements

(IP SLAs) on your router.

To use commands of this module, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using any command, contact your

AAA administrator for assistance.

For detailed information about IP SLA concepts, configuration tasks, and examples, see the Implementing

IP Service Level Agreements module in the Cisco IOS XR System Monitoring Configuration Guide for the

Cisco XR 12000 Series RouterCisco IOS XR System Monitoring Configuration Guide for the Cisco CRS

RouterCisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration GuideSystem

Monitoring Configuration Guide for Cisco NCS 6000 Series Routers.

•

access-list, page 127

•

action (IP SLA), page 129

•

ageout, page 132

•

buckets (history), page 134

•

buckets (statistics hourly), page 136

•

buckets (statistics interval), page 138

•

control disable, page 140

•

datasize request , page 142

•

destination address (IP SLA), page 145

•

destination port, page 147

•

distribution count, page 149

•

distribution interval, page 151

•

exp, page 153

•

filter, page 155

•

force explicit-null, page 157

•

frequency (IP SLA), page 159

Cisco IOS XR System Monitoring Command Reference for the Cisco CRS Router, Release 4.2.x

123

•

history, page 161

•

interval, page 163

•

ipsla, page 165

•

key-chain, page 167

•

life, page 169

•

lives, page 171

•

low-memory, page 173

•

lsp selector ipv4, page 175

•

lsr-path, page 177

•

maximum hops, page 179

•

maximum paths (IP SLA), page 181

•

monitor, page 183

•

mpls discovery vpn, page 185

•

mpls lsp-monitor, page 187

•

operation, page 189

•

output interface, page 191

•

output nexthop, page 193

•

packet count, page 195

•

packet interval, page 197

•

path discover, page 199

•

path discover echo, page 200

•

path discover path, page 202

•

path discover scan, page 204

•

path discover session, page 206

•

react, page 208

•

react lpd, page 211

•

reaction monitor, page 213

•

reaction operation, page 215

•

reaction trigger, page 217

•

responder, page 219

•

recurring, page 221

•

reply dscp, page 223

•

reply mode, page 225

124



OL-26517-02


•

responder twamp, page 227

•

samples, page 228

•

scan delete-factor, page 230

•

scan interval, page 232

•

schedule monitor, page 234

•

schedule operation, page 236

•

schedule period, page 238

•

server twamp, page 240

•

show ipsla application, page 241

•

show ipsla history, page 244

•

show ipsla mpls discovery vpn, page 247

•

show ipsla mpls lsp-monitor lpd, page 249

•

show ipsla mpls lsp-monitor scan-queue, page 251

•

show ipsla mpls lsp-monitor summary, page 253

•

show ipsla responder statistics, page 256

•

show ipsla statistics, page 258

•

show ipsla statistics aggregated, page 262

•

show ipsla statistics enhanced aggregated, page 272

•

show ipsla twamp connection, page 276

•

show ipsla twamp session, page 277

•

show ipsla twamp standards, page 278

•

source address , page 279

•

source port , page 281

•

start-time , page 283

•

statistics, page 286

•

tag (IP SLA), page 289

•

target ipv4, page 291

•

target pseudowire, page 293

•

target traffic-eng , page 295

•

threshold, page 297

•

threshold type average, page 299

•

threshold type consecutive, page 301

•

threshold type immediate, page 303

OL-26517-02


125

•

threshold type xofy, page 305

•

timeout (IP SLA), page 307

•

tos, page 309

•

ttl, page 311

•

type icmp echo, page 313

•

type icmp path-echo, page 315

•

type icmp path-jitter, page 317

•

type mpls lsp ping, page 319

•

type mpls lsp trace, page 321

•

type udp echo, page 323

•

type udp jitter, page 325

•

type udp ipv4 address, page 327

•

verify-data, page 329

•

vrf (IP SLA), page 331

•

vrf (IP SLA MPLS LSP monitor), page 333


126


OL-26517-02

IP Service Level Agreement Commands access-list

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

Release 3.6.0

Release 3.6.0

Release 3.7.2

Release 5.0.0

Modification

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 monitor

Operations read, write


127 OL-26517-02

IP Service Level Agreement Commands access-list

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

RP/0/0RP0RSP0/CPU0:router:hostname# configure

RP/0/0RP0RSP0/CPU0:router:hostname(config)# ipsla

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla)# mpls lsp-monitor

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm)# monitor 1

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-def)# type mpls lsp ping

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lsp-ping)# access-list ipsla

Related Commands

Command

scan interval, on page 232

type mpls lsp ping, on page 319

type mpls lsp trace, on page 321

Description

Specifies the frequency at which the MPLS LSP monitor instance checks the scan queue for updates.

Tests connectivity in an LSP path in an MPLS VPN.

Traces the hop-by-hop route of an LSP path in an

MPLS VPN.

128


OL-26517-02

IP Service Level Agreement Commands action (IP SLA)

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 trigger

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.

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

Release 3.3.0

Release 3.3.0

Release 3.5.0

Release 3.7.2

Release 5.2.3

Modification



This command was added to IP SLA MPLS LSP monitor reaction configuration mode.



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.


129 OL-26517-02


Task ID

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 monitor


Examples The following example shows how to use the action command with the logging keyword:



RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla)# reaction operation 432

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-react)# react connection-loss

RP/0/0RP0RSP0/CPU0:router:hostname(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/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm)# reaction monitor 1

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-react)# react connection-loss

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-react-cond)# action logging


Command

mpls lsp-monitor, on page 187

operation, on page 189

schedule operation, on page 236

reaction monitor, on page 213

reaction operation, on page 215

react, on page 208

threshold, on page 297

threshold type average, on page 299

Description

Configures MPLS label switched path (LSP) monitoring.

Configures an IP SLA operation.

Schedules an IP SLA operation.

Configures MPLS LSP monitoring reactions.

Configures certain actions that are based on events under the control of the IP SLA agent.

Specifies an element to be monitored for a reaction.

Sets the lower-limit and upper-limit values.

Takes action on average values to violate a threshold.

130


OL-26517-02


Command

threshold type consecutive, on page 301

threshold type immediate, on page 303

threshold type xofy, on page 305

Description

Takes action after a number of consecutive violations.

Takes action immediately upon a threshold violation.

Takes action upon X violations in Y probe operations.

OL-26517-02


131

IP Service Level Agreement Commands ageout

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

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





Usage Guidelines No specific guidelines impact the use of this command.

Task ID

Task ID monitor


Examples The following example shows how to use the ageout command:



RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla)# schedule operation 1

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-sched)# ageout 3600

132


OL-26517-02



Command



Description



ageout

OL-26517-02


133

IP Service Level Agreement Commands buckets (history)

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

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.0.0

Modification





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 monitor


134


OL-26517-02

IP Service Level Agreement Commands buckets (history)

Examples The following example shows how to use the buckets command in IP SLA UDP echo configuration mode:



RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla)# operation 1

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op)# type udp echo

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-echo)# history

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op-hist)# buckets 30


Command

history, on page 161



Description

Configures the history parameters for the IP SLA operation.



OL-26517-02


135

IP Service Level Agreement Commands buckets (statistics hourly)

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

Release 3.3.0

Release 3.3.0

Release 3.5.0

Release 3.7.2

Release 5.2.3

Modification



This command was added to IP SLA MPLS LSP monitor statistics configuration mode.



Usage Guidelines The buckets command with the hours argument is valid only for the statistics command with the hourly keyword.

Task ID

Task ID monitor


136


OL-26517-02

IP Service Level Agreement Commands buckets (statistics hourly)

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/0RP0RSP0/CPU0:router:hostname(config-ipsla-op)# type udp jitter

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-jitter)# statistics hourly

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op-stats)# buckets 10


Command

statistics, on page 286

Description

Sets the statistics collection parameters for the operation.

OL-26517-02


137

IP Service Level Agreement Commands buckets (statistics interval)

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 History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





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/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-jitter)# statistics interval 60

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op-stats)# buckets 50

138


OL-26517-02



Command


buckets (statistics interval)

Description


OL-26517-02


139

IP Service Level Agreement Commands control disable

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

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





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 monitor


140


OL-26517-02

IP Service Level Agreement Commands control disable

Examples The following example shows how to use the control disable command in IP SLA UDP jitter configuration mode:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-jitter)# control disable


Command



Description



OL-26517-02


141

IP Service Level Agreement Commands datasize request

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



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

Release 3.3.0

Modification


142


OL-26517-02

IP Service Level Agreement Commands datasize request

Release

Release 3.3.0

Release 3.4.0

Release 3.5.0

Release 3.7.2

Release 5.2.3

Modification


Support was added for IP SLA MPLS LSP ping configuration mode.

This command was added to IP SLA MPLS LSP monitor ping configuration mode.




Task ID

Task ID monitor


Examples The following example shows how to use the datasize request command in IP SLA UDP jitter configuration mode:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-jitter)# datasize request 512


Command




type icmp echo, on page 313

type icmp path-echo, on page 315



Description




Configures an IP SLA ICMP echo operation.

Configures an IP SLA ICMP path-echo operation.



OL-26517-02


143

datasize request

Command

type icmp path-jitter, on page 317

type udp jitter, on page 325


Description

Configures an IP SLA ICMP path-jitter operation.

Configures an IP SLA UDP jitter operation.

144


OL-26517-02

IP Service Level Agreement Commands destination address (IP SLA)

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 History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





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 monitor



145 OL-26517-02

IP Service Level Agreement Commands destination address (IP SLA)

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/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-jitter)# destination address 192.0.2.12


Command



Description



146


OL-26517-02

IP Service Level Agreement Commands destination port

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 History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





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 monitor


OL-26517-02


147

IP Service Level Agreement Commands destination port

Examples The following example shows how to designate a port for the destination port command in IP SLA UDP jitter configuration mode:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-jitter)# destination port 11111


Command



Description



148


OL-26517-02

IP Service Level Agreement Commands distribution count

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 History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





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 monitor



149 OL-26517-02

IP Service Level Agreement Commands distribution count

Examples The following example shows how to set the number of statistics distribution for the distribution count command:






RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op-stats)# distribution count 15


Command

buckets (statistics hourly), on page 136

distribution interval, on page 151

maximum hops, on page 179

maximum paths (IP SLA), on page 181


Description

Sets the number of hours in which statistics are kept.

Sets the time interval (in milliseconds) for each statistical distribution.

Sets the number of hops in which statistics are maintained for each path for the IP SLA operation.

Sets the number of paths in which statistics are maintained for each hour for an IP SLA operation.


150


OL-26517-02

IP Service Level Agreement Commands distribution interval

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 History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





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 monitor



151 OL-26517-02

IP Service Level Agreement Commands distribution interval

Examples The following example shows how to set the time interval for the distribution interval command:






RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op-stats)# distribution interval 50


Command


distribution count, on page 149




Description


Sets the number of statistics distributions that are kept for each hop during the lifetime of the IP SLA operation.




152


OL-26517-02

IP Service Level Agreement Commands exp

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


Command History

Release

Release 3.4.0

Release 3.4.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification



This command was added to the IP SLA MPLS LSP monitor ping and monitor trace configuration modes.



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


153 OL-26517-02

IP Service Level Agreement Commands exp

Task ID 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 monitor


Examples The following example shows how to use the exp command:




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op)# type mpls lsp trace

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mpls-lsp-trace)# exp 5

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





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-def)# type mpls lsp trace

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lsp-trace)# exp 5


Command





Description





MPLS VPN.

154


OL-26517-02

IP Service Level Agreement Commands filter

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 failures

Stores history data for all operations, if set.

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 History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.0.0

Modification





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



• IP SLA UDP echo

If you use the no form of the filter command, the history statistics are not collected.

Task ID

Task ID monitor



155 OL-26517-02

IP Service Level Agreement Commands filter

Examples The following example shows how to use the filter command in IP SLA UDP echo configuration mode:






RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op-hist)# filter all


Command



Description



156


OL-26517-02

IP Service Level Agreement Commands force explicit-null

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


Command Default An explicit null label is not added.





Command History

Release

Release 3.4.0

Release 3.4.0

Release 3.5.0

Release 3.7.2

Modification



This command was added to IP SLA MPLS LSP monitor ping and monitor trace configuration modes.


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.


157 OL-26517-02

IP Service Level Agreement Commands force explicit-null

Task ID

Task ID monitor


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





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mpls-lsp-trace)# force explicit-null


Command





Description





MPLS VPN.

158


OL-26517-02

IP Service Level Agreement Commands frequency (IP SLA)

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.








IP SLA MPLS LSP monitor schedule configuration

Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.4.0

Release 3.5.0

Release 3.7.2

Release 5.2.3

Modification



Support was added for IP SLA MPLS ping and IP SLA MPLS trace configuration modes.

This command was added to IP SLA MPLS LSP monitor schedule configuration mode.




159 OL-26517-02

IP Service Level Agreement Commands frequency (IP SLA)

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 monitor


Examples The following example shows how to use the frequency command in IP SLA UDP jitter configuration mode:





RP/0/0RP0RSP0/CPU0:router:hostname(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/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm)# schedule monitor 1

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-sched)# frequency 1200

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-sched)# schedule period 600


Command



schedule period, on page 238

Description



Configures the amount of time during which all LSP operations are scheduled to start or run.

160


OL-26517-02

IP Service Level Agreement Commands history

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 buckets filter all failures lives lives

Sets the number of history buckets that are kept during the lifetime of the IP SLA operation.

Number of history buckets that are kept during the lifetime of an IP SLA operation.

Range is 1 to 60.

Defines the type of information that is kept in the history table for the IP SLA operation.

Stores history data for all operations, if set.

Stores data for operations that failed, if set.

Sets the number of lives that are maintained in the history table for an IP SLA operation.

Number of lives that are maintained in the history table for an IP SLA operation.

Range is 0 to 2.









Command History

Release

Release 3.3.0

Modification



161 OL-26517-02

IP Service Level Agreement Commands history

Release

Release 3.3.0

Release 3.4.0

Release 3.7.2

Modification


Support was added for IP SLA MPLS LSP ping and IP SLA MPLS

LSP trace configuration modes.


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 monitor


Examples The following example shows how to use the history command in IP SLA UDP echo configuration mode:






RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op-hist)#


Command

buckets (history), on page 134

filter, on page 155



lives, on page 171

samples, on page 228

Description


Defines the type of information that are kept in the history table for the IP SLA operation.



Sets the number of lives that are maintained in the history table for an IP SLA operation.

Sets the number of hop entries that are kept in the history table for an IP SLA ICMP path-echo operation.

162


OL-26517-02

IP Service Level Agreement Commands interval

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

Release 3.5.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification





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 monitor



163 OL-26517-02

IP Service Level Agreement Commands interval

Examples The following example shows how to use the interval command:



RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla)# mpls discovery vpn

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


Command

mpls discovery vpn, on page 185


Description

Configures MPLS label switched path (LSP) provider edge (PE) router discovery.


164


OL-26517-02

IP Service Level Agreement Commands ipsla

ipsla

To enter IP SLA configuration mode and configure IP Service Level Agreements, use the ipsla command in

Global Configuration modeXR Config mode. To return to the default setting, use the no form of this command.

ipsla no ipsla



Command Modes Global Configuration modeXR Config mode

Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





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 monitor


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



RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla)#


165 OL-26517-02

IP Service Level Agreement Commands ipsla


Command

key-chain, on page 167

low-memory, on page 173





reaction trigger, on page 217

responder, on page 219


Description

Configures MD5 authentication for IP SLA control messages.

Configures a low-water memory mark.





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

Enables the IP SLA responder for UDP echo or jitter operations.


166


OL-26517-02

IP Service Level Agreement Commands key-chain

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

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





Usage Guidelines When you configure the key-chain command, you must also configure the key chain command in global configurationXR Config mode to provide MD5 authentication.

Task ID

Task ID monitor


Examples The following example shows how to use the ipsla key-chain command:



RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla)# key-chain ipsla-keys


167 OL-26517-02

IP Service Level Agreement Commands key-chain


Command



Description



168


OL-26517-02

IP Service Level Agreement Commands life

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 seconds

Schedules the operation to run indefinitely.

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.

None


Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification






Task ID

Task ID monitor


Examples The following example shows how to use the life command:




169 OL-26517-02

IP Service Level Agreement Commands life


RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-sched)# life forever


Command



Description



170


OL-26517-02

IP Service Level Agreement Commands lives

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 History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Modification




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



• IP SLA UDP echo

If you use the no form of the lives command, the history statistics are not collected.

Task ID

Task ID monitor



171 OL-26517-02

IP Service Level Agreement Commands lives

Examples The following example shows how to use the lives command in IP SLA UDP echo configuration mode:






RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op-hist)# lives 2


Command


filter, on page 155



samples, on page 228

Description





Sets the number of hop entries that are kept in the history table for an IP SLA ICMP path-echo operation.

172


OL-26517-02

IP Service Level Agreement Commands low-memory

low-memory

low-memory value no low-memory

Syntax Description value Low-water memory mark watermark value. Range is 0 to 4294967295.

Command Default The default value is 20 MB (free memory).


Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





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 monitor


Examples The following example shows how to use the low-memory command:



RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla)# low-memory 102400


173 OL-26517-02

IP Service Level Agreement Commands low-memory


Command



show ipsla application, on page 241

Description



Displays the information for the IP SLA application.

174


OL-26517-02

IP Service Level Agreement Commands lsp selector ipv4

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 History

Release

Release 3.4.0

Release 3.4.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification






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.


175 OL-26517-02

IP Service Level Agreement Commands lsp selector ipv4

Task ID

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


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





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mpls-lsp-trace)# lsp selector ipv4 127.10.10.1


Command





Description





MPLS VPN.

176


OL-26517-02

IP Service Level Agreement Commands lsr-path

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


Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.0.0

Modification





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 monitor



177 OL-26517-02

IP Service Level Agreement Commands lsr-path

Examples The following example shows how to use the lsr-path command in IP SLA ICMP Path-echo configuration mode:




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op)# type icmp path-echo

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-icmp-path-echo)# lsr-path 192.0.2.40


Command



Description



178


OL-26517-02

IP Service Level Agreement Commands maximum hops

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 History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.0.0

Modification


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 monitor


Examples The following example shows how to set the number of hops for the statistics for the maximum command:





179 OL-26517-02

IP Service Level Agreement Commands maximum hops


RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-icmp-path-echo)# statistics hourly

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op-stats)# maximum hops 20


Command






Description






180


OL-26517-02

IP Service Level Agreement Commands maximum paths (IP SLA)

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 History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.0.0

Modification

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 monitor


Examples The following example shows how to set the number of paths for the statistics for the maximum paths command:




181 OL-26517-02

IP Service Level Agreement Commands maximum paths (IP SLA)



RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-icmp-path-echo)# statistics hourly

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op-stats)# maximum paths 20


Command






Description






182


OL-26517-02

IP Service Level Agreement Commands monitor

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

Release 3.5.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification





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 monitor


Examples The following example shows how to use the monitor command:





183 OL-26517-02

IP Service Level Agreement Commands monitor


RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-def)#


Command



Description



184


OL-26517-02

IP Service Level Agreement Commands mpls discovery vpn

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 History

Release

Release 3.5.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

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 monitor


Examples

Modification





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



RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla)# mpls discovery vpn

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mpls-discovery-vpn)#


185 OL-26517-02

mpls discovery vpn


Command

interval, on page 163



Description

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


186


OL-26517-02

IP Service Level Agreement Commands mpls lsp-monitor

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




Command History

Release

Release 3.5.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification





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 monitor


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




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm)#


187 OL-26517-02

IP Service Level Agreement Commands mpls lsp-monitor


Command



Command

monitor, on page 183



schedule monitor, on page 234

Description


Description

Configures an IP SLA MPLS LSP monitor instance.



Schedules an IP SLA MPLS LSP monitor instance.

188


OL-26517-02

IP Service Level Agreement Commands operation

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 History

Examples

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification






Task ID

Task ID monitor


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




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op)#


189 OL-26517-02

IP Service Level Agreement Commands operation


Command


Description


190


OL-26517-02

IP Service Level Agreement Commands output interface

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

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

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 History

Release

Release 3.5.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification





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.


191 OL-26517-02

IP Service Level Agreement Commands output interface

Task ID

Task ID monitor


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




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op)# type mpls ls output interface pos

0/1/0/0


Command


output nexthop, on page 193




Description


Configures the next-hop address to be used for LSP ping or LSP trace operations.




MPLS VPN.

192


OL-26517-02

IP Service Level Agreement Commands output nexthop

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 History

Release

Release 3.6.0

Release 3.6.0

Release 3.7.2

Release 5.0.0

Modification





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 monitor



193 OL-26517-02

IP Service Level Agreement Commands output nexthop

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





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mpls-lsp-trace)# output nexthop 10.1.1.1


Command


output interface, on page 191




Description


Configures the echo request output interface to be used for LSP ping or LSP trace operations.




MPLS VPN.

194


OL-26517-02

IP Service Level Agreement Commands packet count

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


Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification






Task ID

Task ID monitor


Examples The following example shows how to use the packet count command:





195 OL-26517-02

IP Service Level Agreement Commands packet count


RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-jitter)# packet count 30


Command



packet interval, on page 197

Description



Specifies the interval between packets.

196


OL-26517-02

IP Service Level Agreement Commands packet interval

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 110 to 60000 (in milliseconds).

Command Default The default packet interval is 20 ms.

Command Modes IP SLA UDP jitter configuration


Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification






Task ID

Task ID monitor


Examples The following example shows how to use the packet interval command:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-jitter)# packet interval 30


197 OL-26517-02

IP Service Level Agreement Commands packet interval


Command



packet count, on page 195

Description



Specifies the number of packets that are to be transmitted during a probe.

198


OL-26517-02

IP Service Level Agreement Commands path discover

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 History

Release

Release 3.6.0

Release 3.6.0

Release 3.7.2

Release 5.0.0

Modification






Task ID

Task ID monitor


Examples The following example shows how to enter path discover submode:






RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lsp-ping)#

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lpd)# path discover


199 OL-26517-02

IP Service Level Agreement Commands path discover echo

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

timeout value

Configures the number of timeout retry attempts for MPLS LSP echo requests sent during path discovery. Range is 0 to 10. Default is 3.

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

Release 3.6.0

Release 3.6.0

Modification



200


OL-26517-02

IP Service Level Agreement Commands path discover echo

Release

Release 3.7.2

Release 5.0.0

Modification



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 monitor


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






RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lsp-ping)# path discover

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lsp-lpd)# echo interval 777


Command

path discover path, on page 202

path discover scan, on page 204

path discover session, on page 206

Description

Configures MPLS LSP path parameters.

Configures MPLS LSP scan parameters.

Configures MPLS LSP session parameters.

OL-26517-02


201

IP Service Level Agreement Commands path discover path

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


retry range secondary frequency both connection-loss timeout value

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.

Configures a secondary frequency to use after a failure condition (that is, a connection-loss or timeout) occurs.

Enable secondary frequency for a timeout and connection loss.

Enable secondary frequency for only a connection loss.

Enable secondary frequency for only a timeout.

Frequency value range is 1 to 604800.


Command Modes MPLSLM LPD configuration

Command History

Release

Release 3.6.0

Release 3.6.0

Release 3.7.2

Release 5.0.0

Modification





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.

202


OL-26517-02

IP Service Level Agreement Commands path discover path

Task ID

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

Task ID monitor


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







RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lsp-lpd)# path retry 12

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lsp-lpd)# path secondary frequency both 10


Command

path discover echo, on page 200



Description

Configures MPLS LSP echo parameters.



OL-26517-02


203

IP Service Level Agreement Commands path discover scan

path discover scan

To configure MPLS LSP scan parameters, use the path discover scan command in MPLS LSP monitor


path discover scan period value

no path discover scan period value


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

Release 3.6.0

Release 3.6.0

Release 3.7.2

Release 5.0.0

Modification





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 monitor


204


OL-26517-02

IP Service Level Agreement Commands path discover scan

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







RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lsp-lpd)# scan period 2


Command




Description




OL-26517-02


205

IP Service Level Agreement Commands path discover session

path discover session

To configure MPLS LSP session parameters, use the path discover session command in MPLS LSP monitor


path discover session {limit value| timeout value}

no path discover session {limit value| timeout value}


limit value

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

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

Release 3.6.0

Release 3.6.0

Release 3.7.2

Release 5.0.0

Modification





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 monitor


206


OL-26517-02

IP Service Level Agreement Commands path discover session

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







RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lsp-lpd)# session timeout 22


Command




Description




OL-26517-02


207

IP Service Level Agreement Commands react

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

[dest-to-source |

source-to-dest]

Specifies that a reaction occurs if there is a connection-loss for the monitored operation.

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 timeout verify-error

Specifies that a reaction occurs if the round-trip value violates the upper threshold or lower threshold.

Specifies that a reaction occurs if there is a timeout for the monitored operation.

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

208


OL-26517-02


Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.5.0

Release 3.7.2

Release 5.2.3

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.

Task ID

Task ID monitor


Examples

Modification



This command was added to IP SLA MPLS LSP monitor reaction configuration mode.



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




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-react)# react connection-loss

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-react-cond)#

The following example shows how to use the react command with the jitter-average keyword:




OL-26517-02


209


RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-react)# react jitter-average


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




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-react)# react packet-loss dest-to-source


The following example shows how to use the react command with the rtt keyword:




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-react)# react rtt


The following example shows how to use the react command with the timeout keyword:




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-react)# react timeout


The following example shows how to use the react command with the verify-error keyword:




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-react)# react verify-error



Command

action (IP SLA), on page 129








Description

Specifies what action or combination of actions the operation performs when you configure the react command or when threshold events occur.








210


OL-26517-02

IP Service Level Agreement Commands react lpd

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 tree-trace action logging

Specifies that a reaction should occur if there is a status violation for the monitored LPD group.

Specifies that a reaction should occur if there is a path discovery violation for the monitored LPD group.

Configures the action to be taken on threshold violation.

Specifies the generation of a syslog alarm on threshold violation.


Command Modes IP SLA MPLS LSP monitor configuration

Command History

Release

Release 3.6.0

Release 3.6.0

Release 3.7.2

Release 5.0.0

Modification





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 monitor



211 OL-26517-02

IP Service Level Agreement Commands react lpd

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/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-react)# react lpd lpd-group action logging


Command



Description



212


OL-26517-02

IP Service Level Agreement Commands reaction monitor

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 History

Release

Release 3.5.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification





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 monitor



213 OL-26517-02

IP Service Level Agreement Commands reaction monitor

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





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-react)#


Command



react, on page 208




Description

Specifies what action or combination of actions the operation performs when you configure the react command or when threshold events occur.



Schedules an IP SLA MPLS LSP monitor instance.

Specifies to take action after a number of consecutive violations.

Specifies to take action immediately upon a threshold violation.

214


OL-26517-02

IP Service Level Agreement Commands reaction operation

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 History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification






Task ID

Task ID monitor


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




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-react)#


215 OL-26517-02

IP Service Level Agreement Commands reaction operation


Command



Description



216


OL-26517-02

IP Service Level Agreement Commands reaction trigger

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

Operation that contains a configured action-type trigger and can generate reaction events. Range is 1 to 2048.

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 History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





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 monitor



217 OL-26517-02

IP Service Level Agreement Commands reaction trigger

Examples The following example shows how to use the ipsla reaction trigger command:



RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla)# reaction trigger 1 2


Command



Description



218


OL-26517-02

IP Service Level Agreement Commands responder

responder

To enable the IP SLA responder for UDP echo or jitter operations, use the responder command in IP SLA configuration mode. To disable the responder, use the no form of this command.

responder no responder


Command Default The IP SLA responder command is disabled.


Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





Usage Guidelines An IP address and port are configured and identified as a permanent port (for example, a port to which the responder is permanently listening). If no IP address and port are configured, the responder handles only dynamic ports (for example, ports that are listened to when requested by a remote operation).

Task ID

Task ID monitor


Examples The following example shows how to enable the IP SLA responder:



RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla)# responder

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-resp)#


219 OL-26517-02

IP Service Level Agreement Commands responder


Command

type udp ipv4 address, on page 327

Description

Configures a permanent port in the IP SLA Responder for UDP echo or jitter operations.

220


OL-26517-02

IP Service Level Agreement Commands recurring

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


Command Default Recurring is disabled.


Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification






Task ID

Task ID monitor


Examples The following example shows how to use the recurring command:




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-sched)# recurring


221 OL-26517-02

IP Service Level Agreement Commands recurring


Command



Description



222


OL-26517-02

IP Service Level Agreement Commands reply dscp

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 History

Release

Release 3.4.0

Release 3.4.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification






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


223 OL-26517-02

IP Service Level Agreement Commands reply dscp

Task ID 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 monitor


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




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op)# type mpls lsp ping

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mpls-lsp-ping)# reply dscp 5


Command





Description





MPLS VPN.

224


OL-26517-02

IP Service Level Agreement Commands reply mode

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

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.

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 History

Release

Release 3.4.0

Release 3.4.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification




The control-channel keyword was added in IP SLA MPLS LSP ping configuration mode.



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


225 OL-26517-02

IP Service Level Agreement Commands reply mode

Task ID 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 monitor


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





RP/0/0RP0RSP0/CPU0:router:hostname(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/0RP0RSP0/CPU0:router:hostname(config-ipsla-mpls-lsp-ping)# target pseudowire 192.168.1.4

4211

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mpls-lsp-ping)# reply mode control-channel


Command





Description





MPLS VPN.

226


OL-26517-02

IP Service Level Agreement Commands responder twamp

responder twamp

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

responder twamp[ timeout value ]

no responder twamp [ timeout value ]


timeout value Inactivity timeout period (in seconds). Range is 1 to 604800.

Command Default Default timeout is 900 seconds.

Command Modes IPSLA configuration mode

Command History

Release

Release 5.1.1

Modification



Task ID

Task ID monitor

Operation read, write

Examples This example shows how to run the responder twamp command:

RP/0/0RP0RSP0/CPU0:router:hostname (config-ipsla) # responder twamp timeout 100

OL-26517-02


227

IP Service Level Agreement Commands samples

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 Modes IP SLA operation ICMP path-echo history configuration

Command History

Release

Release 3.3.0

Release 3.7.2

Release 5.0.0

Modification




Usage Guidelines The samples command is supported only when you configure an IP SLA ICMP path-echo operation.

Task ID

Task ID monitor


Examples The following example shows how to use the samples command:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-icmp-path-echo)# history

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op-hist)# samples 30

228


OL-26517-02



Command


filter, on page 155

history, on page 161



samples

Description



Configures the history parameters for the IP SLA operation.



OL-26517-02


229

IP Service Level Agreement Commands scan delete-factor

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 History

Release

Release 3.5.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification





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 monitor


230


OL-26517-02

IP Service Level Agreement Commands scan delete-factor

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






RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lsp-ping)# scan delete-factor 214


Command


scan interval, on page 232



Description


Specifies the frequency at which the MPLSLM instance checks the scan queue for updates.



MPLS VPN.

OL-26517-02


231

IP Service Level Agreement Commands scan interval

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 History

Release

Release 3.5.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification





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 monitor


232


OL-26517-02

IP Service Level Agreement Commands scan interval

Examples The following example shows how to use the scan command:






RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lsp-ping)# scan interval 120


Command


scan delete-factor, on page 230




Description


Specifies the frequency with which the MPLSLM instance searches for PE routers to delete.




MPLS VPN.

OL-26517-02


233

IP Service Level Agreement Commands schedule monitor

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 History

Release

Release 3.5.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification





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 monitor


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




234


OL-26517-02

IP Service Level Agreement Commands schedule monitor


RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-sched)#


Command

frequency (IP SLA), on page 159

schedule period, on page 238

start-time , on page 283

Description

Configures the frequency interval during which LSP groups and operations are scheduled to start.

Configures the amount of time during which all LSP operations are scheduled to start or run.

Determines the time when an operation starts.

OL-26517-02


235

IP Service Level Agreement Commands schedule operation

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 History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





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 monitor


Examples The following example shows how to use the ipsla schedule operation command:




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-sched)#

236


OL-26517-02



Command

ageout, on page 132


life, on page 169

recurring, on page 221


schedule operation

Description

Specifies the number of seconds to keep the operation in memory when it is not actively collecting information.


Specifies the length of time to execute.

Indicates that the operation starts automatically at the specified time and for the specified duration every day.

Determines the time when the operation starts.

OL-26517-02


237

IP Service Level Agreement Commands schedule period

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 Modes IP SLA MPLS LSP monitor schedule configuration

Command History

Release

Release 3.5.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification





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 monitor


238


OL-26517-02

IP Service Level Agreement Commands schedule period

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





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-sched)# schedule period 6000


Command

frequency (IP SLA), on page 159


Description

Configures the frequency interval during which LSP groups and operations are scheduled to start.

Determines the time when the operation starts.

OL-26517-02


239

IP Service Level Agreement Commands server twamp

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 ]

noserver twamp [ port number | timer inactivity value ]

Syntax Description port number timer

inactivity value

Configures the port for the server.

Port number. Range is 1 to 65535.

Configures the timer for the server.

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

Release 5.1.1

Modification



Task ID

Task ID monitor

Operation read, write

Examples This example shows how to use the server twamp command:

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

240


OL-26517-02

IP Service Level Agreement Commands show ipsla application

show ipsla application

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




Command Modes EXEC modeXR EXEC mode

Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification






Task ID

Task ID monitor

Operations read

Examples The following sample output is from the show ipsla application command:

RP/0/0RP0RSP0/CPU0:router:hostname# 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


241 OL-26517-02

IP Service Level Agreement Commands show ipsla application

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)

RP/0/0RP0RSP0/CPU0:router:hostname#show ipsla application

Estimated system max number of entries: 2048

Number of Entries configured: 143

Number of active Entries : 111

Number of pending Entries : 0

Number of inactive Entries : 32

Supported Operation Types: 1

Type of Operation: UDP JITTER

Number of configurable probes : 1905

SA Agent low memory water mark: 20480 (KB)

This table describes the significant fields shown in the display.

Table 14: show ipsla application Field Descriptions

Field

Estimated system max number of entries

Number of Entries configured

Number of active Entries

Number of pending Entries

Number of inactive Entries

Supported Operation Types

Number of configurable probes

Description

Maximum number of operations that are configured in the system. The low-memory configured parameter and the available memory in the system are given.

Total number of entries that are configured, such as active state, pending state, and inactive state.

Number of entries that are in the active state. The active entries are scheduled and have already started a life period.

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

Types of operations that are supported by the system.

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.

242


OL-26517-02


Field

SA Agent low memory water mark


Command

low-memory, on page 173



Description

Available memory for the minimum system below which the IP SLA feature does not configure any more operations.

Description

Configures a low-water memory mark.


OL-26517-02


243

IP Service Level Agreement Commands show ipsla history

show ipsla history

To display the history collected for all IP SLA operations or for a specified operation, use the show ipsla

history command in EXEC modeXR EXEC mode.

show ipsla history [ operation-number ]

Syntax Description operation-number (Optional) Number of the IP SLA operation.



Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





Usage Guidelines

4

5

2

3

Code

1

By default, history statistics are not collected. To have any data displayed by using the show ipsla history command, you must configure the history collection.

This table lists the response return values that are used in the show ipsla history command.

Table 15: Response Return Values for the show ipsla history Command

Description

Okay

Disconnected

Over Threshold

Timeout

Busy

244


OL-26517-02


Task ID

Examples

8

9

10

Code

6

7

Description

Not Connected

Dropped

Sequence Error

Verify Error

Application Specific

If the default tabular format is used, the response return description is displayed as code in the Sense column.

The Sense field is always used as a return code.

Task ID monitor

Operations read

The following sample output is from the show ipsla history command:

RP/0/0RP0RSP0/CPU0:router:hostname# show ipsla history 1

Point by point History

Multiple Lines per Entry

Line 1:

Entry

LifeI

= Entry number

= Life index

BucketI = Bucket index

SampleI = Sample index

SampleT = Sample start time

CompT = RTT (milliseconds)

Sense = Response return code

1

1

1

Line 2 has the Target Address

Entry LifeI BucketI SampleI

1 0 0 0

0

0

0

1

2

3

0

0

0

SampleT CompT

1134419252539 9

1134419312509 6

1134419372510 6

1134419432510 5


Table 16: show ipsla history Field Descriptions

Field

Entry number

LifeI

BucketI

Description

Entry number.

Life index.

Bucket index.

Sense

1

1

1

1

TargetAddr

192.0.2.6

192.0.2.6

192.0.2.6

192.0.2.6

OL-26517-02


245


Field

SampleI

SampleT

CompT

Sense

TargetAddr

Description

Sample index.

Sample start time.

Completion time in milliseconds.

Response return code.

IP address of intermediate hop device or destination device.


Command

show ipsla statistics aggregated, on page 262

Description

Displays the statistical errors for all the IP SLA operations or for a specified operation.

246


OL-26517-02

IP Service Level Agreement Commands show ipsla mpls discovery vpn

show ipsla mpls discovery vpn

To display routing information relating to the BGP next-hop discovery database in the MPLS VPN network, use the show ipsla mpls discovery vpn command in EXEC modeXR EXEC mode.

show ipsla mpls discovery vpn




Command History

Release

Release 3.5.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification






Task ID

Task ID monitor

Operations read

Examples The following sample output is from the show ipsla mpls discovery vpn command:

RP/0/0RP0RSP0/CPU0:router:hostname# show ipsla mpls discovery vpn

Next refresh after: 46 seconds

BGP next hop

192.255.0.4

Prefix

192.255.0.4/32

192.255.0.5

192.254.1.6

192.255.0.5/32

192.254.1.0/24

VRF red blue green red green yellow

5

3

4

PfxCount

10

5

7


247 OL-26517-02

IP Service Level Agreement Commands show ipsla mpls discovery vpn


Table 17: show ipsla mpls discovery vpn Field Descriptions

Field

BGP next hop

Prefix

VRF

PfxCount

Description

Identifier for the BGP next-hop neighbor.

IPv4 Forward Equivalence Class (FEC) of the BGP next-hop neighbor to be used by the MPLS LSP ping or trace operation.

Names of the virtual routing and forwarding instances

(VRFs) that contain routing entries for the specified

BGP next-hop neighbor.

Count of the routing entries that participate in the

VRF for the specified BGP next-hop neighbor.

248


OL-26517-02

IP Service Level Agreement Commands show ipsla mpls lsp-monitor lpd

show ipsla mpls lsp-monitor lpd

To display LSP Path Discovery (LPD) operational status, use the show ipsla mpls lsp-monitor lpd command in EXEC modeXR EXEC mode.

show ipsla mpls lsp-monitor lpd {statistics [group-ID| aggregated group-ID]| summary group}

statistics group-ID

aggregated group-ID

summary group- ID

Displays statistics for the specified LPD group, including the latest LPD start time, return code, completion time, and paths.

Displays the aggregated statistics of the LPD group.

Displays the current LPD operational status, which includes LPD start time, return code, completion time, and all ECMP path information.



Command History

Release

Release 3.6.0

Release 3.6.0

Release 3.7.2

Release 5.0.0

Modification





Usage Guidelines For the aggregated group ID, a maximum of two buckets are allowed.

Task ID

Task ID monitor

Operations read


249 OL-26517-02

IP Service Level Agreement Commands show ipsla mpls lsp-monitor lpd

Examples The following sample output is from the show ipsla mpls lsp-monitor lpd statistics command:

RP/0/0RP0RSP0/CPU0:router:hostname# show ipsla mpls lsp-monitor lpd statistics 10001

Group ID: 100001

Latest path discovery start time : 00:41:01.129 UTC Sat Dec 10 2005

Latest path discovery return code : OK

Latest path discovery completion time (ms): 3450

Completion Time Values:

CompTAvg: 3450 NumOfCompT: 1 CompTMin: 3450

Number of Paths Values:

CompTMax : 3450

NumOfPaths: 10 MinNumOfPaths: 10 MaxNumOfPaths: 10


Table 18: show ipsla mpls lsp-monitor lpd statistics Field Descriptions

Field

Group ID

Latest path discovery start time

Latest path discovery return code

Latest path discovery completion time

Completion Time Values

Number of Paths Values

Description

LPD group ID number.

LPD start time.

LPD return code.

LPD completion time.

Completion time values, consisting of Number of

Completion Time samples and Minimum Completion

Time.

Number of paths values, consisting of Minimum number of paths and Maximum number of paths.

250


OL-26517-02

IP Service Level Agreement Commands show ipsla mpls lsp-monitor scan-queue

show ipsla mpls lsp-monitor scan-queue

To display information about BGP next-hop addresses that are waiting to be added to or deleted from the

MPLS label switched path (LSP) monitor instance, use the show ipsla mpls lsp-monitor scan-queue command in EXEC modeXR EXEC mode.

show ipsla mpls lsp-monitor scan-queue [ monitor-id ]

Syntax Description monitor-id (Optional) Number of the IP SLA MPLS LSP monitor instance.



Command History

Release

Release 3.5.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification





Usage Guidelines If the monitor-id argument is not specified, the scan-queue is displayed for all MPLS LSP monitor instances.

Task ID

Task ID monitor

Operations read

Examples The following sample output is from the show ipsla mpls lsp-monitor scan-queue command:

RP/0/0RP0RSP0/CPU0:router:hostname# show ipsla mpls lsp-monitor scan-queue 1

IPSLA MPLS LSP Monitor : 1

Next scan Time after : 23 seconds

Next Delete scan Time after: 83 seconds

BGP Next hop Prefix Add/Delete?


251 OL-26517-02

IP Service Level Agreement Commands show ipsla mpls lsp-monitor scan-queue

192.255.0.2

192.255.0.3

192.255.0.2/32

192.255.0.5/32

Add

Delete


Table 19: show ipsla responder statistics port Field Descriptions

Field

IPSLA MPLS LSP Monitor

Next scan Time after

Next delete Time after

BGP next hop

Prefix

Add/Delete

Description

Monitor identifier.

Amount of time before the MPLS LSP monitor instance checks the scan queue for adding BGP next-hop neighbors. At the start of each scan time, IP

SLA operations are created for all newly discovered neighbors.

Amount of time left before the MPLS LSP monitor instance checks the scan queue for deleting BGP next-hop neighbors. At the start of each delete scan time, IP SLAs operations are deleted for neighbors that are no longer valid.

Identifier for the BGP next-hop neighbor.

IPv4 Forward Equivalence Class (FEC) of the BGP next-hop neighbor to be used.

Indicates that the specified BGP next-hop neighbor will be added or removed.

252


OL-26517-02

IP Service Level Agreement Commands show ipsla mpls lsp-monitor summary

show ipsla mpls lsp-monitor summary

To display the list of operations that have been created automatically by the specified MPLS LSP monitor

(MPLSLM) instance, use the show ipsla mpls lsp-monitor summary command in EXEC modeXR EXEC mode.

show ipsla mpls lsp-monitor summary [monitor-id [group [group id]]]

Syntax Description monitor-id

group group-id

(Optional) Displays a list of LSP group, ping, and trace operations created automatically by the specified MPLSLM instance.

(Optional) Displays the ECMP LSPs found through ECMP path discovery within the specified LSP group.



Command History

Release

Release 3.5.0

Release 3.5.0

Release 3.7.0

Release 3.7.2

Release 5.0.0

Modification



Show output response was expanded to add a pending status when waiting for an LSP ping or trace response.



Usage Guidelines The show ipsla mpls lsp-monitor summary command shows the list of LSP operations that were created automatically by the specified MPLS LSP monitor instance. It also shows the current status and the latest operation time of each operation.

If the monitor-id argument is not specified, the list of operations is displayed for all MPLS LSP monitor instances.

The show ipsla mpls lsp-monitor summary command with the group option shows the list of ECMP paths that are found automatically by the specified LSP path discovery (LPD). In addition, this command with option shows the current status; the number of successes, failures; the most recent round trip time (RTT); and the latest operation time of each path.


253 OL-26517-02


Task ID show ipsla mpls lsp-monitor summary

Examples

If the group-id argument is not specified, the list of paths is displayed for all operations created by the MPLS

LSP monitor instance.

Task ID monitor

Operations read

The following sample output is from the show ipsla mpls lsp-monitor summary command. This output shows a pending status when an MPLS LSP ping operation is waiting to receive the timeout response from the LSP Verification (LSPV) process.

RP/0/0RP0RSP0/CPU0:router:hostname# show ipsla mpls lsp-monitor summary 1

MonID Op/GrpID TargetAddress

1

1

1

100001

100002

100003

192.255.0.4/32

192.255.0.5/32

192.255.0.6/32

Status Latest Operation Time up down

19:33:37.915 EST Mon Feb 28 2005

19:33:47.915 EST Mon Feb 28 2005 pending 19:33:35.915 EST Mon Feb 28 2005

The following sample output shows that a down status is displayed after a timeout response is received.

RP/0/0RP0RSP0/CPU0:router:hostname# show ipsla mpls lsp-monitor summary 1

1

1

1

MonID Op/GrpID TargetAddress

1

1

100001

100002

193.100.0.1/32

193.100.0.2/32

100003

100004

100005

193.100.0.3/32

193.100.0.4/32

193.100.0.5/32

Status Latest Operation Time down 12:47:16.417 PST Tue Oct 23 2007 partial 12:47:22.418 PST Tue Oct 23 2007 partial 12:47:22.429 PST Tue Oct 23 2007 down 12:47:16.429 PST Tue Oct 23 2007 down 12:47:21.428 PST Tue Oct 23 2007


Table 20: show ipsla mpls lsp-monitor summary Field Descriptions

Field

MonID

Op/GrpID

TargetAddress

Status

Description

Monitor identifier.

Operation identifiers that have been created by this

MPLS LSP monitor instance.

IPv4 Forward Equivalence Class (FEC) to be used by this operation.

Status of the paths. Values can be as follows:

• up—Indicates that the latest operation cycle was successful.

• down—Indicates that the latest operation cycle was not successful.

• pending—Indicates that the latest operation cycle is waiting for an LSP ping or trace response.

254


OL-26517-02

IP Service Level Agreement Commands show ipsla mpls lsp-monitor summary

Field

Latest Operation Time

Description

Time the latest operation cycle was issued.

The following sample output is from the show ipsla mpls lsp-monitor summary group command:

RP/0/0RP0RSP0/CPU0:router:hostname# show ipsla mpls lsp-monitor summary 1 group 100001

GrpID LSP-Selector

100001 127.0.0.13

100001 127.0.0.15

100001 127.0.0.16

100001 127.0.0.26

Status Failure Success RTT Latest Operation Time up 0 retry 1

78

77

32

0

20:11:37.895 EST Feb 28 2005

20:11:37.995 EST Feb 28 2005 up up

0

0

78

78

32

32

20:11:38.067 EST Feb 28 2005

20:11:38.175 EST Feb 28 2005


Table 21: show ipsla mpls lsp-monitor summary group Field Descriptions

Field

GrpID

LSP-Selector

Status

Description

Group identifer that has been created by this MPLS

LSP monitor instance.

LSP selector address.

Status of the paths. Values can be as follows:

• up—Indicates that all the paths were successful.

• down—Indicates that all the paths were not successful.

• partial—Indicates that only some paths were successful.

• unknown—Indicates that some (or all) of the paths did not complete a single LSP echo request so the group status could not be identified.

Failure

Success

RTT

Latest Operation Time

Number of failures.

Number of successes.

Round Trip Time (RTT) in milliseconds of the latest

LSP echo request for the path.

Time the latest operation cycle was issued for the path.

OL-26517-02


255

IP Service Level Agreement Commands show ipsla responder statistics

show ipsla responder statistics

To display the number of probes that are received or handled by the currently active ports on the responder, use the show ipsla responder statistics ports command in EXEC modeXR EXEC mode.

show ipsla responder statistics {all| permanent} ports

Syntax Description all permanent

Port statistics is displayed for all ports.

Port statistics is displayed only for permanent ports.



Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





Usage Guidelines The output of the show ipsla responder statistics port command is available only for specific intervals of time in which only nonpermanent ports are being used at the responder. The reason is that the responder closes the nonpermanent ports after each operation cycle. However, if both permanent and nonpermanent ports are used, the output always contains rows for the permanent ports. The rows for the nonpermanent ports are displayed only if those nonpermanent ports are enabled at the instant the command is issued.

Task ID

Task ID monitor

Operations read

Examples The following sample output is from the show ipsla responder statistics port command:

256


OL-26517-02

IP Service Level Agreement Commands show ipsla responder statistics

RP/0/0RP0RSP0/CPU0:router:hostname# show ipsla responder statistics all port

Port Statistics

---------------

Local Address Port Port Type Probes Drops CtrlProbes Discard

172.16.5.1

3001 Permanent 0 0 0

172.16.5.1

172.16.5.5

172.16.5.1

10001 Permanent

8201 Dynamic

4441 Dynamic

728160

12132

207216

0

0

0

24272

12135

3641

ON

ON


Table 22: show ipsla responder statistics port Field Descriptions

Field

Local Address

Port

Port Type

Probes

Drops

CtrlProbes

Discard

Description

Local IP address of the responder device used to respond to IPSLA probes.

UDP socket local to the responder device used to respond to IPSLA probes.

It could be "permanent" or "dynamic"; depends upon whether a permanent port configuration is done.

Number of probe packets the responder has received.

Number of probes dropped.

Number of control packets the responder has received.

If the state is ON, the responder will not respond to probes.

OL-26517-02


257

IP Service Level Agreement Commands show ipsla statistics

show ipsla statistics

To display the operational data and the latest statistics for the IP SLA operation in tabular format, use the

show ipsla statistics command in EXEC modeXR EXEC mode.

show ipsla statistics [ operation-number ]

Syntax Description operation-number (Optional) Operation for which the latest statistics are to be displayed.

Range is 1 to 2048.



Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.6.0

Release 3.7.2

Release 5.2.3

Modification



Show output was expanded to include path information for LSP groups.




Task ID

Task ID monitor

Operations read

Examples The output of the show ipsla statistics command varies depending on the operation type.

The following sample output is from the show ipsla statistics command for an ICMP echo operation:

RP/0/0RP0RSP0/CPU0:router:hostname# show ipsla statistics 100025

Entry number: 100025

258


OL-26517-02


OL-26517-02

Modification time: 00:36:58.602 UTC Sat Dec 10 2007

Start time : 00:36:58.605 UTC Sat Dec 10 2007

Number of operations attempted: 5

Number of operations skipped : 0

Current seconds left in Life : Forever

Operational state of entry

Connection loss occurred

Timeout occurred

Latest RTT (milliseconds)

: Active

: FALSE

: FALSE

: 3

Latest operation start time : 00:41:01.129 UTC Sat Dec 10 2007

Latest operation return code : OK

RTT Values:

RTTAvg : 71

NumOfRTT: 1

Path Information:

Path Path LSP

Idx Sense Selector

1 1 127.0.0.13

RTTMin: 71

RTTSum: 71

Outgoing

Interface

PO0/2/5/0

RTTMax : 71

RTTSum2: 729

Nexthop

Address

192.12.1.2

Downstream

Label Stack

38

2

3

4

5

6

1

1

1

1

1

7

8

1

1

9 1

10 1

127.0.0.6

127.0.0.1

127.0.0.2

127.0.0.13

127.0.0.6

127.0.0.1

127.0.0.2

127.0.0.4

127.0.0.5

PO0/2/5/0

PO0/2/5/0

PO0/2/5/0

PO0/2/5/1

PO0/2/5/1

PO0/2/5/1

PO0/2/5/1

Gi0/2/0/0

Gi0/2/0/0

192.12.1.2

192.12.1.2

192.12.1.2

192.12.2.2

192.12.2.2

192.12.2.2

192.12.2.2

192.15.1.2

192.15.1.2

38

38

38

38

38

38

38

38

38

The following sample output is from the show ipsla statistics command for an UDP jitter operation:

RP/0/0RP0RSP0/CPU0:router:hostname# show ipsla statistics

Entry number: 101

Modification time: 16:39:36.608 GMT Fri Nov 28 2014

Start time : 16:39:36.633 GMT Fri Nov 28 2014

Number of operations attempted: 10

Number of operations skipped : 0

Current seconds left in Life : Forever

Operational state of entry : Active

Operational frequency(seconds): 60

Connection loss occurred : FALSE

Timeout occurred


: FALSE

: 3

Latest operation start time : 16:48:37.653 GMT Fri Nov 28 2014

Next operation start time : 16:49:37.653 GMT Fri Nov 28 2014

Latest operation return code : OK

RTT Values:

RTTAvg : 3

NumOfRTT: 10

Packet Loss Values:

RTTMin: 3

RTTSum: 33

RTTMax : 4

RTTSum2: 111

PacketLossSD

Errors

: 0

PacketOutOfSequence: 0

PacketLateArrival : 0

: 0

InvalidTimestamp : 0

PacketLossDS : 0

PacketMIA : 0

PacketSkipped: 0

Busies : 0

Jitter Values :

MinOfPositivesSD: 1

NumOfPositivesSD: 2

Sum2PositivesSD : 2

MaxOfPositivesSD: 1

SumOfPositivesSD: 2

MinOfNegativesSD: 1

NumOfNegativesSD: 1

Sum2NegativesSD : 1

MinOfPositivesDS: 1

NumOfPositivesDS: 1

MaxOfNegativesSD: 1

SumOfNegativesSD: 1

Sum2PositivesDS : 1

MinOfNegativesDS: 1

NumOfNegativesDS: 1

Sum2NegativesDS : 1

JitterAve: 1

MaxOfNegativesDS: 1

SumOfNegativesDS: 1

JitterSDAve: 1

Interarrival jitterout: 0

One Way Values :

JitterDSAve: 1

Interarrival jitterin: 0

NumOfOW: 0

OWMinSD : 0

MaxOfPositivesDS: 1

SumOfPositivesDS: 1

OWMaxSD: 0 OWSumSD: 0


259


OWSum2SD: 0

OWMinDS : 0

OWSum2DS: 0

OWAveSD: 0

OWMaxDS: 0

OWAveDS: 0

OWSumDS: 0


Table 23: show ipsla statistics Field Descriptions

Field

Entry number

Modification time

Start time

Number of operations attempted

Number of operations skipped

Current seconds left in Life

Operational state of entry

Connection loss occurred

Timeout occurred


Latest operation start time

Latest operation return code

RTTAvg

RTTMin

RTTMax

NumOfRTT

RTTSum

RTTSum2

Description

Entry number.

Latest time the operation was modified.

Time the operation was started.

Number of operation cycles that were issued.

Number of operation cycles that were not issued because one of the cycles extended over the configured time interval.

Time remaining until the operation stops execution.

State of the operation, such as active state, pending state, or inactive state.

Whether or not a connection-loss error happened.

Whether or not a timeout error happened.

Value of the latest RTT sample.

Time the latest operation cycle was issued.

Return code of the latest operation cycle

Average RTT value that is observed in the last cycle.

Minimum RTT value that is observed in the last cycle.

Maximum RTT value that is observed in the last cycle.

Number of successful round trips.

Sum of all successful round-trip values in milliseconds.

Sum of squares of the round-trip values in milliseconds.

260


OL-26517-02


Field

Path Idx

Path Sense

LSP Selector

Outgoing Interface

Nexthop Address

Downstream Label Stack

Description

Path index number.

Response return code for the path. (See

Table 15:

Response Return Values for the show ipsla history

Command, on page 244

, in show ipsla history command.)

LSP selector address of the path.

Outgoing interface of the path.

Next hop address of the path.

MPLS label stacks of the path.


Command


Description


OL-26517-02


261

IP Service Level Agreement Commands show ipsla statistics aggregated

show ipsla statistics aggregated

To display the hourly statistics for all the IP SLA operations or specified operation, use the show ipsla statistics

aggregated command in EXEC modeXR EXEC mode.

show ipsla statistics aggregated [detail] [ operation-number ]

Syntax Description detail operation-number

Displays detailed information.

(Optional) Number of IP SLA operations. Range is 1 to 2048.



Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.6.0

Release 3.7.2

Release 5.2.3

Modification



Show output was expanded to include detailed information when path discovery is enabled.



Usage Guidelines The show ipsla statistics aggregated command displays information such as the number of failed operations and the reason for failure. Unless you configured a different amount of time for the buckets command (statistics command with hourly keyword), the show ipsla statistics aggregated command displays the information collected over the past two hours.

For one-way delay and jitter operations to be computed for UDP jitter operations, the clocks on local and target devices must be synchronized using NTP or GPS systems. If the clocks are not synchronized, one-way measurements are discarded. If the sum of the source to destination (SD) and the destination to source (DS) values is not within 10 percent of the round-trip time, the one-way measurement values are assumed to be faulty, and are discarded.

262


OL-26517-02


Task ID

Examples

Task ID monitor

Operations read

The output of the show ipsla statistics aggregated command varies depending on operation type. The following sample output shows the aggregated statistics for UDP echo operation from the show ipsla statistics aggregated command:

RP/0/0RP0RSP0/CPU0:router:hostname# show ipsla statistics aggregated 1

Entry number: 1

Hour Index: 0

Start Time Index: 21:02:32.510 UTC Mon Dec 12 2005

Number of Failed Operations due to a Disconnect

Number of Failed Operations due to a Timeout

: 0

: 0

Number of Failed Operations due to a Busy : 0

Number of Failed Operations due to a No Connection : 0

Number of Failed Operations due to an Internal Error: 0

Number of Failed Operations due to a Sequence Error : 0

Number of Failed Operations due to a Verify Error : 0

RTT Values:

RTTAvg : 6

NumOfRTT: 36

RTTMin: 4

RTTSum: 229

RTTMax : 38

RTTSum2: 2563

The following sample output is from the show ipsla statistics aggregated command in which operation 10 is a UDP jitter operation:


Entry number: 10

Hour Index: 0

Start Time Index: 00:35:07.895 UTC Thu Mar 16 2006



Number of Failed Operations due to a Busy

: 0

: 0

: 0





RTT Values:

RTTAvg : 14

NumOfRTT: 70

RTTMin: 2

RTTSum: 1034

Packet Loss Values:

PacketLossSD : 0


RTTMax : 99

RTTSum2: 60610

PacketLossDS: 0

PacketMIA : 0


Errors

Jitter Values :

: 0

MinOfPositivesSD: 1

NumOfPositivesSD: 17

Sum2PositivesSD : 629

MinOfNegativesSD: 1

NumOfNegativesSD: 24

Sum2NegativesSD : 914

MinOfPositivesDS: 1

NumOfPositivesDS: 17

Sum2PositivesDS : 174

MinOfNegativesDS: 1

NumOfNegativesDS: 24

Sum2NegativesDS : 267


One Way Values :

Busies : 0

MaxOfPositivesSD: 19

SumOfPositivesSD: 65

MaxOfNegativesSD: 16

SumOfNegativesSD: 106

MaxOfPositivesDS: 7

SumOfPositivesDS: 44

MaxOfNegativesDS: 8

SumOfNegativesDS: 63


OL-26517-02


263


NumOfOW: 0

OWMinSD : 0

OWSum2SD: 0

OWMinDS : 0

OWMaxSD: 0

OWMaxDS: 0

OWSumSD: 0

OWSumDS: 0

RP/0/0RP0RSP0/CPU0:router:hostname# show ipsla statistics aggregated

Captured Statistics

Each Entry per Line

Column Description per Entry:

Entry = Entry number

StartT = Start time of entry (hundredths of seconds)

Pth

Hop

Dst

= Path index

= Hop in path index

= Time distribution index

Comps = Operations completed

SumCmp = Sum of RTT (milliseconds)

SumCmp2H = Sum of RTT squared high 32 bits (milliseconds)

SumCmp2L = Sum of RTT squared low 32 bits (milliseconds)

TMax

TMin

= RTT maximum (milliseconds)

= RTT minimum (milliseconds)

Entry StartT

TMin

Pth Hop Dst Comps

101 1417192777884 1 1 0 0

0

101 1417192777884 1 1 1 0

0

101 1417192777884 1 1 2 2

1

101 1417192777884 1 1 3 8

2

101 1417192777884 1 1 4 0

0

SumCmp

0

0

58

258

0

0

0

0

0

0

SumCmp2H

0

SumCmp2L

0

176

852

0

0

4

5

0

0

TMax


Table 24: show ipsla statistics aggregated Field Descriptions

Field

Busies

Entry Number

Hop in Path Index

Errors

Jitter Values

NumOfJitterSamples



Description

Number of times that the operation cannot be started because the previously scheduled run was not finished.

Entry number.

Hop in path index.

Number of internal errors.

Jitter statistics appear on the specified lines. Jitter is defined as interpacket delay variance.

Number of jitter samples that are collected. The number of samples are used to calculate the jitter statistics.

Number of failed operations due to a disconnect.

Number of failed operations due to a timeout.

264


OL-26517-02


Field


Description

Number of failed operations due to a busy error.

Number of Failed Operations due to a No Connection Error that refers to the case in which the control connection cannot be established.

Number of Failed Operations due to an Internal Error Number of failed operations due to an internal error.

Number of Failed Operations due to a Sequence Error Number of failed operations due to a sequence error.

Number of Failed Operations due to a Verify Error Number of failed operations due to a verify error.

MaxOfNegativesSD

MaxOfPositivesSD

MaxOfPositivesDS

MaxOfNegativesDS

Maximum negative jitter values from the source to the destination. The absolute value is given.

Maximum jitter values from the source to the destination in milliseconds.

Maximum jitter values from the destination to the source in milliseconds.

Maximum negative jitter values from destination-to-source. The absolute value is given.

MinOfPositivesDS

MinOfNegativesSD

MinOfPositivesSD

MinOfNegativesDS

NumOfOW

NumOfNegativesDS

NumOfNegativesSD

NumOfPositivesDS

Minimum jitter values from the destination to the source in milliseconds.

Minimum negative jitter values from the source to the destination. The absolute value is given.

Minimum jitter values from the source to the destination in milliseconds.

Minimum negative jitter values from the destination to the source. The absolute value is given.

Number of successful one-way time measurements.

Number of jitter values from the destination to the source that are negative; for example, network latency decreases for two consecutive test packets.

Number of jitter values from the source to the destination that are negative; for example, network latency decreases for two consecutive test packets.

Number of jitter values from the destination to the source that are positive; for example, network latency increases for two consecutive test packets.

OL-26517-02


265

show ipsla statistics aggregated

Field

NumOfPositivesSD

NumOfRTT

One Way Values

OWMaxDS

OWMaxSD

OWMinDS

OWMinSD

OWSumDS

OWSumSD

OWSum2DS

OWSum2SD

PacketLateArrival

PacketLossDS

PacketLossSD

PacketMIA

PacketOutOfSequence

Path Index

Port Number

266



Description

Number of jitter values from the source to the destination that are positive; for example, network latency increases for two consecutive test packets.


One-way measurement statistics appear on the specified lines. One Way (OW) values are the amount of time that it took the packet to travel from the source router to the target router or from the target router to the source router.

Maximum time from the destination to the source.

Maximum time from the source to the destination.

Minimum time from the destination to the source.

Minimum time from the source to the destination.

Sum of one-way delay values from the destination to the source.

Sum of one-way delay values from the source to the destination.

Sum of squares of one-way delay values from the destination to the source.

Sum of squares of one-way delay values from the source to the destination.

Number of packets that arrived after the timeout.

Number of packets lost from the destination to the source (DS).

Number of packets lost from the source to the destination (SD).

Number of packets lost in which the SD direction or

DS direction cannot be determined.

Number of packets that are returned out of order.

Path index.

Target port number.

OL-26517-02


OL-26517-02

SumOfPositivesDS

SumOfPositivesSD

SumOfNegativesDS

SumOfNegativesSD

Sum2PositivesDS

Sum2PositivesSD

Sum2NegativesDS

Sum2NegativesSD

Target Address

Field

RTTSum

RTTSum2

RTT Values

Start Time

Start Time Index

Description

Sum of all successful round-trip values in milliseconds.

Sum of squares of the round-trip values in milliseconds.

Round-trip time statistics appear on the specified lines.

Start time, in milliseconds.

Statistics that are aggregated for over 1-hour intervals.

The value indicates the start time for the 1-hour interval that is displayed.

Sum of the positive jitter values from the destination to the source.

Sum of the positive jitter values from the source to the destination.

Sum of the negative jitter values from the destination to the source.

Sum of the negative jitter values from the source to the destination.

Sum of squares of the positive jitter values from the destination to the source.

Sum of squares of the positive jitter values from the source to the destination.

Sum of squares of the negative jitter values from the destination to the source.

Sum of squares of the negative jitter values from the source to the destination.

Target IP address.

The output of the show ipsla statistics aggregated detail command varies depending on operation type. The following sample output is from the show ipsla statistics aggregated detail command in tabular format, when the output is split over multiple lines:

RP/0/0RP0RSP0/CPU0:router:hostname# show ipsla statistics aggregated detail 2

Captured Statistics

Multiple Lines per Entry


267


Field

Entry

StartT

Pth

Hop

Dst

Comps

SumCmp

SumCmp2L

Line1:

Entry = Entry number

StartT = Start time of entry (hundredths of seconds)

Pth = Path index

Hop = Hop in path index

Dst

Comps

= Time distribution index

= Operations completed

SumCmp = Sum of RTT (milliseconds)

Line2:

SumCmp2H = Sum of RTT squared high 32 bits (milliseconds)

SumCmp2L = Sum of RTT squared low 32 bits (milliseconds)

TMax

TMin

= RTT maximum (milliseconds)

= RTT minimum (milliseconds)

Entry StartT

2

Pth Hop Dst Comps

SumCmp2H SumCmp2L TMax

1134423910701 1 1 0 12

2

0 1231 6

1134423851116 1 1 1 2

2

2

0 2419 41

1134423070733 1 1 2 1

0 1119 16

0

0

1 1 3 0

0 0

SumCmp

TMin

367

6

129

41

101

16

0

0


Table 25: show ipsla statistics aggregated detail Field Descriptions

SumCmp2H

TMax

TMin

Description

Entry number.

Start time of entry, in hundredths of seconds.

Path index.

Hop in path index.

Time distribution index.

Operations completed.

Sum of completion times, in milliseconds.

Sum of completion times squared low 32 bits, in milliseconds.

Sum of completion times squared high 32 bits, in milliseconds.

Completion time maximum, in milliseconds.

Completion time minimum, in milliseconds.

268


OL-26517-02


The following sample output is from the show ipsla statistics aggregated command when a path discovery operation is enabled. Data following the hourly index is aggregated for all paths in the group during the given hourly interval.


Entry number: 100041

Hour Index: 13

<The following data after the given hourly index is aggregated for all paths in the group during the given hourly interval.>

Start Time Index: 12:20:57.323 UTC Tue Nov 27 2007



: 0

: 249






<end>

RTT Values:

RTTAvg : 21

NumOfRTT: 2780

RTTMin: 19

RTTSum: 59191

RTTMax : 73

RTTSum2: 1290993

<The following data for LSP path information is available after path discovery is enabled.>

Path Information:

Path Path LSP

Idx Sense Selector

1

2

3

1

1

1

127.0.0.1

127.0.0.1

127.0.0.1

Outgoing

Interface

Gi0/4/0/0

Gi0/4/0/0.1

Gi0/4/0/0.2

Nexthop

Address

192.39.1.1

192.39.2.1

192.39.3.1

4

5

6

7

1

1

1

1

127.0.0.1

127.0.0.8

127.0.0.8

127.0.0.8

127.0.0.8

Gi0/4/0/0.3

Gi0/4/0/0

Gi0/4/0/0.1

Gi0/4/0/0.2

Gi0/4/0/0.3

192.39.4.1

192.39.1.1

192.39.2.1

192.39.3.1

192.39.4.1

8 1

<end>

Hour Index: 14

Start Time Index: 13:20:57.323 UTC Tue Nov 27 2007




: 0

: 122

: 0





RTT Values:

RTTAvg : 21

NumOfRTT: 3059

RTTMin: 19

RTTSum: 65272

RTTMax : 212

RTTSum2: 1457612

Path Information:

Path Path LSP

Idx Sense Selector

1 1 127.0.0.1

2

3

4

1

1

1

127.0.0.1

127.0.0.1

127.0.0.1

5

6

7

8

1

1

1

1

127.0.0.8

127.0.0.8

127.0.0.8

127.0.0.8

Outgoing

Interface

Gi0/4/0/0

Gi0/4/0/0.1

Gi0/4/0/0.2

Gi0/4/0/0.3

Gi0/4/0/0

Gi0/4/0/0.1

Gi0/4/0/0.2

Gi0/4/0/0.3

Nexthop

Address

192.39.1.1

192.39.2.1

192.39.3.1

192.39.4.1

192.39.1.1

192.39.2.1

192.39.3.1

192.39.4.1


Downstream

Label Stack

677

677

677

677

677

677

677

677

Downstream

Label Stack

677

677

677

677

677

677

677

677

OL-26517-02


269


Table 26: show ipsla statistics aggregated (with Path Discovery enabled) Field Descriptions

Field

Entry Number

Start Time Index

Description

Entry number.

Start time.





Number of Failed Operations due to a Busy Number of failed operations due to a busy error.





RTT Values

RTT Min/Avg/Max

NumOfRTT

RTT Sum

RTT Sum2


Maximum values of the RTT that are observed in the latest cycle (*).


Sum of all successful round-trip values, in milliseconds.

Sum of squares of the round-trip values, in milliseconds.

RTT Min/Avg/Max

NumOfRTT

Path Idx

Path Sense

LSP Selector



Path index number.

Response return code for the path. (See

Table 15:

Response Return Values for the show ipsla history

Command, on page 244

, in show ipsla history command.)

LSP selector address of the path.

270


OL-26517-02


Field

Outgoing Interface

Nexthop Address

Downstream Label Stack

Description

Outgoing interface name of the path.

Next hop address of the path.

MPLS label stacks of the path.


Command

show ipsla statistics, on page 258

Description

Displays the operational data for the IP SLA operation.

show ipsla statistics enhanced aggregated, on page

272


OL-26517-02


271

IP Service Level Agreement Commands show ipsla statistics enhanced aggregated

show ipsla statistics enhanced aggregated

To display the enhanced history statistics for all collected enhanced history buckets for the specified IP SLA operation, use the show ipsla statistics enhanced aggregated command in EXEC modeXR EXEC mode.

show ipsla statistics enhanced aggregated [ operation-number ] [interval seconds]

Syntax Description operation-number

interval seconds

(Optional) Operation number for which to display the enhanced history distribution statistics.

(Optional) Specifies the aggregation interval in seconds for which to display the enhanced history distribution statistics.



Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





Usage Guidelines The show ipsla statistics enhanced aggregated command displays data for each bucket of enhanced history data shown individually; for example, one after the other. The number of buckets and the collection interval is set using the interval keyword, seconds argument, buckets keyword, and number-of-buckets argument.

Task ID

Task ID monitor

Operations read

Examples The output of the show ipsla statistics enhanced aggregated command varies depending on the operation type.

272


OL-26517-02


The following sample output is from the show ipsla statistics enhanced aggregated command for the UDP echo operation:

RP/0/0RP0RSP0/CPU0:router:hostname# show ipsla statistics enhanced aggregated 20

Entry number: 20

Interval : 300 seconds

Bucket : 1 (0 - 300 seconds)




: 0

: 0






RTT Values:

RTTAvg : 2

NumOfRTT: 5

RTTMin: 2

RTTSum: 13

Bucket : 2 (300 - 600 seconds)

RTTMax : 5

RTTSum2: 41





: 0

: 0

: 0





RTT Values:

RTTAvg : 2

NumOfRTT: 1

RTTMin: 2

RTTSum: 2

RTTMax : 2

RTTSum2: 4

The following sample output is from the show ipsla statistics enhanced aggregated command for the UDP jitter operation:

RP/0/0RP0RSP0/CPU0:router:hostname# show ipsla statistics enhanced aggregated 20

Entry number: 101

Interval : 120 seconds

Bucket : 1

Start Time Index: 16:39:37.884 GMT Fri Nov 28 2014



: 0

: 0






RTT Values:

RTTAvg : 3

NumOfRTT: 20

Packet Loss Values:

RTTMin: 1

RTTSum: 63

RTTMax : 5

RTTSum2: 213

PacketLossSD : 0



Errors : 0

InvalidTimestamp : 0

Jitter Values :

MinOfPositivesSD: 1

PacketLossDS : 0

PacketMIA : 0

PacketSkipped: 0

Busies : 0

MaxOfPositivesSD: 2

SumOfPositivesSD: 9 NumOfPositivesSD: 7

Sum2PositivesSD : 13

MinOfNegativesSD: 1

NumOfNegativesSD: 7

MaxOfNegativesSD: 1

SumOfNegativesSD: 7

Sum2NegativesSD : 7

MinOfPositivesDS: 1

NumOfPositivesDS: 2

Sum2PositivesDS : 2

MinOfNegativesDS: 1

NumOfNegativesDS: 2

Sum2NegativesDS : 2

JitterAve: 1

MaxOfPositivesDS: 1

SumOfPositivesDS: 2

MaxOfNegativesDS: 1

SumOfNegativesDS: 2

JitterSDAve: 1 JitterDSAve: 1

OL-26517-02


273



One Way Values :


NumOfOW: 0

OWMinSD : 0

OWSum2SD: 0

OWMinDS : 0

OWSum2DS: 0

OWMaxSD: 0

OWAveSD: 0

OWMaxDS: 0

OWAveDS: 0

OWSumSD: 0

OWSumDS: 0

Bucket : 2

Start Time Index: 16:41:36.657 GMT Fri Nov 28 2014




: 0

: 0

: 0





RTT Values:

RTTAvg : 3

NumOfRTT: 20

RTTMin: 2

RTTSum: 61

RTTMax : 4

RTTSum2: 189

...


Table 27: show ipsla statistics enhanced aggregated Field Descriptions

Field

Entry Number

Interval

Bucket

Start Time Index

RTT Values

RTT Min/Avg/Max

NumOfRTT

RTT Sum

RTT Sum2

Description

Entry number.

Multiple of the frequency of the operation. The

Enhanced interval field defines the interval in which statistics displayed by the show ipsla statistics

enhanced aggregated command are aggregated. This field must be configured so that the enhanced aggregated statistics are displayed.

Bucket index.

Statistics that are aggregated depend on the interval configuration mode. The value depends on the interval configuration that is displayed.




Sum of all successful round-trip values, in milliseconds.

Sum of squares of the round-trip values, in milliseconds.

274


OL-26517-02


Field



Description



Number of Failed Operations due to a Busy Number of failed operations due to a busy error.






Command



Description

Displays the operational data for the IP SLA operation.


OL-26517-02


275

IP Service Level Agreement Commands show ipsla twamp connection

show ipsla twamp connection

To display the Two-Way Active Management Protocol (TWAMP) connections, use the show ipsla twamp

conection command in the EXEC modeXR EXEC mode.

show ipsla twamp connection[ detailsource-ip | requests]


detail source-ip requests

Displays details of the connection for a specified source-ip.

Displays request details.



Command History

Release

Release 5.1.1

Modification



Task ID

Task ID ip-services

Operation read

Examples This example shows how to run the show ipsla twamp conection command with the requests keyword:

RP/0/0RP0RSP0/CPU0:router:hostname # show ipsla twamp connection requests

276


OL-26517-02

IP Service Level Agreement Commands show ipsla twamp session

show ipsla twamp session

To display the Two-way Active Management Protocol (TWAMP) sessions, use the show ipsla twamp session command in the EXEC modeXR EXEC mode.

show ipsla twamp session [ source-ip host-name ]


source-ip host-name Displays session information for the specified source-ip and hostname.



Command History

Release

Release 5.1.1

Modification



Task ID

Task ID monitor

Operation read

Examples This example shows how to run show ipsla twamp session command:

RP/0/0RP0RSP0/CPU0:router:hostname # show ipsla twamp session

OL-26517-02


277

IP Service Level Agreement Commands show ipsla twamp standards

show ipsla twamp standards

To display the Two-way Active Management Protocol (TWAMP) standards, use the show ipsla twamp

standards command in the EXEC modeXR EXEC mode.

The relevant RFC standards for the TWAMP server and TWAMP reflector are indicated.

show ipsla twamp standards




Command History

Release

Release 5.1.1

Modification



Task ID

Task ID ip-services

Operation read

Examples This example shows how to use the show ipsla twamp standards command:

RP/0/0RP0RSP0/CPU0:router:hostname # show ipsla twamp standards

Feature Organization Standard

TWAMP Server

TWAMP Reflector

IETF

IETF

RFC5357

RFC5357

278


OL-26517-02

IP Service Level Agreement Commands source address

source address

To identify the address of the source device, use the source address command in the appropriate configuration mode. To use the best local address, use the no form of this command.

source address ipv4-address no source address

Syntax Description ipv4-address IP address or hostname of the source device.

Command Default IP SLA finds the best local address to the destination and uses it as the source address.








Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.4.0

Release 3.7.2

Release 5.2.3

Modification



Support was added for IP SLA MPLS LSP Ping and IP SLA MPLS

LSP Trace configuration modes.





279 OL-26517-02

IP Service Level Agreement Commands source address

Task ID

Task ID monitor


Examples The following example shows how to designate an IP address for the source address command in IP SLA

UDP jitter configuration mode:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-jitter)# source address 192.0.2.9


Command



Description



280


OL-26517-02

IP Service Level Agreement Commands source port

source port

To identify the port of the source device, use the source port command in the appropriate configuration mode.

To use the unused port number, use the no form of this command.

source port port no source port


port port Identifies the port number of the source device. Range is 1 to 65535.

Command Default IP SLA uses an unused port that is allocated by system.

Command History

Releas

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





Usage Guidelines The source port command is not supported to configure ICMP operations; it is supported only to configure

UDP operations.

The specified source port should not be used in other IPSLA operations configured on the same source IP address and source VRF.

Task ID

Task ID monitor


Examples The following example shows how to designate a port for the source port command in IP SLA UDP jitter configuration mode:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-jitter)# source port 11111


281 OL-26517-02

IP Service Level Agreement Commands source port


Command



Description



282


OL-26517-02

IP Service Level Agreement Commands start-time

start-time

To determine the time when the operation or MPLS LSP monitor instance starts, use the start-time command in the appropriate configuration mode. To stop the operation and place it in the default state, use the no form of this command.

start-time {hh:mm:ss [day| month day year]| after hh:mm:ss| now| pending} no start-time

Syntax Description hh:mm:ss month day year

after hh:mm:ss now pending

Absolute start time in hours, minutes, and seconds. You can use the 24-hour clock notation. For example, the start-time 01:02 is defined as 1:02 am, or start-time

13:01:30 is defined as start at 1:01 pm. and 30 seconds. The current day is used; unless, you specify a month and day.

(Optional) Name of the month to start the operation. When you use the month argument, you are required to specify a day. You can specify the month by using the full English name or the first three letters of the month.

(Optional) Number of the day, in the range of 1 to 31, to start the operation. In addition, you must specify a month.

(Optional) Year in the range of 1993 to 2035.

Specifies that the operation starts at hh hours, mm minutes, and ss seconds after the

start-time command is used.

Specifies that the operation should start immediately.

Specifies that no information is collected. The default value is the pending keyword.

Command Default If a month and day are not specified, the current month and day are used.


IP SLA MPLS LSP monitor schedule configuration

Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.5.0

Modification



This command was added to IP SLA MPLS LSP monitor schedule configuration mode.


283 OL-26517-02

IP Service Level Agreement Commands start-time

Release

Release 3.7.0

Release 3.7.2

Release 5.2.3

Modification

Added the ability to specify a year.



Usage Guidelines If the start-time command is used in IP SLA operation mode, it configures the start time for the specific operation being configured. If the start-time command is used in IP SLA MPLS LSP monitor mode, it configures the start time for all monitor instances associated with the monitored provider edge (PE) routers.

Task ID

Task ID monitor


Examples The following example shows how to use the start-time command option for the schedule operation:




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-sched)# start-time after 01:00:00

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





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-sched)# start-time after 01:00:00

The following example shows how to use the start-time command and specify a year for a scheduled operation:


RP/0/0RP0RSP0/CPU0:router:hostname(config)# ipsla operation 2

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op)# type icmp echo

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-icmp-echo)# destination address 192.0.2.9

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-icmp-echo)# exit

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op)# exit


RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-sched)# start 20:0:0 february 7 2008

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-sched)#


Command

life, on page 169


Description

Specifies the length of time to execute.


284


OL-26517-02


Command

recurring, on page 221



start-time

Description

Indicates that the operation starts automatically at the specified time and for the specified duration every day.

Schedules an IP SLA MPLS LSP monitoring instance.


OL-26517-02


285

IP Service Level Agreement Commands statistics

statistics

To set the statistics collection parameters for the operation, use the statistics command in the appropriate configuration mode. To remove the statistics collection or use the default value, use the no form of this command.

statistics {hourly| interval seconds}

no statistics {hourly| interval seconds}

Syntax Description hourly

interval seconds

Sets the distribution for statistics configuration that is aggregated for over an hour.

Collects statistics over a specified time interval. Interval (in seconds) over which to collect statistics. Range is 1 to 3600 seconds.


Command Modes IP SLA operation UDP jitter configuration





Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.5.0

Release 3.7.2

Release 5.2.3

Modification






Usage Guidelines The statistics interval command is not supported for the configuration of ICMP path-echo and ICMP path-jitter operations, nor for the configuration of MPLS LSP monitor instances.

286


OL-26517-02

IP Service Level Agreement Commands statistics

Task ID

If the statistics command is used in IP SLA operation mode, it configures the statistics collection for the specific operation being configured. If the statistics command is used in IP SLA MPLS LSP monitor mode, it configures the statistics collection 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 monitor


Examples The following example shows how to set the number of hours in which statistics are maintained for the IP

SLA UDP jitter operation for the statistics command:






RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op-stats)#

The following example shows how to collect statistics for a specified time interval, using the statistics command in an IP SLA UDP jitter operation:


RP/0/0RP0RSP0/CPU0:router:hostname(config)# ipsla operation 1


RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-jitter)# statistics interval 60

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op-stats)#

The following example shows how to set the number of hours in which statistics are maintained for the IP

SLA MPLS LSP monitor ping operation, using the statistics command:






RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lsp-ping)# statistics hourly

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-stats)#


Command


buckets (statistics interval), on page 138



Description


Refers to the data buckets in which the enhanced history statistics are kept.



OL-26517-02


287

statistics


Command







Description







288


OL-26517-02

IP Service Level Agreement Commands tag (IP SLA)

tag (IP SLA)

To create a user-specified identifier for an IP SLA operation, use the tag command in the appropriate configuration mode. To unset the tag string, use the no form of this command.

tag [ text ] no tag

Syntax Description text (Optional) Specifies a string label for the IP SLA operation.

Command Default No tag string is configured.










Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.4.0

Release 3.5.0

Release 3.7.2

Release 5.2.3

Modification









289 OL-26517-02

IP Service Level Agreement Commands tag (IP SLA)

Usage Guidelines If the tag command is used in IP SLA operation mode, it configures the user-defined tag string for the specific operation being configured. If the tag command is used in IP SLA MPLS LSP monitor mode, it configures the user-defined tag string 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 monitor


Examples The following example shows how to use the tag command in IP SLA UDP jitter configuration mode:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-jitter)# tag ipsla

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





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lsp-ping)# tag mplslm-tag


Command



Description



290


OL-26517-02

IP Service Level Agreement Commands target ipv4

target ipv4

To specify the IPv4 address of the target router to be used in an MPLS LSP ping or MPLS LSP trace operation, use the target ipv4 command in the appropriate configuration mode. To unset the address, use the no form of this command.

target ipv4 destination-address destination-mask no target ipv4

Syntax Description destination-address IPv4 address of the target device to be tested.

destination-mask Number of bits in the network mask of the target address. The network mask can be specified in either of two ways:

• The network mask can be a four-part dotted decimal address. For example,

255.0.0.0 indicates that each bit equal to 1 means the corresponding address bit belongs to the network address.

• The network mask can be indicated as a slash (/) and number. For example, /8 indicates that the first 8 bits of the mask are ones, and the corresponding bits of the address are network address.




Command History

Release

Release 3.4.0

Release 3.4.0

Release 3.7.2

Release 5.0.0

Modification





Usage Guidelines Use the target ipv4 command to specify the IPv4 address of the target router at the end of the LSP to be tested or traced and to indicate the destination as an Label Distribution Protocol (LDP) IPv4 address. The target

IPv4 address identifies the appropriate label stack associated with the LSP.


291 OL-26517-02

IP Service Level Agreement Commands target ipv4

Task ID

Note Using the target ipv4 command, you can configure only one LDP IPv4 address as the target in an MPLS

LSP ping or trace operation. If you enter the command a second time and configure a different IPv4 target address, you overwrite the first IPv4 address.

An MPLS LSP ping operation tests connectivity in the LSP using verification on the specified Forwarding

Equivalence Class (FEC)— in this case, LDP IPv4 prefix—between the ping origin and the egress node identified with the target ipv4 command. This test is carried out by sending an MPLS echo request along the same data path as other packets belonging to the FEC. When the ping packet reaches the end of the path, it is sent to the control plane of the egress label switching router (LSR), which then verifies that it is indeed an egress for the LSP. The MPLS echo request contains information about the LSP that is being verified.

In an MPLS network, an MPLS LSP trace operation traces LSP paths to the target router identified with the

target ipv4 command. In the verification of LSP routes, a packet is sent to the control plane of each transit

LSR, which performs various checks, including one that determines if it is a transit LSR for the LSP path.

Each transit LSR also returns information related to the LSP being tested (that is, the label bound to the LDP

IPv4 prefix).

Task ID monitor


Examples The following example shows how to use the target ipv4 command:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mpls-lsp-ping)# target ipv4 192.168.1.4

255.255.255.255


Command





Description





MPLS VPN.

292


OL-26517-02

IP Service Level Agreement Commands target pseudowire

target pseudowire

To specify the pseudowire as the target to be used in an MPLS LSP ping operation, use the target pseudowire command in IP SLA MPLS LSP ping configuration mode. To unset the target, use the no form of this command.

target pseudowire destination-address circuit-id no target pseudowire

Syntax Description destination-address circuit-id

IPv4 address of the target device to be tested.

Virtual circuit identifier. Range is 1 to 4294967295.



Command History

Release

Release 3.5.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification





Usage Guidelines Use the target pseudowire command to specify a target router and to indicate the destination as a Layer 2

VPN pseudowire in an MPLS LSP ping operation. The target pseudowire command identifies the target address and the virtual circuit (VC) identifier.

Note Using the target pseudowire command, you can configure only one pseudowire address as the target in an MPLS LSP ping operation. If you use the command a second time and configure a different pseudowire target address, the first pseudowire address is overwritten.

A pseudowire target of the LSP ping operation allows active monitoring of statistics on Pseudowire

Edge-to-Edge (PWE3) services across an MPLS network. PWE3 connectivity verification uses the Virtual

Circuit Connectivity Verification (VCCV).

For more information on VCCV, refer to the VCCV draft, “Pseudowire Virtual Circuit Connectivity Verification

(VCCV)” on the IETF web page.


293 OL-26517-02

IP Service Level Agreement Commands target pseudowire

Task ID

Task ID monitor


Examples The following example shows how to use the target pseudowire command:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mpls-lsp-trace)# target pseudowire 192.168.1.4

4211


Command




Description




294


OL-26517-02

IP Service Level Agreement Commands target traffic-eng

target traffic-eng

To specify the target MPLS traffic engineering tunnel to be used in an MPLS LSP ping or MPLS LSP trace operation, use the target traffic-eng command in the appropriate configuration mode. To unset the tunnel, use the no form of this command.

target traffic-eng tunnel tunnel-interface no target traffic-eng


tunnel tunnel-interface Tunnel ID of an MPLS traffic-engineering tunnel (for example, tunnel

10) configured on the router. Range is 0 to 65535.




Command History

Release

Release 3.4.0

Release 3.4.0

Release 3.7.2

Release 5.0.0

Modification





Usage Guidelines Use the target traffic-eng command to specify a target router and to indicate the destination as an MPLS traffic-engineering (TE) tunnel in an MPLS LSP ping or MPLS LSP trace operation. The target traffic-eng command identifies the tunnel interface and the appropriate label stack associated with the LSP to be pinged or traced. An LSP tunnel interface is the head-end of a unidirectional virtual link to a tunnel destination.

Note Using the target traffic-eng command, you can configure only one MPLS TE tunnel as the target in an

MPLS LSP ping or trace operation. If you enter the command a second time and configure a different tunnel interfaces, you overwrite the first tunnel ID.

An IP SLA ping operation tests connectivity in the LSP using verification on the specified Forwarding

Equivalence Class (FEC)—in this case, MPLS TE tunnel—between the ping origin and the egress node identified with the target traffic-eng command. This test is carried out by sending an MPLS echo request


295 OL-26517-02

IP Service Level Agreement Commands target traffic-eng

Task ID along the same data path as other packets belonging to the tunnel. When the ping packet reaches the end of the path, it is sent to the control plane of the egress label switching router (LSR), which then verifies that it is indeed an egress for the MPLS TE tunnel. The MPLS echo request contains information about the tunnel whose LSP path is being verified.

In an MPLS network, an IP SLA trace operation traces the LSP paths to a target router identified with the

target traffic-eng command. In the verification of LSP routes, a packet is sent to the control plane of each transit LSR, which performs various checks, including one that determines if it is a transit LSR for the LSP path. Each transit LSR also returns information related to the MPLS TE tunnel to see if the local forwarding information matches what the routing protocols determine as the LSP path.

MPLS traffic engineering automatically establishes and maintains LSPs across the backbone. The path that an LSP uses is determined by the LSP resource requirements and network resources, such as bandwidth.

For more information on MPLS traffic-engineering tunnels, refer to MPLS Traffic Engineering and

Enhancements.

Task ID monitor


Examples The following example shows how to use the target traffic-eng tunnel command:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mpls-lsp-trace)# target traffic-eng tunnel

101


Command





Description





MPLS VPN.

296


OL-26517-02

IP Service Level Agreement Commands threshold

threshold

To set the lower-limit and upper-limit values, use the threshold command in IP SLA reaction condition configuration mode. To use the default value, use the no form of this command.

threshold lower-limit value upper-limit value

no threshold lower-limit value upper-limit value


lower-limit value

upper-limit value

Specifies the threshold lower-limit value. Range is 1 to 4294967295 ms.

Default lower-limit value is 3000 ms.

Specifies the threshold upper-limit value. Range is 5000 to 4294967295 ms.

Default upper-limit value is 5000 ms.

Command Default lower-limit value: 3000 ms

upper-limit value: 5000 ms


Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





Usage Guidelines The threshold command is supported only when used with the react command and jitter-average and

packet-loss keywords.

Task ID

Task ID monitor



297 OL-26517-02

IP Service Level Agreement Commands threshold

Examples The following example shows how to set the lower-limit and upper-limit values for the react command with the jitter-average keyword for the threshold command:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-react-cond)# threshold lower-limit 8000 upper-limit 10000

The following example shows how to set the lower-limit and upper-limit values for the react command with the packet-loss keyword for the threshold command:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-react-cond)# threshold lower-limit 8000 upper-limit 10000


Command




react, on page 208





Description









298


OL-26517-02

IP Service Level Agreement Commands threshold type average

threshold type average

To take action on average values to violate a threshold, use the threshold type average command in IP SLA reaction condition configuration mode. To clear the threshold type (reaction will never happen), use the no form of this command.

threshold type average number-of-probes no threshold type

Syntax Description number-of-probes When the average of the last five values for the monitored element exceeds the upper threshold or the average of the last five values for the monitored element drops below the lower threshold, the action is performed as defined by the action command. Range is 1 to 16.

Command Default If there is no default value, no threshold type is configured.


Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





Usage Guidelines The threshold type average command is supported only when used with the react command and

jitter-average, packet-loss, and rtt keywords.

Task ID

Task ID monitor


OL-26517-02


299

IP Service Level Agreement Commands threshold type average

Examples The following example shows how to set the number of probes for the react command with the jitter-average keyword for the threshold type average command:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-react-cond)# threshold type average 8

The following example shows how to set the number of probes for the react command with the packet-loss keyword for the threshold type average command:


RP/0/0RP0RSP0/CPU0:router:hostname(config)# ipsla reaction operation 432


RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-react-cond)# threshold type average 8


Command





react, on page 208





Description

Specifies what action or combination of actions the operation performs.









300


OL-26517-02

IP Service Level Agreement Commands threshold type consecutive

threshold type consecutive

To take action after a number of consecutive violations, use the threshold type consecutive command in the appropriate configuration mode. To clear the threshold type (reaction will never happen), use the no form of this command.

threshold type consecutive occurrences no threshold type

Syntax Description occurrences When the reaction condition is set for a consecutive number of occurrences, there is no default value. The number of occurrences is set when specifying the threshold type.

The number of consecutive violations is 1 to 16.



IP SLA MPLS LSP monitor reaction condition configuration

Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.5.0

Release 3.7.2

Release 5.2.3

Modification



This command was added to IP SLA MPLS LSP monitor reaction condition configuration mode.



Usage Guidelines If the threshold type consecutive command is used in IP SLA reaction condition mode, it configures the threshold for the specific operation being configured. If the threshold type consecutive command is used in

IP SLA MPLS LSP monitor reaction condition configuration mode, it configures the threshold 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 monitor



301 OL-26517-02

IP Service Level Agreement Commands threshold type consecutive

Examples The following example shows how to use the threshold type consecutive command:



RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla )# reaction operation 432


RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-react-cond)# threshold type consecutive 8

The following example shows how to use the threshold type consecutive command in IP SLA MPLS LSP monitor reaction condition configuration mode:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-react-cond)# threshold type consecutive

2


Command







react, on page 208





Description












302


OL-26517-02

IP Service Level Agreement Commands threshold type immediate

threshold type immediate

To take action immediately upon a threshold violation, use the threshold type immediate command in the appropriate configuration mode. To clear the threshold type (reaction will never happen), use the no form of this command.

threshold type immediate no threshold type




IP SLA MPLS LSP monitor reaction condition configuration

Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.5.0

Release 3.7.2

Release 5.2.3

Modification



This command was added to IP SLA MPLS LSP monitor reaction condition configuration mode.



Usage Guidelines When the reaction conditions, such as threshold violations, are met for the monitored element, the action is immediately performed as defined by the action command.

If the threshold type immediate command is used in IP SLA reaction condition mode, it configures the threshold for the specific operation being configured. If the threshold type immediate command is used in

IP SLA MPLS LSP monitor reaction condition configuration mode, it configures the threshold 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 monitor



303 OL-26517-02

IP Service Level Agreement Commands threshold type immediate

Examples The following example shows how to use the threshold type immediate command:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-react-cond)# threshold type immediate

The following example shows how to use the threshold type immediate command in IP SLA MPLS LSP monitor reaction condition configuration mode:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-react-cond)# threshold type immediate


Command







react, on page 208





Description












304


OL-26517-02

IP Service Level Agreement Commands threshold type xofy

threshold type xofy

To take action upon X violations in Y probe operations, use the threshold type xofy command in IP SLA reaction condition configuration mode. To clear the threshold type (reaction will never happen), use the no form of this command.

threshold type xofy x-value y-value no threshold type

Syntax Description x-value y-value When the reaction conditions, such as threshold violations, are met for the monitored element after some x number of violations within some other y number of probe operations (for example, x of y), the action is performed as defined by the action command. Default is 5 for both x-value and y-value; for example, xofy 5 5. Range is 1 to 16.



Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification






Task ID

Task ID monitor


Examples The following example shows how to use the threshold type xofy command:



305 OL-26517-02

IP Service Level Agreement Commands threshold type xofy




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-react-cond)# threshold type xofy 1 5


Command





react, on page 208





Description










306


OL-26517-02

IP Service Level Agreement Commands timeout (IP SLA)

timeout (IP SLA)

To set the probe or control timeout interval, use the timeout command in the appropriate configuration mode.


timeout milliseconds no timeout

Syntax Description milliseconds Sets the amount of time (in milliseconds) that the IP SLA operation waits for a response from the request packet. Range is 1 to 604800000.

Command Default None.










Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.4.0

Release 3.5.0

Release 3.7.2

Release 5.2.3

Modification









307 OL-26517-02

IP Service Level Agreement Commands timeout (IP SLA)

Usage Guidelines If the timeout command is used in IP SLA operation mode, it configures the amount of time that a specific

IP SLA operation waits for a response from the request packet. If the timeout command is used in IP SLA

MPLS LSP monitor mode, it configures the amount of time that all operations associated with the monitored provider edge (PE) routers wait for a response from the request packet. This configuration is inherited by all

LSP operations that are created automatically.

Note The IP SLA responder needs at least one second to open a socket and program Local Packet Transport

Services (LPTS). Therefore, configure the IP SLA timeout to at least 2000 milli seconds.

Task ID

Task ID monitor


Examples The following example shows how to use the timeout command in IP SLA UDP jitter configuration mode:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-jitter)# timeout 10000

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





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lsp-ping)# timeout 10000


Command



Description



308


OL-26517-02

IP Service Level Agreement Commands tos

tos

To set the type of service (ToS) in a probe packet, use the tos command in the appropriate configuration mode.


tos number no tos

Syntax Description number Type of service number. Range is 0 to 255.

Command Default The type of service number is 0.






Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification





Usage Guidelines The ToS value is an 8-bit field in IP headers. The field contains information, such as precedence and ToS.

The information is useful for policy routing and for features like Committed Access Rate (CAR) in which routers examine ToS values. When the type of service is defined for an operation, the IP SLA probe packet contains the configured tos value in the IP header.

Task ID

Task ID monitor



309 OL-26517-02

IP Service Level Agreement Commands tos

Examples The following example shows how to use the tos command in IP SLA UDP jitter configuration mode:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-jitter)# tos 60


Command



Description



310


OL-26517-02

IP Service Level Agreement Commands ttl

ttl

To specify the time-to-live (TTL) value in the MPLS label of echo request packets, use the ttl command in the appropriate configuration mode. To return to the default value, use the no form of this command.

ttl time-to-live no ttl

Syntax Description time-to-live Maximum hop count for an echo request packet. Valid values are from 1 to

255.

Command Default For an MPLS LSP ping operation, the default time-to-live value is 255.

For an MPLS LSP trace operations, the default time-to-live value is 30.





Command History

Release

Release 3.4.0

Release 3.4.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification






Usage Guidelines Use the ttl command to set the maximum number of hops allowed for echo request packets in an MPLS LSP ping or MPLS LSP trace operation. Note that the number of possible hops differs depending the type of IP

SLA operation:

• For MPLS LSP ping operations, valid values are from 1 to 255 and the default is 255.

• For MPLS LSP trace operations, valid values are from 1 to 30 and the default is 30.


311 OL-26517-02

IP Service Level Agreement Commands ttl

Task ID

If the ttl command is used in IP SLA operation mode, it configures the time-to-live value for the specific operation being configured. If the ttl command is used in IP SLA MPLS LSP monitor mode, it configures the time-to-live value 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 monitor


Examples The following example shows how to use the ttl command:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mpls-lsp-ping)# ttl 200


Command





Description





MPLS VPN.

312


OL-26517-02

IP Service Level Agreement Commands type icmp echo

type icmp echo

To use the ICMP echo operation type, use the type icmp echo command in IP SLA operation configuration mode. To remove the operation, use the no form of this command.

type icmp echo no type icmp echo



Command Modes IP SLA operation configuration

Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.0.0

Modification






Task ID

Task ID monitor


Examples The following example shows how to use the type icmp echo command:




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op)# type icmp echo

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-icmp-echo)#


313 OL-26517-02

IP Service Level Agreement Commands type icmp echo


Command



Description



314


OL-26517-02

IP Service Level Agreement Commands type icmp path-echo

type icmp path-echo

To use the ICMP path-echo operation type, use the type icmp path-echo command in IP SLA operation configuration mode. To remove the operation, use the no form of this command.

type icmp path-echo no type icmp path-echo




Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.0.0

Modification






Task ID

Task ID monitor


Examples The following example shows how to use the type icmp path-echo command:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-icmp-path-echo)#


315 OL-26517-02

IP Service Level Agreement Commands type icmp path-echo


Command



Description



316


OL-26517-02

IP Service Level Agreement Commands type icmp path-jitter

type icmp path-jitter

To use the ICMP path-jitter operation type, use the type icmp path-jitter command in IP SLA operation configuration mode. To remove the operation, use the no form of this command.

type icmp path-jitter no type icmp path-jitter




Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.0.0

Modification






Task ID

Task ID monitor


Examples The following example shows how to use the type icmp path-jitter command:




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-op)# type icmp path-jitter

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-icmp-path-jitter)#


317 OL-26517-02

IP Service Level Agreement Commands type icmp path-jitter


Command



Description



318


OL-26517-02

IP Service Level Agreement Commands type mpls lsp ping

type mpls lsp ping

To verify the end-to-end connectivity of a label switched path (LSP) and the integrity of an MPLS network, use the type mpls lsp ping command in the appropriate configuration mode. To remove the operation, use the no form of this command.

type mpls lsp ping no type mpls lsp ping




IP SLA MPLS LSP monitor definition configuration

Command History

Release

Release 3.4.0

Release 3.4.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification



This command was added to IP SLA MPLS LSP monitor configuration mode.



Usage Guidelines Use the type mpls lsp ping command to configure parameters for an IP SLA LSP ping operation. After you enter the command, you enter IP SLA MPLS LSP Ping configuration mode.

An MPLS LSP ping operation tests connectivity between routers along an LSP path in an MPLS network and measures round-trip delay of the LSP by using an echo request and echo reply.

The MPLS LSP ping operation verifies LSP connectivity by using one of the supported Forwarding Equivalence

Class (FEC) entities between the ping origin and egress node of each FEC. The following FEC types are supported for an MPLS LSP ping operation:

• IPv4 LDP prefixes (configured with the

target ipv4, on page 291

command)

• MPLS TE tunnels (configured with the

target traffic-eng , on page 295

command)

• Pseudowire (configured with the

target pseudowire, on page 293

command)


319 OL-26517-02

IP Service Level Agreement Commands type mpls lsp ping

Task ID

For MPLS LSP monitor ping operations, only IPv4 LDP prefixes are supported.

If the type mpls lsp ping command is used in IP SLA operation configuration mode, it configures the parameters for the specific operation being configured. If the type mpls lsp ping command is used in IP SLA

MPLS LSP monitor configuration mode, it configures the parameters 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 monitor


Examples The following example shows how to use the type mpls lsp ping command:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mpls-lsp-ping)#

The following example shows how to use the type mpls lsp ping command in IP SLA MPLS LSP monitor configuration mode:






RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lsp-ping)#


Command







Description







MPLS VPN.

320


OL-26517-02

IP Service Level Agreement Commands type mpls lsp trace

type mpls lsp trace

To trace LSP paths and localize network faults in an MPLS network, use the type mpls lsp trace command in the appropriate configuration mode. To remove the operation, use the no form of this command.

type mpls lsp trace no type mpls lsp trace




IP SLA MPLS LSP monitor definition configuration

Command History

Release

Release 3.4.0

Release 3.4.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification



This command was added to IP SLA MPLS LSP monitor configuration mode.



Usage Guidelines Use the type mpls lsp trace command to configure parameters for an IP SLA LSP trace operation. After you enter the command, you enter IP SLA MPLS LSP Trace configuration mode.

An MPLS LSP trace operation traces the hop-by-hop route of LSP paths to a target router and measures the hop-by-hop round-trip delay for IPv4 LDP prefixes and TE tunnel FECs in an MPLS network. Echo request packets are sent to the control plane of each transit label switching router (LSR). A transit LSR performs various checks to determine if it is a transit LSR for the LSP path. A trace operation allows you to troubleshoot network connectivity and localize faults hop-by-hop.

In an MPLS LSP trace operation, each transit LSR returns information related to the type of Forwarding

Equivalence Class (FEC) entity that is being traced. This information allows the trace operation to check if the local forwarding information matches what the routing protocols determine as the LSP path.

An MPLS label is bound to a packet according to the type of FEC used for the LSP. The following FEC types are supported for an MPLS LSP trace operation:

• LDP IPv4 prefixes (configured with the

target ipv4, on page 291

command)


321 OL-26517-02

IP Service Level Agreement Commands type mpls lsp trace

Task ID

• MPLS TE tunnels (configured with the

target traffic-eng , on page 295

command)

For MPLS LSP monitor trace operations, only IPv4 LDP prefixes are supported.

If the type mpls lsp trace command is used in IP SLA operation configuration mode, it configures the parameters for the specific operation being configured. If the type mpls lsp trace command is used in IP SLA

MPLS LSP monitor configuration mode, it configures the parameters 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 monitor


Examples The following example shows how to use the type mpls lsp trace command:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mpls-lsp-trace)#

The following example shows how to use the type mpls lsp trace command in IP SLA MPLS LSP monitor configuration mode:






RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lsp-trace)#


Command





Description





322


OL-26517-02

IP Service Level Agreement Commands type udp echo

type udp echo

To use the UDP echo operation type, use the type udp echo command in IP SLA operation configuration mode. To remove the operation, use the no form of this command.

type udp echo no type udp echo




Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.0.0

Modification






Task ID

Task ID monitor


Examples The following example shows how to use the type udp echo command:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-echo)#


323 OL-26517-02

IP Service Level Agreement Commands type udp echo


Command



Description



324


OL-26517-02

IP Service Level Agreement Commands type udp jitter

type udp jitter

To use the UDP jitter operation type, use the type udp jitter command in IP SLA operation configuration mode. To remove the operation, use the no form of this command.

type udp jitter no type udp jitter




Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification






Task ID

Task ID monitor


Examples The following example shows how to use the type udp jitter command:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-jitter)#


325 OL-26517-02

IP Service Level Agreement Commands type udp jitter


Command



Description



326


OL-26517-02

IP Service Level Agreement Commands type udp ipv4 address

type udp ipv4 address

To configure a permanent port in the IP SLA responder for UDP echo or jitter operations, use the type udp

ipv4 address command in IP SLA responder configuration mode. To remove the specified permanent port, use the no form of this command.

type udp ipv4 address ip-address port port

no type udp ipv4 address ip-address port port

Syntax Description ip-address

port port

Specifies the IPv4 address at which the operation is received.

Specifies the port number at which the operation is received. Range is identical to the one used for the subagent that is, 1 to 65355.

Command Default If there is no default value, no permanent port is configured.

Command Modes IP SLA responder configuration

Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification






Task ID

Task ID monitor


Examples The following example shows how to configure a permanent port for the type udp ipv4 address command:




327 OL-26517-02

IP Service Level Agreement Commands type udp ipv4 address

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla)# responder

RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-resp)# type udp ipv4 address 192.0.2.11

port 10001


Command

responder, on page 219

Description

Enables the IP SLA responder for a UDP echo or jitter operation.

328


OL-26517-02

IP Service Level Agreement Commands verify-data

verify-data

To check each IP SLA response for corruption, use the verify-data command in the appropriate configuration mode. To disable data corruption checking, use the no form of this command.

verify-data no verify-data


Command Default The verify-data command is disabled.



Command History

Release

Release 3.3.0

Release 3.3.0

Release 3.7.2

Release 5.2.3

Modification






Task ID

Task ID monitor


Examples The following example shows how to use the verify-data command in IP SLA UDP jitter configuration mode:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-jitter)# verify-data


329 OL-26517-02

IP Service Level Agreement Commands verify-data


Command



Description



330


OL-26517-02

IP Service Level Agreement Commands vrf (IP SLA)

vrf (IP SLA)

To enable the monitoring of a Virtual Private Network (VPN) in an ICMP echo, ICMP path-echo, ICMP path-jitter, UDP echo, or UDP jitter operation, use the vrf command in the appropriate configuration mode.

To disable VPN monitoring, use the no form of this command.

vrf vrf-name no vrf

Syntax Description vrf-name Name of the VPN. Maximum length is 32 alphanumeric characters.

Command Default VPN monitoring is not configured for an IP SLA operation.

Command Modes IP SLA ICMP path-jitter configuration



IP SLA UDP echo configuration




Command History

Release

Release 3.4.0

Release 3.4.0

Release 3.7.2

Release 5.2.3

Modification





Usage Guidelines Use the vrf command to configure a non-default VPN routing and forwarding (VRF) table for an IP SLA operation. A VPN is commonly identified using the name of a VRF table. If you use the vrf command in the configuration of an IP SLA operation, the vrf-name value is used to identify the VPN for the particular operation.


331 OL-26517-02

IP Service Level Agreement Commands vrf (IP SLA)

Task ID

The default VRF table is used if no value is specified with the vrf command. If you enter a VPN name for an unconfigured VRF, the IP SLA operation fails and the following information is displayed in the results for the


command:

Latest operation return code : VrfNameError

The vrf command is supported only to configure the following IP SLA operations:



• IP SLA ICMP path-jitter

• IP SLA UDP echo

• IP SLA UDP jitter

• IP SLA MPLS LSP ping

• IP SLA MPLS LSP trace

Task ID monitor


Examples The following example shows how to use the vrf command:





RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-udp-jitter)# vrf vpn2


Command



type udp jitter, on page 325



type icmp path-jitter, on page 317

type udp echo, on page 323

Description



Configures an IP SLA UDP jitter operation.



Configures an IP SLA ICMP path-jitter operation.

Configures an IP SLA UDP echo operation.

332


OL-26517-02

IP Service Level Agreement Commands vrf (IP SLA MPLS LSP monitor)

vrf (IP SLA MPLS LSP monitor)

To specify which virtual routing and forwarding instance (VRF) is monitored in an IP SLA MPLS LSP monitor ping or trace, use the vrf command in the the appropriate configuration mode. To revert to the monitoring of all VRFs, use the no form of this command.

vrf vrf-name no vrf

Syntax Description vrf-name Name of the VRF. Maximum length is 32 alphanumeric characters.

Command Default All VRFs are monitored.



Command History

Release

Release 3.5.0

Release 3.5.0

Release 3.7.2

Release 5.0.0

Modification





Usage Guidelines The vrf command in IP SLA MPLS LSP monitor configuration mode specifies to monitor a specific VRF in ping and trace operations. The default is that all VRFs are monitored.

Task ID

Task ID monitor


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




333 OL-26517-02

IP Service Level Agreement Commands vrf (IP SLA MPLS LSP monitor)




RP/0/0RP0RSP0/CPU0:router:hostname(config-ipsla-mplslm-lsp-trace)# vrf vpn-lsp


Command




Description




MPLS VPN.

334


OL-26517-02

No results