Home > Flex-10, HP > HP Virtual Connect Firmware upgrade may cause Server Profiles to be unassigned causing a network outage

HP Virtual Connect Firmware upgrade may cause Server Profiles to be unassigned causing a network outage

July 25th, 2013

HP has released a serious advisory that upgrading certain Virtual Connect firmware may cause server profiles to be unassigned which will cause a a network outage for your blades.


The issue occurs when you have both single dense and double dense servers in your chassis and you are upgrading from Virtual Connect firmwares 3.10-3.60 up to Virtual Connect firmwares 3.70-3.75.

The upgrade process will complete successfully however the single dense server profiles will become unassigned which will cause a network outage for those specific server blades.

In order to fix this you will need to power down the affected blades, reassign the server profiles and power on the blades again! Ouch!

This doesn’t affect you if you are upgrading  from Virtual Connect firmware 3.70 to later firmware or going from Virtual Connect firmware 3.10 to anything below 3.70 such as 3.60 and won’t affect you if you only have single dense servers or double dense servers but not a mixture.

Virtual Connect firmware 4.01 which has been recently released fixes this but has a whole raft of new features that you may not be ready to implement so its worth being aware of this issue.

Categories: Flex-10, HP Tags: , , ,
  1. July 26th, 2013 at 03:50 | #1

    HP just can’t seem to get VC firmware right after all these years. *Shakes head*

  2. user84203
    July 26th, 2013 at 08:30 | #2

    Full ACK…it’s very annoying. Since Years we have several Problems with HP Software and Hardware. Newest VC phenomenon after the latest FW-Update are duplicate WWNs in some of our server profiles (BL870) which ends in a loss of the SAN Connection. It seems that HP’s product cycle is to short…customers don’t get finished products anymore.

  3. Marcel koedijk
    October 4th, 2014 at 18:01 | #3

    is fixed in vc 4.30

    Was a very buggy bug in my eyes. Even a oa failover could trigger it, bleh!

  4. Farris
    October 14th, 2014 at 23:31 | #4

    I am in this unfortunate situation. I am at VC v3.15 and need to get to 4.30. I spoke with HP who informed me that I could safely go from 3.15 to 3.70, then from 3.7 to 4.xx. I was still nervous about the procedure but now this article had freaked me out. Am I reading this correctly, there is no way to go from VC 3.60 to 3.7x without the host profiles losing their assignment?? If you know of a way, please tell me the exact steps.

  1. No trackbacks yet.
Comments are closed.