HP Virtual Connect Version 3.17 Release Notes

Known issues 14
Known issues
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.
• No System Log message is logged for FC contact name changes.
• 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 that the import was
successful. Use the OA to verify the working state of all server blades.
• If a BL2x220c server blade is present in an enclosure, the Hardware Overview screen in VC does not
display a picture of the server in the Enclosure View. The picture can be seen on the OA web page.
• 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.
• In a multi-enclosure domain, the VC CLI reports an incorrect error and fails when an Ethernet uplink is
enabled or disabled. This error occurs only if you try to enable or disable uplinks that are part of a VC
network, and if one or more uplinks are on the remote enclosures. Use the VC GUI to enable or disable
links in these instances.
• The VC CLI incorrectly allows invalid speeds to be set on the uplinks of Ethernet modules. If an invalid
speed (for example, setting 100 Mb on an SFP RJ-45 pluggable module uplink) is set using the CLI, the
link state is disabled. This problem does not appear in the VC GUI. Use only valid speeds when the VC
CLI is being used to configure the uplinks on Ethernet modules.
• In Virtual Connect Manager 3.10 or later, when a VC domain is configured with a primary module
installed in a bay other than bays 1 or 2, you must have both a primary module and a backup module.
If the primary module is installed in a bay other than bay 1 or bay 2, and no backup module is installed,
running Virtual Connect Support Utility results in an unconfigured domain after the upgrade and
requires you to restore the domain configuration from a backup file.
• When VC is used and Integrity BL870c i2 or BL890c i2 server blades are present, after an OA is reset
the OA occasionally displays factory-assigned WWNs and MAC addresses for the auxiliary blades in