what is the different between the HVPN and the HoVPN?

Created: Aug 23, 2018 08:40:29Latest reply: Aug 23, 2018 14:53:05 1181 1 0 0

The BGP/MPLS IP VPN architecture is a plane model. The performance requirements for each PE on a BGP/MPLS IP VPN are the same. On a hierarchical network configured with BGP/MPLS IP VPN, the access or routing management capabilities of PEs are frequently challenged as the network expands in scale and service types. As a result, limited network performance and expansibility prevent VPN services from being deployed on a large scale.

To improve expansibility, BGP/MPLS IP VPN must adopt the HVPN model. On an HVPN, PEs play different roles and provide different functions. These PEs form a hierarchical architecture to provide the same functions as that are normally provided by a single PE on a non-hierarchical VPN.

Upper-level devices on an HVPN must have strong routing management and forwarding capabilities, but do not need strong access capabilities. Conversely, lower-level devices on an HVPN must have strong access capabilities, but do not need strong routing management or forwarding capabilities. Different types of devices can be deployed at different hierarchical levels. An HVPN features flexible device deployment and high expansibility. If the access, routing management, or forwarding capabilities of the PEs at a certain hierarchical level cannot meet actual requirements, you can deploy more PEs to that hierarchical level.

There have three roles on the HVPN:

User-end provider edge (UPE): directly connects to CEs and provides access services for users.

Superstratum provider edge (SPE): connects to UPEs and is located at the core of a network. An SPE manages and advertises VPN routes.

Network provider edge (NPE): connects to SPEs and is located at the network side.

There have two configurations on the HVPN, one is called HVPN, the other is called HoVPN.

The different is as below:

On an HoVPN, SPEs advertise default routes to UPEs. UPEs do not have specific routes to NPEs and can only send VPN service data to SPEs over default routes. As a result, route isolation is implemented. An HoVPN can use devices with relatively poor route management capabilities as UPEs, reducing network deployment costs.

On an H-VPN, SPEs advertise specific routes to UPEs. UPEs function as RR clients to receive the specific routes reflected by SPEs functioning as RRs. This mechanism facilitates route management and traffic forwarding control.


This post was last edited by yiyi0519 at 2018-08-23 08:50.
  • x
  • convention:

WoodWood     Created Aug 23, 2018 14:53:05 Helpful(0) Helpful(0)

  • x
  • convention:


You need to log in to reply to the post Login | Register

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " Privacy."
If the attachment button is not available, update the Adobe Flash Player to the latest version!

Login and enjoy all the member benefits

Fast reply Scroll to top