tencent cloud

Feedback

CCN Access: Configuring VPC-IDC Interconnection Through CCN

Last updated: 2022-09-07 14:24:00

    Overview

    CCN can interconnect a VPC with another VPC or a local IDC. To use CCN access, you must establish cross-VPC and VPC-IDC interconnections through CCN in advance.

    In this scenario, you have used CCN to interconnect the three networks of VPC-Guangzhou, VPC-Chengdu, and VPC-Shanghai, have a self-built database in Guangzhou, and plan to migrate the data in the source database in Guangzhou to the target database in Nanjing. VPC-Chengdu is selected as the Accessed VPC.

    Configuration principles

    When selecting CCN access, you need to connect the source database to the source of the DTS migration/sync linkage over CCN as follows: source database > accessed VPC > source of the migration/sync linkage, as shown in orange below.

    The accessed VPC and the source of the migration/sync linkage are interconnected as follows in the entire DTS task:

    • The source of the migration/sync linkage is the network in the region of the source database selected during the task purchase, as shown below:
      The region of the source database selected during task purchase must be the same as the region of the accessed VPC; otherwise, the networks cannot be interconnected, and DTS will change the former to the latter.

    • Accessed VPC: The accessed VPC refers to the VPC in CCN over which the migration/sync linkage is connected. It can be configured when you set the source and target databases as shown below:
      The accessed VPC and the VPC of the source database are interconnected over CCN.

    Directions

    Establish interconnections as instructed in Connecting Network Instances Under the Same Account.

    Note:

    CCN only provides bandwidth below 10 Kbps between all regions free of charge. However, DTS requires a higher bandwidth. Therefore, bandwidth configuration in the link is required.

    Subsequent operations

    1. To perform a data migration task or data sync task, you need to configure relevant parameters. Here, data migration from MySQL is used as an example. In the Set source and target databases step of the data migration task, select CCN and configure key parameters as follows:
      ParameterDescriptionSample Value
      Host AddressIP address of the source database server.172.16.0.0
      Port Port used by the source database. Below are the default ports for common databases (if they are modified, enter the actual ports):
      • MySQL: 3306
      • SQL Server: 1433
      • PostgreSQL: 5432
      • MongoDB: 27017
      • Redis: 6379
      3306
      VPC-based CCN InstanceCCN instance name.ccn6-xxxx7d
      Accessed VPC The accessed VPC refers to the VPC in CCN over which the migration/sync linkage is connected. You need to select a CCN-associated VPC other than the VPC where the source database resides.
      For example, if the database in Guangzhou region is selected as the source database, you should select VPC-Chengdu or VPC-Shanghai as the accessed VPC. Here, Chengdu-VPC is selected.
      VPC-Chengdu
      Subnet Name of the subnet of the selected VPC.
      If you cannot pull the subnet, there may be a problem with your account. The account of the accessed VPC must be the same as the migration account.
      For example, to migrate a database under account A to account B, you should use account B to create a task. Therefore, the accessed VPC must be under account B.
      VPC-Chengdu-Subnet
      Region of Accessed VPCThe region of the source database selected during task purchase must be the same as the region of the accessed VPC; otherwise, DTS will change the former to the latter.Chengdu
    2. Click Test Connectivity. If the test fails, troubleshoot as follows:
    • The Telnet test fails.
      In the CCN-associated VPC (VPC-Chengdu in this example), purchase a CVM instance and ping the source database server address from it:
      • If the address is unpingable:
      • The server where the source database resides has a security group or firewall configured as described in Database Connection Check.
      • The SNAT IP address is blocked in the source database as described in Database Connection Check.
      • The port settings of the source database are incorrect.
      • Some route tables in the CCN instance are not enabled due to IP range conflicts.
      • If the address is pingable, the routing between the source database and CCN is normal.
      • The selected CCN-associated VPC is incorrect.
        The CCN-associated VPC and host address cannot be in the same region (if the network environment of the source database is a VPC in Guangzhou, you cannot select another VPC in Guangzhou as the CCN-associated VPC). The CCN-associated VPC and host address cannot be in the same VPC (if the network environment of the source database is VPC-A, you cannot select VPC-A as the CCN-associated VPC).
      • Submit a ticket for assistance.
    • The Telnet test is passed, but the database connection fails.
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support