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

General requirements and notes 4
General requirements and notes
• Microsoft® Windows® XP (Service Pack 1 or 2) must be installed on the client.
• Users must have Administrative privileges on the client system to install and run the utility.
• A valid HP Virtual Connect firmware package must be available to install. The firmware can be
downloaded from the HP website (http://www.hp.com
). Click Software and Driver Downloads, and
then search for "Virtual Connect Firmware."
• No FTP servers can be running on the client system. A port conflict can prevent the utility from
performing an update.
• The target enclosure must not be currently imported into a Virtual Connect domain. If so, then the
domain must be deleted before the utility can be used to update the firmware. With the backup and
restore capabilities of VC Manager, users can save a configuration before deleting the domain. If
Virtual Connect firmware version 1.20 or later is already installed on the primary VC-Enet module,
HP recommends using the Virtual Connect Manager embedded firmware update capabilities to
upgrade the firmware to v1.20 or later.
• 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 interconnect
bays must be available for use.
• 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.
• No firewalls can exist between the client system and the remote enclosure Onboard Administrator. If
a firewall exists, and is blocking ports, then the utility can not open a connection with the remote
modules to perform the update.
• Onboard Administrator firmware 1.30 or later is required on the target enclosure. OA firmware
version 2.04 is recommended.
• Only one instance of the VC Support Utility can be run at a time on a single client.
• During firmware update operations, the modules are unavailable for use. The modules should not be
reset or removed during the update process or it could result in a corrupted firmware image. In
addition, the Onboard Administrator of the target enclosure should not be reset, or its firmware
updated, 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 a single client should be used to update modules in a
specific remote enclosure. Using multiple clients to interface to the same enclosure remotely can
interrupt the firmware update process and prevent it from completing successfully.