Usage Scenario
VPWS in CCC mode applies to small MPLS networks with simple topologies. It needs neither signaling negotiation nor control packet exchange. Therefore, it consumes fewer resources and is easy to understand. However, it is inconvenient for maintenance, requires manual configuration of the administrator, and has poor scalability.
Two CEs connected to the same PE can communicate with each other using a local CCC connection established between the two CEs.
Prerequisites
MPLS L2VPN has been enabled.
Configuration Impact
An interface cannot serve as both an L2VPN AC interface and an L3VPN AC interface at the same time. If an interface is bound to an L2VPN, its Layer 3 features such as the IP address and routing protocol will not take effect. If an interface is bound to an L2VPN and an L3VPN at the same time, only the L2VPN connection is available. The L3VPN connection becomes available after the interface is unbound from the L2VPN.
Precautions
- A local CCC connection is bidirectional and therefore only one connection is required.
- A sub-interface that is bound to a VPWS can be deleted only after it is unbound from the VPWS.
- raw and tagged can be specified in the ccc interface out-interface command only when the CCC connection is established on an Ethernet link and IP interworking is not configured.
- By default, the encapsulation type on Ethernet main interfaces and Ethernet sub-interfaces is raw.