Configuring Route Advertisement on L2GWs/L3GWs

Procedure

1. Use either of the following methods to configure a VPN route destined for a VNF on an L2GW/L3GW:
   • Configure a VPN static route destined for the VNF. For details, see IPv4 VPN Static Routes or IPv6 VPN Static Routes.
   • Configure L2GWs/L3GWs to establish VPN IGP neighbor relationships with VNFs. For details, see Configuring Basic IPv4 IS-IS Functions, Configuring Basic OSPF Functions, Configuring Basic IPv6 IS-IS Functions, or Configuring Basic OSPFv3 Functions.
     

     In an active-active L2GW/L3GW scenario, a secondary IP address (ip address ip-address sub) needs to be configured for the VBDIF interface on each L2GW/L3GW for the establishment of VPN IGP neighbor relationships with VNFs.

2. Configure an L3VPN instance on each L2GW/L3GW to advertise VPN routes destined for VNFs to the EVPN instance.
   1. Create a route-policy to filter VPN routes destined for VNFs in the L3VPN instance.

      For details about how to create a route-policy, see Routing Policy Configuration. When configuring the apply clause, you need to 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 addresses of VPN routes to the gateway address.

   2. Run the ip vpn-instance vpn-instance-name command to enter the VPN instance view.
   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 that is used to filter the routes to be advertised by the L3VPN instance to the EVPN instance, so that the L3VPN instance advertises only VPN routes destined for VNFs to the EVPN instance.

   5. Run quit

      Return to the VPN instance view.

   6. Run quit

      Return to the system 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 | { ospf | isis } process-id } [ med med | route-policy route-policy-name ] ^* or import-route { static | { ospfv3 | isis } process-id } [ med med | route-policy route-policy-name ] ^*

      Routes destined for VNFs are imported into the routing table for the BGP VPN instance IPv4 address family or BGP VPN instance 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, you are advised to specify the import-route-multipath keyword, so that a VPN instance can advertise all routes with the same destination address as EVPN IP prefix routes.

   11. Run quit

       Return to the BGP view.

3. Configure L2GWs/L3GWs to advertise IRB or IRBv6 routes to DC gateways.
   1. Run l2vpn-family evpn

      The BGP EVPN address family view is displayed.

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

      The device is configured to advertise IRB or IRBv6 routes to DC gateways.

   3. Run quit

      Return to the BGP view.

   4. Run quit

      Return to the system view.

4. Run commit

   The configuration is committed.