Configuring Interworking Between a Common L3VPN and an EVPN L3VPN

When an L3VPN is being reconstructed into an EVPN L3VPN, co-existence of the EVPN L3VPN and L3VPN occurs. To prevent network reconstruction from compromising communication, configure interworking between L3VPN and EVPN L3VPN so that the EVPN L3VPN and L3VPN can communicate with each other.

Context

On the network shown in Figure 1, an L3VPN is already deployed. If a user wants to deploy an EVPN L3VPN over the network, co-existence of the EVPN L3VPN and L3VPN occurs during reconstruction. To ensure communication between the two VPNs, the user must configure interworking between L3VPN and EVPN L3VPN on NPE1.

Figure 1 Interworking between L3VPN and EVPN L3VPN

Pre-configuration Tasks

Before configuring interworking between L3VPN and EVPN L3VPN, complete the following tasks:

Configure basic MPLS functions on the UPE, NPE1, and NPE2.
Configure an IGP on the UPE, NPE1, and NPE2 to implement route reachability.
Configure EVPN instances in BD mode on NPE1 and NPE2. For configuration details, see Establishing a BGP EVPN Peer Relationships.
Configure an L3VPN between NPE1 and the UPE. For configuration details, see Configuring a Basic BGP/MPLS IP VPN or Configuring a Basic BGP/MPLS IPv6 VPN.

Procedure

Configure NPE1 and NPE2 to generate and advertise IP prefix routes.
For IPv4 services, perform the following configurations.
1. Run system-view
  The system view is displayed.
2. Run ip vpn-instance vpn-instance-name
  
  A VPN instance is created, and the VPN instance view is displayed.
3. Run ipv4-family
  
  The IPv4 address family is enabled for the VPN instance, and the VPN instance IPv4 address family view is displayed.
4. Run route-distinguisher route-distinguisher
  An RD is set for the VPN instance IPv4 address family.
5. Run vpn-target vpn-target &<1-8> [ both | export-extcommunity | import-extcommunity ] evpn
  
  VPN targets are configured for the VPN instance IPv4 address family to mutually import routes with the local EVPN instance.
6. Run evpn mpls routing-enable
  
  EVPN is enabled to generate and advertise IP prefix routes and IRB routes.
7. (Optional) Run tnl-policy policy-name evpn
  
  EVPN routes that can be imported into the VPN instance IPv4 address family are associated with a tunnel policy.
8. Run quit
  
  Exit from the VPN instance IPv4 address family view.
9. Run quit
  
  Exit from the VPN instance view.
10. Run commit
  
  The configuration is committed.
For IPv6 services, perform the following configurations.
1. Run system-view
  The system view is displayed.
2. Run ip vpn-instance vpn-instance-name
  
  A VPN instance is created, and the VPN instance view is displayed.
3. Run ipv6-family
  
  The IPv6 address family is enabled for the VPN instance, and the VPN instance IPv6 address family view is displayed.
4. Run route-distinguisher route-distinguisher
  An RD is set for the VPN instance IPv6 address family.
5. Run vpn-target vpn-target &<1-8> [ both | export-extcommunity | import-extcommunity ] evpn
  
  VPN targets are configured for the VPN instance IPv6 address family to mutually import routes with the local EVPN instance.
6. Run evpn mpls routing-enable
  
  EVPN is enabled to generate and advertise IP prefix routes and IRB routes.
7. (Optional) Run tnl-policy policy-name evpn
  
  EVPN routes that can be imported into the VPN instance IPv6 address family are associated with a tunnel policy.
8. Run quit
  
  Exit from the VPN instance IPv6 address family view.
9. Run quit
  
  Exit from the VPN instance view.
10. Run commit
  
  The configuration is committed.
Configure NPE1 to advertise routes regenerated by the EVPN address family to the BGP VPNv4/VPNv6 peer (UPE).
1. Run system-view
  The system view is displayed.
2. Run bgp { as-number-plain | as-number-dot }
  The BGP view is displayed.
3. Run l2vpn-family evpn
  The BGP-EVPN address family view is displayed.
4. Run peer { ipv4-address | group-name } import reoriginate
  The BGP device is enabled to add the regeneration flag to the routes received from the BGP EVPN peer.
5. Run quit
  Return to the BGP view.
6. Run ipv4-family vpnv4 or ipv6-family vpnv6
  The BGP-VPNv4/VPNv6 address family view is displayed.
7. Run peer { ipv4-address | group-name } reflect-client
  NPE1 is configured as an RR, and the UPE is specified as the RR client to reflect BGP VPNv4/VPNv6 routes into which EVPN routes are re-encapsulated.
8. Run peer { ipv4-address | group-name } advertise route-reoriginated evpn { mac-ip | ip | mac-ipv6 | ipv6 }
  NPE1 is configured to advertise routes regenerated by the EVPN address family to the BGP VPNv4/VPNv6 peer (UPE).
  
  After the peer { ipv4-address | group-name } advertise route-reoriginated evpn { mac-ip | ip | mac-ipv6 | ipv6 } command is run, NPE1 uses MPLS to re-encapsulate the EVPN routes received from NPE2 into BGP VPNv4/VPNv6 routes and then sends them to the UPE.
9. Run quit
  Return to the BGP view.
10. Run quit
  Exit from the BGP view.
11. Run commit
  The configuration is committed.
Configure NPE1 to advertise routes regenerated by the VPNv4/VPNv6 address family to the BGP EVPN peer (NPE2).
1. Run system-view
  The system view is displayed.
2. Run bgp { as-number-plain | as-number-dot }
  The BGP view is displayed.
3. Run ipv4-family vpnv4 or ipv6-family vpnv6
  The BGP-VPNv4/VPNv6 address family view is displayed.
4. Run peer { ipv4-address | group-name } import reoriginate
  The BGP device is enabled to add the regeneration flag to the routes received from the BGP VPNv4/VPNv6 peer.
5. Run quit
  Return to the BGP view.
6. Run l2vpn-family evpn
  The BGP-EVPN address family view is displayed.
7. Run peer { ipv4-address | group-name } reflect-client
  NPE1 is configured as an RR, and NPE2 is specified as the RR client to reflect BGP EVPN routes into which BGP VPNv4/VPNv6 routes are re-encapsulated.
8. Run peer { ipv4-address | group-name } advertise route-reoriginated { vpnv4 | vpnv6 }
  NPE1 is configured to advertise routes regenerated by the VPNv4/VPNv6 address family to the BGP EVPN peer (NPE2).
  
  After the peer { ipv4-address | group-name } advertise route-reoriginated { vpnv4 | vpnv6 } command is run, NPE1 re-encapsulates the MPLS-encapsulated VPNv4/VPNv6 routes received from the UPE into EVPN routes and then sends them to NPE2.
9. Run quit
  Return to the BGP view.
10. Run ipv4-family vpn-instance vpn-instance-name or ipv6-family vpn-instance vpn-instance-name
  The BGP-VPN instance IPv4/IPv6 address family view is displayed.
11. Run advertise l2vpn evpn
  The BGP device is enabled to advertise IP prefix routes to the BGP peer. This configuration allows the BGP device to advertise both host IP routes and routes of the network segment where the host resides.
12. Run quit
  Return to the BGP view.
13. Run quit
  Exit from the BGP view.
14. Run commit
  The configuration is committed.

Checking the Configurations

Run the display bgp evpn all routing-table command on NPE2 to check information about EVPN routes received from the UPE.
Run the display ip routing-table vpn-instance vpn-instance-name or display ipv6 routing-table vpn-instance vpn-instance-name command on NPE2 or the UPE to check information about VPN routes received from each other.