HP Virtual Connect Manager Version 1.21 Release Notes and Compatibility Matrix

Known issues 11
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 time. 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 CLI set ldap command IpAddress option supports only an IP address. This
command option does not support the DNS name of the directory server as stated in the Command
Line help and CLI user guide.
• The VC Manager domain configuration database in v1.21 is not downward compatible with 1.1x
versions, causing an issue when downgrading from v1.21 or in an environment where the primary
and secondary VC Managers are at different firmware levels.
For example, if a primary VC Manager is running v1.21 and a secondary VCM is running v1.16,
the primary VC Manager check-points the domain configuration (in v1.21 format) to the secondary
VC Manager. If a failover causes the secondary VC Manager to become the primary, it is unable to
initialize because it cannot interpret the v1.21 configuration file. Avoid running different firmware
versions on the primary and secondary modules in an enclosure.
• Install only VC-Ethernet modules running v1.20a firmware or higher in HP BladeSystem c3000
enclosures. If all VC module firmware is below v1.20a, use the following steps to update the
firmware:
1. Login to Virtual Connect Manager.
2. Import the VC Domain.
3. Install and activate firmware v1.20a or higher using the VC Manager Firmware Update.
4. Delete the VC Domain. This step is necessary for the identification of the c3000 enclosure.
• 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, 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 server blades on and off.
• When operating in a redundant Onboard Administrator environment and the user requests a
"Transition Standby to Active" to the standby Onboard Administrator, then communication between
the Virtual Connect Manager and the active Onboard Administrator 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 VCM to re-establish credentials with the OA. During this process, the VC
rewrites all server settings and sets the state of the servers to "profile recovered." There should not be