Cisco ME 3800x and ME 3600x Switches Software Configuration Guide, Cisco IOS Release 15.4(2)S

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents

Find Matches in This Book

Available Languages

Download Options

Book Title

Cisco ME 3800x and ME 3600x Switches Software Configuration Guide, Cisco IOS Release 15.4(2)S

Chapter Title

Configuring Ethernet OAM, CFM, and E-LMI

PDF - Complete Book (14.22 MB) PDF - This Chapter (437.0 KB)
View with Adobe Reader on a variety of devices

Results

Updated:: April 7, 2021

Chapter: Configuring Ethernet OAM, CFM, and E-LMI

Understanding Ethernet CFM
Configuring Ethernet CFM
Managing and Displaying Ethernet CFM Information
Understanding the Ethernet OAM Protocol
- OAM Features
- OAM Messages
Setting Up and Configuring Ethernet OAM
Displaying Ethernet OAM Protocol Information
Understanding E-LMI
Configuring E-LMI
Displaying E-LMI
Ethernet CFM and Ethernet OAM Interaction
- Enabling Ethernet OAM
- Ethernet OAM and CFM Configuration Example

Configuring Ethernet OAM, CFM, and E-LMI

Last Updated: July 2013

Ethernet Operations, Administration, and Maintenance (OAM) is a protocol for installing, monitoring, and troubleshooting Ethernet networks to increase management capability within the context of the overall Ethernet infrastructure. The Cisco ME 3800X and ME 3600X switch supports IEEE 802.1ag Connectivity Fault Management (CFM), Ethernet Local Management Interface (E-LMI), and IEEE 802.3ah Ethernet OAM discovery, link monitoring, remote fault detection, and remote loopback. It also supports IP Service Level Agreements (SLAs) for CFM.

This chapter provides information about configuring CFM, E-LMI, and the Ethernet OAM protocol.

For complete command and configuration information for Ethernet OAM,CFM, and E-LMI, see the Cisco IOS Carrier Ethernet Configuration Guide.

For complete syntax of the commands used in this chapter, see the command reference for this release and the Cisco IOS Carrier Ethernet Command Reference at this URL:
http://www.cisco.com/en/US/docs/ios-xml/ios/cether/command/ce-cr-book.html

This chapter contains these sections:

Understanding Ethernet CFM

Ethernet CFM is an end-to-end per VLAN Ethernet layer OAM protocol that includes proactive connectivity monitoring, fault verification, and fault isolation. End-to-end can be provider-edge-to-provider-edge (PE-to-PE) device or customer-edge-to-customer-edge (CE-to-CE) device. Ethernet CFM, as specified by IEEE 802.1ag, is the standard for Layer 2 ping, Layer 2 traceroute, and end-to-end connectivity check of the Ethernet network.

The switch does not support:

CFM on VFI interfaces
Provider-edge E-LMI
CFM on SVI based xconnect
CFM on port based xconnect

Note CFM is supported on Ethernet Virtual Circuit-Bridge Domain (EVC BD), EVC xconnect, EFP xconnect and CFM transparencies.

These sections contain conceptual information about Ethernet CFM:

CFM Domain

A CFM maintenance domain is a management space on a network that is owned and operated by a single entity and defined by a set of ports internal to it, but at its boundary. You assign a unique maintenance level (from 0 to 7) to define the hierarchical relationship between domains. The larger the domain, the higher the level. For example, as shown in Figure 48-1, a service-provider domain would be larger than an operator domain and might have a maintenance level of 6, while the operator domain maintenance level is 3 or 4.

As shown in Figure 48-2, domains cannot intersect or overlap because that would require management by more than one entity, which is not allowed. Domains can touch or nest (if the outer domain has a higher maintenance level than the nested domain). Nesting domains is useful when a service provider contracts with one or more operators to provide Ethernet service. Each operator has its own maintenance domain and the service provider domain is a superset of the operator domains. Maintenance levels of nesting domains should be communicated among the administrating organizations. CFM exchanges messages and performs operations on a per-domain basis.

Figure 48-1 CFM Maintenance Domains

Figure 48-2 Allowed Domain Relationships

Maintenance Associations and Maintenance Points

A maintenance association (MA) identifies a service that can be uniquely identified within the maintenance domain. The CFM protocol runs within a maintenance association. A maintenance point is a demarcation point on an interface that participates in CFM within a maintenance domain. Maintenance points drop all lower-level frames and forward all higher-level frames. There are two types of maintenance points:

Maintenance end points (MEPs) are points at the edge of the domain that define the boundaries and confine CFM messages within these boundaries. Outward facing or Down MEPs communicate through the wire side (connected to the port). Inward facing or Up MEPs communicate through the relay function side, not the wire side.

CFM 802.1ag supports up and down per-VLAN MEPs, as well as port MEPs, which are untagged down MEPs that are not associated with a VLAN. Port MEPs are configured to protect a single hop and used to monitor link state through CFM. If a port MEP is not receiving continuity check messages from its peer (static remote MEP), for a specified interval, the port is put into an operational down state in which only CFM and OAM packets pass through, and all other data and control packets are dropped.

– An up MEP sends and receives CFM frames through the relay function. It drops all CFM frames at its level or lower that come from the wire side, except traffic going to the down MEP. For CFM frames from the relay side, it processes the frames at its level and drops frames at a lower level. The MEP transparently forwards all CFM frames at a higher level, regardless of whether they are received from the relay or wire side. If the port on which MEP is configured is blocked by STP, the MEP can still send or receive CFM messages through the relay function. CFM runs at the provider maintenance level (UPE-to-UPE), specifically with up MEPs at the user network interface (UNI).

Note The switch rate-limits all incoming CFM messages at a fixed rate of 500 frames per second.

– A down MEP sends and receives CFM frames through the wire connected to the port on which the MEP is configured. It drops all CFM frames at its level or lower that come from the relay side. For CFM frames from the wire side, it processes all CFM frames at its level and drops CFM frames at lower levels except traffic going to the other lower-level down MEP. The MEP transparently forwards all CFM frames at a higher level, regardless of whether they are received from the relay or through the wire.

Maintenance intermediate points (MIPs) are internal to a domain, not at the boundary, and respond to CFM only when triggered by traceroute and loopback messages. They forward CFM frames received from MEPs and other MIPs, drop all CFM frames at a lower level (unless MIP filtering is enabled), and forward all CFM frames at a higher level and at a lower level and regardless of whether they are received from the relay or wire side. When MIP filtering is enabled, the MIP drops CFM frames at a lower level. MIPs also catalog and forward continuity check messages (CCMs), but do not respond to them.

MIP filtering is disabled by default, and you can configure it to be enabled or disabled. When MIP filtering is disabled, all CFM frames are forwarded.

You can manually configure a MIP or configure the switch to automatically create a MIP. You can configure a MEP without a MIP. In case of a configuration conflict, manually created MIPs take precedence over automatically created MIPs.

If port on which the MEP is configured is blocked by Spanning-Tree Protocol (STP), the MIP can receive and might respond to CFM messages from both the wire and relay side, but cannot forward any CFM messages.

CFM Messages

CFM uses standard Ethernet frames distinguished by EtherType or (for multicast messages) by MAC address. All CFM messages are confined to a maintenance domain and to a service-provider VLAN (S-VLAN). These CFM messages are supported:

Continuity Check (CC) messages—multicast heartbeat messages exchanged periodically between MEPs that allow MEPs to discover other MEPs within a domain and allow MIPs to discover MEPs. CC messages are configured to a domain or VLAN. Enter the continuity-check Ethernet service configuration command to enable CCM.

The default continuity check message (CCM) interval on the switch is 10 seconds. You can set it to be 100 ms, 1 second, 1 minute, or 10 minutes by entering the continuity-check interval Ethernet service mode command. Because faster CCM rates are more CPU intensive, we do not recommend configuring a large number of MEPs running at 100 ms intervals.

Loopback messages—unicast or multicast frames transmitted by a MEP at administrator request to verify connectivity to a particular maintenance point, indicating if a destination is reachable. A loopback message is similar to an Internet Control Message Protocol (ICMP) ping message. Refer to the ping ethernet privileged EXEC command.
Traceroute messages—multicast frames transmitted by a MEP at administrator request to track the path (hop-by-hop) to a destination MEP. Traceroute messages are similar in concept to UDP traceroute messages. Refer to the traceroute ethernet privileged EXEC command.

Crosscheck Function and Static Remote MEPs

The crosscheck function is a timer-driven post-provisioning service verification between dynamically configured MEPs (using crosscheck messages) and expected MEPs (by configuration) for a service. It verifies that all endpoints of a multipoint service are operational. The crosscheck function is performed only one time and is initiated from the command-line interface (CLI).

CFM 802.1ag also supports static remote MEPs or static RMEP check. Unlike the crosscheck function, which is performed only once, configured static RMEP checks run continuously. To configure static RMEP check, enter the continuity-check static rmep Ethernet CFM service mode command.

SNMP Traps and Fault Alarms

The MEPs generate two types of SNMP traps: CC traps and crosscheck traps. Supported CC traps are MEP up, MEP down, cross-connect (a service ID does not match the VLAN), loop, and configuration error. The crosscheck traps are service up, MEP missing (an expected MEP is down), and unknown MEP.

Fault alarms are unsolicited notifications sent to alert the system administrator when CFM detects a fault. You can configure the priority level of alarms that trigger an SNMP trap or syslog message. You can also configure a delay period before a fault alarm is sent and the time before the alarm is reset.

Configuration Error List

CFM configuration errors in CFM 802.1ag can be misconfigurations or extra configuration commands detected during MEP configuration. They can be caused by overlapping maintenance associations. For example, if you create a maintenance association with a VLAN list and a MEP on an interface, a potential leak error could occur if other maintenance associations associated with the same VLAN exist at a higher level without any MEPs configured. You can display the configuration error list, which is informational only, by entering the show ethernet cfm errors configuration privileged EXEC command.

IP SLAs Support for CFM

The switch supports CFM with IP Service Level Agreements (SLAs), which provides the ability to gather Ethernet layer network performance metrics. Available statistical measurements for the IP SLAs CFM operation include round-trip time, jitter (interpacket delay variance), and packet loss. You can schedule multiple IP SLAs operations and use Simple Network Management Protocol (SNMP) trap notifications and syslog messages for proactive threshold violation monitoring.

For more information about IP SLAs, see Chapter46, “Configuring Cisco IOS IP SLAs Operations”

IP SLAs integration with CFM gathers Ethernet layer statistical measurements by sending and receiving Ethernet data frames between CFM MEPs. Performance is measured between the source MEP and the destination MEP. Unlike other IP SLAs operations that provide performance metrics for only the IP layer, IP SLAs with CFM provides performance metrics for Layer 2.

You can manually configure individual Ethernet ping or jitter operations. You can also configure an IP SLAs automatic Ethernet operation that queries the CFM database for all MEPs in a given maintenance domain and VLAN. The operation then automatically creates individual Ethernet ping or jitter operations based on the discovered MEPs.

For more information about IP SLAs operation with CFM, see the IP SLAs for Metro-Ethernet feature module.

CFM on EVC Bridge Domains and EVC Cross-Connect Interfaces

CFM is supported on EVC bridge domains and EVC cross-connect interfaces. EVC interfaces can be used to connect UNI interfaces so that VLAN IDs can be mapped to bridge domains.

CFM is supported on the following types of EVCs:

Default
Tagged
Untagged
Single-dot1q tagged
QinQ

CFM over pseudowires allows service providers to manage access-side, end-to-end connectivity over an MPLS core.

CFM packets can be forwarded over:

SVI Pseudo-wire
VPLS Pseudo-wire
EVC Xconnect Pseudo-wire
Bridge-domain
VLAN

The following CFM features are supported on the Cisco ME3600/ME3800 switches:

CFM transparency on SVI PW / VPLS PW / EVC xconnect PW
CFM Up MEP on EVC Xconnect and Port-Channel EVC Xconnect
CFM Down MEP on EVC BD and Port-Channel EVC Xconnect
CFM Up MEP on EVC BD and Port-Channel EVC Xconnect
MIP support
CFM IEEE MIB (EVC BD, EVC Xconnect)
ELMI PE and CE support
CFM ELMI Interworking
CFM and 802.3ah interworking
SYSLOG
802.3AH SNMP MIB

The following asymmetric configurations are not supported on the Cisco ME3600/ME3800 switches:

efps with 1 tag & no rewrite
efps with 2 tags & pop 1
efps with 2 tags and no rewrite

The following asymmetric configurations are supported on the Cisco ME3600/ME3800 switches:

efps with no tag & no rewrite
efps with 1 tag & pop 1
efps with 2 tag & pop 2

Configuring Ethernet CFM

Configuring Ethernet CFM requires configuring the CFM domain. You can optionally configure and enable other CFM features such as crosschecking, remote MEP, port MEPs, SNMP traps, and fault alarms.

Default Ethernet CFM Configuration

CFM is globally disabled.

CFM is enabled on all interfaces when CFM is globally enabled.

A port can be configured as a flow point (MIP/MEP), a transparent port, or disabled (CFM disabled). By default, ports are transparent ports until configured as MEP, MIP, or disabled.

There are no MEPs or MIPs configured.

When configuring a MEP service, if you do not configure direction, the default is up (inward facing).

Ethernet CFM Configuration Guidelines

CFM is not supported on and cannot be configured on routed ports or on Layer 3 EtherChannels.
CFM is supported on EtherChannel port channels. You can configure an EtherChannel port channel as MEP or MIP. However, CFM is not supported on individual ports that belong to an EtherChannel and you cannot add a CFM port to an EtherChannel group.
Port MEP is not supported on Layer 2 EtherChannels, or on ports that belong to an EtherChannel.
CFM is supported on VLAN interfaces and on service instances (bridge domains).
CFM is supported on trunk ports and access ports with these exceptions:

– Trunk ports configured as MEPs must belong to allowed VLANs

– Access ports configured as MEPs must belong to the native VLAN.

A REP port or FlexLink port can also be a service (VLAN) MEP or MIP, but it cannot be a port MEP.
CFM is supported on ports running STP.
You must configure a port MEP at a lower level than any service (VLAN) MEPs on an interface.
You cannot configure tunnel mode by using the native VLAN as the S-VLAN or the C-VLAN.
Do not configure double-tagged 802.1ag CFM packets entering a trunk port.

Configuring the CFM Domain

Beginning in privileged EXEC mode, follow these steps to configure the Ethernet CFM domain, configure a service to connect the domain to a VLAN, or configure a port to act as a MEP. You can also enter the optional commands to configure other parameters, such as continuity checks.

	Command	Purpose
Step 1	configure terminal	Enter global configuration mode.
Step 2	ethernet cfm ieee	Configure the CFM version as IEEE 802.1ag.
Step 3	ethernet cfm global	Globally enable Ethernet CFM on the switch.
Step 4	ethernet cfm traceroute cache [ size entries \| hold-time minutes ]	(Optional) Configure the CFM traceroute cache. You can set a maximum cache size or hold time. (Optional) For size, enter the cache size in number of entry lines. The range is from 1 to 4095; the default is 100 lines. (Optional) For hold-time, enter the maximum cache hold time in minutes. The range is from 1 to 65535; the default is 100 minutes.
Step 5	ethernet cfm mip auto-create level level-id vlan vlan-id	(Optional) Configure the switch to automatically create MIPs for VLAN IDS that are not associated with specific maintenance associations at the specified level. The level range is 0 to 7. Note Configure MIP auto-creation only for VLANs that MIPs should monitor. Configuring for all VLANs can be CPU and memory-intensive.
Step 6	ethernet cfm mip filter	(Optional) Enable MIP filtering, which means that all CFM frames at a lower level are dropped. The default is disabled.
Step 7	ethernet cfm domain domain-name level level-id	Define a CFM domain, set the domain level, and enter ethernet-cfm configuration mode for the domain. The maintenance level number range is 0 to 7.
Step 8	id { mac-address domain_number \| dns name \| null }	(Optional) Assign a maintenance domain identifier. mac-address domain_number — Enter the MAC address and a domain number. The number can be from 0 to 65535. dns name —Enter a DNS name string. The name can be a maximum of 43 characters. null —Assign no domain name.
Step 9	service { ma-name \| ma-number \| vpn-id vpn } { evc evc-id }{ vlan vlan-id [ direction down ] \| port }	Define a customer service maintenance association (MA) name or number or VPN ID to be associated with the domain, a VLAN ID or port MEP, and enter ethernet-cfm-service configuration mode. ma-name —a string of no more than 100 characters that identifies the MAID. ma-number —a value from 0 to 65535. vpn-id vpn —enter a VPN ID as the ma-name. vlan vlan-id —VLAN range is from 1 to 4094. You cannot use the same VLAN ID for more than one domain at the same level. evc evc-id —enter an EVC name. (Optional) direction down —specify the service direction as down. port —Configure port MEP, a down MEP that is untagged and not associated with a VLAN.
Step 10	continuity-check	Enable sending and receiving of continuity check messages.
Step 11	continuity-check interval value	(Optional) Set the interval at which continuity check messages are sent. The available values are 100 ms, 1 second, 10 seconds, 1 minute and 10 minutes. The default is 10 seconds. Note Because faster CCM rates are more CPU-intensive, we do not recommend configuring a large number of MEPs running at 100 ms intervals.
Step 12	continuity-check loss-threshold threshold-value	(Optional) Set the number of continuity check messages to be missed before declaring that an MEP is down. The range is 2 to 255; the default is 3.
Step 13	maximum meps value	(Optional) Configure the maximum number of MEPs allowed across the network. The range is from 1 to 65535. The default is 100.
Step 14	sender-id { chassis \| none }	(Optional) Include the sender ID TLVs, attributes containing type, length, and values for neighbor devices. chassis —Send the chassis ID (host name). none —Do not include information in the sender ID.
Step 15	mip auto-create [ lower-mep-only \| none ]	(Optional) Configure auto creation of MIPs for the service. lower-mep-only—Create a MIP only if there is a MEP for the service in another domain at the next lower active level. none —No MIP auto-create.
Step 16	exit	Return to ethernet-cfm configuration mode.
Step 17	mip auto-create [ lower-mep-only ]	(Optional) Configure auto creation of MIPs for the domain. lower-mep-only—Create a MIP only if there is a MEP for the service in another domain at the next lower active level.
Step 18	mep archive-hold-time minutes	(Optional) Set the number of minutes that data from a missing maintenance end point is kept before it is purged. The range is 1 to 65535; the default is 100 minutes.
Step 19	exit	Return to global configuration mode.
Step 20	interface interface-id	Specify an interface to configure, and enter interface configuration mode.
Step 21	switchport mode trunk	(Optional) Configure the port as a trunk port.
Step 22	ethernet cfm mip level level-id	(Optional) Configure a customer level or service-provider level maintenance intermediate point (MIP) for the interface. The MIP level range is 0 to 7. Note This step is not required if you have entered the ethernet cfm mip auto-create global configuration command or the mip auto-create ethernet-cfm or ethernet-cfm-srv configuration mode.
Step 23	ethernet cfm mep domain domain-name mpid identifier { vlan vlan-id \| port }	Configure maintenance end points for the domain, and enter ethernet cfm mep mode. domain domain-name —Specify the name of the created domain. mpid identifier —Enter a maintenance end point identifier. The identifier must be unique for each VLAN. The range is 1 to 4094. vlan vlan-id —Enter the service provider VLAN ID or IDs as a VLAN-ID (1 to 4094), a range of VLAN-IDs separated by a hyphen, or a series of VLAN IDs separated by comma. port —Configure port MEP.
Step 24	cos value	(Optional) Specify the class of service (CoS) value to be sent with the messages. The range is 0 to 7.
Step 25	end	Return to privileged EXEC mode.
Step 26	show ethernet cfm maintenance-points { local \| remote }	Verify the configuration.
Step 27	show ethernet cfm errors [configuration]	(Optional) Display the configuration error list.
Step 28	copy running-config startup-config	(Optional) Save your entries in the configuration file.

Use the no versions of the commands to remove the configuration or return to the default configurations.

This is an example of the basic CFM configuration:

Switch(config)# ethernet cfm ieee

Switch(config)# ethernet cfm global

Switch(config)# ethernet evc evcl

Switch(config)# ethernet cfm domain abc level 3

Switch(config-ecfm)# service test evc evcl vlan 5

Switch(config-ecfm-srv)# continuity-check

Switch(config-ecfm-srv)# exit

Switch(config-ecfm)# exit

Switch(config)# interface gigabitethernet0/2

Switch(config-if)# ethernet cfm mep domain abc mpid 222 service test

Switch(config-if-ecfm-mep)# exit

Configuring Ethernet CFM Crosscheck

Beginning in privileged EXEC mode, follow these steps to configure Ethernet CFM crosscheck:

	Command	Purpose
Step 1	configure terminal	Enter global configuration mode.
Step 2	ethernet cfm mep crosscheck start-delay delay	Configure the number of seconds that the device waits for remote MEPs to come up before the crosscheck is started. The range is 1 to 65535; the default is 30 seconds.
Step 3	ethernet cfm domain domain-name level level-id	Define a CFM domain, set the domain level, and enter ethernet-cfm configuration mode for the domain. The maintenance level number range is 0 to 7.
Step 4	service { ma-name \| ma-number \| vpn-id vpn } { evc evc-id }{ vlan vlan-id }	Define a customer service maintenance association name or number or VPN ID to be associated with the domain, and a VLAN ID, and enter ethernet-cfm-service configuration mode. ma-name —a string of no more than 100 characters that identifies the MAID. ma-number —a value from 0 to 65535. vpn-id vpn —enter a VPN ID as the ma-name. vlan vlan-id —VLAN range is from 1 to 4094. You cannot use the same VLAN ID for more than one domain at the same level. evc evc-id —enter and EVC name.
Step 5	mep mpid identifier	Define the MEP maintenance end point identifier in the domain and service. The range is 1 to 4094.
Step 6	end	Return to privileged EXEC mode.
Step 7	ethernet cfm mep crosscheck { enable \| disable } domain domain-name { vlan { vlan-id \| any } \| port }	Enable or disable CFM crosscheck for one or more VLANs or a port MEP in the domain. domain domain-name —Specify the name of the created domain. vlan { vlan-id \| any }—Enter the service provider VLAN ID or IDs as a VLAN-ID (1 to 4094), a range of VLAN-IDs separated by a hyphen, or a series of VLAN IDs separated by comma. Enter any for any VLAN. port —Identify a port MEP.
Step 8	show ethernet cfm maintenance-points remote crosscheck	Verify the configuration.
Step 9	show ethernet cfm errors [ configuration ]	Enter this command after you enable CFM crosscheck to display the results of the crosscheck operation. Enter the configuration keyword to display the configuration error list.
Step 10	copy running-config startup-config	(Optional) Save your entries in the configuration file.

Use the no form of each command to remove a configuration or to return to the default settings.

Configuring Static Remote MEP

Beginning in privileged EXEC mode, follow these steps to configure Ethernet CFM static remote MEP:

	Command	Purpose
Step 1	configure terminal	Enter global configuration mode.
Step 2	ethernet cfm domain domain-name level level-id	Define a CFM domain, set the domain level, and enter ethernet-cfm configuration mode for the domain. The maintenance level number range is 0 to 7.
Step 3	service { ma-name \| ma-number \| vpn-id vpn }{ evc evc-id }{ vlan vlan-id [ direction down ] \| port }	Define a customer service maintenance association name or number or a VPN ID to be associated with the domain, and a VLAN ID or peer MEP, and enter ethernet-cfm-service configuration mode. ma-name —a string of no more than 100 characters that identifies the MAID. ma-number —a value from 0 to 65535. vpn-id —enter a VPN ID as the ma-name. vlan vlan-id —VLAN range is from 1 to 4094. You cannot use the same VLAN ID for more than one domain at the same level. (Optional) direction down —specify the service direction as down. port —Configure port MEP, a down MEP that is untagged and not associated with a VLAN.
Step 4	continuity-check	Enable sending and receiving of continuity check messages.
Step 5	mep mpid identifier	Define the static remote maintenance end point identifier. The range is 1 to 4094.
Step 6	continuity-check static rmep	Enable checking of the incoming continuity check message from a remote MEP that is configured in the MEP list.
Step 7	end	Return to privileged EXEC mode.
Step 8	show ethernet cfm maintenance-points remote static	Verify the configuration.
Step 9	show ethernet cfm errors [ configuration ]	Enter this command after you enable CFM crosscheck to display the results of the crosscheck operation. Enter the configuration keyword to display the configuration error list.
Step 10	copy running-config startup-config	(Optional) Save your entries in the configuration file.

Use the no form of each command to remove a configuration or to return to the default settings.

Configuring a Port MEP

A port MEP is a down MEP that is not associated with a VLAN and that uses untagged frames to carry CFM messages. You configure port MEPs on two connected interfaces. Port MEPs are always configured at a lower domain level than native VLAN MEPs.

Beginning in privileged EXEC mode, follow these steps to configure Ethernet CFM port MEPs:

	Command	Purpose
Step 1	configure terminal	Enter global configuration mode.
Step 2	ethernet cfm domain domain-name level level-id	Define a CFM domain, set the domain level, and enter ethernet-cfm configuration mode for the domain. The maintenance level number range is 0 to 7.
Step 3	service { ma-name \| ma-number \| vpn-id } port	Define a customer service maintenance association name or number or VPN ID to be associated with the domain, define a port MEP, and enter ethernet-cfm-service configuration mode. ma-name —a string of no more than 100 characters that identifies the MAID. ma-number —a value from 0 to 65535. vpn-id vpn —enter a VPN ID as the ma-name.
Step 4	mep mpid identifier	Define the static remote maintenance end point identifier in the domain and service. The range is 1 to 4094.
Step 5	continuity-check	Enable sending and receiving of continuity check messages.
Step 6	continuity-check interval value	(Optional) Set the interval at which continuity check messages are sent. The available values are 100 ms, 1 second, 10 seconds, 1 minute and 10 minutes. The default is 10 seconds. Note Because faster CCM rates are more CPU-intensive, we do not recommend configuring a large number of MEPs running at 100 ms intervals.
Step 7	continuity-check loss-threshold threshold-value	(Optional) Set the number of continuity check messages to be missed before declaring that an MEP is down. The range is 2 to 255; the default is 3.
Step 8	continuity-check static rmep	Enable checking of the incoming continuity check message from a remote MEP that is configured in the MEP list.
Step 9	exit	Return to ethernet-cfm configuration mode.
Step 10	exit	Return to global configuration mode.
Step 11	interface interface-id	Identify the port MEP interface and enter interface configuration mode.
Step 12	ethernet cfm mep domain domain-name mpid identifier port	Configure the interface as a port MEP for the domain. domain domain-name —Specify the name of the created domain. mpid identifier —Enter a maintenance end point identifier. The identifier must be unique for each VLAN. The range is 1 to 4094.
Step 13	end	Return to privileged EXEC mode.
Step 14	show ethernet cfm maintenance-points remote static	Verify the configuration.
Step 15	show ethernet cfm errors [ configuration ]	Enter this command after you enable CFM crosscheck to display the results of the crosscheck operation. Enter the configuration keyword to display the configuration error list.
Step 16	copy running-config startup-config	(Optional) Save your entries in the configuration file.

Use the no form of each command to remove a configuration or to return to the default settings.

This is a sample configuration for a port MEP:

Switch(config)# ethernet cfm domain abc level 3

Switch(config-ecfm)# service PORTMEP port

Switch(config-ecfm-srv)# mep mpid 222

Switch(config-ecfm-srv)# continuity-check

Switch(config-ecfm-srv)# continuity-check static rmep

Switch(config-ecfm-srv)# exit

Switch(config-ecfm)# exit

Switch(config)# interface gigabitethernet0/1

Switch(config-if)# ethernet cfm mep domain abc mpid 111 port

Switch(config-if)# end

Configuring SNMP Traps

Beginning in privileged EXEC mode, follow these steps to configure traps for Ethernet CFM:

	Command	Purpose
Step 1	configure terminal	Enter global configuration mode.
Step 2	snmp-server enable traps ethernet cfm cc [ mep-up ] [ mep-down ] [ config ] [ loop ] [ cross-connect ]	(Optional) Enable Ethernet CFM continuity check traps.
Step 3	snmp-server enable traps ethernet cfm crosscheck [ mep-unknown ] [ mep-missing ] [ service-up ]	(Optional) Enable Ethernet CFM crosscheck traps.
Step 4	end	Return to privileged EXEC mode.
Step 5	show running-config	Verify your entries.
Step 6	copy running-config startup-config	(Optional) Save your entries in the configuration file.

Use the no form of each command to remove a configuration or to return to the default settings.

Configuring Fault Alarms

Beginning in privileged EXEC mode, follow these steps to configure Ethernet CFM fault alarms. Note that you can configure fault alarms in either global configuration mode or Ethernet CFM interface MEP mode. In case of conflict, the interface MEP mode configuration takes precedence.

	Command	Purpose
Step 1	configure terminal	Enter global configuration mode.
Step 2	ethernet cfm alarm notification { all \| error-xcon \| mac-remote-error-xcon \| none \| remote-error-xcon \| xcon }	Globally enable Ethernet CFM fault alarm notification for the specified defects: all —report all defects. error-xcon —Report only error and connection defects. mac-remote-error-xcon —Report only MAC-address, remote, error, and connection defects. none —Report no defects. remote-error-xcon —Report only remote, error, and connection defects. xcon —Report only connection defects.
Step 3	ethernet cfm alarm delay value	(Optional) Set a delay period before a CFM fault alarm is sent. The range is 2500 to 10000 milliseconds (ms). The default is 2500 ms.
Step 4	ethernet cfm alarm reset value	(Optional) Specify the time period before the CFM fault alarm is reset. The range is 2500 to 10000 milliseconds (ms). The default is 10000 ms.
Step 5	ethernet cfm logging alarm ieee	Configure the switch to generate system logging messages for the alarms.
Step 6	interface interface-id	(Optional) Specify an interface to configure, and enter interface configuration mode.
Step 7	ethernet cfm mep domain domain-name mpid identifier vlan vlan-id	Configure maintenance end points for the domain, and enter ethernet cfm interface mep mode. domain domain-name —Specify the name of the created domain. mpid identifier —Enter a maintenance end point identifier. The identifier must be unique for each VLAN. The range is 1 to 4094. vlan vlan-id —Enter the service provider VLAN ID or IDs as a VLAN-ID (1 to 4094), a range of VLAN-IDs separated by a hyphen, or a series of VLAN IDs separated by comma.
Step 8	ethernet cfm alarm notification { all \| error-xcon \| mac-remote-error-xcon \| none \| remote-error-xcon \| xcon }	(Optional) Enable Ethernet CFM fault alarm notification for the specified defects on the interface. Note The Ethernet CFM interface MEP alarm configuration takes precedence over the global configuration.
Step 9	ethernet cfm alarm { delay value \| reset value }	(Optional) Set an alarm delay period or a reset period. Note The Ethernet CFM interface MEP alarm configuration takes precedence over the global configuration.
Step 10	end	Return to privileged EXEC mode.
Step 11	show running-config	Verify your entries.
Step 12	copy running-config startup-config	(Optional) Save your entries in the configuration file.

Use the no form of each command to remove a configuration or to return to the default settings.

Configuring IP SLAs CFM Operation

You can manually configure an individual IP SLAs Ethernet ping or jitter echo operation or you can configure IP SLAs Ethernet operation with endpoint discovery. You can also configure multiple operation scheduling. For accurate one-way delay statistics, the clocks on the endpoint switches must be synchronized. You can configure the endpoint switches with Network Time Protocol (NTP) so that the switches are synchronized to the same clock source.

For more information about configuring IP SLAs Ethernet operation, see the IP SLAs for Metro-Ethernet.

For detailed information about configuring IP SLAs operations, see the Cisco IOS IP SLAs Configuration Guide.

For detailed information about IP SLAs commands, see the command reference at this URL: http://www.cisco.com/en/US/docs/ios/ipsla/command/reference/sla_book.html

This section includes these procedures:

Manually Configuring an IP SLAs CFM Probe or Jitter Operation

Beginning in privileged EXEC mode, follow these steps to manually configure an IP SLAs Ethernet echo (ping) or jitter operation:

	Command	Purpose
Step 1	configure terminal	Enter global configuration mode.
Step 2	ip sla operation-number	Create an IP SLAs operation, and enter IP SLAs configuration mode.
Step 3	ethernet echo mpid identifier domain domain-name vlan vlan-id or ethernet jitter mpid identifier domain domain-name vlan vlan-id [ interval interpacket-interval ] [ num-frames number-of frames transmitted ]	Configure the IP SLAs operation as an echo (ping) or jitter operation, and enter IP SLAs Ethernet echo configuration mode. Enter echo for a ping operation or jitter for a jitter operation. For mpid identifier, enter a maintenance endpoint identifier. The identifier must be unique for each VLAN. The range is 1 to 4094. For domain domain-name, enter the CFM domain name. For vlan vlan-id, the VLAN range is from 1 to 4095. (Optional—for jitter only) Enter the interval between sending of jitter packets. (Optional—for jitter only) Enter the num-frames and the number of frames to be sent.
Step 4	cos cos-value	(Optional) Set a class of service value for the operation.
Step 5	frequency seconds	(Optional) Set the rate at which the IP SLAs operation repeats. The range is from 1 to 604800 seconds; the default is 60 seconds.
Step 6	history history-parameter	(Optional) Specify parameters for gathering statistical history information for the IP SLAs operation.
Step 7	owner owner-id	(Optional) Configure the SNMP owner of the IP SLAs operation.
Step 8	request-data-size bytes	(Optional) Specify the protocol data size for an IP SLAs request packet. The range is from 0 to the maximum size allowed by the protocol being used; the default is 66 bytes.
Step 9	tag text	(Optional) Create a user-specified identifier for an IP SLAs operation.
Step 10	threshold milliseconds	(Optional) Specify the upper threshold value in milliseconds (ms0 for calculating network monitoring statistics. The range is 0 to 2147483647; the default is 5000.
Step 11	timeout milliseconds	(Optional) Specify the amount of time in ms that the IP SLAs operation waits for a response from its request packet. The range is 0 to 604800000; the default value is 5000.
Step 12	exit	Return to global configuration mode.
Step 13	ip sla schedule operation-number [ ageout seconds ] [ life { forever \| seconds }] [ recurring ] [ start-time { hh:mm { :ss } [ month day \| day month ] \| pending \| now \| after hh:mm:ss }]	Schedule the time parameters for the IP SLAs operation. operation-number —Enter the IP SLAs operation number. (Optional) ageout seconds —Enter the number of seconds to keep the operation in memory when it is not actively collecting information. The range is 0 to 2073600 seconds. The default is 0 seconds. (Optional) life —Set the operation to run indefinitely (forever) or for a specific number of seconds. The range is from 0 to 2147483647. The default is 3600 seconds (1 hour) (Optional) recurring —Set the probe to be automatically scheduled every day. (Optional) start-time —Enter the time for the operation to begin collecting information: – To start at a specific time, enter the hour, minute, second (in 24-hour notation), and day of the month. – Enter pending to select no information collection until a start time is selected. – Enter now to start the operation immediately. – Enter after hh:mm:ss to show that the operation should start after the entered time has elapsed.
Step 14	end	Return to privileged EXEC mode.
Step 15	show ip sla configuration [ operation-number ]	Show the configured IP SLAs operation.
Step 16	copy running-config startup-config	(Optional) Save your entries in the configuration file.

To remove an IP SLAs operation, enter the no ip sla operation-number global configuration command.

Configuring an IP SLAs Operation with Endpoint Discovery

Beginning in privileged EXEC mode, follow these steps to use IP SLAs to automatically discover the CFM endpoints for a domain and VLAN ID. You can configure ping or jitter operations to the discovered endpoints.

	Command	Purpose
Step 1	configure terminal	Enter global configuration mode.
Step 2	ip sla ethernet-monitor operation-number	Begin configuration of an IP SLAs automatic Ethernet operation, and enter IP SLAs Ethernet monitor configuration mode.
Step 3	type echo domain domain-name vlan vlan-id [ exclude-mpids mp-ids ] or type jitter domain domain-name vlan vlan-id [ exclude-mpids mp-ids ] [ interval interpacket-interval ] [ num-frames number-of frames transmitted ]	Configure the automatic Ethernet operation to create echo (ping) or jitter operation and enter IP SLAs Ethernet echo configuration mode. Enter type echo for a ping operation or type jitter for a jitter operation. For mpid identifier, enter a maintenance endpoint identifier. The range is 1 to 4094. For domain domain-name, enter the CFM domain name. For vlan vlan-id, the VLAN range is from 1 to 4095. (Optional) Enter exclude-mpids mp-ids to exclude the specified maintenance endpoint identifiers. (Optional—for jitter only) Enter the interval between sending of jitter packets. (Optional—for jitter only) Enter the num-frames and the number of frames to be sent.
Step 4	cos cos-value	(Optional) Set a class of service value for the operation.
Step 5	owner owner-id	(Optional) Configure the SNMP owner of the IP SLAs operation.
Step 6	request-data-size bytes	(Optional) Specify the protocol data size for an IP SLAs request packet. The range is from 0 to the maximum size allowed by the protocol being used; the default is 66 bytes.
Step 7	tag text	(Optional) Create a user-specified identifier for an IP SLAs operation.
Step 8	threshold milliseconds	(Optional) Specify the upper threshold value in milliseconds for calculating network monitoring statistics. The range is 0 to 2147483647; the default is 5000.
Step 9	timeout milliseconds	(Optional) Specify the amount of time in milliseconds that the IP SLAs operation waits for a response from its request packet. The range is 0 to 604800000; the default value is 5000.
Step 10	exit	Return to global configuration mode.
Step 11	ip sla schedule operation-number [ ageout seconds ] [ life { forever \| seconds }] [ recurring ] [ start-time { hh:mm { :ss } [ month day \| day month ] \| pending \| now \| after hh:mm:ss }]	Schedule the time parameters for the IP SLAs operation. operation-number —Enter the IP SLAs operation number. (Optional) ageout seconds —Enter the number of seconds to keep the operation in memory when it is not actively collecting information. The range is 0 to 2073600 seconds. The default is 0 seconds. (Optional) life —Set the operation to run indefinitely (forever) or for a specific number of seconds. The range is from 0 to 2147483647. The default is 3600 seconds (1 hour) (Optional) recurring —Set the probe to be automatically scheduled every day. (Optional) start-time —Enter the time for the operation to begin collecting information: – To start at a specific time, enter the hour, minute, second (in 24-hour notation), and day of the month. – Enter pending to select no information collection until a start time is selected. – Enter now to start the operation immediately. – Enter after hh:mm:ss to show that the operation should start after the entered time has elapsed.
Step 12	end	Return to privileged EXEC mode.
Step 13	show ip sla configuration [ operation-number ]	Show the configured IP SLAs operation.
Step 14	copy running-config startup-config	(Optional) Save your entries in the configuration file.

To remove an IP SLAs operation, enter the no ip sla operation-number global configuration command.

Configuring CFM on EVC Bridge Domains and EVC Cross-Connect Interfaces

The following examples show how to configure CFM on EVC.

Configuring CFM on EVC Commands

The following example shows the CLIs that are available for configuring CFM on EVC.

ethernet cfm ieee

ethernet cfm global

ethernet cfm domain L6 level 6

service vlan100 evc evc100 direction down

continuity-check

service vlan200 evc evc200

continuity-check

service vlan200 evc evc300

continuity-check

service xconn evc xconn direction down

continuity-check

Configuring CFM on an EVC Bridge Domain

The following example shows how to configure CFM on an EVC Bridge Domain.

interface GigabitEthernet2/0/0

no ip address

no mls qos trust

service instance 1 ethernet evc100

encapsulation dot1q 1000

bridge-domain 1000

cfm mep domain L6 mpid 99

exit

service instance 2 ethernet evc200

encapsulation dot1q 2000

bridge-domain 2000

cfm mep domain L6 mpid 77

exit

service instance 3 ethernet evc300

encapsulation dot1q 300

xconnect 1.1.1.1 1 encap mpls

cfm mep domain L6 mpid 88

exit

end

Displaying CFM on EVC

The following example shows how to display CFM information.

Switch# show ethernet cfm ma local

Local MEPs:

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

MPID Domain Name Lvl MacAddress Type CC

Domain Id Dir Port Id

MA Name SrvcInst

EVC name

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

77 L6 6 000b.45e5.cb90 BD-V Y

L6 Up Gi 0/2 2000

vlan2000 2

evc2000

99 L6 6 00e0.aabb.cc00 BD-V Y

L6 Down Gi 0/2 1000

vlan1000 1

evc1000

100 R3 3 00e0.aabb.cc0a BD-V Y

R3 Down Gi 0/10 10

sr1 1

er1

2 eccm2 0 00e0.aabb.cc09 BD-V I

eccm2 Down Gi /0/9 100

ser2 N/A

evc2

Total Local MEPs: 4

Local MIPs: None

Configuring CFM on an EVC with Cross-Connect

The following example shows how to configure CFM on EVC with cross-connect.

pseudowire-class vlan-xconnect

encapsulation mpls

interface gigabit 1/1

service instance 10 ethernet

encapsulation dot1q 20

xconnect 2.2.2.2 123 pw-class vlan-xconnect

cfm mep domain Core mpid 100

Remote MEPs:

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

MPID Domain Name Lvl MacAddress Type CC

Domain Id Dir Port Id

MA Name SrvcInst

EVC name

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

7003 ofm_xcon 5 <port-mac> XCONN Y

ofm_xcon Down Gi4/5 N/A

ofm_serv xcon_evc_name

xcon_evc_name

8103 ifm_xcon 5 <BRAIN-MAC> XCONN Y

ifm_xcon Up (10.10.10.3,81) PW

ifm_serv xcon_evc_name

xcon_evc_name

Managing and Displaying Ethernet CFM Information

You can use the privileged EXEC commands in these tables to clear Ethernet CFM information.

Table 48-1 Clearing CFM Information
Command	Purpose
clear ethernet cfm ais domain domain-name mpid id { vlan vlan-id \| port }	Clear MEPs with matching domain and VLAN ID out of AIS defect condition.
clear ethernet cfm ais link-status interface interface-id	Clear a SMEP out of AIS defect condition.
clear ethernet cfm error	Clear all CFM error conditions, including AIS.

You can use the privileged EXEC commands in Table 48-2 to display Ethernet CFM information.

Table 48-2 Displaying CFM Information
Command	Purpose
show ethernet cfm domain [ brief ]	Displays CFM domain information or brief domain information.
show ethernet cfm errors [ configuration \| domain-id ]	Displays CFM continuity check error conditions logged on a device since it was last reset or the log was last cleared. When CFM crosscheck is enabled, displays the results of the CFM crosscheck operation.
show ethernet cfm maintenance-points local [ detail \| domain \| interface \| level \| mep \| mip ]	Displays maintenance points configured on a device.
show ethernet cfm maintenance-points remote [ crosscheck \| detail \| domain \| static ]	Displays information about a remote maintenance point domains or levels or details in the CFM database.
show ethernet cfm mpdb	Displays information about entries in the MIP continuity-check database.
show ethernet cfm smep [ interface interface-id ]	Displays Ethernet CFM SMEP information.
show ethernet cfm traceroute-cache	Displays the contents of the traceroute cache.
show platform cfm	Displays platform-independent CFM information.

This is an example of output from the show ethernet cfm domain brief command:

Switch# show ethernet cfm domain brief

Domain Name Index Level Services Archive(min)

level5 1 5 1 100

level3 2 3 1 100

test 3 3 3 100

name 4 3 1 100

test1 5 2 1 100

lck 6 1 1 100Total Services : 1

This is an example of output from the show ethernet cfm errors command:

Switch# show ethernet cfm errors

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

MPID Domain Id Mac Address Type Id Lvl

MAName Reason Age

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

6307 level3 0021.d7ee.fe80 Vlan 7 3

vlan7 Receive RDI 5s

This is an example of output from the show ethernet cfm maintenance-points local detail command:

Switch# show ethernet cfm maintenance-points local detail

Local MEPs:

----------

MPID: 7307

DomainName: level3

Level: 3

Direction: Up

Vlan: 7

Interface: Gi0/3

CC-Status: Enabled

CC Loss Threshold: 3

MAC: 0021.d7ef.0700

LCK-Status: Enabled

LCK Period: 60000(ms)

LCK Expiry Threshold: 3.5

Level to transmit LCK: Default

Defect Condition: No Defect

presentRDI: FALSE

AIS-Status: Enabled

AIS Period: 60000(ms)

AIS Expiry Threshold: 3.5

Level to transmit AIS: Default

Suppress Alarm configuration: Enabled

Suppressing Alarms: No

MIP Settings:

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

Local MIPs:

* = MIP Manually Configured

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

Level Port MacAddress SrvcInst Type Id

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

*5 Gi0/3 0021.d7ef.0700 N/A Vlan 2,7

This is an example of output from the show ethernet cfm traceroute command:

Switch# show ethernet cfm traceroute

Current Cache-size: 0 Hops

Max Cache-size: 100 Hops

Hold-time: 100 Minutes

You can use the privileged EXEC commands in Table 48-3 to display IP SLAs Ethernet CFM information.

Table 48-3 Displaying IP SLAs CFM Information
Command	Purpose
show ip sla configuration [ entry-number ]	Displays configuration values including all defaults for all IP SLAs operations or a specific operation.
show ip sla ethernet-monitor configuration [ entry-number ]	Displays the configuration of the IP SLAs automatic Ethernet operation.
show ip sla statistics [ entry-number \| aggregated \| details ]	Display current or aggregated operational status and statistics.

Understanding the Ethernet OAM Protocol

The Ethernet OAM protocol for installing, monitoring, and troubleshooting Metro Ethernet networks and Ethernet WANs relies on an optional sublayer in the data link layer of the OSI model. Normal link operation does not require Ethernet OAM. You can implement Ethernet OAM on any full-duplex point-to-point or emulated point-to-point Ethernet link for a network or part of a network (specified interfaces).

OAM frames, called OAM protocol data units (OAM PDUs) use the slow protocol destination MAC address 0180.c200.0002. They are intercepted by the MAC sublayer and cannot propagate beyond a single hop within an Ethernet network. Ethernet OAM is a relatively slow protocol, with a maximum transmission rate of 10 frames per second, resulting in minor impact to normal operations. However, when you enable link monitoring, because the CPU must poll error counters frequently, the number of required CPU cycles is proportional to the number of interfaces that must be polled.

Ethernet OAM has two major components:

The OAM client establishes and manages Ethernet OAM on a link and enables and configures the OAM sublayer. During the OAM discovery phase, the OAM client monitors OAM PDUs received from the remote peer and enables OAM functionality. After the discovery phase, it manages the rules of response to OAM PDUs and the OAM remote loopback mode.
The OAM sublayer presents two standard IEEE 802.3 MAC service interfaces facing the superior and inferior MAC sublayers. It provides a dedicated interface for the OAM client to pass OAM control information and PDUs to and from the client. It includes these components:

– The control block provides the interface between the OAM client and other OAM sublayer internal blocks.

– The multiplexer manages frames from the MAC client, the control block, and the parser and passes OAM PDUs from the control block and loopback frames from the parser to the subordinate layer.

– The parser classifies frames as OAM PDUs, MAC client frames, or loopback frames and sends them to the appropriate entity: OAM PDUs to the control block, MAC client frames to the superior sublayer, and loopback frames to the multiplexer.

OAM Features

These OAM features are defined by IEEE 802.3ah:

Discovery identifies devices in the network and their OAM capabilities. It uses periodic OAM PDUs to advertise OAM mode, configuration, and capabilities; PDU configuration; and platform identity. An optional phase allows the local station to accept or reject the configuration of the peer OAM entity.
Link monitoring detects and indicates link faults under a variety of conditions and uses the event notification OAM PDU to notify the remote OAM device when it detects problems on the link. Error events include when the number of symbol errors, the number of frame errors, the number of frame errors within a specified number of frames, or the number of error seconds within a specified period exceed a configured threshold.
Remote failure indication conveys a slowly deteriorating quality of an OAM entity to its peers by communicating these conditions: Link Fault means a loss of signal, Dying Gasp means an unrecoverable condition, and Critical Event means an unspecified vendor-specific critical event. The switch can receive and process but not generate Link Fault or Critical Event OAM PDUs. It can generate Dying Gasp OAM PDUs to show when Ethernet OAM is disabled, the interface is shut down, the interface enters the error-disabled state, or the switch is reloading. It also supports Dying Gasp PDUs based on loss of power.
Remote loopback mode to ensure link quality with a remote peer during installation or troubleshooting. In this mode, when the switch receives a frame that is not an OAM PDU or a pause frame, it sends it back on the same port. The link appears to the user to be in the up state. You can use the returned loopback acknowledgement to test delay, jitter, and throughput.
The operation Default Interface is not permitted on slave when OAM remote loopback operation has started. This operation is performed only after removing the interface configuration from Master side of the OAM Remote loopback.

OAM Messages

Ethernet OAM messages or PDUs are standard length, untagged Ethernet frames between 64 and 1518 bytes. They do not go beyond a single hop and have a maximum transmission rate of 10 OAM PDUs per second. Message types are information, event notification, loopback control, or vendor-specific OAM PDUs.

Setting Up and Configuring Ethernet OAM

Default Ethernet OAM Configuration

Ethernet OAM is disabled on all interfaces.

When Ethernet OAM is enabled on an interface, link monitoring is automatically turned on.

Remote loopback is disabled.

No Ethernet OAM templates are configured.

Ethernet OAM Configuration Guidelines

The switch does not support monitoring of egress frames sent with cyclic redundancy code (CDC) errors. The ethernet oam link-monitor transmit crc interface-configuration or template-configuration commands are visible but are not supported on the switch. The commands are accepted, but are not applied to an interface.
For a remote failure indication, the switch does not generate Link Fault or Critical Event OAM PDUs. However, if these PDUs are received from a link partner, they are processed. The switch supports generating and receiving Dying Gasp OAM PDUs when Ethernet OAM is disabled, the interface is shut down, the interface enters the error-disabled state, or the switch is reloading. The switch can also generate and receive Dying Gasp PDUs based on loss of power. The PDU includes a reason code to indicate why it was sent.
The switch does not support Ethernet OAM on ports that belong to an EtherChannel.

Enabling Ethernet OAM on an Interface

Beginning in privileged EXEC mode, follow these steps to enable Ethernet OAM on an interface:

	Command	Purpose
Step 1	configure terminal	Enter global configuration mode.
Step 2	interface interface-id	Define an interface to configure as an OAM interface, and enter interface configuration mode.
Step 3	ethernet oam	Enable Ethernet OAM on the interface.
Step 4	ethernet oam [ max-rate oampdus \| min-rate seconds \| mode { active \| passive } \| timeout seconds ]	You can configure these optional OAM parameters: (Optional) Enter max-rate oampdus to configure the maximum number of OAM PDUs sent per second. The range is from 1 to 10. (Optional) Enter min-rate seconds to configure the minimum transmission rate in seconds when one OAM PDU is sent per second. The range is from 1 to 10. (Optional) Enter mode active to set OAM client mode to active. (Optional) Enter mode passive to set OAM client mode to passive. Note When Ethernet OAM mode is enabled on two interfaces passing traffic, at least one must be in the active mode. (Optional) Enter timeout seconds to set a time for OAM client timeout. The range is from 2 to 30.
Step 5	end	Return to privileged EXEC mode.
Step 6	show ethernet oam status [ interface interface-id ]	Verify the configuration.
Step 7	copy running-config startup-config	(Optional) Save your entries in the configuration file.

Enter the no ethernet oam interface configuration command to disable Ethernet OAM on the interface.

Enabling Ethernet OAM Remote Loopback

You must enable Ethernet OAM remote loopback on an interface for the local OAM client to initiate OAM remote loopback operations. Changing this setting causes the local OAM client to exchange configuration information with its remote peer. Remote loopback is disabled by default.

Remote loopback has these limitations:

Internet Group Management Protocol (IGMP) packets are not looped back.
You cannot configure Ethernet OAM remote loopback on ports that belong to an EtherChannel.

Beginning in privileged EXEC mode, follow these steps to enable Ethernet OAM remote loopback on an interface:

	Command	Purpose
Step 1	configure terminal	Enter global configuration mode.
Step 2	interface interface-id	Define an interface to configure as an OAM interface, and enter interface configuration mode.
Step 3	ethernet oam remote-loopback { supported \| timeout seconds }	Enable Ethernet remote loopback on the interface, or set a loopback timeout period. Enter supported to enable remote loopback. Enter timeout seconds to set a remote loopback timeout period. The range is from 1 to 10 seconds.
Step 4	end	Return to privileged EXEC mode.
Step 5	ethernet oam remote-loopback { start \| stop } { interface interface-id }	Turn on or turn off Ethernet OAM remote loopback on an interface.
Step 6	show ethernet oam status [ interface interface-id ]	Verify the configuration.
Step 7	copy running-config startup-config	(Optional) Save your entries in the configuration file.

Use the no ethernet oam remote-loopback { supported | timeout } interface configuration command to disable remote loopback support or to remove the timeout setting.

Configuring Ethernet OAM Link Monitoring

You can configure high and low thresholds for link-monitoring features. If no high threshold is configured, the default is none —no high threshold is set. If you do not set a low threshold, it defaults to a value lower than the high threshold.

Beginning in privileged EXEC mode, follow these steps to configure Ethernet OAM link monitoring on an interface:

	Command	Purpose
Step 1	configure terminal	Enter global configuration mode.
Step 2	interface interface-id	Define an interface, and enter interface configuration mode.
Step 3	ethernet oam link-monitor supported	Enable the interface to support link monitoring. This is the default. You need to enter this command only if it has been disabled by previously entering the no ethernet oam link-monitor supported command.
Step 4	ethernet oam link-monitor symbol-period { threshold { high { high symbols \| none } \| low { low-symbols }} \| window symbols } Note Repeat this step to configure both high and low thresholds.	(Optional) Configure high and low thresholds for an error-symbol period that trigger an error-symbol period link event. Enter threshold high high-symbols to set a high threshold in number of symbols. The range is 1 to 65535. The default is none. Enter threshold high none to disable the high threshold if it was set. This is the default. Enter threshold low low-symbols to set a low threshold in number of symbols. The range is 0 to 65535. It must be lower than the high threshold. Enter window symbols to set the window size (in number of symbols) of the polling period. The range is 1 to 65535 symbols.
Step 5	ethernet oam link-monitor frame { threshold { high { high-frames \| none } \| low { low-frames }} \| window milliseconds }	(Optional) Configure high and low thresholds for error frames that trigger an error-frame link event. Enter threshold high high-frames to set a high threshold in number of frames. The range is 1 to 65535. The default is none. Enter threshold high none to disable the high threshold if it was set. This is the default. Enter threshold low low-frames to set a low threshold in number of frames. The range is 0 to 65535. The default is 1. Enter window milliseconds to set the a window and period of time during which error frames are counted. The range is 10 to 600 and represents the number of milliseconds in multiples of 100. The default is 100.
Step 6	ethernet oam link-monitor frame-period { threshold { high { high-frames \| none } \| low { low-frames }} \| window frames }	(Optional) Configure high and low thresholds for the error-frame period that triggers an error-frame-period link event. Enter threshold high high-frames to set a high threshold in number of frames. The range is 1 to 65535. The default is none. Enter threshold high none to disable the high threshold if it was set. This is the default. Enter threshold low low-frames to set a low threshold in number of frames. The range is 0 to 65535. The default is 1. Enter window frames to set the a polling window size in number of frames. The range is 1 to 65535; each value is a multiple of 10000 frames. The default is 1000.
Step 7	ethernet oam link-monitor frame-seconds { threshold { high { high-frames \| none } \| low { low-frames }} \| window milliseconds } Note Repeat this step to configure both high and low thresholds.	(Optional) Configure high and low thresholds for the frame-seconds error that triggers an error-frame-seconds link event. Enter threshold high high-frames to set a high error frame-seconds threshold in number of seconds. The range is 1 to 900. The default is none. Enter threshold high none to disable the high threshold if it was set. This is the default. Enter threshold low low-frames to set a low threshold in number of frames. The range is 1 to 900. The default is 1. Enter window frames to set the a polling window size in number of milliseconds. The range is 100 to 9000; each value is a multiple of 100 milliseconds. The default is 1000.
Step 8	ethernet oam link-monitor receive-crc { threshold { high { high-frames \| none } \| low { low-frames }} \| window milliseconds } Note Repeat this step to configure both high and low thresholds.	(Optional) Configure thresholds for monitoring ingress frames received with cyclic redundancy code (CRC) errors for a period of time. Enter threshold high high-frames to set a high threshold for the number of frames received with CRC errors. The range is 1 to 65535 frames. Enter threshold high none to disable the high threshold. Enter threshold low low-frames to set a low threshold in number of frames. The range is 0 to 65535. The default is 1. Enter window milliseconds to set the a window and period of time during which frames with CRC errors are counted. The range is 10 to 1800 and represents the number of milliseconds in multiples of 100. The default is 100.
Step 9	[ no ] ethernet link-monitor on	(Optional) Start or stop (when the no keyword is entered) link-monitoring operations on the interface. Link monitoring operations start automatically when support is enabled.
Step 10	end	Return to privileged EXEC mode.
Step 11	show ethernet oam status [ interface interface-id ]	Verify the configuration.
Step 12	copy running-config startup-config	(Optional) Save your entries in the configuration file.

The ethernet oam link-monitor transmit-crc { threshold { high { high-frames | none } | low { low-frames }} | window milliseconds } command is visible on the switch and you are allowed to enter it, but it is not supported. Enter the no form of the commands to disable the configuration. Use the no form of each command to disable the threshold setting.

Configuring Ethernet OAM Remote Failure Indications

You can configure an error-disable action to occur on an interface if one of the high thresholds is exceeded, if the remote link goes down, if the remote device is rebooted, or if the remote device disables Ethernet OAM on the interface.

Beginning in privileged EXEC mode, follow these steps to enable Ethernet OAM remote-failure indication actions on an interface:

	Command	Purpose
Step 1	configure terminal	Enter global configuration mode.
Step 2	interface interface-id	Define an interface, and enter interface configuration mode.
Step 3	ethernet oam remote-failure { critical-event \| dying-gasp \| link-fault } action error-disable-interface	Configure the Ethernet OAM remote-failure action on the interface. You can configure disabling the interface for one of these conditions: Select critical-event to shut down the interface when an unspecified critical event has occurred. Select dying-gasp to shut down the interface when Ethernet OAM is disabled or the interface enters the error-disabled state. Select link-fault to shut down the interface when the receiver detects a loss of signal.
Step 4	end	Return to privileged EXEC mode.
Step 5	show ethernet oam status [ interface interface-id ]	Verify the configuration.
Step 6	copy running-config startup-config	(Optional) Save your entries in the configuration file.

The switch does not generate Link Fault or Critical Event OAM PDUs. However, if these PDUs are received from a link partner, they are processed. The switch supports sending and receiving Dying Gasp OAM PDUs with reason codes when Ethernet OAM is disabled, the interface is shut down, the interface enters the error-disabled state, or the switch is reloading. It can also respond to and generate, Dying Gasp PDUs based on loss of power. Enter the no ethernet remote-failure { critical-event | dying-gasp | link-fault } action command to disable the remote failure indication action.

Configuring Ethernet OAM Templates

You can create a template for configuring a common set of options on multiple Ethernet OAM interfaces. The template can be configured to monitor frame errors, frame-period errors, frame-second errors, received CRS errors, and symbol-period errors and thresholds. You can also set the template to put the interface in error-disabled state if any high thresholds are exceeded. These steps are optional and can be performed in any sequence or repeated to configure different options.

Beginning in privileged EXEC mode, follow these steps to configure an Ethernet OAM template and to associate it with an interface:

	Command	Purpose
Step 1	configure terminal	Enter global configuration mode.
Step 2	template template-name	Create a template, and enter template configuration mode.
Step 3	ethernet oam link-monitor receive-crc { threshold { high { high-frames \| none } \| low { low-frames }} \| window milliseconds }	(Optional) Configure thresholds for monitoring ingress frames received with cyclic redundancy code (CRC) errors for a period of time. Enter threshold high high-frames to set a high threshold for the number of frames received with CRC errors. The range is 1 to 65535 frames. Enter threshold high none to disable the high threshold. Enter threshold low low-frames to set a low threshold in number of frames. The range is 0 to 65535. The default is 1. Enter window milliseconds to set the a window and period of time during which frames with CRC errors are counted. The range is 10 to 1800 and represents the number of milliseconds in multiples of 100. The default is 100.
Step 4	ethernet oam link-monitor symbol-period { threshold { high { high symbols \| none } \| low { low-symbols }} \| window symbols }	(Optional) Configure high and low thresholds for an error-symbol period that triggers an error-symbol period link event. Enter threshold high high-symbols to set a high threshold in number of symbols. The range is 1 to 65535. Enter threshold high none to disable the high threshold. Enter threshold low low-symbols to set a low threshold in number of symbols. The range is 0 to 65535. It must be lower than the high threshold. Enter window symbols to set the window size (in number of symbols) of the polling period. The range is 1 to 65535 symbols.
Step 5	ethernet oam link-monitor frame { threshold { high { high-frames \| none } \| low { low-frames }} \| window milliseconds }	(Optional) Configure high and low thresholds for error frames that trigger an error-frame link event. Enter threshold high high-frames to set a high threshold in number of frames. The range is 1 to 65535. You must enter a high threshold. Enter threshold high none to disable the high threshold. Enter threshold low low-frames to set a low threshold in number of frames. The range is 0 to 65535. The default is 1. Enter window milliseconds to set the a window and period of time during which error frames are counted. The range is 10 to 600 and represents the number of milliseconds in a multiple of 100. The default is 100.
Step 6	ethernet oam link-monitor frame-period { threshold { high { high-frames \| none } \| low { low-frames }} \| window frames }	(Optional) Configure high and low thresholds for the error-frame period that triggers an error-frame-period link event. Enter threshold high high-frames to set a high threshold in number of frames. The range is 1 to 65535. You must enter a high threshold. Enter threshold high none to disable the high threshold. Enter threshold low low-frames to set a low threshold in number of frames. The range is 0 to 65535. The default is 1. Enter window frames to set the a polling window size in number of frames. The range is 1 to 65535; each value is a multiple of 10000 frames. The default is 1000.
Step 7	ethernet oam link-monitor frame-seconds { threshold { high { high-seconds \| none } \| low { low-seconds }} \| window milliseconds }	(Optional) Configure frame-seconds high and low thresholds for triggering an error-frame-seconds link event. Enter threshold high high-seconds to set a high threshold in number of seconds. The range is 1 to 900. You must enter a high threshold. Enter threshold high none to disable the high threshold. Enter threshold low low-frames to set a low threshold in number of frames. The range is 1 to 900. The default is 1. Enter window frames to set the a polling window size in number of frames. The range is 100 to 9000; each value is a multiple of 100 milliseconds. The default is 1000.
Step 8	ethernet oam link-monitor high threshold action error-disable-interface	(Optional) Configure the switch to put an interface in an error disabled state when a high threshold for an error is exceeded.
Step 9	exit	Return to global configuration mode.
Step 10	interface interface-id	Define an Ethernet OAM interface, and enter interface configuration mode.
Step 11	source-template template-name	Associate the template to apply the configured options to the interface.
Step 12	end	Return to privileged EXEC mode.
Step 13	show ethernet oam status [ interface interface-id ]	Verify the configuration.
Step 14	copy running-config startup-config	(Optional) Save your entries in the configuration file.

The switch does not support monitoring egress frames with CRC errors. The ethernet oam link-monitor transmit-crc { threshold { high { high-frames | none } | low { low-frames }} | window milliseconds } command is visible on the switch and you can enter it, but it is not supported. Use the no form of each command to remove the option from the template. Use the no source-template template-name to remove the source template association.

Displaying Ethernet OAM Protocol Information

You can use the privileged EXEC commands in Table 48-4 to display Ethernet OAM protocol information.

Table 48-4 Displaying Ethernet OAM Protocol Information
Command	Purpose
show ethernet oam discovery [ interface interface-id ]	Displays discovery information for all Ethernet OAM interfaces or the specified interface.
show ethernet oam statistics [ interface interface-id ]	Displays detailed information about Ethernet OAM packets.
show ethernet oam status [ interface interface-id ]	Displays Ethernet OAM configuration for all interfaces or the specified interface.
show ethernet oam summary	Displays active Ethernet OAM sessions on the switch.

Understanding E-LMI

Ethernet Local Management Interface (E-LMI) is a protocol between the customer-edge (CE) device and the provider-edge (PE) device. It runs only on the PE-to-CE UNI link and notifies the CE device of connectivity status and configuration parameters of Ethernet services available on the CE port. E-LMI interoperates with an OAM protocol, such as CFM, that runs within the provider network to collect OAM status. CFM runs at the provider maintenance level (UPE to UPE with up MEPs at the UNI).

OAM manager, which streamlines interaction between any two OAM protocols, handles the interaction between CFM and E-LMI. This interaction is unidirectional, running only from OAM manager to E-LMI on the UPE side of the switch. Information is exchanged either as a result of a request from E-LMI or triggered by OAM when it received notification of a change from the OAM protocol. This type of information is relayed:

Remote UNI name and status
Remote UNI counts

E-LMI can be used to pass information on any service outage over a pseudowire to the remote end. For example:

In a CE-PE-PE-CE setup the PE devices act as MPLS devices and have an xconnect running between them. E-LMI is enabled on the CE devices. Any EVC status change will be notified to the remote CE using E-LMI messages over the pseudowire.

The ME 3800X and ME 3600X switch can be only a customer-edge device.

Configuring E-LMI

Most E-LMI configuration occurs on the PE switch on the interfaces connected to the CE device. On the CE switch, you only need to enable E-LMI on the connecting interface.

The switch supports only E-LMI-CE configuration.

Default E-LMI Configuration

Ethernet LMI is globally disabled by default.

When you globally enable E-LMI by entering the ethernet lmi global global configuration command, it is automatically enabled on all interfaces. You can also enable or disable E-LMI per interface to override the global configuration. The E-LMI command that is given last is the command that has precedence.

There are no UNIs defined. UNI bundling service is bundling with multiplexing.

E-LMI Configuration Guidelines

The switch supports E-LMI only for the customer edge. The provider side of the connection must be running CFM and E-LMI.

E-LMI is not supported on routed ports, EtherChannel port channels or ports that belong to an EtherChannel.
You cannot configure E-LMI on VLAN interfaces.
You must enter the ethernet lmi ce global configuration command to enable the switch or interface in customer-edge mode.

Enabling E-LMI

You can enable E-LMI globally or on an interface and configure the switch as a CE device. Beginning in privileged EXEC mode, follow these steps to enable for E-LMI on the switch or on an interface. Note that the order of the global and interface commands determines the configuration. The command that is entered last has precedence.

	Command	Purpose
Step 1	configure terminal	Enter global configuration mode.
Step 2	ethernet lmi global	Globally enable E-LMI on all interfaces.
Step 3	ethernet lmi ce	Configure the switch as an E-LMI CE device.
Step 4	interface interface-id	Define an interface to configure as an E-LMI interface, and enter interface configuration mode.
Step 5	ethernet lmi interface	Configure Ethernet LMI on the interface. If E-LMI is enabled globally, it is enabled on all interfaces unless you disable it on specific interfaces. If E-LMI is disabled globally, you can use this command to enable it on specified interfaces.
Step 6	ethernet lmi { n391 value \| n393 value \| t391 value \| t392 value }	Configure E-LMI parameters for the UNI. The keywords have these meanings: n391 value —Set the event counter on the customer equipment. The counter polls the status of the UNIs. The range is from 1 to 65000; the default is 360. n393 value —Set the event counter for the metro Ethernet network. The range is from 1 to 10; the default is 4. t391 value —Set the polling timer on the customer equipment. A polling timer sends status enquiries and when status messages are not received, records errors. The range is from 5 to 30 seconds; the default is 10 seconds. t392 value —Set the polling verification timer for the metro Ethernet network or the timer to verify received status inquiries. The range is from 5 to 30 seconds, or enter 0 to disable the timer. The default is 15 seconds. Note The t392 keyword is not supported when the switch is in CE mode.
Step 7	end	Return to privileged EXEC mode.
Step 8	show ethernet lmi	Verify the configuration.
Step 9	copy running-config startup-config	(Optional) Save your entries in the configuration file.

Use the no ethernet lmi global configuration command to globally disable E-LMI. Use the no form of the ethernet lmi interface configuration command with keywords to disable E-LMI on the interface or to return the timers to the default settings.

Use the show ethernet lmi commands to display information that was sent to the CE from the status request poll. Use the show ethernet service commands to show current status on the device.

Customer-Edge Device Configuration

This example shows the commands necessary to configure E-LMI on the CE device. The switch can only be configured as the CE device. The example enables E-LMI globally, but you can also enable it only on a specific interface.

Switch# config t

Switch(config)# ethernet lmi global

Switch(config)# ethernet lmi ce

Switch(config)# exit

Note For E-LMI to work, any VLANs used on the PE device must also be created on the CE device. Create a VLAN by entering the vlan vlan-id global configuration command on the CE device, where the vlan-ids match those on the PE device and configure these VLANs as allowed VLANs by entering the switchport trunk allowed vlan vlan-ids interface configuration command. Allowed VLANs can receive and send traffic on the interface in tagged format when in trunking mode.

Displaying E-LMI

You can use the privileged EXEC commands in Table 48-5 to display E-LMI information.

Table 48-5 Displaying E-LMI and OAM Manager Information
Command	Purpose
show ethernet lmi statistics interface interface-id	Displays Ethernet LMI interface statistics sent to the CE from the status request poll.
show ethernet lmi uni map interface [ interface-id ]	Displays information about the E-LMI UNI VLAN map sent to the CE from the status request poll.

Ethernet CFM and Ethernet OAM Interaction

When the Ethernet OAM Protocol is running on an interface that has CFM MEPs configured, Ethernet OAM informs CFM of the state of the interface. Interaction is unidirectional from the Ethernet OAM to the CFM Protocol, and the only information exchanged is the user network interface port status.

The Ethernet OAM Protocol notifies CFM when these conditions occur:

Error thresholds are crossed at the local interface.

CFM responds to the notification by sending a port status of Local_Excessive_Errors in the Port StatusType Length Value (TLV).

Ethernet OAM receives an OAMPDU from the remote side showing that an error threshold is exceeded on the remote endpoint.

CFM responds to the notification by sending a port status of Remote_Excessive_Errors in the Port Status TLV.

The local port is set into loopback mode.

CFM responds by sending a port status of Test in the Port Status TLV.

The remote port is set into loopback mode.

CFM responds by sending a port status of Test in the Port Status TLV.

This section includes this information:

For more information about CFM and interaction with Ethernet OAM, see the Ethernet Connectivity Fault Management feature module.

Enabling Ethernet OAM

Beginning in privileged EXEC mode, follow these steps to enable Ethernet OAM on an interface.

	Command	Purpose
Step 1	configure terminal	Enter global configuration mode.
Step 2	interface interface-id	Define an interface to configure as an Ethernet OAM interface and enter interface configuration mode.
Step 3	ethernet oam [ max-rate oampdus \| min-rate seconds \| mode { active \| passive } \| timeout seconds ]	Enable Ethernet OAM on the interface (Optional) Enter max-rate oampdus t o set the maximum rate (per second) to send OAM PDUs. The range is 1 to 10 PDUs per second; the default is 10. (Optional) Enter min-rate seconds to set the minimum rate in seconds.The range is 1 to 10 seconds. (Optional) Set the OAM client mode as active or passive. The default is active. (Optional) Enter timeout seconds to set the time after which a device declares the OAM peer to be nonoperational and resets its state machine. The range is 2 to 30 seconds; the default is 5 seconds.
Step 4	end	Return to privileged EXEC mode.
Step 5	copy running-config startup-config	(Optional) Save your entries in the configuration file.
Step 6	show ethernet cfm maintenance points remote	(Optional) Display the port states as reported by Ethernet OAM.

Ethernet OAM and CFM Configuration Example

These are example configurations of the interworking between Ethernet OAM and CFM in a sample service provider network with a provider-edge switch connected to a customer edge switch at each endpoint. You must configure CFM and Ethernet OAM between the customer edge and the provider edge switch.

Customer-edge switch 1 (CE1) configuration:

Switch# config t

Switch(config)# interface gigabitethernet0/1

Switch(config-if)# switchport trunk allowed vlan 10

Switch(config-if)# switchport mode trunk

Switch(config-if)# ethernet oam remote-loopback supported

Switch(config-if)# ethernet oam

Switch(config-if)# exit

Provider-edge switch 1 (PE1) configuration:

Switch# config t

Switch(config)# interface gigabitethernet0/5

Switch(config-if)# switchport trunk encapsulation dot1q

Switch(config-if)# switchport mode trunk

Switch(config-if)# ethernet cfm mip level 7

Switch(config-if)# ethernet cfm mep level 4 mpid 100 vlan 10

Switch(config-if)# ethernet uni id 2004-20

Switch(config-if)# ethernet oam remote-loopback supported

Switch(config-if)# ethernet oam

Switch(config-if-srv)# exit

Provider-edge switch 2 (PE2) configuration:

Switch# config t

Switch(config)# interface gigabitethernet1/20

Switch(config-if)# switchport mode trunk

Switch(config-if)# ethernet cfm mip level 7

Switch(config-if)# ethernet cfm mep level 4 mpid 101 vlan 10

Switch(config-if)# ethernet uni id 2004-20

Switch(config-if)# ethernet oam remote-loopback supported

Switch(config-if)# ethernet oam

Switch(config-if-srv)# exit

Customer-edge switch 2 (CE2) configuration:

Switch# config t

Switch(config)# interface gigabitethernet0/1

Switch(config-if)# switchport trunk allowed vlan 10

Switch(config-if)# switchport mode trunk

Switch(config-if)# ethernet oam remote-loopback supported

Switch(config-if)# ethernet oam

Switch(config-if)# exit

These are examples of the output showing provider-edge switch port status of the configuration. Port status shows as UP at both switches.

Switch PE1:

Switch# show ethernet cfm maintenance points remote

MPID Level Mac Address Vlan PortState InGressPort Age(sec) Service ID

101 * 4 0015.633f.6900 10 UP Gi0/1 27 blue

Switch PE2:

Switch# show ethernet cfm maintenance points remote

MPID Level Mac Address Vlan PortState InGressPort Age(sec) Service ID

100 * 4 0012.00a3.3780 10 UP Gi0/1 8 blue

Total Remote MEPs: 1

This example shows the outputs when you start remote loopback on CE1 (or PE1). The port state on the remote PE switch shows as Test and the remote CE switch goes into error-disable mode.

Switch# ethernet oam remote-loopback start interface gigabitEthernet 0/1

This is a intrusive loopback.

Therefore, while you test Ethernet OAM MAC connectivity,

you will be unable to pass traffic across that link.

Proceed with Remote Loopback? [confirm]

Switch PE1:

Switch# show ethernet cfm maintenance points remote

MPID Level Mac Address Vlan PortState InGressPort Age(sec) Service ID

101 * 4 0015.633f.6900 10 UP Gi0/1 27 blue

Switch PE2:

Switch# show ethernet cfm maintenance points remote

MPID Level Mac Address Vlan PortState InGressPort Age(sec) Service ID

100 * 4 0012.00a3.3780 10 TEST Gi1/1/1 8 blue

Total Remote MEPs: 1

In addition, if you shut down the CE1 interface that connects to PE1, the remote PE2 port will show a PortState of Down.

Note Also see the Configuring Y.1731 Performance Monitoring feature guide for related information.

Was this Document Helpful?

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)