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 VPWS-NE05E

Limitations for VPWS-NE05E

Restrictions

Guidelines

Impact

The basic single-ICB PW functions have the following restrictions: Single-ICB supports only scenarios with three PEs.
  • When the single-ICB PW works with the E-trunk, the sequence cannot be controlled due to multi-device table entry delivery. Traffic switchover due to AC faults is affected by the E-trunk protocol convergence performance, and specifications cannot be ensured. Packets are lost or the CSG receives unexpected packets for hundreds of millisecond or several seconds.
  • When the E-trunk associates with BFD for mPW for fast updates, only the scenario where the proportion of E-trunks, Eth-Trunks, and trunk members is 1:1:1 is supported. The scenario where an E-trunk has multiple Eth-Trunks or a trunk has multiple members are not supported. In the mode where BFD for mPW associates with the E-trunk, fast lower-layer trunk switchover is triggered when BFD is Down.

    If the ICB PW flaps, BFD flaps. As a result, the master/slave E-trunk status flaps, affecting E-trunk switchover. However, packets can be forwarded properly.

  • The MPLS QoS function based on the ICB PW is not supported.

None

  • Packets are lost.
  • Packets are lost.
  • QoS does not take effect.
The basic single-ICB PW functions have the following restrictions:
  • Single-ICB supports only scenarios with three PEs.
  • ICB PW failures are not supported.
  • Load balancing is not supported when traffic is transmitted over the ICB-PW.
  • LDP FRR is not supported.

None

The function cannot be implemented.

The basic dual-ICB PW functions have the following restrictions:
  • The control words of the ICB PW, working PW, and protection PW must be the same.
  • The ICB PW public network does not support ECMP.
  • Secondary failures are not supported.
  • QinQ interfaces at the AC side are not supported.

None

Traffic is interrupted.

The basic dual-ICB PW functions have the following restrictions:
  • In an E-APS 1+1 scenario, only dual-ICB PWs are supported. VLL heterogeneous media are not supported.
  • In an APS 1+1 scenario, fast switchover for TE protection is not supported.
  • When the AC is faulty or a fault recovers, double active APSs or double standby APSs may exist temporarily due to inter-chassis APS. As a result, unexpected packets are received or packets are lost temporarily.
  • The MPLS QoS function based on dual-ICB PWs is not supported.

None

Services are interrupted.

Different DiffServ modes can be configured in the inbound and outbound directions of a PE.

Hard-pipe static VLLs and DiffServ modes are mutually exclusive.

Do not configure any DiffServ mode in hard-pipe scenarios.

The function does not take effect.

VPWS heterogeneous interworking is supported. IPv4 packets are supported, whereas IPv6 packets are not.

None

Traffic is interrupted.

VPWSs support GRE tunnels. ICB PWs do not support GRE tunnels.

None

Traffic is interrupted.

The VPWS flow label has the following restrictions:
  • The public network tunnel type does not support GRE tunnels.
  • The VLL service type does not support the Kompella mode.

None

The function cannot be implemented.

Multi-hop tunnel attributes:LDP PW multi-hop end nodes and intermediate nodes do not support GRE tunnels.

None

Traffic is interrupted.

AC interfaces:VE interface access is supported. The Martini mode is supported, whereas the Kompella mode is not.

None

This function cannot be implemented.

EVC sub-interface access to the VLL has the following restrictions:
  • VLAN or Ethernet encapsulation is supported, without affecting encapsulation of tags that enter the public network. PW tags cannot be configured.
  • Public and private network label EXP priority separation is not supported.
  • Heterogeneous medium is not supported.
  • The access SVC does not support the hard pipe.
  • ETH-OAM services are not supported.
  • CCC is not supported.

None

This function cannot be implemented.

In an L2VPN over PWE3 scenario where inner and outer VLAN tags carry control words, the ingress PE supports in-depth load balancing rather than IP-based load balancing.

None

In the ETH+MPLS+CW+ETH+MPLS+CW+IP scenario, the device performs load balancing based on labels rather than IP addresses.

The PW redundancy mode has the following restrictions:

In a VLL accessing VPLS scenario, only the master/slave mode is supported.

None

The function cannot be implemented.

The PW redundancy mode has the following restrictions:

The Kompella mode does not support VLL PW redundancy.

None

The function cannot be implemented.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 27633

Downloads: 53

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