In a hybrid-cloud environment, you can bind CLB instances to IPs of servers in the local IDC, so as to connect real servers across VPCs and IDCs.
This feature is in beta test. To try it out, for cross-region binding in the Chinese mainland, submit a ticket; for cross-region binding outside the Chinese mainland, contact us.
Benefits
Forward requests to both on-cloud servers and local IDC servers at the same time.
Utilize the public network access capabilities of Tencent Cloud.
Support features of CLB, such as layer-4/7 access, health check, and session persistence.
Set up connections between private networks by using Cloud Connect Network, which supports fine-grained routing and tiered pricing.
Limits
Cross-region binding 2.0 is not available for classic CLBs.
This feature is available only to bill-by-IP accounts. To check your account type, see Checking Account Type.
This feature is not available for CLBs based on the classic network.
This feature is supported on IPv4 and IPv6 NAT64 CLB instances. The IPv6 CLB instance needs to enable the dual-stack mixing binding, which allows the layer-7 listener to bind both IPv4 and IPv6 CVM instances. On this basis, the CLB instance supports cross-region binding 2.0 and hybrid cloud deployment.
Cross-region binding 2.0 and hybrid cloud deployment do not support Allow Traffic by Default in security groups, for which you need to allow the client IP and service port on the real server.
CLB instances cannot be bound with each other in cross-region binding 2.0 and hybrid cloud deployment scenarios.
This feature is only available in Guangzhou, Shanghai, Jinan, Hangzhou, Hefei, Beijing, Tianjin, Chengdu, Chongqing, Hong Kong (China), Singapore and Silicon Valley.
HTTP and HTTPS listeners need to use X-Forwarded-For (XFF) to get the source IP.
UDP listeners cannot get the source IP.
Prerequisites
1. Submit the application to join the beta. For cross-region binding in the Chinese mainland, submit a ticket for application. For cross-region binding outside the Chinese mainland, contact your Tencent Cloud rep.
4. Bind the direct connect gateway associated with the IDC and the target VPC to the created CCN instance. For more information, see Associating Network Instances.
2. On the Instance Management page, click the ID of the target CLB instance.
3. On the Basic Info tab of the Real Server section, click Configure to bind a private IP of another VPC.
4. Click Submit in the pop-up dialog box.
5. On the Basic Info tab of the Real Server section, click Add SNAT IP.
6. In the pop-up dialog box, select Subnet, click Add to assign an IP, and click Save.
Note：
A SNAT IP is mainly used in hybrid cloud deployment where requests are forwarded to IDC servers. It must be assigned when you bind a CLB instance to an IP in the IDC that is interconnected with CNN, and serves as the private IP of your VPC.
A maximum of 10 SNAT IPs can be configured for each CLB instance.
Each CLB instance configures one SNAT IP in one forwarding rule, and supports 55,000 max connections after being bound to one real server. If you configure more SNAT IPs or real servers, the number of connections increases proportionally. Assume that you configure 2 SNAT IPs for the CLB instance and bind 10 ports to the real server, resulting in a maximum of 1.1 million connections (2 x 10 x 55,000). You can calculate how many SNAT IPs to assign based on the number of connections.
Note that deleting a SNAT IP disconnects all connections on the IP.
7. On the instance details page, open the Listener Management tab, and bind a real server to the CLB instance in the listener configuration section. For more information, see Managing Real Servers.
8. In the pop-up dialog box, select Other Private IP, click Add a private IP, and enter the target IDC private IP, port, and weight. Then click Confirm. For more information on ports, see Server Common Port.
9. Now you can view the bound IDC private IP in the Bound Real Servers section.
Yes
No
Was this page helpful?