3Com 8807 Configuration Manual page 617

c
CCC MPLS L2VPN
Configuration Example
Table 564 Configure CCC MPLS L2VPN
Operation
Establish local CCC
connection
Establish remote CCC
connection
CAUTION:
In L2VPN, you can configure only one virtual circuit for each VLAN interface.
■
L2VPN supports VLAN interfaces only. When you configure an L2VPN on a
■
VLAN interface, data is encapsulated as Ethernet packets by default.
You can configure only one VLAN on the access side of each VPN private
■
network. Each VLAN can have only one interface, and all the VLANs connecting
to the interface must have IGMP disabled.
You must configure two static LSPs for each remote CCC connection. Two CCC
■
connections cannot share one static LSP.
A static LSP used by a remote CCC connection cannot be used for other
■
purposes (such as carrying IP packets and BGP/MPLS VPN packets). When you
configure a static LSP for a CCC connection, the next hop must be the IP
address from which the ARP packets are learnt.
Network requirements
CEs and the corresponding PEs shown in Figure 149 are interconnected through
their GigabitEthernet ports. Data is encapsulated as Ethernet packets at the data
link layer. A local connection is required between CE-A and CE-B, and a remote
connection between CE-A and CE-C.
CCC MPLS L2VPN Configuration
Command
ccc ccc-connection-name
interface vlan-interface
vlan-id out-interface
ccc ccc-connection-name
interface vlan-interface
vlan-id transmit-lsp
transmit-lsp-name
receive-lsp receive-lsp-name
617
Description
Required. Two types of CCC
connections exist: local CCC
connection and remote CCC
connection. A local CCC
connection is established
between two local CEs. It can
be switched directly by the PE
without being configured a
static LSP. A remote CCC
connection is established
between the local CE and a
remote CE. The two CEs are
attached to different PEs. In
this case, you need to
configure two static LSPs for
bidirectional packets
transmitted between the two
PEs.