HP Virtual Connect Version 2.33
Release Notes
Part Number 619999-001
May 2010 (First Edition)
© Copyright 2010 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.
Intended audience
This document is 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.
About this document
These release notes provide information that supersedes the information in the documentation set released
with version 2.31 of Virtual Connect.
Contents
Hardware and firmware requirements ............................................................................................. 4
HP Virtual Connect firmware ......................................................................................................................... 4
Firmware upgrade requirements .................................................................................................................... 4
Recommended firmware versions for this release ................................................................................... 6
New features ............................................................................................................................... 9
Resolved issues ........................................................................................................................... 10
Known issues.............................................................................................................................. 12
General .................................................................................................................................................... 12
Firmware update ........................................................................................................................................ 14
Virtual Connect Enterprise Manager Support.................................................................................. 16
Hardware and firmware requirements
HP Virtual Connect firmware
The latest HP Virtual Connect firmware package (version 2.33) contains the following firmware versions:
•
HP VC-Enet version 2.33
•
HP VC 4Gb FC version 1.40
•
HP VC 8Gb 24-Port FC version 1.01
•
HP VC 8Gb 20-Port FC version 1.40
The HP BladeSystem c-Class Virtual Connect Firmware v2.33 is available with the following packages:
•
•
•
Ethernet plus 4/8Gb 20-port FC Edition—contains the firmware for the following:
o
HP VC-Enet modules
o
HP VC 4Gb FC modules
o
HP VC 8Gb 20-Port FC modules
Ethernet plus 8Gb 24-port FC Edition—contains the firmware for the following:
o
HP VC-Enet modules
o
HP VC 8Gb 24-Port FC modules
Ethernet plus 4/8Gb 20-port and 8Gb 24-port FC Edition—this package is used by the HP
BladeSystem c-Class Virtual Connect Support Utility. It contains the firmware for the following:
o
HP VC-Enet modules
o
HP VC 4Gb FC modules
o
HP VC 8Gb 20-Port FC modules
o
HP VC 8Gb 24-Port FC modules
IMPORTANT: When updating firmware, update each domain with the entire firmware
package, which includes the individual VC-Enet and VC-FC firmware. Updating only the VCEnet firmware or only the VC-FC firmware is not supported.
Firmware upgrade requirements
IMPORTANT: For optimal operation of HP Virtual Connect, use the recommended firmware
versions.
Always install the firmware recommended for this release for the following items:
•
Server blade system ROMs
•
Ethernet mezzanines
•
Fibre Channel mezzanines
Hardware and firmware requirements
4
•
HP BladeSystem Onboard Administrator
•
iLO
HP recommends using the HP BladeSystem c-Class Virtual Connect Support Utility version 1.4.1 to install
the HP VC-Enet version 2.3x, the HP VC 4Gb FC version 1.40, and the HP VC 8Gb FC version 1.01
firmware.
For more information on installing the firmware, see the HP BladeSystem c-Class Virtual Connect Support
Utility release notes on the HP website (http://www.hp.com/go/bladesystem/documentation).
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.
4Gb VC-FC (-B21) or VC 4Gb FC (with enhanced NPIV) modules
IMPORTANT: When upgrading the HP VC 4Gb FC firmware from version VC-FC 1.2x to
version VC-FC 1.40, 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.
Firmware
Version
Version
Version
Version
Version
Virtual Connect firmware
1.31
1.32/1.34
2.01/2.02
2.10/2.12
2.3x
VC 4Gb FC firmware within
Virtual Connect
1.20
1.21
1.30
1.32
1.40
The following table shows firmware upgrade/downgrade support for the HP 4Gb Virtual Connect Fibre
Channel Modules.
Upgrade to or
downgrade
from
To VC 1.31
VC 1.31
To VC 2.3x
To VC
1.32/1.34
To VC
2.01/2.02
To VC
2.10/2.12
(VC-FC 1.21)
(VC FC 1.30)
(VC-FC 1.32)
—
Normal
Fabric outage*
Fabric
outage*
Fabric
outage*
VC 1.32
Normal
—
Fabric outage*
Fabric
outage*
Fabric
outage*
VC 2.01/2.02
Fabric
outage*
Fabric outage*
—
Normal
Normal
VC 2.10/2.12
Fabric
outage*
Fabric outage*
Normal
—
Normal
VC 2.3x
Fabric
outage*
Fabric outage*
Normal
Normal
—
(VC-FC 1.20)
(VC-FC 1.40)
* Always reset the module after the upgrade or downgrade.
On HP Virtual Connect 4Gb Fibre Channel Modules (with enhanced NPIV), firmware downgrade to any
versions older than VC 2.10 is not supported.
VC 8Gb 24-Port FC module
Firmware
Version
Version
Virtual Connect firmware
VC 2.10/2.12
VC 2.3x
VC 8Gb 24-Port FC firmware within
Virtual Connect
VC-FC2 1.00
VC-FC2 1.01
Hardware and firmware requirements
5
VC 8Gb 20-Port FC module
Firmware
Version
Virtual Connect firmware
2.3x
VC 8Gb 20-Port FC firmware within Virtual Connect
VC-FC 1.40
The following table shows firmware upgrade/downgrade support for the HP 8Gb Virtual Connect Fibre
Channel modules.
Upgrade to or downgrade from
To VC
2.10/2.12
To VC 2.3x
(VC-FC2 1.01)
(VC-FC2 1.00)
VC 2.10/2.12
—
Normal
VC 2.3x
Normal
—
For more information on required firmware versions and to download firmware upgrades, see the HP
website (http://www.hp.com/go/bladesystemupdates).
Recommended firmware versions for this release
Product
Minimum firmware version
HP Onboard
Administrator
•
For c7000 enclosures, version 2.60 or
higher
•
For c3000 enclosures, version 2.60 or
higher
iLO
Version 1.79 or higher
BL2x220c G5
System ROM 2008.11.02 or higher
BL260c G5
System ROM 2008.11.02 or higher
BL280c G6
System ROM 2008.11.02 or higher
BL460c
System ROM 2007.11.02 or higher
BL460c G5
System ROM 2007.11.02 or higher
BL460c G6
System ROM 2009.03.27 or higher
BL465c G5
System ROM 2009.03.12 or higher
BL465c G6
System ROM 2009.05.07 or higher
BL490c G6
System ROM 2009.03.27 or higher
BL495c G5
System ROM 2009.03.12 or higher
BL495 G6
System ROM 2009.05.07 or higher
xw460c
System ROM 2008.11.02 Rev A or higher
BL680c G5
System ROM 2009.02.24 or higher
BL685c G5
System ROM 2009.01.29 or higher
BL685c G6
System ROM 2009.05.07 or higher
BL860c
Recipe MVT 1.30
BL870c
Recipe BB 1.30
xw2x220c
System ROM 2008.11.02 Rev A or higher
Hardware and firmware requirements
6
Product
Minimum firmware version
NC382m
Boot code version 4.4.14 and MBA version
4.4.16 or higher
NC370i, NC373i, and
NC373m
Boot code version 1.9.6 and C Class option
ROM 1.1.3* or higher.
To use NC373m with the BL680c G5 server
blade, the option ROM must be updated to
NC373m Boot code version 1.9.6 and C Class
option ROM 1.2.7 or higher.
NC326i, NC325m, and
NC326m
Boot code version 3.28 and C Class option
ROM 1.1.3* or higher.
To use NC325m with the BL680c G5 server
blade, the option ROM must be updated to
NC325m Boot code version 3.28 and C Class
option ROM 1.2.8 or higher.
To use NC326m with the BL680c G5 server
blade, the option ROM must be updated to
NC326m Boot code version 3.28 and C Class
option ROM 1.2.8 or higher.
NC360m, NC364m
C Class option ROM 1.0.11
NC532i, NC532m
Boot code version 5.0.11 and Option ROM
MBA version 4.5.20
HP NC-Series Broadcom 1Gb and 10GbE
Multifunction Drive for Linux version 5.0.19-1
HP NC-Series Broadcom 10GbE Multifunction
Driver for Windows Server version 5.0.32.0
NC362i
Supported
NC542m
BIOS version 1.17-2
Minimum hardware revision required: 488074B22.
QLogic QMH2462 4Gb
FC HBA
For ProLiant server blades, use QLogic multiboot
image 1.81af or higher.
HP Emulex LPe 1105-HP
4Gb FC
Emulex boot-pair 6.03a7, Firmware 2.80a4 or
higher
QLogic QMH2562 8Gb
FC HBA
For ProLiant server blades, use QLogic multiboot
image 2.14af or higher.
HP Emulex LPe 1205-HP
8Gb FC HBA
Emulex Universal Boot image 6.03a7, Firmware
1.11a5 or higher
* Use the HP Gigabit Server Adapter Firmware Upgrade Utility for c-Class Blades version 1.10 on the HP website
(http://www.hp.com/cgi-bin/hpsupport/index.pl) or one of the online methods available for the OS. To find the
online update method for your OS, go to the HP website (http://www.hp.com/go/bladesystemupdates) and search
for Server Blade Software & Updates.
Version 2.33 of HP Virtual Connect Manager checks the server ROM image version and displays an
incompatible state only for server blades that have a VC Server Profile assigned and are using
incompatible server ROM versions. Version checking of mezzanine card firmware is not available, so be
sure to verify that the mezzanine card firmware is up-to-date.
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
Hardware and firmware requirements
7
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 the use of networkbased firmware update tools for server blade and mezzanine firmware updates.
Important notes
•
The HP Virtual Connect Flex-10 10Gb Ethernet Module is supported by VC v2.xx and higher
versions of VC firmware only. This module is not supported by older versions (1.3x) of VC firmware.
•
HP Integrity BL860 and BL870 Server Blades do not support the NC532m mezzanine card and the
Flex-10 feature set.
•
QLogic QMH2562 8Gb FC HBA and HP Emulex LPe 1205 8Gb FC HBA are supported with G6
servers only.
•
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. Go to the
LPe1205 product page on the HP website (http://www.hp.com) for download and installation
instructions.
•
Internet Explorer version 8 (IE8) is not supported.
•
Although the GUI allows the selection of SNMP v2 traps, the VC 4Gb FC module and VC 8Gb 20Port FC module default to v1 traps.
•
Configuring more than one FC trap destination with the same IP trap destination address results in
only one entry with the community string being the latter of the duplicated trap entries. The other
community strings in the duplicate traps are not used to send traps.
•
When updating the VC Manager firmware, the prompt for file downloads to a local system might be
blocked by the browser security setting.
•
Changes in the server RBSU can override Virtual Connect server profile settings for PXE (enabled or
disabled). If a change is made in RBSU, that change is not reflected in Virtual Connect Manager. If
PXE is set through RBSU, HP recommends using the "Use BIOS" setting.
•
If you restore a configuration, make sure all the servers are powered off. Otherwise, the server
profile can result in a "Profile Pending" state. To recover the profile, power cycle the server.
•
Although 320 VLANs can be supported within each module, the overall number of VLANs within the
VC Domain is also restricted due to performance limitations of the VC Manager during module
restore or recovery. The limits are defined based on usage scenarios.
•
To operate with the HP VC 8 Gb 20-Port FC modules, all QLogic QMH2562 8Gb FC HBAs must
install the multiboot image revision 2.14af or higher.
•
Virtual Connect v2.3x does not support connecting FlexNICs with any non-VC device, such as an
Ethernet Pass Through Interconnect Module or ProCurve 6120xg Interconnect Module. Each
mezzanine slot in a c-Class server blade is mapped to a pair of interconnect bays. If a mezzanine
slot has a FlexNIC installed, the mapped interconnect bays cannot have a non-VC device installed.
Hardware and firmware requirements
8
New features
The VC 2.33 release has no additional new features.
The VC 2.32 release has no additional new features.
The VC 2.31 release has no additional new features.
The VC 2.30 release includes the following new features:
•
Support for the HP Virtual Connect 8Gb 20-Port Fibre Channel Module. 8Gb configuration and
operation is supported only by G6 servers.
•
The following SNMP enhancements:
o
Added limited extensions to already supported MIBs
o
Added SNMP traps for Ethernet port state changes
o
Added SNMP traps for key, pre-defined threshold conditions
o
Supports new MIBs and traps for key VC domain and module elements
o
Supports both SNMPv1 and SNMPv2 traps (by trap destination)
— Trap destinations
— Type of traps to be sent to the destination
— Levels of traps to be sent to the destination
— Type and class of trap to be sent
— New module and domain MIBs. For additional information, see the VCM user guide.
This feature does not include user configuration of trap thresholds.
•
Increased the maximum number of VLANs allowed for an uplink port (or port set) from 64 to 128.
•
Support for BL495c G6 and BL465c G6 server blades.
•
Support for the new HP Code Signing Process.
•
Support the ability to connect two VC domains together (single enclosure or multi-enclosure) by
directly connecting their uplinks (no switch in between) to form a private network.
•
Added support for dynamic changes to FlexNICs. Servers no longer need to be powered off to
change the following FlexNIC settings:
•
o
bandwidth
o
link state
o
network/VLAN assignment
FlexNIC link state is now accurately reported in the VCM GUI.
New features
9
Resolved issues
The following issue has been resolved in VC 2.33:
•
Resolved an issue with Virtual Connect Flex-10 modules and NICs, where IGMP Snooping is
enabled. The IGMP snooping might stop working after a VC-Enet module is reset, restarted, or
power-cycled.
The following issues have been resolved in VC 2.32:
•
Resolved an issue when un-initialized servers were installed and continuously attempted to PXE boot.
Each server was generating multiple Ethernet port state events, which could result in sluggish VCM
GUI responses.
•
Resolved an issue for VCM GUI that would not allow use of upper case letters to define SNMP
community strings.
•
Resolved an issue where the GUI interface would appear unresponsive during the Checkpoint
Operation time period, which can be up to 40 seconds. Checkpoint Operation is initiated whenever
a profile configuration is being updated.
•
Resolved an issue where RDP operations would fail when VC unexpectedly updated the UUID and
SN to an internal data structure. This update occurs whenever a server POST COMPLETE event is
detected.
•
Resolved an issue where VC CLI SHOW operations would occur in minutes instead of seconds with
large network configurations.
•
Resolved an issue when letting a Virtual Connect configuration sit in idle, unexpected “event
subscriber timeout” error messages showed up in the trace log.
The following issues that existed in previous versions of Virtual Connect have been resolved in Virtual
Connect v2.30 or v2.31:
•
Resolved an issue on VC Flex-10 Ethernet modules where Link Aggregation Groups (LAG) cannot be
formed with more than 40Gb total throughput. With this fix, VC Flex-10 Ethernet modules can
support LAGs with up to 80Gb total throughput.
•
Resolved an issue with some server links mapped to the VC Flex-10 Ethernet module not being able
to link up under certain enclosure/server configurations.
The effect of this fix is that it can take an additional 30 seconds for a VC Flex-10 Ethernet module to
become ready after initial power-on of the module.
•
Resolved an issue for VC 8Gb 24-Port FC Modules when a VC Fabric has all of the uplink ports in
an offline state and one of the uplink ports comes back online. VC 8Gb 24-Port FC Modules now
reconfigure server connectivity to that online uplink port.
•
Resolved an issue for VC 8Gb 24-Port FC Modules that failed to map server connections to a newly
added uplink port on a VC Fabric that already has all of the uplink ports in an offline state.
•
Resolved an issue for VC 8Gb 24-Port FC Modules to generate SNMP traps to indicate that the
parameters have been changed when any of the SNMP configuration parameters are modified.
Resolved issues 10
•
Resolved an issue for VC 8Gb 24-Port FC Modules so the SNMP System Contact string can now be
less than four characters.
•
Resolved an issue for VC 8Gb 24-Port FC Modules to behave correctly after a VC domain deletion.
SAN connectivity is enabled for all the servers in the enclosure, regardless whether a server has
previously has assigned a server profile.
•
Resolved an issue for VC 8Gb 24-Port FC Modules that did not properly populate the SNMP
MibStatus Array.
•
Resolved an issue for VC 8Gb 24-Port FC Module so that under the default port group configuration,
server port logins can occur.
•
Resolved issues when VC FW is upgraded to v2.3x in a Virtual Connect Enterprise Manager (VCEM)
environment. The problem resulted in an incorrect SNMP configuration, which was not re-admitted to
its VCEM Virtual Connect Domain Group.
•
Resolved a v2.30 issue on a Multi-enclosure system in which the VC Manager user responses are
slow or the system appears to be locked up. This behavior is due to high overhead startup of the
SNMPD process.
•
Resolved an issue in which the SNMP SMI-S-enabled flag was not being carried forward to the
configuration from pre-VC 2.30 versions.
Resolved issues 11
Known issues
General
•
No System Log message is logged for FC contact name changes.
•
For server or I/O interconnect hardware changes involving adding or removing Flex 10
functionality, the profile assigned to a server or server bay must be removed, all hardware changes
performed, and the profile reassigned. Otherwise, indeterminate network operation might result.
•
After a configuration is changed, the VC Manager can take up to 90 seconds to save the new
information to non-volatile storage. If power is removed during this update, configuration information
might be lost. A new icon on the Virtual Connect Manager banner line indicates that a configuration
update is in progress or that the backup module has not been updated to the current configuration
changes.
•
During an Onboard Administrator failover, VC Manager can lose communication with the Onboard
Administrator for several minutes. During this time, VC Manager cannot make profile changes to
server blades or perform some enclosure administration functions, such as powering server blades
on and off.
•
When operating in a redundant OA environment and the user sends a "Transition Standby to
Active" request to the standby OA, the communication between Virtual Connect Manager and the
active OA might be lost. To restore communication, reset the Virtual Connect Manager from the
Tools pull-down menu.
•
Replacing the OA in an enclosure containing only one OA causes the OA to leave VC mode. This
mode change requires the VC Manager to re-establish credentials with the OA. During this process,
VC Manager rewrites all server settings and sets the state of the servers to "profile recovered." There
should not be any disruption to the servers, but the administrator should be sure that all servers have
the correct MAC addresses and WWNs. Powering off the server clears the "profile recovered" state.
If any servers are rebooted or power-cycled while the credential recovery occurs, the MAC
addresses and WWNs might be returned to the factory default settings.
•
If an enclosure import is attempted with a server blade in a failed state, VC Manager might report
an erroneous error. If the import completes, close the browser and log in again to verify the import
was successful. Use the OA to verify the working state of all server blades.
•
When scripting CLI commands, only a single scripting client should perform remote management
operations to a remote VC Manager. If multiple scripting clients are used to perform a heavy load of
CLI commands to a single VC Manager, some management commands might fail. In some cases, the
primary module might need to be reset to recover properly.
•
An unsupported state occurs when a VC-Enet module is replaced physically with a non-VC Ethernet
interconnect module without administrative removal of the module from the VC domain. During this
state, if either the Help/About HP Virtual Connect Manager page or Firmware Management page of
the VC Manager GUI is opened, the string, "Loading...," appears indefinitely instead of the
firmware version number for each module in the VC domain.
Known issues
12
•
If a BL2x220c server blade is present in an enclosure, the Hardware overview page in VC does not
display a graphical picture of the server in the Enclosure View. The graphical image can be seen on
the OA web page.
•
When the VC wizard is used to configure domain, network, SAN, and server profiles, the server
profile wizard does not allow double-dense server bay assignment for BL2x220c server blades. Run
the domain, network, and SAN wizards, and then log out. After logging back in, run the server
profile wizard. Double-dense bay assignment for BL2x220c server blades is now possible.
•
When a VC-FC module is replaced with another VC-FC module in a Virtual Connect domain, server
blade Fibre Channel SAN connectivity might not be restored properly. To resolve this problem after
the module is installed, either reset the VC-FC module from the Onboard Administrator GUI or reboot
the affected server blades.
•
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" output. This
condition has been observed periodically after a VCSU firmware upgrade of the VC module
firmware. To resolve this issue, reset the VCM on the primary module, or reset the primary module
using the OA.
•
If a VC-FC module is replaced with a spare VC-FC module without powering down the servers, and
if the server has profiles assigned to it with FC connections, servers are allowed to log in for a brief
period of time through an uplink of the new module. Approximately 8 seconds after discovering the
new VC-FC module, VCM configures it with the correct information, mapping downlinks to the
correct uplinks. To work around this problem, power down the servers in the enclosure before
replacing or swapping FC modules.
•
When a c7000 enclosure is fully populated with BL870c server blades and static login distribution is
used on VC 4Gb FC modules with all 4 uplinks included, VCM does not map any server blades to
uplink 1 and uplink 3. The server blades in bay 2 and bay 4 are mapped to uplink 2, and the server
blades in bay 6 and bay 8 are mapped to uplink 4. HP recommends using dynamic login
distribution.
•
If an HP Virtual Connect Flex-10 10Gb Ethernet Module is removed from an enclosure, it cannot be
administratively removed unless it is re-inserted and removed a second time.
•
If NPIV capability of a SAN Fabric switch port is lost, the disabled uplink port of the VC 8Gb 24-Port
FC module remains disabled until the module is reset. HP requires connectivity to NPIV-enabled
switches for all HP VC-FC modules.
•
For VC 8Gb 24-Port FC modules, if an uplink port 8 is present in the VC SAN Fabric definition and
the fabric type is set to Dynamic, this port is treated as the lowest-numbered port and receives server
logins before any other uplink ports.
•
When a VCM domain is deleted, VCM resets VC 8Gb 24-Port FC modules to a default factory
condition. This operation can take up to 50 seconds per VC 8Gb 24-Port FC module.
•
When VC 8Gb 24-Port FC module uplink port speeds are configured at 2Gb and other uplink ports
are configured at 4Gb or 8Gb, LEDs might illuminate "faint green" or "faint amber".
•
When Dynamic Login Distribution is selected, servers connected through VC 8Gb 24-Port FC
modules can take between 15 and 25 seconds to recover from a module uplink port failure.
•
When an enclosure is being imported, an erroneous "vcCheckpointCompleted" trap might be sent
by VC.
•
Multi-enclosure (ME) Double Dense domains require similar and compatible FC modules in bays 5,
6, 7 and 8 in all enclosures. If a ME Double Dense configuration contains incompatible FC modules
Known issues 13
in bays 5, 6, 7 or 8 in either the local or remote enclosures, some or all of the compatible FC
modules in the remote enclosures might be designated INCOMPATIBLE after import.
To work around this issue, do the following:
1. Replace inappropriate FC modules with similar and compatible FC modules in bays 5, 6, 7 and 8
on all enclosures.
2. Power cycle any FC module that still remains in an INCOMPATIBLE state.
•
The SNMP Managed Status Change trap (vcProfileManagedStatusChange) for all unassigned
Profiles is not sent by VC when the profile status transitions to a Normal state.
•
In a multi-enclosure environment, if local and remote enclosures are shut down and powered back
up, VC might incorrectly report that some empty I/O module bays in a remote enclosure are "NOCOMM". This occurs if there are VC-FC modules in the local enclosure and the corresponding bays
in the remote enclosure are empty. The empty module bays should have been reported as
"MISSING".
•
The VC CLI incorrectly allows enabling or disabling of SNMP on a domain. The same VC domain
attributes are not accessible via the GUI. Do not use the VC CLI to enable or disable SNMP on
domain attributes.
•
If an adapter is inserted in a server that is incompatible with the VC module that it maps to, the
SNMP Physical Server Managed Status trap (vcPhysicalServerManagedStatusChange) is not sent
when this mismatch is corrected.
•
In a multi-enclosure domain, the VC CLI reports an incorrect error and fails when an Ethernet uplink
is enabled or disabled. This occurs only if you try to enable or disable uplinks that are part of a VC
network, and if one or more uplinks are on the remote enclosures. Use the VC GUI to enable or
disable links in these instances.
•
The VC CLI incorrectly allows invalid speeds to be set on the uplinks of Ethernet modules. If an
invalid speed (for example, setting 100 Mb on an SFP RJ-45 pluggable module uplink) is set using
the CLI, the link state is disabled. This problem does not appear in the VC GUI. Use only valid
speeds when the VC CLI is being used to configure the uplinks on Ethernet modules.
•
When upgrading from VC v2.10 to VC v2.3x, the VC 2.10 SNMP configuration is converted to a
comparable VC 2.3x SNMP configuration. If a downgrade is performed from VC 2.3x to v2.10, the
SNMP configuration prior to the v2.3x upgrade is restored. Thus any changes made to the 2.3x
SNMP configuration are not reflected in the downgraded v2.10 SNMP configuration.
•
Even though the system might not prompt for a server reboot, server reboot is required after the
server is upgraded successfully with the latest firmware and drivers for HP Dual Port Flex-10 10GbE
Multifunctional BL-c Adapters, NC532i or NC532m. The reboot allows the newly upgraded drivers
and boot code to run, which then allows Virtual Connect to be able to configure the new feature
"Dynamic Changes to FlexNICs," which is included in this release.
Firmware update
HP recommends using the HP BladeSystem c-Class Virtual Connect Support Utility to install the HP VC-Enet
version 2.33, the HP VC 4Gb FC version 1.40, the HP VC 8Gb 20-Port FC version 1.40, and the HP VC
8Gb 24-Port FC version 1.01 firmware.
For more information on installing the firmware, see the HP BladeSystem c-Class Virtual Connect Support
Utility release notes on the HP website (http://www.hp.com/go/bladesystem/documentation).
Known issues
14
IMPORTANT: When upgrading the HP VC 4Gb FC firmware from version VC-FC 1.2x to
version VC-FC 1.40, 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.
•
If the firmware update procedure indicates a failure to activate a module or appears to be stuck, it
might be caused by a timeout, a stale web page, or both. To refresh the screen and verify the actual
update status, click the Firmware update link under Domain Settings in the left navigation pane of
the VCM user interface.
•
During the firmware update activation countdown, an Internet Explorer pop-up might be displayed
stating "Failed to create processor object: The stylesheet does not contain a document element. The
stylesheet might be empty, or it might not be a well-formed XML document." This pop-up can be
dismissed without consequences.
•
After a firmware update, clear the browser cache. If the browser cache is not cleared after a
firmware update, VC Manager might not function properly.
•
During an automated firmware update, if the primary VC module is running the same version or
higher than the selected firmware update package, and the "Allow firmware downgrades and/or reupdate" checkbox is not selected, only modules with lower versions of the firmware than the selected
package are updated. Upon completion of any updates, the firmware update page might display
inaccurate version numbers. To correct the display, click the Firmware management link in the left
navigation pane.
•
The OA CLI update all firmware command causes a VC Manager loss of domain, and recovery
requires an OA reset plus a VC Manager import of the stale configuration.
•
During a manual firmware update, if a browser "stack overflow" error message appears, some
modules might be running the previous firmware version and the Activate button does not appear in
the firmware update page. If the firmware update page shows the new firmware version under the
"Installed" tab, reset the module to activate the new firmware version.
•
In some circumstances, the primary module might fail to activate after an automated firmware
update. If the primary module fails to activate and the firmware update page shows the new
firmware version under the "Installed" tab, reset the primary module to activate the new firmware
version.
Known issues
15
Virtual Connect Enterprise Manager Support
•
Virtual Connect Enterprise Manager (VCEM) v1.40 provides full compatibility and support for VC
firmware v1.3x, v2.x, v2.1x, and v2.3x.
•
For VCEM availability and full product details, visit the HP website (http://www.hp.com/go/vcem)
or contact your HP representative.
Virtual Connect Enterprise Manager Support
16