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.
© 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.
Contents Important notes and recommendations ............................................................................................ 4 New features ............................................................................................................................... 5 General requirements .................................................................................................................... 6 Resolved issues .........................................................................
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.
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.
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.
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.
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.
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.
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.
