Route advertisement can be configured on DC-GWs to allow the DC-GWs to construct their own forwarding entries based on the received EVPN routes.
The system view is displayed.
The loopback interface view is displayed.
The loopback interface is bound to an L3VPN instance.
IPv6 is enabled on the loopback interface. This step is mandatory when the loopback interface is configured with an IPv6 address.
To configure an IPv4 address for the loopback interface, run the ip address ip-address { mask | mask-length } command.
To configure an IPv6 address for the loopback interface, run the ipv6 address { ipv6-address prefix-length | ipv6-address/prefix-length } command.
Exit from the loopback interface view.
Export route-policy: An if-match clause configured in the route-policy can be used to filter VPN loopback routes and mobile phone routes in the L3VPN instance. You can run the apply gateway-ip { origin-nexthop | ipv4-address } or apply ipv6 gateway-ip { origin-nexthop | ipv6-address } command to configure the original next-hop address of mobile phone routes as a gateway address.
Import route-policy: You can run the apply gateway-ip none or apply ipv6 gateway-ip none command to delete gateway addresses from the routes received from L2GW/L3GWs to ensure that the BGP VPN packets sent by DC-GWs to VNFs can be recursed over SR tunnels, instead of being forwarded through VBDIF interfaces based on gateway addresses (DC-GWs do not have VBDIF interfaces).
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 mobile phone routes and VPN loopback routes to the EVPN instance.
The L3VPN instance is bound to an import route-policy. This route-policy is used to filter the routes received by the L3VPN instance so that the gateway addresses are deleted from the routes received from L2GW/L3GWs.
Exit from the IPv4 or IPv6 address family view of the VPN instance.
Exit from the VPN instance view.
The BGP view is displayed.
The BGP-EVPN address family view is displayed.
The route-policy is used to prohibit DC-GWs from advertising mobile phone routes to each other.
Exit from the BGP-EVPN address family view.
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.
VPN loopback 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.
Exit from the IPv4 or IPv6 address family view of the BGP-VPN instance.
Exit from the BGP view.
A route-policy that denies all routes is created.
Exit from the route-policy 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.
A BGP VPN peer relationship is established.
The source interface and source IP address are specified for the TCP connection to be set up between BGP peers.
The route-policy is applied so that DC-GWs do not advertise BGP VPN routes to VNFs. This prevents route loops.
The RR function is configured to reflect BGP VPN routes. This function allows VNFs to share mobile phone routes.
Exit from the IPv4 or IPv6 address family view of the BGP-VPN instance.
The BGP-EVPN address family view is displayed.
L2GW/L3GWs and PEs are configured as RR clients.
DC-GWs are configured not to modify the next hop during route advertisement to PEs and L2GW/L3GWs and the next-hop address is still the IP address of an L2GW/L3GW when a PE receives routes from a VNF. Upon receipt of default routes, the next -hop addresses of L2GW/L3GWs are the IP addresses of PEs. In this way, routes are recursed over E2E SR-MPLS TE tunnels.
The configuration is committed.