177
Configuration procedure
To configure a Martini MPLS L2VPN connection on a Layer 3 interface on a PE:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Enter the view for the interface
connecting the CE
interface
interface-type
interface-number
The specified interface must be a
Layer 3 interface.
Create a Martini MPLS L2VPN
connection on the Layer 3 interface
mpls l2vc
destination
vcid
[ {
control-word
|
ethernet
|
no-control-word
|
vlan
} |
tunnel-policy
tunnel-policy-name
] *
Required
Return to system view
quit
—
Configure the remote peer
mpls ldp remote-peer
remote-peer-name
Required
remote-ip
ip-address
Required
NOTE:
•
For remote peer configuration information, see the chapter “Configuring basic MPLS.”
•
For a Martini connection, there are two main parameters: one is the IP address of the peer PE, the other
is the VC ID. The combination of the VC ID and the encapsulation type must be unique on a PE.
Changing the encapsulation type may result in VC ID conflicts.
•
You cannot both configure Martini MPLS L2VPN and enable MPLS on a Layer 3 interface. Otherwise,
neither the MPLS service nor the MPLS L2VPN service can work normally and you must remove both
services first for further service configuration.
•
If a Layer 3 Ethernet interface is bound with an L2VPN, the Layer 3 Ethernet sub-interfaces of the
interface cannot be bound with L2VPN or VPLS instances any more. If a Layer 3 Ethernet sub-interface
is bound with an L2VPN, the Layer 3 Ethernet interface of the sub-interface cannot be bound with
L2VPN or VPLS instances any more.
•
When configuring a Martini MPLS L2VPN connection on a Layer 3 Ethernet sub-interface on an
Ethernet interface card, you must configure the PW encapsulation mode as VLAN. Otherwise, packets
may not be forwarded correctly.
Configuring a Martini MPLS L2VPN connection based on Layer
2 Ethernet interface and VLAN