Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am having this issue with many of my CentOS servers where after a reboot the network interface fails to come up automatically. This is a big problem for me since I need to drive to the datacenter every time when this happens as a result from a remote reboot. Then on the console eth0 is down and I have to ifup this manually. Is there a specific config file I can check to prevent this from happening in the future?

share|improve this question
    
One thing to look at is to make sure the designation of NIC device is consistent across reboots. There's like about 3 places you need to look at for this. I don't remember offhand what they are - I've got them written down at my other job, so later I'll take a look and post here. The reason I say this is because I've had this happen before a number of times, and it turned out that the OS was relabeling "eth1" as "eth0" and vice-versa during reboot. ... Annoying! But there's a way to force it to be consistent. –  Michael Martinez Apr 18 at 17:59

2 Answers 2

up vote 5 down vote accepted

Ensure that the file /etc/sysconfig/network-scripts/ifcfg-eth0 has the line

ONBOOT="yes"

See 9.2. Interface Configuration Files for details.

share|improve this answer

Make sure ONBOOT="yes" is set in /etc/sysconfig/network-scripts/ifcfg-eth0 also check that NetworkManager or network (whichever you use) is started on boot.

chkconfig NetworkManager on or chkconfig network on

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.