Restrictions and limitations – HP Virtual Connect 8Gb 20-port Fibre Channel Module for c-Class BladeSystem User Manual

Page 5

Advertising
background image

Introduction 5

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 console application when a firmware update is in progress. If the application 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. For
Virtual Connect version 4.01 and higher, a user account with Firmware Update (VCSU), Export Support

Files, and Save Domain Configuration role operations assigned to their role permissions is 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 the utility.

Ethernet network connectivity is required between the client system hosting VCSU and the VC
interconnect modules in the enclosure.

For VC 4.01 and lower, 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.

For VC 4.01 and lower, 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 the utility cannot open a connection with the remote modules to perform the update.

Onboard Administrator firmware version 1.30 or higher is required for correct VCSU operation.

Onboard Administrator firmware version 4.00 or higher is required to use IPv6.

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.

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.

VCSU must be run on a management network.

32-bit libraries are required for VCSU to install and run on Linux 64-bit platforms.

Restrictions and limitations

By default, the ftp service is disabled in VC. However, VCSU enables the ftp service for a short time

during the firmware update process to update VC-FC modules.

Advertising