HP Virtual Connect Version 2.12 Release Notes

 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.

 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. 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.

 If the VC firmware is downgraded from v2.12 to a version prior to 2.10, 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 should allow you to log in to the Virtual Connect Manager. The

module in bay 2 can now be powered up.

 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.

 When a c7000 enclosure is fully populated with BL870c servers and static login distribution is

utilized on VC 4Gb FC modules with all 4 uplinks included, VCM does not map any servers to uplink

1 and uplink 3. The server in bay 2 and bay 4 is mapped to uplink 2, and the servers 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.

Known issues