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


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


Feature Description - VPN 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Feature Description - 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).
Centralized Management of IP Hard-Pipe-based Leased Line Services on the NMS

Centralized Management of IP Hard-Pipe-based Leased Line Services on the NMS

In the IP hard pipe solution, the NMS centrally manages bandwidth resources and implements service provisioning. Hard pipe service provisioning involves two steps:

  1. Establish a hard pipe plane.
    Figure 7-2 IP hard pipe topology establishment 1

    In the physical network topology, select the public network links that require hard pipe deployment and set the hard pipe bandwidth for each link. The hard pipe topology is then established. On the network shown in Figure 7-3, after hard pipes are classified on the entire network, the original network is divided into two logical networks: a hard pipe network and a normal service network (called a soft pipe network).

    Figure 7-3 IP hard pipe topology establishment 2

  2. Service provisioning

    The service bandwidth, source and destination devices, and service IDs are manually configured for VIP customers. The intermediate path can be configured or automatically calculated by the NMS.

    The NMS checks the hard pipe bandwidth on each node to see if the bandwidth is adequate for service provisioning. If not, the NMS stops service provisioning and informs users of it.

    The NMS delivers configurations to devices.

    After service provisioning succeeds, the NMS updates the bandwidth resource database.

    Figure 7-4 IP hard pipe service provisioning

Updated: 2019-01-14

Document ID: EDOC1100058940

Views: 19756

Downloads: 36

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