This section describes how to establish a P2P VPWS PW between two PEs for communication.
LDP VPWS is classified into two modes: PWE3-compatible and PWE3.
Perform the following configurations on the endpoint PEs of a PW.
The system view is displayed.
MPLS L2VPN is enabled.
The function to send L2VPN Label Request messages to the remote peer is disabled.
The PW is configured to ignore the recursive tunnel status monitored by MPLS OAM/MPLS-TP OAM.
The function to automatically establish a remote LDP session is enabled.
Return to the system view.
The AC interface view is displayed.
An L2VPN description is configured for the AC interface.
Ethernet interface:
mpls l2vc { ip-address | pw-template template-name } * vc-id [ tunnel-policy policy-name [ endpoint endpoint-address color color-value ] | [ control-word | no-control-word ] | [ raw | tagged | ip-layer2 | ip-interworking ] | access-port | ignore-standby-state ] *
The VC IDs with the same encapsulation type must be unique on a PE.
The raw, tagged, and access-port parameters are available in this command only for Ethernet links. In addition, the access-port parameter can be configured only on Ethernet main interfaces.
If an Ethernet sub-interface is used, run the vlan-type dot1q vlan-id command in the interface view to configure the encapsulation type and VLAN ID of the Ethernet sub-interface.
The default tunnel policy uses LDP tunnels for VPWS PWs. To use a different type of tunnel, set the tunnel-policy policy-name parameter for the PW to reference the corresponding tunnel policy.
The VCCV byte is deleted from the Label Mapping message.
Run this command if LDP VPWS is configured for a device running VRP V800R005 or later and this device communicates with another device running VRP V300R001 or any branch version of VRP V300R001.
An L2VPN service name is specified. The L2VPN service can then be maintained through an NMS based on the specified name.
The configuration is committed.