HP Virtual Connect 3.51 Release Notes

Prerequisites 11
• Security Advisories for Firefox 3.0
(http://www.mozilla.org/security/known-vulnerabilities/firefox30.html)
Issue
Editing the SAN fabric should not allow changes to the fabric's I/O bay. The “Add Port” menu may show
incorrect menu entries instead of showing the port details only for the current or previously added bay entries.
If they are selected, the SAN fabric is not updated with the current modifications.
Issue
When multiple Internet Explorer 7 browser sessions are open to the Virtual Connect Manager application,
the VC GUI might hang.
Workaround
Add the following registry value:
[HKLM\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Inte
rnet Settings] "MaxConnectionsPerServer"=dword:6
By default, this registry value does not exist and Internet Explorer 7 defaults to the value of 2. Increasing
the value to 6 resolves the hanging issue. Internet Explorer 8 defaults to a value of 6, so this issue does
not occur. The Firefox web browser may also default to a higher value.
Issue
In a double-dense domain configuration, interconnect bays 7 and 8 should not be used to create an FC
fabric. The fabric should instead be created on bays 5 and 6. If a fabric is created on bays 7 or 8 using the
VCM CLI, an incorrect error message might appear, indicating "ERROR: Module not found" instead of
"ERROR: A fabric is not allowed to be created with the specified bay for a double-sense configuration".
Issue
When a server blade server port has multiple FlexNICs defined and one of the ports is defined as FCoE,
deleting the FCoE FlexNIC does not redistribute the bandwidth to other active FlexNICs, even though the GUI
indicates that this redistribution occurred.
Issue
VC allows mapping of non-supported iSCSI connections for NC522m Mezz ports 1-a and 2-a.
Issue
If a profile that is currently assigned to a server is modified so that Network connections or FCoE connections
are added or removed, VC might change the protocol (Ethernet or FCoE) for a particular Flex-10 interface
without properly reinitializing it. This can result in unexpected behavior.
Workaround
Unassign the profile, and then reassign the profile.
Prerequisites
IMPORTANT: If you have FCoE connections configured through a mezzanine card, see the
"Issues and workarounds (on page 6)" section for a workaround required to avoid a temporary
FCoE outage during firmware update.