HP Virtual Connect 1.10Gb-F Ethernet Module for c-Class BladeSystem User Manual

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

Part Number 506692-001
October 2008 (First Edition)

© Copyright 2008 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 vendor’s 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

Requirements ............................................................................................................................................ 4

Restrictions and limitations.......................................................................................................................... 5

Command line syntax ................................................................................................................................5

Usage...................................................................................................................................................... 6

Password masking..................................................................................................................................... 6

Commands .................................................................................................................................. 8

collect...................................................................................................................................................... 8

discover...................................................................................................................................................8

configbackup............................................................................................................................................ 9

healthcheck .............................................................................................................................................. 9

packageinfo ........................................................................................................................................... 10

report ....................................................................................................................................................11

resetvcm................................................................................................................................................. 11

supportdump ..........................................................................................................................................12

update................................................................................................................................................... 12

version................................................................................................................................................... 14

Troubleshooting.......................................................................................................................... 15

Error messages .......................................................................................................................................15

Technical support........................................................................................................................ 17

Before you contact HP.............................................................................................................................. 17

HP contact information............................................................................................................................. 17

Acronyms and abbreviations........................................................................................................ 18

Contents 3

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, Windows-based 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

Requirements

completed. After the module firmware updates are complete, the utility activates all of the modules.

• Microsoft® Windows® XP (Service Pack 1 or 2), Windows Server® 2003, or Windows Vista® must

be installed on the client.

• 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. The firmware can be

downloaded from the HP website (http://www.hp.com
then search for "Virtual Connect Firmware."

). Click Software and Driver Downloads, and

• No FTP servers can be running on the client system. A port conflict can prevent the utility from

performing an update.

• 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 currently imported
into a Virtual Connect domain, a Virtual Connect user account with Domain privileges is also
required.

• 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.

• 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 cannot open a connection with the remote
modules to perform the update.

Introduction 4

• Onboard Administrator firmware 1.30 or higher is required on the target enclosure. OA firmware

version 2.25 is recommended.

• 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 non-

functional. 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:

vcutil -a <command>

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:

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

To display a single module and its current firmware version, enter:

vcutil -a version -i 192.168.1.100 -u Administrator -p password -b 1

Introduction 5

Usage

Use the following steps to install and run the HP BladeSystem c-Class Virtual Connect Support Utility.

1. Install the application on the client system by running SETUP.EXE.

2. After the program is installed, click Start>Programs>Hewlett-Packard>Virtual Connect Support Utility

to start a console.

o To display the top-level help and available options, enter vcutil.
o To display version syntax and available options, enter vcutil -a version.
o To display report syntax and available options, enter vcutil -a report.
o To display update syntax and available options, enter vcutil -a update.
o To display discover syntax and available options, enter vcutil -a discover.
o To display collect syntax and available options, enter vcutil -a collect.
o To display configbackup syntax and available options, enter vcutil -a configbackup.
o To display supportdump syntax and available options, enter vcutil -a supportdump.
o To display healthcheck syntax and available options, enter vcutil -a healthcheck.
o To display packageinfo syntax and available options, enter vcutil -a packageinfo.
o To display resetvcm syntax and available options, enter vcutil -a resetvcm.

3. Download a valid Virtual Connect firmware package file from the HP website

(http://www.hp.com/go/bladesystemupdates

4. 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 is displayed

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 is
displayed for supported VC modules only.

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 to be updated. These updates are performed simultaneously.

The utility only updates supported VC modules that are able to be updated and require an update.

Password masking

), and then save it to your local file system.

For all of the commands provided by VCSU, the username, password, and IP address of the enclosure
OA must be provided. In some cases, the VC domain username 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 "*" and a prompt is provided that masks the input.

Example:

vcutil -a version -i 192.168.1.100 -u Administrator -p *

Introduction 6

OA Password :***********

Introduction 7

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:

• show enclosure *

• show domain

• show network *

• show fabric *

• show profile *

• show stackinglink

• show interconnect *

• show firmware

Item Description

Syntax

Parameters:

IP
USER
PWD
VCM USER

VCM PASS

Example
Collect configuration information from the OA and VC Manager:

vcutil -a collect -i 192.168.0.100 -u Administrator -p password -vcu
Administrator -vcp password

vcutil -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
Password of the OA user
Name of Virtual Connect user with Domain privileges. Required if an enclosure is in a

Virtual Connect domain.
Password for the Virtual Connect user.

discover

Locate remote OA enclosures that exist on the network within a specified address range.
This command is useful if an Administrator cannot remember the exact IP address of the OA on a certain

enclosure, but the general IP address range is known.

Commands 8

Item Description

Syntax
Parameters:

START IP
END IP

vcutil -a discover -s <START IP> -e <END IP>

First IP address in the range to search
Last IP address in the range to search

Example
Discover an enclosure in a certain address range:

vcutil -a discover -s 192.168.1.100 -e 192.168.1.200

configbackup

Log into VC Manager using the supplied credentials 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 Description

Syntax

Parameters:

IP
USER
PWD
VCM USER

VCM PASS

vcutil -a configbackup -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
Password of the OA user
Name of Virtual Connect user with Domain privileges. Required if an enclosure is in a Virtual

Connect domain.
Password for the Virtual Connect user

Example
Request a configuration download from Virtual Connect:

vcutil -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 failover, or firmware upgrade of VC Manager or OA, would cause an
outage.

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

• Power: On, Off, other

• Health: Ok, Degraded, Failed, other

• For VC-Enet Modules

o VCM Mode: Primary, Backup, Subordinate, Unintegrated

Commands 9

o

Module Configuration: In Sync, Not In Sync, Invalid

o 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 displayed indicates whether this data is in
sync or not between the two modules.

The 'Module configuration' state indicates whether all the modules in an enclosure are in sync with the
primary module with regards to 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 be displayed. Wait up to 2 minutes, and then execute the healthcheck
command again.

Item Description

Syntax
Parameters:

IP
USER
PWD

vcutil -a healthcheck -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
Password of the OA user

Example
List the state of modules in an enclosure:

vcutil -a healthcheck -i 192.168.0.100 -u Administrator -p password

packageinfo

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

• Package Version

• Ethernet Firmware Version Timestamp

• Ethernet Firmware Supported Hardware

• FC Firmware Version

• FC Firmware Supported Hardware

• Release Notes (extract, not display)

Item Description

Syntax
Parameter:

FILE

vcutil -a packageinfo -l <FILE>

Full path to the Virtual Connect package on the local computer

Example
Display package information from a file named VCpackage:

vcutil -a packageinfo -l VCpackage

Commands 10

report

Display the current running firmware version on all modules in a specific target enclosure, plus 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 are displayed, the user must provide a VC package file as part of
the input at the command line.

Item Description

Syntax
Parameters:

IP
USER
PWD
FILE
BAY

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

IP address of the active OA in the enclosure
Name of the OA user with privileges to access all enclosure interconnect bays
Password of the OA user
Full path to the Virtual Connect package on the local computer
Optional. The bay number of the target module. If not specified, the default is all supported

modules.

Examples
Display all modules in an enclosure:

vcutil -a report -i 192.168.1.100 -u Administrator -p password -l
VCpackage

Display a single module in an enclosure:

vcutil -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.

Item Description

Syntax
Parameters:

IP
USER
PWD
BAY

vcutil -a resetvcm -i <IP> -u <USER> -p <PWD> -b <BAY>

IP address of the active OA in the enclosure
Name of the OA user with privileges to access all enclosure interconnect bays
Password of the OA user
Bay number of the target module

Example
Reset a single module in an enclosure:

vcutil -a resetvcm -i 192.168.0.100 -u Administrator -p password -b 1

Commands 11

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 Description

Syntax

Parameters:

IP
USER
PWD
VCM USER

VCM PASS

Example
Save support information:

vcutil -a supportdump -i 192.168.0.100 -u Administrator -p password -vcu
Administrator -vcp password

vcutil -a supportdump -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
Password of the OA user
Name of Virtual Connect user with Domain privileges. Required if an enclosure is in a Virtual

Connect domain.
Password for the Virtual Connect user

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.
The user can also force an update of modules in the following circumstances:

• The target module contains a running firmware image that is the same version as the one in the

• The target module contains a running firmware image that is newer than the version in the source

Item Description

Syntax

Parameters:

IP
USER
PWD
FILE
BAY

-f version

source package.

package.

vcutil -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>]

IP address of the active OA in the enclosure
Name of the OA user with privileges to access all enclosure interconnect bays
Password of the OA user
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.
Optional. Allow an update of same or older firmware versions.

Commands 12

Item Description

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.

Password for the Virtual Connect user
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. Supported activation order methods

are:

• parallel—All modules are activated at the same time.

• odd-even—(Default) All modules in odd numbered bays are activated first, and then

modules in even numbered bays are activated.

• serial—Modules are activated one at a time starting with the highest numbered bay.

• manual—Modules 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. Supported activation order methods
are:

• parallel—All modules are activated at the same time.

• odd-even—All 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.

• manual—Modules are updated but not activated. Use the VC Manager GUI or OA

GUI to activate (reboot) modules.

-we

-wf

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.

Examples
Update multiple modules in an enclosure imported into a VC domain:

vcutil -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 managed by Virtual Connect:

vcutil -a update -i 192.168.1.100 -u Administrator -p password -1
vcfw121.bin -b 3

Update a single module in an enclosure managed by Virtual Connect:

vcutil -a update -i 192.168.1.100 -u Administrator -p password -vcu John

-vcp vcPass -l C:\images\vcfw-120.bin

Perform an update and specify an activation ordering method:

vcutil -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 URL:

vcutil –a update –i 192.168.1.100 –u Administrator –p password –l
http://www.myserver.com/vcfw-120.bin

Commands 13

Perform an update using a firmware image from an FTP server on the network:

vcutil –a update –I 192.168.1.100 –u Administrator –p password –l
ftp://user:password@192.168.1.10/vcfw-120.bin

version

Display the current running firmware version on all modules in a specific target enclosure.

Item Description

Syntax
Parameters:

IP
USER
PWD
BAY

Examples
Display all modules and their current firmware versions:

vcutil -a version -i 192.168.1.100 -u Administrator -p password

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

IP address of the active OA in the enclosure
Name of the OA user with privileges to access all enclosure interconnect bays
Password of the OA user
Optional. The bay number of the target module. If not specified, the default is all supported

modules.

Display a single module and its current firmware version:

vcutil -a version -i 192.168.1.100 -u Administrator -p password -b 1

Commands 14

Troubleshooting

Error messages

Error message Resolution

This version of the application does not support
the target enclosure

Invalid bay number x for an enclosure Specify a valid bay number.
Unable to get enclosure part number Check connectivity with the OA, and then restart the

Another instance of this application is running.
Please wait until all other instances are completed
and 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 An invalid option has been specified by the user. Verify

Invalid -a option An invalid -a format has been specified by the user. Verify

One or more parameters missing One or more required parameters was not specified. See

Missing -l option Specify the required package location.
Invalid -f option

Invalid OA IP address Provide a valid IP address in the proper format.
Unable to communicate with OA IP

aaa.bbb.ccc.ddd
OA username is longer than 40 characters Enter a valid OA username.
OA user password is greater than 40 characters Enter a valid OA user password.
Invalid bay number Specify a valid bay number for the target enclosure.
OA firmware version a.bb is not supported Update the firmware on the target enclosure.
Unable to communicate with Onboard

Administrator. Please confirm validity of the OA IP
address and user credentials.

Specified Onboard Administrator is not primary Specify the OA IP address of the primary OA in the target

Specify a supported enclosure type.

update process.
More than one instance of the update utility is attempting

to run on the client. Wait until all other instances are
complete, and then try again.

Check connectivity with the OA, and then restart the
update process.

Confirm the OA IP address and user credentials.

the list of available options for that command.

the list of available commands.

the required syntax for the command.

The -f version option can only be used with the
update command. Be sure a valid -f option is specified.

Check connectivity with the OA and verify that you are
using a valid IP address.

Confirm the validity of the OA IP address and user
credentials.

enclosure.

Troubleshooting 15

Error message Resolution

Unable to get enclosure VC mode information 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.

Initialization process failed. Firmware update
cannot continue.

Check update requirements, and then try the update
again.

File extraction failed Verify that the Virtual Connect firmware package is

correct, or download it again from the HP website.
Firmware update failed on module See the fwupdate####.log file.
Unable to transfer file to module Verify connectivity between the client and the enclosure.
Unable to configure module for update Verify connectivity between the client and the enclosure.
Another firmware update is currently in progress Wait until the current update is complete before

attempting to update the firmware.
The specified activation ordering method is not

valid

Verify that the activation order method (-oe or -of) is

correct.

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

Troubleshooting 16

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

For HP technical support:

• In the United States, for contact options see the Contact HP United States webpage

(http://welcome.hp.com/country/us/en/contact_us.html

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

o 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

).

). To contact HP by phone:

).

).

Technical support 17

Acronyms and abbreviations

CLI

Command Line Interface

DHCP

Dynamic Host Configuration Protocol

DNS

domain name system

FC

Fibre Channel

IP

Internet Protocol

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 18