Table Of Contents
Enabling Ethernet Local Management Interface
Contents
Prerequisites for Enabling Ethernet Local Management Interface
Restrictions for Enabling Ethernet Local Management Interface
Information About Enabling Ethernet Local Management Interface
EVC
Ethernet LMI
Benefits of Ethernet LMI
How to Enable Ethernet Local Management Interface
Enabling Ethernet LMI on All Supported Interfaces
Enabling Ethernet LMI on a Single Supported Interface
Configuration Examples for Ethernet Local Management Interface
Enabling Ethernet LMI on All Supported Interfaces: Example
Enabling Ethernet LMI on a Single Supported Interface: Example
Additional References
Related Documents
Standards
MIBs
RFCs
Technical Assistance
Feature Information for Enabling Ethernet Local Management Interface
Glossary
Enabling Ethernet Local Management Interface
First Published: June 19, 2006
Last Updated: October 7, 2009
Ethernet Local Management Interface (LMI) is an Ethernet layer operation, administration, and management (OAM) protocol. It provides information that enables autoconfiguration of customer edge (CE) devices and provides the status of Ethernet virtual connections (EVCs) for large Ethernet metropolitan-area networks (MANs) and WANs. Specifically, Ethernet LMI notifies a CE device of the operating state of an EVC and the time when an EVC is added or deleted. Ethernet LMI also communicates the attributes of an EVC and a user-network interface (UNI) to a CE device.
The advent of Ethernet as a MAN and WAN technology imposes a new set of OAM requirements on Ethernet's traditional operations, which were centered on enterprise networks only. The expansion of Ethernet technology into the domain of service providers, where networks are substantially larger and more complex than enterprise networks and the user-base is wider, makes operational management of link uptime crucial. More importantly, the timeliness in isolating and responding to a failure becomes mandatory for normal day-to-day operations, and OAM translates directly to the competitiveness of the service provider.
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for Enabling Ethernet Local Management Interface" section.
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS 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 Enabling Ethernet Local Management Interface
•
Restrictions for Enabling Ethernet Local Management Interface
•
Information About Enabling Ethernet Local Management Interface
•
How to Enable Ethernet Local Management Interface
•
Configuration Examples for Ethernet Local Management Interface
•
Additional References
•
Feature Information for Enabling Ethernet Local Management Interface
•
Glossary
Prerequisites for Enabling Ethernet Local Management Interface
Business Requirements
•
Ethernet OAM such as connectivity fault management (CFM) must be implemented and operational on the service provider's network.
Restrictions for Enabling Ethernet Local Management Interface
•
Ethernet LMI relies on Ethernet CFM for the status of an EVC, the remote UNI identifier associated with an EVC, and remote UNI status.
•
Ethernet LMI CE is available only on routing ports on routing platforms. For information about Ethernet LMI PE functionality on switching platforms, see the "Configuring Ethernet CFM and E-LMI" chapter of the Cisco ME 3400 Switch Software Configuration Guide, Release 12.2(25)SEG.
•
Ethernet LMI in the Cisco IOS Software Release 12.4(9)T does not support autoconfiguration of CE devices.
Information About Enabling Ethernet Local Management Interface
Before you set up Ethernet LMI, you should understand the following concepts:
•
EVC
•
Ethernet LMI
EVC
An EVC as defined by the Metro Ethernet Forum could be a port level point-to-point or multipoint-to-multipoint Layer 2 circuit. EVC status can be used by the CE device to find an alternative path in to the service provider network or in some cases, fall back to a backup path over Ethernet or another alternative service such as Frame Relay or ATM.
Ethernet LMI
Ethernet LMI is an Ethernet layer OAM protocol between a CE device and the PE in large Ethernet MANs and WANs. It provides information that enables service providers to autoconfigure CE devices with service parameters and parameter changes from a user provider edge (UPE) device.
Figure 1 shows where in a network Ethernet LMI functions.
Figure 1
Position in the Network Where Ethernet LMI Functions
LMI also provides the status of Ethernet EVCs in large Ethernet MANs and WANs to the CE. Specifically, Ethernet LMI notifies a CE device of the operating state of an EVC and the time when an EVC is added or deleted. Ethernet LMI also communicates EVC and UNI attributes to a CE device.
The Ethernet LMI protocol includes the following procedures, as defined by the MEF 16 Technical Specification:
•
Notifying the CE when an EVC is added
•
Notifying the CE when an EVC is deleted
•
Notifying the CE of the availability state of a configured EVC (Active, Not Active, or Partially Active)
•
Communicating UNI and EVC attributes to the CE
Benefits of Ethernet LMI
Ethernet LMI provides the following benefits:
•
Communication of end-to-end status of the EVC to the CE device
•
Communication of EVC and UNI attributes to a CE device
•
Competitive advantage for service providers
How to Enable Ethernet Local Management Interface
To enable Ethernet LMI, perform the following tasks:
•
Enabling Ethernet LMI on All Supported Interfaces
•
Enabling Ethernet LMI on a Single Supported Interface
Enabling Ethernet LMI on All Supported Interfaces
Perform this task to enable Ethernet LMI on all supported interfaces on a device.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ethernet lmi global
4.
end
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
|
Puts the CLI in global configuration mode.
|
Step 3
|
ethernet lmi global
Example:
Router(config)# ethernet lmi global
|
Enables Ethernet LMI on all supported interfaces on the device.
|
Step 4
|
end
Example:
Router# end
|
Returns the CLI to privileged EXEC mode.
|
Enabling Ethernet LMI on a Single Supported Interface
Perform the steps in this task to enable Ethernet LMI on a specific supported interface.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number
4.
ethernet lmi interface
5.
end
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
|
Puts the CLI in global configuration mode.
|
Step 3
|
interface type number
Example:
Router(config)# interface ethernet 0/0
|
Specifies an interface and puts the CLI in interface configuration mode.
|
Step 4
|
ethernet lmi interface
Example:
Router(config-if)# ethernet lmi interface
|
Enables Ethernet LMI on the interface.
|
Step 5
|
end
Example:
Router# end
|
Returns the CLI to privileged EXEC mode.
|
Configuration Examples for Ethernet Local Management Interface
The examples in this section show the configurations that enable Ethernet LMI on all interfaces on a CE device (globally) and on a specific interface on a CE device.
•
Enabling Ethernet LMI on All Supported Interfaces: Example
•
Enabling Ethernet LMI on a Single Supported Interface: Example
Enabling Ethernet LMI on All Supported Interfaces: Example
The following example shows how to enable Ethernet LMI on all supported interfaces on a device:
Enter configuration commands, one per line. End with CNTL/Z.
00:06:33: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/0, changed p
Enabling Ethernet LMI on a Single Supported Interface: Example
The following example shows how to enable Ethernet LMI on a single interface:
Enter configuration commands, one per line. End with CNTL/Z.
00:05:51: %SYS-5-CONFIG_I: Configured from console by console
Additional References
The following sections provide references related to enabling Ethernet Local Management Interface.
Related Documents
Standards
MIBs
MIB
|
MIBs Link
|
No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature.
|
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
|
Feature Information for Enabling Ethernet Local Management Interface
Table 1 lists the feature 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 and Catalyst OS 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 train 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 also support that feature.
Table 1 Feature Information for Enabling Ethernet Local Management Interface
Feature Name
|
Releases
|
Feature Information
|
Ethernet Local Management Interface
|
12.4(9)T 12.2(33)SRB 12.4(15)T2
|
Ethernet LMI is an Ethernet layer OAM protocol. It provides information that enables autoconfiguration of CE devices and provides the status of EVCs for large Ethernet MANs and WANs.
This feature was implemented on the Cisco 7600 router in Cisco IOS Release 12.2(33)SRB.
The following commands were introduced or modified: clear ethernet lmi statistics, debug ethernet lmi, ethernet lmi, ethernet lmi global, ethernet lmi interface, show ethernet lmi
|
Glossary
CE—customer edge. Edge equipment on the customer side of a user-network interface (UNI).
CE-VLAN ID—Identifier of a CE-VLAN.
E-LMI—Ethernet Local Management Interface. An Ethernet layer OAM protocol. It provides information that enables autoconfiguration of CE devices and provides the status of Ethernet virtual connections (EVCs) for large Ethernet MANs and WANs.
EVC—Ethernet virtual connection. An association of two or more user-network interfaces.
OAM—operations, administration, and maintenance. A term used by several standards bodies to describe protocols and procedures for operating, administrating, and maintaining networks. Examples are ATM OAM and IEEE Std. 802.3ah OAM.
PE—provider edge. Edge equipment on the service provider side of a user-network interface (UNI).
UNI—user-network interface. A common term for a bridge portion an operator's bridge that is connected to customer equipment. A UNI often includes a C-VLAN-aware bridge component. The term UNI is used broadly in the IEEE P802.1ag/D5.2 standard when the purpose for various features of LMI are explained.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Pulse, 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, and Flip Gift Card 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 Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Fast Step, Follow Me Browsing, FormShare, GainMaker, GigaDrive, HomeLink, iLYNX, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, 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. (0908R)
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.
© 2006-2009 Cisco Systems, Inc. All rights reserved.