H3C S9500 Series Operation Manual - page 6
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:
z
You also can configure LSPs without P devices.
z
If a VLL-enabled port is bound with user-defined flow template, the flow template
must contain a VLAN field.