01-13 PWE3 Configuration

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
1600&AR2200&AR3200&AR3600 Series Enterprise
Routers
CLI-based Configuration Guide - VPN Configuration 13 PWE3 Configuration
13 PWE3 Configuration
About This Chapter
This chapter describes principles, applications, and configurations of the Pseudo-Wire

Emulation Edge to Edge (PWE3).
NOTE
The AR100&AR120&AR150&AR160&AR200 series do not support PWE3.
13.1 Introduction to PWE3

This section describes the PWE3 definition, purpose, and functions.
13.2 Relationship Between PWE3 and L2VPN
PWE3 is a set of point-to-point (P2P) Layer 2 Virtual Private Network (L2VPN) technologies.
Martini L2VPN is only one of the PWE3 technologies. PWE3 uses some Martini L2VPN
techniques, including Label Distribution Protocol (LDP) signaling and encapsulation modes.
In addition, PWE3 extends the Martini L2VPN.
13.3 Principles
This section describes the implementation of PWE3.
13.4 Applications
This section describes applications of the PWE3 feature.
13.5 Configuration Task Summary
When configuring PWE3, you can configure static PW, dynamic PW, TDM PWE3, or PW
switching. If a network spans multiple autonomous systems (ASs), you need to configure
inter-AS PWE3. When a reliability solution is required, you also need to perform other
configurations, such as Bidirectional Forwarding Detection (BFD) for PW and PWE3 fast
reroute (FRR).
13.6 Configuration Notes
This section describes notes about configuring PWE3.
13.7 Default Configuration
This section provides the default PWE3 configuration.
13.8 Configuring PWE3
This section describes how to configure PWE3 functions in details.
13.9 Maintaining PWE3
Issue 02 (2017-10-13) Huawei Proprietary and Confidential 1284

Copyright © Huawei Technologies Co., Ltd.
Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
This section describes how to maintain PWE3, including verifying connectivity of a PW and
locating a fault on a PW.
13.10 Configuration Examples
This section describes PWE3 configuration examples including the networking requirements,
and configuration roadmap, configuration procedure, and configuration files.
13.11 References
This section provides references for the PWE3 feature.
13.1 Introduction to PWE3

This section describes the PWE3 definition, purpose, and functions.
Definition
Pseudo-Wire Emulation Edge to Edge (PWE3) is a point-to-point (P2P) technology that
transmits Layer 2 services on a multiprotocol label switching Layer 2 virtual private network
(MPLS L2VPN). PWE3 simulates essential attributes of a service such as Asynchronous
Transfer Mode (ATM), Frame Relay (FR), Ethernet, low-speed Time Division Multiplexing
(TDM) circuit, Synchronous Optical Network (SONET), or Synchronous Digital Hierarchy
(SDH) on a Packet Switched Network (PSN). PWE3 complies with RFC 4447 (only FEC 128
is supported currently), which is developed based on draft-martini-l2circuit-trans-mpls.
Purpose
The IP network has rapidly developed in recent years because of its flexible upgrade,
scalability, and interoperability. Limited by the transmission mode and services, the traditional
communications network has low flexibility. To make full use of existing or public network
resources during upgrade and expansion of the traditional communications network, PWE3 is
used to integrate the traditional communications network and PSN.
PWE3 often applies to the broadband metro access network (MAN) or mobile bearer network
to transmit various services including Ethernet, ATM, TDM, FR, and PPP. As shown in
Figure 13-1, the headquarters of company A and its branch are located on the traditional
communications network such as ATM or FR. PWE3 is used to establish a PW between PE1
and PE2 so that the headquarters of company A and its branch can communicate over the
MPLS network. PWE3 integrates original access modes with existing IP backbone network to
reduce repetitious network construction, saving operation costs.
Figure 13-1 PWE3 networking

PW
Headquarters Branch of
of enterprise IP/MPLS enterprise A
A Backbone
MPLS Tunnel
AC AC
CE1 PE1 PE2 CE2

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
PWE3 allows various services to be transmitted and supports migration from the mobile
network to Long Term Evolution (LTE). PWE3 protects carrier investments when ATM and
TDM services are migrated to the IP network.
13.2 Relationship Between PWE3 and L2VPN

PWE3 is a set of point-to-point (P2P) Layer 2 Virtual Private Network (L2VPN) technologies.
Martini L2VPN is only one of the PWE3 technologies. PWE3 uses some Martini L2VPN
techniques, including Label Distribution Protocol (LDP) signaling and encapsulation modes.
In addition, PWE3 extends the Martini L2VPN.
PWE3 is extended Martini and has the same signaling process as Martini.
13.2.1 Extensions to the Control Plane
Signaling Extension
PWE3 advertises the PW status using LDP signaling Notification messages. A PW is torn
down only when PW configurations are deleted or the LDP session is interrupted. PWE3
reduces control packets exchanged between PEs and signaling costs. LDP signaling used by
PWE3 is compatible with common LDP and Martini.
Multi-Segment Extension
Multi-segment PWE3 extends networking modes.
l Multi-segment PWE3 has low requirements for the number of LDP sessions supported
by an access device. That is, the costs of LDP sessions on the access device are reduced.
l The access node on a multi-segment PW provides PW aggregation. This allows for more
flexible networking and easily divides a network into access, aggregation, and core
layers.
TDM Interface Extension

PWE3 supports more low-speed Time Division Multiplexing (TDM) interfaces. PWE3
supports packet sequencing, clock extraction, and clock synchronization using the Real-time
Transport Protocol (RTP) on the forwarding plane and the control word.
PWE3 has the following advantages by supporting low-speed TDM interfaces:
l Adds encapsulation types (packets on low-speed TDM interfaces can be encapsulated).

l Integrates the PSTN, TV, and data networks.
l Substitutes the traditional Digital Data Network (DDN) service.
Other Extensions
PWE3 has the following extensions at the control plane:
l Fragmentation negotiation mechanism

l PW connectivity detection, such as VCCV and OAM, which speeds up network
convergence and enhances network reliability

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
13.2.2 Extensions at the Data Plane

l Extensions of the real-time information
l Importing RTP for clock extraction and time synchronization
l Guaranteeing the bandwidth, jitter, and delay of telecom signals
l Re-transmission of disordered packets
13.3 Principles
This section describes the implementation of PWE3.
13.3.1 Basic Principles
PWE3 Architecture
PWE3 uses the Label Distribution Protocol (LDP) as the signaling protocol, and transmits
Layer 2 packets of Customer Edges (CEs) through tunnels such as MPLS LSPs, Generic
Routing Encapsulation (GRE) tunnels, or multiprotocol label switching traffic engineering
(MPLS TE) tunnels. As shown in Figure 13-2, PWE3 uses the following entities:
l Attachment circuit (AC)

l Pseudo wire (PW)
l Forwarder
l Tunnels
l PW signaling protocol
Figure 13-2 PWE3 architecture
VPN1 VPN1
Site1 CE1 CE3 Site2
Forwarder Forwarder
AC
AC
PE1 P PE2
IP/MPLS
CE2 Backbone CE4 VPN2
VPN2
Site1 Site2
AC
PW
PW Signal
Tunnel
The following uses the flow direction of VPN1 packets from CE1 to CE3 as an example to
show the basic direction of data flows.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
l CE1 sends Layer 2 packets to PE1 through an AC.

l After PE1 receives the packets, the forwarder selects a PW to forward the packets.
l PE1 generates double MPLS labels (private and public network labels) based on the
forwarding entry of the PW. The private network label is used to identify the PW, and the
public network label identifies the tunnel to PE2 on the public network.
l After Layer 2 packets arrive at PE2 through the tunnel on the public network, the
Penultimate Hop Popping (PHP) device (a P device) pops out the public network label,
and PE2 pops out the private network label.
l The forwarder of PE2 selects an AC to forward the Layer 2 packets to CE3.
PWE3 Classification
PWs are classified into the following types:
l Static PW and dynamic PW in terms of implementation

Martini VLL uses LDP to establish dynamic PWs. PWE3 also allows static PWs
established using the manually configured PW information.
l Single-segment PW and multi-segment PW in terms of networking modes
– Single-segment PW: Only one PW is set up between two PEs, and PW label
switching is not required. For example, PW1 in Figure 13-3 is a single-segment
PW.
– Multi-segment PW: Multiple segments of the PW exist between two PEs. The
forwarding mechanism of PEs on the multi-segment PW is the same as that of the
single-segment PW. The difference is that PW labels need to be switched on the
Switching PE (SPE). For example, PW2 in Figure 13-3 is a multi-segment PW.
NOTE
A multi-segment PW is required if a signaling connection or directly connected tunnel cannot be

established between two PEs. With the multi-segment PW, PWE3 makes networking flexible.
The two classification modes are independent of each other. PWE3 supports the
mixed PW, that is, a static PW at one end and a dynamic PW at the other end.
Figure 13-3 Single-segment PW and multi-segment PW

PW1
PE1 P PE2
CE1 CE2
IP/MPLS
Backbone
SPE
PW2 PW2
Segment1 Segment2

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Setup, Maintenance, and Teardown of a Dynamic PW

A dynamic PW uses LDP and encapsulates VC information in the type-length-value (TLV) of
LDP packets. PEs need to establish an LDP session, and PW labels are allocated in
Downstream Unsolicited (DU) mode and retained in liberal label retention mode.
NOTE
If a P exists between PEs, a remote LDP session is established between the PEs. If PEs are directly
connected, a common LDP session is established.
After PWE3 configuration is complete on two PEs of the PW and an LDP session is
established between PE1 and PE2, PE1 and PE2 start to establish a dynamic PW, as shown in
Figure 13-4.
1. PE1 sends a Request message and a Mapping message that contain the local private
network label and relevant attributes to PE2.
2. After receiving the Request message from PE1, PE2 sends a Mapping message to PE1.
3. After receiving the Mapping message, PE2 checks whether the same PW parameters as
those in the Mapping message are configured locally. If the configured PW parameters
such as the VC ID, VC type, MTU, and control word status are the same, PE2 sets the
local PW in Up state.
4. After receiving the Mapping message from PE2, PE1 checks whether the locally
configured PW parameters are the same as those in the Mapping message. If they are the
same, PE1 sets the local PW in Up state. A dynamic PW is set up between PE1 and PE2.
5. After the PW is set up, PE1 and PE2 send Notification messages to report their status.
Figure 13-4 Setup and maintenance of a single-segment PW

Loopback1 Loopback1
1.1.1.1/32 2.2.2.2/32
PE1 PE2
mpls l2vc 2.2.2.2 101 Reque

st
Mappin mpls l2vc 1.1.1.1 101

g
Parameter match, VC up
ing
Mapp
Parameter match, VC up
Notification
AC/Tunnel state changed AC/Tunnel state changed
When the AC or the tunnel is Down, Martini and PWE3 take different measures:
l Martini sends a Withdraw message to the peer, requesting to tear down the PW. After the
AC or tunnel becomes Up, two PEs need to perform negotiation again to establish a PW.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
l PWE3 sends a Notification message to notify the peer that packets cannot be forwarded.
The PW is not torn down. When the AC or tunnel becomes Up, PWE3 sends a
Notification message to notify the peer that packets can be forwarded.
Both PEs tear down the PW only when the PW configuration is deleted or the signaling
protocol is interrupted, for example, the public network or PW is Down. On an unstable
network, Notification messages can be sent to prevent repeated PW setup and deletion due to
link flapping.
Figure 13-5 Process of tearing down a single-segment PW

Loopback1 Loopback1
1.1.1.1/32 2.2.2.2/32
PE1 PE2
mpls l2vc 2.2.2.2 101 mpls l2vc 1.1.1.1 101

VC Deletion
Withdraw
Release
Release
VC Deletion
Figure 13-5 shows the PW teardown process.
1. After the PW configuration on PE1 is deleted, PE1 deletes the local VC label and sends
Withdraw and Release messages to PE2.
NOTE
A Withdraw message is used to inform the peer to withdraw labels. A Release message is used to
respond to a Withdraw message and request the peer to send a Withdraw message to withdraw labels.
To tear down a PW more quickly, PE1 sends a Withdraw message and a Release message consecutively.
2. After receiving Withdraw and Release messages from PE1, PE2 delete the remote VC
label and sends a Release message to PE1.
3. After PE1 receives a Release message from PE2, the PW between PE1 and PE2 is torn
down.
As shown in Figure 13-6, one or more SPEs are deployed between two PEs for a multi-
segment PW. PE1 and PE2 establish connections with the SPE and the SPE combines two
segments of the PW.
During signaling negotiation, the SPE forwards parameters in the Mapping message from
UPE1 to UPE2. Similarly, the SPE forwards parameters in the Mapping message from UPE2
to UPE1. If parameters on UPE1 and UPE2 are the same, the PW status becomes Up. Similar
to the Mapping message, Release, Withdraw, and Notification messages are transmitted
segment by segment.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Figure 13-6 Signaling exchange on a multi-segment PW
Loopback1 Loopback1 Loopback1

1.1.1.1/32 2.2.2.2/32 3.3.3.3/32
UPE1 SPE UPE2
mpls l2vc 2.2.2.2 100 Request
Mapping
mpls l2vc 2.2.2.2 100
Request
Mapping
Switch PW
Request
Request
Mapping parameters match
parameters match Mapping VC up
VC up
13.3.2 Control Word

The Control Word is negotiated at the control plane, and is used for packet sequence
detection, packet fragmentation, and packet reassembly at the forwarding plane. In the PWE3
protocols, ATM Adaptation Layer Type 5 (AAL5) requires support for the CW. The
negotiation of the CW at the control plane is simple. If the CW is supported after the
negotiation, the negotiation result needs to be delivered to the forwarding module, which
detects the packet sequence and reassembles the packet.
The CW is a 4-byte encapsulated packet header, as shown in Figure 13-7. It is used to
transmit packets on an MPLS packet switched network (PSN).
Figure 13-7 Position of the CW in a packet

0 7 15 23 31
Tunnel Label(LDP or RSVP) EXP 0 TTL
VC Label(VC) EXP 1 TTL(Set to 2)
Rsvd Flags 0 0 Length Sequence Number
Layer-2 PDU
Tunnel Label /VC Label

Control Word
Layer-2 Protocol Data Unit

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
The CW has the following functions:

l Carries the sequence number for forwarding packets.
If the forwarding plane supports the CW, a 32-bit CW is added before the data packet to
indicate the packet sequence. When load balancing is supported, the packets may be out
of sequence. The CW can be used to number the packets so that the peer can reassemble
the packets.
l Pads the packets to prevent the packets from being too short.
For example, if two PEs connect to each other over an Ethernet and CEs connect to PEs
over PPP links, PPP negotiation cannot succeed because the size of PPP control packets
cannot meet the minimum MTU requirements of an Ethernet. To prevent this problem,
you can pad the CW as padding bits to the PPP control packet.
l Carries the control information of the Layer 2 frame header.
In certain cases, the frame does not need to be transmitted completely in the L2VPN
packets on the network. The frame header is stripped at the ingress and added at the
egress. This method, however, cannot be used if the information in the frame header
needs to be carried. You can use the CW to solve this problem. The CW can carry the
negotiated information between the ingress PE and the egress PE.
At the control plane, the negotiation succeeds only when both ends or neither end supports the
CW. At the forwarding plane, the negotiation result at the control plane determines whether
the CW is added to a packet.
13.3.3 VCCV
As MPLS is widely deployed and the MPLS network transmits various types of traffic, the
ISP must provide the capability to monitor the label switched path (LSP) status and locate
MPLS forwarding faults. Virtual Circuit Connectivity Verification (VCCV) provides the
service capability.
VCCV is an end-to-end PW fault detection and diagnosis mechanism, and tests and checks
connectivity of the PW forwarding path. VCCV provides the control channel through which
connectivity verification (CV) messages are sent between the PW ingress and egress.
Two VCCV modes are available: VCCV ping and VCCV tracert.
l VCCV ping, as an extension of LSP ping, is used to manually test connectivity of a
virtual circuit (VC). VCCV ping sends MPLS Echo Request messages through a PW to
determine connectivity of the PW. VCCV defines a series of messages transmitted
between PEs to verify connectivity of PWs. VCCV ping can be performed in control
word channel mode or label alert channel mode:
– Control word channel: End-to-end detection between UPEs is supported.
– Label alert channel: Segment by segment detection between the UPE and SPE and
end-to-end detection are supported.
l VCCV tracert, as an extension of LSP tracert, is used to locate the faulty node on a PW.
VCCV tracert sends MPLS Echo Request messages through a PW to collect information
about nodes on the PW. VCCV tracert is classified into PWE3 single-segment tracert and
PWE3 multi-segment tracert.
To ensure that both VCCV packets and PW packets are transmitted along the same path,
VCCV packets must be encapsulated in the same way and transmitted in the same channel as
PW packets.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
13.3.4 PWE3 FRR

Definition
As L2VPN is widely used, networks especially L2VPNs that carry real-time services such as
VoIP and IPTV require high reliability.
Pseudo-Wire Emulation Edge to Edge Fast Reroute (PWE3 FRR) is a feasible solution to
improve L2VPN reliability. It uses Operations, Administration and Maintenance (OAM) and
Bidirectional Forwarding Detection (BFD) to detect and report faults on the L2VPN and fast
switch traffic, then improving L2VPN reliability.
PWE3 FRR Implementation

PWE3 FRR is implemented as follows:
l The BFD mechanism is used to fast detect a fault on a PW. As a unified detection
mechanism used on the entire network, BFD can detect a fault in milliseconds. As the
BFD cost is low, if a great number of PWs exist, BFD for PWs greatly reduces the
system cost.
l The OAM mapping between a PW and an AC can be created. When a PW or a PE is
faulty, a CE can take measures in a timely manner. For example, the CE can rapidly
switch traffic to the secondary path.
l OAM messages are transparently transmitted on a PW so that this mechanism
implements end-to-end fault detection on PWs and provides PW protection.
In this way, OAM integrates with BFD to implement PWE3 FRR.
Switchover Mechanism
A fault on the PWE3 FRR network triggers traffic switchover. The device where traffic is
switched also reports the fault and terminates fault notification.
The node that performs fault switchover and terminates fault notification varies with the
networking:
l In a networking with asymmetrically connected CEs as shown in Figure 13-8, PE1 and
CE2 terminate fault propagation. When PE1 detects a fault, it switches traffic and does
not send a fault notification to CE1. CE2 receives the fault notification from PE2 and
switches traffic to the secondary link.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Figure 13-8 Networking with asymmetrically connected CEs
P1 PE2
PE1
AC2
IP/MPLS
Backbone CE2
CE1
AC1
AC3
PE3
Site1 P2 Site2
PW
PW secondary
l As shown in Figure 13-9, two tunnels back up each other on a backbone network. PE1
and PE2 terminate fault notification, and only need to switch the tunnel.
l Figure 13-9 Tunnel backup on a backbone network
P1
PE1
IP/MPLS PE2
Backbone CE2
CE1
AC1 AC2
Site1 P2 PE3 Site2
Tunnel 1
Tunnel 2
When a CE detects a fault on the primary link, the CE checks whether the secondary link is
available. If so, the CE switches traffic to the secondary link. If not, the CE sends an alarm
about the service fault.
In a networking with asymmetrically connected CEs as shown in Figure 13-8, when PE1
detects a fault on the primary PW, it processes the fault as follows:
l If PE1 also detects a local AC fault, it reports a service fault. In this case, the fault cannot
be rectified.
l If PE1 does not detect a local AC fault or a secondary PW fault, it switches traffic to the
secondary PW.
l If PE1 does not detect a local AC fault but detects a secondary PW fault, it reports a
service fault, but does not switch traffic.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
PW Revertive Switchover Policy

In a networking with asymmetrically connected CEs as shown in Figure 13-8, when PE1 is
notified of fault recovery on the primary PW, PE1 works based on the configured revertive
switchover policy.
The PW revertive switchover policies are as follows:
l None revertive switchover: Traffic is not switched to the primary PW.
l Immediate revertive switchover: Traffic is immediately switched to the primary PW.
l Delayed revertive switchover: Traffic is switched to the primary PW after a delay.
After the switchover, PE1 immediately notifies PE3 on the secondary PW of the fault so that
CE2 fast switches the AC through association. In addition, the PE notifies the peer PE on the
secondary PW of fault recovery immediately or after a delay, preventing packet loss due to
transmission delay between PEs.
13.3.5 Inter-AS Technology

The MPLS VPN solution is widely used, serving an increasing number of users in a large
number of applications. As more sites are developed in an enterprise, sites in different
geographical locations often connect to different ISP networks. Consider, for example, the
inter-AS issue facing operators who manage different metropolitan area networks (MANs) or
backbone networks that span different autonomous systems (AS).
Generally, an MPLS VPN architecture runs within an AS in which VPN routing information
is flooded on demand. The VPN routing information within the AS cannot be flooded to the
AS of other service providers (SPs). To implement exchange of VPN routing information
between different ASs, the inter-AS MPLS VPN model is introduced. The inter-AS MPLS
VPN model is an extension of the existing protocol and MPLS VPN framework. This model
allows route prefixes and labels to be advertised over the links between different carrier
networks.
PWE3 supports inter-AS Option A.
Inter-AS Option A
With Option A, ASBRs of two ASs are directly connected and function as PEs in their
respective ASs. The two ASBRs regard each other as a CE.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Figure 13-10 Inter-AS Option A networking
CE-1
IP/MPLS IP/MPLS
Backbone Backbone
AS 100 AS 200
PE-1 PW ASBR1
ASBR2
PW AC
PE-2
LSP1
CE-2
In Figure 13-10, ASBR1 in AS 100 regards ASBR2 in AS 200 as a CE. Similarly, ASBR2
regards ASBR1 a CE.
Option A has the following advantages:
Inter-AS Option A is easy to implement. The two PEs used as ASBRs perform IP forwarding
but not MPLS forwarding. In addition, the two PEs do not require special configurations.
Option A has low scalability.
l The PE needs to manage all L2VPN information, which occupies many resources.
l As the ASBR works as the PE in an AS, each PW requires an AC interface, which can be
a sub-interface, physical interface, or bundled logical interface.
l If a VPN spans multiple ASs, intermediate ASs must support VPN services. As a result,
the configuration workload is heavy and the intermediate ASs are affected.
Therefore, inter-AS Option A is applicable only when there are a small number of inter-AS
L2VPNs.
13.4 Applications
This section describes applications of the PWE3 feature.
13.4.1 PWE3 Carrying Enterprise Leased Line Services on a MAN
Usage Scenario
Figure 13-11 shows a typical single-segment PWE3 networking. A carrier establishes a MAN
to provide PWE3 services. A customer has two branches far from each other. If the customer
use leased lines to connect the branches, it will result in high costs. The customer can request
the carrier to establish a PWE3 connection between PE1 in branch A and PE2 in branch B.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
PWE3 ensures stable Layer 2 communication between branches A and B, facilitates

networking, and allows branches A and B to communicate with each other like on a LAN.
Figure 13-11 PWE3 carrying enterprise leased line services on a MAN
PWE3 Deployment
1. IP addresses and IGPs are configured on the carrier MPLS backbone network so that PEs
can communicate.
2. MPLS is enabled on the carrier MPLS backbone network, and a TE tunnel is configured
between PE1 and PE2. Usually, two TE tunnels are configured to provide tunnel
protection.
3. MPLS L2VPN is enabled on PE1 and PE2 and a remote MPLS LDP session is set up
between them.
4. PWE3 is configured on AC interfaces of PE1 and PE2 so that PE1 and PE2 can
communicate over an MPLS L2VC.
13.5 Configuration Task Summary

When configuring PWE3, you can configure static PW, dynamic PW, TDM PWE3, or PW
switching. If a network spans multiple autonomous systems (ASs), you need to configure
inter-AS PWE3. When a reliability solution is required, you also need to perform other
configurations, such as Bidirectional Forwarding Detection (BFD) for PW and PWE3 fast
reroute (FRR).

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Table 13-1 Summary of PWE3 configuration tasks

Scenario Description Task
Configure PWE3 When configuring PWE3, you can l 13.8.1 Configuring a Static
configure static PW, dynamic PW, PW
TDM PWE3, or PW switching. l 13.8.2 Configuring a
The application scenario of each is Dynamic PW
as follows:
l 13.8.3 Configuring PW
l Configuring static PW: does Switching
not require signaling
negotiation or exchange of l 13.8.4 Configuring TDM
control packets; therefore, it PWE3
consumes few resources and is
easy to configure. However, it
requires manual configuration,
which makes network
maintenance and expansion
difficult. Static PW applies to
small-scale MPLS networks
with simple topologies.
l Configuring dynamic PW:
applies to large-scale
enterprises or local area
networks (LANs) of small-
scale carriers.
l Configuring PW switching:
PW labels need to be
exchanged during multi-
segment PW forwarding.
PW switching applies to the
following scenarios:
– Two PEs are not in the
same AS, and no signaling
connection or tunnel can be
set up between the two PEs.
– The signaling of two PEs
differs from each other.
– If the access device
supports MPLS, but is
incapable of setting up a
large number of LDP
sessions, you can use User
Facing Provider Edge
(UFPE) as the UPE. In
addition, you can use the
SPE as the switching node
of LDP sessions, which is
similar to a signaling
reflector.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Scenario Description Task
l Configuring TDM PWE3:

applies when TDM services
are transmitted using PWE3.
TDM PWE3 encapsulates
TDM service data and
transparently transmits the
encapsulated data through PWs
to implement TDM service
transmission.
Configure inter- Configure inter-AS PWE3 if the 13.8.7 Configuring Inter-AS

AS PWE3 PWE3 backbone network spans PWE3
multiple ASs.
Configure PWE3 When you transmit key services l 13.8.5 Configuring Static
reliability over the PWE3 network, the BFD for PWs
following reliability solutions can l 13.8.6 Configuring PWE3
be used: FRR
l Configuring BFD for PW:
BFD for PW can rapidly detect
a fault on the PW and notify
the forwarding plane of the
fault, ensuring fast traffic
switchover.
l Configuring PWE3 FRR:
PWE3 FRR ensures link-layer
reliability for the PWE3
network.
Configure and This task is required when PWE3 13.8.8 Configuring and
apply a tunnel services need to be transmitted Applying a Tunnel Policy
policy over TE tunnels or when multiple
tunnels need to perform load
balancing to fully use network
resources.
13.6 Configuration Notes

This section describes notes about configuring PWE3.
Involved Network Elements

Other network elements are not required.
License Support
The L2VPN function is used with a license. By default, the PWE3 function cannot be used on
the device. To use the L2VPN function, apply for and purchase the following license from the
Huawei local office:

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
l AR1200 series: AR1200 Value-Added Data Package

Version Support
Table 13-2 Products and minimum version supporting PWE3

Product Minimum Version Required
Router V200R005C10
NOTE
The AR100&AR120&AR150&AR160&AR200
series do not support PWE3.
Feature Dependencies and Limitations

Limitations on PWE3
l PWE3 cannot be configured on the VLANIF 1.
l The VLANIF interface configured with PWE3 can only correspond to one member
interface.This limitation does not apply to AR1220E, AR1220EV, and AR1220EVW.
13.7 Default Configuration

This section provides the default PWE3 configuration.
Table 13-3 lists the default PWE3 configuration.
Table 13-3 Default PWE3 configuration

Parameter Default Setting
MPLS L2VPN Disabled
MTU 1500
VCCV Enabled
Control word Disabled
Jitter buffer depth 8 ms
Number of TDM frames encapsulated in 8

CESoPSN or SAToP packets
13.8 Configuring PWE3

This section describes how to configure PWE3 functions in details.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
13.8.1 Configuring a Static PW

A static PW does not use signaling protocols to transmit L2VPN packets. Packets are
transmitted over the tunnel between PEs.
Pre-configuration Tasks
Before configuring a static PW, complete the following tasks:
l Configuring an IGP protocol on PEs and Ps on the MPLS backbone network to ensure IP
connectivity
l Enabling MPLS on PEs and Ps
l Setting up a tunnel (GRE tunnel, LSP tunnel, or TE tunnel) between the PEs
You also need to configure tunnel policies when 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 13.8.8 Configuring and
Applying a Tunnel Policy.
Configuration Process
To configure a static PW, perform the following operations on the device. Creating a PW
template and setting attributes for the PW template is optional.
13.8.1.1 Enabling MPLS L2VPN
Context
Before configuring a static PW, you must enable MPLS L2VPN.
Perform the following operations on the PEs at both ends of a PW.
Procedure
Step 1 Run:
system-view
The system view is displayed.
Step 2 Run:
mpls l2vpn
MPLS L2VPN is enabled.
By default, MPLS L2VPN is disabled.
----End

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
13.8.1.2 (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
l Some PW attributes such as the MTU, PW type, and encapsulation type are obtained from the
interface connecting the PE to the CE.
l 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

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

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
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 13.8.8 Configuring and Applying a
Tunnel Policy.
NOTICE
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.
13.8.1.3 Creating a Static PW
Context
When creating a static PW, specify the VC label.
Perform the following operations on the PEs at both ends of a PW.
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface interface-type interface-number
The AC interface view is displayed.

Step 3 Create a static PW.
1. To create a primary PW, run:
mpls static-l2vc { { destination ip-address | pw-template pw-template-name vc-
id } * | destination ip-address [ vc-id ] } transmit-vpn-label transmit-label-
value receive-vpn-label receive-label-value [ tunnel-policy tnl-policy-name |
[ control-word | no-control-word ] | [ raw | tagged ] ] *
2. (Optional) To create a secondary PW, run:

mpls static-l2vc { { destination ip-address | pw-template pw-template-name vc-
id } * | destination ip-address [ vc-id ] } transmit-vpn-label transmit-label-
value receive-vpn-label receive-label-value [ tunnel-policy tnl-policy-name |
[ control-word | no-control-word ] | [ raw | tagged ] ] * secondary
NOTE
l When the AC interfaces are Ethernet interfaces, you can specify the parameters raw and tagged.
l You can create a secondary PW only after a primary PW is created.
l 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.
l Primary and secondary PWs must use the same control word; otherwise, many packets may be lost during
service switching.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Step 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.
----End
13.8.1.4 Checking the Configuration
Prerequisites
The configurations of the static PW are complete.
Procedure
l (Optional) Run the display pw-template [ pw-template-name ] command to check
information about the PW template.
l Run the display mpls static-l2vc [ vc-id | interface interface-type interface-number |
state { down | up } ] command to check the information about static VCs.
l Run the display tunnel-info { tunnel-id tunnel-id | all | statistics [ slots ] } command to
check information about tunnels in the system.
l Run the display tunnel-policy [ tunnel-policy-name ] command to check information
about the specified tunnel policy.
----End
13.8.2 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.
Before configuring a dynamic PW, complete the following tasks:
l Configuring an Interior Gateway Protocol (IGP) protocol on PEs and Ps on the
Multiprotocol Label Switching (MPLS) backbone network to ensure IP connectivity
l Configuring basic MPLS functions on the backbone network
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 13.8.8 Configuring and Applying a Tunnel Policy.
l Setting up a remote LDP session between the PEs
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.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
13.8.2.1 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
Step 1 Run:
system-view

Step 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.
----End

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.
NOTE
l 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.
Procedure
1. Run:
system-view

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers

2. Run:

3. Run:
A remote IP address is assigned to a PW template.

4. Run:
control-word

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

6. Run:
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 13.8.8 Configuring and Applying a
Tunnel Policy.
NOTICE
13.8.2.3 Creating a Dynamic PW
Context
To create a dynamic PW, VCs using the same encapsulation type must have different IDs.
Procedure
Step 1 Run:
system-view

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers

Step 2 Run:

Step 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:

policy policy-name | [ control-word | no-control-word ] | [ raw | tagged ] |
mtu mtu-value ] * secondary
NOTE
l When the AC interfaces are Ethernet interfaces, you can specify the parameters raw and tagged.
l 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.
l You can create a secondary PW only after a primary PW is created.
l 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.
l Primary and secondary PWs must use the same control word configuration; otherwise, many packets may
be lost during service switching.

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.
----End
Prerequisites
The configurations of the dynamic PW are complete.
Procedure
l Run the display pw-template [ pw-template-name ] command to check information
about the PW template.
l 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.
----End

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
13.8.3 Configuring PW Switching

You can configure a multi-segment PW to exchange PW labels.
Context
To forward packets through a multi-segment PW, configure PW switching so that PW labels
can be exchanged. PW switching must be configured on the Superstratum PE (SPE) where a
large number of MPLS LDP sessions can be established.
In the following cases, PW switching is required:
l Two PEs are in different ASs, and no signaling connection or tunnel can be set up
between the two PEs.
l Two PEs use different signaling.
l If the access device can run MPLS but does not support a large number of LDP sessions,
the User Facing Provider Edge (UFPE) can be used as a UPE and the SPE as a node for
switching LDP sessions. The SPE is similar to a signaling reflector.
PW switching supports three modes: static mode, dynamic mode, and mixed mode:
l When static PWs are used between the SPE and two connected PEs, configure static PW
switching.
l When dynamic PWs are used between the SPE and two connected PEs, configure
dynamic PW switching.
l When a static PW and a dynamic PW are used between the SPE and two connected PEs,
configure mixed PW switching.
Before configuring multi-segment PW switching, complete the following tasks:
l Enabling MPLS L2VPN on PEs
l Configuring a Static PW on UPEs if PW switching is performed between two static
PWs
l Configuring a Dynamic PW on UPEs if PW switching is performed between two
dynamic PWs
Procedure
l Configuring static PW switching
Perform the following operations on the SPE.
a. Run:
system-view

b. Run:

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
mpls switch-l2vc ip-address vc-id trans trans-label recv received-label

[ tunnel-policy policy-name ] between ip-address vc-id trans trans-label
recv received-label [ tunnel-policy policy-name ] encapsulation
encapsulation-type [ control-word [ cc { alert | cw } * cv lsp-ping ] |
[ no-control-word ] [ cc alert cv lsp-ping ] ] [ control-word-
transparent ]
Static PW switching is configured.
To configure static PW switching, you must configure PW labels on each SPE.
A static multi-segment PW is established as follows:
n On the UPE, when the AC status is Up and the PSN tunnel exists, the PW
status is Up.
n On the SPE, as long as the PSN tunnels exist on both sides, the PW is in Up
state even if the SPE and UPE use different PW encapsulation types.
It is recommended that you set the same PW encapsulation type by specifying the
encapsulation-type parameter on the SPE and UPE to facilitate management.
l Configuring dynamic PW switching
a. Run:
system-view

b. Run:
mpls switch-l2vc ip-address vc-id [ tunnel-policy policy-name ] between
ip-address vc-id [ tunnel-policy policy-name ] encapsulation
encapsulation-type [ control-word-transparent ]
Dynamic PW switching is configured.
Dynamic PW switching is easy to configure. Two neighboring endpoints (UPE or

SPE) will send remote labels to the SPE through signaling. The two UPEs will send
control word and VCCV to the SPE through signaling.
The PW encapsulation type (specified by the encapsulation-type parameter) on the

SPE must be the same as that on the UPE. Otherwise, the PW cannot go Up.
l Configuring mixed PW switching
NOTE
When you configure mixed PW switching, ip-address vc-id before between specifies the VC ID of
a dynamic PW and ip-address vc-id after between specifies the VC ID of a static PW. The two
values cannot be interchanged.
a. Run:
system-view

b. Run:
ip-address vc-id trans trans-label recv received-label [ tunnel-policy
policy-name ] encapsulation encapsulation-type [ mtu mtu-value ]
[ control-word [ cc { alert | cw } * cv lsp-ping ] | [ no-control-word ]
[ cc alert cv lsp-ping ] ] [ control-word-transparent ]

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Mixed PW switching is configured.

To configure mixed PW switching, configure a PW label for the static PW. The PW
encapsulation type (specified by the encapsulation-type parameter) on the SPE must
be the same as that on the UPE connected to a dynamic PW.
To configure mixed PW switching, the following MTUs must be the same:
n Local MTU of the dynamic PW
n Peer MTU of the dynamic PW
n Local MTU of the static PW
n Peer MTU of the static PW
NOTE
In mixed PW switching, the MTUs of the interfaces on the two ends must be the same and
cannot be greater than 1500 bytes.
----End
Checking the Configuration

l Run the display mpls switch-l2vc [ ip-address vc-id encapsulation encapsulation-type |
state { down | up } ] command on the SPE to view information about PW switching.
13.8.4 Configuring TDM PWE3

You can configure TDM PWE3 to encapsulate TDM service data and transparently transmit
the data through PWs to implement TDM service transmission through PWE3.
Before configuring TDM PWE3, complete the following tasks:
l Configuring an IGP protocol on the Ps and PEs on the MPLS backbone network to
implement IP connectivity
l Configuring basic MPLS capabilities on the backbone network
l Installing a 8SA, 6E&M, 8E1T1-M, or 8E1T1-F interface card on the device and
ensuring that it is registered successfully

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
NOTE
Only the AR2204XE, AR2220, AR2240 (using SRU40, SRU60, SRU80, SRU200, or SRU200E, or
SRU400), AR3200 (using SRU40, SRU60, SRU80, SRU200, or SRU200E, or SRU400), and AR3600
(using SRUX5) series routers support this function.
To configure TDM PWE3, you need to perform the following configurations, among which
creating a PW template and setting attributes for the PW template is optional.
13.8.4.1 Configuring an AC Interface to Transparently Transmit TDM Cells
Context
You can configure an AC interface to transparently transmit TDM cells, so that after receiving
TDM packets, the AC interface encapsulates the packets and transmits the packets through a
PW.
Procedure
Step 1 Use either of the following methods to configure AC interface parameters based on the
interface card type:
l 8SA interface card: Configure interface parameters such as a working mode for serial
interfaces. Ensure that the parameters are the same as those of a CE's interface connected
to the AC interface.
NOTE
For the detailed configuration of a serial interface, see Synchronous Serial Interface Configuration in
Huawei AR100&AR120&AR150&AR160&AR200&AR1200&AR1600&AR2200&AR3200&AR3600
Series Enterprise Routers Configuration Guide - Interface Management.
l 6E&M interface card: Configure interface parameters for E&M interfaces. Ensure that
the parameters are the same as those of a CE's interface connected to the AC interface.
NOTE
For the detailed configuration of an E&M interface, see Configuring Line Attributes for an E&M
Interface in Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR1600&AR2200&AR3200&AR3600 Series
Enterprise Routers Configuration Guide - Interface Management.
l 8E1T1-M interface card: Configure interface parameters such as a working mode for
CE1/PRI interfaces. Ensure that the parameters are the same as those of a CE's interface
connected to the AC interface. To ensure that CEs exchange data successfully, the AC
interfaces must work in clock synchronization state.
NOTE
For the detailed configuration of a CE1/PRI interface, see Configuring CE1/PRI Interface in Huawei
l 8E1T1-F interface card: Configure interface parameters such as a working mode for E1-
F interfaces. Ensure that the parameters are the same as those of a CE's interface
connected to the AC interface. To ensure that CEs exchange data successfully, the AC
interfaces must work in clock synchronization state.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
NOTE
For the detailed configuration of an E1-F interface, see Configuring E1-F Interface in Huawei
Step 2 Configure the AC interface to transparently transmit TDM cells.

1. Run:
system-view

2. Run:
interface serial interface-number
The serial interface view is displayed.

3. Run:
link-protocol tdm
The link layer protocol used for packet encapsulation on the serial interface is set to
TDM.
----End

Template
Context
A PW template defines common attributes for PWs, so it can be shared by different PWs. The
PW template simplifies PW configuration. You can use the PW template to create a PW on an
interface.
On the device, the PW can be bound to a PW template and can be reset.
NOTE
l If you specify a PW attribute through commands, the same PW attribute specified in the PW
template does not function on the PW to which this PW template is applied.
Perform the following steps on the PE devices.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Step 3 Run:
The remote device IP address of the PW is specified.

Step 4 Run:
control-word

To enable VCCV in control word mode, enable the control word function only on the UPE for
dynamic single-hop PWs, dynamic multi-hop PWs, and static single-hop PWs; enable the
control word function on both the UPE and SPE for static multi-hop PWs and mixed dynamic
multi-hop PWs.
Step 5 Run:
mtu mtu-value

Step 6 Run:
jitter-buffer depth depth
The jitter buffer depth is configured.

By default, the jitter buffer depth is 8 ms.
The jitter buffer is used to reduce jitter at the network side. A larger jitter buffer depth
indicates a stronger anti-jitter capability. However, when a long transmission delay is
introduced when data flows are reconstructed, improper jitter buffer depth degrades
transmission quality.
Step 7 Run:
tdm-encapsulation-number number
The number of encapsulated TDM frames in Circuit Emulation Services over Packet Switch
Network (CESoPSN) or Structure-Agnostic Time Division Multiplexing over Packet (SAToP)
packets in the TDMoPSN application is set.
By default, the number of encapsulated TDM frames in a CESoPSN or SAToP packet is 8.
When the interface card where the AC interface locates is 8SA, 8E1T1-M or 8E1T1-F, the
interface can encapsulate a maximum of 16 TDM frames in a packet. If the value is larger
than 16, the interface only encapsulates 16 TDM frames in a packet.
You can determine the number of TDM frames encapsulated into each PW packet. The
smaller the number of frames encapsulated into a packet, the shorter the encapsulation and
transmission delay but the more the encapsulation overhead. The larger the number of frames
encapsulated into a packet, the higher the bandwidth utilization but the longer the
encapsulation delay.
Step 8 Run:
idle-code idle-code-value
The device is configured to fill idle codes when a jitter buffer underflow occurs.
By default, the system fills idle codes to FF.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
A jitter buffer underflow occurs when the device needs to read packets but there are not
sufficient packets in the buffer. The idle code has no significance, and can be set to any value.
Step 9 Run:
A tunnel policy is configured for the PW.
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 the tunnel policy
configuration, see step 1 in 13.8.8 Configuring and Applying a Tunnel Policy.
----End
Follow-up Procedure
13.8.4.3 Configuring PW
Context
When configuring TDM PWE3, you can create static PWs, dynamic PWs, or PW switching.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface serial interface-number
The serial interface view is displayed.
Step 3 Configure PWE3 function.

Choose either of them based on the networking.
1. Configure a static PW.
a. To configure an active PW, run:
mpls static-l2vc { { destination ip-address | pw-template pw-template-
name vc-id } * | destination ip-address [ vc-id ] } transmit-vpn-label
transmit-label-value receive-vpn-label receive-label-value [ tunnel-
policy tnl-policy-name | [ control-word | no-control-word ] | idle-code
idle-code-value | jitter-buffer depth | tdm-encapsulation number | tdm-
sequence-number ] *
b. (Optional) To configure a standby PW, run:

transmit-label-value receive-vpn-label receive-label-value [ tunnel-
policy tnl-policy-name | [ control-word | no-control-word ] | idle-code
idle-code-value | jitter-buffer depth | tdm-encapsulation number | tdm-
sequence-number ] * secondary

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
NOTE
– You can configure a standby PW only after an active PW is configured.

– The combination of the PW ID and PW type must be unique on each node. The IDs of PWs on two
ends can be the same. Active and standby PWs must have different VC IDs.
– Active and standby PWs must use the same control word configuration; otherwise, many packets
may be lost during service switching.
2. Configure a dynamic PW
a. To configure an active PW, run:
policy policy-name | [ control-word | no-control-word ] | mtu mtu-value
| idle-code idle-code-value | jitter-buffer depth | tdm-encapsulation-
number number | tdm-sequence-number ] *
b. (Optional) To configure a standby PW, run:

policy policy-name | [ control-word | no-control-word ] | mtu mtu-value
| idle-code idle-code-value | jitter-buffer depth | tdm-encapsulation-
number number | tdm-sequence-number ] * secondary
NOTE
– A dynamic PW requires that the VC ID of the same encapsulation type on a PE be unique.

Changing the encapsulation type may cause a VC ID collision.
– You can configure a standby PW only after an active PW is configured.
– The combination of the PW ID and PW type must be unique on each node. The IDs of PWs on two
ends can be the same. Active and standby PWs must have different VC IDs.
– Active and standby PWs must use the same control word configuration; otherwise, many packets
may be lost during service switching.
3. Configuring PW Switching
Perform this operation on the SPE only. Select static PW or dynamic PW based on the
PW switching mode on the UPE.
PW switching is classified into static mode, dynamic mode, and mixed mode:
– When static PWs are used between the SPE and two connected PEs, configure static
PW switching.
– When dynamic PWs are used between the SPE and two connected PEs, configure
dynamic PW switching.
– When a static PW and a dynamic PW are used between the SPE and two connected
PEs, configure mixed PW switching.
Perform either of the following operations based on actual needs.
– To configuring a static PW switching, run:
transparent ]

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
NOTE
When different PW encapsulation modes are selected, the parameters to be specified are as
follows:
n If encapsulation-type is set to satop-e1, the following parameters can be specified: [no-
control-word ] [ cc alert cv lsp-ping ].
n If encapsulation-type is set to cesopsn-basic, the following parameters can be specified:
control-word [ cc { alert | cw } * cv lsp-ping ], [no-control-word ] [ cc alert cv lsp-
ping ].
The timeslotnum timeslotnum needs to be configured.
– To configuring a dynamic PW switching, run:
– To configuring a mixed PW switching, run:

[ control-word | no-control-word ] [ timeslotnum timeslotnum ] [ tdm-
encapsulation number ] [ control-word-transparent ]
NOTE
n When you configure mixed PW switching, ip-address vc-id before between specifies the
VC ID of a dynamic PW and ip-address vc-id after between specifies the VC ID of a
static PW. The two values cannot be interchanged.
n In mixed PW switching, the MTUs of the interfaces on the two ends must be the same
and cannot be greater than 1500 bytes.
n When different PW encapsulation modes are selected, the parameters to be specified are
as follows:
○ If encapsulation-type is set to satop-e1, the following parameters can be specified:
mtu mtu-value, control-word, no-control-word, and tdm-encapsulation number.
○ If encapsulation-type is set to cesopsn-basic, the following parameters can be
specified: mtu mtu-value, control-word, no-control-word, timeslotnum
timeslotnum, and tdm-encapsulation number.
The timeslotnum timeslotnum needs to be configured.

mpls l2vpn pw performance disable
The statistics collection function for PWs on the TDM interface is disabled.
After PW is configured on a TDM interface, the statistics collection function for PWs on the
TDM interface is enabled by default. The system collects statistics on sent and received
packets of the primary PW at an interval of 15 minutes. To improve statistics collection
efficiency for system performance or other performance, you can perform this step to disable
the statistics collection function for PWs on the TDM interface.
----End
Prerequisites
The configurations of the TDM PWE3 are complete.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
NOTE
After a PW with the encapsulation type being TDM is configured on the AC side, PW performance statistics
collection is enabled on the related TDM interface by default. Run the undo mpls l2vpn pw performance
disable command can enable the function of PW performance information collection on a TDM interface.
Procedure
l Run the display pw-template [ pw-template-name ] command to check information
about the PW template.
l Run the display mpls switch-l2vc [ ip-address vc-id encapsulation encapsulation-type |
state { down | up } ] command on the SPE to view information about PW switching.
l Run the display mpls l2vpn interface interface-type interface-number performance
command to check PW performance information on a TDM interface.
----End
13.8.5 Configuring Static BFD for PWs

Static BFD for PWs enables the device to fast detect faults on PWs and trigger switching of
upper-layer applications. Static BFD applies to small-scale networks.
Before configuring static BFD for PWs, complete the following tasks:
l Setting IP parameters to make each node reachable

l Configuring a PW
The following configurations are mandatory and must be performed in sequence.
13.8.5.1 Enabling BFD Globally
Context
Before configure BFD for PWs, enable BFD globally. Perform the following operations on
the PEs at both ends of a PW.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Procedure
Step 1 Run:
system-view

Step 2 Run:
bfd
BFD is enabled globally on the local node and the BFD view is displayed.
----End
13.8.5.2 Configuring BFD for PWs
Context
You must configure or delete BFD for PWs on the two PEs of a PW simultaneously;
otherwise, the PW status on the two PEs may be different. Perform the following operations
on the two PEs of the PW to be detected.
Procedure
Step 1 Run:
system-view

Step 2 Run:
bfd cfg-name bind pw interface interface-type interface-number [ secondary ]
BFD for PWs is configured.

The outbound interface interface interface-type interface-number bound to a BFD session is
the AC interface where a PW resides.
To detect a secondary PW, specify secondary.
Step 3 Configure BFD discriminators.
l Run:
discriminator local discr-value
The local discriminator is set.

l Run:
discriminator remote discr-value
The remote discriminator is set.

NOTE
The local discriminator at the local end must be the same as the remote discriminator at the peer end,
and the remote discriminator at the local end must be the same as the local discriminator at the peer end.
Step 4 Run:
commit
The configuration is committed.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
When the PW status is Down, a BFD session can be set up but cannot go Up.
NOTE
l The local and remote BFD discriminators cannot be modified once being configured. To modify the
local or remote BFD discriminator, run the undo bfd bfd-name command in the system view to
delete the configuration of BFD for PWs, and then reconfigure the local or remote BFD
discriminator.
l After the PW is deleted, the related BFD session and configuration are deleted.
Step 5 (Optional) Set the encapsulation type for BFD CV packets to be sent to remote peers.
1. Run:
quit
Return to the system view.

2. Run:
mpls l2vpn
The MPLS L2VPN view is displayed.

3. Run either of the following commands:
– To set the encapsulation type to 0x04 for BFD CV packets to be sent to all remote
peers, run the mpls l2vpn vccv bfd-cv-negotiation fault-detection-only command.
– To set the encapsulation type 0x08 for BFD CV packets to be sent to all remote
peers, run the undo mpls l2vpn vccv bfd-cv-negotiation fault-detection-only
command.
– To set the encapsulation type to 0x04 for BFD CV packets to be sent to a specified
remote peer, run the mpls l2vpn vccv bfd-cv-negotiation fault-detection-only
peer peer-address enable command.
– To set the encapsulation type to 0x08 for BFD CV packets to be sent to a specified
remote peer, run the mpls l2vpn vccv bfd-cv-negotiation fault-detection-only
peer peer-address disable command.
– To restore the global encapsulation type of BFD CV packets to be sent to a
specified remote peer, run the undo mpls l2vpn vccv bfd-cv-negotiation fault-
detection-only peer peer-address command.
----End
Prerequisites
The configurations of static BFD for PWs are complete.
Procedure
l Run the display bfd configuration pw interface interface-type interface-number
[ secondary ] [ verbose ] command to check the BFD configuration.
l Run the display bfd session pw interface interface-type interface-number [ secondary ]
[ verbose ] command to check information about the BFD session.
----End

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
13.8.6 Configuring PWE3 FRR

After PWE3 FRR is configured, the L2VPN traffic is rapidly switched to the secondary path
when a fault occurs on the primary path. After the fault on the primary path is rectified, the
L2VPN traffic is switched back to the primary path based on a revertive switchover policy.
Context
On the network where CEs are asymmetrically connected to PEs, the secondary PW cannot
transmit data when the primary path and secondary path work properly. If the AC interface of
the secondary PW borrows the IP address of the AC interface of the primary PW, note the
following points:
l The switching policy No revertive switchover cannot be configured.
l The local CE has two equal-cost and direct routes to the remote CE. The destination
addresses and next hops of the two routes are the same. The route that passes through the
secondary PW is unreachable.
l If the CEs exchange routing information using routing protocols, change the cost or
metric value of the AC interface of the secondary path to a value greater than that of the
AC interface of the primary path. The local CE may be unable to communicate with the
remote CE, but can communicate with other remote user devices.
l If CEs use static routes and the AC links are Ethernet links, BFD for static routes needs
to be configured on CEs.
Before configuring PWE3 FRR, complete the following tasks:
l Configuring primary and secondary PWs of the same type on the network where CEs are
asymmetrically connected to PEs
l Configuring CEs to exchange routing information using routing protocols or static routes
Perform the operations in the following sequence. You can determine whether to perform
optional operations based on site requirements.
13.8.6.1 Configuring Primary and Secondary PWs
Context
You can configure primary and secondary PWs to protect services on the PWs.
l On the network where CEs are symmetrically dual-homed to PEs, configure one primary
PW for each of the primary and secondary paths. The primary and secondary paths can
be configured with different types of PWs.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
l On the network where CEs are asymmetrically connected to PEs, configure primary and
secondary PWs for the primary and secondary paths respectively. The primary and
secondary PWs must be of the same type.
Devices support only dynamic primary and secondary PWs.
Perform the following operations on the two PEs of a PW.
Procedure
Step 1 Configure dynamic primary and secondary PWs on the PEs. For details, see 13.8.2
Configuring a Dynamic PW.
NOTE
l Primary and secondary PWs must have different VC IDs.

l Primary and secondary PWs must use the same control word; otherwise, many packets may be lost
during service switching.
Step 2 (Optional) Configure other primary and secondary PW functions.

1. Run:

2. Run:
mpls l2vpn stream-dual-receiving
The primary and secondary PWs are configured to receive packets simultaneously.
When PWE3 FRR is configured on a network, you must configure the primary and
secondary PWs to receive packets simultaneously on the PE to which the PWs are
single-homed, preventing packet loss during PW revertive switchover.
----End
13.8.6.2 (Optional) Configuring Fast Fault Notification - OAM Mapping
Context
OAM mapping expedites the fault detection and notification on the AC end. OAM mapping
can be configured on various types of links. To configure OAM mapping on Ethernet links,
the PE and CE devices must support the Ethernet OAM function.
Choose either of the following procedures to configure OAM mapping according to the AC
types.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the AC interface is displayed.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Step 3 Run:
mpls l2vpn oam-mapping 3ah
The fault mapping between the AC and the PW is enabled.
NOTE
l The PW need be configured in homogeneous interworking mode when the AC is an Ethernet.

Otherwise, the use device may learn a wrong outbound interface according to ARP.
l Before running the mpls l2vpn oam-mapping 3ah command, you need configure Ethernet OAM on
the AC link. For details, refer to "EFM Configuration" in the Huawei
Enterprise Routers Configuration Guide - Reliability.
l If the mpls l2vpn oam-mapping command is configured, run the display mpls l2vc interface
command to check the VC status. In the command output, "Local AC OAM State" indicates the
status of the AC link; if the mpls l2vpn oam-mapping command is not configured, run the display
mpls l2vc interface command to check the VC status. In the command output, "Local AC OAM
State" is always Up, and has no relationship with the AC link status.
----End
13.8.6.3 (Optional) Configuring BFD for PW
Context
BFD for PW is recommended because it speeds up fault detection.
Procedure
For details, see the following topics.
l 13.8.5 Configuring Static BFD for PWs
NOTE
l BFD for PW on both PEs at the two ends must be configured or deleted simultaneously. Otherwise,
the statuses of PWs on the PEs are inconsistent.
l To monitor statuses of tunnels that carry PWs, configure BFD for tunnel. For detailed
configurations, see "MPLS LDP Configuration" and "MPLS TE Configuration" in Huawei
Enterprise Routers Configuration Manual MPLS.
13.8.6.4 (Optional) Configuring a Revertive Switchover Policy
Context
Revertive switching policies are classified into the following types:
l Immediate revertive switchover: When the primary PW recovers from a fault, the local
PE switches traffic back to the primary PW immediately and notifies the peer PE on the
secondary PW of the fault. In FRR mode, the local PE notifies the peer PE on the
secondary PW of the recovery after a delay of resume-time. In PW redundancy master/
slave mode, the parameter resume-time is not supported.
This revertive switchover applies to scenarios in which users hope traffic to be restored
as soon as possible.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
l Delayed revertive switchover: When the primary PW recovers from a fault, traffic is
switched back to the primary PW after a period specified by delay-time. After traffic is
switched back, the local device immediately notifies the peer device on the secondary
PW of the fault. If resume-time is configured in FRR mode, the local device notifies the
peer device on the secondary PW of the recovery after a delay of resume-time.
On a large-scale network, packet loss caused by incomplete route convergence may
occur during the switchback. To prevent this problem, configure traffic to be switched
back after a delay.
l None revertive switchover: When the primary PW recovers from a fault, traffic is not
switched back to the primary PW until the secondary PW becomes faulty.
If you do not want traffic to be frequently switched between the primary and secondary
PWs, you can use the non-revertive switchover.
By default, the delayed revertive switchover is performed.
A revertive switchover policy is configured on a PE. In asymmetric networking, if the active

PW is faulty, the PE to which a CE is connected through a single link switches traffic. When
the active PW is restored, configure a revertive switchover policy on this PE. The PE then
processes traffic based on the configured revertive switchover policy.
Perform the following operations on the PE (where traffic is switched) to which the CE is
connected through a single link.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
mpls l2vpn reroute { { delay delay-time | immediately } [ resume resume-time ] |
never }
The revertive switchover policy is configured.
For an asymmetric networking with ACs of the Ethernet type, if the Ethernet OAM function
is configured on the PE interface connected to a CE, and a revertive switching policy is also
configured, do not set resume-time to 0 seconds. Set resume-time to 1 second or longer.
NOTE
On the network where CEs are asymmetrically connected to PEs, the secondary PW cannot transmit data
when the primary and secondary paths work normally. On the CE in the dual-homed site, if the interface
of the secondary PW borrows the IP address of the interface of the primary PW, you cannot configure
revertive switchover.
----End
13.8.6.5 Check the Configuration

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Prerequisites
All configurations about PWE3 FRR are complete.
After PWE3 FRR is configured, you can view information about the local and remote PWs,
BFD sessions, L2VPN forwarding, and OAM mapping. You can also run the manual-set pw-
ac-fault command to simulate faults on a PW to verify whether the switchover between the
primary and secondary PWs is normal.
Procedure
l Run the manual-set pw-ac-fault command on the interface of the primary PW to
simulate faults on it to verify whether the switchover between the primary and secondary
PWs is normal.
l Run the display mpls l2vc [ vc-id | interface interface-type interface-number ]
command to check information about the local PWs.
l Run the display mpls l2vc remote-info [ vc-id ] command to check information about
the remote PWs.
l Run the display bfd session pw interface interface-type interface-number [ secondary ]
[ verbose ] command to check information about the BFD session.
l Run the display mpls l2vpn forwarding-info [ vc-label ] interface interface-type
interface-number command to check the MPLS L2VPN forwarding information.
----End
13.8.7 Configuring Inter-AS PWE3

Inter-AS PWE3 allows the MPLS backbone network to transmit PWE3 services over multiple
ASs.
Context
The devices support inter-AS PWE3 Option A. Option A is easy to implement; however, each
ASBR must provide a dedicated interface for each inter-AS VC. The interface can be a sub-
interface, physical interface, or logical interface. If the number of inter-AS VCs is small, this
solution can be used.
Before configuring inter-AS PWE3, complete the following tasks:
l Configuring an IGP protocol for the MPLS backbone network in each AS to ensure IP
connectivity of the backbone network within an AS
l Configuring basic MPLS functions on the MPLS backbone network in each AS
l Configuring MPLS LDP and establishing the LDP LSP for the MPLS backbone in each
AS
Procedure
The configurations of inter-AS PWE3 Option A are as follows:
l Perform the operation of Configuring a Dynamic PW in each AS.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
l Configure the ASBRs. Each ASBR considers the peer ASBR as its CE.
NOTE
You do not need to perform any additional configuration for inter-AS implementation on ASBRs and do
not need to configure IP addresses for the directly connected interfaces between ASBRs.
The configuration details are not mentioned here.

l Run the display mpls l2vc [ vc-id | interface interface-type interface-number ]
command on the PE to view information about the local PW.
l Run the display mpls l2vc remote-info [ vc-id ] command on the PE to view
information about the remote PW.
13.8.8 Configuring and Applying a Tunnel Policy

You need to configure tunnel policies on PEs when 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.
Context
Service data on the PWE3 network is transmitted over tunnels. By default, LSP tunnels are
used to transmit data, and each service is transmitted by only one LSP tunnel.
If the default tunnel configuration cannot meet PWE3 service requirements, apply tunnel
policies to VPNs. You can configure either of the following types of tunnel policies based on
service requirements:
l Tunnel type prioritization policy: This policy can change the type of tunnels selected for
PWE3 data transmission or select multiple tunnels for load balancing.
l Tunnel binding policy: This policy can bind multiple TE tunnels to provide QoS
guarantee for PWE3.
Before configuring and applying a tunnel policy, complete the following task:
l For details on how to create a GRE tunnel, see GRE Configuration in the Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR1600&AR2200&AR3200&AR36
00 Series Enterprise Routers Configuration Guide - VPN.
l For details on how to create an LSP tunnel, see MPLS LDP Configuration in the Huawei
00 Series Enterprise Routers Configuration Guide - MPLS.
l For details on how to create a TE tunnel, see MPLS TE Configuration in the Huawei
00 Series Enterprise Routers Configuration Guide - MPLS.
Perform the following operations on the PEs that need to use a tunnel policy.
Procedure
Step 1 Configure a tunnel policy.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Use either of the following methods to configure a tunnel policy.
Configure a tunnel type prioritization policy.
By default, no tunnel policy is configured. LSP tunnels are used to transmit PWE3 data and
each VPN service is transmitted over one LSP tunnel.
1. Run:
system-view

2. Run:
tunnel-policy policy-name
A tunnel policy is created, and tunnel policy view is displayed.

3. (Optional) Run:
description description-information
The description of the tunnel policy is configured.

4. Run:
tunnel select-seq { cr-lsp | gre | lsp } * load-balance-number load-balance-
number
The sequence in which each type of tunnel is selected and the number of tunnels
participating in load balancing are set.
Configure a tunnel binding policy.
1. Run:
system-view

2. Run:
interface tunnel interface-number
The tunnel interface view of the MPLS TE tunnel is displayed.

3. Run:
mpls te reserved-for-binding
The binding capability of the TE tunnel is enabled.

4. Run:
mpls te commit
The MPLS TE configuration is committed for the configuration to take effect.

5. Run:
quit
Return to the system view.

6. Run:
tunnel-policy policy-name
A tunnel policy is created.

7. (Optional) Run:
description description-information
The description of the tunnel policy is configured.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
8. Run:
tunnel binding destination dest-ip-address te { tunnel interface-number }
&<1-16> [ ignore-destination-check ] [ down-switch ]
The TE tunnel is bound to a specified tunnel policy.
NOTE
– If the PE has multiple peers, you can run the tunnel binding command multiple times to
specify different destination IP addresses in a tunnel policy.
– If down-switch is specified in the command, the system selects available tunnels in an order
of LSP, CR-LSP, and GRE when the bound tunnels are unavailable.
Step 2 Apply the tunnel policy.

Perform the following operations on AC interfaces on the PEs.
1. Run:
system-view

2. Run:
The interface view is displayed.

3. Use either of the following methods to create a static PW, a dynamic PW, or PW
switching.
– To create a static PW, run:
transmit-label-value receive-vpn-label receive-label-value tunnel-policy
tnl-policy-name [ [ control-word | no-control-word ] | [ raw | tagged ]
| idle-code idle-code-value | jitter-buffer depth | tdm-encapsulation
number | tdm-sequence-number | secondary ] *
NOTE
n When the AC interfaces are Ethernet interfaces, you can specify the parameters raw and
tagged.
n When the AC interfaces are serial interfaces, CE1/PRI interfaces, or E1-F interfaces, you can
specify the parameters idle-code, jitter-buffer, tdm-encapsulation, and tdm-sequence-
number.
– To create a dynamic 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 | idle-code idle-code-value | jitter-buffer
depth | tdm-encapsulation-number number | tdm-sequence-number |
secondary ] *
NOTE
n When the AC interfaces are Ethernet interfaces, you can specify the parameters raw and
tagged.
n When the AC interfaces are serial interfaces, CE1/PRI interfaces, or E1-F interfaces, you can
specify the parameters idle-code, jitter-buffer, tdm-encapsulation-number, and tdm-
sequence-number.
– To create static PW switching, run:

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers

transparent ]
– To create dynamic PW switching, run:

– To create mixed PW switching, run:

[ control-word [ cc { alert | cw } * cv lsp-ping ] | [ no-control-word ]
[ cc alert cv lsp-ping ] ] [ timeslotnum timeslotnum ] [ tdm-
encapsulation number ] [ control-word-transparent ]
----End

After configuring a tunnel policy and applying it to PWE3, you can check information about
the tunnel policy applied to the PWE3 and tunnels in the system.
l Run the display tunnel-policy [ tunnel-policy-name ] command to check the
configurations of tunnel policies.
13.9 Maintaining PWE3

This section describes how to maintain PWE3, including verifying connectivity of a PW and
locating a fault on a PW.
13.9.1 Verifying Connectivity of a PW
Context
Before using the ping vc and tracert vc commands to check connectivity of a PW, ensure that
the PWE3 network is correctly configured.
l VCCV ping can be performed in control word channel mode or Label alert channel
mode:
– Control word channel: supports detection between UPEs.
– Label alert channel: supports detection between CEs and per-hop detection between
the UPE and SPE.
By default, VCCV in Label Alert mode is enabled. Before using the control word channel, run
the control-word command to enable the control word function. VCCV in control word
channel mode is then enabled.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
When locating faults on the PW, you can use either VCCV in control word channel mode or
normal mode.
Checking connectivity of the PW is not supported in the following situations:
l SPEs do not support the ping vc and tracert vc command (these commands are
supported only by UPEs).
l Multiple users cannot run the command simultaneously. That is, the devices on the two
ends cannot ping a VC at the same time. On a device serving as both a UPE and an SPE,
if the PW serving as an SPE is performing VCCV ping, the PW serving as a UPE will be
unable to perform VCCV ping. That is, two VCCV pings cannot be performed on a same
device at the same time.
l The MTU check of the VC is not supported.
For an MH-PW, the local VC ID and VC type needs to be specified.
In the control word mode, if VC IDs are different, the VC ID of the remote UPE needs to be
specified. In the MPLS Label Alert mode, the addresses of the remote peer SPEs or UPEs
need to be specified.
Because a static PW does not support signaling negotiation, configurations of the UPE control
word on both ends of the PW are different, with the control word being enabled on one end,
but disabled on the other. When the MPLS Label Alert mode is enabled on both ends, the PW
can be Up and the ping vc command can work. CEs, however, cannot communicate with each
other because the control words are different.
Procedure
l Check the connectivity of the PW.
– Control word channel
ping vc pw-type pw-id [ -c echo-number | -m time-value | -s data-bytes | -t timeout-
value | -exp exp-value | -r reply-mode | -v ] * control-word [ remote remote-ip-
address peer-pw-id | draft6 ] * [ ttl ttl-value ] [ uniform ]
To check the connectivity of a PW switching, run the following commands:
value | -exp exp-value | -r reply-mode | -v ] * control-word remote remote-ip-
address peer-pw-id sender sender-address [ ttl ttl-value ] [ uniform ]
– Label Alert channel
value | -exp exp-value | -r reply-mode | -v ] * label-alert [ no-control-word ]
[ remote remote-ip-address | draft6 ] * [ uniform ]
– Normal mode
value | -exp exp-value | -r reply-mode | -v ] * normal [ no-control-word ] [ remote
remote-ip-address peer-pw-id ] [ ttl ttl-value ] [ uniform ]
l Locate a fault on the PW.
– Control word channel
tracert vc pw-type pw-id [ -exp exp-value | -f first-ttl | -m max-ttl | -r reply-mode | -
t timeout-value ] * control-word [ draft6 ] [ full-lsp-path ] [ uniform ]

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers

t timeout-value ] * control-word remote remote-ip-address [ ptn-mode | full-lsp-
path ] [ uniform ]
t timeout-value ] * control-word remote remote-pw-id draft6 [ full-lsp-path ]
[ uniform ]
– Label Alert channel
t timeout-value ] * label-alert [ no-control-word ] [ remote remote-ip-address ]
[ full-lsp-path ] [ draft6 ] [ uniform ]
– Normal mode
t timeout-value ] * normal [ no-control-word ] [ remote remote-ip-address ] [ full-
lsp-path ] [ draft6 ] [ uniform ]
----End
13.9.2 Locating a Fault on a PW
Context
After PWE3 is configured, you can locate any PW faults. To locate a fault on a PW, configure
basic PWE3 functions using a PW template, and then run the following commands on U-PEs.
Procedure
Step 1 Run the system-view command to enter the system view of the U-PE.
Step 2 Run the pw-template pw-template-name command to enter the PW template view.
Step 3 Run the control-word command to enable the control word function.
Step 4 Run either of the following commands to collect information about each LSR along the PW
and information about the egress PE.
l tracert vc pw-type pw-id [ -exp exp-value | -f first-ttl | -m max-ttl | -r reply-mode | -t

timeout-value ] * control-word [ draft6 ] [ full-lsp-path ] [ uniform ]
timeout-value ] * control-word remote remote-ip-address [ ptn-mode | full-lsp-path ]
[ uniform ]
timeout-value ] * control-word remote remote-pw-id draft6 [ full-lsp-path ]
[ uniform ]
timeout-value ] * label-alert [ remote remote-ip-address ] [ full-lsp-path ] [ draft6 ]
timeout-value ] * normal [ remote remote-ip-address ] [ full-lsp-path ] [ draft6 ]
When running the tracert vc command to locate a PW fault, pay attention to the following
points:

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
l The SPEs do not support this command. You can run this command on UPEs only.
l You can use this command to tracert a single-segment PW and a multi-segment PW
created using LDP.
l When tracerting a multi-segment PW, specify the remote PW ID in addition to the local
PW ID and PW type.
When the tracert vc command is run, the tracert operation is terminated in the following
cases:
l The PE that initiates tracert receives an MPLS Echo Reply packet from the egress PE.
l The TTL in the label of the previous MPLS Echo Request packet sent by the PE that
initiates tracert reaches the configured or default maximum number of hops.
l A user presses Ctrl+C on the PE that initiates tracert.
----End
13.10 Configuration Examples

This section describes PWE3 configuration examples including the networking requirements,
and configuration roadmap, configuration procedure, and configuration files.
13.10.1 Example for Configuring a Dynamic Single-Segment PW
Networking Requirements
As shown in Figure 13-12, the MPLS network of an ISP provides the L2VPN service for
users. Many users connect to the MPLS network through PE1 and PE2, and users on the PEs
change frequently. A proper VPN solution is required to provide secure VPN services for
users, save network resources, and simplify configuration when new users connect to the
network.
Figure 13-12 Networking diagram for configuring a dynamic single-segment PW (using an

LSP tunnel)
10.10.1.1/32 10.10.2.1/32 10.10.3.1/32
GE2/0/0 GE1/0/0 GE2/0/0 GE2/0/0

10.1.1.1/24 10.1.1.2/24 10.2.2.1/24 10.2.2.2/24
PE1 PE2
P
GE1/0/0 GE1/0/0
PW
GE1/0/0 GE1/0/0
10.3.1.1/24 10.3.1.2/24
CE1 CE2

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Configuration Roadmap
Because users on the two PEs change frequently, manual configuration is inefficient and may
cause configuration errors. In this scenario, the two PEs can set up a remote LDP session and
use the LDP protocol to synchronize user information through a dynamic PW. Compared with
Martini, PWE3 reduces the signaling cost and defines the multi-segment negotiation mode,
making networking more flexible. PWE3 is recommended if network resources need to be
saved.
The configuration roadmap is as follows:
1. Configure an IGP protocol on the backbone network so that backbone network devices
can communicate.
2. Configure basic MPLS functions and establish LSP tunnels on the backbone network.
Then establish the remote MPLS LDP peer relationship between the PEs at both ends of
the PW.
3. Create MPLS L2VC connections on the PEs.
Procedure
Step 1 Configure an IP address for each interface on the CEs, PEs, and the P according to Figure
13-12.
# Configure CE1. The configuration on PE1, P, PE2, and CE2 is similar to the configuration
on CE1 and is not mentioned here.
<Huawei> system-view
[Huawei] sysname CE1
[CE1] interface gigabitethernet 1/0/0
[CE1-GigabitEthernet1/0/0] ip address 10.3.1.1 255.255.255.0
[CE1-GigabitEthernet1/0/0] quit
Step 2 Configure an IGP protocol and Loopback address on the MPLS backbone network.
# Configure PE1. The configuration on P and PE2 is similar to the configuration on PE1 and
is not mentioned here.
[PE1] interface loopback 0
[PE1-LoopBack0] ip address 10.10.1.1 255.255.255.255
[PE1-LoopBack0] quit
[PE1] ospf 1
[PE1-ospf-1] area 0
[PE1-ospf-1-area-0.0.0.0] network 10.10.1.1 0.0.0.0
[PE1-ospf-1-area-0.0.0.0] quit
[PE1-ospf-1] quit
After the configuration is complete, run the display ip routing-table command. The
command out shows that PE1 and PE2 have learnt the routes to each other's Loopback0
interface through OSPF, and that PE1 and PE2 can ping each other.
Step 3 Enable MPLS, and set up tunnels and remote LDP sessions.
Enable MPLS on the MPLS backbone network, and set up an LSP tunnel and remote LDP
sessions between the PEs.
# Configure PE1.
[PE1] mpls
[PE1-mpls] mpls ldp
[PE1-mpls-ldp] quit

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
[PE1] interface gigabitethernet 2/0/0

[PE1-GigabitEthernet2/0/0] ip address 10.1.1.1 255.255.255.0
[PE1-GigabitEthernet2/0/0] mpls
[PE1-GigabitEthernet2/0/0] mpls ldp
[PE1-GigabitEthernet2/0/0] quit
[PE1] mpls ldp remote-peer 10.10.3.1
[PE1-mpls-ldp-remote-10.10.3.1] remote-ip 10.10.3.1
[PE1-mpls-ldp-remote-10.10.3.1] quit
# Configure P.
[P] mpls
[P-mpls] mpls ldp
[P-mpls-ldp] quit
[P] interface gigabitethernet 1/0/0
[P-GigabitEthernet1/0/0] ip address 10.1.1.2 255.255.255.0
[P-GigabitEthernet1/0/0] mpls
[P-GigabitEthernet1/0/0] mpls ldp
[P-GigabitEthernet1/0/0] quit
[P-GigabitEthernet2/0/0] ip address 10.2.2.1 255.255.255.0
# Configure PE2.
[PE2] mpls
[PE2-mpls] mpls ldp
[PE2-mpls-ldp] quit
After the configuration is complete, run the display mpls ldp session command on the
devices. The command output shows that LDP sessions are established between the PEs and
between the P and PEs, and the session status is Operational.
Step 4 Create VCs.
Enable MPLS L2VPN on PE1 and PE2, and create a VC on each PE.
# Configure PE1.
[PE1] mpls l2vpn
[PE1-l2vpn] quit
[PE1-GigabitEthernet1/0/0] mpls l2vc 10.10.3.1 100
# Configure PE2.
[PE2] mpls l2vpn
[PE2-l2vpn] quit
Step 5 Verify the configuration.

# Run the following command on the PEs to check the L2VPN connections. The command
output shows that an L2VC connection is set up and is in Up state.
# The display on PE1 is used as an example.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
[PE1] display mpls l2vc interface gigabitethernet 1/0/0

*client interface : GigabitEthernet1/0/0 is up
Administrator PW : no
session state : up
AC status : up
VC state : up
Label state : 0
Token state : 0
VC ID : 100
VC type : Ethernet
destination : 10.10.3.1
local group ID : 0 remote group ID : 0
local VC label : 1031 remote VC label : 1030
local AC OAM State : up
local PSN OAM State : up
local forwarding state : forwarding
local status code : 0x0
remote AC OAM state : up
remote PSN OAM state : up
remote forwarding state: forwarding
remote status code : 0x0
ignore standby state : no
BFD for PW : unavailable
VCCV State : up
manual fault : not set
active state : active
forwarding entry : exist
link state : up
local VC MTU : 1500 remote VC MTU : 1500
local VCCV : alert ttl lsp-ping bfd
remote VCCV : alert ttl lsp-ping bfd
local control word : disable remote control word : disable
tunnel policy name : --
PW template name : --
primary or secondary : primary
load balance type : flow
Access-port : false
Switchover Flag : false
VC tunnel/token info : 1 tunnels/tokens
NO.0 TNL type : lsp , TNL ID : 0x8
Backup TNL type : lsp , TNL ID : 0x0
create time : 0 days, 13 hours, 41 minutes, 24 seconds
up time : 0 days, 0 hours, 46 minutes, 55 seconds
last change time : 0 days, 0 hours, 46 minutes, 55 seconds
VC last up time : 2013/12/02 00:16:31
VC total up time : 0 days, 0 hours, 46 minutes, 55 seconds
CKey : 8
NKey : 7
PW redundancy mode : frr
AdminPw interface : --
AdminPw link state : --
Diffserv Mode : uniform
Service Class : --
Color : --
DomainId : --
Domain Name : --
# CE1 and CE2 can ping each other.

# The display on CE1 is used as an example.
[CE1] ping 10.3.1.2
PING 10.3.1.2: 56 data bytes, press CTRL_C to break
Reply from 10.3.1.2: bytes=56 Sequence=1 ttl=255 time=31 ms
--- 10.3.1.2 ping statistics ---
5 packet(s) transmitted

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 2/15/31 ms
----End
Configuration Files
l Configuration file of CE1
#
sysname CE1
#
interface GigabitEthernet1/0/0
ip address 10.3.1.1 255.255.255.0
#
return
l Configuration file of PE1

#
sysname PE1
#
mpls lsr-id 10.10.1.1
mpls
#
mpls l2vpn
#
mpls ldp
#
mpls ldp remote-peer 10.10.3.1
remote-ip 10.10.3.1
#
mpls l2vc 10.10.3.1 100
#
ip address 10.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 10.10.1.1 255.255.255.255
#
ospf 1
area 0.0.0.0
network 10.10.1.1 0.0.0.0
network 10.1.1.0 0.0.0.255
#
return
l Configuration file of the P

#
sysname P
#
mpls
#
mpls ldp
#
ip address 10.1.1.2 255.255.255.0
mpls
mpls ldp
#
ip address 10.2.2.1 255.255.255.0
mpls
mpls ldp
#

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
interface LoopBack0
ip address 10.10.2.1 255.255.255.255
#
ospf 1
area 0.0.0.0
network 10.10.2.1 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.2.2.0 0.0.0.255
#
return

#
sysname PE2
#
mpls
#
mpls l2vpn
#
mpls ldp
#
remote-ip 10.10.1.1
#
mpls l2vc 10.10.1.1 100
#
ip address 10.2.2.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 10.10.3.1 255.255.255.255
#
ospf 1
area 0.0.0.0
network 10.10.3.1 0.0.0.0
network 10.2.2.0 0.0.0.255
#
return

#
sysname CE2
#
ip address 10.3.1.2 255.255.255.0
#
return
13.10.2 Example for Configuring a Static Multi-Segment PW

As shown in Figure 13-13, sites of an enterprise at different geographical locations connect to
the MPLS network of an ISP through CE1 and CE2. The S-PE has powerful functions, and U-
PE1 and U-PE2 function as access devices and cannot directly establish remote LDP sessions.
To simplify configuration, the enterprise hopes that the two CEs communicate with each other
like on a LAN. That is, data packets of users traverse the ISP network without being modified
by the PEs. The enterprise will not increase sites in the future and wants to use exclusive VPN
resources of the ISP to protect user data security.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Figure 13-13 Networking diagram for configuring a static multi-segment PW

2.2.2.9/32 3.3.3.9/32 4.4.4.9/32
GE1/0/0 GE2/0/0
P1 20.1.1.2/24 30.1.1.1/24 P2
GE1/0/0 GE1/0/0 GE2/0/0
GE2/0/0
10.1.1.2/24 S-PE 30.1.1.2/24 40.1.1.1/24
20.1.1.1/24
Loopback0 Loopback0
1.1.1.9/32 5.5.5.9/32
PW U-PE2
U-PE1 ic
St
GE2/0/0 t GE1/0/0
ta
at
S 40.1.1.2/24
ic
10.1.1.1/24
PW
GE1/0/0 GE2/0/0
GE1/0/0 GE1/0/0
100.1.1.1/24 100.1.1.2/24
CE1 CE2
Because the enterprise will not increase sites in the future and wants to use exclusive VPN
resources, you can configure a static PW to meet the customer requirements. To use
hierarchical networking, configure a static multi-segment PW.
1. Configure a common routing protocol on the backbone network so that backbone
network devices can communicate.
2. Configure basic MPLS functions and establish LSPs on the backbone network.
3. Establish static MPLS L2VC connections on U-PEs.
4. Configure PW switching on the S-PE for a multi-segment PW.
Procedure
Step 1 Configure an IP address for each interface on the devices according to Figure 13-13.
# Configure CE1. The configuration on U-PE1, P1, S-PE, P2, U-PE2, and CE2 is similar to
the configuration on CE1 and is not mentioned here.
# Configure U-PE1. The configuration on P1, S-PE, P2, and U-PE2 is similar to the
configuration on U-PE1 and is not mentioned here.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
[U-PE1] interface loopback 0

[U-PE1-LoopBack0] ip address 1.1.1.9 255.255.255.255
[U-PE1-LoopBack0] quit
[U-PE1] ospf 1
[U-PE1-ospf-1] area 0
[U-PE1-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[U-PE1-ospf-1-area-0.0.0.0] quit
[U-PE1-ospf-1] quit
Step 3 Configure basic MPLS functions and set up LSP tunnels.

Configure basic MPLS functions on the MPLS backbone network, and set up LSP tunnels
between U-PE1 and S-PE, and between SPE and U-PE2. U-PE1 is used as an example. The
configurations of other devices are similar to the configuration of U-PE1 and are not
mentioned here.
# Configure U-PE1.
[U-PE1] mpls lsr-id 1.1.1.9
[U-PE1] mpls
[U-PE1-mpls] mpls ldp
[U-PE1-mpls-ldp] quit
[U-PE1] interface gigabitethernet 2/0/0
[U-PE1-GigabitEthernet2/0/0] ip address 10.1.1.1 255.255.255.0
[U-PE1-GigabitEthernet2/0/0] mpls
[U-PE1-GigabitEthernet2/0/0] mpls ldp
[U-PE1-GigabitEthernet2/0/0] quit
Step 4 Create VCs.

Enable MPLS L2VPN on U-PE1, U-PE2, and S-PE, and set up VCs on U-PE1 and U-PE2.
# Configure U-PE1.
[U-PE1] mpls l2vpn
[U-PE1-l2vpn] quit
[U-PE1] pw-template pwt
[U-PE1-pw-template-pwt] peer-address 3.3.3.9
[U-PE1-pw-template-pwt] quit
[U-PE1-GigabitEthernet1/0/0] mpls static-l2vc pw-template pwt 100 transmit-vpn-
label 100 receive-vpn-label 100
# Configure S-PE.
[S-PE] mpls l2vpn
[S-PE-l2vpn] quit
[S-PE] mpls switch-l2vc 5.5.5.9 100 trans 200 recv 200 between 1.1.1.9 100 trans
100 recv 100 encapsulation ethernet
# Configure U-PE2.
[U-PE2] mpls l2vpn
[U-PE2-l2vpn] quit
NOTE
The transmit-vpn-label configured on the U-PE must be the same as the recv label on the S-PE, and the
receive-vpn-label configured on the U-PE must be the same as the trans label on the S-PE. Otherwise,
CEs cannot communicate.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
# Run the following command on the PEs to check the L2VPN connections. The command
output shows that an L2VC connection is set up and is in Up state.
# The display on U-PE1 and the S-PE is used as an example.

[U-PE1] display mpls static-l2vc interface gigabitethernet 1/0/0
*Client Interface : GigabitEthernet1/0/0 is up
AC Status : up
VC State : up
VC ID : 100
VC Type : Ethernet
Destination : 3.3.3.9
Transmit VC Label : 100
Receive VC Label : 100
Label Status : 0
Token Status : 0
Control Word : Disable
VCCV Capabilty : alert ttl lsp-ping bfd
Link State : up
Tunnel Policy : --
PW Template Name : pwt
Main or Secondary : Main
Access-port : false
NO.0 TNL Type : lsp , TNL ID : 0x4
Backup TNL Type : lsp , TNL ID : 0x0
Create time : 0 days, 4 hours, 38 minutes, 4 seconds
UP time : 0 days, 0 hours, 12 minutes, 6 seconds
Last change time : 0 days, 0 hours, 12 minutes, 6 seconds
VC last up time : 2013/12/04 15:29:44
CKey : 2
NKey : 1
Service Class : --
Color : --
DomainId : --
Domain Name : --
[S-PE] display mpls switch-l2vc
Total Switch VC : 1, 1 up, 0 down
*Switch-l2vc type : SVC<---->SVC

Peer IP Address : 5.5.5.9, 1.1.1.9
VC ID : 100, 100
VC Type : Ethernet
VC State : up
In/Out Label : 200/200, 100/100
InLabel Status : 0 , 0
Control Word : Disable, Disable
VCCV Capability : alert ttl lsp-ping bfd , alert ttl lsp-ping bfd
Switch-l2vc tunnel info :
1 tunnels for peer 5.5.5.9
NO.0 TNL Type : lsp , TNL ID : 0xe
CKey : 8, 10
NKey : 7, 9
Tunnel policy : --, --
VC last up time : 2013/12/01 22:31:43

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
# CE1 and CE2 can ping each other successfully.

[CE1] ping 100.1.1.2

0.00% packet loss
----End
Configuration Files
#
sysname CE1
#
ip address 100.1.1.1 255.255.255.0
#
return
l Configuration file of U-PE1

#
sysname U-PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
pw-template pwt
peer-address 3.3.3.9
#
mpls ldp
#
mpls static-l2vc pw-template pwt 100 transmit-vpn-label 100 receive-vpn-
label 100
#
ip address 10.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 1.1.1.9 0.0.0.0
#
return
l Configuration file of P1
#
sysname P1
#

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
mpls lsr-id 2.2.2.9

mpls
#
mpls ldp
#
ip address 10.1.1.2 255.255.255.0
mpls
mpls ldp
#
ip address 20.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 20.1.1.0 0.0.0.255
network 2.2.2.9 0.0.0.0
#
return
l Configuration file of S-PE
#
sysname S-PE
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
mpls switch-l2vc 5.5.5.9 100 trans 200 recv 200 between 1.1.1.9 100 trans 100
recv 100 encapsulation ethernet
#
mpls ldp
#
ip address 20.1.1.2 255.255.255.0
mpls
mpls ldp
#
ip address 30.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 20.1.1.0 0.0.0.255
network 30.1.1.0 0.0.0.255
network 3.3.3.9 0.0.0.0
#
return
#
sysname P2
#
mpls lsr-id 4.4.4.9
mpls
#
mpls ldp
#

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
ip address 30.1.1.2 255.255.255.0
mpls
mpls ldp
#
ip address 40.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 4.4.4.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 4.4.4.9 0.0.0.0
network 30.1.1.0 0.0.0.255
network 40.1.1.0 0.0.0.255
#
return

#
sysname U-PE2
#
mpls lsr-id 5.5.5.9
mpls
#
mpls l2vpn
#
pw-template pwt
#
mpls ldp
#
ip address 40.1.1.2 255.255.255.0
mpls
mpls ldp
#
label 200
#
interface LoopBack0
ip address 5.5.5.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 5.5.5.9 0.0.0.0
network 40.1.1.0 0.0.0.255
#
return

#
sysname CE2
#
ip address 100.1.1.2 255.255.255.0
#
return

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
13.10.3 Example for Configuring a Dynamic Multi-Segment PW
users. The S-PE has powerful functions, and U-PE1 and U-PE2 function as access devices
and cannot directly establish remote LDP sessions. Many users connect to the MPLS network
through U-PE1 and U-PE2, and users on the U-PEs change frequently. A proper VPN solution
is required to provide secure VPN services for users and simplify configuration and
maintenance when new users connect to the network.
Figure 13-14 Networking diagram for configuring a dynamic multi-segment PW

2.2.2.9/32 3.3.3.9/32 4.4.4.9/32
GE1/0/0 GE2/0/0
P1 P2
20.1.1.2/24 30.1.1.1/24
GE1/0/0 GE2/0/0
GE2/0/0 GE1/0/0
10.1.1.2/24 40.1.1.1/24
20.1.1.1/24 S-PE 30.1.1.2/24
Loopback0 Loopback0
0
1.1.1.9/32 PW 5.5.5.9/32
10
GE2/0/0 GE1/0/0
PW
U-PE1 20 U-PE2
10.1.1.1/24 0 40.1.1.2/24
GE1/0/0 GE2/0/0
GE1/0/0 GE1/0/0
100.1.1.1/24 100.1.1.2/24
CE1 CE2
Because the S-PE has powerful functions, and U-PE1 and U-PE2 cannot directly establish
remote LDP sessions, you can configure a multi-segment PW and PW switching on the S-PE
to meet the customer requirements. To simplify maintenance, configure a dynamic multi-
segment PW.
can communicate.
2. Configure basic MPLS functions and establish LSPs on the backbone network. Establish
remote MPLS LDP peer relationships between U-PE1 and the S-PE, and between U-PE2
and the S-PE.
3. Create PW templates and enable the control word function and LSP ping.
4. Configure a dynamic PW on the S-PE.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
5. Configure PW switching on the S-PE.
Procedure
[U-PE1] ospf 1
[U-PE1-ospf-1] quit
After the configuration is complete, run the display ip routing-table command on the U-PEs,
Ps or S-PE. The command output shows that these devices have learnt the routes of each
other.
Step 3 Enable MPLS and set up LSP tunnels and remote LDP sessions.
Configure basic MPLS functions on the MPLS backbone network, and set up LSP tunnels and
remote LDP sessions between U-PE1 and the S-PE, and between the S-PE and U-PE2.
# Configure U-PE1.
[U-PE1] mpls
[U-PE1-mpls] quit
[U-PE1] mpls ldp
[U-PE1] mpls ldp remote-peer 3.3.3.9
[U-PE1-mpls-ldp-remote-3.3.3.9] remote-ip 3.3.3.9
[U-PE1-mpls-ldp-remote-3.3.3.9] quit
# Configure P1.
[P1] mpls lsr-id 2.2.2.9
[P1] mpls
[P1-mpls] quit
[P1] mpls ldp
[P1-mpls-ldp] quit
[P1] interface gigabitethernet 1/0/0
[P1-GigabitEthernet1/0/0] mpls
[P1-GigabitEthernet1/0/0] mpls ldp
[P1-GigabitEthernet1/0/0] quit

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers

# Configure the S-PE.

[S-PE] mpls lsr-id 3.3.3.9
[S-PE] mpls
[S-PE-mpls] quit
[S-PE] mpls ldp
[S-PE-mpls-ldp] quit
[S-PE] interface gigabitethernet 1/0/0
[S-PE-GigabitEthernet1/0/0] mpls
[S-PE-GigabitEthernet1/0/0] mpls ldp
[S-PE-GigabitEthernet1/0/0] quit
[S-PE] mpls ldp remote-peer 1.1.1.9
[S-PE-mpls-ldp-remote-1.1.1.9] remote-ip 1.1.1.9
[S-PE-mpls-ldp-remote-1.1.1.9] quit
# Configure P2.
[P2] mpls
[P2-mpls] quit
[P2] mpls ldp
[P2-mpls-ldp] quit
# Configure U-PE2.
[U-PE2] mpls
[U-PE2-mpls] quit
[U-PE2] mpls ldp
After the configuration is complete, run the display mpls ldp session command on the U-
PEs, Ps, or S-PE. The command output shows that the LDP sessions are established and the
status is Operational. Run the display mpls ldp peer command. The command output shows
that LDP peer relationships are established. Run the display mpls lsp command. The
command output shows that LSPs are established.
Step 4 Create and configure PW templates.
Create PW templates on the U-PEs, and enable the control word function.
# Configure U-PE1.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
[U-PE1] mpls l2vpn

[U-PE1-l2vpn] quit
[U-PE1-pw-template-pwt] control-word
# Configure U-PE2.
[U-PE2] mpls l2vpn
[U-PE2-l2vpn] quit
[U-PE2-pw-template-pwt] control-word
NOTE
You can also configure a dynamic PW without using the PW template. If the PW template is not used,
PW connectivity cannot be verified and path information of the PW cannot be collected. That is, you
cannot run the ping vc or tracert vc command.
Step 5 Create VCs.

Enable MPLS L2VPN on U-PE1, U-PE2, and the S-PE.
Configure dynamic PWs on U-PEs, and configure PW switching on the S-PE.
# Configure U-PE1.
[U-PE1-GigabitEthernet1/0/0] mpls l2vc pw-template pwt 100

[S-PE] mpls l2vpn
[S-PE-l2vpn] quit
[S-PE] mpls switch-l2vc 1.1.1.9 100 between 5.5.5.9 200 encapsulation ethernet
# Configure U-PE2.
[U-PE2-GigabitEthernet2/0/0] mpls l2vc pw-template pwt 200

1. View the PWE3 connection.
View the L2VPN connection on the U-PEs and S-PE. The command output shows that
an L2VC is set up and the VC status is Up.
The display on U-PE1 is used as an example.
[U-PE1] display mpls l2vc interface gigabitethernet 1/0/0
session state : up
AC status : up
VC state : up
Label state : 0
Token state : 0
VC ID : 100
VC type : Ethernet

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers

VCCV State : up
link state : up
local VCCV : cw alert ttl lsp-ping bfd
remote VCCV : cw alert ttl lsp-ping bfd
local control word : enable remote control word : enable
PW template name : pwt
Access-port : false
VC last up time : 2013/12/04 16:09:45
CKey : 4
NKey : 3
Service Class : --
Color : --
DomainId : --
Domain Name : --
Check the L2VC status on the S-PE.
*Switch-l2vc type : LDP<---->LDP

Peer IP Address : 5.5.5.9, 1.1.1.9
VC ID : 200, 100
VC Type : Ethernet
VC State : up
VC StatusCode |PSN |OAM | FW | |PSN |OAM | FW |
-Local VC :| UP | UP | UP | | UP | UP | UP |
-Remote VC:| UP | UP | UP | | UP | UP | UP |
Session State : up, up
Local/Remote Label : 1031/1028, 1032/1028
Local/Remote MTU : 1500/1500, 1500/1500
Local/Remote Control Word : Enable/Enable, Enable/Enable
Local/Remote VCCV Capability : cw alert ttl lsp-ping bfd /cw alert ttl
lsp-ping bfd , cw alert ttl lsp-ping bfd /cw alert ttl lsp-ping bfd
CKey : 14, 16
NKey : 13, 15
Control-Word transparent : NO

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers

VC last up time : 2013/12/01 23:02:39
2. Detect connectivity of the PW.

Run the ping vc command on the U-PEs. The command output shows that connectivity
of the PW is normal. The display on U-PE1 is used as an example.
[U-PE1] ping vc ethernet 100 control-word remote 5.5.5.9 200
Reply from 5.5.5.9: bytes=100 Sequence=1 time = 740 ms
--- FEC: FEC 128 PSEUDOWIRE (NEW). Type = vlan, ID = 100 ping statistics ---
0.00% packet loss
3. Check connectivity between the CEs and information about the paths between the CEs.
CE1 and CE2 can ping each other.
[CE1] ping 100.1.1.2

0.00% packet loss
On CE1, perform the tracert operation.

[CE1] tracert 100.1.1.2
traceroute to 100.1.1.2(100.1.1.2) max hops: 30 ,packet length: 40,press
CTRL_C to break
1 100.1.1.2 250 ms 220 ms 130 ms
----End
Configuration Files
#
sysname CE1
#
ip address 100.1.1.1 255.255.255.0
#
return

#
sysname U-PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
pw-template pwt

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
control-word
#
mpls ldp
#
remote-ip 3.3.3.9
#
mpls l2vc pw-template pwt 100
#
ip address 10.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 1.1.1.9 0.0.0.0
#
return
#
sysname P1
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
ip address 10.1.1.2 255.255.255.0
mpls
mpls ldp
#
ip address 20.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.255
network 20.1.1.0 0.0.0.255
#
return
l Configuration file of the S-PE
#
sysname S-PE
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
mpls switch-l2vc 1.1.1.9 100 between 5.5.5.9 200 encapsulation ethernet
#
mpls ldp
#

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
remote-ip 1.1.1.9
#
remote-ip 5.5.5.9
#
ip address 20.1.1.2 255.255.255.0
mpls
mpls ldp
#
ip address 30.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 20.1.1.0 0.0.0.255
network 30.1.1.0 0.0.0.255
#
return
#
sysname P2
#
mpls lsr-id 4.4.4.9
mpls
#
mpls ldp
#
ip address 30.1.1.2 255.255.255.0
mpls
mpls ldp
#
ip address 40.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 4.4.4.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 4.4.4.9 0.0.0.0
network 30.1.1.0 0.0.0.255
network 40.1.1.0 0.0.0.255
#
return
#
sysname U-PE2
#
mpls lsr-id 5.5.5.9
mpls
#
mpls l2vpn
#
pw-template pwt
control-word
#
mpls ldp

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
#
remote-ip 3.3.3.9
#
ip address 40.1.1.2 255.255.255.0
mpls
mpls ldp
#
mpls l2vc pw-template pwt 200
#
interface LoopBack0
ip address 5.5.5.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 5.5.5.9 0.0.0.0
network 40.1.1.0 0.0.0.255
#
return

#
sysname CE2
#
ip address 100.1.1.2 255.255.255.0
#
return
13.10.4 Example for Configuring a Mixed Multi-Segment PW

users. The S-PE has powerful functions, and U-PE1 and U-PE2 (U-PE2 supports only static
PWs) function as access devices and cannot directly establish remote LDP session. Many
users connect to the MPLS network through U-PE1 and U-PE2, and users on the U-PEs
change frequently. A proper VPN solution is required to provide secure VPN services for
users and simplify configuration and maintenance when new users connect to the network.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Figure 13-15 Networking diagram for configuring a mixed multi-segment PW

2.2.2.9/32 3.3.3.9/32 4.4.4.9/32
GE1/0/0 GE2/0/0
P1 P2
20.1.1.2/24 30.1.1.1/24
GE1/0/0 GE2/0/0
GE2/0/0 GE1/0/0
10.1.1.2/24 40.1.1.1/24
20.1.1.1/24 S-PE 30.1.1.2/24
Loopback0 Loopback0
0
10
St
1.1.1.9/32 5.5.5.9/32
a
PW
tic
GE2/0/0 GE1/0/0
PW
U-PE1 U-PE2
ic
10.1.1.1/24 40.1.1.2/24
20
a
yn
0
D
GE1/0/0 GE2/0/0
GE1/0/0 GE1/0/0
100.1.1.1/24 100.1.1.2/24
CE1 CE2
Because the S-PE has powerful functions, and U-PE1 and U-PE2 cannot directly establish
remote LDP sessions, you can configure a multi-segment PW and PW switching on the S-PE
to meet the customer requirements. U-PE2 supports only static PWs, so a mixed multi-
segment PW is used.
can communicate.
2. Configure basic MPLS functions and establish LSP tunnels on the backbone network.
3. Set up a remote LDP session between U-PE1 and the S-PE.
4. Set up static or dynamic MPLS L2VC connections on the U-PEs.
5. Configure PW switching on the S-PE.
Procedure

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
[U-PE1] ospf 1
[U-PE1-ospf-1] quit
Step 3 Enable MPLS, set up tunnels, and set up a remote LDP session between U-PE1 and the S-PE.
Configure basic MPLS functions and set up tunnels on the MPLS backbone network. In this
example, the LSP tunnel is used.
You need to set up a remote LDP session between U-PE1 and the S-PE. U-PE1 is used as an
example.
# Configure U-PE1.
[U-PE1] mpls
[U-PE1-mpls] quit
[U-PE1] mpls ldp
# Configure P1
[P1] mpls
[P1-mpls] quit
[P1] mpls ldp
[P1-mpls-ldp] quit

[S-PE] mpls lsr-id 3.3.3.9
[S-PE] mpls
[S-PE-mpls] quit
[S-PE] mpls ldp
[S-PE-mpls-ldp] quit

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers

# Configure P2
[P2] mpls
[P2-mpls] quit
[P2] mpls ldp
[P2-mpls-ldp] quit
# Configure U-PE2
[U-PE2] mpls
[U-PE2-mpls] quit
[U-PE2] mpls ldp
Step 4 Create VCs.

Enable MPLS L2VPN on U-PE1, U-PE2, and the S-PE.
Configure a dynamic VC on U-PE1 and a static VC on U-PE2, and configure mixed PW
switching on the S-PE.
# Configure U-PE1.
[U-PE1] mpls l2vpn
[U-PE1-l2vpn] quit
[U-PE1-GigabitEthernet1/0/0] mpls l2vc 3.3.3.9 100
NOTE
When you configure mixed PW switching, ip-address vc-id before between specifies the VC ID of a
dynamic PW and ip-address vc-id after between specifies the VC ID of a static PW. The two values
cannot be interchanged.

[S-PE] mpls l2vpn
[S-PE-l2vpn] quit
[S-PE] mpls switch-l2vc 1.1.1.9 100 between 5.5.5.9 200 trans 200 recv 100
encapsulation ethernet
# Configure U-PE2.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
[U-PE2] mpls l2vpn

[U-PE2-l2vpn] quit
# View information about L2VPN connections on the PEs. The command output shows that
an L2VC is set up and the VC status is Up.
# The display on U-PE1 and the S-PE is used as an example.

[U-PE1] display mpls l2vc interface gigabitethernet 1/0/0
session state : up
AC status : up
VC state : up
Label state : 0
Token state : 0
VC ID : 100
VC type : Ethernet
VCCV State : up
link state : up
Access-port : false
VC last up time : 2013/12/04 16:32:08
CKey : 6
NKey : 5

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Service Class : --
Color : --
DomainId : --
Domain Name : --
*Switch-l2vc type : LDP<---->SVC

Peer IP Address : 1.1.1.9, 5.5.5.9
VC ID : 100, 200
VC Type : Ethernet
VC State : up
Session State : up, None
Local(In)/Remote(Out) Label : 1033/1029, 100/200
Local/Remote MTU : 1500/1500, 1500
Local/Remote Control Word : Disable/Disable, Disable
Local/Remote VCCV Capability : alert ttl lsp-ping bfd /alert ttl lsp-ping bfd ,
alert ttl lsp-ping bfd
CKey : 18, 20
NKey : 17, 19
VC last up time : 2013/12/01 23:25:03

[CE1] ping 100.1.1.2

0.00% packet loss
----End
Configuration Files
#
sysname CE1
#
ip address 100.1.1.1 255.255.255.0
#
return

#
sysname U-PE1

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
mpls ldp
#
remote-ip 3.3.3.9
#
mpls l2vc 3.3.3.9 100
#
ip address 10.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 1.1.1.9 0.0.0.0
#
return
#
sysname P1
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
ip address 10.1.1.2 255.255.255.0
mpls
mpls ldp
#
ip address 20.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 20.1.1.0 0.0.0.255
network 2.2.2.9 0.0.0.0
#
return
l Configuration file of the S-PE
#
sysname S-PE
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
mpls switch-l2vc 1.1.1.9 100 between 5.5.5.9 200 trans 200 recv 100
encapsulation ethernet

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
#
mpls ldp
#
remote-ip 1.1.1.9
#
remote-ip 5.5.5.9
#
ip address 20.1.1.2 255.255.255.0
mpls
mpls ldp
#
ip address 30.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 20.1.1.0 0.0.0.255
network 30.1.1.0 0.0.0.255
network 3.3.3.9 0.0.0.0
#
return
#
sysname P2
#
mpls lsr-id 4.4.4.9
mpls
#
mpls ldp
#
ip address 30.1.1.2 255.255.255.0
mpls
mpls ldp
#
ip address 40.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 4.4.4.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 4.4.4.9 0.0.0.0
network 30.1.1.0 0.0.0.255
network 40.1.1.0 0.0.0.255
#
return
#
sysname U-PE2
#
mpls lsr-id 5.5.5.9
mpls
#
mpls l2vpn
#
pw-template pwt

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
#
mpls ldp
#
remote-ip 3.3.3.9
#
ip address 40.1.1.2 255.255.255.0
mpls
mpls ldp
#
label 200
#
interface LoopBack0
ip address 5.5.5.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 5.5.5.9 0.0.0.0
network 40.1.1.0 0.0.0.255
#
return

#
sysname CE2
#
ip address 100.1.1.2 255.255.255.0
#
return
13.10.5 Example for Configuring Inter-AS PWE3 Option A

users. PE1 becomes to AS 100 and PE2 belongs to AS 200. Many users connect to the MPLS
network through PE1 and PE2, and many new users will connect to the PEs in the future. A
proper VPN solution is required to provide secure VPN services for users, save network
resources, and simplify configuration when new users connect to the network.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Figure 13-16 Networking diagram for configuring inter-AS PWE3 Option A
IP/MPLS backbone IP/MPLS backbone

network network
AS 100 AS 200
Loopback0 Loopback0 Loopback0 Loopback0
1.1.1.9/32 2.2.2.9/32 3.3.3.9/32 4.4.4.9/32
GE2/0/0 GE1/0/0
GE2/0/0 GE1/0/0
10.1.1.1/24 30.1.1.2/24
GE1/0/0 GE2/0/0
10.1.1.2/24 ASBR -PE1 ASBR -PE2 30.1.1.1/24 PE2
PE1
GE1/0/0 GE2/0/0
GE1/0/0 GE1/0/0
100.1.1.1/24 100.1.1.2/24
CE1 CE2
MPLS backbone networks in the same AS use IS-IS as the IGP protocol.
The PEs connect to different ASs (AS 100 and AS 200) of the ISP, so an inter-AS VPN
solution is required. To simplify configuration when new users connect to the network and
save network resources, PWE3 Option A is recommended to meet the customer requirements.
1. Run an IGP protocol on the backbone network so that devices in an AS can

communicate.
2. Configure basic MPLS functions on the backbone network and establish a dynamic LSP
between the PE and ASBR-PE in the same AS. Establish a remote LDP session if the PE
and ASBR-PE are not directly connected.
3. Establish an MPLS L2VC between the PE and ASBR-PE in the same AS.
Procedure
Step 1 Configure an IP address for each interface on the devices according to Figure 13-16. CE1 is
used as an example.
# Configure CE1. The configuration on PE1, ASBR-PE1, ASBR-PE2, PE2, and CE2 is
similar to the configuration on CE1 and is not mentioned here.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
# Configure PE1. The configuration on ASBR-PE1, ASBR-PE2,and PE2 is similar to the

configuration on PE1 and is not mentioned here.
[PE1] isis 1
[PE1-isis-1] network-entity 10.0000.0000.0001.00
[PE1-isis-1] quit
After the configuration is complete, the IS-IS neighbor relationship can be established
between the ASBR-PE and PE in the same AS. Run the display isis peer command. The
command output shows that the neighbor relationship is Up.
Run the display ip routing-table command. The command output shows that the PE and
ASBR-PE in the same AS can learn the routes to the loopback interface of each other.
The ASBR-PE and PE in the same AS can ping each other successfully.
Step 3 Enable MPLS and configure a dynamic LSP.
Configure basic MPLS functions on the MPLS backbone network. Establish a dynamic LDP
LSP between the PE and ASBR-PE in the same AS.
# Configure PE1. The configuration on ASBR-PE1, ASBR-PE2,and PE2 is similar to the
configuration on PE1 and is not mentioned here.
[PE1] mpls lsr-id 1.1.1.9
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
After this step is performed, an LSP tunnel is established between the PE and ASBR-PE in
the same AS.
Step 4 Configure MPLS L2VCs.
Configure the L2VC on the PE and ASBR-PE and connect the PE to the CE.
# Configure PE1.
[PE1] mpls l2vpn
[PE1-l2vpn] quit
# Configure ASBR-PE1.
[ASBR-PE1] mpls l2vpn
[ASBR-PE1-l2vpn] quit
[ASBR-PE1] interface gigabitethernet 2/0/0
[ASBR-PE1-GigabitEthernet2/0/0] mpls l2vc 1.1.1.9 100
[ASBR-PE1-GigabitEthernet2/0/0] quit
# Configure ASBR-PE2.
[ASBR-PE2] mpls l2vpn
[ASBR-PE2-l2vpn] quit
[ASBR-PE2] interface gigabitethernet 1/0/0

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
[ASBR-PE2-GigabitEthernet1/0/0] mpls l2vc 4.4.4.9 100

[ASBR-PE2-GigabitEthernet1/0/0] quit
# Configure PE2.
[PE2] mpls l2vpn
[PE2-l2vpn] quit
# Run the following command to check information about the L2VPN connection on the PEs.
The command output shows that an L2VC is set up and the VC status is Up.
# The display on PE1 is used as an example.

[PE1] display mpls l2vc interface gigabitethernet 1/0/0
session state : up
AC status : up
VC state : up
Label state : 0
Token state : 0
VC ID : 100
VC type : Ethernet
VCCV State : up
link state : up
Access-port : false
VC last up time : 2013/12/04 17:17:07
CKey : 8
NKey : 7

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers

Service Class : --
Color : --
DomainId : --
Domain Name : --

The display on CE1 is used as an example.
[CE1] ping 100.1.1.2

0.00% packet loss
----End
Configuration Files
#
sysname CE1
#
ip address 100.1.1.1 255.255.255.0
#
return
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
mpls ldp
#
isis 1
network-entity 10.0000.0000.0001.00
#
mpls l2vc 2.2.2.9 100
#
ip address 10.1.1.1 255.255.255.0
isis enable 1
mpls
mpls ldp
#
interface LoopBack0
ip address 1.1.1.9 255.255.255.255
isis enable 1
#
return
l Configuration file of ASBR-PE1
#
sysname ASBR-PE1

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
mpls ldp
#
isis 1
network-entity 10.0000.0000.0002.00
#
ip address 10.1.1.2 255.255.255.0
isis enable 1
mpls
mpls ldp
#
mpls l2vc 1.1.1.9 100
#
interface LoopBack0
ip address 2.2.2.9 255.255.255.255
isis enable 1
#
return
l Configuration file of ASBR-PE2
#
sysname ASBR-PE2
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
mpls ldp
#
isis 1
network-entity 10.0000.0000.0003.00
#
mpls l2vc 4.4.4.9 100
#
ip address 30.1.1.1 255.255.255.0
isis enable 1
mpls
mpls ldp
#
interface LoopBack0
ip address 3.3.3.9 255.255.255.255
isis enable 1
#
return
#
sysname PE2
#
mpls lsr-id 4.4.4.9
mpls
#
mpls l2vpn
#
mpls ldp
#
isis 1
network-entity 10.0000.0000.0004.00
#

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
ip address 30.1.1.2 255.255.255.0

isis enable 1
mpls
mpls ldp
#
mpls l2vc 3.3.3.9 100
#
interface LoopBack0
ip address 4.4.4.9 255.255.255.255
isis enable 1
#
return
#
sysname CE2
#
ip address 100.1.1.2 255.255.255.0
#
return
13.10.6 Example for Configuring TDM PWE3 (Using the 8E1T1-M

Interface Card)
NOTE
Only the AR2220, AR2240 (using SRU40, SRU60, SRU80, SRU200, or SRU400), AR3200 (using SRU40,
SRU60, SRU80, SRU200, or SRU400), and AR3600 (using SRUX5) series routers can be used in this
scenario.
As shown in Figure 13-17, the carrier MPLS network provides the L2VPN service for users
who access the network through low-speed TDM links. The backbone devices are connected
through the 4GECS interface cards on which the Combo interfaces work as electrical
interfaces with a rate of 1000 Mbit/s. Many users connect to the network through PE1 and
PE2, and users on the PEs change frequently. (This example lists only two user devices CE1
and CE2, and they are connected to the PEs which have 8E1T1-M interface cards installed.) A
proper VPN solution is required to provide secure VPN services for users, save network
resources, and simplify configuration when new users connect to the network.
Figure 13-17 Configuring TDM PWE3 using the 8E1T1-M interface card
1.1.1.9/32 2.2.2.9/32 3.3.3.9/32
GE1/0/0 GE1/0/0 GE2/0/0 GE1/0/0

172.1.1.1/24 172.1.1.2/24 172.2.1.1/24 172.2.1.2/24
PE1 PE2
Serial2/0/0:0 P Serial2/0/0:0
Serial1/0/0:0 PW Serial1/0/0:0
192.168.1.1/24 192.168.1.2/24
CE1 CE2

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Because users on the PEs change frequently, manual configuration is inefficient and may
Martini, PWE3 reduces signaling costs and defines the multi-hop negotiation mode, making
networking more flexible. PWE3 is recommended if network resources need to be saved.
TDM PWE3 can be used to meet user requirements based on users' access modes.
1. Run an IGP protocol on the backbone network so that backbone devices can
communicate.
2. Enable basic MPLS capabilities, set up an LSP tunnel on the backbone network, and
establish a remote MPLS LDP peer relationship between the PEs at two ends of the PW.
3. Create an MPLS L2VC connection between CE1/PRI interfaces on the PEs to implement
TDM PWE3, so that users can communicate with each other.
4. Configure all the devices to work in clock synchronization state to ensure that CEs can
accurately exchange data with each other. In this example, the system clock of PE1 is
used as the clock source.
Procedure
Step 1 Configure IP addresses for the interfaces on the MPLS backbone network.
[Huawei] sysname PE1
Step 2 Configure an IGP protocol on the MPLS backbone network.

Configure an IGP protocol on the MPLS backbone network. In this example, OSPF is used.
[PE1] ospf 1
[PE1-ospf-1] area 0
[PE1-ospf-1] quit
After the configuration is complete, run the display ip routing-table command. You can view
that the devices have learnt routes to Loopback1 of each other.
Step 3 Enable MPLS, and set up LSPs and remote LDP sessions.
Enable MPLS on the MPLS backbone network and set up a remote MPLS peer relationship
between the PEs.
# Configure PE1.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers

[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
# Configure P.
[P] mpls lsr-id 2.2.2.9
[P] mpls
[P-mpls] quit
[P] mpls ldp
[P-mpls-ldp] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
After the configuration is complete, run the display mpls ldp session command. You can
view that LDP sessions are established between PEs and between PEs and P, and the session
status is Operational.
Step 4 Configure user devices to access the PEs.
Configure interface parameters on the CEs and PEs because user devices access the PEs
through low-speed TDM links.
# Configure CE1.
[CE1] controller e1 1/0/0
[CE1-E1 1/0/0] using e1
[CE1-E1 1/0/0] quit
[CE1] interface serial 1/0/0:0
[CE1-Serial1/0/0:0] link-protocol ppp
[CE1-Serial1/0/0:0] ip address 192.168.1.1 255.255.255.0
[CE1-Serial1/0/0:0] quit
# Configure PE1.
[PE1] controller e1 2/0/0
[PE1-E1 2/0/0] using e1

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
[PE1-E1 2/0/0] quit

[PE1] interface serial 2/0/0:0
[PE1-Serial2/0/0:0] link-protocol tdm
[PE1-Serial2/0/0:0] quit
# Configure PE2.
[PE2-E1 2/0/0] using e1
[PE2-E1 2/0/0] quit
[PE2-Serial2/0/0:0] link-protocol tdm
# Configure CE2.
[CE2-E1 1/0/0] using e1
[CE2-E1 1/0/0] quit
[CE2] interface serial 1/0/0:0
[CE2-Serial1/0/0:0] link-protocol ppp
[CE2-Serial1/0/0:0] ip address 192.168.1.2 255.255.255.0
[CE2-Serial1/0/0:0] quit
Step 5 Create a VC connection.
Enable MPLS L2VPN on PE1 and PE2, and create a VC connection between them.
# Configure PE1.
[PE1] mpls l2vpn
[PE1-l2vpn] quit
[PE1] pw-template pe2pe
[PE1-pw-template-pe2pe] peer-address 3.3.3.9
[PE1-pw-template-pe2pe] jitter-buffer depth 8
[PE1-pw-template-pe2pe] tdm-encapsulation-number 8
[PE1-pw-template-pe2pe] quit
[PE1-Serial2/0/0:0] mpls l2vc pw-template pe2pe 100
# Configure PE2.
[PE2] mpls l2vpn
[PE2-l2vpn] quit
[PE2-Serial2/0/0:0] mpls l2vc pw-template pe2pe 100
Step 6 Configure the clock synchronization function.
Configure all the devices to work in clock synchronization state; otherwise, CEs cannot
accurately exchange data with each other. The system clock of PE1 is used as the clock source
for all the devices.
# Configure PE1.
[PE1-GigabitEthernet1/0/0] clock master

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
[PE1-E1 2/0/0] clock system

[PE1-E1 2/0/0] quit
# Configure CE1.
[CE1-E1 1/0/0] clock slave
[CE1-E1 1/0/0] quit
# Configure the P.
[P-GigabitEthernet1/0/0] clock slave
[P] clock source 0 1/0/0
[P-GigabitEthernet2/0/0] clock master
# Configure PE2.
[PE2-GigabitEthernet1/0/0] clock slave
[PE2] clock source 0 1/0/0
[PE2-E1 2/0/0] clock system
[PE2-E1 2/0/0] quit
# Configure CE2.
[CE2-E1 1/0/0] clock slave
[CE2-E1 1/0/0] quit

# Check the L2VPN connections on PEs. You can see that an L2VC connection has been set
up and is in the Up state.
# The display on PE1 is used as an example:
[PE1] display mpls l2vc interface serial 2/0/0:0
*client interface : Serial2/0/0:0 is up
session state : up
AC status : up
VC state : up
Label state : 0
Token state : 0
VC ID : 100
VC type : SAT E1 over Packet
local TDM Encap Num : 8 remote TDM Encap Num : 8
jitter-buffer : 8
idle-code : ff
local rtp-header : disable remote rtp-header : disable
local bit-rate : 32 remote bit-rate : 32

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers

VCCV State : up
link state : up
local VC MTU : -- remote VC MTU : --
PW template name : pe2pe
Access-port : false
VC last up time : 2013/11/02 09:30:04
CKey : 9
NKey : 8
Diffserv Mode : pipe
Service Class : ef
Color : green
DomainId : --
Domain Name : --

# The display on CE1 is used as an example:
[CE1] ping 192.168.1.2

0.00% packet loss
----End
Configuration Files
#
sysname CE1
#
controller E1 1/0/0
using e1
#
interface Serial1/0/0:0
link-protocol ppp
ip address 192.168.1.1 255.255.255.0
#
return

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers

#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
pw-template pe2pe
#
mpls ldp
#
remote-ip 3.3.3.9
#
controller E1 2/0/0
using e1
clock system
#
link-protocol tdm
mpls l2vc pw-template pe2pe 100
#
ip address 172.1.1.1 255.255.255.0
mpls
mpls ldp
clock master
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 172.1.1.0 0.0.0.255
#
return
l Configuration file of the P device

#
sysname P
#
clock source 0 1/0/0 priority 9
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
ip address 172.1.1.2 255.255.255.0
mpls
mpls ldp
clock slave
#
ip address 172.2.1.1 255.255.255.0
mpls
mpls ldp
clock master
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
network 2.2.2.9 0.0.0.0

network 172.1.1.0 0.0.0.255
network 172.2.1.0 0.0.0.255
#
return

#
sysname PE2
#
clock source 0 1/0/0 priority 9
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
pw-template pe2pe
#
mpls ldp
#
remote-ip 1.1.1.9
#
controller E1 2/0/0
using e1
clock system
#
link-protocol tdm
#
ip address 172.2.1.2 255.255.255.0
mpls
mpls ldp
clock slave
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 172.2.1.0 0.0.0.255
#
return

#
sysname CE2
#
controller E1 1/0/0
using e1
#
link-protocol ppp
ip address 192.168.1.2 255.255.255.0
#
return

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
13.10.7 Example for Configuring TDM PWE3 (Uusing the 8SA

interface card)
NOTE
Only the AR2220, AR2240 (using SRU40, SRU60, SRU80, SRU200, or SRU400), AR3200 (using SRU40,
SRU60, SRU80, SRU200, or SRU400), and AR3600 (using SRUX5) series routers can be used in this
scenario.
As shown in Figure 13-18, the MPLS network of an Internet service provider (ISP) provides
the L2VPN service for users who access the network through low-speed TDM links. Many
users connect to the network through PE1 and PE2, and users on the PEs change frequently.
(This example lists only two user devices CE1 and CE2, and they are connected to the PEs
which have 8SA interface cards installed.) A proper VPN solution is required to provide
secure VPN services for users, save network resources, and simplify configuration when new
users connect to the network.
Figure 13-18 Configuring TDM PWE3 using the 8SA interface card
1.1.1.9/32 2.2.2.9/32 3.3.3.9/32
GE1/0/0 GE1/0/0 GE2/0/0 GE1/0/0

172.1.1.1/24 172.1.1.2/24 172.2.1.1/24 172.2.1.2/24
PE1 PE2
Serial2/0/0 P Serial2/0/0
Serial1/0/0 PW Serial1/0/0
192.168.1.1/24 192.168.1.2/24
CE1 CE2
Because users on the PEs change frequently, manual configuration is inefficient and may
Martini, PWE3 reduces signaling costs and defines the multi-hop negotiation mode, making
networking more flexible. PWE3 is recommended if network resources need to be saved.
TDM PWE3 can be used to meet user requirements based on users' access modes.
1. Run an IGP protocol on the backbone network so that backbone devices can
communicate.
2. Enable basic MPLS capabilities, set up an LSP tunnel on the backbone network, and
establish a remote MPLS LDP peer relationship between the PEs at two ends of the PW.
3. Create an MPLS L2VC connection between CE1/PRI interfaces on the PEs to implement
TDM PWE3, so that users can communicate with each other.

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Procedure
Step 1 Configure IP addresses for the interfaces on the MPLS backbone network.
[Huawei] sysname PE1
Step 2 Configure an IGP protocol on the MPLS backbone network.

Configure an IGP protocol on the MPLS backbone network. In this example, OSPF is used.
[PE1] ospf 1
[PE1-ospf-1] area 0
[PE1-ospf-1] quit
After the configuration is complete, run the display ip routing-table command. You can view
that the devices have learnt routes to Loopback1 of each other.
Step 3 Enable MPLS, and set up LSPs and remote LDP sessions.
Enable MPLS on the MPLS backbone network and set up a remote MPLS peer relationship
between the PEs.
# Configure PE1.
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
# Configure P.
[P] mpls lsr-id 2.2.2.9
[P] mpls
[P-mpls] quit
[P] mpls ldp
[P-mpls-ldp] quit

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
After the configuration is complete, run the display mpls ldp session command. You can
view that LDP sessions are established between PEs and between PEs and P, and the session
status is Operational.
Step 4 Configure user devices to access the PEs.
Configure interface parameters on the CEs and PEs because user devices access the PEs
through low-speed TDM links.
# Configure CE1.
[CE1] interface serial 1/0/0
[CE1-Serial1/0/0] link-protocol ppp
[CE1-Serial1/0/0] ip address 192.168.1.1 255.255.255.0
[CE1-Serial1/0/0] physical-mode async
[CE1-Serial1/0/0] quit
# Configure PE1.
[PE1] interface serial 2/0/0
[PE1-Serial2/0/0] link-protocol tdm
[PE1-Serial2/0/0] physical-mode async
[PE1-Serial2/0/0] quit
# Configure PE2.
[PE2-Serial2/0/0] link-protocol tdm
[PE2-Serial2/0/0] physical-mode async
# Configure CE2.
[CE2] interface serial 1/0/0
[CE2-Serial1/0/0] link-protocol ppp
[CE2-Serial1/0/0] ip address 192.168.1.2 255.255.255.0
[CE2-Serial1/0/0] physical-mode async
[CE2-Serial1/0/0] quit
Step 5 Create a VC connection.

Enable MPLS L2VPN on PE1 and PE2, and create a VC connection between them.
# Configure PE1.
[PE1] mpls l2vpn
[PE1-l2vpn] quit

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers

[PE1-Serial2/0/0] mpls l2vc pw-template pe2pe 100
# Configure PE2.
[PE2] mpls l2vpn
[PE2-l2vpn] quit
[PE2-Serial2/0/0] mpls l2vc pw-template pe2pe 100
# Check the L2VPN connections on PEs. You can see that an L2VC connection has been set
up and is in the Up state.
# The display on PE1 is used as an example:

[PE1] display mpls l2vc interface serial 2/0/0
*client interface : Serial2/0/0 is up
session state : up
AC status : up
VC state : up
Label state : 0
Token state : 0
VC ID : 100
VC type : CESoPSN basic mode
local TDM Encap Num : 8 remote TDM Encap Num : 0
jitter-buffer : 8
idle-code : ff
local rtp-header : disable remote rtp-header : disable
local bit-rate : 0 remote bit-rate : 0
VCCV State : up
link state : up
local VC MTU : -- remote VC MTU : --
PW template name : pe2pe
Access-port : false

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers

VC last up time : 2013/11/02 09:30:04
CKey : 9
NKey : 8
Diffserv Mode : pipe
Service Class : ef
Color : green
DomainId : --
Domain Name : --

# The display on CE1 is used as an example:
[CE1] ping 192.168.1.2

0.00% packet loss
----End
Configuration Files
#
sysname CE1
#
interface Serial1/0/0
link-protocol ppp
ip address 192.168.1.1 255.255.255.0
physical-mode async
#
return

#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
pw-template pe2pe
#
mpls ldp
#

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
remote-ip 3.3.3.9
#
link-protocol tdm
physical-mode async
#
ip address 172.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 172.1.1.0 0.0.0.255
#
return
l Configuration file of the P device
#
sysname P
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
ip address 172.1.1.2 255.255.255.0
mpls
mpls ldp
#
ip address 172.2.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 172.1.1.0 0.0.0.255
network 172.2.1.0 0.0.0.255
#
return
#
sysname PE2
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
pw-template pe2pe
#
mpls ldp
#
remote-ip 1.1.1.9
#

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
link-protocol tdm
physical-mode async
#
ip address 172.2.1.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 172.2.1.0 0.0.0.255
#
return

#
sysname CE2
#
link-protocol ppp
ip address 192.168.1.2 255.255.255.0
physical-mode async
#
return
13.11 References
This section provides references for the PWE3 feature.
The following table lists the RFC standards related to the PWE3 feature.
Document Description Remark

s
RFC3916 Requirements for Pseudo-Wire Emulation Edge-to- -

Edge (PWE3)
RFC3985 Pseudo Wire Emulation Edge-to-Edge (PWE3) -

Architecture
RFC4446 IANA Allocations for Pseudowire Edge to Edge -

Emulation (PWE3)
draft-ietf-pwe3- Pseudo wire Setup and Maintenance using the Label -

control-protocol-17 Distribution Protocol
draft-martini-pwe3- Pseudo Wire Switching -

pw-switching-03
draft-ietf-pwe3-cw-00 PWE3 Control Word for use over an MPLS PSN -
draft-ietf-pwe3- Pseudo Wire Virtual Circuit Connectivity -

vccv-03 Verification (VCCV)
draft-ietf-pwe3- Encapsulation Methods for Transport of Ethernet -

ethernet-encap-10 Over MPLS Networks

Huawei
AR100&AR120&AR150&AR160&AR200&AR1200&AR
Routers
Document Description Remark

s
draft-ietf-pwe3-atm- Encapsulation Methods for Transport of ATM Over -

encap-11 MPLS Networks
draft-ietf-pwe3-cell- PWE3 ATM Transparent Cell Transport Service -

transport-05
RFC 5085 Pseudowire Virtual Circuit Connectivity Verification The

(VCCV) A Control Channel for Pseudowires device
does not
support
PW
VCCV in
L2TP V3
mode.


01-13 PWE3 Configuration

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

01-13 PWE3 Configuration

Enviado por

Direitos autorais:

Formatos disponíveis

Huawei

About This Chapter

This chapter describes principles, applications, and configurations of the Pseudo-Wire

The AR100&AR120&AR150&AR160&AR200 series do not support PWE3.

13.1 Introduction to PWE3

Issue 02 (2017-10-13) Huawei Proprietary and Confidential 1284

13.1 Introduction to PWE3

Figure 13-1 PWE3 networking

Issue 02 (2017-10-13) Huawei Proprietary and Confidential 1285

13.2 Relationship Between PWE3 and L2VPN

13.2.1 Extensions to the Control Plane

TDM Interface Extension

PWE3 has the following advantages by supporting low-speed TDM interfaces:

l Adds encapsulation types (packets on low-speed TDM interfaces can be encapsulated).

l Fragmentation negotiation mechanism

Issue 02 (2017-10-13) Huawei Proprietary and Confidential 1286

13.2.2 Extensions at the Data Plane

13.3.1 Basic Principles

l Attachment circuit (AC)

Figure 13-2 PWE3 architecture

Issue 02 (2017-10-13) Huawei Proprietary and Confidential 1287

l CE1 sends Layer 2 packets to PE1 through an AC.

l Static PW and dynamic PW in terms of implementation

A multi-segment PW is required if a signaling connection or directly connected tunnel cannot be

Figure 13-3 Single-segment PW and multi-segment PW

Issue 02 (2017-10-13) Huawei Proprietary and Confidential 1288

Setup, Maintenance, and Teardown of a Dynamic PW

Figure 13-4 Setup and maintenance of a single-segment PW

mpls l2vc 2.2.2.2 101 Reque

Mappin mpls l2vc 1.1.1.1 101

Issue 02 (2017-10-13) Huawei Proprietary and Confidential 1289

Figure 13-5 Process of tearing down a single-segment PW

mpls l2vc 2.2.2.2 101 mpls l2vc 1.1.1.1 101

Figure 13-5 shows the PW teardown process.

Issue 02 (2017-10-13) Huawei Proprietary and Confidential 1290

Figure 13-6 Signaling exchange on a multi-segment PW

Loopback1 Loopback1 Loopback1

UPE1 SPE UPE2

mpls l2vc 2.2.2.2 100 Request

13.3.2 Control Word

Figure 13-7 Position of the CW in a packet

Tunnel Label /VC Label

Issue 02 (2017-10-13) Huawei Proprietary and Confidential 1291

The CW has the following functions:

Issue 02 (2017-10-13) Huawei Proprietary and Confidential 1292

13.3.4 PWE3 FRR

PWE3 FRR Implementation

Issue 02 (2017-10-13) Huawei Proprietary and Confidential 1293

Figure 13-8 Networking with asymmetrically connected CEs

Site1 P2 PE3 Site2

Issue 02 (2017-10-13) Huawei Proprietary and Confidential 1294

PW Revertive Switchover Policy

13.3.5 Inter-AS Technology

Issue 02 (2017-10-13) Huawei Proprietary and Confidential 1295

Figure 13-10 Inter-AS Option A networking

13.4.1 PWE3 Carrying Enterprise Leased Line Services on a MAN

Issue 02 (2017-10-13) Huawei Proprietary and Confidential 1296

PWE3 ensures stable Layer 2 communication between branches A and B, facilitates

Figure 13-11 PWE3 carrying enterprise leased line services on a MAN

13.5 Configuration Task Summary

Issue 02 (2017-10-13) Huawei Proprietary and Confidential 1297

Table 13-1 Summary of PWE3 configuration tasks

Issue 02 (2017-10-13) Huawei Proprietary and Confidential 1298

Scenario Description Task