CCC is best suited for small MPLS networks with simple topologies. Because it does not require signaling negotiation or control packet exchange, CCC consumes fewer resources; however, it must be configured by network administrators, and therefore has poor scalability and is difficult to maintain.
In this case some CE connect to one PE, it need to communicate through the CE. We can create a local CCC connection enables two CEs that connect to the same PE to communicate.
The topology is as below:
Figure 1-1 CCC VPWS Topology
The CCC VPWS deployment guide is as below:
l Enable the MPLS and MPLS L2VPN on the PE
l Configure the local CCC connection on PE
The configuration template is as below:
Table 1-1 CCC VPWS Configuration Example
# mpls l2vpn # ccc ce1-ce2 interface gigabitethernet 1/0/0 out-interface gigabitethernet 2/0/0 // port GE 1/0/0 connect to CE1 and port GE2/0/0 connect to CE2 # commit # |
Note:
l Because the local CCC connection is bidirectional, only one connection is required, and only the inbound and outbound interfaces of the connection need to be configured on the PE.
l If the link encapsulation types on the two CEs are inconsistent, configure ip-interworking in this command to enable heterogeneous IP interworking for the local CCC connection.
l The raw, tagged, and access-port parameters can be configured in this command only when this command is applied to Ethernet links. The access-port parameter applies only to Ethernet main interfaces.
