HP Virtual Connect Version 2.02 Release Notes and Compatibility Matrix

• Network uplinks that are linked after the Network Setup Wizard has been started may not show
proper link status in the wizard. When the wizard is completed, all uplink link statuses are displayed
•
ed in the server profile. In most cases, a warning is provided, but in some cases it is not.
ct model number. The model number is displayed correctly in other screens
ab of the Ethernet Networks screen, the port status shows OK even if the
Firm
higher to install
W e
(
correctly.
A server profile can be assigned to a device bay with a server that has fewer physical NIC ports
than defin
• If a server is rebooted several times while its server profile is being edited, an error displaying an
XSL transformation failure may be displayed. Do not edit a server profile while repeatedly rebooting
a server.
• In the Bay Summary screen for a VC-FC module in Virtual Connect Manager, some servers might be
displayed with the incorre
and in the Onboard Administrator.
• In the Server Connections t
server port is not linked.
ware update
HP recommends using HP BladeSystem c-Class Virtual Connect Support Utility v1.3.1 or
the HP VC-Enet v2.02 and HP 4Gb VC-FC v1.30 firmware. Be sure to read the instructions on the
HP
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=MTX-
ebsit
793857044078415aa4ba4d9252&lang=en&cc=us&idx=1&mode=4&) and in the HP BladeSystem
al Connect Support Utility v1.3.1 or higher release notes for the procedures.
c-
Class Virtu
IMPORTANT: With the HP 4Gb VC-FC upgrade for version 1.21, the VC-FC module can
connectivity temporarily during the activation process. A redundant customer configuration
experiences a failover with no loss of application connectivity to the fabric.
drop
•
. To clear the degraded health status, use the OA to reset the
installed.
f
yed
s not contain a document element. The
•
•
d
completes, a subsequent upload attempt might fail with the GUI reporting an "unknown error" or
If the internal GUI-based firmware update support within VC v1.2x is used to perform either a
manual or automated firmware update for the HP 4Gb VC-FC v1.20 firmware, in some VC-FC
modules the OA and VC Manager might report a "degraded" health status of the VC-FC module
when the firmware update completes
status or power-cycle each VC-FC module showing the degraded status. This operation is required
only once for each module showing the degraded status. VC-FC modules that complete the firmware
update without showing the degraded status do not need to be reset. This status is corrected when
the v2.02 VC firmware is
• If the firmware update procedure indicates a failure to activate a module or appears to be stuck, it
might be caused by a timeout and/or a stale web page. To refresh the screen and verify the actual
update status, click the
Firmware update link under Domain Settings in the left navigation pane o
the VCM user interface.
• During the firmware update activation countdown, an Internet Explorer pop-up might be displa
stating "Failed to create processor object: The stylesheet doe
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.
When using the "Upload from local file system" option on the GUI firmware update page, if the
browser is closed, aborts, or loses network contact with the primary VC manager before the uploa
Known issues 18