Hybrid Cloud Deployment

Last updated: 2020-12-18 15:55:07

    In hybrid cloud deployment scenarios, you can directly bind a CLB instance to IPs in the local IDC off the cloud so as to bind it to real servers across VPCs and IDCs.
    This feature is currently in beta test. For cross-region binding in Mainland China, please submit a ticket for application. For cross-region binding outside Mainland China, please contact your Tencent Cloud rep.

    Scheme Advantages

    • A hybrid cloud can be built quickly to seamlessly connect the environments in and off the cloud. CLB can forward requests to CVM instances in the in-cloud VPC and the off-cloud IDC at the same time.
    • The high-quality public network access capabilities of Tencent Cloud can be reused.
    • The rich features of CLB such as layer-4/7 access, health check, and session persistence can be reused.
    • The private networks can be interconnected with each other through CCN, fine-grained routing is supported to guarantee the quality, and diversified tiered pricing is supported to reduce the costs.

    Limits

    • Cross-network CVM instance binding is currently not supported for private network CLB and classic CLB.
    • This feature is available only to standard accounts. You can determine the account type as instructed in Checking Account Type.
    • Currently, this feature is supported only in the Beijing, Shanghai, Guangzhou, Chengdu, Chongqing, and Hong Kong (China) regions.
    • TCP and TCP SSL listeners need to use TOA on the real server to get the source IP. For more information, please see Loading TOA Module.
    • 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. You have submitted the application for beta test eligibility. For cross-region binding in Mainland China, please submit a ticket for application. For cross-region binding outside Mainland China, please contact your Tencent Cloud rep.
    2. You have created a CLB instance. For more information, please see Creating CLB Instances.
    3. You have created a CCN instance. For more information, please see Creating a CCN Instance.
    4. You have associated the Direct Connect gateway associated with the IDC and the target VPC to be bound with the created CCN instance. For more information, please see Associating Network Instances.

    Directions

    1. Log in to the CLB Console.
    2. On the "Instance Management" page in the CLB Console, click the ID of the target CLB instance.
    3. In the "Real Server" section on the "Basic Info" page, click Configure to bind a private IP not in the current VPC.
    4. In the "Enable IP Not in Current VPC" dialog box that pops up, click Submit.
    5. In the "Real Server" section on the "Basic Info" page, click Add SNAT IP.
    6. In the "Add SNAT IP" dialog box that pops up, select "Subnet", click Add to assign an IP, and click Save.
    7. On the instance details page, click the "Listener Management" tab and bind a real server to the CLB instance in the "Configure Listener" section. For more information, please see Adding real server to CLB instance.
    8. In the "Bind Real Server" dialog box that pops up, select "Other Private IPs", click Add Private IP, enter the IDC private IP address to be bound, port, and weight, and click OK. For more information, please see Common Server Ports.
    9. Return to the "Bound Real Servers" section and you can view the bound IDC private IP.

    Was this page helpful?

    Was this page helpful?

    • Not at all
    • Not very helpful
    • Somewhat helpful
    • Very helpful
    • Extremely helpful
    Send Feedback
    Help