Configuring Route Advertisement on a DC-GW

Procedure

1. Configure EVPN on the DC-GW to advertise default static routes and loopback routes in a VPN instance.
   1. Run system-view

      The system view is displayed.

   2. Run interface Loopback interface-number

      The loopback interface view is displayed.

   3. Run ip binding vpn-instance vpn-instance-name

      An L3VPN instance is bound to the loopback interface.

   4. (Optional) Run ipv6 enable

      IPv6 is enabled on the interface. This step is mandatory if the interface requires an IPv6 address.

   5. Configure an IPv4/IPv6 address for the interface.

      • Run ip address ip-address { mask | mask-length }

        An IPv4 address is configured for the interface.

      • Run ipv6 address { ipv6-address prefix-length | ipv6-address/prefix-length }

        An IPv6 address is configured for the interface.

   6. Run quit

      Exit from the loopback interface view.

   7. Configure a default static route for the VPN instance.

      • Run ip route-static vpn-instance vpn-instance-name 0.0.0.0 { 0.0.0.0 | 0 } { nexthop-address | interface-type interface-number [ nexthop-address ] } [ tag tag ]

        A default IPv4 static route is created for the VPN instance.

      • Run ipv6 route-static vpn-instance vpn-instance-name :: 0 { nexthop-ipv6–address | interface-type interface-number [ nexthop-ipv6-address ] } [ tag tag ]

        A default IPv6 static route is created for the VPN instance.

   8. Create a route policy to filter default static routes and loopback routes in the VPN instance. For configuration details, see Configuring a Route-Policy.
   9. Run ip vpn-instance vpn-instance-name

      The VPN instance view is displayed.

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

   11. Run export route-policy policy-name evpn

       The VPN instance is associated with an export route policy, which filters routes that the VPN instance will advertise to an EVPN instance. This ensures that the VPN instance advertises only its default static routes and loopback routes to the EVPN instance.

   12. Run quit

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

   13. Run quit

       Exit from the VPN instance view.

   14. Create a route-policy to filter the mobile phone routes received by the DC-GW from the L2GW/L3GW and prohibit the advertisement of such mobile phone routes. For details about how to create a route-policy, see Configuring a Route-Policy.
   15. Run bgp { as-number-plain | as-number-dot }

       The BGP view is displayed.

   16. Run l2vpn-family evpn

       The BGP-EVPN address family view is displayed.

   17. Run peer { group-name | ipv4-address } route-policy route-policy-name export

       The route-policy is used to prohibit DC-GWs from advertising mobile phone routes to each other.

   18. Run quit

       Exit from the BGP-EVPN address family view.

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

   20. Run import-route direct [ med med | route-policy route-policy-name ] ^*

       Importing loopback routes in the VPN instance to the BGP-VPN instance IPv4/IPv6 address family view is enabled on the device.

   21. Run network { 0.0.0.0 0 | :: 0 }

       Importing default static routes in the VPN instance to the BGP-VPN instance IPv4/IPv6 address family view is enabled on the device.

   22. Run advertise l2vpn evpn

       Advertising EVPN IP prefix routes is enabled in the VPN instance.

   23. Run quit

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

   24. Run quit

       Exit from the BGP view.

2. Configure the DC-GW to establish a VPN BGP peer relationship with a VNF.
   1. Run route-policy route-policy-name deny node node

      A route policy that denies all routes is created.

   2. Run quit

      Exit from the route-policy view.

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

      The BGP view is displayed.

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

   5. Run peer { ipv4-address | ipv6-address | group-name } as-number { as-number-plain | as-number-dot }

      A VPN BGP peer relationship is established.

   6. Run peer { ipv4-address | ipv6-address | group-name } connect-interface interface-type interface-number [ ipv4-source-address ]

      A source interface and a source IP address are specified to set up a TCP connection between the BGP peers.

   7. Run peer { ipv4-address | ipv6-address | group-name } route-policy route-policy-name export

      The route policy is applied so that the DC-GW does not advertise VPN BGP routes to the VNF to prevent route loops.

   8. Run quit

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

3. (Optional) Configure the asymmetric mode for IRB routes. If an L2GW/L3GW is configured to advertise IRB (IRBv6) routes to the DC-GW, you need to configure the IRB asymmetric function on the DC-GW.
   1. 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.

   2. Run irb asymmetric

      The asymmetric mode is enabled for IRB routes.

4. Run commit

   The configuration is committed.