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.


NE20E-S V800R010C10SPC500 Feature Description - VPN 01

This is NE20E-S V800R010C10SPC500 Feature Description - 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).
EVPN Splicing

EVPN Splicing


The current MAN is evolving into EVPN. However, because there are a large number of devices at the aggregation layer, it is difficult for the MAN to evolve into EVPN at a time. To allow traditional VPWS or VPLS to be still used at the aggregation layer and the core layer to evolve into EVPN first, splicing between EVPN and the traditional network must be supported.

L3VPN Accessing EVPN

The network between the UPE and NPE1 resides at the aggregation layer. The network between NPE1 and NPE2 resides at the core layer. An L3VPN is deployed at the aggregation layer, and EVPN-MPLS is deployed at the core layer. After receiving user routes from the access side, the UPE sends these routes to NPE1 through a BGP VPNv4 peer relationship. Both an EVPN instance and an L3VPN instance are configured on NPE1. After receiving BGP VPNv4 routes, NPE1 imports these routes into the L3VPN instance, encapsulates the routes into EVPN routes, and sends the EVPN routes to NPE2 through a BGP EVPN peer relationship. This implementation is L3VPN accessing EVPN as such.

Figure 12-51 L3VPN accessing EVPN

VLL Accessing EVPN

On a network with VLL accessing EVPN, CE1 and CE2 stand for two users. Each user has three sites: CE1-1, CE1-2, and CE1-3 for CE1, and CE2-1, CE2-2, and CE2-3 for CE2. NIDs, which function as aggregation devices on the user side, are attached to the user sites and access the aggregation network. When accessing the aggregation network, the CEs use the S-VLAN and C-VLAN tags. S-VLAN indicates an NID, and C-VLAN indicates the user site connected to the NID. The users access the VLL network, a Layer 2 network, through the NIDs. The UPE and NPE1 belong to the aggregation layer, at which an MPLS network is deployed. Services between the devices are carried using a VLL. NPE1 and NPE2 belong to the core layer, at which an MPLS network is deployed. Services between them are carried through an EVPN.

To allow communication between different sites of the same user, VLL accessing EVPN supports the following scenarios:

  • Single-homing scenario

    An NID on the access side can be single-homed to a UPE through a main interface. The UPE establishes a PW with NPE1 for each NID. On NPE1 and NPE2, an EVPN instance is created for each user. On NPE1, a VLL is connected to the EVPN through a PW VE interface. The VLL is bound to the PW VE interface, and the EVPN instances are bound to the PW VE sub-interfaces that are configured as QinQ VLAN tag termination sub-interfaces. In this manner, traffic of user packets is imported to different EVPN instances based on the S-VLAN and C-VLAN tags.

    Figure 12-52 Single-homing scenario 1 for VLL accessing EVPN (per NID per PW)

    Additionally, VLL accessing EVPN allows multiple NIDs to share a PW. In this scenario, multiple NIDs are aggregated to a switch, which then accesses a PW on a UPE.

    Figure 12-53 Single-homing scenario 2 for VLL accessing EVPN (multiple NIDs per PW)
  • Dual-homing scenario

    A UPE is dual-homed to the master and slave NPEs through primary and secondary PWs respectively to improve access reliability. On the EVPN, the NPE1-NPE3 link and the NPE2-NPE3 link can be configured to work in single-active mode or in all-active mode, which allows for load balancing.

    Figure 12-54 Dual-homing scenario for VLL accessing EVPN

Splicing VXLAN and VPLS

When a DC with an EVPN VXLAN deployed interconnects to an enterprise campus through an MPLS L2VPN, splicing VXLAN and VPLS must be deployed.

On the network shown in Figure 12-55, the TOR, which is a DC's gateway, accesses the backbone network through the egress routers PE1 and PE2 on the DC network. PE3, which is the egress router on the campus network, interconnects to PE1 and PE2 through the MPLS VPLS network. Splicing VXLAN and VPLS is configured on PE1 and PE2 to implement communication between the DC and campus network.

Figure 12-55 Splicing VXLAN and VPLS

Updated: 2019-01-03

Document ID: EDOC1100055135

Views: 10331

Downloads: 19

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