Cloud Connect Network (CCN) bridges between Tencent Cloud VPCs and between VPCs and local IDCs. It provides you with public and private network multi-point interconnection, route self-learning, linkage prioritization, failure fast convergence, and other capabilities. With its presence in over 20 regions around the world, 100+ Gbps bandwidth and 99.99% high availability, it helps you easily build fast, stable, secure, and flexible globally interconnected networks. CCN is typically used in:
A CCN consists of:
The VPN gateway associated with CCN is now in beta test. To apply for its use, [Submit a Ticket] (https://console.cloud.tencent.com/workorder/category). For more information, see Connecting IDC to CCN via VPN Gateway.
CCN has the following features:
CCN features multi-node multi-route-level automatic forwarding and learning on the public and private network and route convergence in seconds, which allows you to interconnect all network instances with a simple step, and manage them easily.
CCN frees you from the heavy route maintenance with its Full Mesh interconnection between multiple nodes and links in public and private networks. The smart scheduling system monitors the multi-layer network topology, routes, and traffic of the entire network to connect your local services to the nearest point and ensure interconnection using the shortest link.
CCN automatically learns multi-level routes, and updates the routing table if your network topology changes. This simple management replaces your extra manual configuration or updates, which in turn, greatly improves the scalability and OPS efficiency of your network.
Without CCN, if you want to interconnect multiple VPCs and your IDC with multiple VPCs, you need to establish one peering connection for each pair of VPCs and one dedicated tunnel between your IDC and each VPC. And then, you also need to make sure VPC and IDC IP ranges do not overlap. After establishing the connection, you must manage the route tables of instances and manually add routing policies to make it all work.
On the other hand, doing the same with CCN would only require a CCN instance and adding all VPCs and the IDC to the CCN instance. After you add the instances to the CCN, it will automatically forward and learn all routes, saving you the hassle of manually configuring and managing the route tables of the instances.
For details on how to migrate existing applications to CCN, refer to Best Practices.
|CCN Benefit||Peering Connection/Dedicated Tunnel||CCN|
|Full-mesh links||1. To interconnect multiple VPCs, you need to establish Cn2 peers.
2. A single dedicated tunnel can only connect to one VPC.
3. VPCs with overlapping IP ranges cannot be peered.
|1. No peering connection needed. All instances added to the CCN instance are in a full mesh interconnection.
2. Each dedicated tunnel can communicate with all VPCs and IDCs.
3. CCN allows for network instances with overlapping CIDR blocks. This provides greater flexibility for interconnection.
|Automatic route learning||
1. Routes must be configured for every link.
2. Manual updates are required for any link change.
1. Routes are automatically learned and forwarded.
2. Route tables are dynamically updated without manual maintenance.
|Greater stability and reliability||Multi-cluster disaster recovery in a single zone.||Multi-zone hot backup disaster recovery with 99.99% high availability.|
1. You pay for each link separately.
2. You pay a higher unit price.
1. You pay for all bandwidth in a region as a whole (similar to bandwidth packages), which evens out the price.
2. Unit price is more competitive.
|Lower latency||Connections are established using lines randomly selected among multiple underlying lines. The latency difference can be 10 ms or more and the latency fluctuates.||Select the optimal line.|