HP Virtual Connect 3.51 Release Notes

Issues and workarounds 6
Resolved an issue where the MAC Address table did not get purged when a Flex-10 NIC was shut
down, causing a loss of connectivity.
Resolved an issue where changing the host name in either the GUI or CLI had no effect on the host name
used in system log.
Resolved an issue where both the GUI Domain Status screen and the CLI show status command did
not include servers with a failed status.
Resolved an issue where the GUI would stop its loading operation if the cursor was pointing to the DIP
switch warning icon.
Resolved an issue where VCM would restart when multiple iterations of the VCM CLI show
statistics command was issued.
Resolved an issue where Insight Control for VMware Center was unable to retrieve date from VC v3.30.
Resolved an issue where a fabric previously set to Manual Login Re-Distribution might appear as set to
Automatic Re-Distribution when you attempted to edit the fabric on the Edit SAN Fabric screen.
Resolved an issue where the incorrect status of "linked-standby" was displayed for uplink ports with
RJ-45 connectors.
The CLI now supports three boot target WWN formats.
The Network Setup Wizard now enables you to add a network access group before creating new
networks.
Resolved an issue with VCM internal states being out of sync, which resulted in loss of network
connectivity.
Resolved an issue where the FC profile connection entries were not being mapped to FC mezzanine
cards installed on the third and fourth server blades in an HP Integrity BL890c i2 Server Blade installed
in a c3000 enclosure.
Resolved an issue that caused VCM and VCEM to be out of sync, which was caused by VCM and OA
losing their communication during a VCEM profile assignment.
Resolved an issue where unassigning the profile from an auxiliary bay in an HP Integrity BL8x0c i2
Server Blade cleared the connections on the auxiliary blade.
Resolved an issue where copying a shared uplink set that had no associated networks failed in both the
GUI and CLI.
Resolved an issue that occurred when editing a shared uplink set. Previously, clicking on the links under
the "Connected To" column in the External Uplink Ports table displayed a progress bar indicating that
the data was loading, but the data load never completed.
Issues and workarounds
New issues
Issue
When VC or VCEM change the boot order using FC HBA boot parameters to configure Port 2 as primary and
Port 1 as secondary, the boot order might be incorrect.