Hey Everyone,
Came across a strange issue today.. We have a DL380G5 which i've just installed two INTEL Quad nics - E1G44ET on a newly installed ESX 3.5 Update 5 box. For some reason the Nics are not showing up.. I've applied all the latest drives/patches and still no luck.. Anyone came across this yet?
try this driver CD...it should work for the ET flavors of Intel...
http://downloads.vmware.com/d/details/esx_35u5_intel_82575_82576_dt/dGViZGolaGJkZXBo
try this driver CD...it should work for the ET flavors of Intel...
http://downloads.vmware.com/d/details/esx_35u5_intel_82575_82576_dt/dGViZGolaGJkZXBo
Ok awesome i'll try it out.. am I suppose to boot into the iso? There's not much info on how to install.
don't boot into the ISO...you need to mount it....similar to this kb article.
http://kb.vmware.com/kb/1009640
I think the drivers you need for this are for the Intel 82576 noted by this kb:
Ok, both links come up as page not found.
i just fixed them...try again
I actually just took a quick look at the hw compatability guide...I do not see the Intel ET quad NICs listed, though I may have missed them. I do see the dual port NICs listed, but not quad...you may want to double check on your end.
I've done the same.. on my end.. What is strange is the Intel site says it's supported and compatible.
The driver that you proved did the trick.. All was required was to extract the .iso and upload it to the /tmp folder of the box and run esxupdate esxupdate command and it applied the patch.. Once the reboot was completed all nics we're showing on the box.. Thanks for your help on this one.
I had this problem on an esx 3.5 box that was updated to 4.0. I was able to get it to work by following the instructions here for ESX 4.0:
After I pushed up the driver from:
http://downloads.vmware.com/d/details/esx40_intel_82580_v4002198_dt/ZHcqYmRwakBiZHdlZQ==
I used the following driver.
VMware ESX/ESXi 4.x Driver CD for Intel 82576 and 82580 Gigabit Ethernet Controller 400.2.1.10.2
Warning: your box needs to be in Maintenance mode and then rebooted.
Using the previous version of the driver didn't help at all.