HP Insight Virtualization Manager with Logical Server Management 6.1 User Guide

Use caution when renaming or moving a Virtual Connect domain group
Use caution when renaming or moving a Virtual Connect domain group, which is accomplished
by checking Change Logical Server Associations using the Tools→Logical Servers→Refresh...
menu selection. Do not use this functionality to merge Virtual Connect domain groups. This
functionality must only be used to reassociate logical servers to a new domain group name. Do
not specify an existing domain group for the New Domain Group Name, otherwise your logical
servers may become unusable.
Deactivate or move logical servers before replacing blade
Before you replace a blade in an enclosure that is currently hosting a logical server, move or
deactivate any logical servers that are active on the blade. After the new blade has been installed,
discovered, and licensed, perform the Tools→Logical Servers→Refresh menu selection for
Virtual Connect server resources. Then reactivate the logical servers on the blade or move them
back from the location to which they have been moved.
Unmanaging a logical server using a storage pool entry may result in an
inconsistent state
When you unmanage a Virtual Connect logical server that was previously activated, the
underlying VC profile, if it exists, is not deleted and the profile continues to use its WWN and
MAC addresses. If a storage pool entry was associated with the unmanaged logical server, the
WWNs that are still being used by the profile are replaced by newly allocated WWNs, so that
the maximum number of logical servers sharing the storage entry is not changed. The SAN
Administrator must present the LUNs to these new WWNs before they can be used. (Mark the
new WWNs as “Not Ready” on the Storage Entry screen to be sure they are not used prematurely.)
Suggested Action Delete the logical server to delete the underlying Virtual Connect profile and
allow the WWNs and MAC addresses to be available for reuse. HP recommends that you do not
use Unmanage Logical Server to unmanage a logical server that has been previously activated.
Unmanaging the logical server may result in an inconsistent state, and may render the storage
pool entries unusable. An exception to this recommendation is if you plan to manage the profile
using VCEM.
Synchronize clocks on the CMS, managed systems, and VMware vCenter
Ensure that time synchronization has been performed among the CMS, managed systems
(including ESX hosts), and VMware vCenter. Failure to do so results in errors in both vCenter
and Insight Dynamics software.
Suggested Action Use clock synchronization software such as the Windows Time Service or
the Network Time Protocol.
VM Host does not appear on move logical server target screen
If a VM Host does not appear on the Move: Assign Logical Servers to Target Hosts screen
in the Available Target Hosts and Rejected Target Hosts tables, or if a virtual machine fails
to be imported with a "cannot find VM" or "cannot find VM Host" message, check to see that the
VM Host is properly configured and has a UUID. To perform this check, view the HP SIM system
page for the VM Host and look for the UUID field.
Possible Cause If the UUID is null or missing, the VM Host will not appear in the logical server
management internal inventory. This means that the VM Host will not appear as an activate or
move target, and any virtual machines on that VM Host will not be importable.
Suggested Action Perform the following steps if vselog.lsm.log contains the error:
2010-03-05 12:58:41,675 [pool-8-thread-9] WARN app - (LSM) Populate VM Host
(15.2.9.3) failed with exception: LSM_ADPT_VMM_ERR_NO_VM_HOST_UUI
102 Troubleshooting