VMware Cloud Community
oddWill
Contributor
Contributor

Upgrading 4.1 to 5.5 HP Blade Server, Virtual Connect etc.

Hello Community,

Please help me understand the matrix compatibility with my current setup, all I look up online is blurry and unorganized for me.

Im running BL460C G6 mounted on C7000 enclosure with Virtual Connect - Under one domain, VC Flex-10 Enet Module and HP Virtual Connect 4Gb FC Module.

VC Flex-10 version is 3.70

FC Module version is 1.43


I know BL460C G6 and my CPU are compatible for 5.5 but couldn't find relevant info if VC needs to be upgraded.


Please advice, from your personal experience.

Thanks in advance,

D.

6 Replies
peetz
Leadership
Leadership

Hi,

HP has extensive information about support for and compatibility with VMware vSphere. The key document is their

Current VMware FW and Software Recipe

To say it short take these steps:

1. Upgrade all firmware (OA, VC, blade servers) using there latest ProLiant Supportpack

2. Install the hosts with the current HP Customized ESXi installation ISO (can also be used for updating with Update Manager)

Andreas

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

Hi

Welcome to communities.

As you have already search lot on www then ask to vmware of HP .

Reply
0 Kudos
JPM300
Commander
Commander

I recently did a simular setup the only difference is our Blades are Gen 7/8 Blades.  You can acutally look up each piece in the hardware compatabililty guide

What I check on the HCL guide:

Server & CPU:

Example: HP BL460c Gen 8 Intel Xeon XXXX Series

I/O - Network cards and HBA, since we run the Flex this is all 1 card:

Example: Emulex Corporation HP FlexFabric 10GB 2 port 554FLB Adapter

Storage Compatability (SAN):

Example: HP Lefthand 4530 ect ect

SRM Storage Compatability

Make sure both your SAN's are still on the HCL for 5.5 so you can remain your SRM protection when you upgrade

Between vCenter, ILO on the blades, and the HP c7000 chasiss you should be able to pull alll the information you require.

Hope this has helped

Reply
0 Kudos
oddWill
Contributor
Contributor

Thank you guys for all the input.

I found it all, drivers version, firmware version, blades generation.

The only thing I couldn't find is what virtual-connect version is compatible with 5.5 version.

I mean, we have X enclosures with different VC versions, some 3.61, others 3.70 etc.

Could you please point me to a paper says VC version X is compatibly with 5.5? As simple as that 😉


Thanks

D.

Reply
0 Kudos
peetz
Leadership
Leadership

VMware does not certify "external" network equipment like e.g. switches. And - to an ESXi host running on a blade server - a VC module is nothing else than that.

Just follow HP's recommendations in the cited sources (esp. the VMware FW and software recipe) and update your VC modules with the firmware versions listed there.

The ProLiant Support Pack also includes firmware updates for VC.

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

The Flex module should be compatible with Vmware, its not acutally the module in the chassis that VM cares about its the nic in the hosts.  So the Emulex Mezz card is what Vmware cares about as it needs to have drivers to make it work.  What HP does with that card up the pipe VMware doesn't care as it just see's it as an available NIC.  Your fibre module should be fine as well but double check.

Also the nice thing about the ugprade process is you start with your SSO, Inventory Service, Web Client, and Vcenter then go to the hosts so you can have vCenter at 5.5 managing lower level hosts just fine, then you can migrate one host over and test it prior to pushing the rest.  This allows to you test everything on one host prior to upgrading all the rest to insure everything works nicely.

Hope this has helped