HP BladeSystem c-Class Virtual Connect Support Utility Version 1.5.

2 User Guide

Part Number 642067-001 December 2010 (First Edition)

 Copyright 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendors standard commercial license. Microsoft, Windows, Windows Server, and Windows Vista are U.S. registered trademarks of Microsoft Corporation.

Intended audience This document is for the person who installs, administers, and troubleshoots servers and storage systems. HP assumes you are qualified in the servicing of computer equipment and trained in recognizing hazards in products with hazardous energy levels.

Contents
Introduction .................................................................................................................................. 4
Overview ................................................................................................................................................. 4 Using HP-UX ................................................................................................................................... 4 Requirements ............................................................................................................................................ 4 Restrictions and limitations .......................................................................................................................... 5 Command line syntax ................................................................................................................................ 5 Usage ...................................................................................................................................................... 6 Password masking ..................................................................................................................................... 7 Interactive mode........................................................................................................................................ 7 Questions ....................................................................................................................................... 7

Commands ................................................................................................................................ 10
collect .................................................................................................................................................... 10 discover ................................................................................................................................................. 10 configbackup .......................................................................................................................................... 11 healthcheck ............................................................................................................................................ 11 packageinfo ........................................................................................................................................... 12 report .................................................................................................................................................... 13 resetvcm................................................................................................................................................. 13 supportdump .......................................................................................................................................... 14 update ................................................................................................................................................... 14 version ................................................................................................................................................... 16 Error messages ....................................................................................................................................... 18 Before you contact HP.............................................................................................................................. 20 HP contact information ............................................................................................................................. 20

Troubleshooting .......................................................................................................................... 18 Technical support ........................................................................................................................ 20

Acronyms and abbreviations ........................................................................................................ 21

Contents

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 o o o o

Microsoft Windows XP (Service Pack 1 or 2) Microsoft Windows Vista Microsoft Windows Server 2003, 2008 HP-UX 11.23 and 11.31 Linux (Red Hat 4, Red Hat 5, SLES 10, SLES 11)

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.

Introduction

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 if you do not have a healthy Backup VCM module. No firewalls can exist between the client system and the remote enclosure Onboard Administrator if you do not have a healthy Backup VCM module. 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.

Restrictions and limitations

This version of VCSU supports c3000 and c7000 enclosures. The utility does not update modules that are not physically present, are powered off, or are nonfunctional. A status message indicates if any modules are in these states. The utility does not update unknown or unsupported module types, including pass-thru Ethernet and FC modules. HTTP and HTTPS downloads are restricted to non-authenticated websites. FTP downloads are restricted to non-SSL/TLS, Passive Transfer Mode FTP sites. Any IP addresses that are not accessible timeout within 20 seconds. Any IP addresses that have an active SSL enabled web server, but not an OA, fail immediately. Only IPv4 addresses are supported in this release.

Command line syntax

CLI input is case-insensitive except when otherwise noted. The general CLI syntax is as follows: vcsu -a <command>

Introduction

Parameters are extensions that provide extra information required for the execution of a particular command. Whether or not a parameter is required depends on the specific action being executed. For example, the version command includes parameters for IP address, username, password, and bay location. The syntax is as follows: vcsu -a version -i <IP> -u <USER> -p <PWD> [-b <BAY>] NOTE: When entering a username from a Linux command shell with the domain\username format, use quotation marks around the username ("domain\username") so it is not expanded by the Linux shell. To display a single module and its current firmware version, enter the following: vcsu -a version -i 192.168.1.100 -u Administrator -p password -b 1

Usage
To install and run the HP BladeSystem c-Class Virtual Connect Support Utility:
1. 2.

Install the application on the client system by running the MSI file. After the program is installed, click Start>Programs>Hewlett-Packard>Virtual Connect Support Utility to start a console.
o o o o o o o o o o o o

To start the Virtual Connect Support Utility in interactive mode, enter vcsu. To display the top-level help and available options, enter vcsu -a. To display version syntax and available options, enter vcsu -a version. To display report syntax and available options, enter vcsu -a report. To display update syntax and available options, enter vcsu -a update. To display discover syntax and available options, enter vcsu -a discover. To display collect syntax and available options, enter vcsu -a collect. To display configbackup syntax and available options, enter vcsu -a configbackup. To display supportdump syntax and available options, enter vcsu -a supportdump. To display healthcheck syntax and available options, enter vcsu -a healthcheck. To display packageinfo syntax and available options, enter vcsu -a packageinfo. To display resetvcm syntax and available options, enter vcsu -a resetvcm.

3. 4.

Download a valid Virtual Connect firmware package file from the HP website (http://www.hp.com/go/bladesystemupdates), and then save it to your local file system. Enter the version command to display all of the modules in the enclosure and ensure that the required connectivity exists between the utility and the remote enclosure. Non-VC modules are shown as Unknown or unsupported module. Version information appears for supported VC modules only.

5.

Enter the report command to display all modules in the target enclosure and which modules can be updated. The report command also displays the firmware package file contents and versions. To use the report command, a valid firmware package must be available on the local file system or supported remote server. Non-VC modules are shown as Unknown or unsupported module. Detailed information appears for supported VC modules only.

Introduction

6.

Enter the update command to update the firmware on supported VC-Enet and VC-FC modules in the enclosure. The update process takes approximately 20 minutes for VC-Enet modules, and 5 minutes for VC-FC modules. These updates are performed simultaneously. The utility only updates supported VC modules that are able to be updated and require an update.

Password masking
For all of the commands provided by VCSU, the user name, password, and IP address of the enclosure OA must be provided. In some cases, the VC domain user name and password must also be specified. VCSU enables the user to enter the password interactively with password masking, primarily for security reasons. To do this, enter the password as *. A prompt is provided that masks the input. Example: vcsu -a version -i 192.168.1.100 -u Administrator -p * OA Password :*********** From a Linux command shell, use quotation marks around the asterisk so it is not expanded by the Linux shell. Example: vcsu -a version -i 192.168.1.100 -u Administrator -p "*" OA Password :***********

Interactive mode
VCSU enters interactive mode when invoked without any parameters. Users are prompted to enter missing command line parameters. Example: No command line parameters given. Starting interactive mode. Please enter action ("help" for list): healthcheck Please enter Onboard Administrator IP Address: 192.168.1.100 Please enter Onboard Administrator Username: Administrator Please enter Onboard Administrator Password: ********

Questions
The following table provides information on interactive mode questions and requests for input. Interactive mode question/request
Please enter action ("help\" for list):

Description

Reference

Please enter action:

(required) Enter a command, or enter Commands (on page 10) help for a list of available commands. -a <command> Commands (on page 10) (required) Asked if help was entered for previous question. Enter a command. -a <command> (required for all commands except discover and packageinfo) IP Commands (on page 10) -i <IP>

Please enter Onboard Administrator IP Address:

Introduction

Interactive mode question/request

Description
address of the active OA in the primary enclosure

Reference

Please enter Onboard Administrator Username:

(required for all commands except Commands (on page 10) discover and packageinfo) User -u <USER> name of the active OA in the primary enclosure (required for all commands except discover and packageinfo) Password of the active OA in the primary enclosure (required) First IP address in the range to search (required) Ending IP address in the range to search (required) Full path to the Virtual Connect package on the local computer Commands (on page 10) -p <PWD>

Please enter Onboard Administrator Password:

Please enter starting IP address: Please enter ending address: Please enter firmware package location:

discover -s <START IP> discover -s <END IP> packageinfo report update (on page 14) -l <FILE>

Please enter Bay Number:

(optional) Bay number of the target report module. If not specified, the default is resetvcm all supported modules. update (on page 14) version -b <BAY> (optional) Full path to the configuration backup or support dump file (optional) Password for the configuration backup file configbackup (on page 11) supportdump -l <FILE> configbackup (on page 11) update (on page 14) -cp <CONFIG PASS>

Please enter the file location: Please enter the Configuration backup password:

Do you want to force an update on modules? (yes/no):

(optional) Enter Yes to force an update on modules.

update (on page 14) -f <FORCE>

Please enter Force Update options (eg: version,health):

Required only if previous question was answered yes. Enter options separated by a comma.

update (on page 14) -f <FORCE>

Introduction

Interactive mode question/request

Do you want to specify VCEnet module activation order? (yes/no):

Description
(optional) Specify VC-Enet module activation order

Reference
update (on page 14) -oe <ORDER>

Please enter VC-Enet module activation order (eg: parallel or odd-even or serial or manual):

Required only if previous question was answered yes. Enter one of the following: parallel, odd-even, serial, or manual

update (on page 14) -oe <ORDER>

Do you want to specify VC-FC module activation order? (yes/no):

(optional) Specify VC-FC module activation order.

update (on page 14) -of <ORDER>

Please enter VC-FC module activation odrer (eg: parallel or odd-even or serial or manual):

Required only if previous question was answered yes. Enter one of the following: parallel, odd-even, serial, or manual

update (on page 14) -of <ORDER>

Do you want to specify the amount of time (in minutes) to wait between activating or rebooting VC-Enet modules? (yes/no): Please enter the time (in minutes) [max 60 mins]:

(optional) Specify the amount of time, update (on page 14) in minutes, to wait between -we <MINUTES> activating or rebooting VC-Enet modules.

Required only if previous question was answered yes. Enter the time in minutes (maximum of 60 minutes).

update (on page 14) -we <MINUTES>

Do you want to specify the amount of time (in minutes) to wait between activating or rebooting VC-FC modules? (yes/no): Please enter the time (in minutes) [max 60 mins]:

(optional) Specify the amount of time, update (on page 14) in minutes, to wait between -wf <MINUTES> activating or rebooting VC-FC modules.

Only required if previous question was answered yes. Enter the time in minutes (maximum of 60 minutes).

update (on page 14) -wf <MINUTES>

Introduction

Commands
collect
Contact the OA using the supplied credentials and execute a SHOW ALL from the OA CLI, saving the output to an "oaShowAll.txt" file in the current directory. This support action also contacts the primary VC Manager using the supplied credentials and executes the following commands, saving the output to a "vcmShowAll.txt" file:

Item

show enclosure * show domain show network * show fabric * show profile * show stackinglink show interconnect * show firmware Description
vcsu -a collect -i <IP> -u <USER> -p <PWD> -vcu <VCM USER> -vcp <VCM PASS> IP address of the active OA in the enclosure* Name of the OA user with privileges to access all enclosure interconnect bays. Minimum length is 3 characters. Password of the OA user. Minimum length is 3 characters. Name of Virtual Connect user with Domain privileges. Required if an enclosure is in a Virtual Connect domain. Minimum length is 3 characters. Password for the Virtual Connect user. Minimum length is 3 characters.

Syntax Parameters: IP USER PWD VCM USER VCM PASS

*In a multi-enclosure environment, this must be the IP address of the active OA in the primary enclosure.

Example Collect configuration information from the OA and VC Manager: vcsu -a collect -i 192.168.0.100 -u Administrator -p password -vcu Administrator -vcp password

discover
Locate remote OA enclosures that exist on the network within a specified address range.

Commands

10

This command is useful if an Administrator cannot remember the exact IP address of the OA on a certain enclosure, but knows the general IP address range. Item
Syntax Parameters: START IP END IP First IP address in the range to search Last IP address in the range to search

Description
vcsu -a discover -s <START IP> -e <END IP>

Example Discover an enclosure in a certain address range: vcsu -a discover -s 192.168.1.100 -e 192.168.1.200

configbackup
Using the supplied credentials, log into VC Manager and access Virtual Connect to request a configuration download. VCSU saves that backup in the current directory as the file name supplied by Virtual Connect. A functioning VC Manager domain is required for this action. Item
Syntax Parameters: IP USER PWD VCM USER VCM PASS IP address of the active OA in the enclosure* Name of the OA user with privileges to access all enclosure interconnect bays. Minimum length is 3 characters. Password of the OA user. Minimum length is 3 characters. Name of the Virtual Connect user with Domain privileges. Required if an enclosure is in a Virtual Connect domain. Minimum length is 3 characters. Password for the Virtual Connect user. Minimum length is 3 characters.

Description
vcsu -a configbackup -i <IP> -u <USER> -p <PWD> -vcu <VCM USER> vcp <VCM PASS> [-cp <CONFIG PASS>] -l <LOCATION>

CONFIG PASS Optional. Password for the configuration backup file. Supported only for VCM versions 3.00 and higher. The default is no password. LOCATION Full path, including file name, to save the configuration backup file. If not provided, VCSU saves the configuration backup file to the file name that VCM provides and downloads it to the current directory.

*In a multi-enclosure environment, this must be the IP address of the active OA in the primary enclosure.

Example Request a configuration download from Virtual Connect: vcsu -a configbackup -i 192.168.0.100 -u Administrator -p password -vcu Administrator -vcp password

healthcheck
List the state of modules in the enclosure. This command is useful if an Administrator needs to know if performing an action, such as a failover or a VC Manager or OA firmware upgrade, would cause an outage.

Commands

11

On an enclosure configured for Virtual Connect, the command displays the following:

Onboard Administrator firmware version Power: On, Off, other Health: OK, Degraded, Failed, other IP Address Connectivity Test For VC-Enet Modules:
o o o

VCM Mode: Primary, Backup, Subordinate, Unintegrated Module Configuration: In Sync, Not In Sync, Invalid Domain Configuration (for primary or backup VC-Enet modules): In Sync, Not In Sync

The primary Virtual Connect manager saves the domain configuration data to the backup module in a VC domain at a regular interval. The 'Domain configuration' state indicates whether or not this data is in sync between the two modules. The 'Module configuration' state indicates whether all the modules in an enclosure are in sync with the primary module regarding the Virtual Connect configuration information. If a module is being reconfigured by Virtual Connect, or is rebooting, a 'Not In Sync' or 'Invalid' configuration status might appear. Wait up to 2 minutes, and then execute the healthcheck command again. Item
Syntax Parameters: IP USER PWD IP address of the active OA in the enclosure* Name of the OA user with privileges to access all enclosure interconnect bays. Minimum length is 3 characters. Password of the OA user. Minimum length is 3 characters.

Description
vcsu -a healthcheck -i <IP> -u <USER> -p <PWD>

*In a multi-enclosure environment, this must be the IP address of the active OA in the primary enclosure.

Example List the state of modules in an enclosure: vcsu -a healthcheck -i 192.168.0.100 -u Administrator -p password

packageinfo
Extract the package information from the supplied package path and display the following information:

Digital Signature Validation (for Virtual Connect firmware version 2.30 and higher) Package Version Ethernet Firmware Version Timestamp Ethernet Firmware Supported Hardware FC Firmware Version FC Firmware Supported Hardware

Commands

12


Item

Release Notes (extract, not display) Description

vcsu -a packageinfo -l <FILE> Full path to the Virtual Connect package on the local computer or supported remote server

Syntax Parameter: FILE

Example Display package information from a file named VCpackage: vcsu -a packageinfo -l VCpackage

report
Display the current running firmware version on all modules in a specific target enclosure. Also display the VC-Enet and VC-FC firmware versions provided in the specified VC package file, and whether or not the module can be updated. In addition to displaying the module firmware version and status, the report command also displays details about the VC package contents. Because the package version details appear, the user must provide a VC package file as part of the input at the command line. Item
Syntax Parameters: IP USER PWD FILE BAY IP address of the active OA in the enclosure* Name of the OA user with privileges to access all enclosure interconnect bays. Minimum length is 3 characters. Password of the OA user. Minimum length is 3 characters. Full path to the Virtual Connect package on the local computer or supported remote server Optional. The bay number of the target module. If not specified, the default is all supported modules.

Description
vcsu -a report -i <IP> -u <USER> -p <PWD> -l <FILE> [-b <BAY>]

*In a multi-enclosure environment, this must be the IP address of the active OA in the primary enclosure.

Examples Display all modules in an enclosure: vcsu -a report -i 192.168.1.100 -u Administrator -p password -l VCpackage Display a single module in an enclosure: vcsu -a report -i 192.168.1.100 -u Administrator -p password -1 VCpackage -b 2

resetvcm
Log into the specified interconnect bay and restart the Virtual Connect Manager service. This is the same process as the menu option "Reset VC Manager" from the Virtual Connect user interface.

Commands

13

Item
Syntax Parameters: IP USER PWD

Description
vcsu -a resetvcm -i <IP> -u <USER> -p <PWD> IP address of the active OA in the enclosure* Name of the OA user with privileges to access all enclosure interconnect bays. Minimum length is 3 characters. Password of the OA user. Minimum length is 3 characters.

*In a multi-enclosure environment, this must be the IP address of the active OA in the primary enclosure.

Example Reset a single module in an enclosure: vcsu -a resetvcm -i 192.168.0.100 -u Administrator -p password -b 1

supportdump
Log into VC Manager using the supplied credentials and access Virtual Connect to request a support information (debug dump) download. VCSU saves that file in the current directory as the file name supplied by Virtual Connect. A functioning VC Manager domain is required for this action. Item
Syntax Parameters: IP USER PWD VCM USER VCM PASS LOCATION IP address of the active OA in the enclosure* Name of the OA user with privileges to access all enclosure interconnect bays. Minimum length is 3 characters. Password of the OA user. Minimum length is 3 characters. Name of Virtual Connect user with Domain privileges. Required if an enclosure is in a Virtual Connect domain. Minimum length is 3 characters. Password for the Virtual Connect user. Minimum length is 3 characters. Full path, including file name, to save the support dump file. If not provided, VCSU saves the support dump file to the file name that VCM provides and downloads it to the current directory.

Description
vcsu -a supportdump -i <IP> -u <USER> -p <PWD> -vcu <VCM USER> -vcp <VCM PASS> -l <LOCATION>

*In a multi-enclosure environment, this must be the IP address of the active OA in the primary enclosure.

Example Save support information: vcsu -a supportdump -i 192.168.0.100 -u Administrator -p password -vcu Administrator -vcp password

update
Update the firmware. The user must provide the primary OA IP address, user credentials, and the package file to use for the update. The user can also provide an optional bay number.

Commands

14

The user can also force an update of modules in the following circumstances:

Item

The target module contains a running firmware image that is the same version as the one in the source package. The target module contains a running firmware image that is newer than the version in the source package. The target module is in a degraded or failed state. Description
vcsu -a update -i <IP> -u <USER> -p <PWD> -l <FILE> [-b <BAY>] [-f <FORCE>] -vcu <VCM USER> -vcp <VCM PASS> [-q] [-oe <ORDER>] [-of <ORDER>] [-we <MINUTES>] [-wf <MINUTES>] [-cp <CONFIG PASS>] IP address of the active OA in the enclosure* Name of the OA user with privileges to access all enclosure interconnect bays. Minimum length is 3 characters. Password of the OA user. Minimum length is 3 characters. Full path to the Virtual Connect package on the local computer or supported remote server Optional. The bay number of the target module. If not specified, the default is all supported modules. The BAY parameter is supported only for single-enclosure Virtual Connect domains and for enclosures that are not in a Virtual Connect domain. Enclosures in a MultiEnclosure Domain have all modules updated regardless of the BAY parameter. Optional. Comma-separated list of force operations under certain conditions:

Syntax

Parameters: IP USER PWD FILE BAY

FORCE

versionAllows an update of the same or older firmware versions. healthAllows an update on a module with failed or degraded health.

VCM USER VCM PASS -q -oe

Name of the Virtual Connect user with Domain privileges. This command is required if an enclosure is in a Virtual Connect domain. Minimum length is 3 characters. Password for the Virtual Connect user. Minimum length is 3 characters. Optional. Specifies that the firmware update does not prompt for confirmation before updating, and uses the default answer for the confirmation (YES). Optional. Specifies VC-Enet module activation order. The following activation order methods are supported:

parallelAll modules are activated at the same time.

odd-even(Default) All modules on the backup VCM side are activated first, then all modules on the primary VCM side except the primary VCM, then the primary VCM itself. serialModules are activated one at a time, starting with the highest numbered bay. manualModules are updated but not activated. Use the VC Manager GUI or OA GUI to activate (reboot) modules.

-of

Optional. Specifies VC-FC module activation order. The following activation order methods are supported:

parallelAll modules are activated at the same time.

odd-evenAll modules in odd-numbered bays are activated first, and then modules in even-numbered bays are activated. serial(Default) Modules are activated one at a time, starting with the highest numbered bay. manualModules are updated but not activated. Use the OA GUI to activate (reboot) modules.

Commands

15

Item
-we

Description
Optional. Specifies the amount of time, in minutes, to wait between activating or rebooting VC-Enet modules. This command is required for some MPIO/teaming software on the server blades in the enclosure. The default is 0, or no delay. Optional. Specifies the amount of time, in minutes, to wait between activating or rebooting VC-FC modules. This command is required for some MPIO/teaming software on the server blades in the enclosure. The default is 0, or no delay. Optional. Password for the configuration backup file. Supported in VCM firmware versions 3.00 and higher. The default is no password.

-wf

-cp

*In a multi-enclosure environment, this must be the IP address of the active OA in the primary enclosure.

Examples Update multiple modules in an enclosure imported into a VC domain: vcsu -a update -i 192.168.1.100 -u Administrator -p password -vcu John vcp vcPass -l C:\images\vcfw-120.bin Update a single module in an enclosure not imported into a VC domain: vcsu -a update -i 192.168.1.100 -u Administrator -p password -l vcfw121.bin -b 3 Update a single module in an enclosure managed by the VC domain: vcsu -a update -i 192.168.1.100 -u Administrator -p password -vcu John vcp vcPass -l C:\images\vcfw-120.bin -b 3 Perform an update and specify an activation ordering method: vcsu -a update -i 192.168.1.100 -u Administrator -p password -vcu John vcp vcPass -l C:\images\vcfw-120.bin -oe serial -of parallel Perform an update using a firmware image from a web server address: vcsu a update i 192.168.1.100 u Administrator p password l http://www.myserver.com/vcfw-120.bin Perform an update using a firmware image from an FTP server on the network: vcsu a update i 192.168.1.100 u Administrator p password l ftp://user:password@192.168.1.10/vcfw-120.bin Perform an update of the same firmware version on a degraded module: vcsu -a update -i 192.168.1.100 -u Administrator -p password -l C:\images\vcfc-120.bin -f version,health

version
Display the current running firmware version on all modules in a specific target enclosure. Item
Syntax Parameters: IP USER PWD BAY IP address of the active OA in the enclosure* Name of the OA user with privileges to access all enclosure interconnect bays. Minimum length is 3 characters. Password of the OA user. Minimum length is 3 characters. Optional. The bay number of the target module. If not specified, the default is all supported

Description
vcsu -a version -i <IP> -u <USER> -p <PWD> [-b <BAY>]

Commands

16

Item

Description
modules.

*In a multi-enclosure environment, this must be the IP address of the active OA in the primary enclosure.

Examples Display all modules and their current firmware versions: vcsu -a version -i 192.168.1.100 -u Administrator -p password Display a single module and its current firmware version: vcsu -a version -i 192.168.1.100 -u Administrator -p password -b 1

Commands

17

Troubleshooting
Error messages
Error message
This version of the application does not support the target enclosure Invalid bay number x for an enclosure Unable to get enclosure part number

Resolution
Specify a supported enclosure type. Specify a valid bay number. Check connectivity with the OA, and then restart the update process.

Another instance of this application is running. More than one instance of the update utility is attempting Please wait until all other instances are completed to run on the client. Wait until all other instances are and try again. complete, and then try again. Unable to initialize Onboard Administrator interface Unable to login to the Onboard Administrator. Please confirm the OA IP address and user credentials. Invalid option Invalid -a option One or more parameters missing Missing -l option Invalid -f option Invalid OA IP address Unable to communicate with OA IP aaa.bbb.ccc.ddd OA username is longer than 40 characters OA user password is greater than 40 characters Invalid bay number OA firmware version a.bb is not supported Check connectivity with the OA, and then restart the update process. Confirm the OA IP address and user credentials.

An invalid option has been specified by the user. Verify the list of available options for that command. An invalid -a format has been specified by the user. Verify the list of available commands. One or more required parameters was not specified. See the required syntax for the command. Specify the required package location. The -f version option can only be used with the update command. Be sure a valid -f option is specified. Provide a valid IP address in the proper format. Check connectivity with the OA and verify that you are using a valid IP address. Enter a valid OA username. Enter a valid OA user password. Specify a valid bay number for the target enclosure. Update the firmware on the target enclosure.

Unable to communicate with Onboard Confirm the validity of the OA IP address and user Administrator. Please confirm validity of the OA IP credentials. address and user credentials. Specified Onboard Administrator is not primary Specify the OA IP address of the primary OA in the target enclosure.

Troubleshooting

18

Error message
Unable to get enclosure VC mode information

Resolution
Log into VC Manager GUI and resolve any errors with VC Manager. Reset the OA to factory defaults, and then log into the VC Manager GUI. Check update requirements, and then try the update again. Verify that the Virtual Connect firmware package is correct, or download it again from the HP website (http://www.hp.com). See the fwupdate####.log file. Verify connectivity between the client and the enclosure. Verify connectivity between the client and the enclosure. Wait until the current update is complete before attempting to update the firmware. Verify that the activation order method (-oe or -of) is correct. The firmware package file is corrupt. Download the firmware package from a trusted source or directly from the HP website (http://www.hp.com).

Initialization process failed. Firmware update cannot continue. File extraction failed

Firmware update failed on module Unable to transfer file to module Unable to configure module for update Another firmware update is currently in progress The specified activation ordering method is not valid Signature Validation failed

Before contacting HP technical support, be sure to have the Virtual Connect Support Utility log file (fwupdate####.log) available.

Troubleshooting

19

Technical support
Before you contact HP
Be sure to have the following information available before you call HP:

Technical support registration number (if applicable) Product serial number Product model name and number Product identification number Applicable error messages Add-on boards or hardware Third-party hardware or software Operating system type and revision level

HP contact information
For the name of the nearest HP authorized reseller:

See the Contact HP worldwide (in English) webpage (http://welcome.hp.com/country/us/en/wwcontact.html). In the United States, for contact options see the Contact HP United States webpage (http://welcome.hp.com/country/us/en/contact_us.html). To contact HP by phone:
o o

For HP technical support:

Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7 days a week. For continuous quality improvement, calls may be recorded or monitored. If you have purchased a Care Pack (service upgrade), call 1-800-633-3600. For more information about Care Packs, refer to the HP website (http://www.hp.com/hps).

In other locations, see the Contact HP worldwide (in English) webpage (http://welcome.hp.com/country/us/en/wwcontact.html).

Technical support

20

Acronyms and abbreviations

DHCP
Dynamic Host Configuration Protocol

DNS
domain name system

FC
Fibre Channel

OA
Onboard Administrator

SSH
Secure Shell

SSL
Secure Sockets Layer

TLS
Transport Layer Security

VCM
Virtual Connect Manager

VCSU
Virtual Connect Support Utility

Acronyms and abbreviations

21