Manualshelf

HP BladeSystem c-Class Virtual Connect Support Utility Version 1.6.0 User Guide

ManualsBrandsHP ManualsComputer AccessoriesHP Virtual Connect 8Gb 24-port Fibre Channel Module for c-Class BladeSystem
12345678910
Introduction 4
Introduction
Overview
The HP BladeSystem c-Class Virtual Connect Support Utility enables administrators to upgrade VC-Enet and
VC-FC firmware, and to perform other maintenance tasks remotely on both HP BladeSystem c-Class c7000
and c3000 Enclosures using a standalone command line utility.
When the utility initiates a firmware upgrade process, all modules are updated at the same time. The utility
displays a progress message indicating that an update is in progress and the percentage completed. After
the module firmware updates are complete, the utility activates all of the modules.
Using HP-UX
When using HP-UX, use the swinstall command to install the utility.
Example command line:
swinstall -s /tmp/download vcsu
where "/tmp/download" is the local directory that contains the downloaded "vcsu.depot".
Requirements
• A supported operating system must be installed on the client:
o Microsoft Windows XP (Service Pack 1 or 2)
o Windows Vista
o Windows Server 2003, 2008
o HP-UX 11.23 and 11.31
o Linux (Red Hat 4, Red Hat 5, SLES 10, SLES 11)
• To run VCSU, the minimum, required, available free disk space is 600 MB per install instance. For
example, if you run VCSU three times in parallel against three different enclosures, you must have
approximately 1.8GB of available disk space.
• 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/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 properly, causing the module
firmware to be inoperative.