For hierarchical VPNs, you can adopt HoVPN to reduce the performance requirements for PEs.
Configuration Prerequisites
Before configuring HoVPN, complete these tasks:
Configuring HoVPNs
Follow these steps to configure HoVPN:
With the peer default-route-advertise vpn-instance command configured, the SPE always advertises a default route using the local address as the next hop address to the UPE, regardless of whether the default route is present in the local routing table or not.
Note:
Configuration Prerequisites
Before configuring HoVPN, complete these tasks:
- Configuring basic MPLS L3VPN
Configuring HoVPNs
Follow these steps to configure HoVPN:
With the peer default-route-advertise vpn-instance command configured, the SPE always advertises a default route using the local address as the next hop address to the UPE, regardless of whether the default route is present in the local routing table or not.
Note:
- The default routes of a VPN instance can be advertised to only a BGP peer or peer group that is UPE.
- It is not recommended to configure the peer default-route-advertise vpn-instance command and the peer upe route-policy command at the same time.
- It is not recommended for an SPE to be connected to a CE directly. If an SPE must be directly connected with a CE, the VPN instance on the SPE and that on the UPE must be configured with different RDs.
No comments:
Post a Comment