Specifications

17-51
System Management Software Configuration Guide for Cisco IE 2000U and Connected Grid Switches
Chapter 17 Configuring Ethernet OAM, CFM, and E-LMI
Information About E-LMI
EXAMPLE
This example shows how to configure an Ethernet terminal loopback to test QoS on the interface, to swap
the MAC source and destination addresses, to time out after 30 seconds, and to start the loopback
process:
Switch(config)# interface gigabitethernet 0/1
Switch(config-if)# ethernet loopback terminal mac-address swap timeout 30 supported
Switch(config-if)# end
Switch# ethernet loopback start gigabitethernet 0/1
Information About 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). E-LMI
relies on the OAM Ethernet Infrastructure to interwork with CFM for end-to-end status of Ethernet
virtual connections (EVCs) across CFM domains.
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:
EVC name and availability status
Remote UNI name and status
Remote UNI counts
You can configure Ethernet virtual connections (EVCs), service VLANs, UNI ids (for each CE-to-PE
link), and UNI count and attributes. You need to configure CFM to notify the OAM manager of any
change to the number of active UNIs and or the remote UNI ID for a given S-VLAN domain.
You can configure the switch as either the customer-edge device or the provider-edge device.
E-LMI Interaction with OAM Manager
No interactions are required between E-LMI and OAM manager on the CE side. On the UPE side, OAM
manager defines an abstraction layer that relays data collected from OAM protocols (in this case CFM)
running within the metro network to the E-LMI switch. The information flow is unidirectional (from
OAM manager to the E-LMI) but is triggered in one of two ways:
Synchronous data flow triggered by a request from the E-LMI
Asynchronous data flow triggered by OAM manager when it receives notification from CFM that
the number of remote UNIs has changed
This data includes:
EVC name and availability status (active, not active, partially active, or not defined)
Remote UNI name and status (up, disconnected, administratively down, excessive FCS failures, or
not reachable)