Route advertisement can be configured on L2GW/L3GWs to allow the L2GW/L3GWs to construct their own forwarding entries based on the received EVPN or BGP routes.
The system view is displayed.
A VBDIF interface is created, and the VBDIF interface view is displayed.
To allow L2GW/L3GWs to generate ARP entries for Layer 2 forwarding based on the ARP information in EVPN routes, run the arp generate-rd-table enable command.
To allow L2GW/L3GWs to generate ND entries for Layer 2 forwarding based on the ND information in EVPN routes, run the ipv6 nd generate-rd-table enable command.
To enable the function to collect host information by VBDIF interface for IPv4 services, run the arp collect host enable command.
To enable the function to collect host information by VBDIF interface for IPv6 services, run the ipv6 nd collect host enable command.
DAD is prohibited. This command is mandatory in IPv6 scenarios to prevent service interruptions occurred because the system detects that the IPv6 address of another device is the same as the VBDIF interface's IP address.
Exit from the VBDIF interface view.
The VPN instance view is displayed.
To enter the IPv4 address family view of the VPN instance, run the ipv4-family command.
To enter the IPv6 address family view of the VPN instance, run the ipv6-family command.
The L3VPN instance is bound to an export route-policy. This route-policy is used to filter the routes advertised to the EVPN instance from the L3VPN instance so that the L3VPN instance advertises only the static VPN routes destined for VNFs to the EVPN instance.
Exit from the IPv4 or IPv6 address family view of the VPN instance.
Exit from the VPN instance view.
The BGP view is displayed.
To enter the IPv4 address family view of a BGP-VPN instance, run the ipv4-family vpn-instance vpn-instance-name command.
To enter the IPv6 address family view of a BGP-VPN instance, run the ipv6-family vpn-instance vpn-instance-name command.
Static routes are imported to the IPv4 or IPv6 address family of the BGP-VPN instance.
The function to advertise IP routes from the VPN instance to the EVPN instance is enabled.
If the load balancing function needs to be deployed on the network, specify the import-route-multipath parameter so that the VPN instance can advertise all the routes with the same destination address to the EVPN instance.
The asymmetric mode is enabled for IRB routes.
If L2GW/L3GWs are configured to advertise ARP or ND routes to each other, skip this step. If L2GW/L3GWs are configured to advertise IRB or IPBv6 routes to each other, perform this step so that L2GW/L3GWs do not generate IP prefix routes. This prevents route loops.
Exit from the IPv4 or IPv6 address family view of the BGP-VPN instance.
The BGP-EVPN address family view is displayed.
L2GW/L3GWs are configured to advertise IRB/IRBv6 or ARP/ND routes.
If L2GW/L3GWs are configured to advertise ARP or ND routes, L2GW/L3GWs send only the routes carrying MAC addresses and ARP information to DC-GWs. If L2GW/L3GWs are configured to advertise IRB or IRBv6 routes, L2GW/L3GWs send routes carrying MAC address, ARP information, and L3 VNIs to DC-GWs. In this case, you need to run the irb asymmetric command on DC-GWs so that DC-GWs do not generate IP prefix routes based on IP addresses and L3 VNIs. This prevents route loops.
Exit from the BGP-EVPN address family view.
Exit from the BGP view.
The configuration is committed.