During the evolution from L3VPN HoVPN to EVPN HoVPN over SRv6, these two types of services may coexist. In this case, you need to configure interworking between an L3VPN HoVPN and an EVPN L3VPN over SRv6.
On the network shown in Figure 1, a traditional L3VPN HoVPN is deployed between the UPEs and SPEs, and an EVPN L3VPN over SRv6 is deployed between the SPEs and NPEs. In this case, you need to configure each SPE for interworking between the L3VPN HoVPN and the EVPN L3VPN over SRv6.
Before configuring interworking between an L3VPN HoVPN and an EVPN L3VPN over SRv6, complete the following tasks:
The system view is displayed.
The BGP view is displayed.
The BGP-VPNv4 or BGP-VPNv6 address family view is displayed.
The device is enabled to add the regeneration flag to VPNv4 or VPNv6 routes received from UPEs that function as peers.
The ipv4-address parameter specifies the IP address of a UPE peer, and the group-name parameter specifies the name of a UPE peer group.
Return to the BGP view.
The BGP-EVPN address family view is displayed.
The device is enabled to regenerate the received VPNv4 or VPNv6 routes as EVPN routes and advertise them to NPEs.
The peerIpv6Addr parameter specifies the IP address of an NPE peer, and the peerGroupName parameter specifies the name of an NPE peer group.
The configuration is committed.
Run the display ip routing-table vpn-instance or display ipv6 routing-table vpn-instance vpn-instance-name command on a UPE or NPE to check the VPN routing table. The command output shows the default routes or specific routes sent from the remote ends.
Run the display bgp evpn all routing-table prefix-route command to check the EVPN IP prefix routing table. The command output shows the IP prefix routes sent from the remote ends.