A CCC VLL does not require signaling negotiation or exchange of control packets; therefore, it requires few resources and is easy to configure. However, it requires manual configuration which makes network maintenance and expansion difficult. This mode applies to small-scale MPLS networks with simple topologies.
Before configuring a local CCC connection, enable basic MPLS capabilities on the PE and P devices of the MPLS backbone network.
Configure static routes or an Interior Gateway Protocol (IGP) on the PE and P devices of the MPLS backbone network to implement IP connectivity.
Enable basic MPLS capabilities on the PE and P devices of the MPLS backbone network.
Configure a local CCC connection.
To create a local CCC connection, configure the inbound and outbound interfaces of the CCC connection on the PE device. Perform the following operations on the PE device:
Run system-view
The system view is displayed.
Run mpls l2vpn
MPLS L2VPN is enabled and the MPLS L2VPN view is displayed.
MPLS L2VPN must be enabled on the PE device before you configure a VLL.
Run quit
Return to the system view.
Run ccc ccc-connection-name interface interface-type1 interface-number1 [ raw | tagged ] out-interface interface-type2 interface-number2 [ raw | tagged ]
A local CCC connection is created.
The local CCC connection is bidirectional; therefore, only one connection is required. The device can create local CCC connections only on VLANIF interfaces and uses the raw encapsulation mode by default.
Configure a remote CCC connection.
To create a remote CCC connection, configure the inbound interface, outbound interfaces, inbound label, and outbound label for the connection on the PE devices at both ends. If a P device is deployed between the two PE devices, configure a static LSP in both directions on the P device.
The remote CCC connection is unidirectional; therefore, two connections are required.
Perform the following operations on the PE devices at both ends of a VC:
Run system-view
The system view is displayed.
Run mpls l2vpn
MPLS L2VPN is enabled and the MPLS L2VPN view is displayed.
Run quit
Return to the system view.
Run ccc ccc-connection-name interface interface-type1 interface-number1 [ raw | tagged ] in-label in-label-value out-label out-label-value nexthop nexthop-address [ control-word | no-control-word ]
A remote CCC connection is created.
The device can create remote CCC connections only on VLANIF interfaces. A remote CCC connection uses the raw encapsulation mode by default.
Perform the following operations on the P device on the VC:
Run system-view
The system view is displayed.
Run static-lsp transit lsp-name [ incoming-interface interface-type interface-number ] in-label in-label { nexthop nexthop-address | outgoing-interface interface-type interface-number } * out-label out-label
The P device is configured as the transit label switching router (LSR) of the static LSP.
When creating a remote CCC connection, map the AC interfaces on the PE devices to static LSPs and configure static LSPs in both directions on the P device to exclusively transmit CCC connection data. You do not need to enable MPLS L2VPN on the P device.
The incoming label of the CCC and receive label of the SVC all range from 16 to 1023. They are in the same label space with those reserved for static LSPs. However, the outgoing label of the CCC and the transmit label of the SVC range from 0 to 1048575 because they are used for interworking.
After completing the CCC VLL configuration, run the following commands to check information about the CCC connection and interfaces used by the connection.