HP Virtual Connect 3.60 Release Notes

Fixes 6
• Resolved an issue where VC or VCEM changed the boot order with the FC HBA boot parameters being
configured, and the end result was not what was expected.
• Resolved an issue where a pair of FlexNIC interfaces might experience failure to establish connectivity
due to addition or removal of FCoE connections in the server profile that resulted in those interfaces
changing their mapping from Ethernet to FCoE connection (or vice versa).
• Resolved an issue where using the HP BLc Virtual Connect 1Gb RJ-45 Small Form Factor Pluggable
Option Kit (Part Number 453154-B21) or HP BLc VC 1Gb SX SFP (Part Number 453151-B21) on a HP
VC Flex-10 10Gb Ethernet Module for c-Class BladeSystem caused Cyclic Redundancy Check (CRC)
errors during normal operation after a period of time, and then the link might go down. This issue only
occurred with the HP VC Flex-10 10Gb Ethernet Module. When the link went down, Virtual Connect
reported the link as down. However, the link to the external switch was still maintained. This fix resolved
the Customer Advisory c03367942.
• Resolved an issue where OpenSSH used by VC was vulnerable to NIST alerts CVE-2008-5161 and
CVE-2008-1483.
• Resolved an issue where the Apache HTTP Server used by VC was vulnerable to the NIST alert for
Denial Of Service Vulnerability CVE-2011-3192.
• Resolved an issue where the boot parameter might be incorrect when VC or VCEM changed the boot
order using FC HBA boot parameters to configure Port 2 as primary and Port 1 as secondary.
• Resolved an issue where VCM might enable server ports with no network connections. For example, if
a simple server profile had only one Ethernet connection, which maps to LOM1, then only LOM1 should
be enabled. However, both LOM1 and LOM2 were enabled.
• Resolved an issue where both the GUI and CLI allowed restoring from a configuration file when a
domain existed and server blades were powered on, which could result in duplicate MACs or WWNs
on the network or SAN.
• Resolved an issue when Upgrading VC FlexFabric firmware from 3.15, 3.17, or 3.18 to a newer
version might result in a temporary FCoE outage.
This behavior was limited to systems using HP ProLiant or Integrity server blades with a FlexFabric
Mezzanine adapter and a corresponding FCoE connection to an HP VC FlexFabric 10Gb/24-port
module. This behavior did not appear for FCoE connections using an embedded FlexFabric adapter
(LOM).
For more information, see Customer Advisory c02950493 on the HP website
(http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02950493).
• Resolved an issue for the Shared Uplink Sets screen, where the list of networks on the Associated
Networks tab might not be displayed in the correctly sorted order.
• Resolved an issue when VC was used and Integrity BL870c i2 or BL890c i2 Server Blades were present,
after an OA was reset the OA occasionally displayed factory-assigned WWNs and MAC addresses for
the auxiliary blades in a multi-blade server, even though VC-assigned values existed. This problem does
not affect the operation of the server. The server blades have and operate with the correct VC-assigned
WWNs and MAC addresses.
• Resolved an issue for Virtual Connect release 3.0x or later, where the Server Admin user was not able
to modify the IGMP Snooping settings. This known issue was related to the authorizations of the Server
Admin user in the security token being passed between VC software components.
• Resolved an issue where editing the SAN fabric should not allow changes to the fabric I/O bay. The
“Add Port” menu might show incorrect menu entries instead of showing the port details only for the