HP Virtual Connect 3.60 Release Notes

Prerequisites 10
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
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
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.
Issue
The SNMP Managed Status Change trap (vcProfileManagedStatusChange) for all unassigned profiles is not
sent by VC when the profile status transitions to Normal state.
Issue
When a server blade server port has multiple FlexNICs defined and one of the ports is defined as FCoE,
deleting the FCoE FlexNIC does not redistribute the bandwidth to other active FlexNICs, even though the GUI
indicates that this redistribution occurred.
Issue
If a profile that is currently assigned to a server is modified so that Network connections or FCoE connections
are added or removed, VC might change the protocol (Ethernet or FCoE) for a particular Flex-10 interface
without properly reinitializing it. This can result in unexpected behavior.
Workaround
Unassign the profile, and then reassign the profile.
Prerequisites
• There is a known issue with Virtual Connect data not appearing correctly in Insight Control for VMware
vCenter Server version 6.2. HP recommends that customers using Insight Control for VMware vCenter
Server upgrade to version 6.3 when using Virtual Connect firmware version 3.30 or higher.
• The Virtual Connect GUI requires a minimum of 512 MB of available memory to operate efficiently.