A network configuration problem with the VMware clone function

A network configuration problem with the VMware clone function

Today, we are going to install Hadoop on our own machine. We need a Namenode and two Datanode according to the plan. In this way, we need three nodes. After installing the CentOS 6.5 system on the first node, for convenience, the clone function of VMware is used. However, when the cloned system is enabled, a network configuration error is found, the system network is not correctly configured, and the network service is restarted. The error "no suitable device is found" is reported, 1 and figure 2:

Figure 1

Figure 2

View the configuration information for cloning the new system NIC: cat/etc/udev/rules. d/70-persistent-net.rules

Figure 3

Figure 3 shows that a new Nic is added to the system because VMware assigned a new Nic to the new system during cloning, however, the contents in the NIC's profile ifcfg-eth0 are not updated, so replace hwaddr in the ifcfg-eth0 with the HWADDR corresponding to the NIC (eth1 in the 70-persistent-net.rules file) assigned by VMware for the new system.

Figure 4 (problematic Nic configuration)

Figure 5 (modified Nic configuration)

Restart the network service. The network configuration is successful:

Figure 6

This article permanently updates the link address: