On an H-VPN, SPEs function as RRs and UPEs function as RR clients. UPEs receive specific routes from SPEs.
Configure a VPN instance on each UPE and NPE. For configuration details, see Configuring a VPN Instance.
Configure an MP-BGP peer relationship between each SPE and NPE and between each UPE and SPE. This configuration is similar to configuring an MP-IBGP peer relationship between PEs on a BGP/MPLS IP VPN. For configuration details, see Establishing MP-IBGP Peer Relationships Between PEs.
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 IP VPN. For configuration details, see Configuring Route Exchange Between PEs and CEs.
Configure SPEs as RRs and configure UPEs as RR clients.
Perform the following steps on each SPE.
The system view is displayed.
The BGP view is displayed.
The BGP-VPNv4 address family view is displayed.
The SPE is configured as an RR and the UPEs are configured as RR clients.
The SPE is configured to use its own IP address as the next hops of routes when advertising these routes.
To enable an SPE to use its own IP address as the next hops of routes when advertising these routes to UPEs and NPEs, run the peer next-hop-local command twice with different parameters specified on the SPE.
One-label-per-next-hop label distribution is enabled on the SPE.
In an H-VPN scenario, if an SPE needs to send large numbers of VPNv4 routes but the MPLS labels are inadequate, configure one-label-per-next-hop label distribution on the SPE.
The configuration is committed.