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.

http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay/?javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken&javax.portlet.prp_ba847bafb2a2d782fcbb0710b053ce01=wsrp-navigationalState%3DdocId%253Demr_na-c03708135-2%257CdocLocale%253D%257CcalledBy%253D&javax.portlet.tpst=ba847bafb2a2d782fcbb0710b053ce01&ac.admitted=1373876123412.876444892.492883150

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.