HP Virtual Connect 3.51 Release Notes

Issues and workarounds 7
Issue
VCM might enable server ports with no network connections. For example, if a simple server profile has only
one Ethernet connection, which maps to LOM1, then only LOM1 should be enabled. However both LOM1
and LOM2 are enabled.
Issue
While performing OA fail over events, the GUI prompt for “restoring OA credentials” is delayed longer than
expected. The GUI displays the message “Web browser unable to communicate with VCM, please close the
browser and re-connect”. The GUI might also display additional errors.
Workaround
Start a new VCM GUI session and OA credentials can be restored successfully.
Issue
The GUI fabric status is green for uplinks linked to the Ethernet switch, even through the port type is FC and
FC SFPs are installed.
Issue
After confirming a DELETE DOMAIN operation, an error message "Unexpected failure while fetching system
state" might be displayed.
Workaround
Acknowledge the message and continue.
Issue
After fail over from the primary module to a backup module, the following SNMP traps are not received:
Traps Value/Severity
vcDomainManagedStatus
Minor
vcModuleManagedStatus
Critical
vcEnclosureManagedStatusChange
Minor
vcProfileManagedStatusChange
Unknown
vcEnetNetworkManagedStatus
Unknown
Issue
Virtual Connect Manager might reset when it contains more assigned and unassigned profiles than can be
in use by physical servers in the domain.
Issue
The VCM CLI show uplinkport command does not display the serial numbers for pluggable modules.
Issue
For double-dense server blades, the side B server mezz port mapping is incorrect.
Issue
The timestamp for SNMP traps from VC FC interconnect modules is not in sync with the timestamp kept by
Virtual Connect Manager.
Issue
Both the GUI and CLI allow restoring from a configuration file when a domain exists and server blades are
powered on, which can result in duplicate MACs or WWNs on the network or SAN.