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

environment. To correct this issue, perform a rediscovery on the Onboard Administrator IP address
associated with the VC Module.
VCM does not accept Onboard Administrator credentials
If a VC Domain is being managed by VCEM, and the Onboard Administrator is brought out of
VC mode, the following error message appears the next time you log into VCM:
The HP VC 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 vcmode 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 VCM. Wait to be prompted for new Onboard Administrator credentials.
NOTE: You must have domain privileges to log in to VCM.
3. Provide the Onboard Administrator credentials, and then follow the VCM instructions.
4. In VCM, 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 31) .
Also, a VC Domain might fail to add to the VC Domain Group for the following reasons:
•
Network issues, specifically:
Configuration mismatches between VC Domains and VC Domain Groups ◦
◦ VC Domain Group with the latest version of firmware
•
Invalid IP address
•
Insufficient credentials permission
•
Another VCEM external manager exists
•
The models of VC modules installed in the VC Domain are different from those in the VC
Domain Group.
To correct this issue:
•
Verify that you can ping from the command line of the VCEM server and log on to the VCM
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 Systems Insight Manager
rediscovery of Onboard Administrator associated with the VC module.
166 Troubleshooting VCEM