HP Matrix Operating Environment 7.3 Update 1 Installation and Configuration Guide for Provisioning with Virtual Resources

allow existing system names. Although logical server management prevents you from using the
name of an existing system in HP SIM, if a host with that name is discovered after you create or
import the logical server, then HP SIM will display that system using the FQDN.
Suggested actions
Create a name for each logical server which will always be unique from any managed system
name.
Synchronizing the clocks on the hosts and virtual machines
Issue
If you are performing operations on ESX virtual machine logical servers, be sure that you have
synchronized the clocks on the hosts and virtual machines. If the VM hosts are managed by VMware
vCenter and the host clocks are not synchronized, some issues might occur while managing the
virtual machines that might affect logical servers.
Suggested actions
Use clock synchronization software such as the Windows Time Service or the Network Time Protocol
to synchronize the host clocks.
Recovering an inoperable logical server
Issues
On the Matrix OE visualization user interface a logical server is marked inoperable, or on the
logical server job status screen an error message reports that a logical server is inoperable.
Suggested actions
Review Table 4 (page 155) for several possible causes and suggested actions.
Table 4 Recovering an inoperable logical server
Suggested actionsPossible causes
Perform one of the following actions:The server with VC or VM host
resources associated with a logical
• Refresh the appropriate logical server resources (VC or VM) using
Tools→Logical Servers→Refresh....
server has been made unavailable
for further management operations.
Examples are:
• Reverse the operation that made the underlying server blade or VM host
unavailable for management operations. If the underlying resource is a blade,
• Using VCEM to remove a
domain group from management
consider restoring the domain group or bringing the domain group back from
maintenance mode. For a VM host, re-register the VM host with Insight Control
virtual machine management, or restart the VM host.
Refresh the appropriate logical server resources (VC or VM) using
Tools→Logical Servers→Refresh....
or to move a domain into
maintenance mode
• Using Insight Control virtual
machine management to
unregister or shutdown a VM
host
• Unmanage the inoperable logical server.
Perform the following sequence of steps:Both the blade and VM guest
resources of a cross-technology
1. Unmanage the inoperable logical server
logical server have been activated
2. Determine the underlying resources that is the intended instance, and delete
the other instance. Delete the underlying VM with Insight Control virtual machine
management, or delete the blade instance using VCEM.
1
and are operating simultaneously.
When blade or VM guest resources
associated with logical servers are
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
activated using VCEM or Insight
Control virtual machine
the integrity of the remaining instance cannot be verified then remove it and
recreate.
management, dialog boxes display
warning that such activation is not
recommended.
Troubleshooting procedures 155