HP Virtual Connect 4.10 Release Notes

Important notes 12
Additional 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 (http://www.hp.com/storage/spock).
The link to Virtual Connect is under the category "Other Hardware" in the list of selections on the left.
Firmware version for HP BladeSystem for Integrity
To obtain HP BladeSystem Release Sets for Integrity, see the HP website
(http://h18004.www1.hp.com/products/blades/integrity-release-sets.html).
Important notes
• FCoE protocol, which includes FIP Snooping, is not supported on uplinks with SFP-LR transceivers.
• Any configuration using Integrity server blades should only use OA firmware version 3.60. For more
information, see the HP website
(https://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay/?docId=e
mr_na-c03613140).
• 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:
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.
• Although the GUI enables the selection of SNMP v2 traps, the VC 4Gb FC Module and the VC 8Gb
20-Port FC Module remain as v1 traps.