Table Of Contents

IP SLAs for Metro-Ethernet

Finding Feature Information

Contents

Prerequisites for the IP SLAs Ethernet Operation

Restrictions for the IP SLAs Ethernet Operation

Information About the IP SLAs Ethernet Operation

Benefits of the IP SLAs Ethernet Operation

Ethernet CFM

IP SLAs Ethernet Operation Basics

How to Configure the IP SLAs Ethernet Operation

Configuring an IP SLAs Ethernet Operation with Endpoint Discovery

Troubleshooting Tips

What to Do Next

Manually Configuring an Individual IP SLAs Ethernet Operation

Troubleshooting Tips

What to Do Next

Configuration Examples for the IP SLAs Ethernet Operation

Configuring an IP SLAs Ethernet Operation with Endpoint Discovery: Examples

Manually Configuring an Individual IP SLAs Ethernet Operation: Examples

Where to Go Next

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Command Reference

Feature Information for the IP SLAs Ethernet Operation

IP SLAs for Metro-Ethernet

---

First Published: February 27, 2007

Last Updated: November 20, 2009

The IP Service Level Agreements (SLAs) for Metro-Ethernet feature provides the capability to gather network performance metrics in service provider Ethernet networks. This feature 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. Available statistical measurements for the IP SLAs Ethernet operation include round-trip time, jitter (interpacket delay variance), and packet loss.

The IP SLAs for Metro-Ethernet feature also allows you to perform multioperation scheduling of IP SLAs operations and supports proactive threshold violation monitoring through Simple Network Management Protocol (SNMP) trap notifications and syslog messages.

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 the IP SLAs Ethernet Operation" section.

Use Cisco Feature Navigator to find information about platform support and Cisco IOS, Catalyst OS, and Cisco IOS XE 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 the IP SLAs Ethernet Operation

•Restrictions for the IP SLAs Ethernet Operation

•Information About the IP SLAs Ethernet Operation

•How to Configure the IP SLAs Ethernet Operation

•Configuration Examples for the IP SLAs Ethernet Operation

•Where to Go Next

•Additional References

•Command Reference

•Feature Information for the IP SLAs Ethernet Operation

Prerequisites for the IP SLAs Ethernet Operation

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.

---

Note The destination devices do not require the IP SLAs Responder to be enabled.

---

Restrictions for the IP SLAs Ethernet Operation

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 the IP SLAs Ethernet Operation

To configure an IP SLAs Ethernet operation, you should understand the following concepts:

•Benefits of the IP SLAs Ethernet Operation

•Ethernet CFM

•IP SLAs Ethernet Operation Basics

Benefits of the IP SLAs Ethernet Operation

•End-to-end connectivity measurements for determining network availability or testing network connectivity in service provider Ethernet networks

•Proactive threshold violation monitoring through SNMP trap notifications and syslog messages

•Reduced network troubleshooting time for service provider Ethernet networks

•Creation of IP SLAs Ethernet ping and Ethernet jitter operations based on network topology

•Discovery of existing maintenance endpoints (MEPs) in a given Ethernet CFM maintenance domain and EVC or VLAN based on the Ethernet CFM database

•Multioperation scheduling of IP SLAs operations

Ethernet CFM

Ethernet CFM is an end-to-end per-service-instance Ethernet-layer operation, administration, and management (OAM) protocol. For more information about this feature, see the documentation for the Ethernet CFM feature. (See the "Related Documents" section for the location of this document.)

IP SLAs Ethernet Operation Basics

---

Note 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 the IP SLAs Ethernet Operation" section.

---

The IP SLAs for Metro-Ethernet feature integrates the IP SLAs software subsystem with the Ethernet CFM software subsystem to provide 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 ping or auto Ethernet jitter operation 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 also allows you to perform multioperation scheduling of IP SLAs operations and supports proactive threshold violation monitoring through SNMP trap notifications and syslog messages. For more information on these topics, see the "Related Documents" section.

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 the IP SLAs Ethernet Operation

This section contains the following tasks:

•Configuring an IP SLAs Ethernet Operation with Endpoint Discovery

•Manually Configuring an Individual IP SLAs Ethernet Operation

Configuring an IP SLAs Ethernet Operation with Endpoint Discovery

Perform this task to configure and schedule an IP SLAs auto Ethernet operation.

SUMMARY STEPS

1. enable

2. configure terminal

3. ip sla ethernet-monitor operation-number

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

5. cos cos-value

6. owner owner-id

7. request-data-size bytes

8. tag text

9. threshold milliseconds

10. timeout milliseconds

11. exit

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

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

14. exit

15. 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] or 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 echo domain testdomain vlan 34 or Example: Router(config-ip-sla-ethernet-monitor)# type jitter domain testdomain evc testevc interval 20 num-frames 30	Configures an auto Ethernet operation to create Ethernet ping operations. or Configures an auto Ethernet operation to create Ethernet jitter operations.
Step 5	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 6	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 7	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 8	tag text Example: Router(config-ip-sla-ethernet-params)# tag TelnetPollSever1	(Optional) Creates a user-specified identifier for an IP SLAs operation.
Step 9	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 10	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 11	exit Example: Router(config-ip-sla-ethernet-params)# exit	Exits IP SLAs auto Ethernet parameters configuration submode and returns to global configuration mode.
Step 12	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] Example: Router(config)# ip sla ethernet-monitor reaction-configuration 10 react connectionLoss threshold-type consecutive 3 action-type trapOnly	Configures proactive threshold monitoring parameters for an IP SLAs auto Ethernet operation.
Step 13	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	Configures scheduling parameters for an IP SLAs auto Ethernet operation.
Step 14	exit Example: Router(config)# exit	(Optional) Exits global configuration mode and returns to privileged EXEC mode.
Step 15	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.

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 display the results of an IP SLAs operation, use the show ip sla statistics and show ip sla statistics aggregated commands. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable.

Manually Configuring an Individual IP SLAs Ethernet Operation

Perform this task to manually configure and schedule an individual IP SLAs Ethernet ping or Ethernet jitter operation.

SUMMARY STEPS

1. enable

2. configure terminal

3. ip sla operation-number

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

5. cos cos-value

6. frequency seconds

7. history history-parameter

8. owner owner-id

9. request-data-size bytes

10. tag text

11. threshold milliseconds

12. timeout milliseconds

13. exit

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

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

16. exit

17. show ip sla configuration [operation-number]

18. 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} or 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 echo mpid 23 domain testdomain vlan 34 or Example: Router(config-ip-sla)# ethernet jitter mpid 23 domain testdomain evc testevc interval 20 num-frames 30	Configures the IP SLAs operation as an Ethernet ping operation and enters Ethernet echo configuration mode. or Configures the IP SLAs operation as an Ethernet jitter operation and enters Ethernet jitter configuration mode.
Step 5	cos cos-value Example: Router(config-ip-sla-ethernet-echo)# cos 2	(Optional) Sets the class of service for an IP SLAs Ethernet operation.
Step 6	frequency seconds Example: Router(config-ip-sla-ethernet-echo)# frequency 30	(Optional) Sets the rate at which a specified IP SLAs operation repeats.
Step 7	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 8	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 9	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 10	tag text Example: Router(config-ip-sla-ethernet-echo)# tag TelnetPollSever1	(Optional) Creates a user-specified identifier for an IP SLAs operation.
Step 11	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 12	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 13	exit Example: Router(config-ip-sla-ethernet-echo)# exit	Exits IP SLAs Ethernet monitor configuration submode and returns to global configuration mode.
Step 14	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] Example: Router(config)# ip sla reaction-configuration 1 react jitterAvg threshold-value 5 2 action-type trap threshold-type immediate	Configures proactive threshold monitoring parameters for an IP SLAs operation.
Step 15	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	Configures the scheduling parameters for an individual IP SLAs operation.
Step 16	exit Example: Router(config)# exit	(Optional) Exits global configuration mode and returns to privileged EXEC mode.
Step 17	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 18	show ip sla application Example: Router# show ip sla application	(Optional) Displays global information about supported IP SLAs features.

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.

What to Do Next

To display the results of an IP SLAs operation use the show ip sla statistics and show ip sla statistics aggregated commands. 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 for the IP SLAs Ethernet Operation

This section provides the following configuration examples:

•Configuring an IP SLAs Ethernet Operation with Endpoint Discovery: Examples

•Manually Configuring an Individual IP SLAs Ethernet Operation: Examples

Configuring an IP SLAs Ethernet Operation with Endpoint Discovery: Examples

The following examples show how to configure operation parameters, proactive threshold monitoring, and scheduling options using 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

Manually Configuring an Individual IP SLAs Ethernet Operation: Examples

The following examples show how to configure 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

Where to Go Next

For information about other types of IP SLAs operations and IP SLAs features, see the Cisco IOS IP SLAs Features Roadmap.

Additional References

The following sections provide references related to the IP SLAs for Metro-Ethernet feature.

Related Documents

Related Topic	Document Title
Ethernet CFM	"Configuring Ethernet Connectivity Fault Management in a Service Provider Network" chapter of the Cisco IOS Carrier Ethernet Configuration Guide
Multioperation scheduling for Cisco IOS IP SLAs	"IP SLAs—Multiple Operation Scheduling" chapter of the Cisco IOS IP SLAs Configuration Guide
Proactive threshold monitoring for Cisco IOS IP SLAs	"IP SLAs—Proactive Threshold Monitoring" chapter of the Cisco IOS IP SLAs Configuration Guide
Cisco IOS IP SLAs command-line interface enhancements	Cisco IOS IP Service Level Agreements Command Line Interface, Cisco white paper
Cisco IOS IP SLAs commands	Cisco IOS IP SLAs Command Reference

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 website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

http://www.cisco.com/techsupport

Command Reference

The following commands are introduced or modified in the feature or features documented in this module. For information about these commands, see the Cisco IOS IP SLA Command Reference at http://www.cisco.com/en/US/docs/ios/ipsla/command/reference/sla_book.html. For information about all Cisco IOS commands, go to the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or to the Cisco IOS Master Commands List at http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html.

•cos

•debug ip sla ethernet-monitor

•ethernet echo mpid

•ethernet jitter mpid

•ip sla ethernet-monitor

•ip sla ethernet-monitor reaction-configuration

•ip sla ethernet-monitor schedule

•request-data-size (Ethernet)

•show ip sla ethernet-monitor configuration

•type echo domain

•type jitter domain

Feature Information for the IP SLAs Ethernet Operation

Table 1 lists the release history for this feature.

Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS, Catalyst OS, and Cisco IOS XE 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 Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.

---

Table 1 Feature Information for the IP SLAs Ethernet Operation 

Feature Name	Releases	Feature Information
IP SLAs for Metro-Ethernet	12.2(33)SRB, 12.2(33)SB, 12.4(20)T, Cisco IOS XE Release 2.1, 12.2(33)SXI	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	Support for Ethernet Virtual Circuits (EVCs) was added. The following sections provide information about this feature: •IP SLAs Ethernet Operation Basics •Configuring an IP SLAs Ethernet Operation with Endpoint Discovery •Manually Configuring an Individual IP SLAs Ethernet Operation •Configuring an IP SLAs Ethernet Operation with Endpoint Discovery: Examples •Manually Configuring an Individual IP SLAs Ethernet Operation: Examples
IP SLAs Metro-Ethernet 3.0 (CFM d8.1)	12.2(33)SRE	Support for port level statistical measurements was added. The following sections provide information about this feature: •IP SLAs Ethernet Operation Basics •Manually Configuring an Individual IP SLAs Ethernet Operation

CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website 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. (0910R)

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-2009 Cisco Systems, Inc. All rights reserved.