Configuring Interworking Between an L3VPN HoVPN and an EVPN L3VPN over MPLS

As L3VPN HoVPN evolves towards EVPN HoVPN over MPLS, interworking between L3VPN HoVPN and EVPN L3VPN over MPLS occurs. An L3VPN HoVPN is deployed between UPEs and SPEs, and an EVPN L3VPN over MPLS is deployed between SPEs and NPEs.

Context

On a network with an L3VPN HoVPN interworking with an EVPN L3VPN over MPLS, the following configurations must be performed:

Configure VPN instances on SPEs and NPEs and bind the VPN instances to the NPE interfaces that connect to CEs. For details, see Creating an L3VPN Instance and Binding It to a VBDIF Interface.

According to relevant standards, the VPN instance status obtained from an NMS is Up only if at least one interface bound to the VPN instance is Up. On an HoVPN, VPN instances on SPEs are not bound to interfaces. As a result, the VPN instance status obtained from an NMS is always Down. To solve this problem, run the transit-vpn command in the VPN instance view or VPN instance IPv4 or IPv6 address family view of an SPE. Then, the VPN instance status obtained from the NMS is always Up, regardless of whether the VPN instance is bound to interfaces.
Configure VPN instances and bind the VPN instances to AC interfaces on UPEs.
Configure BGP-EVPN peer relationships between SPEs and NPEs. For details, see Establishing a BGP EVPN Peer Relationships.
Configure a BGP VPNv4 peer relationship between each SPE and UPE. This configuration is similar to configuring a BGP VPNv4 peer relationship between PEs on a BGP/MPLS VPN. For more information, see Establishing MP-IBGP Peer Relationships Between PEs.
Configure routing protocols for NPEs and UPEs to exchange routes with CEs. This configuration is similar to configuring PEs and CEs to exchange routes on a BGP/MPLS VPN. For more information, see Configuring Route Exchange Between PEs and CEs.
Configure SPEs to advertise only default or summarized routes to UPEs.
Configure SPEs to advertise re-encapsulated EVPN routes to NPEs. For details, see Procedure.

Perform the following steps on each SPE.

Procedure

Run system-view
The system view is displayed.
Run bgp { as-number-plain | as-number-dot }
The BGP view is displayed.
Run ipv4-family vpnv4
The BGP-VPNv4 address family view is displayed.
Run peer { ipv4-address | group-name } import reoriginate
The SPE is enabled to add the regeneration flag to the routes received from the UPE.
Run quit
Return to the BGP view.
Run l2vpn-family evpn
The BGP-EVPN address family view is displayed.
Run peer { ipv4-address | group-name } advertise route-reoriginated vpnv4
The SPE is configured to re-encapsulate the BGP VPNv4 routes received from the UPE into EVPN routes and then send them to the NPE.
Run commit
The configuration is committed.