Physical adapter on ESXi Host will not come up

albevier
albevier used Ask the Experts™
on
OK, after eight hours of screwing around I give -- I have to start asking around and this place seems likely to have some folk who know what they're talking about.
 
Environment: Simple simple setup of a stand alone ESXi v5.5 server, all hardware is approved, including a dual Intel 82574L and three guest VMs. No big deal.
 
Problem: One of the physical adapters on the dual port Intel 82574L, vmnic0, will not come up. It shows up in the vSphere client. I can add or delete the adapter from any vSwitch. I get no error messages as I manipulate or configure this physical adapter. But no matter what I do, the adapter will not come up. The darn thing just sits there taking up space.

The other physical adapter, vmnic1, is up and running just fine on the default vSwitch0. The VMkernel Port is attached to vSwitch0 and the Network Management port is "attached" to vmnic1 at the Direct Console screen. I don't see how VMkernel might play into the problem but figured I'd mention it anyway.

Any thoughts would be appreciated.

The attached is a screen shot of the vSphere client. vSphere Client
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Okay, often the issue with network interfaces is:-

1. firmware in the host.
2. drivers in the host.
3. vendor known issue with the hardware.

Ensure that the firmware you are using for the network interface is the latest, check and check again, and sometimes it maybe required that you update the firmware for the network interface in Windows, and not the DVD/CDROM Firmware CDROM.

Ensure you are using the Vendor OEM edition of ESXi, e.g. if you have a Dell server, download and use from Dell, same with HP, IBM etc

Author

Commented:
lol - yep, I hope that's the issue, Andrew Hancock, I'll give it a try and post back.
I am sure you already have seen this but here is the supported VMware compatibility driver/ firmware  version guide for your NIC...

http://partnerweb.vmware.com/comp_guide2/detail.php?deviceCategory=io&productid=5327
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Commented:
Well this is a bit sad.  The site with the "bad" nic is remote so I rely upon the on-site tech to help with the physical movement of equipment.

When he plugged the "bad" NIC into the network for me, he used the IPMI port on the server instead of the second LAN port. sigh. Well, I suppose I have done worse things in my life but a lot of time wasted trying to figure out a non-existent problem.

Thanks for the two comments.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Umm.

That's what we call in our Team - PEBKAC!

Author

Commented:
The problem was non-existent. The hardware had not been setup correctly.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial