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).
Limitations for IP Hard Pipe-NE08E

Limitations for IP Hard Pipe-NE08E

Restrictions

Guidelines

Impact

In IP hard-pipe scenarios:

1. If the hard pipe function is enabled in the VSI-LDP view, only static PWs can be configured, and a tunnel binding policy must be configured, and the tunnel must be static bidirectional LSPs.

2. If an LDP peer relationship is established in the VSI-LDP view, no hard pipe can be configured.

3. If QoS is configured for a PW, no hard pipe can be configured.

4. Only LDP VSIs are supported.

5. Hard-pipe VSIs cannot be bound to virtual access interfaces.

None

When a hard pipe is configured in the VSI-LDP view, if the tunnel bound using a tunnel policy is not a static bidirectional co-routed TE tunnel, services are compromised.

IP hard pipe and DiffServ mode on an interface are mutually exclusive.

None

IP hard pipe and DiffServ mode on an interface are mutually exclusive.

An MP2MP IP hard pipe supports TP OAM for TE to detect link faults and APS for TE to trigger link protection. However, TP OAM for VPLS PW and PW APS are not supported.

Hard-pipe link protection can use the detection and protection mechanisms of TE tunnels.

If TP OAM for VPLS PW and PW APS are configured, the hard pipe function may be unavailable.

After an MP2MP IP hard pipe is configured for a VPLS, the default MPLS differentiated services (DS) mode is pipe enhancement. The diffserv-mode command cannot be run with the pipe or shortpipe parameter specified.

None

None

An MP2MP IP hard pipe must be established over a static bidirectional co-routed TE tunnel (public-network tunnel), and the tunnel interface must have hard-pipe bandwidth specified.

If an E2E VPLS hard pipe is deployed on the NMS, the preceding requirement does not have to be met.

If a hard pipe configured using a command is iterated to a tunnel, the involved PW does not take effect, and services are interrupted.

The public network side of an MP2MP IP hard pipe does not support tunnel load balancing, and the tunnel interface must be unique.

If an E2E VPLS hard pipe is deployed on the NMS, the preceding requirement does not have to be met.

The VPLS hard pipe fails, and bandwidth cannot be guaranteed.

On an MP2MP IP hard pipe, multiple ACs communicate with multiple PWs. The hard-pipe bandwidth between the ACs and PWs cannot be checked.

A PW's hard-pipe bandwidth value must be greater than the total bandwidth value of all AC interfaces in the same VSI.

If the total bandwidth value of all AC interfaces in the same VSI exceeds the PW's hard-pipe bandwidth value, packets are lost.

If a VLL hard pipe and an MP2MP IP hard pipe co-exist on the same main interface, interface-based bandwidth check for the VLL hard pipe may be inaccurate.

A VLL hard pipe and an MP2MP IP hard pipe cannot be configured on the same interface.

The VLL hard-pipe bandwidth check is not accurate.

For an MP2MP IP hard pipe, the pipe attribute of a primary TE tunnel and that of a backup TE tunnel must be the same. That is, they are both soft pipes or both hard pipes.

If an E2E VPLS hard pipe is deployed on the NMS, the preceding requirement does not have to be met.

If a hard pipe configured using a command is iterated to a primary tunnel and backup tunnel whose hard pipe attributes are inconsistent, the involved PW does not take effect, and services are interrupted.

An MP2MP IP hard pipe for rail transport and HQoS on an AC interface are mutually exclusive.

None

If an AC interface has HQoS enabled, a VPLS hard pipe cannot be configured on the AC interface.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 33462

Downloads: 59

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