Configuring Cisco IOS IP SLAs for Metro-Ethernet

First Published: February 27, 2007
Last Updated: February 14, 2011

This module describes how to configure an IP Service Level Agreements (SLAs) for Metro-Ethernet to gather network performance metrics in service-provider Ethernet networks. Available statistical measurements for the IP SLAs Ethernet operation include round-trip time, jitter (interpacket delay variance), and packet loss.

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Cisco IOS IP SLAs for Metro-Ethernet" section.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Contents

•Prerequisites for Cisco IOS IP SLAs for Metro-Ethernet

•Restrictions for Cisco IOS IP SLAs for Metro-Ethernet

•Information About Cisco IOS IP SLAs for Metro-Ethernet

•How to Configure Cisco IOS IP SLAs for Metro-Ethernet

•Configuration Examples Cisco IOS IP SLAs for Metro-Ethernet

•Additional References

•Feature Information for Cisco IOS IP SLAs for Metro-Ethernet

Prerequisites for Cisco IOS IP SLAs for Metro-Ethernet

It is recommended that the IEEE 802.1ag standard is supported on the destination devices in order to obtain complete error reporting and diagnostics information.

Restrictions for Cisco IOS IP SLAs for Metro-Ethernet

Memory and performance may be impacted for a given Ethernet CFM maintenance domain and Ethernet Virtual Circuit (EVC) or VLAN that has a large number of maintenance endpoints (MEPs).

Information About Cisco IOS IP SLAs for Metro-Ethernet

•IP SLAs Ethernet Operation Basics

IP SLAs Ethernet Operation Basics

The IP SLAs for Metro-Ethernet integrates Cisco IOS IP SLAs with the Ethernet Connectivity Fault Management (CFM) feature. Ethernet CFM is an end-to-end per-service-instance Ethernet-layer operation, administration, and management (OAM) protocol. See the "Configuring Ethernet Connectivity Fault Management in a Service Provider Network" chapter of the Cisco IOS Carrier Ethernet Configuration Guide for more information.

The IP SLAs for Metro-Ethernet feature provides the capability to gather statistical measurements by sending and receiving Ethernet data frames between Ethernet CFM maintenance endpoints (MEPs). The performance metrics for IP SLAs Ethernet operations are measured between a source MEP and a destination MEP. Unlike existing IP SLAs operations that provide performance metrics for the IP layer, the IP SLAs Ethernet operation provides performance metrics for Layer 2.

IP SLAs Ethernet operations may be configured using the command-line interface (CLI) or Simple Network Management Protocol (SNMP).

You can manually configure individual Ethernet ping or Ethernet jitter operations by specifying the destination MEP identification number, name of the maintenance domain, and EVC or VLAN identifier or port level option.

You also have the option to configure an IP SLAs auto Ethernet operation (ping or jitter) that will query the Ethernet CFM database for all maintenance endpoints in a given maintenance domain and EVC or VLAN. When an IP SLAs auto Ethernet operation is configured, individual Ethernet ping or Ethernet jitter operations are automatically created based on the MEPs that were discovered. A notification mechanism exists between the IP SLAs and Ethernet CFM subsystems to facilitate the automatic creation of Ethernet ping or Ethernet jitter operations for applicable MEPs that are added to a given maintenance domain and EVC or VLAN while an auto Ethernet operation is running.

The IP SLAs for Metro-Ethernet feature supports multioperation scheduling of IP SLAs operations and proactive threshold violation monitoring through SNMP trap notifications and syslog messages.

Statistics Measured by the IP SLAs Ethernet Operation

The network performance metrics supported by the IP SLAs Ethernet operation is similar to the metrics supported by existing IP SLAs operations. The statistical measurements supported by the IP SLAs Ethernet jitter operation include the following:

•Jitter (source-to-destination and destination-to-source)

•Round-trip time latency

•Unprocessed packets

•Packet loss (source-to-destination and destination-to-source)

•Out-of-sequence, tail-dropped, and late packets

How to Configure Cisco IOS IP SLAs for Metro-Ethernet

Note There is no need to configure an IP SLAs responder on the destination device.

•Configuring an IP SLAs Auto Ethernet Operation with Endpoint Discovery on the Source Device (required)

•Manually Configuring an IP SLAs Ethernet Ping or Jitter Operation on the Source Device (optional)

•Scheduling IP SLAs Operations (required)

Configuring an IP SLAs Auto Ethernet Operation with Endpoint Discovery on the Source Device

SUMMARY STEPS

1. enable

2. configure terminal

3. ip sla ethernet-monitor operation-number

For Echo operations only:

4. type echo domain domain-name {evc evc-id | vlan vlan-id} [exclude-mpids mp-ids]
or

For Jitter operations only:

5. type jitter domain domain-name {evc evc-id | vlan vlan-id} [exclude-mpids mp-ids] [interval interframe-interval] [num-frames frames-number]

6. cos cos-value

7. owner owner-id

8. request-data-size bytes

9. tag text

10. threshold milliseconds

11. timeout milliseconds

12. end

13. show ip sla ethernet-monitor configuration [operation-number]

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

ip sla ethernet-monitor operation-number

Example:

Router(config)# ip sla ethernet-monitor 1

Begins configuration for an IP SLAs auto Ethernet operation and enters IP SLA Ethernet monitor configuration mode.

Step 4 

type echo domain domain-name {evc evc-id | vlan vlan-id} [exclude-mpids mp-ids]

Example:

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

For Echo operations only:

Configures an auto Ethernet operation for Ethernet ping operations.

Step 5 

type jitter domain domain-name {evc evc-id | vlan vlan-id} [exclude-mpids mp-ids] [interval interframe-interval] [num-frames frames-number]

Example:

Router(config-ip-sla-ethernet-monitor)# type jitter domain testdomain evc testevc interval 20 num-frames 30

For Jitter operations only:

Configures an auto Ethernet operation for Ethernet jitter operations.

Step 6 

cos cos-value

Example:

Router(config-ip-sla-ethernet-params)# cos 2

(Optional) Sets the class of service for an IP SLAs Ethernet operation.

Step 7 

owner owner-id

Example:

Router(config-ip-sla-ethernet-params)# owner admin

(Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation.

Step 8 

request-data-size bytes

Example:

Router(config-ip-sla-ethernet-params)# request-data-size 64

(Optional) Sets the padding size for the data frame of an IP SLAs Ethernet operation.

•The default value for IP SLAs Ethernet ping operations is 66 bytes.

•The default value for IP SLAs Ethernet jitter operations is 51 bytes.

Step 9 

tag text

Example:

Router(config-ip-sla-ethernet-params)# tag TelnetPollSever1

(Optional) Creates a user-specified identifier for an IP SLAs operation.

Step 10 

threshold milliseconds

Example:

Router(config-ip-sla-ethernet-params)# threshold 10000

(Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation.

Step 11 

timeout milliseconds

Example:

Router(config-ip-sla-ethernet-params)# timeout 10000

(Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet.

Step 12 

end

Example:

Router(config-ip-sla-ethernet-params)# end

Exits to privileged EXEC configuration mode.

Step 13 

show ip sla ethernet-monitor configuration [operation-number]

Example:

Router# show ip sla ethernet-monitor configuration 1

(Optional) Displays configuration settings for all IP SLAs auto Ethernet operations or a specified auto Ethernet operation.

Manually Configuring an IP SLAs Ethernet Ping or Jitter Operation on the Source Device

SUMMARY STEPS

1. enable

2. configure terminal

3. ip sla operation-number

For Ethernet ping operations only:

4. ethernet echo mpid mp-id domain domain-name {evc evc-id | port | vlan vlan-id}

For Ethernet jitter operations only:

5. ethernet jitter mpid mp-id domain domain-name {evc evc-id | port | vlan vlan-id} [interval interframe-interval] [num-frames frames-number]

6. cos cos-value

7. frequency seconds

8. history history-parameter

9. owner owner-id

10. request-data-size bytes

11. tag text

12. threshold milliseconds

13. timeout milliseconds

14. exit

15. show ip sla configuration [operation-number]

16. show ip sla application

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

ip sla operation-number

Example:

Router(config)# ip sla 1

Begins configuration for an IP SLAs operation and enters IP SLA configuration mode.

Step 4 

ethernet echo mpid mp-id domain domain-name {evc evc-id | port | vlan vlan-id}

Example:

Router(config-ip-sla)# ethernet echo mpid 23 domain testdomain vlan 34

For a ping operation only:

Configures the IP SLAs operation as an Ethernet ping operation and enters Ethernet echo configuration mode.

Step 5 

ethernet jitter mpid mp-id domain domain-name {evc evc-id | port | vlan vlan-id} [interval interframe-interval] [num-frames frames-number]

Example:

Router(config-ip-sla)# ethernet jitter mpid 23 domain testdomain evc testevc interval 20 num-frames 30

For a jitter operation only:

Configures the IP SLAs operation as an Ethernet jitter operation and enters Ethernet jitter configuration mode.

Step 6 

cos cos-value

Example:

Router(config-ip-sla-ethernet-echo)# cos 2

(Optional) Sets the class of service for an IP SLAs Ethernet operation.

Note For this and the remaining steps, the configuration mode shown in the example is for the Ethernet echo operation. However, the commands are the same in the Ethernet jitter configuration mode.

Step 7 

frequency seconds

Example:

Router(config-ip-sla-ethernet-echo)# frequency 30

(Optional) Sets the rate at which a specified IP SLAs operation repeats.

Step 8 

history history-parameter

Example:

Router(config-ip-sla-ethernet-echo)# history hours-of-statistics-kept 3

(Optional) Specifies the parameters used for gathering statistical history information for an IP SLAs operation.

Step 9 

owner owner-id

Example:

Router(config-ip-sla-ethernet-echo)# owner admin

(Optional) Configures the Simple Network Management Protocol (SNMP) owner of an IP SLAs operation.

Step 10 

request-data-size bytes

Example:

Router(config-ip-sla-ethernet-echo)# request-data-size 64

(Optional) Sets the padding size for the data frame of an IP SLAs Ethernet operation.

The default value for IP SLAs Ethernet ping operations is 66 bytes. The default value for IP SLAs Ethernet jitter operations is 51 bytes.

Step 11 

tag text

Example:

Router(config-ip-sla-ethernet-echo)# tag TelnetPollSever1

(Optional) Creates a user-specified identifier for an IP SLAs operation.

Step 12 

threshold milliseconds

Example:

Router(config-ip-sla-ethernet-echo)# threshold 10000

(Optional) Sets the upper threshold value for calculating network monitoring statistics created by an IP SLAs operation.

Step 13 

timeout milliseconds

Example:

Router(config-ip-sla-ethernet-echo)# timeout 10000

(Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet.

Step 14 

end

Example:

Router(config-ip-sla-ethernet-echo)# end

Exits to privileged EXEC mode.

Step 15 

show ip sla configuration [operation-number]

Example:

Router# show ip sla configuration 1

(Optional) Displays configuration values including all defaults for all IP SLAs operations or a specified operation.

Step 16 

show ip sla application

Example:

Router# show ip sla application

(Optional) Displays global information about supported IP SLAs features.

Scheduling IP SLAs Operations

Restrictions

•All IP SLAs operations to be scheduled must be already configured.

•The frequency of all operations scheduled in an operation group must be the same unless you are enabling the random scheduler option for a multioperation scheduler.

SUMMARY STEPS

1. enable

2. configure terminal

For individual auto Ethernet operations only:

3. 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}]

For individual IP SLAs operations only:

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

For multioperations scheduler only:

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

6. exit

7. show ip sla group schedule

8. show ip sla configuration

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

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

Example:

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

For individual auto Ethernet operations only:

Configures scheduling parameters for an IP SLAs auto Ethernet operation.

Step 4 

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

Example:

Router(config)# ip sla schedule 1 start-time now life forever

For individual IP SLAs operations only:

Configures the scheduling parameters for an individual IP SLAs operation.

Step 5  

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

Router(config)# ip sla group schedule 1 3,4,6-9

For mulioperation scheduler only:

Specifies an IP SLAs operation group number and the range of operation numbers to be scheduled in global configuration mode.

Step 6 

exit

Example:

Router(config)# exit

Exits to the privileged EXEC mode.

Step 7 

show ip sla group schedule

Example: 
Router# show ip sla group schedule

(Optional) Displays the IP SLAs group schedule details.

Step 8  

show ip sla configuration
Example: 
Router# show ip sla configuration

(Optional) Displays the IP SLAs configuration details.

Troubleshooting Tips

Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an individual IP SLAs Ethernet ping or Ethernet jitter operation. Use the debug ip sla ethernet-monitor command to help troubleshoot issues with an IP SLAs auto Ethernet operation.

What to Do Next

To add proactive threshold conditions and reactive triggering for generating traps, or for starting another operation, to an IP SLAs operation, see Configuring Proactive Threshold Monitoring.

To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable

Configuration Examples Cisco IOS IP SLAs for Metro-Ethernet

•Example: IP SLAs Auto Ethernet Operation with Endpoint Discovery

•Example: Individual IP SLAs Ethernet Ping Operation

Example: IP SLAs Auto Ethernet Operation with Endpoint Discovery

The following examples shows the operation parameters, proactive threshold monitoring, and scheduling options for an IP SLAs auto Ethernet operation. In Configuration A, 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. In Configuration B, operation 20 is configured to automatically create IP SLAs Ethernet ping operations for all the discovered maintenance endpoints in the domain named testdomain and EVC identified as testevc. In both configurations, the proactive threshold monitoring configuration specifies that when three consecutive connection loss events occur, an SNMP trap notification should be sent. The schedule period for operation 10 and operation 20 is 60 seconds, and both operations are scheduled to start immediately.

Configuration A 

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

Configuration B 

ip sla ethernet-monitor 20

 type echo domain testdomain evc testevc

!

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

!

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

Example: Individual IP SLAs Ethernet Ping Operation

The following example show the configuration for an IP SLAs Ethernet ping operation. In Configuration C, the maintenance endpoint identification number is 23, the maintenance domain name is testdomain, and the VLAN identification number is 34. In Configuration D, the maintenance endpoint identification number is 23, the maintenance domain name is testdomain, and the EVC is identified as testevc. In both configurations, the proactive threshold monitoring configuration specifies that when three consecutive connection loss events occur, an SNMP trap notification should be sent. Operation 1 and operation 5 are scheduled to start immediately.

Configuration C 

ip sla 1

 ethernet echo mpid 23 domain testdomain vlan 34

!

ip sla reaction-configuration 1 react connectionLoss threshold-type consecutive 3 
action-type trapOnly

!

ip sla schedule 1 start-time now

Configuration D 

ip sla 5

 ethernet echo mpid 23 domain testdomain evc testevc

!

ip sla reaction-configuration 5 react connectionLoss threshold-type consecutive 3 
action-type trapOnly

!

ip sla schedule 5 start-time now

Additional References

Related Documents

Related Topic
Document Title

Cisco IOS commands

Cisco IOS Master Commands List, All Releases

Cisco IOS IP SLAs commands

Cisco IOS IP SLAs Command Reference

Ethernet CFM

"Configuring Ethernet Connectivity Fault Management in a Service Provider Network" module of the Cisco IOS Carrier Ethernet Configuration Guide

Multioperation scheduling for Cisco IOS IP SLAs

"Configuring a Multiple Operation Scheduler" module of the Cisco IOS IP SLAs Configuration Guide

Proactive threshold monitoring for Cisco IOS IP SLAs

"Configuring Proactive Threshold Monitoring of IP SLAs Operations" module of the Cisco IOS IP SLAs Configuration Guide


Standards

Standard
Title

IEEE 802.1ag

Connectivity Fault Management


MIBs

MIB
MIBs Link

•CISCO-RTTMON-MIB

•CISCO-IPSLA-ETHERNET-MIB

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://www.cisco.com/go/mibs


RFCs

RFC
Title

No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.

—


Technical Assistance

Description
Link

The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password.

http://www.cisco.com/cisco/web/support/index.html


Feature Information for Cisco IOS IP SLAs for Metro-Ethernet

Table 1 ists the features in this module and provides links to specific configuration information.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Note Table 1 lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature..

Table 1 Feature Information for Cisco IOS IP SLAs for Metro-Ethernet 

Feature Name
Releases
Feature Information

IP SLAs for Metro-Ethernet

12.2(33)SB
12.2(33)SRB
12.2(33)SXI
12.4(20)T
15.0(1)S

The IP Service Level Agreements (SLAs) for Metro-Ethernet feature provides the capability to gather Ethernet-layer network performance metrics. Available statistical measurements for the IP SLAs Ethernet operation include round-trip time, jitter (interpacket delay variance), and packet loss.

IP SLAs Metro-Ethernet 2.0 (EVC)

12.2(33)SRD
15.0(1)S
12.2(50)SY

Support for Ethernet Virtual Circuits (EVCs) was added.

In Cisco IOS Release 12.2(50)SY, support of IP SLAs Metro-Ethernet 2.0 (EVC) was added.

The following sections provide information about this feature:

•IP SLAs Ethernet Operation Basics

•How to Configure Cisco IOS IP SLAs for Metro-Ethernet

IP SLAs Metro-Ethernet 3.0 (CFM d8.1)

12.2(33)SRE
15.0(1)S

Support for port level statistical measurements was added.

The following sections provide information about this feature:

•IP SLAs Ethernet Operation Basics

•How to Configure Cisco IOS IP SLAs for Metro-Ethernet

IEEE 802.1ag - D8.1 standard Compliant CFM, IP SLA for Ethernet

15.1(1)T

Support for CFM d8.1 replaced support for CFM d1.0. IP SLAs integration with CFM d1.0 continues to be supported in Cisco IOS Release 15.0M and Cisco IOS Release 12.4(20)T.


Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2007-2010 Cisco Systems, Inc. All rights reserved.