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.

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

+ 12 hidden pages