After Clone network configuration
- Jun
- 24
- Posted by TKH Specialist
- Posted in System Administration
The best part about Virtual Environments is the ability to clone new hosts from old ones. Most of our infrastructure resides in vmware, so when we clone a system it retains the old Nic settings. This is how you get the network interface working after cloning the system:
vi /etc/udev/rules.d/70-persistent-net-rules remove eth0 rename eth1 to eth0 save vi /etc/sysconfig/networking/devices/ifcfg-eth0 change the MAC address, IP, netmask make sure ONBOOT=yes If UUID is present, delete it. vi /etc/sysconfig/networking/profiles/default/hosts change the host file definitions vi /etc/sysconfig/network change the HOSTNAME
That is it for configuring the system. Sometimes you will need to run the following commands (I run them as part of the process since they do no harm).
modprobe -r vmxnet3 modprobe vmxnet3
That’s it. I usually reboot the system to clean up anything cached, however you should be able to ifdown/ifup eth0.
Don’t forget to clean up your other configuration files that will have the old system information. Backup definitions, monitoring, etc.
Recent Comments
- Stefan on Flush This!
- Timestamping your Bash History | Matt's Entropy on Remember when you issued that command…?
- Matt Smith on Remember when you issued that command…?
- Ruan on Putting ‘lsof’ to use
- Dylan F. Marquis on External Mapping of LDAP attributes in CAS