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

S1720, S2700, S5700, and S6720 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 CE Connection

Creating a CE Connection

Context

The CE connections in Kompella VLL have an impact on network planning. Read the following parameters and perform the necessary operations on the PE devices at both ends of a VC.

Parameter Function Remarks
CE ID

A CE ID uniquely identifies a CE in a VPN.

It is recommended that the CE IDs be numbered in sequence starting from 1.

CE range

The CE range indicates the maximum number of CEs that a local CE can connect.

Based on the expected VPN scale in the future, you can configure a CE range to be larger than what is originally required. This reduces the amount of configuration modifications when CEs are added to the VPN later.

You can only increase the CE range. For example, if the CE range is 10, you can increase it to 20, but cannot reduce it to 5. When the CE range is increased from 10 to 20, the system allocates another label block whose range is 10 instead of releasing the original label block. Services are not interrupted when the CE range changes. The only way to reduce the CE range is to delete the CE connection and create a new CE connection.

CE offset

The CE offset is the CE ID of the other local or remote CE that is connected to this CE.

If the CE offset is not specified when you create a CE connection, pay attention to the following points:
  • For the first connection of a CE, the CE offset uses the value of default-offset by default.
  • For other connections, the CE offset is the CE offset of the earlier connection plus 1. If the CE offset of the earlier connection plus 1 is equal to the current CE ID, set the value to the CE offset of the earlier connection plus 2.
If CE IDs are numbered in an incremental sequence starting from 1 and connections are created for CEs based on their CE IDs, most connections can use the default CE offset. This simplifies the configuration.
Default-offset

The default-offset is the default CE offset. You can set the default-offset to 0 (default value) or 1. If the default-offset is 1, you cannot change it to 0.

  • If the default offset is 0, the CE offset must be smaller than the CE range. If the default offset is 1, the CE offset must be less than or equal to the CE range, and cannot be 0.

  • For a remote connection, the CE offset must be the same as the CE ID of the remote CE; otherwise, the connection cannot be set up. For a local connection between two CEs, the offset of a CE is the CE ID of the other CE.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    mpls l2vpn vpn-name

    The MPLS L2VPN instance view is displayed.

  3. Run:

    ce ce-name id ce-id [ range ce-range ] [ default-offset ce-offset ]

    A CE is created and the MPLS-L2VPN-CE view is displayed.

  4. Run:

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

    An AC interface is bound to the CE, a Kompella VLL connection is created for the CE, and an encapsulation mode is specified for the connection. By default, the Kompella connection uses the tagged encapsulation mode.

    The Kompella VLL supports the following types of AC interfaces: GE interfaces, GE sub-interfaces, XGE interfaces, XGE sub-interfaces, 40GE interfaces, 40GE sub-interfaces, Eth-Trunk interfaces, Eth-Trunk sub-interfaces, and VLANIF interfaces.

    The sub-interfaces can be dotlq sub-interfaces, QinQ sub-interfaces, QinQ mapping sub-interfaces, or QinQ stacking sub-interfaces.

    NOTE:
    • When using the connection command to set the encapsulation mode for a Kompella connection, ensure that the encapsulation mode is consistent with that of the L2VPN instance.
      • If the encapsulation mode of the L2VPN instance is Ethernet, the encapsulation mode of the Kompella connection must be raw.
      • If the encapsulation mode of the L2VPN instance is VLAN, the encapsulation mode of the Kompella connection must be tagged.
    • All Kompella L2VPN instances and VPLS VSI instances of a device share one label block. Therefore, the sum of the ranges of all Kompella L2VPN instances and VPLS VSI instances cannot exceed the size of the label block. If the size exceeds the limit, the system displays a message indicating that the labels cannot be obtained because the number of required labels exceeds the upper limit, and allocation of a site ID to a VSI or creation of a CE fails.

    • To use an XGE interface, a GE interface, a 40GE interface, or an Eth-Trunk interface of the device as the AC interface of the PE, run the undo portswitch command to change a Layer 2 interface to a Layer 3 interface.

    • The management interface cannot be configured as the AC interface if it is connected to a CE.

Translation
Download
Updated: 2019-04-18

Document ID: EDOC1000141944

Views: 84837

Downloads: 518

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