HP Virtual Connect Version 2.02 Release Notes and Compatibility Matrix
• 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, and 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.
• 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 webpage.
• 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 blade servers). Run
the domain, network, and SAN wizards, and then log out. After logging back in, run the server
profile wizard. Assignment of double-dense bay assignment for BL2x220c server blades is now
possible.
• When multiple uplink ports on the same VC-Enet module are linked at the same speed and
configured in "failover" mode with the same priority, and one of these uplinks is the Active uplink for
the corresponding Shared Uplink Set or dedicated network, then deleting this Active uplink from the
VCM GUI or CLI does not result in another uplink being selected as the newly Active uplink. This
action results in loss of network connectivity for servers mapped to those network(s). To work around
this problem, disable the Active uplink port through the VCM GUI or CLI, or disconnect the port
physically before deleting it. This action ensures minimum disruption to network connectivity for the
affected network(s).
•
reset the VC-FC module from the Onboard Administrator GUI, or reboot the
•
re.
• f
lem, the
•
ould allow login to the Virtual Connect Manager. The module in bay 2 can
•
profile can end up in a "Profile Pending" state. To recover the profile, power cycle the server.
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
module insertion, either
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 sometimes after a VCSU firmware upgrade of the VC module firmwa
To resolve this issue, reset the VCM on the primary module, or reset the primary module via OA.
If a VC-FC module is replaced with a spare VC-FC module without shutting down the servers, and i
the server has profiles assigned to it with FC connections, there is a brief period of time when the
servers are allowed to login through an uplink of the new module. The Virtual Connect Manager
takes approximately 8 seconds after discovering the new VC-FC module to configure it with the
correct information (mapping downlinks to the correct uplinks). To work around this prob
servers in the enclosure must be shut down before replacing or swapping FC modules.
If the VC firmware is downgraded from v2.02 to an older version, and Flex-10 connections exist in
the profiles, it might not be possible to log in to the Virtual Connect Manager after the downgrade. If
this problem occurs, power down the VC module in bay 2, and then reset the module in bay 1 from
the OA. This action sh
now be powered up.
If you restore a configuration, make sure all the servers are powered off. Otherwise, the server
Known issues 16