H3C S9500 Series User manual

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Table of Contents
i
Table of Contents
Chapter 1 MPLS VLL.....................................................................................................................1-1
1.1 MPLS VLL Overview..........................................................................................................1-2
1.1.1 Concepts in MPLS VLL...........................................................................................1-2
1.1.2 Introduction to MPLS VLL.......................................................................................1-2
1.1.3 Packet Forwarding ..................................................................................................1-3
1.1.4 Implementation........................................................................................................1-4
1.2 CCC MPLS VLL Configuration ..........................................................................................1-6
1.2.1 Configuring CCC MPLS VLL...................................................................................1-6
1.2.2 CCC MPLS VLL Configuration Example (1)...........................................................1-8
1.2.3 CCC MPLS VLL Configuration Example (2).........................................................1-11
1.3 Martini MPLS VLL Configuration .....................................................................................1-13
1.3.1 Configuring Martini MPLS VLL..............................................................................1-13
1.3.2 Martini MPLS VLL Configuration Example............................................................1-16
1.3.3 Martini MPLS VLL Primary/backup PW Configuration Example........................... 1-19
1.4 Kompella MPLS VLL Configuration.................................................................................1-25
1.4.1 Configuring Kompella MPLS VLL..........................................................................1-25
1.4.2 Kompella MPLS VLL Configuration Example (1)..................................................1-28
1.4.3 Kompella MPLS VLL Configuration Example (2)..................................................1-31
1.5 Displaying and Debugging MPLS VLL ............................................................................1-34
1.6 Troubleshooting MPLS VLL.............................................................................................1-34

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-1
Chapter 1 MPLS VLL
When configuringMPLS VLL, go to these sections for information you are interested in:
zMPLS VLL Overview
zCCC MPLS VLL Configuration
zMartini MPLS VLL Configuration
zKompella MPLS VLL Configuration
zDisplaying and Debugging MPLS VLL
zTroubleshooting MPLS VLL
For MPLS VLL configuration examples, go to the following sections:
zCCC MPLS VLL Configuration Example (1)
zCCC MPLS VLL Configuration Example (2)
zMartini MPLS VLL Configuration Example
zMartini MPLS VLL Primary/backup PW Configuration Example
zKompella MPLS VLL Configuration Example (1)
zKompella MPLS VLL Configuration Example (2)
Terms used in this document are listed below:
Table 1-1 Terminology
Term Full name
AC Attachment Circuit
CE Customer Edge
FEC Forwarding Equivalence Class
FR Frame Relay
NPE Network Facing PE
PE Provider Edge
PW Pseudowire
PHP Penultimate Hop Popping
UPE User Facing PE
VLL Virtual Leased Line
VPLS Virtual Private LAN Service
VSI Virtual Switching Instance
LSP Label Switched Path

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-2
1.1 MPLS VLL Overview
1.1.1 Concepts in MPLS VLL
MPLS Virtual Leased Line (MPLS VLL) provides transparently transmission of Layer 2
data of users over an MPLS network. From the users’ perspective, this MPLS network
is a Layer switched network through which Layer 2 connections can be set up between
different sites. AVLLis a point-to-point virtual connection service provided in the public
network. With the VLL, the two sites appear as if they were directly connected through
a circuit. However a VLL cannot provide switching service among multiple points
directly at the service provider.
1.1.2 Introduction to MPLS VLL
MPLS VLL provides MPLS network-based Layer 2 VPN services. For users, an MPLS
network is a Layer 2 switched network, through which Layer 2 connections can be
established between network nodes.
CE
VPN A VPN A
VPN B
PE PE
PE
LSP
PP
CE
CE
VPN B CE
VC
VC
Figure 1-2 Networking diagram of MPLS VLL
MPLS VLL has the following advantages:
zMultiple network layer protocols supported, such as IP, IPv6, IPX, and SNA.
zPowerful extensibility. MPLS VLL only establishes Layer 2 connections, rather
than imports and manages the routing information. This eases work load of PE
(provider edge) devices and the entire SP (service provider) network remarkably
and thus enables SPs to provide more VPNs and accommodate more users.
zReliability and privacy of user routes. As no user routing information is imported,
there is no need for MPLS VLL to obtainand process the information, ensuring the
privacy of user routes.
Figure 1-3 illustrates the structure of an MPLS VLL packet.

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-3
Tunnellabel VC label
Label Stack L2 PDU
Tunnel label VC label
Label Stack L2 PDU
Tunnellabel VC label
Label Stack L2 PDU
Tunnel label VC label
Label Stack L2 PDU
Figure 1-3 Structure of an MPLS VLL packet
The fields in an MPLS VLL packet are described as follows:
Tunnel label (the outer label) is an MPLS label or a GRE label. It is used to transmit a
packet from one PE to anther.
VC label (the inner label) is a lower layer label used to identify the links between PEs
and CEs. Packets of MPLS VLLs implemented through circuit cross connect (CCC) do
not contain this label.
Data in MPLS VLL can be encapsulated as Ethernet or VLAN packets at the data link
layer. At present, data of different nodes in a VPN must be encapsulated as the same
type of packets.
1.1.3 Packet Forwarding
In an MPLS VLL, CE, PE, and P operate in the same way as those in a BGP/MPLS
VPN. That is, they also forward packets in an MPLS network transparently by using
label stacks. To forward packets in an MPLS VLL, tunnels must be established first
between PEs (this can be achieved by either manual configuration or signaling
protocols). When the interfaces connecting PEs and CEs are up, PEs insert VC labels
for packets sent by CE, and then mark them with tunnel labels. On receiving these
packets, the remote PEs strip off the tunnel labels and send the packets to the
corresponding CEs according to their VC labels.
Figure 1-4 illustrates changes of the label stack of a packet during the forwarding.
Figure 1-4 Label stack processing of MPLS VLL

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-4
1.1.4 Implementation
At present, the official standard for MPLS VLL has not been established yet. However,
the PPVPN (Provider-provisioned Virtual Private Network) group of IETF (Internet
Engineering Task Force) defines multipleframework drafts, two of which are commonly
used. They are known as Martini draft and Kompella draft. Till May, 2005, they are
depicted in the following documents respectively:
zdraft-martini-l2circuit-trans-mpls-09.txt
zdraft-kompella-ppvpn-l2vpn-02.txt
Martini draft defines the way to implement MPLS VLL by establishing point-to-point
links. Here, LDP (Label Distribution Protocol) is used as the signaling protocol to
exchange VC labels. This kind of MPLS VLLs is known as Martini MPLS VLLs.
Kompella draft defines how to establish MPLS VLLs in MPLS networks through
end-to-end (CE-to-CE) connections. At present, BGP(border gateway protocol) is used
as the signaling protocol to propagate the information about Layer 2 reachability and
VC labels. Such MPLS VLLs are known as Kompella MPLS VLLs.
Also, you can establish MPLS VLLs without signaling protocols. In this case, MPLS VLL
services are provided through statically configured VC labels. An example of this is
CCC, which implement MPLS VLLs through static configuration.
Table 1-2 describes the features and implementation ways of the above three types of
MPLS VLLs.
Table 1-2 Features and implementation ways of the three types of MPLS VLLs
VPN type Implementation Feature
CCC
Configures static LSPs to
implement MPLS VLL.
You must manually configure two
LSPs (for sending and receiving
packets respectively) for each
CCC connection node by node
(including PEs and Ps). The
configured LSPs can only be used
to transmit packets of the
corresponding CCC connections.
Data is transmitted through
packets with single-layer
labels. LSPs are used
exclusively.
No signaling is needed to
transmit the Layer 2 VPN
information. Only MPLS
forwarding is required. In this
way, CEs of different SPs can
be interconnected easily.

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-5
VPN type Implementation Feature
Martini
Uses extended LDP as the
signaling to transmit the VC
information.
Uses VC-TYPE and VC-ID to
identify VCs. VC-TYPE indicates
the encapsulation type of data link
layer, and VC-ID uniquely
identifies a VC.
PEs connecting CEs exchange
VC labels through LDPs. They
bind the corresponding CEs
through VC-IDs.
Local switching like CCC is not
available.
An LSP can be shared by
multiple VCs.
Kompella
Similar to Layer 3 BGP/MPLS
VPN defined in RFC2547.
PEs discover Layer 2 VPN nodes
automatically through IBGP
sessions established between
them. They also propagate the
VPN information.
Labels are distributed in the form
of label blocks, which enables
multiple connections being
assigned tags simultaneously.
The size of a tag block is
determined by CE Range
(user-configurable).
VPN-target is used to differentiate
VPNs.
Users can assign extra labels
to VPNs for future use. This
eases the configuration work
loads of VPN deployment and
capacity expansion.
VPN-target is used to identify
VPNs. This brings great
flexibility for VPN networking.
Connections between CEs are
not concerned. This type of
MPLS VLL is implemented by
dividing the entire SP network
into different VPNs and
numbering these CEs in the
VPNs. To establish a
connection between two CEs,
you need to set the local CE ID
and the remote CE ID on the
PE, and specify the Circuit ID
assigned for the connection by
the local CE.
Note:
zYou also can configure LSPs without P devices.
zIf a VLL-enabled port is bound with user-defined flow template, the flow template
must contain a VLAN field.

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-6
Caution:
zMPLS VLL does not support NDP transparent transmission.
zIt is not recommended to bind VLLs on the default VLAN interface.
zMartini VLL and Kompella VLL modes support multiport access mode, while CCC
does not support this.
1.2 CCC MPLS VLL Configuration
1.2.1 Configuring CCC MPLS VLL
Follow these steps to configure CCC MPLS VLL:
To do... Use the command... Remarks
Enter system view system-view —
Configure LASR-ID mpls lsr-id ip-address Required
Enable MPLS mpls Required
Create the egress for
the static LSP
static-lsp egress lsp-name
l2vpn incoming-interface
vlan-interface vlan-id
in-label in-label
Create the ingress for
the static LSP
static-lsp ingress lsp-name
l2vpn nexthop
next-hop-addr out-label
out-label
Create the transit for
the static LSP
static-lsp transit lsp-name
l2vpn incoming-interface
vlan-interface vlan-id
in-label in-label nexthop
next-hop-addr out-label
out-label
Required. Before
configuring a CCC
connection, you need to
configure two static LSPs
between the two PEs and
all P routers in between
for bidirectional packets.
Refer to corresponding
sections in the command
manual for more
information about these
commands and
corresponding undo
commands.
Quit MPLS view and
enter system view quit —
Enable MPLS VLL mpls l2vpn Required

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-7
To do... Use the command... Remarks
Establish local CCC
connection
ccc ccc-connection-name
interface vlan-interface
vlan-id out-interface
vlan-interface vlan-id
Establish remote CCC
connection
ccc ccc-connection-name
interface vlan-interface
vlan-id transmit-lsp
transmit-lsp-name
receive-lsp
receive-lsp-name
Required. Two types of
CCC connections exist:
local CCC connection and
remote CCC connection.
A local CCC connection is
established between two
local CEs. It can be
switched directly by the
PE without being
configured a static LSP. A
remote CCC connection is
established between the
local CE and a remote
CE. The two CEs are
attached to different PEs.
In this case, you need to
configure two static LSPs
for bidirectional packets
transmitted between the
two PEs.
Caution:
zIn VLL, you can configure only one virtual circuit for each VLAN interface.
zVLL supports VLAN interfaces only. When you configure a VLL on a VLAN interface,
data is encapsulated as Ethernet packets by default.
zYou must use cards with the suffix CA (such as LSB2FT48CA) for the P devices and
PE devices at the access sides of CCC public/private network.
zYou can configure only one VLAN on the access side of each VPN private network.
Each VLAN can contain only one interface, and IGMP and IGMP Snooping cannot
be enabled in any of the VLANs configured on the interface. If IGMP and IGMP
Snooping are enabled in some of the VLANs configured on the interface, IGMP
packets cannot be transparently transmitted in the VPN.
zYou must configure two static LSPs for each remote CCC connection. Two CCC
connections cannot share one static LSP.
zA static LSP used by a remote CCC connection cannot be used for other purposes
(such as carrying IP packets and BGP/MPLS VPN packets). When you configure a
static LSP for a CCC connection, the next hop must be the IP address from which
the ARP packets are learnt.
zCCC does not support multiport access of private network.

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-8
1.2.2 CCC MPLS VLL Configuration Example (1)
I. Network requirements
CEs and the corresponding PEs shown in Figure 1-5 are interconnected through their
GigabitEthernet ports. Data is encapsulated as Ethernet packets at the data link layer. A
local connection is required between CE-A and CE-B, and a remote connection
between CE-Aand CE-C.
II. Network diagram
Local connection
Remote connection
CEB
CE CPE A PE B
VLAN212
VLAN212
VLAN211 VLAN211
VLAN213
CE A
VLAN214
P
Figure 1-5 Network diagram for CCC MPLS VLL (1)
III. Configuration procedure
1) Configure PE-A.
# Enable MPLS globally.
[H3C] mpls lsr-id 1.1.1.1
[H3C] mpls
# Enable MPLS VLL globally.
[H3C] mpls l2vpn
# Configure VLAN 211.
[H3C] vlan 211
[H3C-vlan211] port gigabitethernet 2/1/1
[H3C-Vlan211] interface vlan-interface 211
[H3C-Vlan-interface211] quit
# Configure VLAN 212.
[H3C] vlan 212
[H3C-vlan212] port gigabitethernet 2/1/2
[H3C-vlan212] interface vlan-interface 212
[H3C-Vlan-interface212] quit
# Configure VLAN 213.
[H3C] vlan 213

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-9
[H3C-vlan213] port gigabitethernet 2/1/3
[H3C-vlan213] interface vlan-interface 213
[H3C-Vlan-interface213] quit
# Enable MPLS on the interface of VLAN 214.
[H3C] vlan 214
[H3C-vlan214] port gigabitethernet 2/1/4
[H3C-vlan214] quit
[H3C] interface vlan-interface 214
[H3C-Vlan-interface214] ip address 5.5.5.1 24
[H3C-Vlan-interface214] mpls
[H3C-Vlan-interface214] quit
# Configure the local connection.
[H3C] ccc local-connection interface vlan-interface 211 out-interface
vlan-interface 213
# Configure a static LSP, with the out-label of 100 and the egress interface being the
interface of VLAN 214.
[H3C] mpls
[H3C-mpls] static-lsp ingress PEA-PEB l2vpn nexthop 5.5.5.2 out-label 100
# Configure a static LSP, with the in-label of 211 and the ingress interface being the
interface of VLAN 214.
[H3C-mpls] static-lsp egress PEB-PEA l2vpn incoming-interface vlan-interface
214 in-label 211
# Configure the remote connection.
[H3C] ccc remote-connection interface vlan-interface 212 transmit-lsp PEA-PEB
receive-lsp PEB-PEA
2) Configure PE-B.
# Enable MPLS globally.
[H3C] mpls lsr-id 10.0.0.1
[H3C] mpls
# Enable MPLS VLL globally.
[H3C] mpls l2vpn
# Configure VLAN 211.
[H3C] vlan 211
[H3C-vlan211] port gigabitethernet 2/1/1
[H3C] interface vlan-interface 211
[H3C-Vlan-interface211] quit
# Enable MPLS on the interface of VLAN 212.
[H3C] vlan 212

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-10
[H3C-vlan212] port gigabitethernet 2/1/2
[H3C-vlan212] quit
[H3C] interface Vlan-interface 212
[H3C-Vlan-interface212] ip address 6.6.6.1 24
[H3C-Vlan-interface212] mpls
# Configure a static LSP, with the out-label of 200 and the egress interface being the
interface of VLAN 212.
[H3C-mpls] static-lsp ingress PEB-PEA l2vpn nexthop 6.6.6.2 out-label 200
# Configure a static LSP, with the in-label of 101 and the ingress interface being the
interface of VLAN 212.
[H3C-mpls] static-lsp egress PEA-PEB l2vpn incoming-interface vlan-interface
212 in-label 101
# Configure the remote connection.
[H3C] ccc remote-connection interface vlan-interface 211 transmit-lsp PEB-PEA
receive-lsp PEA-PEB
3) Configure P.
[H3C] mpls lsr-id 10.0.0.2
[H3C] mpls
[H3C] vlan 214
[H3C-vlan214] port gigabitethernet 2/1/1
[H3C-vlan214] quit
[H3C] interface Vlan-interface 214
[H3C-Vlan-interface214] ip address 5.5.5.2 24
[H3C-Vlan-interface214] mpls
[H3C] vlan 212
[H3C-vlan212] port gigabitethernet 2/1/2
[H3C-vlan212] quit
[H3C] interface Vlan-interface 212
[H3C-Vlan-interface212] ip address 6.6.6.2 24
[H3C-Vlan-interface212] mpls
# Configure a static LSP, with the in-label of 100, the ingress interface being the
interface of VLAN 214, the out-label of 101, and the egress interface being the interface
of VLAN 212.
[H3C-mpls] static-lsp transit PEA-PEB l2vpn incoming-interface vlan-interface
214 in-label 100 nexthop 6.6.6.1 out-label 101
# Configure a static LSP, with the in-label of 200, the ingress interface being the
interface of VLAN 212, the out-label of 211, and the egress interface being the interface
of VLAN 211.

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-11
[H3C-mpls] static-lsp transit PEB-PEA l2vpn incoming-interface vlan-interface
212 in-label 200 nexthop 5.5.5.1 out-label 211
Caution:
Following must be met to make a local CCC connection to go up:
zThe interfaces of the two CE are physically up.
zThe encapsulation types of the interfaces of the two CEs are the same and are
supported by the MPLS VLL.
zFor Layer 2 connections with the MPLS VLL being VLAN encapsulation, the VLAN
IDs of the interfaces of the two CEs can either be the same or different. However, if
a trunk is configured between the CEs and the PEs on both sides, the VLAN IDs of
the interfaces of the two CEs must be the same.
1.2.3 CCC MPLS VLL Configuration Example (2)
I. Network requirements
zPE-A, PE-B, PE-C, and the P device constitute an MPLS domain.
zConfigure a remote CCC connection between PE-A and PE-B so that CE-A1 and
CE-B can communicate at Layer 2. Configure a CCC connection between PE-A
and PE-C through the P device, so that CE-A2 and CE-C can communicate at
Layer 2.
II. Network diagram
CE-A1
CE-A2
CE-B
CE-C
PE-A
PE-C
PE-B
P
VLAN12
VLAN14
VLAN23
VLAN34
VLAN14
VLAN14
VLAN34
VLAN23
GE3/1/1
VLAN12
LSP
AC AC
AC
LSP
Figure 1-6 Network diagram for CCC MPLS VLL (2)

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-12
III. Configuration procedure
1) Configure PE-A
# Configure the LSR-ID. Enable MPLS and MPLS L2VPN.
<PE-A> system-view
[PE-A] mpls lsr-id 1.1.1.1
[PE-A] mpls
[PE-A] mpls l2vpn
# Create public network VLAN 12, configure a VLAN interface, and then enable MPLS
for the VLAN interface.
[PE-A] vlan 12
[PE-A-vlan12] interface vlan-interface 12
[PE-A-Vlan-interface12] ip address 192.168.12.1 24
[PE-A-Vlan-interface12] mpls
[PE-A-Vlan-interface12] quit
# Configure static LSPs in MPLS view.
[PE-A] mpls
[PE-A-mpls] static-lsp ingress A-ingress l2vpn nexthop 192.168.12.2 out-label
821
[PE-A-mpls] static-lsp egress A-egress l2vpn incoming-interface
Vlan-interface 12 in-label 812
[PE-A-mpls] quit
# Create a private VLAN and a CCC connection.
[PE-A] vlan 4012
[PE-A-vlan4012] interface vlan-interface 4012
[PE-A-Vlan-interface4012] quit
[PE-A] ccc AB-connection interface Vlan-interface 4012 transmit-lsp A-ingress
receive-lsp A-egress
[PE-A] interface GigabitEthernet 3/1/1
[PE-A-GigabitEthernet3/1/1] port trunk permit vlan 4012
2) Configure other PE devices
The configurations required on the other PE devices are similar to those on PE-A and
are therefore omitted.
3) Configure the P device
# Configure the LSR-ID and enable MPLS (configuration steps are omitted).
# Create a public VLAN for each connected PE and assign an IP address for the VLAN
interface. Then, enable MPLS and MPLS LDP on the interface. Configure a Loopback
interface. Its IP address is used as the Router-ID (configuration steps are omitted).
# Configure static LSP in MPLS view.

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-13
<P> system-view
[P-mpls] static-lsp transit P l2vpn incoming-interface Vlan-interface34
in-label 843 nexthop 192.168.14.1 out-label 814
1.3 Martini MPLS VLL Configuration
1.3.1 Configuring Martini MPLS VLL
Follow these steps to configure Martini MPLS VLL:
To do... Use the command... Remarks
Enter system view system-view —
Configure the LSR-ID mpls lsr-id lsr-id Required
Enable MPLS mpls Required
Configure the LDP remote
peer mpls ldp
remote-peer index
Required.
Before configuring the
connection, you need to
enable LDP on each router
and each port of the public
network along the
connection and configure the
LDP remote peer on the peer
PE. For details, refer to the
LDP Configuration section in
MPLS Configuration.
Enable MPLS VLL mpls l2vpn Required
VLAN
interface view
interface
vlan-interface vlan
id —
Enter
VLAN
interface
view or port
view GE/10GE
port view
interface
GigabitEthernet
interface-number —

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-14
To do... Use the command... Remarks
In VLAN
interface view
mpls l2vc ip-address
vc-id
[preferred-path
peer tnl-address ]
encapsulation
{ethernet | vlan }
[primary |backup ]
[multi-port ] [ mtu
mtu ]
Required
To configure a Martini MPLS
VLL in VLAN interface view
on a PE, you need to provide
the IP address (lsr-id) of the
peer PE, the VC ID, and the
encapsulation type. The
combination of the IP
address and the VC ID must
be unique on the PE.
The default MTU is 1500
bytes.
Create a
Martini
MPLS VLL
virtual
connection
In GE/10GE
port view
mpls l2vc ip-address
vc-id
[preferred-path
peer tnl-address ]
vlan vlan-id
encapsulation
{ ethernet |vlan }
[ mtu mtu ]
To configure a Martini MPLS
VLL in port view on a PE,
you need to provide the IP
address (lsr-id) of the peer
PE, the VC ID, the PW
encapsulation type, and a
VLAN ID. The combination
of the IP address and the VC
ID must be unique on the
PE, and the VLAN ID must
be unique in the
configuration on the same
port.
The default MTU is 1500
bytes.
Return to system view quit —
Enter VLAN view interface vlan-interface vlan
id —
Manually switch the Martini
MPLS VLL virtual
connection on the VLAN
interface (primary or
backup)
mpls l2vc
manual-switch
[primary | backup ] Optional
Return to system view quit —
In system view, restore the
primary connections for all
Martini MPLS VLL virtual
connection configured
mpls l2vc
manual-restore Optional
In system view, enable the
primary connection
auto-restore function for
Martini MPLS VLL virtual
connections
mpls l2vc
auto-restore
delay-time
delay-time
Optional
The auto-restore function is
disabled by default.

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-15
To do... Use the command... Remarks
Display the information
about Martini MPLS VLL
virtual connections
display mpls l2vc
[interface
{ GigabitEthernet
interface-number
[vlan vlan-id ] |
vlan-interface
vlan-id } | verbose ]
display mpls l2vc
protection
[ interface
vlan-interface
vlan-id ]
Optional
Available in any view
Note the following:
zDuring the Martini VLL configuration, if you specify the tunnel destination address,
you must specify the 32-bit loopback address of the peer PE as the tunnel
destination address; if you do not specify the tunnel destination address, the
LSR-ID of the peer PE will be used as the tunnel destination address.
zYou must use cards with the suffix CA (such as LSB2FT48CA) on the public
network access sides when configuring Martini MPLS VLL; you can use cards with
the suffix C or CA on the private network access side.
zVLL configured on a VLAN interface supports single-port or multi-port VLAN
access private VLANs. If the encapsulation type is Ethernet access, the port link
type for the private VLAN is Access; if the encapsulation type is VLAN access, the
port link type for the private VLAN is Trunk.It is not recommended to use Hybrid as
the port link type for the private VLAN. The user access mode across the PW
connection must be the same.
zFor single-port access Martini VLL configuration, there can be only one VLAN at
the access side of each VPN, each VLAN can comprise only one interface, and
IGMP or IGMP Snooping must not be enabled in any VLAN on this interface; if
IGMP or IGMP Snooping is enabled in any VLAN on this interface, IGMP
messages cannot be transparently transmitted in this VPN.
zMultiport access Martini VLL does not support VLANs that contain hybrid inserted
cards or aggregated ports. On the same VLAN interface, the access mode of the
primary and backup virtual connection must be the same, both single-port access
or both multi-port access. For a multi-port access private network VLAN, the
encapsulation type of all the ports in the VLAN must be the same.
zCurrently only GE/10GE cards suffixed with CA support Martini VLL configuration
in port view (XP4CA cards and WAN cards, such as ATM, E1/T1 and CPOS, do
not support this configuration). Only one port is allowed at the access side of each
VPN, no duplicate VLAN ID configuration is allowed on the port, and this port must
belong to the VLAN in configuration. Make sure the STP is disabled on the port.
The Martini VLL configuration cannot be made on a port in hybrid insertion

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-16
configuration or an aggregation port. Other configurations, such other VLL
connections, IGMP, and IGMP snooping, cannot be made on the specified VLAN
interface; otherwise these configurations will not work normally. To allow normal
operation of other services configured on the VLAN interface, you need to remove
the Martini VLL configuration made on the port.
zCurrently only Martini VLLs configured on a VLAN interface support the
primary/backup VC mode, while port-based Martini VLLs do not support this.
zLSB1XP4CA0 cards do not support the multi-port VLL feature.
zInterface cards configured for ACL redirection in port groups (such as XP4B)
cannot be used as non-MPLS intermixing cards.
zThe MTU value set in Martini VLL configuration does not affect the actual MTU of
the link.
zIf you use the mpls l2vc manual-restore command to manually restore primary
connections for the MPLS VLL virtual connections on the device, the device will
automatically disable the primary connection auto-restore function.
zWith the primary connection auto-restore function enabled on the device, you can
still use the mpls l2vc manual-restore command to manually switch the MPLS
VLL virtual connection on the specified VLAN interface. In this case, if the primary
L2VC flapping occurs, after the primary virtual connection resumes normal, the
MPLS VLL virtual connection will switch to the primary L2VC automatically.
1.3.2 Martini MPLS VLL Configuration Example
I. Network requirements
CEs shown in Figure 1-7 are in the same VLAN as the corresponding PEs resides in. A
remote connection is required between CE-A and CE-B.
II. Network diagram
VLAN212
CE A CE B
PE A PEBP
VLAN22
VLAN21 VLAN212
Figure 1-7 Network diagram for Martini MPLS VLL
III. Configuration procedure
1) Configure PE-A.
# Configure the LSR-ID. Enable MPLS, LDP, and MPLS VLL.
[H3C-A] mpls lsr-id 192.1.1.1
[H3C-A] mpls
[H3C-A-mpls] quit
[H3C-A] mpls ldp
[H3C-A] mpls l2vpn

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-17
# Configure VLAN 212.
[H3C-A] vlan 212
[H3C-A-vlan212] port gigabitethernet 2/1/2
[H3C-A-vlan212]interface vlan-interface 212
[H3C-A-Vlan-interface212] quit
# Configure VLAN 21.
[H3C-A] vlan 21
[H3C-A-vlan21] port gigabitethernet 2/1/1
[H3C-A-vlan21] quit
[H3C-A] interface Vlan-interface 21
[H3C-A-Vlan-interface21] ip address 168.1.1.1 255.255.0.0
[H3C-A-Vlan-interface21] mpls
[H3C-A-Vlan-interface21] mpls ldp enable
# Configure an IP address for the Loopback interface, which is used as the Router ID.
[H3C-A] interface loopback 0
[H3C-A-LoopBack0] ip address 192.1.1.1 255.255.255.255
# Enable OSPF.
[H3C-A] ospf 1
[H3C-A-ospf-1] area 0.0.0.0
[H3C-A-ospf-1-area-0.0.0.0] network 192.1.1.1 0.0.0.0
[H3C-A-ospf-1-area-0.0.0.0] network 168.1.1.1 0.0.255.255
# Configure the LDP Remote Peer.
[H3C-A] mpls ldp remote-peer 1
[H3C-A-remote-peer-1] remote-ip 192.1.1.2
# Configure a Martini MPLS VLL connection.
[H3C-A] interface vlan-interface 212
[H3C-A-Vlan-interface212] mpls l2vc 192.1.1.2 20 encapsulation ethernet
2) Configure PE-B.
# Configure the LSR-ID. Enable MPLS, MPLS LDP, and MPLS VLL.
[H3C-B] mpls lsr-id 192.1.1.2
[H3C-B] mpls
[H3C-B-mpls] quit
[H3C-B] mpls ldp
[H3C-B] mpls l2vpn
# Configure VLAN 22.
[H3C-B] vlan 22
[H3C-B-vlan22] port gigabitethernet 2/1/1
[H3C-B-vlan22] interface Vlan-interface 22
[H3C-B-Vlan-interface22] ip address 169.1.1.1 255.255.0.0

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-18
[H3C-B-Vlan-interface22] mpls
[H3C-B-Vlan-interface22] mpls ldp enable
# Configure VLAN 212.
[H3C-B] vlan 212
[H3C-B-vlan212] port gigabitethernet 2/1/2
[H3C-B-vlan212] interface vlan-interface 212
[H3C-B-Vlan-interface212] quit
# Configure an IP address for the Loopback interface, which is used as the LSR-ID.
[H3C-B] interface loopback 0
[H3C-B-LoopBack0] ip address 192.1.1.2 255.255.255.255
# Enable OSPF.
[H3C-B] ospf 1
[H3C-B-ospf-1] area 0.0.0.0
[H3C-B-ospf-1-area-0.0.0.0] network 192.1.1.2 0.0.0.0
[H3C-B-ospf-1-area-0.0.0.0] network 169.1.0.0 0.0.255.255
# Configure the LDP Remote Peer.
[H3C-B] mpls ldp remote-peer 1
[H3C-B-mpls-remote1] remote-ip 192.1.1.1
# Configure a Martini MPLS VLL connection.
[H3C-B] interface vlan-interface 212
[H3C-B-Vlan-interface212] mpls l2vc 192.1.1.1 20 encapsulation ethernet
3) Configure P.
# Configure the LSR-ID. Enable MPLS, and LDP.
[H3C-P] mpls lsr-id 192.1.1.3
[H3C-P] mpls
[H3C-P-mpls] quit
[H3C-P] mpls ldp
# Configure an IP address for the Loopback interface and use it as the LSR-ID.
[H3C-P] interface loopback 0
[H3C-P-LoopBack0] ip address 192.1.1.3 255.255.255.255
[H3C-P-LoopBack0] quit
# Configure the VLAN interface.
[H3C-P] vlan 21
[H3C-P-vlan21] port gigabitethernet 2/1/1
[H3C-P-vlan21] quit
[H3C-P] interface Vlan-interface 21
[H3C-P-Vlan-interface21] mpls
[H3C-P-Vlan-interface21] mpls ldp enable

Operation Manual – MPLS VLL
H3C S9500 Series Routing Switches Chapter 1 MPLS VLL
1-19
[H3C-P-Vlan-interface21] ip address 168.1.1.2 255.255.0.0
[H3C-P-Vlan-interface21] quit
[H3C-P] vlan 22
[H3C-P-vlan22 port gigabitethernet 2/1/2
[H3C-P-vlan22] quit
[H3C-P] interface Vlan-interface 22
[H3C-P-Vlan-interface22] mpls
[H3C-P-Vlan-interface22] mpls ldp enable
[H3C-P-Vlan-interface22] ip address 169.1.1.2 255.255.0.0
# Enable OSPF.
[H3C-P] ospf 1
[H3C-P-ospf-1] area 0.0.0.0
[H3C-P-ospf-1-area-0.0.0.0] network 168.1.0.0 0.0.255.255
[H3C-P-ospf-1-area-0.0.0.0] network 169.1.0.0 0.0.255.255
[H3C-P-ospf-1-area-0.0.0.0] network 192.1.1.3 0.0.0.0
Caution:
Following must be met to make an LDP Layer 2 VPN to go up:
zThe interfaces of the two CEs are physically up.
zTwo LSP tunnels, which are opposite in direction, exist between two PEs.
zThe encapsulation types of interfaces of the two CEs are the same and are
supported by the MPLS VLL.
zIt is recommended that the VLANs on PE A and PE B which are connected to the
CEs be consistent.
zLDP remote sessions exist between PEs and are in Operational state.
zTo establish a tunnel, routes to the peer PE are necessary. So you need to
configure interior gateway protocol (IGP) on each router along the path, such as
OSPF.
1.3.3 Martini MPLS VLL Primary/backup PW Configuration Example
I. Network requirements
zThe CEs are connected through VLAN. A remote connection is established
between PE2 and PE1, PE2 and PE3, respectively.
zOn VLAN101, the virtual interface of PE2, configure a primary virtual connection to
PE1 and a backup virtual connection to PE3. Enable manual primary/backup
switchover on VLAN101.
zIn system view, restore the connection mode to primary.