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

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 AD Signaling

Creating VSIs and Configuring the BGP AD Signaling

Context

When configuring BGP AD VPLS, you need to create VSIs on PEs, set automatic VPLS member discovery and PW deployment for the VSIs, configure BGP AD signaling on the PEs, and set VPLS IDs and VPN targets for the VSIs in the VSI-BGPAD view.

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

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run vsi vsi-name

    A VSI is created.

  3. Run bgp-ad

    Automatic VPLS member discovery and PW deployment are set for the VSI, and the VSI-BGP AD view is displayed.

  4. Run vpls-id vpls-id

    A VPLS ID is set.

    NOTE:
    • By default, the RD of BGP AD VPLS is the same as the VPLS ID. If a VPLS ID is set, an RD does not need to be set. The VSI ID is equal to the local LSR ID and does not need to be set.

    • The VPLS IDs for VSIs in one VPLS domain must be the same.

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

    A VPN target is configured for the VSI.

    The mappings between the local VPN target attribute and the peer VPN target attribute must be correct:

    • The local export-extcommunity is the same as the peer import-extcommunity.

    • The local import-extcommunity is the same as the peer export-extcommunity.

    Traffic is transmitted properly in a bidirectional manner only if the preceding two conditions are both met. If only one condition is met, traffic is transmitted only in a unidirectional manner. These four parameters are usually set to the same value.

  6. (Optional) Run pw spoke-mode

    Split horizon is disabled for all PWs in a VSI.

    By default, all PW attributes of a BGP AD VSI are Hub.

    NOTE:

    The function of this command is similar to the function of configuring a peer PE as a UPE on a Martini HVPLS network. The difference is that this command allows all peer PEs in a VPLS domain to serve as UPEs. This means a star topology, in which a PE functions as a Hub, and other PEs connected to this Hub are Spoke PEs.

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

      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.

Translation
Download
Updated: 2019-04-08

Document ID: EDOC1100065751

Views: 39144

Downloads: 50

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