Configuring a Border Leaf Node to Provide Interworking Between EVPN L3VPN over SRv6 TE Policy and Common L3VPN over MPLS

During network evolution, an EVPN L3VPN over SRv6 TE Policy and a common L3VPN over MPLS may coexist. To allow these two networks to communicate, configure each border leaf node to provide interworking between EVPN L3VPN over SRv6 TE Policy and common L3VPN over MPLS.

Context

In Figure 1, network A is newly deployed and runs the EVPN L3VPN over SRv6 TE Policy service. Network B is a legacy network and runs the common L3VPN over MPLS service. Alternatively, network A runs the EVPN L3VPNv6 over SRv6 TE Policy service, and network B runs the common L3VPNv6 over MPLS service. To ensure that these two types of networks can communicate with each other and services are running properly, configure each border leaf node to provide interworking between EVPN L3VPN over SRv6 TE Policy and common L3VPN over MPLS.

Figure 1 Configuring a border leaf node to provide interworking between EVPN L3VPN over SRv6 TE Policy and common L3VPN over MPLS

Pre-configuration Tasks

Before configuring a border leaf node to provide interworking between EVPN L3VPN over SRv6 TE Policy and common L3VPN over MPLS, complete the following tasks:

Configure EVPN L3VPN over SRv6 TE Policy or Configuring EVPN L3VPNv6 over SRv6 TE Policy on the network that contains area A.
Configure a basic BGP/MPLS IPv4 VPN and configure a basic BGP/MPLS IPv6 VPN on network B.

Procedure

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

Verifying the Configuration

Run the display bgp evpn all routing-table command to check information about EVPN routes re-originated after the border leaf node receives VPNv4 or VPNv6 routes encapsulated in MPLS packets from PEs.
Run the display bgp vpnv4 all routing-table command to check information about VPNv4 routes re-originated after the border leaf node receives EVPN IP prefix routes encapsulated in SRv6 packets from access leaf nodes.
Run the display bgp vpnv6 all routing-table command to check information about VPNv6 routes re-originated after the border leaf node receives EVPN IP prefix routes encapsulated in SRv6 packets from access leaf nodes.