No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Configuration Guide - VPN 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - VPN
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Splicing a VLL with a Common EVPN E-LAN

Splicing a VLL with a Common EVPN E-LAN

Traditional VLL is still used at the aggregation layer of a network, whereas the core network has evolved into EVPN. To allow communication between different layers, VLL splicing common EVPN must be configured.


As the MAN is evolving into EVPN, a large number of devices at the aggregation layer still use traditional VLLs, making E2E evolution into EVPN at a time difficult. However, the core network has evolved into EVPN. To implement communication between different network layers, VLL splicing common EVPN must be supported.

On the network shown in Figure 11-15, CE1 with two sites attached is connected to a UPE through a NID (switch). The UPE and NPEs are connected through an MPLS network at the aggregation layer, and services are carried using a VLL. NPE1, NPE2, and NPE3 are connected through an MPLS network at the core layer, and services are carried through an EVPN.

Figure 11-15 Splicing a VLL with a Common EVPN E-LAN
  • A UPE is dual-homed to NPE1 and NPE2, which improves access reliability. The UPE establishes the primary and secondary PWs with the master and slave NPEs, respectively. Traffic is sent through the primary PW, and the UPE is enabled to receive traffic through both the primary and secondary PWs.

  • On NPE1 and NPE2, the VLL is connected to the EVPN through PW VE interfaces. Specifically, the VLL is configured on the PW VE interfaces, and EVPN instances are bound to the PW VE sub-interfaces that are configured as QinQ VLAN tag termination sub-interfaces. In this manner, traffic is imported to the EVPN instances.

Pre-configuration Tasks

Before splicing a VLL with a common EVPN E-LAN, complete the following tasks:


  1. Configure basic EVPN functions on NPE1 and NPE2.
    1. Configure an EVPN instance.
    2. Configure an EVPN source address.
    3. Configure a BGP EVPN peer relationship.
  2. Run mpls l2vpn

    MPLS L2VPN is enabled on NPE1 and NPE2.

  3. Configure PW VE interfaces and sub-interfaces on NPE1 and NPE2. Bind the VLL to the PW VE interfaces and bind EVPN instances to the PW VE sub-interfaces.
    1. Run interface interface-type interface-number

      The PW VE interface view is displayed.

    2. Run mpls l2vc { ip-address | pw-template pw-template-name } * vc-id [ tunnel-policy policy-name | [ control-word | no-control-word ] | [ raw | tagged ] | access-port | ignore-standby-state ] *

      A VPWS connection is created.

    3. Run esi esi

      An ESI is configured.

    4. Run quit

      Return to the system view.

    5. Run interface interface-type interface-number [ .subinterface-number ]

      The PW VE sub-interface view is displayed.

    6. Run encapsulation qinq-termination [ local-switch | rt-protocol ]

      The encapsulation type of the sub-interface is set to QinQ VLAN tag termination.

    7. Run qinq termination pe-vid pe-vid [ to high-pe-vid ] ce-vid ce-vid [ to high-ce-vid ]

      The sub-interface is configured as a QinQ VLAN tag termination sub-interface.

    8. Run evpn binding vpn-instance vpn-instance-name

      The PW VE sub-interface is bound to an EVPN instance.

    9. Run commit

      The configuration is committed.

Configuration Examples

  • Run the display evpn vpn-instance [ verbose ] command to view information about the EVPN instance-bound PW VE sub-interfaces.
  • Run the display mpls l2vc [ vc-id | brief | interface interface-type interface-number | remote-info [ vc-id | unmatch | verbose ] | state { down | up } ] command to view the VLL-bound PW VE interfaces.
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 32495

Downloads: 59

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next