 Feedback
|
Table Of Contents
Ethernet Local Management Interface at a Provider Edge
Prerequisites for Ethernet Local Management Interface at a Provider Edge
Restrictions for Ethernet Local Management Interface at a Provider Edge
Information About Ethernet Local Management Interface at a Provider Edge
Benefits of Ethernet LMI at a Provider Edge
How to Configure Ethernet Local Management Interface at a Provider Edge
Ethernet LMI Interaction with CFM
Displaying Ethernet LMI and OAM Manager Information
Configuration Examples for Ethernet Local Management Interface at a Provider Edge
Ethernet OAM Manager on a PE Device Configuration: Example
Ethernet OAM Manager on a CE Device Configuration: Example
show ethernet service instance
show ethernet service interface
Feature Information for Ethernet Local Management Interface at a Provider Edge
Ethernet Local Management Interface at a Provider Edge
First Published: February 27, 2007Last Updated: March 2, 2007The advent of Ethernet as a metropolitan-area network (MAN) and WAN technology imposes a new set of operations, administration, and management (OAM) requirements on Ethernet's traditional operations, which had been 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.
This module provides general information about configuring Ethernet Local Management Interface (LMI), an OAM protocol, on a provider edge (PE) device.
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 Ethernet Local Management Interface at a Provider Edge" 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 Ethernet Local Management Interface at a Provider Edge
•
•
•
•
•
Prerequisites for Ethernet Local Management Interface at a Provider Edge
•
•
•
Restrictions for Ethernet Local Management Interface at a Provider Edge
•
•
Information About Ethernet Local Management Interface at a Provider Edge
To configure Ethernet LMI on a PE device, you should understand the following concepts:
•
Ethernet Virtual Circuit
An Ethernet virtual circuit (EVC) as defined by the Metro Ethernet Forum is a port level point-to-point or multipoint-to-multipoint Layer 2 circuit. EVC status can be used by a 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 OAM protocol between a CE device and a PE device. Ethernet LMI provides CE devices with the status of EVCs for large Ethernet MANs and WANs and provides information that enables CE devices to autoconfigure. Specifically, Ethernet LMI runs on the PE-CE user network interface (UNI) link and 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.
Ethernet LMI interoperates with Ethernet CFM, an OAM protocol that runs within the provider network to collect OAM status. Ethernet CFM runs at the provider maintenance level (user provider edge [UPE] to UPE at the UNI). Ethernet LMI relies on the OAM Ethernet Infrastructure (EI) to interwork with CFM to learn the end-to-end status of EVCs across CFM domains.
Ethernet LMI is disabled globally by default. When Ethernet LMI is enabled globally, all interfaces are automatically enabled. Ethernet LMI can also be enabled or disabled at the interface to override the global configuration. The last Ethernet LMI command issued is the command that has precedence. No EVCs, Ethernet service instances, or UNIs are defined, and the UNI bundling service is bundling with multiplexing.
Ethernet CFM
Ethernet CFM is an end-to-end per-service-instance (per VLAN) Ethernet layer OAM protocol that includes proactive connectivity monitoring, fault verification, and fault isolation. End-to-end CFM can be from PE device to PE device or from CE device to CE device. For more information about Ethernet CFM, see Ethernet Connectivity Fault Management.
OAM Manager
The OAM manager is an infrastructure element that streamlines interaction between OAM protocols. The OAM manager requires two interworking OAM protocols, in this case, Ethernet CFM and Ethernet LMI. No interactions are required between Ethernet LMI and the OAM manager on the CE side. On the UPE side, the OAM manager defines an abstraction layer that relays data collected from Ethernet CFM to the Ethernet LMI device.
Ethernet LMI and OAM manager interaction is unidirectional, from the OAM manager to Ethernet LMI on the UPE side of the device. An information exchange results from an Ethernet LMI request or is triggered by the OAM manager when it receives notification from the OAM protocol that the number of UNIs has changed. A change in the number of UNIs may cause a change in EVC status.
The OAM manager calculates EVC status given the number of active UNIs and the total number of associated UNIs. You must configure CFM to notify the OAM manager of all changes to the number of active UNIs or to the remote UNI ID for a given service provider VLAN (S-VLAN) domain.
The information exchanged includes the following:
•
•
•
Benefits of Ethernet LMI at a Provider Edge
Ethernet LMI on a PE device provides the following benefits:
•
•
•
How to Configure Ethernet Local Management Interface at a Provider Edge
Perform the following tasks to configure Ethernet LMI on a PE device.
•
•
Ethernet LMI Interaction with CFM
For Ethernet LMI to function with CFM, you must configure EVCs, Ethernet service instances, and Ethernet LMI customer VLAN mapping. Most of the configuration occurs on the PE device on the interfaces connected to the CE. On the CE device, you need only enable Ethernet LMI on the connecting interface. Also, you must configure some OAM parameters; for example, EVC definitions on PE devices on both sides of a metro network.
CFM and OAM interworking requires an inward facing MEP.
Configuring the OAM Manager
Note
Perform this task to configure the OAM manager on a PE device.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
DETAILED STEPS
Enabling Ethernet LMI
The order in which the global and interface configuration commands are issued determines the configuration. The last command that is issued has precedence.
Perform this task to enable Ethernet LMI on a device or on an interface.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Displaying Ethernet LMI and OAM Manager Information
Perform this task to display Ethernet LMI or OAM manager information. All the steps are optional and can be performed in any order.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Examples
The following example shows sample output from the show ethernet lmi command using the evc keyword:
Router# show ethernet lmi evcSt EVC Id Port--- ------------------------------------------------------------ --------------A EVC_MP2MP_101 Gi0/1A EVC_P2P_110 Gi0/1The following example shows sample output from the show ethernet service evc command:
R1# show ethernet service evcIdentifier Type Act-UNI-cnt Status50 MP-MP 0 NotDefinedThe following example shows sample output from the show ethernet service interface command using the detail keyword:R1# show ethernet service interface ethernet 1/3 detailInterface: Ethernet1/3ID: uni2CE-VLANS: 30EVC Map Type: BundlingAssociated EVCs:EVC-ID CE-VLAN50 30Associated Service Instances:Service-Instance-ID CE-VLAN400 30The following example shows sample output from the show ethernet service instance command using the detail keyword:R1# show ethernet service instance detailService Instance ID: 400Associated Interface: Ethernet1/3Associated EVC: 50CE-Vlans: 30State: AdminDownEFP Statistics:Pkts In Bytes In Pkts Out Bytes Out0 0 0 0Configuration Examples for Ethernet Local Management Interface at a Provider Edge
This section contains the following example:
•
•
Ethernet OAM Manager on a PE Device Configuration: Example
This example shows a sample configuration of OAM manager, CFM, and Ethernet LMI on a PE device:
Router# configure terminalRouter(config)# ethernet cfm domain Top level 7Router(config)# ethernet cfm domain Provider level 4Router(config-ether-cfm)# service customer_1 vlan 101Router(config-ether-cfm)# mep crosscheck mpid 404 vlan 101Router(config-ether-cfm)# exitRouter(config)# ethernet cfm domain Operator_level 2Router(config-ether-cfm)# service operator_1 vlan 101Router(config-ether-cfm)# exitRouter(config)# ethernet cfm enableRouter(config)# ethernet evc test1Router(config-evc)# oam protocol cfm svlan 101 domain ProviderRouter(config-evc)# exitRouter(config)# ethernet evc 101Router(config-evc)# uni count 3Router(config-evc)# oam protocol cfm svlan 101 domain OperatorRouter(config-evc)# exitRouter(config)# ethernet lmi globalRouter(config)# interface gigabitethernet 1/0/2Router(config-if)# service instance 101 ethernet test1Router(config-if-srv)# ethernet lmi ce-vlan map 101Router(config-if-srv)# exitRouter(config-if)# exitRouter(config)# ethernet cfm cc enable level 2-4 vlan 101Router(config)# exitEthernet OAM Manager on a CE Device Configuration: Example
This example shows how to configure Ethernet LMI globally on a CE device:
Router# configure terminalRouter(config)# ethernet lmi globalRouter(config)# exitAdditional References
The following sections provide references related to the Ethernet Local Management Interface at a Provider Edge Device feature.
Related Documents
Ethernet CFM
Ethernet LMI
Remote Port Shutdown feature
IEEE 802.3ah
IEEE 802.3ah Ethernet in the First Mile
Standards
MIBs
RFCs
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Command Reference
This section documents only commands that are new or modified.
•
•
debug ethernet service
To enable debugging of Ethernet customer service instances, use the debug ethernet service command privileged EXEC mode. To disable debugging, use the no form of this command.
debug ethernet service {all | api | error | evc [evc-id] | instance [id id | interface type number | qos] | interface type number | microblock | oam-mgr}
debug ethernet service {all | api | error | evc | instance | interface | microblock | oam-mgr}
Syntax Description
Command Default
Ethernet service debugging is disabled.
Command Modes
Privileged EXEC
Command History
12.2(25)SEG
This command was introduced.
12.2(33)SRB
This command was implemented on the Cisco 7600 series routers.
Usage Guidelines
The debug ethernet service command is useful for troubleshooting. The undebug ethernet service command is the same as the no debug ethernet service command.
When you use the evc keyword without specifying an EVC ID, debugging is enabled for all EVCs on the system.
When you use the instance keyword without specifying options, debugging for all service instances is enabled. If a service instance ID and interface are specified, only debug messages for the associated service instance are displayed. If only an interface is specified, debug messages for all service instances on that interface only are displayed.
Examples
The following example shows output after issuing the debug ethernet service all command:
Router# debug ethernet service allEthernet service error debugging is onEthernet service api debugging is onEthernet service interface debugging is onEthernet service instance debugging is onEthernet service instance qos debugging is onEthernet service evc debugging is onEthernet service OAM Manager debugging is onRelated Commands
show debugging
Displays information about the types of debugging that are enabled.
ethernet evc
To define an Ethernet virtual connection (EVC) and to enter EVC configuration mode, use the ethernet evc command in global configuration mode. To delete the EVC, use the no form of this command.
ethernet evc evc-id
no ethernet evc evc-id
Syntax Description
Command Default
No EVCs are defined.
Command Modes
Global configuration
Command History
12.2(25)SEG
This command was introduced.
12.2(33)SRB
This command was implemented on the Cisco 7600 series routers.
Usage Guidelines
After you enter the ethernet evc command, the device enters EVC configuration mode and the following configuration commands are available:
•
•
•
•
•
Examples
The following example shows how to define an EVC named test1 and to enter EVC configuration mode:
Router(config)# ethernet evc test1Router(config-evc)#Related Commands
ethernet lmi ce-vlan map
To configure Ethernet Local Management Interface (LMI) parameters, use the ethernet lmi ce-vlan map command in Ethernet service configuration mode. To remove the configuration, use the no form of this command.
ethernet lmi ce-vlan map {vlan-id [untagged] | any | default | untagged}
no ethernet lmi ce-vlan map {vlan-id | any | default | untagged}
Syntax Description
Command Default
No Ethernet LMI mapping parameters are defined.
Command Modes
Ethernet service configuration
Command History
12.2(25)SEG
This command was introduced.
12.2(33)SRB
This command was implemented on the Cisco 7600 series routers.
Usage Guidelines
If you intend to use the ethernet lmi ce-vlan map any command, you must first configure all-to-one bundling on the interface.
Use this command to configure an Ethernet LMI customer VLAN-to-EVC map for a particular user-network interface (UNI).
Ethernet LMI mapping parameters are related to the bundling characteristics set by entering the ethernet uni command in interface configuration mode.
•
•
•
•
Examples
The following example shows how to configure an Ethernet LMI customer VLAN-to-EVC map to test customer VLAN 101 in service instance 333 on the interface:
Router(config)# interface ethernet 2/1Router(config-if)# service instance 333 ethernet testRouter(config-if-srv)# ethernet lmi ce-vlan map 101Related Commands
ethernet uni
To set user-network interface (UNI) bundling attributes, use the ethernet uni command in interface configuration mode. To return to the default bundling configuration, use the no form of this command.
ethernet uni [bundle [all-to-one] | id uni-id | multiplex]
no ethernet uni
Syntax Description
Command Default
If bundling or multiplexing attributes are not configured, the default is bundling with multiplexing. The UNI then has one or more EVCs with one or more CE VLANs mapped to each EVC.
Command Modes
Interface configuration
Command History
12.2(25)SEG
This command was introduced.
12.2(33)SRB
This command was implemented on the Cisco 7600 series routers.
Usage Guidelines
UNI options determine the functionality that the interface has regarding bundling VLANs and multiplexing EVCs.
If you want only the bundling or only the multiplexing service, you must configure the service appropriately. Bundling supports only one EVC at the UNI with one or multiple customer edge (CE)-VLAN IDs mapped to the EVC.
When multiplexing is configured, the UNI can have one or more EVCs with a single CE-VLAN ID mapped to each EVC.
When you configure a UNI ID on a port, that ID is used as the default name for all maintenance end points (MEPs) configured on the port.
You must enter the ethernet uni command with the id keyword and id argument on all ports that are directly connected to CE devices. When the specified ID is not unique on a device, an error message is displayed.
When you configure, change, or remove a UNI service type, the EVC and CE-VLAN ID configurations are checked to ensure that the configurations and the UNI service types match. If the configurations do not match, the command is rejected.
Examples
The following example shows how to configure bundling without multiplexing:
Router(config)# interface ethernet 2/1Router(config-if)# ethernet uni bundleThis example shows how to identify a UNI as test2:
Router(config)# interface ethernet 2/1Router(config-if)# ethernet uni id test2Related Commands
show ethernet service interface
Displays information about Ethernet service instances on an interface, including service type.
oam protocol
To specify an operations, maintenance, and administration (OAM) protocol for an Ethernet virtual connection (EVC), use the oam protocol command in EVC configuration mode. To remove an OAM protocol configuration for an EVC, use the no form of this command.
oam protocol {cfm svlan svlan-id domain domain-name | ldp}
no oam protocol
Syntax Description
Command Default
An OAM protocol is not specified.
Command Modes
EVC configuration
Command History
Usage Guidelines
Use this command to specify the OAM protocol to use for communicating link status in an Ethernet over Multiprotocol Label Switching (EoMPLS) network.
Examples
The following example shows how to specify CFM as the OAM protocol:
Router(config)# ethernet evc evc10Router(config-evc)# oam protocol cfm svlan 10 domain cstmrservice instance ethernet
To configure an Ethernet service instance on an interface and to enter Ethernet service configuration mode, use the service instance ethernet command in interface configuration mode. To delete a service instance, use the no form of this command.
service instance id ethernet [evc-id]
no service instance id
Syntax Description
Command Default
No Ethernet service instances are defined.
Command Modes
Interface configuration
Command History
12.2(25)SEG
This command was introduced.
12.2(33)SRB
This command was implemented on the Cisco 7600 series routers.
Usage Guidelines
After you enter the service instance ethernet command, the device enters Ethernet service configuration mode, and these configuration commands are available:
•
•
•
•
Examples
The following example shows how to define an Ethernet service instance and to enter Ethernet service configuration mode for an EVC:
Router(config-if)# service instance 333 ethernet testRouter(config-if-srv)#Related Commands
show ethernet service instance
Displays information about configured Ethernet service instances.
show ethernet service evc
To display information about Ethernet virtual connections (EVCs), use the show ethernet service evc command in privileged EXEC mode.
show ethernet service evc [detail | id evc-id [detail] | interface type number [detail]]
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(25)SEG
This command was introduced.
12.2(33)SRB
This command was implemented on the Cisco 7600 series routers.
Usage Guidelines
This command is useful for system monitoring and troubleshooting.
Examples
Following is sample output from the show ethernet service evc command:
Router# show ethernet service evcIdentifier Type Act-UNI-cnt StatusBLUE P-P 2 ActivePINK MP-MP 2 PartiallyActivePURPLE P-P 2 ActiveBROWN MP-MP 2 ActiveGREEN P-P 3 ActiveYELLOW MP-MP 2 PartiallyActiveBANANAS P-P 0 InActiveTEST2 P-P 0 NotDefinedORANGE P-P 2 ActiveTEAL P-P 0 InActiveTable 1 describes the significant fields in the output.
Related Commands
show ethernet service instance
To display information about Ethernet customer service instances, use the show ethernet service instance command in privileged EXEC mode.
show ethernet service instance [detail | id id | interface type number | policy-map | stats]
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(25)SEG
This command was introduced.
12.2(33)SRB
This command was implemented on the Cisco 7600 series routers.
Usage Guidelines
This command is useful for system monitoring and troubleshooting.
Examples
Following is an example of output from the show ethernet service instance command:
Router# show ethernet service instanceIdentifier Interface CE-Vlans222 FastEthernet0/1 untagged,1-409410 FastEthernet0/2222 FastEthernet0/2 200333 FastEthernet0/2 default10 FastEthernet0/3 30011 FastEthernet0/310 FastEthernet0/4 30010 FastEthernet0/6 untagged,1-409410 FastEthernet0/7 untagged,1-409410 FastEthernet0/8 untagged,1-409410 FastEthernet0/9 untagged20 FastEthernet0/9222 FastEthernet0/11 300-350,900-999333 FastEthernet0/11 100-200,1000,1999-4094222 FastEthernet0/12 20333 FastEthernet0/12 1010 FastEthernet0/13 1020 FastEthernet0/13 2030 FastEthernet0/13 30200 FastEthernet0/13 222200 FastEthernet0/14 200,222300 FastEthernet0/14 333555 FastEthernet0/14 555Table 2 describes the significant fields in the output.
Related Commands
show ethernet service interface
To display interface-only information about Ethernet customer service instances for all interfaces or for a specified interface, use the show ethernet service interface in privileged EXEC mode.
show ethernet service interface [type number] [detail]
Syntax Description
type
(Optional) Type of interface.
number
(Optional) Number of the interface.
detail
(Optional) Displays detailed information about interfaces or a specified service instance ID or interface.
Command Modes
Privileged EXEC
Command History
12.2(25)SEG
This command was introduced.
12.2(33)SRB
This command was implemented on the Cisco 7600 series routers.
Usage Guidelines
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output are not displayed, but the lines that contain "Output" are displayed.
Examples
Following are examples of output from the show ethernet service interface command:
Router# show ethernet service interface gigabitethernet0/1Interface IdentifierGigabitEthernet0/1 PE2-G101Router# show ethernet service interface detailInterface: FastEthernet0/1ID:CE-VLANS:EVC Map Type: Bundling-MultiplexingInterface: FastEthernet0/2ID:CE-VLANS:EVC Map Type: Bundling-MultiplexingInterface: FastEthernet0/3ID:CE-VLANS:EVC Map Type: Bundling-Multiplexing<output truncated>Interface: GigabitEthernet0/1ID: PE2-G101CE-VLANS: 10,20,30EVC Map Type: Bundling-MultiplexingAssociated EVCs:EVC-ID CE-VLANWHITE 30RED 20BLUE 10Associated Service Instances:Service-Instance-ID CE-VLAN10 1020 2030 30Table 3 describes the significant fields in the output.
Related Commands
uni count
To set the user-network interface (UNI) count for an Ethernet virtual connection (EVC), use the uni count command in EVC configuration mode. To return to the default setting, use the no form of this command.
uni count value [multipoint]
no uni count
Syntax Description
Command Default
The UNI count defaults to 2 and the service defaults to point-to-point service.
Command Modes
EVC configuration
Command History
12.2(25)SEG
This command was introduced.
12.2(33)SRB
This command was implemented on the Cisco 7600 series routers.
Usage Guidelines
The UNI count determines the type of service in the EVC.
•
•
•
You should know the correct number of maintenance end points (MEPs) in the domain. If you enter a UNI count value greater than the number of endpoints, the UNI status shows as partially active even if all endpoints are up. If you enter a UNI count less than the number of endpoints, UNI status shows as active, even if all endpoints are not up.
Caution
Examples
The following example shows how to set a UNI count of 2 with point-to-multipoint service:
Router(config)# ethernet evc test1Router(config-evc)# uni count 2 multipointRelated Commands
Feature Information for Ethernet Local Management Interface at a Provider Edge
Table 4 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS 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
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.
