Print | Rate this content

Advisory: (Revision) HP Virtual Connect (VC) - Updating to VC Firmware Version 4.30 May Cause Some or All Networks to Be Unavailable Which Could Result in All Uplink Ports Showing as Linked-Standby

SUPPORT COMMUNICATION - CUSTOMER ADVISORY

Document ID: c04422904

Version: 6

Advisory: (Revision) HP Virtual Connect (VC) - Updating to VC Firmware Version 4.30 May Cause Some or All Networks to Be Unavailable Which Could Result in All Uplink Ports Showing as Linked-Standby
NOTICE: The information in this document, including products and software versions, is current as of the Release Date. This document is subject to change without notice.

Release Date: 2014-08-26

Last Updated: 2015-08-19


DESCRIPTION

Document Version
Release Date
Details
6
8/19/2015
Updated the Resolution to include Virtual Connect Support Utility (VCSU) Version 1.11.1 or later for firmware updates that will detect and resolve the issue.
And note indicating VCSU Version 1.11.0 is no longer available.
5
6/25/2015
Added smart component information for Linux and Windows operating systems in the Resolution.
4
6/11/2015
Changes made to Resolution:
Added information to upgrade to Virtual Connect Firmware Version 4.31 instead of VC Firmware Version 4.30.
Added information to use Virtual Connect Support Utility (VCSU) Version 1.10.1, since VCSU Version 1.11.0 is not fixing this issue.
Removed information about updating with HP Smart Update Manager (HP SUM) smart component for VCSU Version 1.10.1 since it is better to upgrade to VC 4.31 instead.
3
3/3/2015
Added permanent solution, VC Firmware Version 4.31 in the Resolution.
2
8/27/2014
Added the following information to the NOTE in the Resolution section: "When completing the firmware update operation VCEM will put the VC Domain into Configuration Mismatch status. To return the VC Domain to Normal status either navigate to the VC Domains page, select the VC Domain and click on "Enable VC Domain Maintenance" or navigate to the Server Profiles page and click on the Edit button for a Server Profile that is contained in the VC Domain. Click the "Okay" button when VCEM alerts that the domain must be resynchronized."
1
8/25/14
Original Document Release.

Any Virtual Connect (VC) domain containing networks originally created in VC Firmware Version 3.18 (or earlier) may have those networks become unavailable when the domain is updated to VC Firmware Version 4.30. This issue may occur even if the current firmware version is later than VC Firmware Version 3.18 because the VC firmware version in which the networks were originally created determines whether a domain is susceptible to the issue. Note that VC 4.30 is the only VC version to have any customer impact due to this issue. The firmware version installed when the upgrade to VC Firmware Version 4.30 occurred does NOT determine whether a domain and the networks are susceptible, as shown in the following two examples:

Example 1
A VC domain created in version 3.18 (or earlier) with defined networks (whether it is updated directly to version 4.30 or has been updated to intermediate versions), and then updated to firmware version 4.30 it may exhibit the issue.


Example 2
A VC Domain created in version 3.30 (or later) with defined networks (whether it is updated directly to version 4.30 or has been updated to intermediate versions), and then updated to firmware version 4.30 it will NOT encounter the issue.


IMPORTANT: This issue will only occur immediately after the update to VC Firmware Version 4.30. If all networks are available following the update to version 4.30, then the issue has not been encountered and there is no risk in continuing to use VC Firmware Version 4.30.


Two possible indications of this VC Firmware Version 4.30 issue are described in the following scenarios:

Scenario 1 Indication
All uplink ports will display as "Linked-Standby," even though one or more networks associated with the Shared Uplink Set (or the dedicated network itself) are assigned to a profile, (i.e., "In-Use" networks). The Virtual Connect Manager (VCM) CLI screen will display all uplink ports in Linked-Standby even though there is at least one in-use network.
The same information may be seen from the Virtual Connect Manager (VCM) GUI by viewing the Shared Uplink Sets page, and then viewing the corresponding in-use networks on the Ethernet Networks page.


Scenario 2 Indication
Some networks, such as the ones defined in VC Firmware Version 3.18 (or earlier) will be unavailable. Networks defined in VC Firmware Version 3.30 (or later) will still be available.

SCOPE

Any Virtual Connect (VC) Firmware Version 4.30 with networks that were INITIALLY created in VC Firmware Version 3.18 (or earlier) using Virtual Connect Manager (VCM) for the following:

HP Virtual Connect Flex-10 10Gb Ethernet Module for c-Class BladeSystem

  • HP Virtual Connect Flex-10/10D Module for c-Class BladeSystem
  • HP Virtual Connect FlexFabric 10Gb/24-port Module for c-Class BladeSystem
  • HP Virtual Connect FlexFabric-20/40 F8 Module for c-Class BladeSystem
  • HP Virtual Connect Manager (VCM) Software

RESOLUTION

To prevent and correct this issue, upgrade to Virtual Connect (VC) Firmware Version 4.31 (or later). Any future VC firmware versions will not be susceptible to this issue.

If upgrading to VC 4.30, use Virtual Connect Support Utility (VCSU) Version 1.10.1 or 1.11.1 or later for firmware updates that will detect and resolve this issue.

Note: Do not use VCSU Version 1.11.0 to upgrade to VC Firmware Version 4.30 and please note that VCSU Version 1.11.0 is no longer available. If you must upgrade to VC Firmware Version 4.30 (although it is highly recommended to upgrade to VC Firmware Version 4.31 instead of VC Firmware Version 4.30), use VCSU Version 1.10.1 or 1.11.1 or later.

For environments needing to update to VC Firmware Version 4.30 using a Smart Component available in HP Service Pack for ProLiant (SPP) 2014.09.0, refer to the following URL: http://h17007.www1.hp.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx?version=2014.09.0


HP recommends using the following Smart Components for the appropriate operating systems:

4.30(b) - CP024624.scexe HP BladeSystem c-Class Virtual Connect Firmware, Ethernet plus 4/8Gb 20-port and 8Gb 24-port FC Edition Component for Linux

4.30(b) - CP024625.exe HP BladeSystem c-Class Virtual Connect Firmware, Ethernet plus 4/8Gb 20-port and 8Gb 24-port FC Edition Component for Windows

Warning: HP does NOT recommended installing VC Firmware Version 4.30 on the enclosure, when HP Virtual Connect Flex-10/10D Module for c-Class BladeSystem (638526-B21) is installed, because it will cause all the issues described in the Customer Advisory c04459474 (HP Virtual Connect (VC) - Some VC Flex-10/10D Modules for c-Class BladeSystem May Shut Down When Running VC Firmware Version 4.20 or 4.30 Due to an Erroneous High Temperature Reading): http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04459474

Note: If the VC Domain is managed by Virtual Connect Enterprise Manager (VCEM) to update a domain with networks created in VC Firmware Version 3.18 (or earlier) using VCSU 1.10.1 or 1.11.1 or later, a brief outage may occur as the issue is being corrected on the domain and the outage duration will vary depending upon the network size: a few seconds for domains with a small number of networks to a minute or more for domains with a large number of networks (e.g. four thousand networks).

When completing the firmware update operation VCEM will put the VC Domain into "Configuration Mismatch" status. To return the VC Domain to "Normal" status, either navigate to the VC Domains page, select the VC Domain and click on "Enable VC Domain Maintenance" or navigate to the Server Profiles page and click on the Edit button for a Server Profile that is contained in the VC Domain. Click the Okay button when VCEM alerts that the domain must be resynchronized.

  • If the issue is detected, a warning message will be displayed during the upgrade confirmation prompt to mention the potential network outage, as follows:

"Warning: This domain is managed by Virtual Connect Enterprise Manager (VCEM) and network configuration issues are detected on this domain. VCSU will fix the issues during firmware update which may result in temporary network outage."

  • When VCSU 1.10.1 or 1.11.1 or later is used to update VC Domains that are not managed by VCEM, an outage will not occur when correcting the issue.

As a workaround, if the VC Domain has been updated to VC Firmware Version 4.30 and this issue has been encountered, select one of the following two options:

Option 1) Downgrade the VC firmware to the version that was running prior to the update to version 4.30 (even if this version was 3.18 or earlier). *NOTE: VC Firmware Version 3.30 (or later) has a firmware rollback feature.

Option 2) This option will not allow for recovery. However, to continue using VC Firmware Version 4.30, perform the following steps to recreate the VC Domain:

  1. From the Virtual Connect Manager (VCM) CLI, capture the output from the following command: "show config -includepoolinfo"
  2. Gather default Administrator passwords for VC Ethernet modules.
  3. Power off all servers.
  4. Delete the domain.
  5. Log into VCM via the default Administrator password.
  6. Import the domain.
  7. Run the show config script via VCM CLI.
  8. Create a new Backup Domain Configuration file. (Do not restore any previous backup configuration files that could re-introduce the issue.)

RECEIVE PROACTIVE UPDATES : Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively via e-mail through HP Subscriber's Choice. Sign up for Subscriber's Choice at the following URL: Proactive Updates Subscription Form

NAVIGATION TIP : For hints on navigating HP.com to locate the latest drivers, patches, and other support software downloads for ProLiant servers and Options, refer to the Navigation Tips document .

SEARCH TIP : For hints on locating similar documents on HP.com, refer to the Search Tips document .


Hardware Platforms Affected: HPE Virtual Connect Flex-10 10Gb Ethernet Module for c-Class BladeSystem, HPE Virtual Connect Manager (VCM) Software, HPE Virtual Connect FlexFabric 10Gb/24-port Module for c-Class BladeSystem, HPE Virtual Connect Flex-10/10D Module for c-Class BladeSystem, HPE Virtual Connect FlexFabric-20/40 F8 Module for c-Class BladeSystem
Operating Systems Affected: Not Applicable
Software Affected: Not Applicable
Support Communication Cross Reference ID: IA04422904
©Copyright 2018 Hewlett Packard Enterprise Development LP
Hewlett Packard Enterprise Development shall not be liable for technical or editorial errors or omissions contained herein. The information provided is provided "as is" without warranty of any kind. To the extent permitted by law, neither HPE nor its affiliates, subcontractors or suppliers will be liable for incidental, special or consequential damages including downtime cost; lost profits; damages relating to the procurement of substitute products or services; or damages for loss of data, or software restoration. The information in this document is subject to change without notice. Hewlett Packard Enterprise Development and the names of Hewlett Packard Enterprise Development products referenced herein are trademarks of Hewlett Packard Enterprise Development in the United States and other countries. Other product and company names mentioned herein may be trademarks of their respective owners.

Legal Disclaimer: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models.

Provide feedback

Please rate the information on this page to help us improve our content. Thank you!
Document title: Advisory: (Revision) HP Virtual Connect (VC) - Updating to VC Firmware Version 4.30 May Cause Some or All Networks to Be Unavailable Which Could Result in All Uplink Ports Showing as Linked-Standby
Document ID: emr_na-c04422904-8
How helpful was this document?
How can we improve this document?
Note: Only English language comments can be accepted at this time.
Please wait while we process your request.