0% found this document useful (0 votes)
139 views

HP Virtual Connect 3.70 Release Notes

HP Virtual Connect 3.70 Release Notes

Uploaded by

Muhammad Shokr
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
139 views

HP Virtual Connect 3.70 Release Notes

HP Virtual Connect 3.70 Release Notes

Uploaded by

Muhammad Shokr
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 15

HP Virtual Connect 3.

70
Release Notes

Abstract
This document provides Virtual Connect release information for version 3.70. This document supersedes the information in the documentation set
released with version 2.3x, 3.0x, 3.1x, 3.30, 3.51, and 3.60. 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: 694425-003


December 2012
Edition: 3
© Copyright 2012 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.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

Adobe™ is a trademark of Adobe Systems Incorporated.


Contents

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


Supercede information .................................................................................................................. 4
Product models ............................................................................................................................. 4
Operating Systems ........................................................................................................................ 4
Languages ................................................................................................................................... 5
Enhancements .............................................................................................................................. 5
Fixes ........................................................................................................................................... 6
Issues and workarounds ................................................................................................................ 7
Prerequisites ............................................................................................................................... 10
Installation instructions ................................................................................................................. 11
Important notes ........................................................................................................................... 14
Related information ..................................................................................................................... 14
Documentation feedback .......................................................................................................................... 15

Contents 3
Update recommendation

Update Recommendation: Recommended

Supercede information

Supercedes: 3.60

Product models

Virtual Connect 3.70 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 4Gb FC Module (409513-B22 - End of Life announced in December, 2011)
• HP VC 8Gb 20-Port FC Module
• HP VC 8Gb 24-Port FC Module

IMPORTANT: The HP 1/10Gb VC Enet Module (399593-B22) and the HP 1/10Gb-F VC Enet
Module (447047-B21) are no longer supported.

Operating Systems

The HP Virtual Connect version 3.70 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 (http://h18004.www1.hp.com/products/servers/software/index.html).

Update recommendation 4
Languages

Languages supported for this release: English, Japanese

Enhancements

Version 3.70 of Virtual Connect contains support for the following enhancements:
• Support for new hardware:
o HP Virtual Connect Flex-10/10D Module
o HP ProLiant BL660c Gen8 Server series
o HP ProLiant WS460c Gen8 Workstation series
o HP Integrity BL860c i4 Server Blades
o HP Integrity BL870c i4 Server Blades
o HP Integrity BL890c i4 Server Blades
o HP 7m C-series Active Copper SFP+ cables (QK701A)
o HP 10m C-series Active Copper SFP+ cables (QK702A)
o Cisco 7m copper active Twinax cables (SFP-H10GB-ACU7M)
o Cisco 10m copper active Twinax cables (SFP-H10GB-ACU10M)
• Virtual Connect Direct-Attach Fibre Channel for HP P10000 3PAR Storage Systems, HP 3PAR T-Class
and F-Class Storage Systems
• Manageability enhancements:
o VCM GUI access to telemetry information
o Advanced telemetry and statistics for Link Aggregation Groups and FlexNICs
o GUI access to the FC Port Statistics for HP FlexFabric 10Gb/24-port Modules
o Improvements to the Statistics Throughout display and data collection
o Display of factory default MACs and WWNs in server profiles
o Added an FC/FCoE “Connect To” field to help identify how server ports are connected to the uplink
ports
o LLDP enhancements to more easily identify VC Ethernet modules on the network
o Improvements to the display of the MAC Address table to show the network name and VLAN ID
where the MAC address was learned, as well as display of the LAG membership table
• VCM GUI/CLI task progress activity indicator for predefined VCM operations
• Security enhancements:
o Support for 2048 bit SSL certificates and configurable SSL-CSR
o Activity logging improvements for TACACS+ accounting

Languages 5
o Option to disable local account access when LDAP, RADIUS, or TACACS+ authentication is
enabled
o Increased the default VCM local user account minimum required password length
o SNMP access security to prevent access from unauthorized management stations
• SmartLink failover improvements
• IGMP “NoFlood” option when IGMP snooping is enabled
• Browser support:
o Internet Explorer 8 and 9
o Firefox 10 and 11
• Firmware upgrade rollback from a previous firmware upgrade without domain deletion

Fixes

The VC 3.70 release resolves the following issues:


• Resolved an issue where a non-user friendly SOAP error message appeared in the GUI after a DELETE
DOMAIN confirmation. This might have happened when a user logged in with multiple sessions tried to
log out from one session (either a tab or window), or if another user deleted the VC domain.
• Resolved an issue where the output from the CLI show uplinkset command was not sorted by vNet
name or VLAN ID.
• Resolved an issue where VCM incorrectly cleared the module configuration of the Primary VC module
and was still unable to acquire an IP address after all retries were exhausted. If VCM incorrectly cleared
the module configuration and VCSU was used to check the VC health state, VCSU reported that the
module was not configured.
• Resolved an issue where changing uplink ports in a SUS removed SmartLink settings on all vNets.
• Resolved an issue where the "Connector Type" displayed by VCM and the information displayed on the
Detailed Statistics screen were not consistent when one of the uplinks ports X1-X4 on the FlexFabric
module was not configured for FC or was configured for Enet but had an FC SFP transceiver inserted
into the SFP cage.
• Resolved an issue where the VC Unknown (unmanaged) module states (Operational, VC, OA, and
Comm) were not being displayed in a consistent manner.
• Resolved an issue where, when a profile had more than 162 connections, the maximum number
allowed, defined on a physical Flex-10 port, the port was disabled when the profile was applied and
the port status displayed as Disabled.
• Resolved an issue where when using the Virtual Connect Support Utility (VCSU) or HP Smart Update
Manager (HP SUM), Virtual Connect firmware upgrades from VC 3.18 or earlier could fail on a single
module when updating to VC firmware later than version 3.51. This fix addressed Customer Advisory
c03395976, which can be found on the HP website
(http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03395976).
• Resolved an issue where PXE, iSCSI, or FCoE boot could fail to be invoked on Gen8 servers.

Fixes 6
• Resolved an issue where the GUI fabric status was green for uplinks that were linked to the Enet switch,
even though the port type was FC and FC SFP transceivers were installed.
• Resolved security vulnerability CVE-2010-4180.
• Resolved an issue where HP VC Flex-10 and FlexFabric modules could experience an extended timeout
when re-establishing the Link Aggregation Group (LAG). This issue could increase the possibility of
encountering a ping loss, and the likelihood of encountering a lost ping also increased with the number
of port members in the LAG that were being recovered or reintegrated.
• GUI performance was improved to prevent Flex applications from reloading on each navigation event.
• Resolved an issue where, when using IE9 to activate the VC GUI, no error message appeared when
executing without Adobe Flash Player.
• Resolved an issue where the GUI allowed creation of a new domain from an existing configuration file
without a warning to power off the server blades.
• Resolved an issue where if an Enet connection was configured with multiple networks and custom speed
settings, the output of the show config command did not preserve the Custom speed setting and
reverted the connections back to the Preferred speed setting.
• Resolved an issue where during a NO_COMM condition, VC Manager would preclude the user from
making changes leading to potentially harmful network outages.

Issues and workarounds

New issues
Issue
The Virtual Connect Manager CLI does not allow modification of an already existing Ethernet profile
connection with an index of 100 or higher.
Workaround
Use the Virtual Connect Manager GUI to modify Ethernet profile connections with an index of 100 or
higher.
Issue
The Virtual Connect Manager CLI interface does not allow creation of the local user account with a password
containing the ‘|’ (pipe) special character.
Workaround
Use the VCM GUI to create a local user account with a password containing the ‘|’ (pipe) special
character.
Issue
When trying to copy a working profile with multiple networks that belong to a user-defined network access
group, the following error message appears: "The operation resulted in the following error null."
Workaround
Add those networks to the "Default" network access group also.
Issue

Issues and workarounds 7


On the Ethernet Networks (Server Connections) screen the "Go to Network" action does not open the Edit
Network screen.
Workaround
Go to Ethernet Networks (External Connections) screen and perform the "Edit" action for that network.
Issue
HP recommends that the “Prevent flooding of unregistered multicast traffic” option remains disabled when
using VCEM to manage the VC domain with the “VCEM Compatibility Mode” set to a VC firmware version
earlier than 3.70.
Issue
VC occasionally reports a loss of communication with a remote enclosure. VC automatically recovers the
communication within seconds.
Issue
The search functionality in the left navigation tree of the GUI is incomplete. The help text states that you can
search for Network Access Groups, Modules, Interconnect Bays, and Device Bay items. These options are
not implemented in this release. To access a specific item, use the corresponding link in the left navigation
tree, and then locate the item on the right side of the screen.
Issue
While configuring a Shared Uplink Set in failover mode using the GUI, the GUI incorrectly allows uplink ports
that are designated as Primary ports to be deleted, which can render the Shared Uplink Set without any
Primary uplink ports.
Workaround
When using the GUI to configure a Shared Uplink Set, do not attempt to remove the uplink port
designated as Primary.
Issue
In a VC domain with a VC profile assigned to a BL2x220 server blade, when the I/O module connected to
the dual-technology port is replaced with a module using the other technology, the OA detects that the
identity of the server changed, but VC does not detect the change. As a result, the OA will not power on the
server until VC updates the server configuration.
Workaround
To resolve the problem, unassign and reassign the profiles to the two server bays (for example, Bays 1a
and 1b), hot-plug the server, or simulate a hot-plug of the server using the OA reset server
command. The problem can also be resolved if VC restarts, fails over, reboots, receives a firmware
update, or re-evaluates the server after an OA failover.
Issue
Clicking Backup Configuration on the Domain Settings (Backup/Restore) screen and then navigating away
from that screen does not save the configuration file.
Workaround
During the backup operation, do not refresh the screen or navigate to another screen.
Issue
Under rare conditions, if the time setting on an enclosure is modified in such a way that the HP VC 8Gb
20-Port FC Module or the HP Virtual Connect 4Gb FC Module happen to set the DHCP lease renewal date

Issues and workarounds 8


far in the future, the module might stop renewing the lease, which can potentially result in duplicate IP
address assignments in the network.
Issue
An extra button appears when using Internet Explorer 8 to view the Detailed Statistics screen for FC uplink
ports on a VC FlexFabric module. If you click Back to Previous Page, the tabs in the main window change.
To return to the previous screen, simply close the browser window.
General issues
Issue
The SCSI command aborts under load with the HP VC 8Gb 24-Port FC Module.
Issue
The HP VC 8Gb 24-Port FC Module does not respond to the HP Insight Control cpqHoGUID MIB request and
reports as an error.
Workaround
Remove the FC module from the query.
Issue
During an OA failover, the VC GUI might be unable to communicate with VCM for some amount of time.
However, VCM is still operational and working to recover from the OA failover. During this time, the browser
might display an alert dialog to inform you about the loss of communication. Additional alert dialogs might
then be displayed for WebService calls that fail.
Workaround
Start a new VCM GUI session and OA credentials can be restored successfully.
Issue
When an HP VC 8Gb 24-Port FC Module is connected to Brocade 16Gb switches and directors or to Cisco
MDS 9000 series switches with an advanced 8Gb line card, the link between the VC-FC module and the
switch can only negotiate to 4Gb instead of 8Gb. For more information, see the HP website
(http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03521759).
Workaround
Lock the switch port speed to 8Gb for the port to which the FC module is connected.
Issue
HP Systems Insight Manager might incorrectly identify the HP VC 8Gb 24-Port FC Module as a SAN switch
due to the incorrect value returned in the SysObjectOid.
Issue
Virtual Connect Manager might reset when it contains more assigned and unassigned profiles than can be
in use by physical servers in the domain.
Issue
The VCM CLI show uplinkport command does not display the serial numbers for pluggable modules.
Issue
For double-dense server blades, the side B server mezz port mapping is incorrect.
Issue

Issues and workarounds 9


The timestamp for SNMP traps from VC-FC interconnect modules is not in sync with the timestamp kept by
Virtual Connect Manager.
Issue
Even though the VC iSCSI boot from SAN implementation allows you to select LUN values from 0-255, the
adapter firmware limits the supported LUN values to 0-8
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
When multiple Internet Explorer 7 browser sessions are open to the Virtual Connect Manager application,
the VC GUI might hang.
Workaround
Add the following registry value:
[HKLM\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Inte
rnet Settings] "MaxConnectionsPerServer"=dword:6
By default, this registry value does not exist and Internet Explorer 7 defaults to the value of 2. Increasing
the value to 6 resolves the hanging issue. Internet Explorer 8 defaults to a value of 6, so this issue does
not occur. The Firefox web browser also defaults to a higher value.

Prerequisites

• Immediately review OA Customer Advisory c02639172 on the HP website


(http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c
02639172) to see if any recent changes made to the enclosure configuration are at risk of not being
persistently preserved. If you made changes using a non-Administrator user account, before the next
OA firmware upgrade or reset, execute the workaround documented in Customer Advisory
c02639172 to ensure that the enclosure configuration changes are being persistently preserved. The
issue described in Customer Advisory c02639172 is resolved with OA 3.21 and later.
• The lowest VCEM 7.1.1 support compatibility mode is now set to VC 3.30.
• If you are planning to use VC 3.70 firmware in a VCEM environment, HP recommends upgrading to
VCEM v7.1.1. For more information about the VC firmware that is compatible with VCEM, see the
Virtual Connect Enterprise Manager User Guide on the HP website
(http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=Support
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.

Prerequisites 10
• 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 (http://www.hp.com).
• Virtual Connect Manager version 3.70 requires Adobe Flash Player 10.x or higher before you can log
in. HP recommends updating to Adobe Flash Player 10.2 or higher. When using IE9, HP recommends
using Adobe Flash Player 10.3.181.16 or higher.
The recommended Adobe Flash Player web browser plug-in can be downloaded and installed from the
Adobe website (http://get.adobe.com/flashplayer/), or downloaded as a standalone executable
from the Adobe website (http://www.adobe.com/downloads).
For the latest Adobe Flash Player Security Bulletin Updates, see the Adobe website
(http://www.adobe.com/support/security/index.html#flashplayer).

Installation instructions

Two options are available for VC firmware update:


• HP BladeSystem c-Class Virtual Connect Support Utility
For this release of HP Virtual Connect, the minimum firmware requirement for VCSU is version 1.7.0. HP
recommends that you always use the latest version available. For more information about VCSU, see the
HP BladeSystem c-Class Virtual Connect Support Utility release notes on the Installing tab of the HP
BladeSystem Technical Resources website (http://www.hp.com/go/bladesystem/documentation). To
download the VC firmware and the VCSU utility, view the BladeSystem for ProLiant Release Set
Compatibility Table on the HP website (http://www.hp.com/go/bladesystemupdates) and select the
appropriate download.
• HP Service Pack for ProLiant
SPP is the replacement product for Insight Foundation (PSPs, Smart Update Firmware DVD, and other
systems software). To download the update, see the HP Service Pack for ProLiant website
(http://www.hp.com/go/spp).
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 3.70 upgrades when Virtual Connect Enterprise Manager (VCEM) is in
use, HP recommends upgrading to VCEM v7.1.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
(http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=Su
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
tables show the version of VC-FC firmware included with each VC firmware package.

Installation instructions 11
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 VC 4Gb FC firmware VC 8Gb 20-Port FC VC 8Gb 24-Port FC


firmware within Virtual firmware within Virtual firmware within Virtual
Connect Connect Connect
v1.31 1.20 — —
v1.32, v1.34 1.21 — —
v2.01, v2.02 1.30 — —
v2.10, v2.12 1.32 1.32 1.00
v2.30–v2.33 1.40 1.40 1.01
v2.34 1.41 1.41 1.01
v3.0x 1.40 1.40 1.02
v3.10, v3.15 1.41 1.41 1.03
v3.17, v3.18 1.41 1.41 1.04
v3.30 1.42 1.42 1.04
v3.51, v3.60, v3.70 1.43 1.43 1.04

The following table shows firmware upgrade/downgrade support for the HP VC 4Gb FC Modules or HP VC
8Gb 20-Port FC Modules.
Upgrade to or 1.31 1.32, 2.01, 2.10, v2.3x 3.0x 3.10, 3.30,
downgrade from 1.34 2.02 2.12 3.15, 3.51,
3.17, 3.18 3.60,
3.70
VC 1.31 — Normal Fabric Fabric Fabric Fabric Fabric Fabric
outage* outage* outage* outage* outage* outage*
VC 1.32/1.34 Normal — Fabric Fabric Fabric Fabric Fabric Fabric
outage* outage* outage* outage* outage* outage*
VC 2.01/2.02 Fabric Fabric — Normal Normal Normal Normal Normal
outage* outage*
VC 2.10/2.12 Fabric Fabric Normal — Normal Normal Normal Normal
outage* outage*
VC 2.3x Fabric Fabric Normal Normal — Normal Normal Normal
outage* outage*
VC 3.0x Fabric Fabric Normal Normal Normal — Normal Normal
outage* outage*
VC 3.10/3.15/ Fabric Fabric Normal Normal Normal Normal — Normal
3.17/3.18 outage* outage*
VC 3.30/3.51/ Fabric Fabric Normal Normal Normal Normal Normal —
3.60/3.70 outage* outage*

* 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.
Firmware version for HP BladeSystem for ProLiant

Installation instructions 12
The firmware versions and software versions listed in this section have been tested as a solution set using HP
Service Pack for ProLiant 2012.08.0 as a baseline, and are fully supported by HP. For Virtual Connect
version 3.70, HP recommends the use of SPP version 2012.08.0 with updates for specific components of the
solution. For best results, follow the pre-deployment planning steps in the HP Virtual Connect for c-Class
BladeSystem Setup and Installation Guide and the HP BladeSystem ProLiant Firmware Management Best
Practices Implementer Guide on the HP website
(http://h18004.www1.hp.com/products/servers/service_packs/documentation/index.html) to deploy the
baseline set with component updates.
HP Service Pack for ProLiant is the replacement product for Insight Foundation (PSPs, Smart Update Firmware
DVD, and other systems software). To download the update, see the HP Service Pack for ProLiant website
(http://www.hp.com/go/spp).

CAUTION: HP recommends using the specific firmware and software versions listed together in
SPP 2012.08.0 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.

Baseline Firmware Release Set


The contents of SPP 2012.08.0 is documented in the HP Service Pack for ProLiant 2012.08.0 Release Notes
and HP Service Pack for ProLiant 2012.08.0 Server Support Guide on the HP website
(http://h18004.www1.hp.com/products/servers/service_packs/documentation/index.html).
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

CAUTION: HP recommends using the specific firmware and software versions listed together in
SPP 2012.08.0 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.

Baseline Firmware Release Set


HP Integrity i2 Server Blade Version
HP Smart Updated Firmware – HP Integrity BL860c/870c/890c i2 System Firmware Bundle for 26.33
Linux/Windows (http://h18004.www1.hp.com/products/blades/integrity-release-sets.html)

Installation instructions 13
HP Integrity Server Blade Version
HP Integrity BL860c 04.31
(http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&pro
dNameId=3351095&prodTypeId=3709945&prodSeriesId=3331044&swLang=13&taskId=135&
swEnvOID=4001)
HP Integrity BL870c 04.31
(http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?lang=en&cc=us&pr
odNameId=3676869&taskId=135&prodTypeId=3709945&prodSeriesId=3676868&lang=en&cc
=us)

Important notes

• 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 within the same Domain
Group or between different Domain Groups 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.
• Changes in the server 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.

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
(http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManu
al&lang=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=18964&prodSeriesId=3601866).

Important notes 14
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 (mailto:[email protected]).
Include the document title and part number, version number, or the URL when submitting your feedback.

Related information 15

You might also like