HP BladeSystem c-Class Virtual Connect Support Utility Version 1.5.0 Release Notes

General requirements 6
General requirements
• Microsoft® Windows® XP (Service Pack 1 or 2), Windows Server® 2003, or Windows Vista®
operating systems must be installed on the client.
• When upgrading from Virtual Connect 4Gb FC module version 1.31 or earlier, users must have
Administrative or Power User privileges on the client system to install and run the utility.
• A valid HP Virtual Connect firmware package must be available to install. Download the firmware
from the HP website (
http://www.hp.com). Click Software and Driver Downloads, and then search
for "Virtual Connect Firmware."
• Do not close the console application when a firmware update is in progress. If the application is
closed before the update completes, the module firmware might not update properly, causing the
module firmware to be inoperative.
• An Onboard Administrator user account with Administrative privileges and access to all Onboard
Administrators and interconnect bays must be available for use. If the enclosure is imported into a
Virtual Connect domain, a Virtual Connect user account with Domain privileges is also required.
• The user must have Ethernet network connectivity between the client system and the enclosure
Onboard Administrator. To validate this connectivity, open a web browser to the enclosure Onboard
Administrator before running the utility.
• The user must have Ethernet network connectivity between the client system and the interconnect
modules in the enclosure.
• Add the Virtual Connect Support Utility application to the list of exceptions for any host-based
firewall on the client.
• No firewalls can exist between the client system and the remote enclosure Onboard Administrator. If
a firewall exists, and it is blocking ports, then the utility cannot open a connection with the remote
modules to perform the update.
• Onboard Administrator firmware v1.30 or higher is required for correct VCSU operation.
• Only one instance of the VC Support Utility accessing a single enclosure can be run on a single
client at one time.
• During firmware update operations, the modules are unavailable for use. Any attempt to reset or
remove the modules during the update process could result in a corrupted firmware image. In
addition, do not reset the Onboard Administrator of the target enclosure or update its firmware while
VC modules are being updated. Doing so can interfere with the firmware update process and cause
it to fail. During the firmware update process, connectivity through the modules, which might be
hosted to servers in the enclosure, can be interrupted temporarily.
• During a firmware update session, only use a single client to update modules in a specific remote
enclosure. Using multiple clients to interface remotely with the same enclosure can interrupt the
firmware update process and prevent it from completing successfully.
• If the firmware update client is interrupted or loses network connectivity during the update, reset the
affected module and restart the firmware update process.