Configuring EVPN E-LAN Accessing L3VPN

If point-to-multipoint Layer 2 services are carried using EVPN E-LAN and Layer 3 services are carried using MPLS L3VPN, EVPN E-LAN accessing L3VPN must be configured on L2-to-L3 devices.

Usage Scenario

On the network shown in Figure 1, the first layer is the user-side access network where Layer 2 services are carried between CPEs and UPEs to implement VLAN forwarding. The second layer is the aggregation network where services are carried using EVPN E-LAN and BD-based EVPN MPLS is deployed between UPEs and NPEs. The third layer is the core network where services are carried using MPLS L3VPN. In this case, EVPN E-LAN accessing L3VPN must be configured on NPEs.

Figure 1 Networking of EVPN E-LAN accessing L3VPN

Pre-configuration Tasks

Before configuring EVPN E-LAN accessing L3VPN, complete the following tasks:

Configuring BD-EVPN Functions on UPEs and NPEs.
Configuring a Basic BGP/MPLS IP VPN or Configuring a Basic BGP/MPLS IPv6 VPN on NPEs.

Creating an L2VE Interface: This section describes how to configure an L2VE interface to terminate an EVPN and bind the L2VE interface to a VE-Group.

Creating an L3VE Interface: This section describes how to configure an L3VE interface to access an L3VPN and bind the L3VE interface to a VE-Group.

(Optional) Configuring MAC Addresses for L2VE and L3VE Interfaces: When the MAC address of an L2VE or L3VE interface conflicts with the MAC address of another type of interface, you can change the MAC address of the L2VE or L3VE interface to allow normal communication.

Adding an L2VE Interface to a BD: You can add an L2VE interface to the BD so that EVPN E-LAN services are terminated on the L2VE interface.

Associating an L3VE Interface with a VPN Instance: This section describes how to configure an IP address for an L3VE sub-interface and bind it to a VPN instance to access L3VPN.

Verifying the Configuration of EVPN E-LAN Accessing L3VPN: After EVPN E-LAN accessing L3VPN is configured, you can view the binding relationship between VE interfaces and a VE-Group, as well as EVPN instance information.