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

S7700 and S9700 V200R013C00

This document describes the configurations of VPN, including GRE, IPSec, BGP/MPLS IP VPN, BGP/MPLS IPv6 VPN, VLL, PWE3, VPLS, L2VPN Access to L3VPN.
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 VSIs and Configuring the BGP Signaling

Creating VSIs and Configuring the BGP Signaling


When configuring Kompella VPLS, you need to create and configure VSIs (set RDs and VPN targets of the VSIs), configure BGP, and create site connections. Configure two VSIs with the same attributes on two dual-homed PEs.

Do as follows on the PEs:


  1. Run system-view

    The system view is displayed.

  2. Run vsi vsi-name auto

    VSIs are created and the automatic member discovery mechanism is used.

    The Kompella VPLS does not directly run on the connection between CEs. Each CE has a globally unique number. On a PE, a VSI is created for each CE that is directly connected to this PE device.

  3. Run pwsignal bgp

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

  4. Run route-distinguisher route-distinguisher

    The RD is configured for the VSI.

    After configuring BGP as the PW signaling protocol, you must configure the RD of the VSI to validate the VSI.

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

    A VPN target is configured for the VSI.

    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 } ]

    Information about the sites of the VSI is configured.

    The site ID of the local end must be less than the sum of the site-range value and default-offset value on the peer end. The site ID of the local end cannot be less than the default-offset value of the peer end.


    At present, the VSIs of the two dual-homed PEs can be configured with only one label block. To enlarge the range, use the undo site command to delete all the original sites and then configure a larger range. In addition, the VSIs of the two dual-homed PEs can be configured with only one AC.

  7. Run encapsulation rfc4761-compatible

    The encapsulation type for Kompella VPLS is configured to be in compliance with RFC 4761.

    Before a Kompella VPLS network sends packets with encapsulation types other than encapsulation type 19, the network converts the encapsulation types of these packets to encapsulation type 19.

    If a Kompella VPLS network receives packets with encapsulation type 19, the network automatically converts the encapsulation types of these packets to its own encapsulation type.

Updated: 2019-04-08

Document ID: EDOC1100065751

Views: 39086

Downloads: 50

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