
155
To set up a local VC connection, you only need to bind two ACs on the PE.
This document only describes the MPLS L2VPN-related configurations on PEs. The MPLS L2VPN is
transparent to a user network. You do not need to perform MPLS L2VPN-specific configurations on
CEs.
To configure MPLS L2VPN on a PE:
Task Remarks
Required.
Perform this task to enable MPLS L2VPN. You can
perform other MPLS L2VPN configurations only after
you enable MPLS L2VPN.
Required.
Perform this task to set up an AC between a PE and
a CE.
Use one of the methods according to the MPLS
L2VPN implementation method.
For a remote connection, perform this task to set up
a VC, and bind the VC to an AC.
For a local connection, perform this task to bind two
ACs on a PE.
Configuring Martini MPLS L2VPN
Configuring Kompella MPLS L2VPN
Creating a VC on a Layer 3 interface disables the IP related functions on the sub-interfaces of the
Layer 3 interface. For example, the sub-interfaces cannot receive ARP or IGMP packets. They
cannot forward unicast or multicast packets. After you remove the VC, the IP related functions on the
sub-interfaces recover.
Configuring basic MPLS L2VPN
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Configure the LSR ID.
mpls lsr-id
lsr-id
N/A
3.
Configure basic MPLS and
enter MPLS view.
mpls
N/A
4.
Return to system view.
quit
N/A
5.
Enable L2VPN and enter
L2VPN view.
l2vpn
Disabled by default.
6.
Enable MPLS L2VPN.
mpls l2vpn
Disabled by default.
Configuring a PE-CE interface
A PE-CE interface refers to a PE's interface connected to a CE. On a PE-CE interface, you must
configure the link layer protocol to set up an AC between the PE and CE. The configurations on the
interface vary with different VC types.
The PE forwards packets received from a PE-CE interface through the bound VC without network
layer processing. Therefore, you do not need to configure an IP address for a PE-CE interface.