mpls l2vc ac-bypass (interface view)

Function

The mpls l2vc ac-bypass command creates a VPWS connection using LDP signaling.

The undo mpls l2vc ac-bypass command deletes an LDP VPWS connection.

By default, no VPWS connection is created.

Format

mpls l2vc { ip-address | pw-template pw-template-name } ^* ac-bypass vc-id [ pw-bypass vc-id ] [ [ control-word | no-control-word ] | [ raw | tagged | ip-interworking | ip-layer2 ] | tunnel-policy policy-name [ endpoint endpoint-address color color-value ] | access-port ] ^*

undo mpls l2vc { ip-address | pw-template pw-template-name } ^* ac-bypass vc-id [ pw-bypass vc-id ] [ [ control-word | no-control-word ] | [ raw | tagged | ip-interworking | ip-layer2 ] | tunnel-policy policy-name [ endpoint endpoint-address color color-value ] | access-port ] ^*

Parameters

Parameter	Description	Value
ip-address	Specifies the IP address of the remote peer on a PW.	The value is usually the LSR ID of the remote peer.
pw-template pw-template-name	Specifies the name of a PW template. You can set attributes for a PW template, including the remote peer, control word, MTU, VCCV capability, and tunnel policy. When configuring an LDP VPWS connection, you can directly apply the PW template rather than specify attributes for the PW in explicit mode. After setting attributes for a PW template, you can make desired changes whenever needed and run the reset pw command for the modified PW template to take effect. You need to define the name and attributes of the PW template in the system view before applying a PW template. If a PW attribute, such as the remote peer, tunnel policy, or control word, is specified in the mpls l2vc command, the same PW attribute configured in the PW template does not take effect.	The value is a string of 1 to 19 case-sensitive characters, spaces not supported. The string can contain spaces if it is enclosed in double quotation marks (").
control-word	Enables the control word function. The control word carries the sequence number and Layer 2 header control information. The control word can be filled in a packet to prevent the packet from being too short.	-
no-control-word	Disables the control word function.	-
raw	Specifies that user packets do not carry P-Tags when being transmitted over a PW. This parameter applies only to Ethernet links.	-
tagged	Specifies that user packets carry P-Tags when being transmitted over a PW. This parameter applies only to Ethernet links.	-
ip-interworking	Enables IP interworking for an LDP PW between Huawei devices. ip-interworking is required for IP interworking between Huawei devices.	-
ip-layer2	Enables IP interworking for an LDP PW between a Huawei device and a non-Huawei device. ip-layer2 is required for IP interworking between a Huawei device and a non-Huawei device.	-
tunnel-policy policy-name	Specifies the name of a tunnel policy. If no tunnel policy is specified, the default tunnel policy is adopted. The default tunnel policy for the VPWS connection uses LSPs and only one LSP is used for load balancing. If a tunnel policy name is specified but the tunnel policy is not configured, the default tunnel policy is adopted. You need to define the name and attributes of the tunnel policy in the system view before applying a tunnel policy.	The value is a string of 1 to 39 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.
endpoint endpoint-address	Specifies the endpoint of an SRv6 TE Policy.	The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X.
color color-value	Specifies the color value of an SRv6 TE Policy.	The value is an integer that ranges from 0 to 4294967295.
access-port	Specifies that only untagged packets can be forwarded. By default, all packets can be forwarded. Access-port applies only to Ethernet main interfaces. The secondary PW must have the same access-port attribute as the primary PW.	-

Views

100ge sub-interface view, 100GE interface view, 10GE sub-interface view, 10GE interface view, 200GE sub-interface view, 25GE sub-interface view, 25GE interface view, 400GE Layer 2 sub-interface view, 400GE sub-interface view, 400GE interface view, 40GE sub-interface view, 40GE interface view, 50GE Layer 2 sub-interface view, 50GE sub-interface view, 50GE interface view, Eth-Trunk Layer 2 sub-interface view, Eth-Trunk sub-interface view, Eth-Trunk interface view, GE Layer 2 sub-interface view, GE optical interface view, GE sub-interface view, GE interface view, GE electrical interface view, XGE sub-interface view, XGE interface view, Layer 2 sub-interface view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
l2vpn	write

Usage Guidelines

Usage Scenario

The VPWS network provides Layer 2 VPN services based on an MPLS network, enabling carriers to provide L2VPN services over different media, such as VLAN, Ethernet, Point-to-Point Protocol (PPP), on a unified MPLS network. The MPLS network can still provide traditional IP services, MPLS L3VPN, traffic engineering, and QoS services.

The VPWS network transparently transmits Layer 2 user data over the MPLS network. For users, the MPLS network is a Layer 2 switched network on which Layer 2 connections can be set up between nodes.

LDP VPWS uses two layers of labels. The inner label uses extended LDP as the signaling protocol to transmit Layer 2 information and VC label information.

To configure a VPWS connection that uses LDP as the signaling protocol on interfaces, run the mpls l2vc command.

The primary PW needs to be created before dynamic VPWS is created.
The secondary PW can be created to protect the primary PW. When the primary PW fails, traffic can be immediately switched to the secondary PW, preventing traffic interruption.
The secondary PWs are used to protect the primary PW. Therefore, configure the primary PW first. Otherwise, the secondary PWs cannot be configured. PWs are deleted in reverse order. Delete the secondary PWs before deleting the primary PW.
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 the standby state, traffic cannot be forwarded, resulting in packet loss. If ignore-standby-state is configured for the secondary PW, the secondary PW will ignore the secondary state indicated by the peer device and be always in the forwarding state, preventing packet loss during a primary/secondary PW switchover.

Prerequisites

MPLS has been enabled in the system view.
MPLS L2VPN has been enabled in the system view.

Configuration Impact

An interface cannot serve as a VPWS AC interface and an L3VPN AC interface at the same time. If an interface is bound to a VPWS, its Layer 3 features such as the IP address and routing protocol will not take effect. If an interface is bound to both a VPWS and an L3VPN, only the VPWS connection is available. After the VPWS connection is deleted, the L3VPN service becomes available.

Precautions

A sub-interface that is bound to a VPWS can be deleted only after it is unbound from the VPWS.
raw, tagged, and access-port in the mpls l2vc command are available only for Ethernet links. In addition, access-port applies only to Ethernet main interfaces.
In a PW redundancy scenario, configure the same parameters for the primary, secondary, and bypass PWs. A parameter inconsistency causes the secondary or bypass PW to fail to take over traffic if the primary PW fails.
Dynamic VCs must be configured on the PEs at both ends of a PW. When configuring a VPWS connection, note the following:
The peer address, destination address of the tunnel, and MPLS LSR ID of the peer PE must be the same. Otherwise, the VPWS connection cannot be set up.
The VC IDs of the PEs at both ends must be the same. Otherwise, the VPWS connection cannot be set up.
If a certain PW attribute is specified in the mpls l2vc command, the corresponding PW attribute in the PW template is invalid.
Control word auto-negotiation is supported only if PEs at both ends of a PW support the control word function. If either of the PEs does not support the control word function, control word auto-negotiation fails.
The PW dynamic BFD detect configuration in the interface view depends on Control Word configuration.

Example

# Configure a VPWS connection on GE 0/1/1.

<HUAWEI> system-view
[~HUAWEI] interface loopback 1
[*HUAWEI-Loopback1] ip address 1.1.1.1 32
[*HUAWEI-Loopback1] quit
[*HUAWEI] mpls lsr-id 1.1.1.1
[*HUAWEI] mpls
[*HUAWEI-mpls] quit
[*HUAWEI] mpls l2vpn
[*HUAWEI-l2vpn] quit
[*HUAWEI] interface GigabitEthernet 0/1/1
[*HUAWEI-GigabitEthernet0/1/1] mpls l2vc 2.2.2.2 100 ac-bypass 3