Mpls L2Vpn Configuration Task List - H3C SR8800 10G Mpls Configuration Manual

The Martini method applies to scenarios with sparse Layer 2 connections, such as a scenario with a star
topology.
Kompella MPLS L2VPN
Kompella MPLS L2VPN is different from Martini MPLS L2VPN in that it does not operate on the
connections between CEs directly. It organizes different VPNs in the whole service provider network and
encodes each CE in a VPN. For a connection to be established between two CEs, you only need to
perform these tasks on the PEs:
Configuring CE IDs of the local and remote CEs respectively
•
• Specifying the circuit ID that the local CE assigns to the connection, such as the VPI/VCI with ATM.
Kompella MPLS L2VPN uses extended BGP as the signaling protocol to distribute VC labels. Its label
block mode allows it to assign labels to multiple connections at a time.
With Kompella MPLS L2VPN, you can specify the CE range of a VPN to indicate how many CEs can be
connected to the VPN. Then, the system assigns a label block of a size equal to the CE range for the CE.
In this way, you can reserve some labels for the VPN for future use. This wastes some label resources in
a short term, but can reduce the VPN deployment and configuration workload in the case of expansion.
Imagine that an enterprise VPN contains 10 CEs and the number may increase to 20 in future service
expansion. In this case, you can set the CE range of each CE to 20. Thus, when you need to add a CE
to the VPN later, you only need to modify the configurations of the PE to which the new CE is connected.
No change is required for the other PEs. This makes VPN expansion extremely simple.
Similar to MPLS L3VPN, Kompella MPLS L2VPN also uses VPN targets to identify VPNs. This brings
excellent VPN networking flexibility.
In addition, Kompella supports local connections.

MPLS L2VPN configuration task list

Complete the following tasks to configure MPLS L2VPN:
Task
Configuring MPLS L2VPN
Configuring CCC MPLS L2VPN
Configuring SVC MPLS L2VPN
Configuring Martini MPLS L2VPN
Configuring Kompella MPLS L2VPN
Enabling the MPLS L2VPN mix function
NOTE:
After you create an MPLS L2VPN connection on a Layer 3 interface, IP related functions on the
sub-interfaces of the Layer 3 interface will fail. For example, the sub-interfaces cannot receive ARP or
IGMP packets; they cannot forward unicast or multicast packets. After you remove the MPLS L2VPN
connection, the IP related functions on the sub-interfaces recover.
Remarks
Required
Use one of the approaches according to the MPLS
L2VPN implementation method
Optional
192