Network Switch

Last updated:2026-01-12 17:16:52
Network Switch
Last updated: 2026-01-12 17:16:52
Overview
Tencent Cloud supports classic network and Virtual Private Cloud (VPC) as described in Overview, which are capable of offering a diversity of smooth services. On this basis, we provide more flexible services as shown below to help you manage network connectivity with ease.
Network switch
Switch from classic network to VPC: A single TencentDB source instance can be switched from classic network to VPC.
Switch from VPC A to VPC B: A single TencentDB source instance can be switched from VPC A to VPC B.
Custom IP and port
Custom source instance IP and port: The IP and port of a source instance can be customized on the instance details page in the console.
Custom read-only instance IP and port: The IP and port of a read-only instance can be customized on the instance details page in the console.
Note：
The Cluster Edition instance features one read-write node and up to five read-only nodes. The operations for switching networks and modifying ports are slightly different. For details, see Managing Read-Write Addresses and Managing Read-Only Addresses.
Notes
After the basic network is switched to the Virtual Private Cloud (VPC), cloud products (such as CVMs and databases) under the same VPC are interconnected. Through the configuration of VPC CIDR blocks, the VPC IP address can remain unchanged from the basic network IP address.
The repossession time for the old IP is 24 hours by default and can be up to 168 hours. If "Valid Hours of Old IP" is set to 0 hours, the IP is released immediately after the network is changed.
The switch from classic network to VPC is irreversible. After the switch to a VPC, the TencentDB instance cannot communicate with Tencent Cloud services in other VPCs or classic network.
The network switch of a primary instance doesn't apply to its associated read-only instances or disaster recovery instances, you need to manually switch the network for these instances.
Subnet Description
A subnet is a logical network space in a VPC. You can create subnets in different ​​Availability Zones (AZs) in the same VPC, which communicate with each other over the private network by default.
After you select a network, the subnet IPs in the ​​Availability Zone (AZ) of the selected instance are displayed by default. You can also select subnet IPs in other AZs in the region of the instance. Business connections adopt nearby access, so the network latency will not be increased.
Directions
Switching the network
1. Log in to the TencentDB for MySQL console. In the instance list, click an Instance ID or Manage in the Operation column to enter the instance details page.
2. Click Switch to VPC or Change Network after Network in the Basic Info section.
3. In the pop-up window, select a VPC and a subnet and click OK.
Note: 
If there is no IP address specified, one will be automatically assigned by the system.
You can only select a VPC in the region of the instance, but you can choose a subnet in any AZ and view its IP range.
We recommend that you select a VPC in the region where the CVM instance resides; otherwise, the CVM instance will not be able to access TencentDB for MySQL over the private network, unless a peering connection or a CCN instance is created between the two VPCs.
Switch from classic network to VPC
﻿
Switch from VPC A to VPC B
﻿
4. Return to the instance details page where you can view the network of the instance.
Note:
If the old IP address recycling time is set to 0 hours, the old IP address will be reclaimed immediately after the network switch.
If the old IP address recycling time is set to a non-zero value, the old IP address will be reclaimed after the set duration following a network switch. To release the old IP address in advance, go to the Instance Details page, choose Network Information > Private IP Address, and click Release Original IP Address to perform an immediate release on the target address.
﻿
Switching the RO group network
1. Log in to the TencentDB for MySQL console. In the instance list, click an Instance ID or Manage in the Operation column to enter the instance details page.
2. In the RO Group Info of a read-only instance, click Change Subnet or Switch to VPC according to the network switch type (classic network to VPC or VPC to VPC).
3. In the pop-up window, select a VPC and a subnet and click OK.
Note: 
If there is no IP address specified, one will be automatically assigned by the system.
You can only select a VPC in the region of the instance, but you can choose a subnet in any AZ and view its IP range.
We recommend you select a VPC in the region where the CVM instance resides; otherwise, the CVM instance will not be able to access TencentDB for MySQL over the private network, unless a peering connection or a CCN instance is created between the two VPCs.
4. After the network switch is completed, you can view the network associated with the read-only group on the read-only instance page.
Note:
If the old IP address recycling time is set to 0 hours, the old IP address will be reclaimed immediately after the network switch.
If the old IP address recycling time is set to a non-zero value, the old IP address will be reclaimed after the set duration following a network switch. To release the old IP address in advance, go to the Read-Only Instance page, locate the target read-only group, click Release Original IP Address next to Private IP Address, and then perform an immediate release on the target address.
Customizing the IP and port
1. Log in to the TencentDB for MySQL console. In the instance list, click an Instance ID or Manage in the Operation column to enter the instance details page.
2. Click Edit next to the private network address in the Network Information section.
Note: 
Modifying the private network address and port affects the database business being accessed.
3. In the pop-up window, specify the IP and port and click OK.