Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring Ethernet Local Management Interface

Ethernet Local Management Interface Overview

MX Series routers with Gigabit Ethernet (ge), 10-Gigabit Ethernet (xe), or Aggregated Ethernet (ae) interfaces support the Ethernet Local Management Interface (E-LMI). The E-LMI specification is available at the Metro Ethernet Forum. E-LMI procedures and protocols are used for enabling automatic configuration of the customer edge (CE) to support Metro Ethernet services. The E-LMI protocol also provides user-to-network interface (UNI) and Ethernet virtual connection (EVC) status information to the CE. The UNI and EVC information enables automatic configuration of CE operation based on the Metro Ethernet configuration.

The E-LMI protocol operates between the CE device and the provider edge (PE) device. It runs only on the PE-CE link and notifies the CE of connectivity status and configuration parameters of Ethernet services available on the CE port. The scope of the E-LMI protocol is shown in Figure 1.

Figure 1: Scope of the E-LMI Protocol

The E-LMI implementation on MX Series routers includes only the PE side of the E-LMI protocol.

E-LMI interoperates with an OAM protocol, such as Connectivity Fault Management (CFM), that runs within the provider network to collect OAM status. CFM runs at the provider maintenance level (UNI-N to UNI-N with up MEPs at the UNI). E-LMI relies on the CFM for end-to-end status of EVCs across CFM domains (SVLAN domain or VPLS).

• Notification to the CE of the addition/deletion of an EVC (active, not active, or partially active)
• Notification to the CE of the availability state of a configured EVC
• Communication of UNI and EVC attributes to the CE:
  • UNI attributes:
    • UNI identifier (a user-configured name for UNI)
    • CE-VLAN ID/EVC map type (all-to-one bundling, service multiplexing with bundling, or no bundling)
    • Bandwidth profile is not supported (including the following features):
      
      • CM (coupling mode)
      • CF (color flag)
      • CIR (committed Information rate)
      • CBR (committed burst size)
      • EIR (excess information rate)
      • EBS (excess burst size)
  • EVC attributes:
    • EVC reference ID
    • EVC status type (active, not active, or partially active)
    • EVC type (point-to-point or multipoint-to-multipoint)
    • EVC ID (a user-configured name for EVC)
    • Bandwidth profile (not supported)
  • CE-VLAN ID/EVC map

• Q-in-Q SVLAN (point-to-point or multipoint-to-multipoint)—Requires an end-to-end CFM session between UNI-Ns to monitor the EVS status.
• VPLS (BGP or LDP) (point-to-point or multipoint-to-multipoint)—Either VPLS pseudowire status or end-to-end CFM sessions between UNI-Ns can be used to monitor EVC status.
• L2 circuit/L2VPN (point-to-point)—Either VPLS pseudowire status or end-to-end CFM sessions between UNI-Ns can be used to monitor EVC status.

  Note: l2-circuit and l2vpn are not supported.

Configuring the Ethernet Local Management Interface

To configure E-LMI, perform the following steps:

• Configuring an OAM Protocol (CFM)
• Assigning the OAM Protocol to an EVC
• Enabling E-LMI on an Interface and Mapping CE VLAN IDs to an EVC

Configuring an OAM Protocol (CFM)

For information on configuring the OAM protocol (CFM), see IEEE 802.1ag OAM Connectivity Fault Management Overview.

Assigning the OAM Protocol to an EVC

To configure an EVC, you must specify a name for the EVC using the evcsevc-id statement at the [edit protocols oam ethernet] hierarchy level. You can set the EVC protocol for monitoring EVC statistics to cfm or vpls using the evc-protocol statement and its options at the [edit protocols oam ethernet evcs] hierarchy level.

You can set the number of remote UNIs in the EVC using the remote-uni-count number statement at the [edit protocols oam ethernet evcs evcs-protocol] hierarchy level. The remote-uni-count defaults to 1. Configuring a value greater than 1 makes the EVC multipoint-to-multipoint. If you enter a value greater than the actual number of endpoints, the EVC status will display as partially active even if all endpoints are up. If you enter a remote-uni-count less than the actual number of endpoints, the status will display as active, even if all endpoints are not up.

Enabling E-LMI on an Interface and Mapping CE VLAN IDs to an EVC

To configure E-LMI, include the lmi statement at the [edit protocols oam ethernet] hierarchy level:

You can set the status counter to count consecutive errors using the status-counter count statement at the [edit protocols oam ethernet lmi] hierarchy level. The status counter is used to determine if E-LMI is operational or not. The default value is 4.

You can set the polling-verification-timer value statement at the [edit protocols oam ethernet lmi] hierarchy level. The default value is 15 seconds.

You can enable an interface and set its options for use with E-LMI using the interface name statement at the [edit protocols oam ethernet lmi] hierarchy level. Only ge, xe, and ae interfaces are supported. You can use the interface uni-id option to specify a name for the UNI. If uni-id is not configured, it defaults to the name variable of interface name.

You can specify the CE-VLAN ID/EVC map type using the evc-map-type type interface option. The options are all-to-one-bundling, bundling, or service-multiplexing. Service multiplexing is with no bundling. The default type is all-to-one-bundling.

To specify the EVC that an interface uses, use the evc evc-id statement at the [edit protocols oam ethernet lmi interface name] hierarchy level. You can specify an interface as the default EVC interface using the default-evc statement at the [edit protocols oam ethernet lmi interface name evc evc-id] hierarchy level. All VIDs that are not mapped to any other EVCs are mapped to this EVC. Only one EVC can be configured as the default.

You can map a list of VLANs to an EVC using the vlan-list vlan-id-list statement at the [edit protocols oam ethernet lmi interface name evc evc-id] hierarchy level.

Example E-LMI Configuration

Figure 2 illustrates the E-LMI configuration for a point-to-point EVC (SVLAN) monitored by CFM. In this example, VLANs 1 through 2048 are mapped to evc1 (SVLAN 100) and 2049 through 4096 are mapped to evc2 (SVLAN 200). Two CFM sessions are created to monitor these EVCs.

Figure 2: E-LMI Configuration for a Point-to-Point EVC (SVLAN) Monitored by CFM

Configuring PE1

Configuring PE2

Configuring Two UNIs Sharing the Same EVC