HP Virtual Connect 4.10 Release Notes

Issues and workarounds 7
• OpenSSL used by VC was modified to address vulnerability to CVE-2012-2110 and CVE-2012-2131.
• While configuring a Shared Uplink Set in failover mode using the GUI, the GUI incorrectly allowed
uplink ports that were designated as Primary ports to be deleted, which could render the Shared Uplink
Set without any Primary uplink ports.
• Under rare conditions, if the time setting on an enclosure was modified such that the HP VC 8Gb 20-Port
FC Module or the HP Virtual Connect 4Gb FC Module set the DHCP lease renewal date far in the future,
the module might stop renewing the lease, which might result in duplicate IP address assignments on the
network.
• After configuring LDAP authentication, users logging in that did not have Domain role permissions
received an error when attempting to access the Local Users page. The error was only a notification
because Local Users settings cannot be modified by users who do not have Domain role permissions.
Issues and workarounds
Issue
The detailed port statistics field cosq[N]_ucast_DroppedPkts incorrectly reports the number of per CoS queue
dropped packets on HP VC FlexFabric 10Gb/24-port Modules and HP VC Flex-10 10Gb Enet Modules.
Issue
The SetVCBase method fails when a Network Access Group is configured in a server profile.
Workaround
For more information and a workaround, see the HP website
(http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c
03805654).
Issue
After configuring LDAP authentication, users logging in that do not have Domain role permissions receive an
error when attempting to access the Local Users page. The error is only a notification because Local Users
settings cannot be modified by users who do not possess Domain role permissions.
Issue
If a HP ProLiant BL870c i2 server is present in bays 3 and 4 of a C3000 enclosure, then the Hardware
Overview page in VC Manager does not display the correct graphical picture of the server. VC Manager
manages the server properly. It is only the graphical image that is incorrect.
Issue
In a VC domain with a VC profile assigned to a HP ProLiant BL2x220 server blade, when the I/O module
connected to the dual-technology port is replaced with a module using single-blade technology, the OA
detects that the identity of the server changed, but VC does not detect the change. As a result, the OA does
not power on the server until VC updates the server configuration.
Workaround
To resolve the problem, unassign and reassign the profiles to the two server bays (for example, Bays 1a
and 1b), perform a hot-plug install of the server, or simulate a hot-plug install of the server using the OA