HP Virtual Connect 3.75 Release Notes

Issues and workarounds 7
• The output from the CLI show uplinkset command was not sorted by vNet name or VLAN ID.
• VCM incorrectly cleared the module configuration of the Primary VC module and was still unable to
acquire an IP address after all retries were exhausted. If VCM incorrectly cleared the module
configuration and VCSU was used to check the VC health state, VCSU reported that the module was not
configured.
• Changing uplink ports in a SUS removed SmartLink settings on all vNets.
• The "Connector Type" displayed by VCM and the information displayed on the Detailed Statistics
screen were not consistent when one of the uplinks ports X1-X4 on the FlexFabric module was not
configured for FC or was configured for Enet but had an FC SFP transceiver inserted into the SFP cage.
• VC Unknown (unmanaged) module states (Operational, VC, OA, and Comm) were not being
displayed in a consistent manner.
• When a profile had more than 162 connections, the maximum number allowed, defined on a physical
Flex-10 port, the port was disabled when the profile was applied and the port status displayed as
Disabled.
• When using the Virtual Connect Support Utility (VCSU) or HP Smart Update Manager (HP SUM), Virtual
Connect firmware upgrades from VC 3.18 or earlier could fail on a single module when updating to VC
firmware later than version 3.51. This fix addressed Customer Advisory c03395976, which can be
found on the HP website
(http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03395976).
• PXE, iSCSI, or FCoE boot could fail to be invoked on Gen8 servers.
• The GUI fabric status was green for uplinks that were linked to the Enet switch, even though the port type
was FC and FC SFP transceivers were installed.
• Resolved security vulnerability CVE-2010-4180.
• HP VC Flex-10 and FlexFabric modules could experience an extended timeout when re-establishing the
Link Aggregation Group (LAG). This issue could increase the possibility of encountering a ping loss, and
the likelihood of encountering a lost ping also increased with the number of port members in the LAG
that were being recovered or reintegrated.
• GUI performance was improved to prevent Flex applications from reloading on each navigation event.
• When using IE9 to activate the VC GUI, no error message appeared when executing without Adobe
Flash Player.
• The GUI allowed creation of a new domain from an existing configuration file without a proper warning
to power off the server blades.
• If an Enet connection was configured with multiple networks and custom speed settings, the output of the
show config command did not preserve the Custom speed setting and reverted the connections back
to the Preferred speed setting.
Issues and workarounds
Issue