Linux network device fails to start problem handling

A CentOS operating system was previously installed to test the Nginx load Balancer, which later was useless. Once a colleague upgraded the VM and recently tried to test the keepalived on it, the service was not connected.

Start looking for reasons, have been silly to change the Ifcfg-eth0 configuration file, restart the network is always prompt

650) this.width=650; "Src=" http://img.blog.csdn.net/20130913113318453?watermark/2/text/ ahr0cdovl2jsb2cuy3nkbi5uzxqvaxv4aw4=/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/dissolve/70/gravity/ Southeast "style=" Border:none; "/>

Unable to find the device eth0, so use the ifconfig-a command to see all the current network devices, found that there is no eth0, but indeed more out of a eth1, the name has changed? No matter how much, re-match it.

So I changed the configuration of the Ifcfg-eth0 directly to change the device to eth1, trying to restart the network, and then something went wrong.

650) this.width=650; "Src=" http://img.blog.csdn.net/20130913113733578?watermark/2/text/ ahr0cdovl2jsb2cuy3nkbi5uzxqvaxv4aw4=/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/dissolve/70/gravity/ Southeast "style=" Border:none; "/>

This time tell me the MAC address is wrong, you have to retrieve Eth1 MAC address.

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

Remember the MAC address of eth1 and re-edit the Ifcfg-eth0 to replace the MAC address inside

Restart Network

Service Network restart

Get!!

Linux network device fails to start problem handling