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).
Creating a VSI and Configuring LDP Signaling

Creating a VSI and Configuring LDP Signaling

Configuring VSI IDs and peer IP addresses are mandatory for LDP VPLS services. VSI IDs are used to identify VSIs in PW signaling negotiation. Perform the following steps on the PEs at both ends of a PW.


  1. Run system-view

    The system view is displayed.

  2. Run vsi vsi-name [ static ]

    A VSI is created, and the VSI view is displayed.

    Two VSIs on the same device cannot be configured with the same name.

  3. (Optional) Run description text

    The VSI description is configured.

    By default, no description is configured for a VSI.

  4. Run encapsulation { ethernet | vlan }

    The encapsulation mode is configured for the VSI.

    Note that:

    • VSIs have two encapsulation modes: Ethernet and VLAN. On the public network, a packet encapsulated in Ethernet mode does not carry a VLAN tag, and a packet encapsulated in VLAN mode carries a VLAN tag.

    • The two ends of a PW must be configured with the same encapsulation mode.

    • The default PW encapsulation mode is VLAN.

  5. (Optional) Run tnl-policy policy-name

    A tunnel policy is applied to the VSI.

    If you do not use tnl-policy policy-name to specify a tunnel policy when configuring the VSI peer in Step 9, run this command to apply a public tunnel policy to the VSI.

    The tunnel policy specified during VSI peer configuration takes precedence over the tunnel policy applied to the VSI view. If tunnel policies are configured in both manners, only the tunnel policy specified during VSI peer configuration takes effect.

    By default, a VSI does not reference any tunnel policy.

  6. (Optional) Run mtu mtu

    The MTU of the VSI is configured for VPLS negotiation.

    If the MTUs of the same VSI on two PEs are different, the two PEs may fail to establish a connection.

    By default, the MTU of a VSI is 1500 bytes.

  7. Run pwsignal ldp

    LDP is configured as the signaling protocol for the VSI, and the VSI LDP view is displayed.

    By default, no signaling mode is configured for a VSI.

  8. (Optional) Run control-word enable

    The control word function is enabled for all PWs in the VSI.

    By default, the control word function is disabled for VSIs.

  9. Run vsi-id vsi-id

    The VSI ID is configured.

    • The VSI IDs of the two ends of a PW must be the same; otherwise, the VSI cannot be created. If the VSI IDs of the two ends of a PW are different, specify negotiation-vc-id vc-id for PW negotiation.

    • VSIs exist only on PEs. A PE can be configured with multiple VSIs, but the ID of each VSI must be unique on a PE.

    By default, no ID is set for a VSI.

  10. (Optional) Run admin-vsi

    The current service VSI is configured as the mVSI.

    By default, no mVSI is configured.

  11. Run peer peer-address [ negotiation-vc-id vc-id ] [ tnl-policy policy-name ] [ secondary ] [ ignore-standby-state ]

    The VSI peer is specified.

    The parameters in the preceding command are described as follows:

    • peer-address specifies the IP address of the peer, usually referring to the LSR ID of the peer.

    • negotiation-vc-id vc-id specifies the PW ID used for parameter negotiation. In most cases, the VSI IDs on both ends of a VSI must be the same. If not, you need to configure the same VSI ID for both ends.

    • If a tunnel policy is configured, you can use tnl-policy policy-name to invoke the tunnel policy when configuring the peer.

    • On the network where PW redundancy is configured, if the primary PW fails, traffic is switched to the secondary PW. If the secondary PW is in Backup state, traffic cannot be forwarded, which results in packet loss. If the ignore-standby-state parameter is configured for the PW on the PE in dual-homed mode, the PW will ignore the secondary state sent from the peer and stays in the forwarding state. This configuration can prevent packet loss during a primary/secondary PW switchover.

    By default, no peer is specified for a VSI.

  12. (Optional) Run peer peer-address [ negotiation-vc-id vc-id ] pw pw-name

    The VSI-LDP-PW view is displayed.

    By default, no peer is specified for a VSI.

  13. (Optional) Run control-word enable

    The control word function is enabled for the PW.

    By default, a PW has the same control word function as the VSI to which the PW belongs.

  14. (Optional) Run undo interface-parameter-type vccv

    The VCCV byte (an interface parameter) is deleted from the Label Mapping message.

    If LDP VPLS is configured for devices running V800R005 or later to communicate with devices running VRPV300R001 or branch versions, configure this command.

    By default, a Mapping packet carries the VCCV byte.

  15. (Optional) Run ignore-stp-loopcheck

    STP loopback detection is disabled for the PW.

    By default, STP loopback detection is enabled for PWs.

  16. (Optional) Run status-code-change flush-mac disable

    The VPLS PW is configured not to clear local MAC addresses when it receives the remote status code of 20.

  17. Run commit

    The configuration is committed.

Follow-up Procedure

If the specified VSI is an mVSI, you must run the track admin-vsi vsi-name command in the service VSI view to bind the service VSI to the mVSI.

Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 32093

Downloads: 59

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