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

Reminder

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

upgrade

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 an MPLS EVPN E-Line

Splicing a VLL with an MPLS EVPN E-Line

The 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 MPLS EVPN must be configured.

Context

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 accessing EVPN must be supported. EVPN-VPWS services involve the E-Line and E-LAN models. This section describes how to splice a VLL with an MPLS EVPN E-Line.

On the network shown in Figure 11-16, 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-16 Splicing a VLL with an MPLS EVPN E-Line
  • 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 an MPLS EVPN E-Line, complete the following tasks:

Perform the following steps on the NPE.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The view of a main PW-VE interface is displayed.

  3. 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 dynamic VPWS connection is created.

  4. Run esi esi

    An ESI is configured.

  5. Run quit

    Return to the system view.

  6. Run interface interface-type interface-number.subnum

    A PW-VE sub-interface is created, and the PW-VE sub-interface view is displayed.

    By default, no PW-VE sub-interface is created.

    NOTE:

    Before running this command, ensure that the Layer 2 interface on which the PW-VE sub-interface is to be created does not have the port link-type dot1q-tunnel command configuration. If this configuration exists, run the undo port link-type command to delete the configuration.

    In addition to a Layer 2 sub-interface, an Ethernet main interface, Layer 3 sub-interface, or Eth-Trunk interface can also function as an AC interface.

  7. Configure an encapsulation type for the PW-VE sub-interface.

    • Configure a QinQ VLAN tag termination sub-interface:
      1. Run control-vid vid qinq-termination [ local-switch | rt-protocol ] or encapsulation qinq-termination [ local-switch | rt-protocol ]

        The encapsulation type for a VLAN tag termination sub-interface is configured to be QinQ.

        • Specify local-switch so that the sub-interface for QinQ VLAN tag termination supports local switching.

        • Specify rt-protocol so that the sub-interface for QinQ VLAN tag termination supports routing protocols.

      2. Run qinq termination pe-vid pe-vid [ to high-pe-vid ] ce-vid ce-vid [ to high-ce-vid ] [ vlan-group group-id ]

        The VLAN tag termination function is configured for the sub-interface for QinQ VLAN tag termination.

        After you specify rt-protocol, the sub-interface terminates double-tagged packets, and both inner and outer tags must be specific VLAN IDs.

    • Configure a dot1q VLAN tag termination sub-interface:
      1. Run control-vid vid dot1q-termination [ rt-protocol ] or encapsulation dot1q-termination [ rt-protocol ]

        The encapsulation type for a VLAN tag termination sub-interface is configured to be dot1q.

        Specify rt-protocol so that the sub-interface for dot1q VLAN tag termination supports routing protocols.

      2. Run the following commands:
        • To configure a sub-interface for dot1q VLAN tag termination, run the dot1q termination vid low-pe-vid [ to high-pe-vid ] [ vlan-group group-id ] command.
        NOTE:
        • After the dot1q termination vid low-pe-vid [ to high-pe-vid ] [ vlan-group group-id ] command is run in the Ethernet sub-interface view, the specified VLAN range belongs to the sub-interface, and any VLAN ID in the VLAN range cannot be configured together with the 802.1p value/DSCP value/EthType on other sub-interfaces.

  8. Run evpl instance evpl-id

    The PW-VE sub-interface is bound to the EVPL instance.

    By default, no EVPL instance is bound to a PW-VE sub-interface.

  9. Run commit

    The configuration is committed.

Checking the Configurations

Run the display bgp evpn all routing-table command on the NPEs and check for EVI AD routes received by the NPEs.

[~NPE3] display bgp evpn all routing-table

 Local AS number : 65001

 BGP Local router ID is 192.168.14.4
 Status codes: * - valid, > - best, d - damped, x - best external, a - add path,
               h - history,  i - internal, s - suppressed, S - Stale
               Origin : i - IGP, e - EGP, ? - incomplete


 EVPN address family:
 Number of A-D Routes: 2
 Route Distinguisher: 1:1
       Network(ESI/EthTagId)                                  NextHop
 *>    0011.1111.0000.0000.0000:100                       1.1.1.100
 Route Distinguisher: 1.1.1.100:0
       Network(ESI/EthTagId)                                  NextHop
 *>    0011.1111.0000.0000.0000:4294967295                    1.1.1.100
    

 EVPN-Instance evpna:
 Number of A-D Routes: 3
       Network(ESI/EthTagId)                                  NextHop
 *>    0011.1111.0000.0000.0000:100                       1.1.1.100
       0011.1111.0000.0000.1111:200                       127.0.0.1
 *>    0011.1111.0000.0000.0000:4294967295                    1.1.1.100

 EVPN address family:
 Number of ES Routes: 1
 Route Distinguisher: 1.1.1.100:0
       Network(ESI)                                           NextHop
 *>    0011.1111.0000.0000.0000                               1.1.1.100
    

 EVPN-Instance evpna:
 Number of ES Routes: 1
       Network(ESI)                                           NextHop
 *>    0011.1111.0000.0000.0000                               1.1.1.100
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 27603

Downloads: 53

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