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

Prerequisites 7
• To run VCSU, the minimum, required, available free disk space is 600 MB per installation instance. For
example, if you run VCSU three times in parallel against three different enclosures, you must have
approximately 1.8 GB of available disk space.
• When upgrading a Virtual Connect 4Gb FC module from version 1.31 or earlier, you must have
Administrative or Power User privileges on the client system to install and run VCSU.
• A valid HP Virtual Connect firmware package must be available to install. Download the firmware from
the HP website (http://www.hp.com/go/bladesystemupdates). View the BladeSystem for ProLiant
Release Set Compatibility Table and select the appropriate download.
• Do not close the VCSU console application when a firmware update is in progress. If VCSU is closed
before the update completes, the module firmware might not update correctly, 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.
• Ethernet network connectivity between the client system and the enclosure Onboard Administrator is
required. To validate this connectivity, open a web browser to the enclosure Onboard Administrator
before running VCSU.
• Ethernet network connectivity is required between the client system hosting VCSU and the VC
interconnect modules in the enclosure.
• Onboard Administrator firmware v1.30 or higher is required for correct VCSU operation.
• Only one instance of the VCSU accessing a single enclosure can be run on a single client at one time.
Using multiple clients to interface remotely with the same enclosure can interrupt the firmware update
process and prevent it from completing successfully.
• During firmware update operations, the VC modules are unavailable for use. Attempting to reset or
remove the modules during the update process can result in a corrupted firmware image. Do not reset
or update the firmware for the Onboard Administrator of the target enclosure while VC modules are
being updated. These actions can interfere with the firmware update process and cause the update to
fail. During the firmware update process, LAN and SAN connectivity through the VC modules, which
might be hosted to servers in the enclosure, can be interrupted temporarily.
• If VCSU is interrupted or loses network connectivity during the update, reset the affected module and
restart the firmware update process.
• VCSU supports IPv4 addresses, and IPv6 addresses with VC 4.10 and higher
• In a multi-enclosure environment, the Onboard Administrator user name and password must be
identical across the local and remote enclosures in the Virtual Connect domain. Otherwise, firmware
update of the remote enclosures does not succeed.
The following notes apply only when VC 4.01 or earlier versions are installed in the managed enclosures
and servers:
• Add the Virtual Connect Support Utility application to the list of exceptions for any host-based firewall
on the client if you do not have a healthy Backup VC module.
• If you do not have a healthy Backup VC module, no firewalls can exist between the client system and the
remote enclosure Onboard Administrator. If a firewall exists, and it is blocking ports, then VCSU cannot
open a connection with the remote modules to perform the update.