Hello CentOS list,
On all of my CentOS 5 VMWare ESX3 virtual machines (about 15), after installing a new kernel and rebooting the machine, the Network script tries to run dhclient and can't determine the IP info (since I don't run a dhcpd server... it's a static IP only lan). This also backs up my ifcfg-eth0 file to ifcfg-eth0.bak and writes a new ifcfg-eth0 that has dhcpd with no IP info. Copying the ifcfg-eth0.bak to ifcfg-eth0 and running /etc/init.d/network start or ifup eth0 brings my network back up.
This is an example of what one of my ifcfg-eth0 files looks like...
# Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] DEVICE=eth0 BROADCAST=69.x.x.x #HWADDR=00:50:56:9C:19:7D IPADDR=69.x.x.x IPV6ADDR= IPV6PREFIX= NETMASK=255.255.255.0 NETWORK=69.x.x.0 ONBOOT=yes
Any ideas?
TIA,
Paul Norton wrote:
On all of my CentOS 5 VMWare ESX3 virtual machines (about 15), after installing a new kernel and rebooting the machine, the Network script tries to run dhclient and can't determine the IP info (since I don't run a dhcpd server... it's a static IP only lan). This also backs up my ifcfg-eth0 file to ifcfg-eth0.bak and writes a new ifcfg-eth0 that has dhcpd with no IP info. Copying the ifcfg-eth0.bak to ifcfg-eth0 and running /etc/init.d/network start or ifup eth0 brings my network back up.
I have found that kudzu does this if it detects changes in the MAC addresses of your NICs. Did you clone/copy your virtual machine and did VMware regenerate MAC addresses for your virtual NICs?
Cheers, Michael
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Michael D. Kralka Sent: Thursday, November 01, 2007 2:12 PM To: CentOS mailing list Subject: Re: [CentOS] Network issue after new kernel install
Paul Norton wrote:
On all of my CentOS 5 VMWare ESX3 virtual machines (about 15), after installing a new kernel and rebooting the machine, the Network script tries to run dhclient and can't determine the IP info (since I don't
run
a dhcpd server... it's a static IP only lan). This also backs up my ifcfg-eth0 file to ifcfg-eth0.bak and writes a new ifcfg-eth0 that has dhcpd with no IP info. Copying the ifcfg-eth0.bak to ifcfg-eth0 and running /etc/init.d/network start or ifup eth0 brings my network back
up.
I have found that kudzu does this if it detects changes in the MAC addresses of your NICs. Did you clone/copy your virtual machine and did VMware regenerate MAC addresses for your virtual NICs?
Cheers, Michael _______________________________________________
I had this as well. I found that if you configured you ifcfg interface script with the MAC address included and uncommented, kudzu no longer manipulated the file.
Michael D. Kralka wrote:
Paul Norton wrote:
On all of my CentOS 5 VMWare ESX3 virtual machines (about 15), after installing a new kernel and rebooting the machine, the Network script tries to run dhclient and can't determine the IP info (since I don't run a dhcpd server... it's a static IP only lan). This also backs up my ifcfg-eth0 file to ifcfg-eth0.bak and writes a new ifcfg-eth0 that has dhcpd with no IP info. Copying the ifcfg-eth0.bak to ifcfg-eth0 and running /etc/init.d/network start or ifup eth0 brings my network back up.
I have found that kudzu does this if it detects changes in the MAC addresses of your NICs. Did you clone/copy your virtual machine and did VMware regenerate MAC addresses for your virtual NICs?
Yes, these are all clones(From one base image). Would I just copy the MAC address given from VMWARE to the ifcfg-eth0 file?
Paul Norton wrote:
Michael D. Kralka wrote:
Paul Norton wrote:
On all of my CentOS 5 VMWare ESX3 virtual machines (about 15), after installing a new kernel and rebooting the machine, the Network script tries to run dhclient and can't determine the IP info (since I don't run a dhcpd server... it's a static IP only lan). This also backs up my ifcfg-eth0 file to ifcfg-eth0.bak and writes a new ifcfg-eth0 that has dhcpd with no IP info. Copying the ifcfg-eth0.bak to ifcfg-eth0 and running /etc/init.d/network start or ifup eth0 brings my network back up.
I have found that kudzu does this if it detects changes in the MAC addresses of your NICs. Did you clone/copy your virtual machine and did VMware regenerate MAC addresses for your virtual NICs?
Yes, these are all clones(From one base image). Would I just copy the MAC address given from VMWARE to the ifcfg-eth0 file?
If you move ifcfg-eth0.bak to ifcfg-eth0 after the first reboot, kudzu will not move it again (since all subsequent reboots will have the new "cloned" MAC address).
I would probably just disable kudzu in the base image, unless you plan on adding/removing hardware in the future.
Cheers, Michael
-
Michael D. Kralka -
Paul Norton -
Scott A. McClanahan