Ccc Mpls L2Vpn Configuration - 3Com 8807 Configuration Manual

616 C 51: MPLS VLL
HAPTER
CCC MPLS L2VPN
Configuration
Configuring CCC MPLS
L2VPN
Table 563 Features and implementation ways of the three types of MPLS L2VPNs
VPN type Implementation
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
Kompella
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.
n
You also can configure LSPs without P devices.
Table 564 Configure CCC MPLS L2VPN
Operation
Enter system view
Configure LSR ID
Enable MPLS
Create the egress for the
static LSP
Create the ingress for the
static LSP
Create the transit for the
static LSP
Quit MPLS view and enter
system view
Enable MPLS L2VPN
Feature
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 L2VPN 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.
Command
system-view
mpls lsr-id X.X.X.X
mpls
static-lsp egress lsp-name
l2vpn incoming-interface
vlan-interface vlan-id
in-label in-label
static-lsp ingress lsp-name
l2vpn nexthop
next-hop-addr out-label
out-label
static-lsp transit lsp-name
l2vpn incoming-interface
vlan-interface vlan-id
in-label in-label { nexthop
next-hop-addr |
out-interface vlan-interface
vlan-id } out-label out-label
quit
mpls l2vpn
Description
-
Required
Required
Required. Before configuring
a CCC connection, you need
to configure two static LSPs
between the two PEs and all P
routers in between for
bidirectional packets. Refer to
corresponding sections in the
command manual for more
information about these
commands and corresponding
undo commands.
-
Required