HP Virtual Connect 4.

40
Release Notes

Abstract
This document provides Virtual Connect release information for version 4.40. This document supercedes the information in the documentation set
released with the previous version. This document is intended 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: 798319-001

February 2015
Edition: 1
© Copyright 2015 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.

Adobe™ is a trademark of Adobe Systems Incorporated.

Contents

Update recommendation ............................................................................................................... 4

Supersedes information ................................................................................................................. 4
Product models ............................................................................................................................. 4
Operating systems ........................................................................................................................ 4
Languages ................................................................................................................................... 5
Enhancements .............................................................................................................................. 5
Fixes ........................................................................................................................................... 5
Issues and workarounds ................................................................................................................ 6
Prerequisites ................................................................................................................................. 8
Installation instructions ................................................................................................................... 9
Firmware upgrade requirements ................................................................................................................ 10
Version support for HP ProLiant Servers ...................................................................................................... 12
Version support for HP Integrity Servers ...................................................................................................... 13
Additional firmware information ................................................................................................................ 13

Important notes ........................................................................................................................... 13

Acronyms and abbreviations ........................................................................................................ 16
Related information ..................................................................................................................... 17
Documentation feedback ............................................................................................................. 18

Contents 3
Update recommendation

Update Recommendation: Recommended

Supersedes information

Supersedes 4.3x

Product models

Virtual Connect 4.40 is supported on the following interconnect modules:

• HP VC Flex-10/10D Module
• HP VC FlexFabric 10Gb/24-port Module
• HP VC Flex-10 10Gb Enet Module
• HP VC FlexFabric-20/40 F8 Module
• HP VC 4Gb Fibre Channel Module for BladeSystem c-Class (enhanced NPIV)
• HP VC 8Gb 20-Port FC Module
• HP VC 8Gb 24-Port FC Module
• HP VC 16Gb 24-Port FC Module

IMPORTANT: Beginning with VC 3.70, the HP 1/10Gb VC Enet Module (399593-B22) and the
HP 1/10Gb-F VC Enet Module (447047-B21) are no longer supported. Beginning with VC 4.10,
the HP 4Gb VC-FC Module (409513-B21) is no longer supported.

Virtual Connect 4.40 adds support for the following server blade hardware:
• HP LPe1605 16Gb FC HBA
• HP QMH 2672 16Gb FC HBA

IMPORTANT: First generation HP Integrity 860c and 870c Server Blades are no longer
supported. Support is continued for HP Integrity i2 and i4 model server blades.

Operating systems

Update recommendation 4
 The HP Virtual Connect version 4.40 firmware package operates in an embedded environment within each
Virtual Connect module; therefore, it is not dependent on any operating system.
For more information, see the HP Operating Systems and Virtualization Software Support for ProLiant Servers
web page on the HP website ([Link] or
view the Operating Systems section for Integrity Servers on the HP website
([Link]

IMPORTANT: Virtual Connect versions 4.30 and later no longer support first-generation HP
Integrity BL860c Server Blades and HP Integrity BL870c Server Blades. HP Integrity i2 and i4
model server blades are still supported.

Languages

Languages supported for this release: English, Japanese

Enhancements

VC 4.40 contains the following enhancements:

• Features supporting the HP VC 16Gb 24-Port FC Module
o FC trunking when connected to Brocade FC switches
o Enhanced statistics for the HP VC 8Gb and 16Gb 24-Port FC modules
• Enhanced SR-IOV features
o Configure SR-IOV Virtual Functions for server profiles
• rDNS support
• Support for Mozilla Firefox ESR 31.x and 33.x
• Support for AOC QSFP+ to SFP+ (splitter) cables with the HP VC FlexFabric-20/40 F8 Module. For
more information, see the module QuickSpecs on the HP website ([Link]

Fixes

VC 4.40 release resolves the following issues:

• HP VC 8Gb/20 Port FC and HP VC 4Gb FC modules may not fetch IP address after installing or
re-seating the module.
• Incorrect MAC addresses are written to the Command Line Protocol string after a domain MAC setting
database corruption.

Languages 5
 • In rare cases, DCC messages from VC are intermittently dropped by Integrity servers. Links become
non-responsive while the server NIC addresses excessive DCC packets.
• When attempting to log into VCM CLI using SSH or the Onboard Administrator CLI serial connection,
the login fails and the following error message is displayed:
Unable to communicate with the Virtual Connect manager. Please retry again
later.
• Double-density servers do not display in the VCM GUI Hardware > Overview > Front View.
• In a pure IPv6 environment, FC modules enter a NO-COMM state when DHCPv6 or EBIPAv6 is not
configured.
• Unable to use LDAP authenticated user to perform VC firmware updated when the VC domain is
managed by VCEM and using the VCEM Firmware Update Mode
VC 4.40 release addresses the following security vulnerabilities:
• CVE-2014-3567
• CVE 2014-6271
• CVE 2014-3566
• CVE 2014-3513

Issues and workarounds

Issue
Only manual login redistribution is supported across VC-FC uplinks. When many NPIV logins are
carried over a VC FC uplink connected to a SAN switch configured with a “default-zone all access”
zoning policy or when zones have been configured on the SAN with large numbers of devices in each
zone, there is a possibility that NPIV logins may get redistributed across multiple uplinks upon uplink
port failure and recovery.
Workaround
To prevent this from happening, create multiple zones on the SAN switch with a smaller number of ports
devices in each zone to group relevant NPIV ports together. HP recommends using a WWN-based
soft-zoning policy while having many NPIV ports. For more information on supported zoning policies,
see the HP SAN Design Guide.
Issue
Two alerts are generated when an Ethernet or FC cable is removed from a FlexFabric module. Ethernet
and FC ports are identified differently in traps. For example, port X1 is identified as 1017 for Ethernet
and 1.1 for FC. If a port is configured as a FC port on a FlexFabric module, VC sends both an Ethernet
and FC trap when the link changes state.
Issue
The text size of the Set/Clear SSH Key buttons are not displayed properly under SSH Key
Administration in Internet Explorer 11.
Workaround
Set a readable text size in Internet Explorer. Click on View→Text size→Smaller.

Issues and workarounds 6

Issue
The “show config” command generates a network map configuration using a list of server VLAN IDs
from the “server-port-map-range” command. The “show config” output displays “Network not found”
for multiple networks where the server VLAN ID is different from the SUS VLAN ID.
Workaround
Identify the specific “server-port-map-range” command in the “show config” output, and then replace it
with the “server-port-map” command and appropriate network name and VLAN ID.
Issue
A server using an HP FlexFabric 20Gb 2-port 630FLB/630M Adapter and configured to use Ethernet
Jumbo frames may experience lower FCoE throughput if server traffic is oversubscribed (more than
20Gb over) on the FlexFabric Adapter port and the server is only reading disks without writing them.
This is because the Ethernet traffic consuming excessive bandwidth.
Workaround
Configure the server to use standard 1500 byte MTU frames. Alternatively, ensure that server traffic
(FCoE + Ethernet) doesn’t oversubscribe the port bandwidth of 20Gb.
Issue
The VCM GUI does not redirect to the correct IP after a VC failover.
Workaround
The next failover succeeds without any issues. Refreshing the browser or closing and opening a new
session redirects the browser to the correct IP address.
Issue
Under certain circumstances, the checkpoint status icon in the GUI persists for a long time and is not
cleared. The CLI also shows a "Checkpoint Status: Invalid" status in the show domain command output.
This condition occurs periodically after a VCSU firmware upgrade of the VC module firmware.
Workaround
To resolve this issue, reset VCM on the primary module or reset the primary module using the OA.
Issue
VCSU upgrade fails when upgrading VC firmware from VC4.30/4.31 to VC4.40 in FIPS mode with
domain configured. VCSU log reports below message.
Backup Module is in unintegrated mode and not in backup mode. Cannot force
failover.
Failover not successful to activate primary module
Aborting further activations as this would destroy the VC Domain
configuration.
Workaround
Use the manual activation option -oe manual described in the VCSU User Guide.
Issue
When the domain is in maintenance mode from the VCEM, an error is received when editing the VC
stacking mode via CLI.
Workaround
Apply one of the following workarounds:

Issues and workarounds 7

 o Change the domain stacking mode before importing the domain under VCEM.
o If the domain is already under VCEM, then use the VCM GUI to modify the stacking mode after
placing the domain under maintenance mode.
Issue
In NNMi 9.2, the [Link] can not be loaded
Workaround
Edit the MIB file. Change vcQoSDot1MapTrafficClassId to
vcQoSDot1pMapTrafficClassId. Save the MIB file, and then reload it.
Issue
After issuing the reset statistics command, VCM sends the following traps:
o vcModPortOutputUtilizationUp
o vcModPortOutputUtilizationDown
Workaround
These traps can be ignored.

Prerequisites

• VC SR-IOV prerequisites:
o Supports the following adapters:
— HP FlexFabric 20Gb 2-port 650FLB Adapter
— HP FlexFabric 20Gb 2-port 650M Adapter
— HP FlexFabric 10Gb 2-port 536FLB Adapter
— HP Flex-10 10Gb 2-port 530FLB Adapter
— HP FlexFabric 10Gb 2-port 534FLB Adapter
— HP Flex-10 10Gb 2-port 530M Adapter
— HP FlexFabric 10Gb 2-port 534M Adapter
— HP NC552m Flex-10 Adapter
— HP NC553m 10Gb 2-P FlexFabric Converged Network Adapter
— HP FlexFabric 10Gb 2-port 554M Adapter
— HP Flex-10 10Gb 2-port 552M Adapter
— HP FlexFabric 10Gb 2-port 554FLB Adapter
— HP FlexFabric 20Gb 2-port 630FLB Adapter
— HP FlexFabric 20Gb 2-port 630M Adapter
o Supports the following operating systems:
— Microsoft Windows Server 2012 (64-bit)
— VMware ESXi 5.1 U2, 5.5 (64-bit)

Prerequisites 8
 — Red Hat Enterprise Linux 5.9 and 5.10 (64-bit with KVM)
— Red Hat Enterprise Linux 6.4 and 6.5 (64-bit with KVM)
— SUSE Linux Enterprise Server 11 SP2, SP3 (64-bit with KVM)
• The lowest VCEM 7.4.1 support compatibility mode is set to VC 3.30.
• If you are planning to use VC 4.40 firmware in a VCEM environment, HP recommends upgrading
VCEM to version 7.4.1. For more information about compatibility between VC firmware and VCEM
versions, see the Virtual Connect Enterprise Manager User Guide on the HP website
([Link]
Manual&lang=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=18964&prodSeriesId=360
1866).
• Customers using Insight Control for VMware vCenter Server should upgrade to version 6.3 when using
Virtual Connect firmware version 3.30 and later. Version 6.3 fixes a known issue with version 6.2
where Virtual Connect data did not display correctly.
• The Virtual Connect GUI requires a minimum of 512 MB of available memory to operate efficiently.
• To operate with HP VC 8Gb 20-Port FC Modules, all HP Emulex LPe 1205 8Gb FC HBAs that are
revision A (identified by label EDC A-4904) must perform a CFL region 19 flash update. For download
and installation instructions, see the LPe1205 product page on the HP website ([Link]
• Virtual Connect Manager version 4.40 requires Adobe Flash Player 11.1.x or higher before you can
log in. HP recommends updating to Adobe Flash Player 11.5 or higher for Windows and 11.2 for Linux
systems.
For more information, see the latest HP Virtual Connect for c-Class BladeSystem User Guide in the
Virtual Connect Information Library ([Link]
• When VC 4.10 or higher is configured in "IPv6 Only" mode, the OA "Enclosure IP Mode" must also be
configured through the OA CLI or OA GUI. However, you must ensure that any OA IPv4 addresses are
cleared or the VC module cannot function correctly. To recover, clear any OA IPv4 addresses using the
OA CLI or OA GUI, and then reset the VC module. For more information, see the "Enabling IPv6
support" section in the latest HP Virtual Connect for c-Class BladeSystem User Guide in the Virtual
Connect Information Library ([Link]

Installation instructions

Use one of the following methods to update the VC firmware:

• HP BladeSystem c-Class Virtual Connect Support Utility
To download the latest utility, see the HP website ([Link]
For information about using the utility, see the HP BladeSystem c-Class Virtual Connect Support Utility
Release Notes in the Virtual Connect Information Library ([Link]
• HP Service Pack for ProLiant
To download the service pack, see the HP Service Pack for ProLiant website
([Link]
For information about installing the service pack, see the documentation tab on the HP Service Pack for
ProLiant website.

Installation instructions 9
 SPP is the replacement product for Insight Foundation (PSPs, Smart Update Firmware DVD, and other
systems software).

IMPORTANT: VC 4.40 supports SPP 2014.09.0, SPP 2014.06.0, SPP 2014.02.0 (B), and HP
Maintenance Supplement Bundle for SPP 2014.09.0 and SPP 2014.02.0 (B) and the features
available in each release. HP recommends using the most current firmware and driver updates for
your components following the latest SPP release. When available, they can be obtained from the
HP Single Point of Connectivity Knowledge (SPOCK) website
([Link] The link to Virtual Connect is on the left, under the
category "Other Hardware" in the list of selections.

Firmware upgrade requirements

IMPORTANT: When updating VC firmware, update each domain with the entire firmware
package, which includes the individual VC-Enet and VC-FC firmware. Updating only the VC-Enet
firmware or only the VC-FC firmware is not supported.

IMPORTANT: For VC 4.40 upgrades when Virtual Connect Enterprise Manager (VCEM) is in
use, HP recommends upgrading to VCEM v7.4.1. For more information about the VC firmware
that is compatible with VCEM, see the latest version of the Virtual Connect Enterprise Manager
User Guide on the HP website
([Link]
pportManual&lang=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=18964&prodSe
riesId=3601866).

Each HP Virtual Connect firmware package contains a separate HP VC FC firmware version. The following
table shows the VC FC firmware version included with each VC firmware package.

IMPORTANT: When upgrading the HP VC 4Gb FC firmware from version VC-FC 1.2x to version
VC-FC 1.4x, the VC-FC module can drop connectivity temporarily during the activation process.
A redundant customer configuration experiences a failover with no loss of application
connectivity to the fabric.

Virtual Connect HP 4Gb VC-FC HP Virtual HP VC 8Gb HP VC 8Gb HP VC 16Gb

firmware Module Connect 4Gb 20-Port FC 24-Port FC 24-Port FC
firmware FC Module Module Module Module
(409513-B21) firmware firmware firmware firmware
(409513-B22)
v1.31 1.20 — — — —

v1.32, v1.34 1.21 — — — —

v2.01, v2.02 1.30 1.30 — — —
v2.10, v2.12 1.32 1.32 1.32 1.00 —
v2.30–v2.33 1.40 1.40 1.40 1.01 —
v2.34 1.41 1.41 1.41 1.01 —
v3.0x 1.40 1.40 1.40 1.02 —
v3.10, v3.15 1.41 1.41 1.41 1.03 —
v3.17, v3.18 1.41 1.41 1.41 1.04 —
v3.30 1.42 1.42 1.42 1.04 —

Installation instructions 10
Virtual Connect HP 4Gb VC-FC HP Virtual HP VC 8Gb HP VC 8Gb HP VC 16Gb
firmware Module Connect 4Gb 20-Port FC 24-Port FC 24-Port FC
firmware FC Module Module Module Module
(409513-B21) firmware firmware firmware firmware
(409513-B22)
v3.51, v3.60, 1.43 1.43 1.43 1.04 —
v3.70
v3.75 1.44 1.44 1.44 1.04 —
v4.01 1.44 1.44 1.44 1.05 —
v4.10 Not Supported* 2.00 2.00 1.10 —
v4.20, v4.21 — 2.01 2.01 1.11 —
v4.30, v4.31 — 2.02 2.02 1.11 —
v4.40 — 2.05 2.05 3.00 3.00

*Beginning with VC 4.10:

• Modules with the part number 409513-B21 are displayed as “HP 4Gb VC-FC Module” and are
unsupported as of VC 4.10 and onward.
• Modules with the part number 409513-B22 are displayed as “HP Virtual Connect 4Gb FC Module”
and remain supported in VC 4.10 and onward.
Use the following procedure to verify your FC module. The part number can be verified using VCM or OA:
If using VCM:
a. In the left pane, under the Hardware section, click the Enclosure name, and then select Interconnect
Bays.
The Interconnect Bays screen is displayed.
b. Under the Interconnect Bays Summary table, click on the module of interest.
c. Find the part number under the Interconnect Bay Information table.
If using OA:
a. In the left pane, click Enclosure Information, and then select Interconnect Bays.
The Interconnect Bay screen is displayed.
b. Under the Interconnect List table, click on the bay of interest.
c. Under the Interconnect Bay Information screen, click the Information tab.
d. Find the part number under the Interconnect Bay Information tab.

The following table shows firmware upgrade/downgrade support for the HP VC 4Gb FC Modules or HP VC
8Gb 20-Port FC Modules.
Virtual Connect To To To To To To To To To
versions 1.31 1.32, 2.01, 2.10, 2.3x 3.0x 3.10, 3.30, 4.20,
1.34 2.02 2.12 3.15, 3.51, 4.21,
3.17, 3.60, 4.30,
3.18 3.70, 4.31,
3.75, 4.40
4.01,
4.10
From VC 1.31 — Normal Fabric Fabric Fabric Fabric Fabric Fabric Fabric
outage* outage* outage outage outage* outage* outage*

Installation instructions 11
 Virtual Connect To To To To To To To To To
versions 1.31 1.32, 2.01, 2.10, 2.3x 3.0x 3.10, 3.30, 4.20,
1.34 2.02 2.12 3.15, 3.51, 4.21,
3.17, 3.60, 4.30,
3.18 3.70, 4.31,
3.75, 4.40
4.01,
4.10
* *
From VC 1.32/1.34 Normal — Fabric Fabric Fabric Fabric Fabric Fabric Fabric
outage* outage* outage outage outage* outage* outage*
* *
From VC 2.01/2.02 Fabric Fabric — Normal Normal Normal Normal Normal Fabric
outage outage outage*
* *
From VC 2.10/2.12 Fabric Fabric Fabric — Normal Normal Normal Normal Fabric
outage outage outage* outage*
* *
From VC 2.3x Fabric Fabric Fabric Fabric — Normal Normal Normal Fabric
outage outage outage* outage* outage*
* *
From VC 3.0x Fabric Fabric Fabric Fabric Fabric — Normal Normal Fabric
outage outage outage* outage* outage outage*
* * *
From VC Fabric Fabric Fabric Fabric Fabric Fabric — Normal Fabric
3.10/3.15/ outage outage outage* outage* outage outage outage*
3.17/3.18 * * * *
From VC Fabric Fabric Fabric Fabric Fabric Fabric Fabric — Fabric
3.30/3.51/ outage outage outage* outage* outage outage outage* outage*
3.60/3.70/3.75/ * * * *
4.01/4.10
From VC Fabric Fabric Fabric Fabric Fabric Fabric Fabric Fabric —
4.20/4.21/4.30/4 outage outage outage* outage* outage outage outage* outage*
.31/ * * * *
4.40
* Always reset the module after the upgrade or downgrade.

On HP Virtual Connect 4Gb Fibre Channel Modules (with enhanced NPIV), downgrading the firmware to
any version older than VC 2.10 is not supported.

Version support for HP ProLiant Servers

Firmware and software versions have been tested using the latest HP Service Pack for ProLiant as a baseline
set and are fully supported by HP. HP recommends using the latest SPP release and component updates
specific to your solution. To deploy the baseline set with component updates, follow the pre-deployment
planning steps in the following documents on the HP website
([Link]
• HP Virtual Connect for c-Class BladeSystem Setup and Installation Guide
• HP BladeSystem ProLiant Firmware Management Best Practices Implementer Guide

Installation instructions 12
 CAUTION: HP recommends using the firmware and software versions listed in the latest SPP
version to ensure complete solution component compatibility and full functionality. These versions
have been tested as a set. Using other version levels might result in operational issues.

The contents of the latest SPP version is documented in the HP Service Pack for ProLiant Release Notes,
Contents Report, and Server Support Guide on the HP website
([Link]

Version support for HP Integrity Servers

To obtain HP BladeSystem Release Sets for Integrity Servers, see the HP website
([Link]

Additional firmware information

Versions 3.15 and higher of HP Virtual Connect Manager check the server ROM image version and display
an incompatible state only for server blades that have a VC Server Profile assigned and are using
incompatible server ROM versions.
Virtual Connect does not have the capability to perform version checking of the mezzanine card firmware.
Validate this information through server POST for mezzanine support utilities.
Server blades and mezzanine cards that do not meet the required firmware versions do not accept Virtual
Connect-assigned parameters such as MACs and WWNs properly and therefore maintain factory defaults.
However, these server blades do have the Ethernet network and Fibre Channel fabric connectivity specified
in their Virtual Connect server profiles. This connectivity enables you to use network-based firmware update
tools for server blade and mezzanine firmware updates.
For Virtual Connect Fibre Channel and FlexFabric modules, the supported firmware and OS drivers are listed
in the HP Single Point of Connectivity Knowledge (SPOCK) website ([Link]
The link to Virtual Connect is under the category "Other Hardware" in the list of selections on the left.

Important notes

IMPORTANT: Virtual Connect versions 4.30 and later no longer support first-generation HP
Integrity BL860c Server Blades and HP Integrity BL870c Server Blades. HP Integrity i2 and i4
model server blades are still supported.

Observe the following information:

• When upgrading to VC 4.40, the following SR-IOV settings are configured:
o When upgrading from 4.10 or higher, the SR-IOV mode is set to "Simplified" for all existing
profiles. All VFs are allocated to the 3rd PF or FlexNIC port of the server. To assign VFs to other PFs,
set the SR-IOV mode to "Advanced."
o When upgrading from 4.00 or lower, SR-IOV is disabled by default to maintain pre-4.10 SR-IOV
behavior.

Important notes 13
• If a new VC FC module is installed in an interconnect bay which is lower than an existing VC FC module
bay, for example, if new VC FC modules are installed in bay 3 and bay 4, where bay 5 and bay 6
already have VC FC modules that are part of the domain, server profiles that have a fabric configured
with the existing VC FC module will not allow you to manage FC connections. In order to recover from
this situation, remove all the existing FC connections from the profile using VCM CLI, and then add the
fabrics again either using VCM GUI or VCM CLI.
• The total number of NICs displayed by the operating system may be more than configured by VC even
if “Hide Unused FlexNICs” has been selected in the server profile. This can happen while configuring
Ethernet Network Connections in the server profile, either by skipping interfaces or configuring an odd
number of total interfaces.
For example, if you configure LOM1:1-d, and then skip LOM1:1-a, LOM1:1-c, LOM1:2-a and
LOM1:2-c, the operating system displays 6 network interfaces:
o LOM1:1-a
o LOM1:1-c
o LOM1:1-d
o LOM1:2-a
o LOM1:2-c
o LOM1:2-d
Similarly, if you configure LOM1:1-a, LOM1:1-c, LOM1:1-d, LOM1:2-a and LOM1:2-c, the operating
system also displays 6 network interfaces, including LOM1:2-d. This happens because the CNA
enumerates all of the physical functions until it reaches the network assigned interface, and then it
enumerates all of the physical functions for LOM1:2 as configured in LOM1:1. Unassigned NICs that
are shown in the operating system may not be used since there is no network associated with it in the
server profile.
• When changing the PXE/IP boot order, the server may require a reboot after applying the VC profile.
• When an OS is installed on the hard drive, it automatically updates the boot order, placing the hard
drive first. If the PXE/IP boot order is configured in the VC profile, the server may not boot from PXE,
since the boot order was updated by the OS. To boot from PXE, be sure to check the boot order in RBSU
or OA.
• Changes in RBSU can override Virtual Connect server profile settings for PXE (enabled or disabled). If
you make a change in RBSU, that change is not reflected in Virtual Connect Manager. If you set PXE
through RBSU, HP recommends using the "Use-BIOS" setting.
• A network outage may result when upgrading directly from VC [Link] release version to VC 4.40 release
in a Multi-Enclosure environment. Upgrade from VC [Link] to VC 3.70 or VC 4.10 first, and then
upgrade from VC 3.70 or VC 4.10 to VC 4.40 in a Multi-Enclosure setup.
• IPv6 requires a minimum SPP release of 2013.09.0 (B). The minimum OA firmware version required is
4.01, and the minimum iLO 4 firmware version required is 1.30.
• FCoE protocol, which includes FIP Snooping, is not supported on uplinks with SFP-LR transceivers.
• When connecting a Virtual Connect FlexFabric 10Gb/24-port Module directly to 3PAR storage systems
in the VC multi-enclosure environment, a server profile migration of a SAN-booted server between
enclosures is not supported. Similarly, in the domains managed by Virtual Connect Enterprise Manager
(VCEM), a server profile migration of a SAN-booted server between enclosures is not supported.
To perform a server profile migration of a SAN-booted server between enclosures directly attached to
a 3PAR storage system in the VC multi-enclosure environment, the following manual steps are required:

Important notes 14
 a. Power off the server.
b. Un-assign the server profile.
c. Change the Primary and Secondary Target WWNs in the FC Boot Parameters section of the profile
to reflect the WWNs of the 3PAR storage array ports directly connected to the destination
enclosure.
d. Assign the profile to the destination location.
e. Power on the destination server.

• During OA failover or other management network disruptions, VC SNMP traps might not reach the
management station.
• The latest version of VC MIBs can be downloaded from the HP Systems Insight Manager "MIB Kit" site
on the HP website
([Link]
• To access Virtual Connect documentation for current and past releases, see the HP website
([Link]

Important notes 15
Acronyms and abbreviations

ALB
adaptive load balancing

CNA
Converged Network Adaptor

DAC
direct attach cable

DCC
device control channel

DHCP
Dynamic Host Configuration Protocol

FCoE
Fibre Channel over Ethernet

FIPS
Federal Information Processing Standard

FLOGI
fabric login (Fibre Channel)

IGMP
Internet Group Management Protocol

LACP
Link Aggregation Control Protocol

LLDP
Link Layer Discovery Protocol

LUN
logical unit number

Acronyms and abbreviations 16

 MIB
management information base

OA
Onboard Administrator

QoS
Quality of Service

SPP
HP Service Pack for ProLiant

SSL
Secure Sockets Layer

TLB
transmit load balancing

VC
Virtual Connect

VCEM
Virtual Connect Enterprise Manager

VCM
Virtual Connect Manager

VCSU
Virtual Connect Support Utility

WWN
World Wide Name

Related information

Virtual Connect Enterprise Manager support

For information about the VC firmware that is compatible with VCEM, see the latest version of the Virtual
Connect Enterprise Manager User Guide on the HP website

Related information 17
 ([Link]
al&lang=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=18964&prodSeriesId=3601866).

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 ([Link]
Include the document title and part number, version number, or the URL when submitting your feedback.

Documentation feedback 18