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 a Local BGP VPWS Connection

Configuring a Local BGP VPWS Connection

If two CEs connect to the same PE, you can configure a local BGP VPWS connection for the two CEs to communicate.


On the network shown in Figure 7-6, CE1 and CE2 connect to the same PE. A local BGP VPWS connection needs to be established between CE1 and CE2 for them to communicate. After the connection is established, the PE can function like a Layer 2 switch to directly transmit packets, without using any static LSP.

Figure 7-6 Configuring a local BGP VPWS connection


  1. Enable MPLS L2VPN.
    1. Run system-view

      The system view is displayed.

    2. Run mpls l2vpn

      MPLS L2VPN is enabled.

    3. Run quit

      Return to the system view.

  2. Configure a local BGP VPWS connection.
    1. Run mpls l2vpn l2vpn-name [ encapsulation encapsulation-type [ control-word | no-control-word ] ]

      A BGP VPWS instance is created, and the MPLS-L2VPN instance view is displayed.

      If heterogeneous interworking is required, specify encapsulation-type as ip-interworking for successful PW establishment.

    2. Run route-distinguisher route-distinguisher

      An RD is configured for the L2VPN instance.

    3. (Optional) Run mtu mtu-value

      An MTU is configured for the L2VPN instance.

      The MTU size determines the maximum packet size allowed by a VPWS network. If the MTU exceeds the maximum packet size allowed by a VPWS network or an intermediate node (P), packet fragmentation or even drop will occur, affecting network transmission. The MTU is one of the VPWS negotiation parameters. If the MTUs of the same L2VPN instance on the endpoint PEs are different, the two PEs cannot exchange reachability information or establish a PW. An appropriate MTU must be set for an L2VPN instance based on the MTU of the interface bound to the L2VPN instance. Specifically, the MTU of an L2VPN instance must be smaller than or equal to the MTU of the interface bound to the L2VPN instance.

    4. (Optional) Run ignore-mtu-match

      The current device is configured not to perform the MTU match check.

      By default, an MTU match check is performed on the endpoint PEs.

      If the MTUs of the same L2VPN instance on the two endpoint PEs do not match, the VC cannot go Up. If some devices do not support the MTU match check, run the ignore-mtu-match command to disable this check.

    5. Run ce ce-name [ id ce-id [ range ce-range ] [ default-offset ce-offset ] ]

      A CE is created in the L2VPN instance.

    6. Run connection [ ce-offset ce-offset-id ] interface interface-type interface-number [ tunnel-policy tunnel-policy-name ] [ raw | tagged ] [ secondary ]

      A local BGP VPWS connection is configured.

  3. Run commit

    The configuration is committed.

Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 31899

Downloads: 59

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