Configuring an EVPN L3VPN HoVPN over MPLS

On an EVPN L3VPN HoVPN over MPLS, a UPE only needs to obtain a default route from an SPE. This mechanism isolates routes and reduces the route storage space required on a UPE.

Context

On an EVPN L3VPN HoVPN over MPLS, the following configurations must be performed:

Create VPN instances on UPE, SPEs, and NPEs and bind the VPN instances to AC interfaces or bind the IPv6 VPN instances to AC interfaces on the UPEs and NPEs.

According to relevant standards, the VPN instance status obtained from an NMS is Up only if at least one interface bound to the VPN instance is Up. On an HoVPN, VPN instances on SPEs are not bound to interfaces. As a result, the VPN instance status obtained from an NMS is always Down. To solve this problem, run the transit-vpn command in the VPN instance view or VPN instance IPv4 or IPv6 address family view of an SPE. Then, the VPN instance status obtained from the NMS is always Up, regardless of whether the VPN instance is bound to interfaces.
Configure BGP-EVPN peer relationships between UPEs and SPEs and between SPEs and NPEs. For details, see Establishing a BGP EVPN Peer Relationships.
Configure routing protocols for NPEs and UPEs to exchange routes with CEs. This configuration is similar to configuring PEs and CEs to exchange routes on a BGP/MPLS VPN. For more information, see Configuring Route Exchange Between PEs and CEs or Configuring IPv6 Route Exchange Between PEs and CEs.
Configure SPEs to advertise only default or summarized routes to UPEs. For details, see Procedure.

Procedure

Configure an SPE to advertise only default or summarized routes to a UPE.
- Configure the SPE to advertise default routes to the UPE.
  1. Run system-view
    
    The system view is displayed.
  2. 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 ] } or ipv6 route-static vpn-instance vpn-instance-name 0::0 0 { nexthop-ipv6-address | interface-type interface-number [ nexthop-ipv6-address ] }
    
    A default IPv4/IPv6 static route is created for the VPN instance.
  3. Run bgp { as-number-plain | as-number-dot }
    
    The BGP view is displayed.
  4. Run ipv4-family vpn-instance vpn-instance-name or ipv6-family vpn-instance vpn-instance-name
    
    The BGP-VPN instance IPv4/IPv6 address family view is displayed.
  5. Run network 0.0.0.0 [ 0.0.0.0 | 0 ] [ route-policy route-policy-name ]network 0::0 0 [ route-policy route-policy-name ]
    
    The default route is imported to the IPv4/IPv6 VPN instance routing table.
  6. Run advertise l2vpn evpn
    
    The SPE is enabled to advertise IP prefix routes.
  7. Run quit
    
    Return to BGP view.
  8. Run l2vpn-family evpn
    
    The BGP-EVPN address family view is displayed.
  9. Run peer { ipv4-address | group-name } upe
    
    The UPE is specified as a lower-level PE of the SPE.
  10. Run commit
    
    The configuration is committed.
  Configure a route policy on the NPE to prevent the NPE from receiving default routes.
- Configure the SPE to advertise summarized routes to the UPE.
  1. Run system-view
    
    The system view is displayed.
  2. Run bgp { as-number-plain | as-number-dot }
    
    The BGP view is displayed.
  3. Run ipv4-family vpn-instance vpn-instance-name or ipv6-family vpn-instance vpn-instance-name
    
    The BGP-VPN instance IPv4/IPv6 address family view is displayed.
  4. Run aggregate ipv4-address { mask | mask-length } [ as-set | attribute-policy route-policy-name1 | detail-suppressed | origin-policy route-policy-name2 | suppress-policy route-policy-name3 ] ^* or aggregate ipv6-address prefix-length [ as-set | attribute-policy route-policy-name1 | detail-suppressed | origin-policy route-policy-name2 | suppress-policy route-policy-name3 ] ^*
    
    A summarized route is created.
  5. Run advertise l2vpn evpn
    
    The SPE is enabled to advertise IP prefix routes.
  6. Run quit
    
    Return to BGP view.
  7. Run l2vpn-family evpn
    
    The BGP-EVPN address family view is displayed.
  8. Run peer { ipv4-address | group-name } upe
    
    The UPE is specified as a lower-level PE of the SPE.
  9. Run commit
    
    The configuration is committed.
(Optional) Configure route next hop modification on the SPE.
1. Run system-view
  
  The system view is displayed.
2. Run bgp { as-number-plain | as-number-dot }
  
  The BGP view is displayed.
3. Run l2vpn-family evpn
  
  The BGP-EVPN address family view is displayed.
4. Run peer { ipv4-address | group-name } next-hop-local
  
  The SPE is configured to use its own IP address as the next hop of routes when advertising these routes to the NPE.
5. Run commit
  
  The configuration is committed.