So, as you may know, HP has released new versions of their chassis firmware, this includes release 4.10 of the Virtual Connect (VC) firmware and release 4.01 of the Onboard Administrator (OA). The OA upgrade is fairly trivial, and can be done by navigating to your HP OA website and telling it to update itself, see the screen shot.
The VC upgrade is a little more complex, and needs to have the Virtual Connect Support Utility (VCSU) installed before you can upgrade. This utility comes in Windows and Linux versions, but finding the latest version on the HP website is not trivial (I am embarrassed to say it took me an hour). I thought the links might be useful to others, so here goes:
Windows VCSU utility, version 1.8, which is required to implement VC 4.01+:
Linux VCSU utility, version 1.8, for those not running Windows:
VC version 4.10 firmware, released September 2013:
OA version 4.01 firmware, released September 2013:
VC release notes, in case you want to read the documentation:
Note that you can get yourself into a bind if you attempt to upgrade the VC modules from a guest virtual machine inside the blade chassis. Basically, you are updating the networking components, which might bring network connectivity to your guest down long enough to hang the upgrade process. It happened to me once when upgrading to VC 3.75, which I why I mention it.
So, I recommend that you install the VCSU utility on a machine outside the chassis you are upgrading, but with fast network connectivity to that chassis. I have targeted installing VCSU on the physical syslog server which runs Red Hat Linux.