HP Virtual Connect Enterprise Manager Software - Manual (Page 121)

In addition, after logging in to the Virtual Connect Manager user interface, the following warning
message might 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, 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:
1.
Select the affected VC Domain, and start VC Domain Maintenance.
2. Log in 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. In Virtual Connect Manager, restart all servers with server profiles that present a Pending
status.
5. Verify that the servers are operating correctly.
6. Access VCEM, and complete VC Domain Maintenance.
Systems Insight Manager customizations for VCEM have not taken place
VCEM customizations for both Systems Insight Manager menu and Systems Insight Manager System
and Events collections might not take place when installing VCEM in standalone mode.
To correct this issue from the Systems Insight Manager menu, access Options
→Managed
Environment, and click OK to apply VCEM customization to Systems Insight Manager menu and
Systems Insight Manager System and Events collections.
After a server profile failover, 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, because it is possible to have
Ethernet or Fibre Channel connections in the server profile that cannot be configured in the server
blade where it is assigned, causing those servers to not function.
To correct this issue, perform either of the following:
•
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.
Server profiles are not displaying physical port mapping and allocated
bandwidth information
VCEM does not display physical port mapping and allocated bandwidth information for the Ethernet
network connection in a server profile.
To correct this information, perform the following:
1.
Go to Virtual Connect Manager user interface.
Systems Insight Manager customizations for VCEM have not taken place 121