Cisco IOS IP SLAs Command Reference

icmp-echo

To configure an IP Service Level Agreements (SLAs) Internet Control Message Protocol (ICMP) echo operation, use the icmp-echo command in IP SLA configuration mode.

icmp-echo {destination-ip-address | destination-hostname} [source-ip {ip-address | hostname} | source-interface interface-name]

Syntax Description

Defaults

No IP SLAs operation type is configured for the operation being configured.

Command Modes

IP SLA configuration (config-ip-sla)

Command History

Usage Guidelines

The default request packet data size for an ICMP echo operation is 28 bytes. Use the request-data-size command to modify this value. This data size is the payload portion of the ICMP packet, which makes a 64-byte IP packet.

You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or ICMP echo) before you can configure any of the other parameters of the operation. To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla global configuration command) and then reconfigure the operation with the new operation type.

IP SLAs ICMP echo operations support both IPv4 and IPv6 addresses.

Examples

In the following example, IP SLAs operation 10 is created and configured as an echo operation using the ICMP protocol and the destination IPv4 address 172.16.1.175:

ip sla 10

 icmp-echo 172.16.1.175

!

ip sla schedule 10 start-time now

In the following example, IP SLAs operation 11 is created and configured as an echo operation using the ICMP protocol and the destination IPv6 address 2001:DB8:100::1:

ip sla 11

 icmp-echo 2001:DB8:100::1

!

ip sla schedule 11 start-time now

Related Commands

icmp-jitter

To configure an IP Service Level Agreements (SLAs) Internet Control Message Protocol (ICMP) jitter operation, use the icmp-jitter command in IP SLA configuration mode.

icmp-jitter {destination-ip-address | destination-hostname} [interval milliseconds] [num-packets packet-number] [source-ip {ip-address | hostname}]

Syntax Description

Command Default

No IP SLAs operation type is configured for the operation being configured.

Command Modes

IP SLA configuration (config-ip-sla)

Command History

Usage Guidelines

You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation. To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla global configuration command) and then reconfigure the operation with the new operation type.

Examples

The following example shows how to configure an IP SLAs ICMP jitter operation:

ip sla 1

 icmp-jitter 172.18.1.129 interval 40 num-packets 100 source-ip 10.1.2.34

 frequency 50

!

ip sla reaction-configuration 1 react jitterAvg threshold-value 5 2 action-type trap 
threshold-type immediate

!

ip sla schedule 1 start-time now life forever

Related Commands

interval (LSP discovery)

To specify the time interval between Multiprotocol Label Switching (MPLS) echo requests that are sent as part of the label switched path (LSP) discovery process for a Cisco IOS IP Service Level Agreements (SLAs) LSP Health Monitor operation, use the interval command in auto IP SLA MPLS LSP discovery parameters configuration mode. To return to the default value, use the no form of this command.

interval milliseconds

no interval

Syntax Description

Command Default

0 milliseconds

Command Modes

Auto IP SLA MPLS LSP discovery parameters configuration (config-auto-ip-sla-mpls-lpd-params)

Command History

Usage Guidelines

Use the path-discover command to enable the LSP discovery option for an IP SLAs LSP Health Monitor operation and enter auto IP SLA MPLS LSP discovery parameters configuration mode.

Examples

The following example shows how to configure operation parameters, proactive threshold monitoring, and scheduling options using the LSP Health Monitor. In this example, the LSP discovery option is enabled for LSP Health Monitor operation 1. Operation 1 is configured to automatically create IP SLAs LSP ping operations for the equal-cost multipaths to all Border Gateway Protocol (BGP) next hop neighbors in use by all VPN routing and forwarding (VRF) instances associated with the source Provider Edge (PE) router. To discover the equal cost multipaths per BGP next hop neighbor, MPLS echo requests are sent every 2 milliseconds.

auto ip sla mpls-lsp-monitor 1

 type echo ipsla-vrf-all

 path-discover

!

 maximum-sessions 2

 session-timeout 60

 interval 2

 timeout 4

 force-explicit-null

 hours-of-statistics-kept 1

 scan-period 30

!

auto ip sla mpls-lsp-monitor schedule 1 schedule-period 60 frequency 100 start-time now

!

auto ip sla mpls-lsp-monitor reaction-configuration 1 react lpd tree-trace action-type 
trapOnly

auto ip sla mpls-lsp-monitor reaction-configuration 1 react lpd lpd-group retry 3 
action-type trapOnly

Related Commands

interval (params)

To specify the interval between packets for a jitter operation in an auto IP Service Level Agreements (SLAs) operation template, use the interval command in the appropriate submode of IP SLA template parameters configuration mode. To return to the default, use the no form of this command.

interval milliseconds

no interval

Syntax Description

Command Default

The default interval between packets is 20 ms.

Command Modes

IP SLA Template Parameters Configuration

ICMP jitter configuration (config-icmp-jtr-params)
UDP jitter configuration (config-udp-jtr-params)

Command History

Usage Guidelines

This command changes the interval between packets sent during a jitter operation from the default (20 ms) to the specified interval.

You must configure the type of IP SLAs operation, such as User Datagram Protocol (UDP) jitter or Internet Control Message Protocol (ICMP) jitter, before you can configure any other parameters of the operation.

Before you can use this command to configure auto IP SLAs operation templates, you must enter the parameters command in IP SLA template configuration mode.

Examples

The following example shows how to configure an auto IP SLAs operation template for an ICMP jitter operation with an interval of 30 ms between packets:

Router(config)#ip sla auto template type ip icmp-jitter 1

Router(config-tplt-icmp-jtr)#parameters

Router(config-icmp-jtr-params)#interval 30

Router(config-icmp-jtr-params)#end

Router# show ip sla auto template type ip icmp-jitter

IP SLAs Auto Template: 1

    Measure Type: icmp-jitter

    Description: 

    IP options:

        Source IP: 0.0.0.0

        VRF:    TOS: 0x0

    Operation Parameters:

        Number of Packets: 10   Inter packet interval: 30

        Timeout: 5000           Threshold: 5000

    Statistics Aggregation option:

        Hours of statistics kept: 2

    Statistics Distributions options:

        Distributions characteristics: RTT

        Distributions bucket size: 20

        Max number of distributions buckets: 1

    Reaction Configuration: None

Related Commands

ip-address (endpoint list)

To specify destination IP addresses for routing devices or Cisco IOS IP Service Level Agreements (SLAs) Responders in Cisco devices and add them to an auto IP SLAs endpoint list, use the ip-address command in IP SLA endpoint-list configuration mode. To remove some or all IP addresses from the template, use the no form of this command.

ip-address address [-address | ,...,address] port port

no ip-address address [address-address | ,...,address] port port

Syntax Description

Command Default

The auto IP SLAs endpoint list is empty.

Command Modes

IP SLA endpoint-list configuration (config-epl)

Command History

Usage Guidelines

This command adds IP addresses to the auto IP SLAs endpoint list being configured.

Destination IP addresses can either be manually configured by using this command or automatically discovered by using the discover command. If you use this command to configure an auto IP SLAs endpoint list, you cannot use the discover command to discover IP addresses for this endpoint list.

You cannot combine a list of individual IP addresses (address,address) and a range of IP addresses (address-address) in a single command.

The maximum number of IP addresses allowed in a list of individual addresses (address,address) per command is five.

To remove one or more IP addresses without reconfiguring the entire template, use the no form of this command. You can delete a range of IP addresses or a single IP addresses per command.

Modifications to auto IP SLAs endpoint lists, such as adding or removing IP addresses, take effect in the next schedule cycle.

Use the destination command in IP SLA auto-measure group configuration mode to specify an endpoint list for an IP SLAs auto-measure group.

Examples

The following example shows how to configure an IP SLAs endpoint list using this command:

Router(config)#ip sla auto endpoint-list type ip test

Router(config-epl)#ip-address 10.1.1.1-13 port 5000

Router(config-epl)#no ip-address 10.1.1.3-4 port 5000

Router(config-epl)#no ip-address 10.1.1.8 port 5000

Router(config-epl)#no ip-address 10.1.1.12 port 5000         

Router(config-epl)#exit

Router#

The following output from the show ip sla auto endpoint command shows the results of the preceding configuration:

Router# show ip sla auto endpoint-list

Endpoint-list Name: test

    Description: 

    ip-address 10.1.1.1-2 port 5000

    ip-address 10.1.1.5-7 port 5000

    ip-address 10.1.1.9-11 port 5000

    ip-address 10.1.1.13 port 5000

Related Commands

ip sla

To begin configuring a Cisco IOS IP Service Level Agreements (SLAs) operation and enter IP SLA configuration mode, use the ip sla command in global configuration mode. To remove all configuration information for an operation, including the schedule of the operation, reaction configuration, and reaction triggers, use the no form of this command.

ip sla operation-number

no ip sla operation-number

Syntax Description

Defaults

No IP SLAs operation is configured.

Command Modes

Global configuration

Command History

Usage Guidelines

The ip sla command is used to begin configuration for an IP SLAs operation. Use this command to specify an identification number for the operation you are about to configure. After you enter this command, the router will enter IP SLA configuration mode.

The ip sla command is supported in IPv4 networks. This command can also be used when configuring an IP SLAs operation that supports IPv6 addresses.

IP SLAs allows a maximum of 2000 operations.

Debugging is supported only on the first 32 operation numbers.

After you configure an operation, you must schedule the operation. For information on scheduling an operation, refer to the ip sla schedule and ip sla group schedule global configuration commands. You can also optionally set reaction triggers for the operation. For information on reaction triggers, refer to the ip sla reaction-configuration and ip sla reaction-trigger global configuration commands.

To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla) and then reconfigure the operation with the new operation type.

Note After you schedule an operation, you cannot modify the configuration of the operation. To modify the configuration of the operation after it is scheduled, you must first delete the IP SLAs operation (using the no ip sla command) and then reconfigure the operation with the new operation parameters.

To display the current configuration settings of the operation, use the show ip sla configuration command in user EXEC or privileged EXEC mode.

Examples

In the following example, operation 99 is configured as a UDP jitter operation in an IPv4 network and scheduled to start running in 5 hours. The example shows the ip sla command being used in an IPv4 network.

ip sla 99

 udp-jitter 172.29.139.134 dest-port 5000 num-packets 20

!

ip sla schedule 99 life 300 start-time after 00:05:00

Note If operation 99 already exists and has not been scheduled, the command line interface will enter IP SLA configuration mode for operation 99. If the operation already exists and has been scheduled, this command will fail.

Related Commands

ip sla auto discovery

To enable auto discovery in Cisco IOS IP Service Level Agreements (SLAs) Engine 3.0, use the ip sla auto discovery command in global configuration mode. To disable auto discovery, use the no form of this command.

ip sla auto discovery

no ip sla auto discovery

Syntax Description

This command has no arguments or keywords.

Command Default

Auto discovery is disabled.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

This command enables the source for IP SLAs operations to auto-discover Cisco IP SLAs Responder endpoints.

Examples

The following example shows how to configure the ip sla auto discovery command:

Router>show ip sla auto discovery

IP SLAs auto-discovery status: Disabled

The following Endpoint-list are configured to auto-discovery:

Router>enable

Router#configure terminal

Enter configuration commands, one per line.  End with CNTL/Z.

Router(config)#ip sla auto discovery 

Router(config)#exit

Router#

Router# show ip sla auto discovery

IP SLAs auto-discovery status: Enabled

The following Endpoint-list are configured to auto-discovery:

.

.

.

Related Commands

ip sla auto endpoint-list

To enter IP SLA endpoint-list configuration mode and begin configuring an auto IP Service Level Agreements (SLAs) endpoint list, use the ip sla auto endpoint-list command in global configuration mode. To remove an endpoint list, use the no form of this command.

ip sla auto endpoint-list type ip template-name

no ip sla auto endpoint-list template-name

Syntax Description

Command Default

No auto IP SLAs endpoint list is configured.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

This command assigns a name to an auto IP SLAs endpoint list and enters IP SLA endpoint-list configuration mode on the router.

Use the commands in IP SLA endpoint-list configuration mode to configure a template of destination IP addresses of routing devices or Cisco IOS IP SLAs Responders in Cisco devices to be referenced by one or more IP SLAs auto-measure groups. Destination addresses can be either manually configured by using the ip-address command or automatically discovered using the discover command.

Each auto IP SLAs endpoint list can be referenced by one or more IP SLAs auto-measure groups. Use the destination command in IP SLA auto-measure group configuration mode to specify an endpoint list for an IP SLAs auto-measure group.

Examples

The following example shows how to configure two auto IP SLAs endpoint lists of endpoints, one by manually configuring destination IP addresses and one using auto discovery:

Router(config)# ip sla auto endpoint-list type ip man1

Router(config-epl)# ip-address 10.1.1.1-10.1.1.12 port 23

Router(config-epl)# ip-address 10.1.1.15,10.1.1.23 port 23

Router(config-epl)# no ip-address 10.1.1.8,10.1.1.10 port 23

Router(config-epl)# description testing manual build

Router(config-epl)# exit 

Router(config)#

Router(config)#ip sla auto discover

Router(config)#ip sla auto endpoint-list type ip autolist

Router(config-epl)#discover port 5000

Router(config-epl)#access-list 3

Router(config-epl)#exit

Router#

Router# show ip sla auto endpoint-list

Endpoint-list Name: man1

    Description: testing manual build

    ip-address 10.1.1.1-7 port 23

    ip-address 10.1.1.9,10.1.1.15,10.1.1.23 port 23

Endpoint-list Name: autolist

    Description: 

    Auto Discover Parameters

        Destination Port: 5000

        Access-list: 3

        Ageout: 3600    Measurement-retry: 3

    1 endpoints are discovered for autolist

Related Commands

ip sla auto group

To enter IP SLA auto-measure group configuration mode and begin configuring a Cisco IOS IP Service Level Agreements (SLAs) auto-measure group, use the ip sla auto group command in global configuration mode. To remove the auto-measure group configuration, use the no form of this command.

ip sla auto group type ip group-name

no ip sla auto group group-name

Syntax Description

Command Default

No IP SLAs auto-measure group is configured.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

This command assigns a name to an IP SLAs auto-measure group and enters IP SLA auto-measure group configuration mode.

Use the commands in IP SLA auto-measure group configuration mode to specify an auto IP SLAs operation template, endpoint list, and scheduler for the group.

Examples

The following example shows how to configure an IP SLAs auto-measure group:

Router(config)#ip sla auto group type ip 1           

Router(config-am-grp)#destination 1

Router(config-am-grp)#schedule 1

Router(config-am-grp)#end

Router#

Router# show ip sla auto group 

Group Name: 1

    Description: 

    Activation Trigger: Immediate

    Destination: 1

    Schedule: 1

IP SLAs Auto Template: default

    Measure Type: icmp-jitter

    Description: 

    IP options:

        Source IP: 0.0.0.0

        VRF:    TOS: 0x0

    Operation Parameters:

        Number of Packets: 10   Inter packet interval: 20

        Timeout: 5000           Threshold: 5000

    Statistics Aggregation option:

        Hours of statistics kept: 2

    Statistics Distributions options:

        Distributions characteristics: RTT

        Distributions bucket size: 20

        Max number of distributions buckets: 1

    Reaction Configuration: None

IP SLAs auto-generated operations of group 1

    no operation created

Related Commands

ip sla auto schedule

To enter IP SLA auto-measure schedule configuration mode and begin configuring an auto IP Service Level Agreements (SLAs) scheduler, use the ip sla auto schedule command in global configuration mode. To remove the configuration and stop all operations controlled by this scheduler, use the no form of this command.

ip sla auto schedule schedule-id

no ip sla auto schedule schedule-id

Syntax Description

Command Default

No auto IP SLAs scheduler is configured.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

This command assigns a unique identifier to an auto IP SLAs scheduler and enters IP SLA auto-measure schedule configuration mode on the router.

Use the commands in IP SLA auto-measure schedule configuration mode to modify the default configuration of an auto IP SLAs scheduler.

Each auto IP SLAs scheduler can be referenced by one or more IP SLAs auto-measure groups. Use the schedule command in IP SLA auto-measure group configuration mode to specify a scheduler for an IP SLAs auto-measure group.

Examples

The following example shows how to create the default configuration for an auto IP SLAs scheduler:

Router(config)#ip sla auto schedule 2

Router(config-am-schedule)#end

Router#

Router# show ip sla auto schedule 2

Group sched-id: 2

    Probe Interval (ms) : 1000

    Group operation frequency (sec): 60

    Status of entry (SNMP RowStatus): Active

    Next Scheduled Start Time: Pending trigger

    Life (sec): 3600

    Entry Ageout (sec): never

Related Commands 

ip sla auto template

To enter IP SLA template configuration mode and begin configuring an auto IP Service Level Agreements (SLAs) operation template, use the ip sla auto template command in global configuration mode. To remove the operation template, use the no form of this command.

ip sla auto template type ip operation template-name

no ip sla auto template type ip operation template-name

Syntax Description

Command Default

No IP SLAs operation template is configured.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

This command assigns a name and operation to an auto IP SLAs operation template and enters a submode of the IP SLA template configuration mode based on the specified operation argument, such as IP SLA template icmp-echo configuration submode (config-tplt-icmp-ech).

Use the commands in IP SLA template configuration submode to modify the default configuration of an auto IP SLAs operation template.

Each auto IP SLAs operation template can be referenced by one or more IP SLAs auto-measure groups. Use the template command in IP SLA auto-measure group configuration mode to specify an operation template for an IP SLAs auto-measure group.

Examples

The following example shows how to create a default configuration for an auto IP SLAs operation template for ICMP echo:

Router(config)# ip sla auto template type ip icmp-echo

Router(config-tplt-icmp-ech)#end

Router# show ip sla auto template type ip icmp-echo

IP SLAs Auto Template: basic_icmp_echo

    Measure Type: icmp-echo

    Description: 

    IP options:

        Source IP: 0.0.0.0

        VRF:    TOS: 0x0

    Operation Parameters:

        Request Data Size: 28   Verify Data: false

        Timeout: 5000           Threshold: 5000

    Statistics Aggregation option:

        Hours of statistics kept: 2

    History options:

        History filter: none

        Max number of history records kept: 15

        Lives of history kept: 0

    Statistics Distributions options:

        Distributions characteristics: RTT

        Distributions bucket size: 20

        Max number of distributions buckets: 1

    Reaction Configuration: None

Related Commands

ip sla enable reaction-alerts

To enable Cisco IP Service Level Agreements (SLAs) notifications to be sent to all registered applications, use the ip sla enable reaction-alerts command in global configuration mode. To disable IP SLAs notifications, use the no form of this command.

ip sla enable reaction-alerts

no ip sla enable reaction-alerts

Syntax Description

This command has no arguments or keywords.

Command Default

IP SLAs notifications are not sent to registered applications.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

The only applications that can register are Cisco IOS processes running on the router. Proactive threshold monitoring parameters for a Cisco IOS IP SLAs operation can be configured that will generate notifications when a threshold is crossed.

Examples

The following example shows how to enable IP SLAs notifications to be sent to all registered applications:

Router(config)# ip sla enable reaction-alerts

Related Commands

ip sla ethernet-monitor

To begin configuring a Cisco IOS IP Service Level Agreements (SLAs) auto Ethernet operation and enter IP SLA Ethernet monitor configuration mode, use the ip sla ethernet-monitor command in global configuration mode. To remove all configuration information for an auto Ethernet operation, including the schedule of the operation, reaction configuration, and reaction triggers, use the no form of this command.

ip sla ethernet-monitor operation-number

no ip sla ethernet-monitor operation-number

Syntax Description

Command Default

No IP SLAs operation is configured.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

The ip sla ethernet-monitor command is used to begin configuration for an IP SLAs auto Ethernet operation. Use this command to specify an identification number for the operation you are about to configure. After you enter this command, the router will enter IP SLA Ethernet monitor configuration mode.

After you configure an auto Ethernet operation, you must schedule the operation. To schedule an auto Ethernet operation, use the ip sla ethernet-monitor schedule command in global configuration mode. You can also optionally set reaction configuration for the operation (see the ip sla ethernet-monitor reaction-configuration command).

To display the current configuration settings of an auto Ethernet operation, use the show ip sla ethernet-monitor configuration command in user EXEC or privileged EXEC mode.

To change the operation type of an existing auto Ethernet operation, you must first delete the operation (using the no ip sla ethernet-monitor global configuration command) and then reconfigure the operation with the new operation type.

Examples

The following example shows how to configure operation parameters, proactive threshold monitoring, and scheduling options using an IP SLAs auto Ethernet operation. In this example, operation 10 is configured to automatically create IP SLAs Ethernet ping operations for all the discovered maintenance endpoints in the domain named testdomain and VLAN identification number 34. As specified by the proactive threshold monitoring configuration, when three consecutive connection loss events occur, a Simple Network Management Protocol (SNMP) trap notification should be sent. The schedule period for operation 10 is 60 seconds, and the operation is scheduled to start immediately.

ip sla ethernet-monitor 10

 type echo domain testdomain vlan 34

!

ip sla ethernet-monitor reaction-configuration 10 react connectionLoss threshold-type 
consecutive 3 action-type trapOnly

!

ip sla ethernet-monitor schedule 10 schedule-period 60 start-time now

Related Commands

ip sla ethernet-monitor reaction-configuration

To configure proactive threshold monitoring parameters for a Cisco IOS IP Service Level Agreements (SLAs) auto Ethernet operation, use the ip sla ethernet-monitor reaction-configuration command in global configuration mode. To clear all threshold monitoring configuration for a specified auto Ethernet operation, use the no form of this command.

ip sla ethernet-monitor reaction-configuration operation-number [react monitored-element [action-type {none | trapOnly}] [threshold-type {average [number-of-measurements] | consecutive [occurrences] | immediate | never | xofy [x-value y-value]}] [threshold-value upper-threshold lower-threshold]]

no ip sla ethernet-monitor reaction-configuration operation-number [react monitored-element]

Syntax Description

Command Default

IP SLAs proactive threshold monitoring is disabled.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

You can configure the ip sla ethernet-monitor reaction-configuration command multiple times to enable proactive threshold monitoring for multiple elements (for example, configuring thresholds for round-trip time and destination-to-source packet loss) for the same operation. However, disabling of individual monitored elements is not supported. In other words, the no ip sla ethernet-monitor reaction-configuration command will disable all proactive threshold monitoring configuration for the specified IP SLAs operation.

SNMP traps for IP SLAs are supported by the CISCO-RTTMON-MIB and CISCO-SYSLOG-MIB. Use the ip sla logging traps command to enable the generation of SNMP system logging messages specific to IP SLAs trap notifications. Use the snmp-server enable traps rtr command to enable the sending of IP SLAs SNMP trap notifications.

To display the current threshold monitoring configuration settings for an auto Ethernet operation, use the show ip sla ethernet-monitor configuration command.

Table 10 lists the default upper and lower thresholds for specific monitored elements.

Examples

The following example shows how to configure operation parameters, proactive threshold monitoring, and scheduling options using an IP SLAs auto Ethernet operation. In this example, operation 10 is configured to automatically create IP SLAs Ethernet ping operations for all the discovered maintenance endpoints in the domain named testdomain and VLAN identification number 34. As specified by the proactive threshold monitoring configuration, when three consecutive connection loss events occur, an SNMP trap notification should be sent. The schedule period for operation 10 is 60 seconds, and the operation is scheduled to start immediately.

Router(config)# ip sla ethernet-monitor 10

Router(config-ip-sla-ethernet-monitor)# type echo domain testdomain vlan 34

!

Router(config)# ip sla ethernet-monitor reaction-configuration 10 react connectionLoss 
threshold-type consecutive 3 action-type trapOnly

!

Router(config)# ip sla ethernet-monitor schedule 10 schedule-period 60 start-time now

Related Commands

ip sla ethernet-monitor schedule

To configure the scheduling parameters for an IP Service Level Agreements (SLAs) auto Ethernet operation, use the ip sla ethernet-monitor schedule command in global configuration mode. To stop the operation and place it in the default state (pending), use the no form of this command.

ip sla ethernet-monitor schedule operation-number schedule-period seconds [frequency [seconds]] [start-time {after hh:mm:ss | hh:mm[:ss] [month day | day month] | now | pending}]

no ip sla ethernet-monitor schedule operation-number

Syntax Description

Command Default

The IP SLAs auto Ethernet operation is placed in a pending state (that is, the operation is enabled but is not actively collecting information).

Command Modes

Global configuration (config)

Command History

Usage Guidelines

After you schedule an IP SLAs auto Ethernet operation with the ip sla ethernet-monitor schedule command, you should not change the configuration of the operation until the operation has finished collecting information. To change the configuration of the operation, use the no ip sla ethernet-monitor schedule operation-number command in global configuration mode and then enter the new configuration information.

To display the current configuration settings of an IP SLAs auto Ethernet operation, use the show ip sla ethernet-monitor configuration command in user EXEC or privileged EXEC mode.

Examples

The following example shows how to configure operation parameters, proactive threshold monitoring, and scheduling options using an IP SLAs auto Ethernet operation. In this example, operation 10 is configured to automatically create IP SLAs Ethernet ping operations for all the discovered maintenance endpoints in the domain named testdomain and VLAN identification number 34. As specified by the proactive threshold monitoring configuration, when three consecutive connection loss events occur, a Simple Network Management Protocol (SNMP) trap notification should be sent. The schedule period for operation 10 is 60 seconds, and the operation is scheduled to start immediately.

ip sla ethernet-monitor 10

 type echo domain testdomain vlan 34

!

ip sla ethernet-monitor reaction-configuration 10 react connectionLoss threshold-type 
consecutive 3 action-type trapOnly

!

ip sla ethernet-monitor schedule 10 schedule-period 60 start-time now

Related Commands

ip sla group schedule

To perform multioperation scheduling for Cisco IOS IP Service Level Agreements (SLAs) operations, use the ip sla group schedule command in global configuration mode. To cause all the IP SLAs operations belonging to a multioperation schedule to become inactive, use the no form of this command.

ip sla group schedule group-id {operation-ids | add operation-ids | delete operation-ids | reschedule} schedule-period seconds [ageout seconds] [frequency [seconds | range random-frequency-range]] [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}]

no ip sla group schedule group-id

Syntax Description

Defaults

The multioperation schedule is placed in a pending state (that is, the group of IP SLAs operations are enabled but are not actively collecting information).

Command Modes

Global configuration

Command History

Usage Guidelines

Though the IP SLAs multioperation scheduling functionality helps in scheduling thousands of operations, you should be cautious when specifying the number of operations, the schedule period, and the frequency to avoid any significant CPU impact.

For example, consider a scenario where you are scheduling 1 to 780 operations at a schedule period of 60 seconds. The command would be as follows:

ip sla group schedule 2 1-780 schedule-period 60 start-time now

IP SLAs calculates how many operations it should start in each 1-second interval by dividing the number of operations by the schedule period (780 operations divided by 60 seconds, which is 13 operations per second). Operations 1 to 13 in multioperation group 2 start after 0 seconds, operations 14 to 26 start after 1 second, operations 27 to 40 start after 2 seconds, and the iteration continues until operations 768 to 780 start after 59 seconds. This high value of operations starting at every 1-second interval (especially for jitter operations) can load the CPU to very high values.

On a Cisco 2600 router, the maximum recommended value of operations per second is 6 or 7 (approximately 350 to 400 operations per minute). Exceeding this value of 6 or 7 operations per second could cause major performance (CPU) impact. Note that the maximum recommended value of operations per second varies from platform to platform.

Note No warning messages will be displayed if IP SLAs multiple operations scheduling leads to a high number of operations starting per second.

When you reboot the router, the IP SLAs multiple operations scheduling functionality schedules the operations in the same order as was done before the reboot. For example, assume the following operation had been scheduled:

ip sla group schedule 2 1-20 schedule-period 40 start-time now

Over a range of 40 seconds, 20 operations have to be started (that is, one operation every 2 seconds). After the system reboot, operation 1 will start at t seconds and operation 2 starts at t+2 seconds, operation 3 starts at t+4 seconds, and so on.

The IP SLAs multiple operations scheduling functionality schedules the maximum number of operations possible without aborting. However, this functionality skips those IP SLAs operations that are already running or those that are not configured and hence do not exist. The total number of operations will be calculated based on the number of operations specified in the command, irrespective of the number of operations that are missing or already running. The IP SLAs multiple operations scheduling functionality displays a message showing the number of active and missing operations. However, these messages are displayed only if you schedule operations that are not configured or are already running.

IP SLAs Random Scheduler

The IP SLAs random scheduler option provides the capability to schedule multiple IP SLAs operations to begin at random intervals over a specified duration of time. The random scheduler option is disabled by default. To enable the random scheduler option, you must configure the frequency range random-frequency-range keywords and argument. The operations within the multioperation schedule restart at uniformly distributed random frequencies within the specified frequency range. The following guidelines apply for setting the frequency range:

•The starting value of the frequency range should be greater than the timeout values of all the operations in the multioperation schedule.

•The starting value of the frequency range should be greater than the schedule period (amount of time for which the group of operations is scheduled). This guideline ensures that the same operation does not get scheduled more than once within the schedule period.

The following guidelines apply if the random scheduler option is enabled:

•The individual operations in a multioperation schedule will be uniformly distributed to begin at random intervals over the schedule period.

•The operations within the multioperation schedule restart at uniformly distributed random frequencies within the specified frequency range.

•The minimum time interval between the start of each operation in a multioperation schedule is 100 milliseconds (0.1 seconds). If the random scheduler option is disabled, the minimum time interval is 1 second.

•Only one operation can be scheduled to begin at any given time. If the random scheduler option is disabled, multiple operations can begin at the same time.

•The first operation will always begin at 0 milliseconds of the schedule period.

•The order in which each operation in a multioperation schedule begins is random.

Adding or Deleting IP SLAs Operations

The following guidelines apply when an IP SLAs operation is added to or deleted from an existing multioperation schedule:

•If an operation is added that already belongs to the multioperation schedule, no action is taken.

•If two or more operations are added after the multioperation schedule has started, then the start times of the newly added operations will be uniformly distributed based on a time interval that was calculated prior to the addition of the new operations. If two or more operations are added before the multioperation schedule has started, then the time interval is recalculated based on both the existing and newly added operations.

•If an operation is added to a multioperation schedule in which the random scheduler option is enabled, then the start time and frequency of the newly added operation will be randomly chosen within the specified parameters.

•If an operation is added to a multioperation schedule in which the existing operations have aged out or the lifetimes of the existing operations have ended, the newly added operation will start and remain active for the amount of time specified by the multioperation schedule.

•If an active operation is deleted, then the operation will stop collecting information and become inactive.

•If the ip sla group schedule group-id reschedule command is entered after an operation is added or deleted, the time interval between the start times of the operations is recalculated based on the new number of operations belonging to the multioperation schedule.

Before Cisco IOS Release 15.1(1)T, this command could not be used to schedule a single operation because the only valid options for the operation-ids argument were a list (id,id,id) of IDs, a range (id-id) of IDs, or a combination of lists and ranges. If you attempted to use this command to schedule a single operation, the following messages were displayed:

Router(config)# sla group schedule 1 1 schedule-period 5 start-time now

%Group Scheduler: probe list wrong syntax

%Group schedule string of probe ID's incorrect

Router(config)#

In Cisco IOS Release 15.1(1)T and later releases, a single operation ID is a valid option for the operation-ids argument.

Examples

The following example shows how to schedule IP SLAs operations 3, 4, and 6 to 10 (identified as group 1) using multioperation scheduling. In this example, the operations are scheduled to begin at equal intervals over a schedule period of 20 seconds. The first operation (or set of operations) is scheduled to start immediately. Since the frequency is not specified, it is set to the value of the schedule period (20 seconds) by default.

ip sla group schedule 1 3, 4, 6-10 schedule-period 20 start-time now

The following example shows how to schedule IP SLAs operations 1 to 3 (identified as group 2) using the random scheduler option. In this example, the operations are scheduled to begin at random intervals over a schedule period of 50 seconds. The first operation is scheduled to start immediately. The frequency at which each operation will restart will be chosen randomly within the range of 80 to 100 seconds.

ip sla group schedule 2 1-3 schedule-period 50 frequency range 80-100 start-time now

Related Commands

ip sla key-chain

To enable Cisco IOS IP Service Level Agreements (SLAs) control message authentication and specify an MD5 key chain, use the ip sla key-chain command in global configuration mode. To remove control message authentication, use the no form of this command.

ip sla key-chain name

no ip sla key-chain

Syntax Description

Defaults

Control message authentication is disabled.

Command Modes

Global configuration

Command History

Usage Guidelines

The authentication configuration on the IP SLAs source and IP SLAs Responder devices must be the same. In other words, both devices must be configured with the same key chain or both devices must not use authentication.

If the ip sla key-chain command is entered, at least one key must be added to the specified MD5 key chain in order for MD5 authentication to occur.

Examples

In the following example, the IP SLAs control message uses MD5 authentication, and the key chain name is CSAA. The authentication string for key 1 is csaakey1.

ip sla key-chain csaa

key chain csaa

key 1

key-string csaakey1

Related Commands

ip sla logging traps

To enable the generation of Simple Network Management Protocol (SNMP) system logging messages specific to Cisco IOS IP Service Level Agreements (SLAs) trap notifications, use the ip sla logging traps command in global configuration mode. To disable IP SLAs system logging SNMP traps, use the no form of this command.

ip sla logging traps

no ip sla logging traps

Syntax Description

This command has no arguments or keywords.

Defaults

SNMP system logging messages specific to IP SLAs trap notifications are not generated.

Command Modes

Global configuration

Command History

Usage Guidelines

SNMP trap notifications for IP SLAs can be configured as a triggered action, to be sent when monitored values exceed an upper threshold or fall below a lower threshold, or when a set of defined conditions are met. For example, an SNMP trap can be triggered by five consecutive timeouts during an IP SLAs operation. The sending of SNMP traps is one of the options for triggered actions that can be configured for IP SLAs threshold violations. To configure proactive threshold monitoring parameters for an IP SLAs operation, use the ip sla reaction-configuration command in global configuration mode.

SNMP traps for IP SLAs are supported by the CISCO-RTTMON-MIB and CISCO-SYSLOG-MIB. Use the snmp-server enable traps rtr command to enable the sending of IP SLAs SNMP trap notifications.

Examples

The following example shows the configuration of IP SLAs traps to be triggered for round-trip time (RTT) violations and Voice over IP (VoIP) mean opinion score (MOS) violations, and the necessary SNMP configuration for enabling these SNMP logging traps:

ip sla 1

 udp-jitter 209.165.200.225 dest-port 9234

!

ip sla schedule 1 start now life forever

ip sla reaction-configuration 1 react rtt threshold-type immediate threshold-value 3000 
2000 action-type trapOnly 

ip sla reaction-configuration 1 react MOS threshold-type consecutive 4 threshold-value 390 
220 action-type trapOnly 

!

ip sla logging traps

snmp-server enable traps rtr

Related Commands

ip sla low-memory

To specify how much unused memory must be available to allow Cisco IOS IP Service Level Agreements (SLAs) configuration, use the ip sla low-memory command in global configuration mode. To remove the type configuration for the operation, use the no form of this command.

ip sla low-memory bytes

no ip sla low-memory

Syntax Description

Defaults

The default amount of memory is 25 percent of the memory available on the system.

Command Modes

Global configuration

Command History

Usage Guidelines

The ip sla low-memory command allows you to specify the amount of memory that the IP SLAs can use. If the amount of available free memory falls below the value specified in the ip sla low-memory command, then the IP SLAs will not allow new operations to be configured. If this command is not used, the default low-memory value is 25 percent. This means that if 75 percent of system memory has been utilized you will not be able to configure any IP SLAs characteristics.

The value of the ip sla low-memory command should not exceed the amount of free memory available on the system. To determine the amount of free memory available on the system, use the show memory user EXEC or privileged EXEC command.

Examples

In the following example, the router is configured so that no less than 2 MB of memory will be free for IP SLAs configuration:

ip sla low-memory 2097152

Related Commands

ip sla monitor

Note Effective with Cisco IOS Release 12.4(4)T, 12.2(33)SB, and 12.2(33)SXI, the ip sla monitor command is replaced by the ip sla command. See the ip sla command for more information.

To begin configuring a Cisco IOS IP Service Level Agreements (SLAs) operation and enter IP SLA monitor configuration mode, use the ip sla monitor command in global configuration mode. To remove all configuration information for an operation, including the schedule of the operation, reaction configuration, and reaction triggers, use the no form of this command.

ip sla monitor operation-number

no ip sla monitor operation-number

Syntax Description

Defaults

No IP SLAs operation is configured.

Command Modes

Global configuration

Command History

Usage Guidelines

The ip sla monitor command is used to begin configuration for an IP SLAs operation. Use this command to specify an identification number for the operation you are about to configure. After you enter this command, the router will enter IP SLA monitor configuration mode.

IP SLAs allows a maximum of 2000 operations.

Debugging is supported only on the first 32 operation numbers.

After you configure an operation, you must schedule the operation. For information on scheduling an operation, refer to the ip sla monitor schedule and ip sla monitor group schedule global configuration commands. You can also optionally set reaction triggers for the operation. For information on reaction triggers, refer to the ip sla monitor reaction-configuration and ip sla monitor reaction-trigger global configuration commands.

To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla monitor global configuration command) and then reconfigure the operation with the new operation type.

Note After you schedule an operation, you cannot modify the configuration of the operation. To modify the configuration of the operation after it is scheduled, you must first delete the IP SLAs operation (using the no ip sla monitor command) and then reconfigure the operation with the new operation parameters.

To display the current configuration settings of the operation, use the show ip sla monitor configuration command in user EXEC or privileged EXEC mode.

Examples

In the following example, operation 99 is configured as a UDP jitter operation and scheduled to start running in 5 hours:

ip sla monitor 99

 type jitter dest-ipaddr 172.29.139.134 dest-port 5000 num-packets 20

!

ip sla monitor schedule 99 life 300 start-time after 00:05:00

Note If operation 99 already exists and has not been scheduled, the command line interface will enter IP SLA monitor configuration mode for operation 99. If the operation already exists and has been scheduled, this command will fail.

Related Commands

ip sla monitor group schedule

Note Effective with Cisco IOS Release 12.4(4)T, 12.2(33)SB, and 12.2(33)SXI, the ip sla monitor group schedule command is replaced by the ip sla group schedule command. See the ip sla group schedule command for more information.

To perform group scheduling for Cisco IOS IP Service Level Agreements (SLAs) operations, use the ip sla monitor group schedule command in global configuration mode. To stop the operation and place it in the default state of normal scheduling, use the no form of this command.

ip sla monitor group schedule group-operation-number operation-id-numbers schedule-period seconds [ageout seconds] [frequency [seconds | range random-frequency-range]] [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}]

no ip sla monitor group schedule

Syntax Description

Defaults

The operation is placed in a pending state (that is, the operation is enabled but is not actively collecting information).

Command Modes

Global configuration

Command History

Usage Guidelines

Though IP SLAs multiple operations scheduling functionality helps in scheduling thousands of operations, you should be cautious while specifying the number of operations, the schedule period, and the operation group frequency to avoid any significant CPU impact.

For example, consider a scenario where you are scheduling 1 to 780 operations at a schedule period of 60 seconds. The command would be as follows:

ip sla monitor group schedule 2 1-780 schedule-period 60 start-time now

IP SLAs calculates how many operations it should start in each 1-second interval by dividing the number of operations by the schedule period (780 operations divided by 60 seconds, which is 13 operations per second). Operations 1 to 13 in operation group 2 start after 0 seconds, operations 14 to 26 start after 1 second, operations 27 to 40 start after 2 seconds, and the iteration continues until operations 768 to 780 start after 59 seconds. This high value of operations starting at every 1-second interval (especially for jitter operations) can load the CPU to very high values.

On a Cisco 2600 router, the maximum recommended value of operations per second is 6 or 7 (approximately 350 to 400 operations per minute). Exceeding this value of 6 or 7 operations per second could cause major performance (CPU) impact. Note that the maximum recommended value of operations per second varies from platform to platform.

Note No warning messages will be displayed if IP SLAs multiple operations scheduling leads to a high number of operations starting per second.

When you reboot the router, the IP SLAs multiple operations scheduling functionality schedules the operations in the same order as was done before the reboot. For example, assume the following operation had been scheduled:

ip sla monitor group schedule 2 1-20 schedule-period 40 start-time now

Over a range of 40 seconds, 20 operations have to be started (that is, one operation every 2 seconds). After the system reboot, operation 1 will start at t seconds and operation 2 starts at t+2 seconds, operation 3 starts at t+4 seconds, and so on.

The IP SLAs multiple operations scheduling functionality schedules the maximum number of operations possible without aborting. However, this functionality skips those IP SLAs operations that are already running or those that are not configured and hence do not exist. The total number of operations will be calculated based on the number of operations specified in the command, irrespective of the number of operations that are missing or already running. The IP SLAs multiple operations scheduling functionality displays a message showing the number of active and missing operations. However, these messages are displayed only if you schedule operations that are not configured or are already running.

IP SLAs Random Scheduler

The IP SLAs random scheduler option provides the capability to schedule multiple IP SLAs operations to begin at random intervals over a specified duration of time. The random scheduler option is disabled by default. To enable the random scheduler option, you must configure the frequency range random-frequency-range keywords and argument. The group of operations restarts at uniformly distributed random frequencies within the specified frequency range. The following guidelines apply for setting the frequency range:

•The starting value of the frequency range should be greater than the timeout values of all the operations in the group operation.

•The starting value of the frequency range should be greater than the schedule period (amount of time for which the group operation is scheduled). This guideline ensures that the same operation does not get scheduled more than once within the schedule period.

The following guidelines apply if the random scheduler option is enabled:

•The individual operations in a group operation will be uniformly distributed to begin at random intervals over the schedule period.

•The group of operations restarts at uniformly distributed random frequencies within the specified frequency range.

•The minimum time interval between the start of each operation in a group operation is 100 milliseconds (0.1 seconds). If the random scheduler option is disabled, the minimum time interval is 1 second.

•Only one operation can be scheduled to begin at any given time. If the random scheduler option is disabled, multiple operations can begin at the same time.

•The first operation will always begin at 0 milliseconds of the schedule period.

•The order in which each operation in a group operation begins is random.

Examples

The following example shows how to schedule IP SLAs operations 3, 4, and 6 to 10 as a group (identified as group 1). In this example, the operations are scheduled to begin at equal intervals over a schedule period of 20 seconds. The first operation (or set of operations) is scheduled to start immediately. Since the frequency is not specified, it is set to the value of the schedule period (20 seconds) by default.

ip sla monitor group schedule 1 3, 4, 6-10 schedule-period 20 start-time now

The following example shows how to schedule IP SLAs operations 1 to 3 as a group (identified as group 2). In this example, the operations are scheduled to begin at random intervals over a schedule period of 50 seconds. The first operation is scheduled to start immediately. The random scheduler option is enabled and the frequency at which the group of operations will restart will be chosen randomly within the range of 80-100 seconds.

ip sla monitor group schedule 2 1-3 schedule-period 50 frequency range 80-100 start-time 
now

Related Commands

ip sla monitor key-chain

Note Effective with Cisco IOS Release 12.4(4)T, 12.2(33)SB, and 12.2(33)SXI, the ip sla monitor key-chain command is replaced by the ip sla key-chain command. See the ip sla key-chain command for more information.

To enable Cisco IOS IP Service Level Agreements (SLAs) control message authentication and specify an MD5 key chain, use the ip sla monitor key-chain command in global configuration mode. To remove control message authentication, use the no form of this command.

ip sla monitor key-chain name

no ip sla monitor key-chain

Syntax Description

Defaults

Control message authentication is disabled.

Command Modes

Global configuration

Command History

Usage Guidelines

The authentication configuration on the IP SLAs source and IP SLAs Responder devices must be the same. In other words, both devices must be configured with the same key chain or both devices must not use authentication.

If the ip sla monitor key-chain command is entered, at least one key must be added to the specified MD5 key chain in order for MD5 authentication to occur.

Examples

In the following example, the IP SLAs control message uses MD5 authentication, and the key chain name is CSAA. The authentication string for key 1 is csaakey1.

ip sla monitor key-chain csaa

key chain csaa

key 1

key-string csaakey1

Related Commands

ip sla monitor logging traps

Note Effective with Cisco IOS Release 12.4(4)T, 12.2(33)SB, and 12.2(33)SXI, the ip sla monitor logging traps command is replaced by the ip sla logging traps command. See the ip sla logging traps command for more information.

To enable the generation of Simple Network Management Protocol (SNMP) system logging messages specific to Cisco IOS IP Service Level Agreements (SLAs) trap notifications, use the ip sla monitor logging traps command in global configuration mode. To disable IP SLAs system logging SNMP traps, use the no form of this command.

ip sla monitor logging traps

no ip sla monitor logging traps

Syntax Description

This command has no arguments or keywords.

Defaults

SNMP system logging messages specific to IP SLAs trap notifications are not generated.

Command Modes

Global configuration

Command History

Usage Guidelines

SNMP trap notifications for IP SLAs can be configured as a triggered action, to be sent when monitored values exceed an upper threshold or fall below a lower threshold, or when a set of defined conditions are met. For example, an SNMP trap can be triggered by five consecutive timeouts during an IP SLAs operation. The sending of SNMP traps is one of the options for triggered actions that can be configured for IP SLAs threshold violations. To configure proactive threshold monitoring parameters for an IP SLAs operation, use the ip sla monitor reaction-configuration command in global configuration mode.

SNMP traps for IP SLAs are supported by the CISCO-RTTMON-MIB and CISCO-SYSLOG-MIB. Use the snmp-server enable traps rtr command to enable the sending of IP SLAs SNMP trap notifications.

Examples

The following example shows the configuration of IP SLAs traps to be triggered for round-trip time (RTT) violations and Voice over IP (VoIP) mean opinion score (MOS) violations, and the necessary SNMP configuration for enabling these SNMP logging traps:

ip sla monitor 1

type jitter dest-ipaddr 209.165.200.225 dest-port 9234

!

ip sla monitor schedule 1 start now life forever

ip sla monitor reaction-configuration 1 react rtt threshold-type immediate threshold-value 
3000 2000 action-type trapOnly

ip sla monitor reaction-configuration 1 react MOS threshold-type consecutive 4 
threshold-value 390 220 action-type trapOnly

!

ip sla monitor logging traps

snmp-server enable traps rtr

Related Commands

ip sla monitor low-memory

Note Effective with Cisco IOS Release 12.4(4)T, 12.2(33)SB, and 12.2(33)SXI, the ip sla monitor low-memory command is replaced by the ip sla low-memory command. See the ip sla low-memory command for more information.

To specify how much unused memory must be available to allow Cisco IOS IP Service Level Agreements (SLAs) configuration, use the ip sla monitor low-memory command in global configuration mode. To remove the type configuration for the operation, use the no form of this command.

ip sla monitor low-memory bytes

no ip sla monitor low-memory

Syntax Description

Defaults

The default amount of memory is 25 percent of the memory available on the system.

Command Modes

Global configuration

Command History

Usage Guidelines

The ip sla monitor low-memory command allows you to specify the amount of memory that the IP SLAs can use. If the amount of available free memory falls below the value specified in the ip sla monitor low-memory command, then the IP SLAs will not allow new operations to be configured. If this command is not used, the default low-memory value is 25 percent. This means that if 75 percent of system memory has been utilized you will not be able to configure any IP SLAs characteristics.

The value of the ip sla monitor low-memory command should not exceed the amount of free memory available on the system. To determine the amount of free memory available on the system, use the show memory user EXEC or privileged EXEC command.

Examples

In the following example, the router is configured so that no less than 2 MB of memory will be free for IP SLAs configuration:

ip sla monitor low-memory 2097152

Related Commands

ip sla monitor reaction-configuration

Note Effective with Cisco IOS Release 12.4(4)T, 12.2(33)SB, and 12.2(33)SXI, the ip sla monitor reaction-configuration command is replaced by the ip sla reaction-configuration command. See the ip sla reaction-configuration command for more information.

To configure proactive threshold monitoring parameters for a Cisco IOS IP Service Level Agreements (SLAs) operation, use the ip sla monitor reaction-configuration command in global configuration mode. To clear all threshold monitoring configuration for a specified IP SLAs operation, use the no form of this command.

ip sla monitor reaction-configuration operation-number react monitored-element [action-type option] [threshold-type {average [number-of-measurements] | consecutive [occurrences] | immediate | never | xofy [x-value y-value]}] [threshold-value upper-threshold lower-threshold]

no ip sla monitor reaction-configuration operation-number

Syntax Description

Defaults

IP SLAs proactive threshold monitoring is disabled.

Note See Table 11 in the "Usage Guidelines" section for a list of the default upper and lower thresholds for specific monitored elements.

Command Modes

Global configuration

Command History

Usage Guidelines

You can configure the ip sla monitor reaction-configuration command multiple times to enable proactive threshold monitoring for multiple elements (for example, configuring thresholds for destination-to-source packet loss and MOS) for the same operation. However, disabling of individual monitored elements is not supported. In other words, the no ip sla monitor reaction-configuration command will disable all proactive threshold monitoring configuration for the specified IP SLAs operation.

SNMP traps for IP SLAs are supported by the CISCO-RTTMON-MIB and CISCO-SYSLOG-MIB. Use the ip sla monitor logging traps command to enable the generation of SNMP system logging messages specific to IP SLAs trap notifications. Use the snmp-server enable traps rtr command to enable the sending of IP SLAs SNMP trap notifications.

To display the current threshold monitoring configuration settings for an IP SLAs operation, use the show ip sla monitor configuration command.

Table 11 lists the default upper and lower thresholds for specific monitored elements.

Examples

In the following example, IP SLAs operation 10 (a UDP jitter operation) is configured to send an SNMP logging trap when the MOS value exceeds 4.9 (best quality) or falls below 2.5 (poor quality):

ip sla monitor reaction-configuration 10 react mos threshold-type immediate 
threshold-value 490 250 action-type trapOnly

Related Commands

ip sla monitor reaction-trigger

Note Effective with Cisco IOS Release 12.4(4)T, 12.2(33)SB, and 12.2(33)SXI, the ip sla monitor reaction-trigger command is replaced by the ip sla reaction-trigger command. See the ip sla reaction-trigger command for more information.

To define a second Cisco IOS IP Service Level Agreements (SLAs) operation to make the transition from a pending state to an active state when one of the trigger action type options are defined with the ip sla monitor reaction-configuration command, use the ip sla monitor reaction-trigger command in global configuration mode. To remove the trigger combination, use the no form of this command.

ip sla monitor reaction-trigger operation-number target-operation

no ip sla monitor reaction-trigger operation

Syntax Description

Defaults

No trigger combination is defined.

Command Modes

Global configuration

Command History

Usage Guidelines

Triggers are usually used for diagnostics purposes and are not intended for use during normal operation conditions.

Examples

In the following example, a trigger action type is defined for IP SLAs operation 2. When operation 2 experiences certain user-specified threshold violation events while it is actively collecting statistical information, the operation state of IP SLAs operation 1 will be triggered to change from pending to active.

ip sla monitor reaction-trigger 2 1

Related Commands

ip sla monitor reset

Note Effective with Cisco IOS Release 12.4(4)T, 12.2(33)SB, and 12.2(33)SXI, the ip sla monitor reset command is replaced by the ip sla reset command. See the ip sla reset command for more information.

To perform a shutdown and restart of the Cisco IOS IP Service Level Agreements (SLAs) engine, use the ip sla monitor reset command in global configuration mode.

ip sla monitor reset

Syntax Description

This command has no arguments or keywords.

Defaults

None

Command Modes

Global configuration

Command History

Usage Guidelines

The ip sla monitor reset command stops all operations, clears IP SLAs configuration information, and returns the IP SLAs feature to the startup condition. This command does not reread the IP SLAs configuration stored in the startup configuration in NVRAM. You must retype the configuration or load a previously saved configuration file.

Note The ip sla monitor reset command does not remove IP SLAs label switched path (LSP) Health Monitor configurations from the running configuration.

Note Use the ip sla monitor reset command only in extreme situations such as the incorrect configuration of a number of operations.

Examples

The following example shows how to reset the Cisco IOS IP SLAs engine, clearing all stored IP SLAs information and configuration:

ip sla monitor reset

Related Commands

ip sla monitor responder

Note Effective with Cisco IOS Release 12.4(4)T, 12.2(33)SB, and 12.2(33)SXI, the ip sla monitor responder command is replaced by the ip sla responder command. See the ip sla responder command for more information.

To enable the Cisco IOS IP Service Level Agreements (SLAs) Responder for general IP SLAs operations, use the ip sla monitor responder command in global configuration mode. To disable the IP SLAs Responder, use the no form of this command.

ip sla monitor responder

no ip sla monitor responder

Syntax Description

This command has no arguments or keywords.

Defaults

The IP SLAs Responder is disabled.

Command Modes

Global configuration

Command History

Usage Guidelines

This command is used on the destination device for IP SLAs operations to enable the sending and receiving of IP SLAs control packets. Enabling the IP SLAs Responder allows the generation of packet loss statistics on the device sending IP SLAs operations.

Prior to sending an operation packet to the IP SLAs Responder, the IP SLAs operation sends a control message to the IP SLAs Responder to enable the destination port.

Examples

The following example shows how to enable the IP SLAs Responder:

ip sla monitor responder

Related Commands

ip sla monitor responder type tcpConnect ipaddress

Note Effective with Cisco IOS Release 12.4(4)T, 12.2(33)SB, and 12.2(33)SXI, the ip sla monitor responder type tcpConnect ipaddress command is replaced by the ip sla responder tcp-connect ipaddress command. See the ip sla responder tcp-connect ipaddress command for more information.

To enable the Cisco IOS IP Service Level Agreements (SLAs) Responder for TCP Connect operations, use the ip sla monitor responder type tcpConnect ipaddress command in global configuration mode. To disable the IP SLAs Responder, use the no form of this command.

ip sla monitor responder type tcpConnect ipaddress ip-address port port-number

no ip sla monitor responder type tcpConnect ipaddress ip-address port port-number

Syntax Description

Defaults

The IP SLAs Responder is disabled.

Command Modes

Global configuration

Command History

Usage Guidelines

This command is used on the destination device for IP SLAs operations to enable the acceptance and return of TCP connection operation packets.

Examples

The following example shows how to enable the IP SLAs Responder for TCP connection operations:

ip sla monitor responder type tcpConnect ipaddress A.B.C.D port 1

Related Commands

ip sla monitor responder type udpEcho ipaddress

Note Effective with Cisco IOS Release 12.4(4)T, 12.2(33)SB, and 12.2(33)SXI, the ip sla monitor responder type udpEcho ipaddress command is replaced by the ip sla responder udp-echo ipaddress command. See the ip sla responder udp-echo ipaddress command for more information.

To enable the Cisco IOS IP Service Level Agreements (SLAs) Responder for User Datagram Protocol (UDP) echo or jitter operations, use the ip sla monitor responder type udpEcho ipaddress command in global configuration mode. To disable the IP SLAs Responder, use the no form of this command.

ip sla monitor responder type udpEcho ipaddress ip-address port port-number

no ip sla monitor responder type udpEcho ipaddress ip-address port port-number

Syntax Description

Defaults

The IP SLAs Responder is disabled.

Command Modes

Global configuration

Command History

Usage Guidelines

This command is used on the destination device for IP SLAs operations to enable UDP echo and jitter (UDP+) operations with control disabled.

Examples

The following example shows how to enable the IP SLAs Responder for jitter operations:

ip sla monitor responder type udpEcho ipaddress A.B.C.D port 1

Related Commands

ip sla monitor restart

Note Effective with Cisco IOS Release 12.4(4)T, 12.2(33)SB, and 12.2(33)SXI, the ip sla monitor restart command is replaced by the ip sla restart command. See the ip sla restart command for more information.

To restart a Cisco IOS IP Service Level Agreements (SLAs) operation, use the ip sla monitor restart command in global configuration mode.

ip sla monitor restart operation-number

Syntax Description

Defaults

None

Command Modes

Global configuration

Command History

Usage Guidelines

To restart an operation, the operation should be in an active state.

IP SLAs allows a maximum of 2000 operations.

This command does not have a no form.

Examples

The following example shows how to restart operation 12:

ip sla monitor restart 12

Related Commands

ip sla monitor schedule

Note Effective with Cisco IOS Release 12.4(4)T, 12.2(33)SB, and 12.2(33)SXI, the ip sla monitor schedule command is replaced by the ip sla schedule command. See the ip sla schedule command for more information.

To configure the scheduling parameters for a single Cisco IOS IP Service Level Agreements (SLAs) operation, use the ip sla monitor schedule command in global configuration mode. To stop the operation and place it in the default state (pending), use the no form of this command.

ip sla monitor schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring]

no ip sla monitor schedule operation-number

Syntax Description

Defaults

The operation is placed in a pending state (that is, the operation is enabled but not actively collecting information).

Command Modes

Global configuration

Command History

Usage Guidelines

After you schedule the operation with the ip sla monitor schedule command, you cannot change the configuration of the operation. To change the configuration of the operation, use the no form of the ip sla monitor global configuration command and reenter the configuration information.

If the operation is in a pending state, you can define the conditions under which the operation makes the transition from pending to active with the ip sla monitor reaction-trigger and ip sla monitor reaction-configuration global configuration commands. When the operation is in an active state, it immediately begins collecting information.

The following time line shows the age-out process of the operation:

W----------------------X----------------------Y----------------------Z

where:

•W is the time the operation was configured with the ip sla monitor global configuration command.

•X is the start time or start of life of the operation (that is, when the operation became "active").

•Y is the end of life as configured with the ip sla monitor schedule global configuration command (life seconds have counted down to zero).

•Z is the age out of the operation.

Age out starts counting down at W and Y, is suspended between X and Y, and is reset to its configured size at Y.

The operation to can age out before it executes (that is, Z can occur before X). To ensure that this does not happen, configure the difference between the operation's configuration time and start time (X and W) to be less than the age-out seconds.

Note The total RAM required to hold the history and statistics tables is allocated at the time of scheduling the IP SLAs operation. This prevents router memory problems when the router gets heavily loaded and lowers the amount of overhead an IP SLAs operation causes on a router when it is active.

The recurring keyword is supported only for scheduling single IP SLAs operations. You cannot schedule multiple IP SLAs operations using the ip sla monitor schedule command. The life value for a recurring IP SLAs operation should be less than one day. The ageout value for a recurring operation must be "never" (which is specified with the value 0), or the sum of the life and ageout values must be more than one day. If the recurring option is not specified, the operations are started in the existing normal scheduling mode.

Examples

In the following example, operation 25 begins actively collecting data at 3:00 p.m. on April 5. This operation will age out after 12 hours of inactivity, which can be before it starts or after it has finished with its life. When this operation ages out, all configuration information for the operation is removed (that is, the configuration information is no longer in the running configuration in RAM).

ip sla monitor schedule 25 life 43200 start-time 15:00 apr 5 ageout 43200

In the following example, operation 1 begins collecting data after a 5-minute delay:

ip sla monitor schedule 1 start-time after 00:05:00

In the following example, operation 3 begins collecting data immediately and is scheduled to run indefinitely:

ip sla monitor schedule 3 start-time now life forever

In the following example, operation 15 begins automatically collecting data every day at 1:30 a.m.:

ip sla monitor schedule 15 start-time 01:30:00 recurring

Related Commands

ip sla reaction-configuration

To configure proactive threshold monitoring parameters for a Cisco IOS IP Service Level Agreements (SLAs) operation, use the ip sla reaction-configuration command in global configuration mode. To disable all the threshold monitoring configuration for a specified IP SLAs operation, use the no form of this command.

ip sla reaction-configuration operation-number [react monitored-element [action-type option] [threshold-type {average [number-of-measurements] | consecutive [occurrences] | immediate | never | xofy [x-value y-value]}] [threshold-value upper-threshold lower-threshold]]

no ip sla reaction-configuration operation-number [react monitored-element]

Syntax Description

Command Default

IP SLAs proactive threshold monitoring is disabled.

Command Modes

Global configuration (config)

Command History