No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - VPN 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - VPN
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring an HVPN

Configuring an HVPN

On an HVPN, PEs play different roles and provide different functions. These PEs form a hierarchical architecture to provide functions that are provided by one PE on a non-hierarchical VPN. HVPNs lower the performance requirements for PEs.

Usage Scenario

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.

Figure 5-12 shows the basic architecture of an HVPN, which consists of the following device roles:
  • 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.
Figure 5-12 HVPN architecture

An HVPN can be either an HoVPN or an H-VPN:
  • 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.

Pre-configuration Tasks

Before you configure an HVPN, configure a basic BGP/MPLS IP VPN.

Configuration Procedures

Perform one or more of the following configurations as required.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 33423

Downloads: 59

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next