VMware Cloud Community
rscar
Contributor
Contributor

Eth0 module lost after upgrading to v3.5

I recently upgraded from ESX server 3.0 to v3.5. I had no issue with the upgrade. Yesterday I had to change the eth0 from DHCP to Static. On reboot the machine lost eth0. It can no longer find the eth0 device. If you look in the logs, etc you can find that it is losing Module support for eth0. You can find the old module in the previous Kernel but it does not exist in the new kernel that came with v3.5. I downloaded v3.5 from the VMWare website.

When I try to load a new module for the eth0 it says the kernel can not support it.

The machine I am using is an HP DL380 G5. I only have one NIC card installed and two virtual NICs.

Has anyone seen anything like this?

Thanks for the help,

Rachel

Reply
0 Kudos
4 Replies
aguacero
Hot Shot
Hot Shot

Are you referring to the "one nic" as the imbedded nic that comes standard with the server? Did you install a PCI-e NIC card within one of the available slots?

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
Reply
0 Kudos
Exwork
Enthusiast
Enthusiast

Make sure your network card is still on the HCL for 3.5, not everything that worked in 3.0.x will work in 3.5; you may need a firmware update on the NIC.

http://www.vmware.com/pdf/vi35_io_guide.pdf

If you can still see the host via Virtualcenter, look in the network adapters section to see if the NIC changed.

If you only have service console, look at the output of 'esxcfg-nics -l'

Reply
0 Kudos
rscar
Contributor
Contributor

Thanks. I checked the document as you suggested and the hardware is on the

supported list. Good news on that one.

Someone else recommended to ensure I was using the vmware tools (i.e.

esxcfg-vswif) rather than the standard Linux tools.

Thanks again

Reply
0 Kudos
rscar
Contributor
Contributor

Thanks for the help.

Another person suggested the following:

Actually vswif0 is the default that vmware names it.. they create a virtual

interface on top of the physical (eth0) in order to do the virtual switch

stuff.

Basically, don't use the traditional linux tools (ifconfig etc.) use the

vmware tools

Look in /usr/sbin ls -l esxcfg*

  1. esxcfg-vswif -l

Name Port Group IP Address Netmask Broadcast

Enabled DHCP

vswif0 Service Console x.x.x.x 255.255.x.x x.x.x.x true

false

vswif1 Service Console 2 x.x.x.x 255.255.x.x x.x.x.x true

false

FYI...I was usisng the NIC that was on the MotherBoard of the HP itself. So

it was not an additional PCI card.

Thanks again.

Reply
0 Kudos