VMware Cloud Community
GuyTC
Enthusiast
Enthusiast
Jump to solution

"No compatible network adapter found" HP Blade VirtualConnect Upgrade to ESXi 5

Hi

I have just upgraded an HP Proliant BL490c G6 from ESXi 4.1.0 to ESXi 5.0 U2. The host has booted up OK but has not found any Nics. The exact error message at the logon on screen is "No compatible network adapter found. Please consult the product's Hardware Compatibility Guide (HCG) for of supported adapters."

The host uses HP Virtual Connect for networking.

As an ESXi 4 host it worked fine.

Using Update Manager 5 it was then upgraded to ESXi 5 using the HP Custom ESX Image (HP-ESX-5.0.2-standard-iso build 914586) , which is when it lost the network adapters.

(A similar upgrade of a BL490c G7 in the same chassis worked fine)

When the Blade was at ESXi version 4.1 the network adapters showed up in the viclient as Broadcom NetXtreme II 57711E/NC532i 10 Gig Ethernet.

A look at Driver Versions in HP supplied VMware ESX/ESXi images http://h18004.www1.hp.com/products/servers/software/vmware-esxi/driver_version.html shows that    net-bnx2 - Version - 2.2.1l.v50.1-1   &   net-bnx2x - Version - 1.72.54.v50.2-1    are both included in the build image.

VirtualConnect firmware is at version 3.15

Can anyone tell me whats gone wrong and how to fix it ?

Cheers

Guy

Reply
0 Kudos
1 Solution

Accepted Solutions
peetz
Leadership
Leadership
Jump to solution

You need to boot the Blade servers with the "HP Service Pack for ProLiant CD" to update the NIC firmware.

Online firmware updates are also possible (through "Smart Components"), but unfortunately not for NICs.

See my HP & VMware Links page for relevant download links.

- Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de

View solution in original post

Reply
0 Kudos
8 Replies
a_nut_in
Expert
Expert
Jump to solution

Check if these drivers help. Please note the 5.1 and 5.0 drivers are the same. So the download page might contain just one image for both versions

cnic version 1.74.04.v50.3

bnx2x version 1.74.22.v50.1

Also check if firmware can be upgraded to

7.4.22

You might have to burn a cd or use ILO should those be the only NIC cards the host has!

http://www.vmware.com/resources/compatibility/detail.php?deviceCategory=io&productid=9402&deviceCate...

Do remember to mark my post as "helpful" or "correct" if I've helped resolve or answer your query!
julianwood
Enthusiast
Enthusiast
Jump to solution

Hi Guy.

Looks like it may be vour Virtual Connect Firmware version.

The HP Flex-10 and Flex-Fabric Supportability list shows you need Adapter Firmware 7.2.54 and Virtual Connect Firmware 3.50 for the bnx2x driver version 1.72.54.v50.2 on ESXi 5.0

http://partnerweb.vmware.com/programs/hcl/ESX_Flex_config.pdf

3.15 is pretty old firmware but then again with it often being an unstable upgrade process, VC firmware upgrades are not normally done until you need to!

Cheers,

Julian

http://WoodITWork.com
peetz
Leadership
Leadership
Jump to solution

According to

http://www.vmware.com/resources/compatibility/detail.php?deviceCategory=io&productid=9404&deviceCate...

you probably need a newer driver (bnx2x 1.74.22) that is available here:

https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESXI5X-BROADCOM-BNX2X-17422V501&productId=...

- Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de
Reply
0 Kudos
GuyTC
Enthusiast
Enthusiast
Jump to solution

VMware Tech Support have come back with the following:

"It appears that the drivers required are:

cnic version 1.74.04.v50.3

bnx2x version 1.74.22.v50.1

And the firmware version required is 7.4.22."

Two further questions:

1. Is the firmware version of 7.4.22 upgraded through HP SUM / SIM ?

and just to be clear...

2. the firmware that is getting upgraded is the Blade's onboard NIC (Mezz card ?)

Thanks

Reply
0 Kudos
a_nut_in
Expert
Expert
Jump to solution

Firmware is upgraded through the HP management console. Firmware is for  the mezzanine card. Thing to keep in mind is HP is choosy regarding BIOS, driver, firmware, flex connect versions etc and have a compatibility matrix that needs to be followed for upgrade.

Best way would be to involve HP during the upgrade process for finer details we might be missing out on :smileysilly:

Do remember to mark my post as "helpful" or "correct" if I've helped resolve or answer your query!
Reply
0 Kudos
peetz
Leadership
Leadership
Jump to solution

You need to boot the Blade servers with the "HP Service Pack for ProLiant CD" to update the NIC firmware.

Online firmware updates are also possible (through "Smart Components"), but unfortunately not for NICs.

See my HP & VMware Links page for relevant download links.

- Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de
Reply
0 Kudos
GuyTC
Enthusiast
Enthusiast
Jump to solution

The fix: Do a clean install on the Blade using the original HP Custom ESXi 5 image.

Details: After the firmware and Virtual Connect were upgraded - Using VUM to do the upgrade process worked only a few times. It didnt matter if i used the HP Custom ESXi 5 Image or an image I had created with newer drivers. The only guaranteed way to get it to install everytime was to install ESXi from scratch and wipe whatever was on the disk (in my case 4.1 U3). Note this only applies to the G6 Blades - all the G7s upgraded first time without problem using VUM and the HP Custom ESXi 5 Image.

Thanks for your help

Guy

Reply
0 Kudos
GuyTC
Enthusiast
Enthusiast
Jump to solution

Andreas - ESXi Customiser is brilliant - thank you !

Reply
0 Kudos