Configuring Route Advertisement on L2GW/L3GWs

Procedure

1. Configure L2GW/L3GWs to generate ARP or ND entries for Layer 2 forwarding based on the ARP or ND information in EVPN routes.
   1. Run system-view

      The system view is displayed.

   2. Run interface vbdif bd-id

      A VBDIF interface is created, and the VBDIF interface view is displayed.

   3. Configure L2GW/L3GWs to generate ARP or ND entries for Layer 2 forwarding based on the ARP or ND information in EVPN routes.

      • 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.

   4. (Optional) Run ipv6 nd dad attempts 0

      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.

   5. Run quit

      Exit from the VBDIF interface view.

2. Configure an L3VPN instance to advertise the static VPN routes destined for VNFs to an EVPN instance.
   1. Create a route-policy so that the static VPN routes destined for VNFs can be filtered out in the L3VPN instance. For configuration details, see Configuring a Route-Policy. During configuration of an apply clause, run the apply gateway-ip { origin-nexthop | ipv4-address } or apply ipv6 gateway-ip { origin-nexthop | ipv6-address } command to specify the original next-hop address of a static VPN route as a gateway address.
   2. Run ip vpn-instance vpn-instance-name

      The VPN instance view is displayed.

   3. Enter the IPv4 or IPv6 address family view of the VPN instance.

      • 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.

   4. Run export route-policy policy-name evpn

      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 and gateway addresses are added to the static VPN routes.

   5. Run quit

      Exit from the IPv4 or IPv6 address family view of the VPN instance.

   6. Run quit

      Exit from the VPN instance view.

   7. Run bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

   8. Enter the IPv4 or IPv6 address family view of a BGP-VPN instance.

      • 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.

   9. Run import-route static [ med med | route-policy route-policy-name ] ^*

      Static routes are imported to the IPv4 or IPv6 address family of the BGP-VPN instance.

   10. Run advertise l2vpn evpn [ import-route-multipath ]

       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.

   11. (Optional) Run irb asymmetric

       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.

   12. Run quit

       Exit from the IPv4 or IPv6 address family view of the BGP-VPN instance.

3. Run commit

   The configuration is committed.