Cross-region Binding v2.0 (New)

Last updated: 2020-11-13 14:05:03

    CLB can be bound to CVM instances in different regions through CCN. You can select multiple regions of real servers for cross-VPC and cross-region binding.
    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.

    Note:

    • Cross-region CVM instance binding is currently not supported for classic CLB.
    • This feature is available only to standard accounts. You can determine the account type as instructed in Checking Account Type.

    Use Cases

    1. This feature can meet the needs in unified cross-region server scenarios for gaming businesses such as P2P. For example, if your real server cluster is deployed in Guangzhou, you can create CLB instances in Shanghai and Beijing and bind them to the same real server cluster in Guangzhou for game acceleration and traffic convergence, effectively ensuring the quality of data transfer and reducing the latency.
    2. This feature can meet the needs in financial business and payment scenarios by effectively ensuring the transfer quality and consistency of data in key businesses.

    Differences from Legacy Cross-region Binding

    Comparison Item Cross-region Binding v2.0 (New) Cross-region Binding v1.0 (Legacy)
    Whether binding to services in multiple regions at the same time is supported Yes:
    • On the new version, a CLB instance can be bound to CVM instances in multiple regions at the same time.
    • For example, a CLB instance in the Beijing region can be bound to CVM instances in the Beijing and Shanghai regions at the same time.
    No:
    • On the legacy version, a CLB instance can be bound to CVM instances in only one region.
    • For example, a CLB instance in the Beijing region can be bound to CVM instances in the Shanghai region but cannot be bound to those in the Beijing and Shanghai regions at the same time.
    Whether intra-region binding can be switched back after cross-region binding is used Yes:
    • On the new version, the original intra-region binding can be switched back after cross-region binding is used.
    No:
    • On the legacy version, after the real server region attribute is modified during cross-region binding, if the new region is different from that of the CLB instance, you cannot change back to the original intra-region binding.
    Supported CLB types Public network CLB and private network CLB. Public network CLB.
    Whether CLB is automatically unbound when a CVM instance is released Automatic unbinding if CVM and CLB are in the same region:
    • If a CLB instance is bound to a CVM instance in the same region, when the CVM instance is released, the CLB instance will be automatically unbound from it.
    Automatic unbinding if CVM and CLB are in different regions:
    • If a CLB instance is bound to a CVM instance in another region, when the CVM instance is released, the CLB instance will not be automatically unbound from it, and you need to unbind them manually.
    Automatic unbinding if CVM and CLB are in the same region:
    • If a CLB instance is bound to a CVM instance in the same region, when the CVM instance is released, the CLB instance will be automatically unbound from it.
    Automatic unbinding if CVM and CLB are in different regions:
    • If a CLB instance is bound to a CVM instance in another region, when the CVM instance is released, the CLB instance will not be automatically unbound from it.
    Whether the price is favorable It is billed in CCN. The costs are controlled in a fine-grained manner, which leads to lower prices. -

    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 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 details page, 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, you can see that "Enable IP Not in Current VPC" is enabled, which indicates that in-cloud IPs can be bound to.
    6. 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.
    7. In the "Bind Real Server" dialog box that pops up, select "Other VPCs", click CVM, select one or multiple CVM instances to be associated with, enter the port and weight, and click OK. For more information, please see Common Server Ports.
    8. Return to the "Bound Real Servers" section and you can view the bound CVM instances in other regions.

    Was this page helpful?

    Was this page helpful?

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