Nic problem after cloning Linux system

Issue: VMware cloned Linux using Ifconfig view without eth0 nic corresponding information environment: centOS6.5 cause Analysis:

During the system boot process, the network card is identified, and the MAC address and network card name are recorded in Udev's rules script, and VMware automatically generates the MAC address of the virtual machine. In this way, because the virtual machine of the basic system has recorded that the virtual machine's network card MAC address corresponds to the NIC Eth0, in the cloned virtual machine due to the MAC address changes, Udev will automatically correspond to the Mac to the NIC Eth1. And so on, Udev will record all the identified Mac and network card name relationship, so each clone network card name will automatically add 1;
Since the network-related configuration of the basic system is based on the NIC Eth0, the NIC Eth1 does not have a network-related configuration, so bind the newly generated MAC address eth0.

Workaround: 1, start the network card, Onboot=yes

/etc/sysconfig/network-scripts/ifcfg-eth0

2, modify the UUID,

1) Delete the MAC address line:

/etc/sysconfig/network-scripts/ifcfg-eth0

2) Delete the eth0 line record of the NIC and Mac bindings and change the newly identified "eth1" to "eth0":

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

3) Rebooting the system

Nic problem after cloning Linux system