Software Owner's manual

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 24).
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 with the VC module.
• VCEM requires Virtual Connect Manager credentials with full privileges to communicate to
Virtual Connect Module.
• Access the Virtual Connect Manager CLI:
1. Telnet in to the Virtual Connect Manager using an SSH connection such as SSH
[e-mail], where xxx.xxx.xxx.xxx is the VC Domain IP address.
2. To determine the user name of the external manager account, enter show
external-manager in the Virtual Connect Manager Command User Interface. The
status of the external manager name appears.
For more information, see the HP Virtual Connect Command Line Interface User Guide.
Unable to add an unconfigured VC Domain to a VC Domain Group
If you are unable to add an unconfigured server to a VC Domain Group, 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 24).
Cannot access VC Domain from Virtual Connect Manager after a data
migration has been performed
If, after performing data migration, you are running Virtual Connect Manager and try to access a
VCEM-managed VC Domain, the following error message appears:
VC Domain locked by Virtual Connect Enterprise Manager <CMS IP address>.
To resolve this issue:
1. Go to the CMS and invoke the MS-DOS command window.
2. Change directory into the <DRIVE>\<VCEM INSTALLATION FOLDER>.
126 Troubleshooting VCEM