Hi there.
Supermicro X7SBi has lost the network (both NICs) after reboot during upgrade from ESXi 5.0U2 to ESXi 5.1 via Update Manager.
Local console displays ESXi 5.1 version and correct IP settings.
After manual reboot host starts responding to ping for about 6 seconds then disappears again.
Has anyone encountered something like that?
Sorry I should have been more clear with that statement.
I have the new X9SCM-F SuperMicro motherboard and an old X7SBi both require the Intel e1000 drivers.
On the X9SCM-F with ESXi versions 5 and 5.1 only one of the two NIC's work, the custom driver is required for the additional NIC to function.
On the X7SBi with ESXi version 5.1 neither of the two NIC's work, the custom driver is required for any NIC to function.
Also I should mention I didn't write or have any involvement making the custom driver, I came across it looking for solutions to my first problem, and it appears to have saved me again.
I'm sure that VMWare will resolve these issues in the future, but I would expect two IT giants like VMWare and Intel should be able to come to the market with working systems off the shelf, it's a little disappointing.
Update.
The same shit happens for the fresh installation of ESXi 5.1.
Two identical hosts with X7SBi MBs has been tested.
I also have the same problem with both NIC's on a X7SBi motherboard with ESXi 5.1, you are not alone.
Running these commands from the command console will replicate a reboot for testing purposes.
esxcfg-module -u e1000e
esxcfg-module e1000e
Problem solved and tested using unofficial driver
Also I haven't tested this but it should work without reinstalling ESX.
From the console:
also refer my blog to install the driver or update the driver in the ESXi
http://pibytes.wordpress.com/2013/02/17/vmware-esxi-network-driver-install-and-upgrade/
Thanks a lot guys!
Does anyone knows if VMware going to fix the issue in the stock image or am I doomed to cook the customized ones for each future release?
It would seem, Intel82573E/L is not the NIC, which is time to retire.
I'm not certain, all I know is I have been using this custom driver for the e1000 since ESXi 5.0 and no VMWare support yet.
What exactly made you switch to the custom driver?
As for me, there were np with the stock one until 5.1.
Sorry I should have been more clear with that statement.
I have the new X9SCM-F SuperMicro motherboard and an old X7SBi both require the Intel e1000 drivers.
On the X9SCM-F with ESXi versions 5 and 5.1 only one of the two NIC's work, the custom driver is required for the additional NIC to function.
On the X7SBi with ESXi version 5.1 neither of the two NIC's work, the custom driver is required for any NIC to function.
Also I should mention I didn't write or have any involvement making the custom driver, I came across it looking for solutions to my first problem, and it appears to have saved me again.
I'm sure that VMWare will resolve these issues in the future, but I would expect two IT giants like VMWare and Intel should be able to come to the market with working systems off the shelf, it's a little disappointing.
So, the reason was that one of the X9SCM-F NICs couldn't work with ESXi 5.0.
That's why you prepared a custom image with the proper custom drivers and installed it on both X9SCM-F and good old X7SBi, right?
And, fortunately, the same custom drivers worked fine with ESXi 5.1 for both MBs, right?
I would say that VMware should pay a little attention to the situation with e1000 (one of the best NICs, so far).
You got it dude