Configuring Interworking Between an EVPN L3VPN over SRv6 and a Common L3VPN over MPLS

During network evolution, an EVPN L3VPN over SRv6 and a common L3VPN over MPLS may coexist. To ensure normal communication between the two types of networks, configure interworking between an EVPN L3VPN over SRv6 and a common L3VPN over MPLS.

Context

On the network shown in Figure 1, area A is a newly built network deployed with the EVPN L3VPN over SRv6 service, and area B is the legacy network deployed with the common L3VPN over MPLS service. To ensure normal communication between the two networks, configure interworking between the EVPN L3VPN over SRv6 and the common L3VPN over MPLS on border leaves.

Figure 1 Interworking between an EVPN L3VPN over SRv6 and a common L3VPN over MPLS

Pre-configuration Tasks

Before configuring interworking between an EVPN L3VPN over SRv6 and a common L3VPN over MPLS, complete the following tasks:

On the network in area A, Configuring EVPN L3VPN over SRv6 BE.
On the network in area B, Configuring a Basic BGP/MPLS IP VPN or Configuring a Basic BGP/MPLS IPv6 VPN.

Procedure

Configure a border leaf to advertise the routes that are re-originated in the BGP-EVPN address family to a BGP VPNv4/VPNv6 peer (PE).
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 peerIpv6Addr import reoriginate
  The function to re-originate the routes received from a specified BGP EVPN IPv6 peer is enabled.
5. Run quit
  The BGP view is displayed.
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 } advertise route-reoriginated evpn { ip | ipv6 }
  The function to advertise the routes re-originated in the BGP-EVPN address family to a BGP VPNv4/VPNv6 peer or peer group is enabled.
  
  After this step is performed, the border leaf re-originates the SRv6-encapsulated EVPN IPv4/IPv6 prefix routes that are received from access leaf nodes and then advertises the MPLS-encapsulated BGP VPNv4/VPNv6 routes to the BGP VPNv4/VPNv6 peer (PE).
Configure the border leaf to advertise the routes that are re-originated in the BGP-VPNv4/VPNv6 address family to a BGP EVPN peer (access leaf).
1. Run peer { ipv4-address | group-name } import reoriginate
  The device is enabled to re-originate the routes received from a BGP VPNv4 peer in the BGP-VPNv4/VPNv6 address family view.
2. Run quit
  The BGP view is displayed.
3. Run l2vpn-family evpn
  The BGP-EVPN address family view is displayed.
4. Run peer ipv6-address advertise route-reoriginated { vpnv4 | vpnv6 }
  The border leaf is enabled to advertise the routes re-originated in the BGP VPNv4/VPNv6 address family to the BGP VPN IPv6 peer.
  
  After this step is performed, the border leaf re-originates the MPLS-encapsulated VPNv4/VPNv6 routes that are received from the BGP VPNv4/VPNv6 peer (PE) and then advertises SRv6-encapsulated EVPN routes to the BGP EVPN peer (access leaf).
5. Run quit
  The BGP view is displayed.
Enable the EVPN route advertisement in the BGP-VPN instance address family view.
1. 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.
2. Run advertise l2vpn evpn
  The device is enabled to advertise the host IPv4/IPv6 routes in the VPN instance as EVPN IPv4/IPv6 prefix routes.
Run commit
The configuration is committed.

Verifying the Configuration

Run the display bgp evpn all routing-table command to check the EVPN routes re-originated by the border leaf upon receipt of MPLS-encapsulated VPNv4/VPNv6 routes received by the PE.
Run the display bgp vpnv4 routing-table command to check the VPNv4 routes re-originated by the border leaf upon receipt of SRv6-encapsulated EVPN IPv4 prefix routes received by the access leaf.
Run the display bgp vpnv6 routing-table command to check the VPNv6 routes re-originated by the border leaf upon receipt of SRv6-encapsulated EVPN IPv6 prefix routes received by the access leaf.