HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem - General
Showing results for 
Search instead for 
Did you mean: 

VCM Flex-10 Firmware 2.33

David Claussen
Regular Advisor

VCM Flex-10 Firmware 2.33

On the HP site, I see five files that could be firmware v2.33 for the Flex-10 VCM:


None of the pages, that hold these files, specifically list the Flex-10 module - not even under the Flex-10 section does it say "Firmware for the Flex-10 VCM".

Which one do I use?
Honored Contributor

Re: VCM Flex-10 Firmware 2.33


All of those packages include Flex-10 ethernet module firmware. The difference in the packages is firmware for the different fibre channel models.

If you only have Flex-10 modules and no VC FC, just download the smallest one:

David Claussen
Regular Advisor

Re: VCM Flex-10 Firmware 2.33

Thanks for clearing that up!
juan quesada
Respected Contributor

Re: VCM Flex-10 Firmware 2.33


I just updated mine, I used vcfwe1f233.bin.

below the output ...

C:\Program Files (x86)\Hewlett-Packard Company\Virtual Connect Support Utility>v

HP BladeSystem c-Class Virtual Connect Support Utility
Version 1.5.0 (Build 235)
Build Date: May 16 2010 14:25:26
Copyright (C) 2007-2010 Hewlett-Packard Development Company, L.P.
All Rights Reserved

Please enter action ("help" for list): update
Please enter Onboard Administrator IP Address:
Please enter Onboard Administrator Username: JMQR
Please enter Onboard Administrator Password: *************
Please enter firmware package location: c:\vcfwe1f233.bin
Please enter Bay Number (Optional): 1
Please enter Configuration backup password (Optional):
Do you want to force an update on modules? (yes/NO):
Do you want to Specify VC-Enet module activation order? (yes/NO):
Do you want to Specify VC-FC module activation order? (yes/NO):
Do you want to Specify the amount of time(in minutes) to wait between
activating or rebooting VC-Enet modules? (yes/NO): yes
Please enter the time (in minutes)[max 60 mins]: 1
Do you want to Specify the amount of time(in minutes) to wait between
activating or rebooting VC-FC modules? (yes/NO):
Please enter the VCM Domain user credentials.
User Name: JMQR
Password: *************
The following modules will be updated:

Enclosure Bay Module Current Version New Version
2UX01507GN 1 HP VC Flex-10 2.31 2.33
Enet Module 2009-10-23T20:36:20Z 2010-04-17T15:36:24Z

During the update process, modules being updated will be temporarily
unavailable. In addition, the update process should NOT be interrupted by
removing or resetting modules, or by closing the application. Interrupting
the update or the modules being updated may cause the modules to not be updated

Please verify the above report before continuing.

Would you like to continue with this update? [YES/NO]: yes

The following modules were updated successfully:

Enclosure Bay Module New Version
2UX01507GN 1 HP VC Flex-10 Enet Module 2.33 2010-04-17T15:36:24Z

Total execution time: 00:11:52
Press Return/Enter to exit...

Re: VCM Flex-10 Firmware 2.33

Hi all,
Could you confirm that throughout the update you maintained network connectivity?

I currently have v2.12 & would like to stay up to date.

In the past I updated the modules from an older version, but back then it had test Blades & now the chassis has production servers.

Thanks in advance,
The Brit
Honored Contributor

Re: VCM Flex-10 Firmware 2.33

In principle there should not be a connectivity problem, however the failover between VC ENet modules (during the upgrade) takes ~30 secs, which usually upsets someone in the enclosure (especially cluster nodes).

To avoid this, all blades should be configured with Teamed NICS (between horizontal module pairs). If NICs are teamed and the VC configuration is correctly set up, then you should have no problem.

Occasional Advisor

Re: VCM Flex-10 Firmware 2.33

I dropped 3 pings with my update, cost of the failover.