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

Virtual Connect Manager does not accept Onboard Administrator
credentials
If a VC Domain is being managed by VCEM, and the Onboard Administrator is brought out of
Virtual Connect Mode, the following error message appears the next time you log into Virtual
Connect Manager:
The HP Virtual Connect has lost its login credentials for the HP Onboard
administrator (OA). The OA may have been replaced or reset to factory
defaults. To ensure proper operation, these credentials must be
reestablished.
When Onboard Administrator credentials are provided, an error message appears stating that
the credentials are not valid. This situation can occur when:
•
Onboard Administrator is replaced or reset to factory default settings.
•
The clear vcmmode command was executed in the Onboard Administrator CLI.
•
The VC Ethernet modules were temporarily replaced by another BladeSystem c-Class
interconnect module.
To resolve this issue:
1.
Select the affected VC Domain, and put it into 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 report a Pending status.
5. Verify that the servers are operating correctly.
6. Access VCEM, and complete VC Domain Maintenance.
Unable to add VC Domain to a VC Domain Group
If the VC Domain is not the same as the VC Domain configuration group, then you might not be
able to add the VC Domain to the VC Domain Group. To correct this issue, verify that the VC
Domain meets the requirements for adding a VC Domain to a VC Domain Group. For more
information, see
“Requirements for adding a VC Domain to a VC Domain Group” (page 22) .
Also, a VC Domain might fail to add to the VC Domain Group for the following reasons:
•
Network issues
•
Invalid IP address
•
Insufficient credentials permission
•
Another VCEM external manager exists
To correct this issue:
•
Verify that you can ping from the command line of the VCEM server and log on to the Virtual
Connect Manager using the browser.
•
In a redundant environment, verify if the failover between an active and standby VC module
occurs. If so, wait until the failover completes and then perform rediscovery of Onboard
Administrator associated to the VC module.
•
VCEM requires Virtual Connect Manager credentials with full privileges to communicate to
Virtual Connect Module.
•
Access the Virtual Connect Manager CLI:
Virtual Connect Manager does not accept Onboard Administrator credentials 109