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.


Configuration Guide - VPN

CloudEngine 12800 and 12800E V200R005C10

This document describes the configurations of VPN, including GRE, BGP/MPLS IP VPN, BGP/MPLS IPv6 VPN, VLL, PWE3, and VPLS.
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).
Licensing Requirements and Limitations for VPLS

Licensing Requirements and Limitations for VPLS

Involved Network Elements

Other network elements are not required.

License Requirements

You can use the VPLS feature only after the MPLS function is enabled. The MPLS function is controlled by a license. By default, MPLS is disabled on a new device. To use the MPLS function, apply for and purchase the license from the equipment supplier.

Version Requirements

Table 6-6 Products and minimum version supporting VPLS

Product Model

Minimum Version Required







Feature Limitations

Limitations on VPLS

  • The device supports only IPv4 VPLS.
  • The device supports only the unqualified mode in which the device learns MAC addresses.
  • The device cannot transmit Layer 2 protocol packets such as BPDUs on a VPLS network.
  • The device supports GRE tunnels or LSPs used to transmit the VPLS service, but load balances VPLS service traffic only through LSPs.
  • The device only supports LDP hierarchical virtual private LAN service (HVPLS). A UPE connects to an SPE through LSPs.
  • When the PW type is GRE tunnel, and multiple public network tunnels are the ECMP next hop, traffic can be forwarded over only of these tunnels. Load balancing is not supported in this case.
  • The device does not support VPLS access through main interfaces.
  • For the EA, EC, BA, EC1, ED, EF, and EG series cards in an Option C VPLS scenario, the ASBRs do not support explicit null labels being used as the outermost labels.

Limitations on VPLS traffic statistics

  • VPLS traffic statistics collection and GRE traffic statistics collection do not take effect simultaneously on the device.
  • When a VSI contains multiple PWs, the device collects statistics on VPLS traffic on multiple PWs.
  • Within five minutes, if a PW goes Down, VPLS traffic before the PW is Down cannot be used to compute the traffic rate in the five minutes.
  • Slight deviation exists in the VSI's outgoing traffic statistics. Each multicast or broadcast packet forwarded at Layer 2 has two less bytes than the actual value. Each packet forwarded at Layer 3 has six more bytes than the actual value.
  • Some traffic statistics data will be lost after an active/standby switchover or a card restart.

Limitations when VPLS is used with other services

  • Binding VSI to BD cannot be configured together with the following features:
    • Binding VLAN to BD
    • Binding VNI to BD
    • M-LAG
    • Creating a VBDIF interface
    • ARP broadcast suppression
  • If the encapsulation type of the VSI is VLAN, the type of the Layer 2 sub-interface added to the BD must be transparent transmission. If the encapsulation type of the VSI is Ethernet, the type of the Layer 2 sub-interface added to the BD must be termination.
  • Only the Admin-VS in port mode supports VPLS; all VSs in group mode support VPLS.
  • VPLS over GRE and ERSPAN cannot be configured together in the Admin-VS in port mode; VPLS over GRE and Layer 3 remote port mirroring cannot be configured together in a VS in group mode.
  • The Layer 2 port isolation and VPLS functions can be configured on a switch together only when the card interoperability mode is set to enhanced mode.

  • The VLANIF interface corresponding to a VLAN cannot be used as the AC interface in the following situations:
    • The physical interface in the VLAN is configured with port security, or static MAC address entries are generated according to the Dynamic Host Configuration Protocol (DHCP) snooping binding table on the interface.
    • IGMP snooping is configured in the VLAN.
    • The VLAN is specified as a CE VLAN for a Transparent Interconnection of Lots of Links (TRILL) process.
    • The VLAN is used as the MUX VLAN.
    • The VLAN is not mapped to MSTI 0.
  • The egress node cannot load balance VPLS packets over Eth-Trunk based on the inner IP header.
  • The VBST and VPLS functions can be configured on a switch together only when the card interoperability mode is set to enhanced mode.

  • LDP over SR-TE is not supported in the VPLS scenario.
  • In V200R003C00 and later versions, the device functions as a PE node in an IPv6 VXLAN network. When the device also functions as a transit or an egress node in a VPLS network, traffic cannot be load balanced based on the inner Ethernet header.

Updated: 2019-04-03

Document ID: EDOC1100075353

Views: 14552

Downloads: 25

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