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

CLI-based Configuration Guide - VPN

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

This document describes VPN features on the device and provides configuration procedures and 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).
Configuring a Dynamic PW

Configuring a Dynamic PW

This section describes how to configure a dynamic PW. A dynamic PW uses the extended Label Distribution Protocol (LDP) to transmit Layer 2 information and VC labels.

Pre-configuration Tasks

Before configuring a dynamic PW, complete the following tasks:

  • Configuring an Interior Gateway Protocol (IGP) protocol on PEs and Ps on the Multiprotocol Label Switching (MPLS) backbone network to ensure IP connectivity

  • Configuring basic MPLS functions on the backbone network

  • Setting up a tunnel (GRE tunnel, LSP tunnel, or TE tunnel) between the PEs

    You also need to configure tunnel policies when Pseudo-Wire Emulation Edge to Edge (PWE3) services need to be transmitted over TE tunnels or when PWE3 services need to be load balanced among multiple tunnels to fully use network resources. For details, see step 1 in Configuring and Applying a Tunnel Policy.

  • Setting up a remote LDP session between the PEs

Configuration Procedure

To configure a dynamic PW, perform the following operations on the device. Creating a PW template and setting attributes for the PW template is optional.

Enabling MPLS L2VPN

Context

Before configuring a PW, you must enable MPLS L2VPN.

Perform the following operations on the PEs or UPEs at both ends of a PW.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run mpls l2vpn

    MPLS L2VPN is enabled.

    NOTE:

    If the non-Huawei device does not have the capability of processing L2VPN label requests, you need to run the mpls l2vpn no-request-message command on the Huawei device to enable the two devices to communicate.

(Optional) Creating a PW Template and Setting Attributes for the PW Template

Context

A PW template defines common attributes for PWs, so it can be shared by different PWs. You can run the pw-template command to define some common attributes in a PW template to simplify PW configuration. After creating a PW on an interface, you can apply a PW template to the interface.

On the device, you can bind a PW template to a PW or reset the PW.

You can set the attributes for a PW through commands or a PW template. The attributes include the peer, tunnel policy, and control word. Importing the PW template can simplify the configuration of PWs with similar attributes.

NOTE:
  • Some PW attributes such as the MTU, PW type, and encapsulation type are obtained from the interface connecting the PE to the CE.

  • If you specify a PW attribute through a command, the same PW attribute specified in the PW template does not take effect on the PW to which this PW template is applied.

Perform the following operations on the PEs.

Procedure
  1. Run system-view

    The system view is displayed.

  2. Run pw-template pw-template-name

    A PW template is created and the PW template view is displayed.

  3. Run peer-address ip-address

    A remote IP address is assigned to a PW template.

  4. Run control-word

    The control word function is enabled.

    By default, the control word function is disabled.

    For dynamic single-segment PWs, dynamic multi-segment PWs, and static single-segment PWs, VCCV in control word mode must be enabled on the UPEs. For static and mixed multi-segment PWs, VCCV in control word mode must be enabled on both the UPEs and SPEs.

  5. Run mtu mtu-value

    The MTU in the PW template is specified.

    By default, the MTU in a PW template is 1500.

  6. Run tnl-policy policy-name

    A tunnel policy is configured for the PW template.

    Configure a tunnel policy before you can apply this policy. If no tunnel policy is configured, an LSP tunnel is used and load balancing is not implemented. For details on how to configure a tunnel policy, see step 1 in Configuring and Applying a Tunnel Policy.

After modifying the attributes of a PW template, run the reset pw pw-template command in the user view to make the modification take effect. This may cause PW disconnection and reconnection. If multiple PWs use this template simultaneously, system operation is affected.

Creating a Dynamic PW

Context

To create a dynamic PW, VCs using the same encapsulation type must have different IDs.

Perform the following operations on the PEs.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The AC interface view is displayed.

  3. Create a PW.
    1. To create a primary PW, run:

      mpls l2vc { ip-address | pw-template pw-template-name } * vc-id [ tunnel-policy policy-name  | [ control-word | no-control-word ] | [ raw | tagged ] | mtu mtu-value ] *

    2. (Optional) To create a secondary PW, run:

      mpls l2vc { ip-address | pw-template pw-template-name } * vc-id [ tunnel-policy policy-name  | [ control-word | no-control-word ] | [ raw | tagged ] | mtu mtu-value ] * secondary

    NOTE:
    • When the AC interfaces are Ethernet interfaces, you can specify the parameters raw and tagged.

    • A dynamic PW requires that the IDs of VCs using the same encapsulation type are different. Changing the encapsulation type may cause a VC ID collision.

    • You can create a secondary PW only after a primary PW is created.

    • The combination of the VC ID and VC type must be unique on each node. The VC IDs at both ends of a switching PW can be the same. Primary and secondary PWs must have different VC IDs.

    • Primary and secondary PWs must use the same control word configuration; otherwise, many packets may be lost during service switching.

  4. (Optional) Run mpls l2vpn service-name service-name

    A name is configured for the L2VPN service.

    After a name is configured for the L2VPN service, you can maintain the L2VPN service by clicking the name directly on the NMS GUI.

Verifying the Dynamic PW Configuration

Prerequisites

The configurations of the dynamic PW are complete.

Procedure

  • Run the display pw-template [ pw-template-name ] command to check information about the PW template.
  • Run the display mpls l2vc [ vc-id | interface interface-type interface-number | remote-info [ vc-id | verbose ] | state { down | up } ] command to check the information about virtual circuits in LDP mode.
  • Run the display tunnel-info { tunnel-id tunnel-id | all | statistics [ slots ] } command to check information about tunnels in the system.
  • Run the display tunnel-policy [ tunnel-policy-name ] command to check information about the specified tunnel policy.
Translation
Download
Updated: 2019-08-07

Document ID: EDOC1100033725

Views: 153813

Downloads: 372

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