Filter
Top Products
Known issues 12
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.
• When an SSH key is uploaded using the GUI interface, user authentication fails. The user must enter
the password when logging in using SSH.
• 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.20 is not downward compatible with
previous versions, causing an issue when downgrading from v1.20 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.20 and a secondary VCM is running 1.16, the
primary VC Manager check-points the domain configuration (in v1.20 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.20 configuration file. Avoid running different firmware
versions on the primary and secondary modules in an enclosure.
• Virtual Connect modules with firmware revisions of v1.00 and v1.10 are not compatible and cannot
be upgraded within the c3000 enclosure. Modules must be upgraded in a c7000 enclosure, or
contact your HP representative for additional options. Virtual Connect modules with v1.15 and
v1.16 in a c3000 enclosure should be upgraded to v1.20 for full support 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 (Tools->Reset Virtual Connect Manager).
• Replacing the OA in an enclosure containing only one OA causes the OA to lose all of the Virtual
Connect configuration for the server blades. Server blades configured for VC-assigned MAC
addresses or WWNs are marked as "Profile Pending." Rebooting a server blade after replacing the
OA causes it to revert to the factory default MAC addresses. The user must re-enter the OA user
name and password to restart the VC Mode. Replacing a redundant OA does not result in this
situation.