Configuring Interworking Between an EVPN L3VPN HoVPN over MPLS with a Common L3VPN

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

Context

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

Create VPN instances on UPEs and SPEs and bind the VPN instances to AC interfaces or bind the IPv6 VPN instances to AC interfaces on the UPEs.

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.
For IPv4 services, please configure VPN instances and bind the VPN instances to AC interfaces on NPEs; For IPv6 services, please Configure IPv6 VPN instances and bind the IPv6 VPN instances to AC interfaces on NPEs.
Configure the default static VPN routes on the SPEs. For details, see Creating IPv4 Static Routes or Creating IPv6 Static Routes.
For IPv4 services, please configure a BGP VPNv4 peer relationship between each SPE and NPE. This configuration is similar to configuring a BGP VPNv4 peer relationship between PEs on a BGP/MPLS IPv4 VPN. For more information, see Establishing MP-IBGP Peer Relationships Between PEs; For IPv6 services, please configure a BGP VPNv6 peer relationship between each SPE and NPE. This configuration is similar to configuring a BGP VPNv6 peer relationship between PEs on a BGP/MPLS IPv6 VPN. For more information, see Establishing MP-IBGP Peer Relationships Between PEs.
Configure BGP-EVPN peer relationships between UPEs and SPEs. For details, see Establishing a BGP EVPN Peer Relationships.
Configure SPEs to advertise only default or summarized routes to UPEs. For details, see Configuring an EVPN L3VPN HoVPN over MPLS.
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 or Configuring IPv6 Route Exchange Between PEs and CEs.
Configure SPEs to advertise re-encapsulated VPNv4 routes to NPEs. For details, see Procedure.

Perform the following steps on an SPE.

Procedure

Run system-view
The system view is displayed.
Run bgp { as-number-plain | as-number-dot }
The BGP view is displayed.
Run l2vpn-family evpn
The BGP-EVPN 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 ipv4-family vpnv4 or ipv6-family vpnv6
The BGP-VPNv4/VPNv6 address family view is displayed.
Run peer { ipv4-address | group-name } advertise route-reoriginated evpn { ip | ipv6 }
The SPE is configured to re-encapsulate the EVPN routes received from the UPE into BGP VPNv4/VPNv6 routes and then send them to the NPE.
Run commit
The configuration is committed.