HP Virtual Connect 4.01 Release Notes

Prerequisites 9
While configuring a Shared Uplink Set in failover mode using the GUI, the GUI incorrectly allows uplink ports
that are designated as Primary ports to be deleted, which can render the Shared Uplink Set without any
Primary uplink ports.
Workaround
When using the VCM GUI to configure a Shared Uplink Set, do not attempt to remove the uplink port
designated as Primary.
Issue
In a VC domain with a VC profile assigned to a 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
reset server command. The problem can also be resolved if VC restarts, fails over, reboots,
receives a firmware update, or re-evaluates the server after an OA failover.
Issue
Under rare conditions, if the time setting on an enclosure is modified in such a way 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 in
the network.
Issue
Under certain circumstances, the checkpoint status icon in the GUI persists for a long time and is not cleared.
The CLI also shows a "Checkpoint Status: Invalid" status in the show domain command output. This
condition occurs periodically after a VCSU firmware upgrade of the VC module firmware.
Workaround
To resolve this issue, reset VCM on the primary module or reset the primary module using the OA.
Prerequisites
• Immediately review OA Customer Advisory c02639172 on the HP website
(http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c
02639172) to see if any recent changes made to the enclosure configuration are at risk of not being
preserved persistently. If you made changes using a non-Administrator user account, before the next
OA firmware upgrade or reset, execute the workaround documented in Customer Advisory
c02639172 to ensure that the enclosure configuration changes are being preserved persistently. The
issue described in Customer Advisory c02639172 is resolved with OA 3.21 and later.
• The lowest VCEM 7.2 support compatibility mode is now set to VC 3.30.
• If you are planning to use VC 4.01 firmware in a VCEM environment, HP recommends upgrading to
VCEM v7.2. For more information about the VC firmware that is compatible with VCEM, see the Virtual
Connect Enterprise Manager User Guide on the HP website