Configuring Route Advertisement on an L2GW/L3GW

Procedure

1. Configure an L2GW/L3GW to generate ARP (ND) entries for Layer 2 forwarding based on ARP/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 a DC gateway to generate ARP (ND) entries for Layer 2 forwarding based on ARP/ND information in EVPN routes.

      • Run arp generate-rd-table enable

        The L2GW/L3GW is enabled to generate ARP entries used for Layer 2 forwarding based on ARP information.

      • Run ipv6 nd generate-rd-table enable

        The L2GW/L3GW is enabled to generate ND entries used for Layer 2 forwarding based on ND information.

   4. Run quit

      Exit from the VBDIF interface view.

2. Configure an L3VPN instance on the L2GW/L3GW to advertise static VPN routes reachable to a VNF to EVPN.
   1. Create a route policy to filter the static VPN routes reachable to the VNF from the L3VPN instance. For details on how to configure a route policy, see Configuring a Route-Policy. When you specify an apply clause, run the apply gateway-ip { origin-nexthop | ipv4-address } or apply ipv6 gateway-ip { origin-nexthop | ipv6-address } command to set the original next hop of a static route to the gateway IP address.
   2. Run ip vpn-instance vpn-instance-name

      The view of a VPN instance is displayed.

   3. Enter the VPN instance IPv4/IPv6 address family view.

      • Run ipv4-family

        The VPN instance IPv4 address family view is displayed.

      • Run ipv6-family

        The VPN instance IPv6 address family view is displayed.

   4. Run export route-policy policy-name evpn

      The L3VPN instance is associated with an export route policy, which filters routes that the L3VPN instance will advertise to an EVPN instance. This ensures that the L3VPN instance advertises only static VPN routes reachable to the VNF to EVPN.

   5. Run quit

      Exit from the VPN instance IPv4/IPv6 address family view.

   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 BGP-VPN instance IPv4/IPv6 address family view.

      • Run ipv4-family vpn-instance vpn-instance-name

        The BGP-VPN instance IPv4 address family view is displayed.

      • Run ipv6-family vpn-instance vpn-instance-name

        The BGP-VPN instance IPv6 address family view is displayed.

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

      The device is enabled to import static routes into the routing table of the BGP-VPN instance IPv4/IPv6 address family.

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

       The VPN instance is enabled to advertise EVPN IP prefix routes. If load balancing is required, specifying the import-route-multipath parameter is recommended, so that the VPN instance can advertise all routes with the same destination address as EVPN IP prefix routes.

   11. (Optional) Run irb asymmetric

       The asymmetric mode is enabled for IRB routes. If L2GW/L3GWs are configured to advertise ARP (ND) routes to each other, skip this step. If L2GW/L3GWs are configured to advertise IRB (IRBv6) routes each other, perform this step so that the L2GW/L3GWs do not generate IP prefix routes. This helps prevent route loops.

   12. Run quit

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

3. Configure the L2GW/L3GW to advertise IRB (IRBv6) or ARP (ND) routes to a DC gateway.
   1. Run l2vpn-family evpn

      The BGP-EVPN address family view is displayed.

   2. Run peer { ipv4-address | group-name } advertise { irb | arp | irbv6 | nd }

      The device is enabled to advertise IRB (IRBv6) or ARP (ND) routes. If ARP (ND) routes need to be advertised, the L2GW/L3GW sends only routes carrying MAC and ARP information to the DC gateway. If IRB (IRBv6) routes need to be advertised, the L2GW/L3GW sends the MAC addresses, ARP information, and L3 VNI to the DC gateway. In this case, however, the irb asymmetric command must be enabled on the DC gateway so that the DC gateway does not generate IP prefix routes based on the IP address and L3 VNI. This prevents route loops on the network.

   3. Run quit

      Exit from the BGP-EVPN address family view.

   4. Run quit

      Exit from the BGP view.

4. Run commit

   The configuration is committed.