HP Virtual Connect Version 1.34 Release Notes and Compatibility Matrix

Known issues 15
any servers are rebooted or power cycled while the credential recovery is occurring, 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. The working state of all server blades can be verified using the OA.
• 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.
• RDP "rip and replace" is not supported in a Virtual Connect environment.
• 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).
• Before restoring a configuration, be sure all the servers are powered off. Otherwise, the server
profile can end up in a "Profile Pending" state. To recover the profile, power cycle the server.
• If an OA reset is performed and the VC GUI page is open, the VC might display "NO COMM" for
some VC FC modules, and also mark the fabrics as "failed". This state is transient and clears itself
after the OA module is reset fully. No fabric or network outage exists.
Fibre Channel and SAN boot
• To boot properly from SAN with some versions of Linux and VMware ESX 3.0.1 and 3.0.2, change
the QLogic QMH2462 4Gb FC HBA connection options to "point-to-point only" in the QLogic BIOS
configuration utility. Emulex LPe 1105-HP 4Gb FC HBA does not require the "point-to-point"
connection option to boot properly from SAN.