HP BladeSystem c-Class Virtual Connect Support Utility Version 1.7

HP BladeSystem c-Class Virtual Connect Support
Utility Version 1.7.1
Release Notes
Abstract
This document provides release information for the HP BladeSystem c-Class Virtual Connect Support Utility Version 1.7.1, which remotely upgrades
the VC-Enet and VC-FC module firmware in HP BladeSystem c-Class c3000 and c7000 Enclosures. 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.
Part Number: 720616-001
December 2012
Edition: 1
© Copyright 2012 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®, and Windows Server® are U.S. registered trademarks of Microsoft Corporation.
Contents
Important notes and recommendations ............................................................................................ 4
New features ............................................................................................................................... 5
General requirements .................................................................................................................... 6
Resolved issues ............................................................................................................................. 8
Known issues ............................................................................................................................... 9
Related information ..................................................................................................................... 10
Documentation feedback .......................................................................................................................... 10
Contents
3
Important notes and recommendations
•
IMPORTANT: If you have FCoE connections configured through a mezzanine card, please read the
"Known issues" section for an important workaround required to avoid a temporary FCoE outage
during firmware update.
•
For upgrading to VC 3.00 or later, the embedded Virtual Connect GUI and CLI FW update options
have been removed. VCSU is the only stand alone method of FW update.
•
HP strongly recommends running the healthcheck option on an enclosure before performing any
management tasks. These tasks include, but are not limited to, the following:
•
o
Onboard Administrator firmware upgrade
o
Virtual Connect firmware upgrade
o
Onboard Administrator planned failover
o
Virtual Connect planned failover
When entering an OA user name from a Linux command shell with the domain\username format, use
quotation marks around the username so it is not expanded by the Linux shell.
Example:
vcsu -a collect -i 128.88.142.141 -u "dvt\ldapuser" -p hp123
•
When entering an OA user password interactively with password masking 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
:***********
Important notes and recommendations
4
New features
The HP BladeSystem c-Class Virtual Connect Support Utility Version 1.7.1 contains the following new
features:
•
Ability to roll back from a firmware update
o
Minimum version to downgrade to: VC v3.18
o
Minimum version to downgrade from: VC v3.70
•
VCSU now automatically performs a health check of all modules before proceeding with the firmware
update
•
Compatibility validation of the VCM version and VCSU version
New features 5
General requirements
•
A supported operating system must be installed on the client:
o
Microsoft Windows XP (Service Pack 1 or 2)
o
Windows Server 2003, 2008
o
HP-UX 11.23 and 11.31
o
Linux (RHEL 4, RHEL 5, SLES 10, SLES 11)
•
To run VCSU, the minimum, required, available free disk space is 600 MB per installation instance. For
example, if you run VCSU three times in parallel against three different enclosures, you must have
approximately 1.8 GB of available disk space.
•
When upgrading a Virtual Connect 4Gb FC module from version 1.31 or earlier, you must have
Administrative or Power User privileges on the client system to install and run VCSU.
•
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 VCSU console application when a firmware update is in progress. If VCSU 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.
•
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 VCSU.
•
Ethernet network connectivity is required between the client system hosting VCSU and the VC
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 VC module.
•
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 VCSU 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 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
General requirements
6
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.
•
VCSU supports IPv4 addresses only.
•
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.
General requirements
7
Resolved issues
The following issues that existed in previous versions of Virtual Connect Support Utility have been resolved in
Virtual Connect Support Utility Version 1.7.1:
•
Resolved an issue where VCSU 1.7.0 and earlier might abort the firmware upgrade process at 40%
due to a defective or invalid iLO state on one or more server blades and leave a VC Ethernet module
with a status of "Update Failed." The VCSU log reports these failures under the following conditions:
o
[VcsuCore.cpp:3411] : Fail over to backup module failed
o
[VcsuProgress.cpp:1222] : Failover not successful to activate primary module
o
[VcsuProgress.cpp:1223] : Aborting further activations as this would destroy the VC Domain
configuration
o
[VcsuProgress.cpp:166] : VC Enet Activation Failed
o
[VcsuUpdate.cpp:626] : Firmware update failed on one or more modules
•
Resolved an issue where VCSU appeared to hang during firmware activation.
•
Resolved an issue where VCSU failed to update in a no domain environment in which modules were in
higher numbered bays and new modules were inserted into lower numbered bays.
•
Resolved an issue where VCSU failed to activate in a no domain environment for bays 3 and 4 when
bay 1 had a VC module installed and bay2 did not have a VC module installed.
•
Resolved an issue where VCSU did not validate user privileges before performing the update.
•
Resolved an issue where VCSU returned a 0 exit code for a failure condition and the modules were not
being updated.
•
Resolved an issue where VCSU would generate an exception if a password longer than 256 characters
was used for the Configuration Backup Password option.
•
Resolved an issue where VCSU would fail to activate when the VC version was first updated to VC 3.70,
and later downgraded to VC 3.18.
Resolved issues
8
Known issues
Issue
If all the modules in an enclosure within a domain are replaced by a single module without deleting the
domain and an update is performed using VCSU, it causes abnormal VCSU termination.
Workaround
Either clear the “VC mode” in OA before performing the firmware update or import the domain and
then perform the update.
Issue
If the VCSU update confirmation prompt is left unanswered longer than the OA session timeout before typing
'Yes', then the update will fail due to OA session timeout.
Issue
If both primary and backup modules are replaced at the same time without deleting the domain and an
update is performed using VCSU, then the update on bay 1 is skipped.
Workaround
Either clear the “VC mode” in OA before performing the firmware update or import the domain and
then perform the update.
Issue
Upgrading VC firmware using Virtual Connect Support Utility (VCSU) or HP Smart Update Manager (HP
SUM) from 3.15, 3.17, or 3.18 to a newer version might result in a temporary Fibre Channel over Ethernet
(FCoE) outage. For more information, see Customer Advisory c0295049 on the HP website
(http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02950493).
Known issues
9
Related information
Documentation feedback
HP is committed to providing documentation that meets your needs. To help us improve the documentation,
send any errors, suggestions, or comments to Documentation Feedback (mailto:docsfeedback@hp.com).
Include the document title and part number, version number, or the URL when submitting your feedback.
Related information 10
Open as PDF
Similar pages