Application Scenario
If the IP addresses of two instances in a VPC are in conflict, or if you want to adjust the VPC network architecture or subnet division during network reconstruction or migration, you may need to modify the Intranet IP addresses of the physical servers or change to another VPC.
Before You Begin
l The physical server is shut down.
l You can only modify the Intranet IP address for the primary NIC. Please delete secondary NICs.
l If the NIC has been bound to a virtual IP address or DNAT rule, unbind their association relationship.
l If the NIC uses an IPv6 address and you cannot modify the Intranet IP addresses (including IPv4 and IPv6). Please delete the IPv6 address.
l To modify the Intranet IP addresses of the elastic load balancing back-end server, remove the back-end server group and then modify the Intranet IP address.
l If the physical server serves as the next hop of a static route, you must delete the static route before modifying the Intranet IP address.
Operation Steps
1. Log in to the console.
2. Click 
in the upper left corner of the console page, and select a region. In this topic, Southwest 1 is selected.
3. Choose Computing and click Physical Server Service to go to the physical server console page.
4. In the physical server list, select the physical server for which you want to change the Intranet IP address or change the VPC. On the physical server details page, click the NIC tab, and click Modify Intranet IP or Change VPC.
5. On the Modify Intranet IP or Change VPC page, enter related parameters and click OK.
Note:
l Modifying Intranet IP will interrupt the physical server network, and at the same time, the physical server subnet, IP address, and MAC address change accordingly.
l Do not operate the EIP or perform other operations on the physical server while modifying Intranet IP.
l After modifying Intranet IP, please check the security group, ACL, and virtual IP address again.
l After modifying Intranet IP, please re-configure network-related services and application software again, such as virtual IP, static routing table, ELB, NAT, and DNS.