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 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 BGP AD VPLS

Configuring BGP AD VPLS

BGP AD VPLS-enabled devices exchange extended BGP packets to automatically discover member VSIs in a VPLS domain and then use LDP FEC 129 to negotiate PW establishment to achieve automatic VPLS PW deployment.

Usage Scenario

As VPLS technologies are widely employed and VPLS networks increase in their scale, VPLS configurations on networks increase accordingly. To simplify network configurations and reduce carriers' operational expenditure (OpEx), BGP AD VPLS is used. It can achieve automatic service deployment.

BGP AD VPLS has the advantages of Kompella VPLS and Martini VPLS. BGP AD VPLS-enabled devices exchange extended BGP packets to automatically discover member VSIs in a VPLS domain and then use LDP FEC 129 to negotiate PW establishment to achieve automatic VPLS PW deployment.

BGP AD VPLS also has the following advantages as compared with other VPLS configuration modes:

  • As shown in Table 9-1, BGP AD VPLS saves label resources on PEs. To establish PWs with each other, PEs use LDP signaling as PW establishment is quite complicated.

  • As shown in Table 9-2, BGP AD VPLS uses existing BGP sessions to discover member VSIs in a VPLS domain when new nodes are added to VPLS domains or new VPLS domains are deployed. If member VSIs in a VPLS domain are discovered, BGP AD VPLS-enabled devices can automatically establish PWs with each other. This simplifies PW configurations on PEs.

With automatic VPLS member discovery and PW deployment, BGP AD VPLS simplifies VPLS network configuration, achieves automatic service deployment, and reduces carriers' OpEx.

Table 9-1 Comparison between BGP AD VPLS and Kompella VPLS


Advantage Disadvantage

Kompella VPLS

  • Kompella VPLS-enabled devices exchange BGP Update packets that carry VPLS label block information and compute and compare received label block information with the local label block information before establishing a PW with each other.
  • Kompella VPLS implementation is simpler than BGP AD VPLS implementation.
  • Labels are wasted.
  • Site ID management is needed.
  • There is no standard mechanism of clearing MAC address entries.


  • Label resources are saved.
  • BGP AD VPLS-enabled devices can communicate with PWE3-enabled devices by using LDP FEC 128.
  • To establish a PW with each other, BGP AD VPLS-enabled devices need to use LDP signaling packets to exchange label information after VPLS member discovery.
  • BGP AD VPLS depends on BGP capabilities and its implementation is complex.
Table 9-2 Comparison of VPLS configurations in BGP AD VPLS mode and Martini VPLS mode when existing BGP sessions are used for VPLS member discovery after new nodes are added


VSI Configurations on New Nodes

Additional Configurations on Existing Nodes

Martini VPLS

vsi-id company1
 pwsignal ldp
  vsi-id 2
  peer x.x.x.x
vsi-id company1
 pwsignal ldp
  vsi-id 2
  peer y.y.y.y


vsi-id company1
  vpls-id 10
  peer x.x.x.x enable

No additional configurations need to be performed.

BGP AD VPLS-enabled devices exchange extended BGP Update packets that carry VSI member information to automatically discover member VSIs in a VPLS domain and then use LDP FEC 129 signaling to negotiate and establish PWs between the member VSIs that are discovered. BGP AD VPLS allows automatic VSI member discovery and automatic VPLS PW deployment in VPLS domains. Therefore, existing VSIs do not need additional configuration.

On the network shown in Figure 9-16, BGP sessions are established between PE1, PE2, and PE3, and BGP AD VPLS is configured on PE1 and PE2 that reside in the same VPLS domain. PE3 needs to be added to the VPLS domain for network expansion. To achieve this goal, configuring the ID of the VPLS domain for a VSI on PE3 is required. VPLS configurations do not need to be modified on BGP AD VPLS-enabled PE1 and PE2. After PE3 joins the domain, PWs can be automatically established using BGP AD VPLS between PE1 and PE3 and between PE2 and PE3. This simplifies VPLS configuration.

Figure 9-16 Full-mesh BGP AD VPLS networking

BGP AD also supports HVPLS. The pw spoke-mode command can be run to configure the PWs of BGP AD VSIs as spoke PWs. After the command is run, remote peers of a PE are used as user-side devices on an HVPLS network.

Pre-configuration Tasks

Before configuring BGP AD VPLS, complete the following tasks:

  • Configure IP addresses and routes on PEs and Ps to ensure that neighboring nodes are reachable at the network layer.

  • Configure LSR IDs and enable basic MPLS functions on PEs and Ps.

  • Establish tunnels between PEs to bear L2VPN services.

  • Enable MPLS L2VPN on PEs.

Configuration Procedures

Figure 9-17 Flowchart for BGP AD VPLS
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 33615

Downloads: 59

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