HP Virtual Connect 3.51 Release Notes

Issues and workarounds 9
If a user attempts to remove or add a mezzanine card to a server blade, then VCM might not detect the
addition or removal of the mezzanine card when the server is re-inserted into the enclosure. However, the
OA shows the correct configuration.
Workaround
Reset the VC Manager before powering up the server blade that has the mezzanine card changes. For
new server installations, VCM correctly detects the server configuration and no reset is required. The
VCM reset does not affect the operation of any other servers.
Issue
During an OA failover the VC GUI might be unable to communicate with VCM for some amount of time.
However, VCM is still operational and working to recover from the OA failover. During this time, the browser
might display an alert dialog to inform the user about this loss of communication. Additional alert dialogs
might then be displayed for WebService calls that have failed.
Workaround
Acknowledge all alert dialogs, close the browser, and then begin a new GUI session.
Issue
On the Shared Uplink Sets screen, the list of networks on the Associated Networks tab might not be displayed
in the correctly sorted order.
Workaround
Select External Connections to edit a shared uplink set. Click on the column headers to sort list of
associated networks by name or VLAN ID. You can also see the correctly sorted list of networks by
selecting Ethernet Networks in the left navigation tree, and then use Filter to narrow the list.
Issue
HP VC 8 Gb 24-Port FC Module does not return a proper value for the cpqHoGUID element of the
CPHSHOST MIB during HP System Insight Control discovery, which causes discovery to complete with errors.
Issue
Under certain circumstances, you might encounter a pop-up message after deleting the VC domain through
the GUI. Even though a pop-up message is encountered, the domain deletion is successful.
Issue
iSCSI Boot from SAN is supported only on the NC551i Dual Port FlexFabric 10Gb Adapter and NC553i/m
10Gb 2-port FlexFabric Converged Network Adapter. The boot LUN IDs must be in the range of 0 to 8.
Issue
If an enclosure import is attempted with a server blade in a failed state, VCM might incorrectly report an error
when one does not exist. If the import completes, close the browser and log in again to verify that the import
was successful. Use the OA to verify the working state of all server blades.
Issue
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 VCM on the primary module, or reset the primary module using the OA.