HP Virtual Connect Version 2.33 Release Notes

Known issues 12
Known issues
General
• No System Log message is logged for FC contact name changes.
• For server or I/O interconnect hardware changes involving adding or removing Flex 10
functionality, the profile assigned to a server or server bay must be removed, all hardware changes
performed, and the profile reassigned. Otherwise, indeterminate network operation might result.
• After a configuration is changed, the VC Manager can take up to 90 seconds to save the new
information to non-volatile storage. If power is removed during this update, configuration information
might be lost. A new icon on the Virtual Connect Manager banner line indicates that a configuration
update is in progress or that the backup module has not been updated to the current configuration
changes.
• During an Onboard Administrator failover, VC Manager can lose communication with the Onboard
Administrator for several minutes. During this time, VC Manager cannot make profile changes to
server blades or perform some enclosure administration functions, such as powering server blades
on and off.
• When operating in a redundant OA environment and the user sends a "Transition Standby to
Active" request to the standby OA, the communication between Virtual Connect Manager and the
active OA might be lost. To restore communication, reset the Virtual Connect Manager from the
Tools pull-down menu.
• Replacing the OA in an enclosure containing only one OA causes the OA to leave VC mode. This
mode change requires the VC Manager to re-establish credentials with the OA. During this process,
VC Manager rewrites all server settings and sets the state of the servers to "profile recovered." There
should not be any disruption to the servers, but the administrator should be sure that all servers have
the correct MAC addresses and WWNs. Powering off the server clears the "profile recovered" state.
If any servers are rebooted or power-cycled while the credential recovery occurs, the MAC
addresses and WWNs might be returned to the factory default settings.
• If an enclosure import is attempted with a server blade in a failed state, VC Manager might report
an erroneous error. If the import completes, close the browser and log in again to verify the import
was successful. Use the OA to verify the working state of all server blades.
• When scripting CLI commands, only a single scripting client should perform remote management
operations to a remote VC Manager. If multiple scripting clients are used to perform a heavy load of
CLI commands to a single VC Manager, some management commands might fail. In some cases, the
primary module might need to be reset to recover properly.
• An unsupported state occurs when a VC-Enet module is replaced physically with a non-VC Ethernet
interconnect module without administrative removal of the module from the VC domain. During this
state, if either the Help/About HP Virtual Connect Manager page or Firmware Management page of
the VC Manager GUI is opened, the string, "Loading...," appears indefinitely instead of the
firmware version number for each module in the VC domain.