HP Virtual Connect Manager Version 1.10 Release Notes

Known issues 8
Known issues
In this section
General .................................................................................................................................................. 8
Fibre Channel and SAN boot .................................................................................................................... 8
User interface .......................................................................................................................................... 9
Firmware update.................................................................................................................................... 10
General
• During an Onboard Administrator failover, Virtual Connect Manager can lose communication with
the Onboard Administrator for as long as 15 minutes. During this time, Virtual Connect Manager is
not able to make profile changes to server blades or perform some enclosure administration
functions, such as powering servers on and off.
• Changes in the server RBSU can override Virtual Connect server profile settings for PXE (enabled or
disabled). If a change is made in RBSU, that change is not reflected in Virtual Connect Manager.
• To move a server profile from a device bay containing a storage blade to another bay, the storage
blade must first be removed.
• Do not create or modify a network name with a hyphen ("-") in the name. Only use characters that
are alpha-numeric (a-z, A-Z, 0-9) and the underscore ("_"). Virtual Connect Manager does not reject
names with a hyphen, but subsequent updates to the network fail without giving any error indication.
• RDP "rip and replace" does not work properly when using VC-administered MAC addresses
because RDP is tracking the server blades by MAC address rather than by the primary lookup key
(which can be set to serial number, MAC address, UID, or Asset Tag). To work around this issue,
manually redeploy the server blade.
Fibre Channel and SAN boot
• If a VC-FC module is connected to a Fibre Channel switch that does not support NPIV, the Virtual
Connect user interface performance will degrade significantly. If this occurs, disconnect the FC
switch, reconfigure the FC switch for NPIV support, and reconnect.
• To properly boot from SAN with some versions of Linux, change the QLogic HBA connection options
to "point to point only" in the QLogic BIOS configuration.
• The VC-FC module health status remains "good" during hardware reset and power cycle events
initiated though the OA. Although the state transition is not seen, the reset does occur.
• The VC-FC module port operational and speed statuses reflect the current configuration rather than
the operational status.
• Virtual Connect Manager does not provide an interface to force 1-Gb speed on the VC-FC module
uplink and downlink ports. However, the ports will auto-negotiate properly to 1 Gb.