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

S9300, S9300E, and S9300X V200R010C00

This document describes the VPN configuration procedures and provides configuration examples.
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).
Creating a VSI and Configuring BGP Signaling

Creating a VSI and Configuring BGP Signaling


When configuring BGP VPLS to implement automatic discovery, you need to create and configure VSIs (set RDs and VPN targets of the VSIs), configure BGP, and create site connections.

Perform the following steps on PEs at both ends of a PW:


  1. Run:


    The system view is displayed.

  2. Run:

    vsi vsi-name auto

    A VSI is created and the automatic member discovery mechanism is configured.

    The Kompella VPLS does not directly deal with the connection between the CEs. It numbers the CEs and creates a VSI on the PE for each CE.

  3. Run:

    pwsignal bgp

    The PW signaling protocol is configured as BGP and the VSI-BGP view is displayed.

  4. Run:

    route-distinguisher route-distinguisher

    The RD of the VSI is configured.

    After the PW signaling protocol is configured as BGP, configure the RD to make the VSI take effect.


    For a PE, different VSIs have different RDs.

    For the same VSI on different PEs:

    • If a CE accesses two PEs, RDs of the VSI must be different.

    • If a CE accesses a PE, RDs of the VSI can be either the same or different.

  5. Run:

    vpn-target vpn-target & <1-16> [ both | export-extcommunity | import-extcommunity ]

    The VPN target of the VSI is configured.

    When using this command, note the mapping between the VPN target attribute at the local end and the VPN target at the remote end.

    • export-extcommunity of the local end must be consistent with import-extcommunity of the peer.

    • import-extcommunity of the local end must be consistent with export-extcommunity of the peer.

    Traffic can be normally transmitted in bidirectional way only if the preceding two conditions are satisfied. If only one condition is met, the traffic can be transmitted only in unidirectional way. For convenience of configuration, the four values are configured to be the same.
    When locating a VPLS fault, you can use the remote-vpn-target refresh command to refresh the VPN target of the remote end.

  6. Run:

    site site-id [ range site-range ] [ default-offset { 0 | 1 } ]

    The site ID is configured.

    The two ends of the VSI cannot be configured with the same site ID. The value of the local site ID must be less than the sum of the site-range and default-offset of the remote end. The value of the local site ID cannot be less than the value of the default-offset of the remote end. If the rang parameter is specified, the system reserves the required labels for the VSI.


    All Kompella L2VPN instances and VPLS VSI instances of one device share one label block; therefore, the sum of the ranges of all Kompella L2VPN instances and VPLS VSI instances cannot be greater than the label block. Otherwise, the system prompts that the labels cannot be obtained because the required labels exceed the upper limit. Allocation of a site ID to a VSI or creation of a CE fails.

  7. (Optional) The VPLS encapsulation type is configured.
    1. Run:


      Return to the VSI view.

    2. Run:

      encapsulation { ethernet | vlan }

      The VSI encapsulation type is configured.

      By default, the encapsulation type of the interface is VLAN.

      When the QinQ sub-interface or dot1q sub-interface is bound to the VSI, the VPLS encapsulation type cannot be set to ethernet.

Updated: 2019-08-21

Document ID: EDOC1000142068

Views: 119315

Downloads: 212

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