Shulou(Shulou.com)06/02 Report--

After restoring to a snapshot of the new machine, you may encounter problems caused by the MAC address of the network adapter. Typically, when a network adapter changes the operating system, a new network adapter is created for it. You will usually see the network adapter on "eth2" (you can use eth3 if the private network is enabled).

CentOS

Log in to the server through the KVM in the control panel.

Delete / etc/udev/rules.d/70-persistent-net.rules.

Open / etc/sysconfig/network-scripts/ifcfg-eth0, and change the content to the following:

DEVICE=eth0

TYPE=Ethernet

>

NM_CONTROLLED=yes

BOOTPROTO=dhcp

DNS1=8.8.8.8

NAME= "System eth0"

Restart the server

Once you have a network connection again, you can permanently solve these problems by installing cloud-init from EPEL. When the snapshot is restored, the software will be responsible for adjusting your network adapter configuration.

Debian / Ubuntu

Log in to your server through the KVM in the control panel.

Delete / etc/udev/rules.d/70-persistent-net.rules.

Check the contents of / etc/network/interfaces and update any IP addresses to match the current server.

Restart the server

Once you have a network connection again, you can permanently solve these problems by installing the cloud-init package. When the snapshot is restored, the software will be responsible for adjusting your network adapter configuration.

Windows

Windows does not need to be changed. It will automatically start using the new network adapter.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.