Operation Manual – MPLS L2VPN
H3C S9500 Series Routing Switches
Chapter 1 MPLS L2VPN Configuration
1-14
Caution:
z
The
mtu
command is not recommended. It affects only parameter negotiation,
which may occur; it does not affect data forwarding.
z
With Kompella MPLS L2VPN, you must create on the PE an L2VPN instance for
each VPN where a directly connected CE resides. When creating an L2VPN, you
must specify an encapsulation type matching that of the CE interface.
z
The configuration of the VPN targets and RD are the same as that for MPLS L3VPN.
For Kompella MPLS L2VPN, the RD is required. Once configured, an RD cannot be
changed, unless you delete the L2VPN instance and then re-create it.
III. Creating a CE Connection
Follow these steps to create a CE connection:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Create a VPN and enter
MPLS L2VPN view
mpls l2vpn vpn-name
[
encapsulation
{
ethernet
|
vlan
} ]
Required
Create a CE for a VPN
and enter MPLS L2VPN
CE view
ce
ce-name
[
id
ce-id
[
range
ce-range
] [
default-offset
ce-offset
] ]
Required
Create a Kompella
connection
connection
[
ce-offset
id
]
interface
interface-type interface-number
[
tunnel-policy tunnel-policy-name
]
Required
Caution:
Do not enable VLL and MPLS on a VLAN interface of the device at the same time
because doing so will cause the MPLS L2VPN and MPLS services to malfunction at the
same time. You will have to cancel the configurations of these two services to restore
normal operation.
CE ID is used for identifying a CE uniquely in a VPN. To facilitate the configuration, it is
recommended to encode the CE IDs in continuous natural numbers starting from 1.
The CE range of a CE indicates the maximum number of CEs that the CE can connect
with. You can configure a CE range greater than what is required based on your
estimate of the future VPN expansion if the label resources are abundant (they are
