Operating Environment Software User Manual

Table 10 Recovering an inoperable logical server (continued)
Suggested actionPossible cause
the VM Host with Insight Control virtual machine
management, or restart the VM Host.
Refresh the appropriate logical server resources (Virtual
Connect or Virtual Machine) using Tools→Logical
Servers→Refresh....
• Unmanage the inoperable logical server.
Perform the following sequence of steps:Both the blade and VM guest resources of a
cross-technology logical server have been activated and
1. Unmanage the inoperable logical server
are operating simultaneously. When blade or VM guest
2. Determine which of the underlying resources is the
intended instance, and delete the other instance. Delete
resources associated with logical servers are activated
using VCEM or Insight Control virtual machine
the underlying virtual machine with Insight Control virtual
management, dialog boxes appear warning that such
activation is not recommended.
machine management, or delete the blade instance using
VCEM.
1
3. Verify the integrity of the remaining instance; if necessary,
restore the remaining instance from backup and
unmanage and re-import the recovered instance. If the
integrity of the remaining instance cannot be verified
then remove it and recreate.
Inoperable logical server appears immediately after a
failure of the HP Logical Server Automation service or of
1. Unmanage the inoperable logical server.
2. Re-import the logical server.
the entire CMS. Partially completed operations, such as
move operations, will not resume after the LSA service or
CMS restarts, and the CMS may not be able to
synchronize the state of the recovered underlying resource
with the logical server.
For an ESX virtual machine logical server, unregister the
virtual machine using Insight Control virtual machine
Logical server is marked inoperable during a roll back of
virtual machine registration after credentials were not
retrieved from Systems Insight Manager. management (VMM). For a Hyper-V virtual machine logical
server, use the VMM CLI to unregister the virtual machine:
1. CD to the installed VMM directory and CD to
clientapi\bin
C:\Program Files\HP\Insight Control virtual
machine management\clientapi\bin
2. Authenticate the session using the “adminlogin.cmd”
command:
C:\Program Files\HP\Insight Control
virtual machine
management\clientapi\bin>adminlogin.cmd
Login successful.
3. Find the VM URI or configuration path “cli getVmIds”
C:\Program Files\HP\Insight Control
virtual machine
management\clientapi\bin> cli getVmIds
vm://15.1.50.205/C:\VSE_VirtualMachines\vsels_ls-hyperv-01\
Virtual
Machines\880401BA-5024-4E76-9CD3-AA5F706F3332.xml
4. Unregister the virtual machine using “cli unregisterVm
–vm “vmUri”
C:\Program Files\HP\Insight Control
virtual machine
management\clientapi\bin>cli unregisterVm
-vm "v
m://15.1.50.205/C:\VSE_VirtualMachines\vsels_ls-hyperv-01\
Virtual
Machines\880401BA-5024-4E76-9CD3-AA5F706F3332.xml
ok
C:\Program Files\HP\Insight Control
80 Troubleshooting