HP Virtual Connect Enterprise Manager 6.3 CLI Guide

As a result, VCEM APIs can report false job results such as, Completed with success, even
though the server profile changes have not taken effect. The ability of VCEM to manage server
profiles might also be affected for:
Creating an unsigned server profile
Editing of an assigned server profile
Assigning a server profile
Deleting a server profile
Unassigning a server profile
The following bay operations might also be affected:
False information might be displayed for the power status, server model, and the serial number
functions
Power buttons might not perform the expected operations
In addition, after logging in to the Virtual Connect Manager user interface, the following warning
message can appear:
The HP Virtual Connect has lost its login credentials for HP Onboard
Administrator (OA). OA may have been replaced or reset to factory defaults. To ensure proper operation, these
credentials must be reestablished
This situation occurs because VCEM relies on proper communication from the Virtual Connect
Manager to the Onboard Administrator to retrieve and change configurations, report statuses of
the physical devices inside the enclosure, and perform server power all on and off operations. To
correct this issue, restore communication between the Onboard Administrator and Virtual Connect
Manager by performing the following procedure:
1. Select the affected VC Domain, and start VC Domain Maintenance.
2. Log on to Virtual Connect Manager. Wait to be prompted for new Onboard Administrator
credentials.
NOTE: You must have domain privileges to log in to Virtual Connect Manager.
3. Provide the Onboard Administrator credentials, and then follow the Virtual Connect Manager
instructions.
4. Restart all servers with server profiles that present a pending status In Virtual Connect Manager.
5. Verify that the servers are operating correctly.
6. Complete VC Domain Maintenance either using the SDK APIs or the VCEM web interface.
After a server profile assignment, some connections defined in the server
profile are not functional
VCEM cannot identify if all Fibre Channel and Ethernet connections configured in a server profile
can be physically mapped to the physical ports of a server blade. It is possible that there are
Ethernet or Fibre Channel connections in the server profile that cannot be configured in the server
blade where the blade is assigned.
To correct this issue, perform either of the following options:
Manually move the affected server profile to a spare server blade that contains all the necessary
physical ports to receive the server profile.
Install the necessary mezzanine cards in the server blade to provide the physical port mappings
required by the server profile connections
After a server profile assignment, some connections defined in the server profile are not functional 87