Print | Rate this content

Advisory: HPE Virtual Connect (VC) 4.60 and 4.61 – Reboot/Reset/Power-Cycle of Blade(s) or VC Module(s) May Result in Loss of Stacking Link Between VC Modules, Latency in FCoE Traffic and Uplink May Not Form LACP Group, Causing a Network Outage

SUPPORT COMMUNICATION - CUSTOMER ADVISORY

Document ID: a00029108en_us

Version: 5

Advisory: (Revision) HPE Virtual Connect 4.60 and 4.61 – Reboot/Reset/Power-Cycle of Blade(s) or VC Module(s) May Result in Loss of Stacking Link Between VC Modules, Latency in FCoE Traffic and Uplink May Not Form LACP Group, Causing a Network Outage
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: 2017-11-09

Last Updated: 2017-11-08


DESCRIPTION

Document Version
Release Date
Details
5
11/08/2017
Revised Resolution - OneView 3.10.07 is supported on Gen10 Servers with Virtual Connect 4.50
4
11/01/2017
Revised Resolution
3
10/25/2017
"Important Note" from the Resolution updated
2
10/24/2017
"Important Note" added to the Resolution
1
10/17/2017
Original Document Release.

When using a Virtual Connect (VC) domain running Virtual Connect Firmware Version 4.60 or 4.61, following a reset, reboot or power-cycle of a server blade or VC Module, the Stacking Link(s) between VC Modules either within a single enclosure or across multiple enclosures may be lost and/or Uplink(s) may not form a LACP Group, resulting in a network outage. Additionally, latency may be seen in FCoE Traffic.

This occurs due to an issue found in the control traffic handler within Virtual Connect Modules.

SCOPE

Any HPE c7000 Enclosure with HPE Virtual Connect (VC) running Virtual Connect firmware versions 4.60 or 4.61.

RESOLUTION

Any HPE BladeSystem c7000 Enclosures already updated to version 4.60 or 4.61 should be downgraded to 4.50 at the earliest convenience to avoid the referenced failure. HPE BladeSystem c7000 Enclosures with Virtual Connect firmware version 4.50 (or earlier) should not be updated.

HPE Virtual Connect firmware version 4.50 has been qualified on Gen10 server blade environments, including and supporting enclosures managed by OneView 3.10.07. HPE BladeSystem c7000 Enclosures configured with new Gen10 server blades should be deployed with Virtual Connect firmware version 4.50.

Gen10 server blade deployment using PXE boot will require manual configuration of the system boot order. (Reference detailed procedure below)

For any customers currently running version 4.60 or 4.61 that encounter the referenced failure, resetting the Virtual Connect module(s) which is not transmitting any packets on HPE BladeSystem c7000 enclosures having Gen8, Gen9, or Gen10 Blades, will help to temporarily clear the described condition. However, the issue may reoccur on subsequent reboots of Virtual Connect modules or servers.

To obtain Virtual Connect firmware version 4.50, follow the steps below:

1. Click the following link: https://support.hpe.com/hpesc/public/home
2. Enter a product name (e.g., "Virtual Connect FlexFabric 10Gb/24-port Module") in the text search field and wait for a list of products to populate. From the products displayed, identify the desired product and click on the Drivers & software icon to the right of the product.

3. From the Drivers & software dropdown menus on the left side of the page:

Select the Software Type - (Firmware)
Select the Software Sub Type - (Blade Infrastucture)
For further filtering (if needed) - Select the specific Operating System from the Operating Environment.

5. Select the latest release of *RECOMMENDED * HPE BladeSystem c-Class Virtual Connect Firmware Version 4.50", dated 16 May 2016.6.
6. Click Download.

NOTE: HPE Service Pack for ProLiant (SPP) 2017.10.1 contains Virtual Connect version 4.50 and is available for download at http://h17007.www1.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx .

IMPORTANT NOTE

Downgrading the Virtual Connect firmware could affect the domain integrity. Collect a VCM CLI "show config –IncludePoolInfo" output from the current 4.6x version. If the configuration needs to be restored after the firmware downgrade, the following methods can be used:

  • If the enclosure had Virtual Connect 4.50 installed previously and a backup is available, it can be restored. However, any changes made after the backup was created will not be restored. If there were no changes made, or if there are few changes made since the backup, they can be entered manually.

Or

  • Use the "show config –-IncludePoolInfo" output to restore the current configuration using the VCM CLI.

Gen10 limitations when running on VC Version 4.50 (not qualified with OneView)

In UEFI mode, the PXE Boot Order setting is not supported with Gen10 and VC 4.50.

As a workaround, use the OA to set the PXE Boot Order settings for Gen10 systems with VC 4.50:




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 HPE Subscriber's Choice. Sign up for Subscriber's Choice at the following URL: Proactive Updates Subscription Form.

NAVIGATION TIP : For hints on navigating HPE.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 HPE.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 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: SIK2640
©Copyright 2017 Hewlett Packard Enterprise Company, L.P.
Hewlett Packard Enterprise Company 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 Company and the names of Hewlett Packard Enterprise Company products referenced herein are trademarks of Hewlett Packard Enterprise Company in the United States and other countries. Other product and company names mentioned herein may be trademarks of their respective owners.

Provide feedback

Please rate the information on this page to help us improve our content. Thank you!