HP BladeSystem c-Class Virtual Connect Support Utility Version 1.6.0 Release Notes Abstract This document provides release information for the HP BladeSystem c-Class Virtual Connect Support Utility Version 1.6.0, 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 2011 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.6.0 contains the following new features: • A VCSU update operation can be performed from a server blade in the same enclosure that is being updated. However, this feature is only supported when using a redundant network configuration on the server blade running the VCSU client. • If the enclosure is in VCM mode, a support dump is downloaded before an update operation begins.
General requirements • A supported operating system must be installed on the client: o Microsoft Windows XP (Service Pack 1 or 2) o Windows Vista o Windows Server 2003, 2008 o HP-UX 11.23 and 11.31 o Linux (Red Hat 4, Red Hat 5, SLES 10, SLES 11) • To run VCSU, the minimum, required, available free disk space is 600 MB per install instance. For example, if you run VCSU three times in parallel against three different enclosures, you must have approximately 1.8GB of available disk space.
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.
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.6.0: • At the final stage of a firmware update, VCSU waits a fixed amount of time for a primary VC module to become active. VCSU exits when this timer has expired, which results in a FAILURE status. VCSU has increased the amount of wait time to ensure that VCSU does not exit before VC Manager has completed its activation process.
• Resolved an issue where the firmware update for FC modules would fail due to an interrupted previous firmware update. • Resolved an issue where a firmware update would fail with an error message "Unable to create SSH session." • In some cases where VCM was in NO_COMM with the primary module, the VCSU healthcheck command incorrectly reported modules IN SYNC.
Known issues Issue When running Virtual Connect Support Utility in Interactive Mode, do not use quotation marks around the firmware package path even if the path has spaces. Only use quotation marks around the firmware package path when specifying the package location on the command line with the “-l” command-line parameter. Issue For important VCEM compatibility and version details when upgrading to VC 3.30 in VCEM 6.1, 6.2, and 6.3 environments, see the "Known Issues" section of the VC 3.
were made while in maintenance mode. Verify that all running and pending jobs are allowed to complete before proceeding to step b. b. Click the VC Domains tab, select VC domain, and then click VC Domain Maintenance. c. 3. Click Make Changes via VC Manager. This action releases control to the VCM. Run VCSU update using the –oe manual option to avoid the activation phase. Example: vcsu -a update -i 192.168.1.100 -u Administrator -p password -vcu John -vcp vcPass -l C:\images\vcfw-120.