HP Virtual Connect Manager Version 1.31 Release Notes and Compatibility Matrix

Known issues 13
Known issues
General
• For configuration changes, the VC Manager can take up to 90 seconds for the new information to
be saved to non-volatile storage. Configuration information might be lost if power is removed during
this update. A new icon has been added to the Virtual Connect Manager banner line that indicates
a configuration update is in progress or if the backup module has not been updated to the current
configuration changes.
• The VC Manager domain configuration database in v1.31 is downward compatible with 1.2x
versions unless the double-dense server blade option or the Multiple Enclosure Beta configuration has
been enabled. If either of these options are enabled, the configuration is lost.
For example, if a primary VC Manager is running v1.31 and a secondary VC Manager is running
v1.2x, the primary VC Manager check-points the domain configuration (in v1.31 format) to the
secondary VC Manager. If a failover causes the secondary VC Manager to become the primary, it
does so with only the v1.2x feature set. If double-dense blades are enabled, then the initialization
fails with no configuration.
• When updating the VC Manager firmware, the prompt for file downloads to a local system might be
blocked by the browser security setting.
• During an Onboard Administrator failover, VC Manager can lose communication with the Onboard
Administrator for several minutes. During this time, VC Manager is not able to make profile changes
to server blades or perform some enclosure administration functions, such as powering server blades
on and off.
• The OA firmware CLI command update all with VCM Mode causes the VC domain to be lost,
and it must be recovered using OA reset and VCM import of a previous configuration file. This OA
command should not be used if VC Manager is active. This defect has been fixed in OA v2.25, but
could be triggered while upgrading to OA v2.25.
• When operating in a redundant OA environment, after the initial import of the enclosure and
transition to Virtual Connect mode, the standby OA should be reset to ensure proper configuration. If
not reset, a failover to the standby OA results in loss of communication between the Virtual Connect
modules. This problem is resolved in OA releases after OA v2.20.
• 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 ensure all servers have the
correct MAC addresses and WWNs. Powering off the server clears the "profile recovered" state. If