Prerequisites
- You can shut down first, and switch to Virtual Private Cloud to operate.
- Before migration, unbind the private/public network LB and Elastic Network Interface by yourself, release the secondary IP of the primary network interface, and then bind them after migration.
- During the migration process, the instance needs to be restarted. Do not perform other operations.
- After migration, check the instance running status, private network access, and remote log-in to see if they are normal.
- Switching from a basic network to a VPC is irreversible. After a CVM is switched to a VPC, CVM cannot communicate with cloud services on other basic networks.
Operation Steps
- Log in to the CVM Console.
- In the instances list, select the instance for which you want to switch the VPC and click More > CVM Configuration > Switching Private Network.
- On the page that pops up, read the precautions carefully and click Next.
- Select the target network and subnet, then click Next.
- Set the pre-allocated IP address and HostName options, and click Next.
Note: If the pre-allocated IP address is empty, the system will automatically allocate one. - Read the precautions carefully, determine whether forced shutdown is required and click OK.
- On the Instances page, the status column will display Modify instance vpc attributes. After the modification is successful, the corresponding configuration will be updated to the latest network information.