HP Matrix Operating Environment 7.3 and 7.3 Update 1 Logical Server Management User Guide

After unmanaging a logical server with a shared storage pool entry, the logical server may be
automatically re-imported in a subsequent refresh unless the associated storage pool entry is deleted.
Immediately after unmanaging a logical server, optionally modify the shared storage pool entry
to remove the unmanaged logical server's WWNs (if not using SPM). This step is optional since
the WWNs will be considered in use by an Unknown logical server; another logical server will
not be able to re-use those WWNs. It does contribute to the Sharer count for the storage pool
entry, and thus Unmanage has this different behavior than Delete. (If the storage pool entry is
defined as part of the logical server and is not shared, the storage pool entry is automatically
deleted when the logical server is unmanaged).
NOTE: If you unmanage a cross-technology logical server that was active on both a server with
Virtual Connect and a VM Host at different points in time, be sure to remove the corresponding
Virtual Connect profile or VM Guest configuration files that will no longer be used.
Import
The Tools→Logical Servers→Import... menu selection imports the definition for an existing physical
server or virtual machine and creates an active logical server with that definition.
Importing a logical server allows you to manage the resource or system using the logical servers
interface in Matrix OE visualization. If you decide you no longer want to manage a particular
resource or system, you can unmanage the logical server.
• You can import an ESX, Hyper-V, or HP-UX vPars and Integrity VMs (with file-based or
SAN-based storage) or a server with Virtual Connect. The system that you are importing can
be powered on or powered off.
• You can select the portability group into which the imported logical server is created.
The list of choices is based on what is being imported. For example, if a server with Virtual
Connect is being imported, then only portability groups that contain that VC Domain Group
are displayed as valid choices (this display includes the default portability group, as well as
any user-defined portability groups).
If an ESX VM is being imported, then only portability groups with ESX members are displayed.
NOTE: If a pre-existing SPE if found to be a match to the server with Virtual Connect during
import, then the portability group that the SPE is in dictates the portability group for the imported
logical server. The portability group menu is disabled.
• The resulting logical server is automatically activated, but maintains the powered on or off
state that existed before it was imported.
• The virtual machine guest or server with Virtual Connect does not need to be provisioned with
an operating system before it is imported.
• Import operations are supported for HP-UX vPars and Integrity VMs that contain physical
(whole) disks on a FC SAN, virtual disks in an SLVM volume group or NPIV storage.
• On import of a virtual machine, you can select the appropriate portability group (selecting
from among those containing the VM Host).
NOTE: Multiple datastores are supported for a variety of VMware ESXi and Hyper-V
environments. All storage volumes for HP-UX vPars and Integrity VMs must use the same datastore,
and Hyper-V Linked Clone disks must use the same datastore. Those virtual machines must be using
a single datastore for import to succeed.
Manage storage pools and tags
The Modify→Logical Server Storage Pools... menu selection allows you to manage entries in a
preexisting storage pool for a selected portability group. You can select these entries as part of
the storage configuration for a Virtual Connect logical server or a virtual machine logical server.
14 Managing logical servers