HP Virtual Connect Version 3.30 Release Notes

Known issues 18
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
A fabric previously set to Manual Login Re-Distribution might appear as set to Automatic Re-Distribution when
you attempt to edit the fabric on the Edit SAN Fabric screen.
Workaround
To ensure that your fabric is set to Automatic Re-Distribution on the Edit SAN Fabric screen:
1. Under "Show Advanced Settings" select Manual Login Re-Distribution.
2. Select Automatic Login Re-Distribution.
3. Click Apply.
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
Changing the host name of the primary VC Ethernet module results in a loss of the module’s IP address alias
(the VC domain IP address).
Workaround
From the VC GUI or CLI, disable the Virtual Connect Domain IP Address settings, and then re-enable the
settings with the previously used parameters.
General
• 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.
• 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.
• 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.
• The SNMP Managed Status Change trap (vcProfileManagedStatusChange) for all unassigned profiles
is not sent by VC when the profile status transitions to Normal state.
• In a multi-enclosure environment, if local and remote enclosures are shut down and powered back up,
VC might incorrectly report that some empty I/O module bays in a remote enclosure are "NO-COMM".
This error occurs if VC-FC modules are installed in the local enclosure and the corresponding bays in the
remote enclosure are empty. The empty module bays should have been reported as "MISSING".
• If an adapter is inserted in a server that is incompatible with the VC module that it maps to, the SNMP
Physical Server Managed Status trap (vcPhysicalServerManagedStatusChange) is not sent when this
mismatch is corrected.