HP Virtualization Manager with Logical Server Manager 6.2 User Guide

Suggested action Do not shut down or restart the HP Logical Server Automation service while
operations are being performed on logical servers. In this specific case:
1. Sign out of Insight Dynamics and close the browser window.
2. Open a new browser window and sign into Insight Dynamics.
3. Retry the operation.
Restart Logical Server Automation service after VMware vCenter failure
After a VMware vCenter failure, information about ESX Hosts and virtual machines in the logical
server database is not updated, and a refresh of logical server resources may run for longer than
30 minutes or time out in the browser.
Suggested action After vCenter is restarted, use the Report→Logical Server Job Status...
menu selection to make sure that there are no logical server operations in progress. Then, restart
the Logical Server Automation service.
Profile is created but not associated with a logical server when service is
stopped during logical server activation
If the first activation of a new logical server is in progress when the HP Logical Server Automation
service is stopped, the logical server definition may be left in a state where the Virtual Connect
profile has been created but is not associated with the logical server. When the logical server is
in this state, an attempt to activate it will fail with the following error:
Unable to create profile {profile name}. (Cannot perform server profile operation because:
Server profile name {profile name} is duplicate. Another server profile with the same name
already exists in VCEM. Verify all the server profile information is correct
and perform the operation again.)
IMPORTANT: This error also occurs during the first activation of a logical server if the designated
Virtual Connect profile name is assigned to an existing profile. In this case, following the suggested
action to delete the underlying profile will result in a loss of data if the profile is in use. To avoid
data loss by accidentally deleting an existing profile, follow steps 1 and 2 below to verify that
the activate operation did not successfully complete and that the Virtual Connect Profile was
created as part of the failed operation.
Suggested action
1. View the status of the activate logical server job using the Report→Logical Server Job
Status… menu selection from the lower, gray menu-bar. Verify that the activate logical
server job did not complete successfully.
2. Verify that the underlying Virtual Connect profile definition is consistent with the logical
server definition.
a. View the logical server definition using the Report→View Logical Server Details…
menu selection. Note the Managed Resource Name.
b. View the Virtual Connect profile by selecting Tools→Integrated Consoles→Virtual
Connect Enterprise Manager (VCEM)… from the upper, blue menu-bar. From the
Server Profiles tab, select the Virtual Connect profile and click Edit…
3. Delete the Virtual Connect profile using Tools→Integrated Consoles→Virtual Connect
Enterprise Manager (VCEM)… and selecting the Server Profiles tab. Select the profile,
and click Delete....
4. Activate the logical server using Tools→Logical Servers→Activate... from the lower, gray
menu-bar.
108 Troubleshooting