Operating Environment Software Manual

IMPORTANT: You can use cross-technology logical servers only if your storage is SAN-based.
Virtual machine logical servers can be moved to physical systems if the VM storage uses RDM.
Data store-based VMs cannot be moved across technologies.
In this release, SAN Catalog Storage Pool Entires and SAN Pre-populated Catalog Storage
Pool Entries are supported on servers with Virtual Connect logical servers only. Catalog storage
pool entries cannot be used with cross-technology logical servers that may be activated on an
ESX VM Host.
To allow flexibility and movement between underlying technology types, storage must be
presented to both the WWNs tied to the Virtual Connect server profile as well as to any ESX VM
Hosts that are potential targets for the logical server. Storage pool entries must be created within
the same portability group as the logical server(s) that will use the storage.
See “Defining storage for logical servers” (page 73) for more information.
Defining a network
You create a network definition for a cross-technology logical server in the same way as you do
for standard logical servers, using Create→Logical Servers… and specifying information on
the Network screen.
NOTE: To move cross-technology logical servers from physical to virtual systems and back,
ensure that at least one network in the Virtual Connect domain group is named identically to a
vSwitch on the ESX Host.
Unmanaging a cross-technology logical server
Unmanaging a cross-technology logical server requires additional steps. If the logical server is
active on a VM Host, and it has been active on a server with Virtual Connect, you must delete
the Virtual Connect profile using Virtual Connect Enterprise Manager after you unmanage the
logical server.
If the logical server is active on a server with Virtual Connect, and has been active on a VM Host,
you must delete the VM configuration file using vCenter after you unmanage the logical server.
Moving a cross-technology logical server
This section provides step-by-step instructions for moving a logical server from a physical system
to a virtual machine and back.
NOTE: Before you begin:
• Ensure that at least one LUN is commonly presented to all Virtual Connect generated WWNs
and VM Hosts.
In this release, catalog storage pool entries are supported on servers with Virtual Connect
logical servers only. Catalog storage pool entries cannot be used with cross-technology
logical servers that may be activated on an ESX VM Host.
• Ensure that at least one network in the Virtual Connect domain group is named identically
to a vSwitch on the ESX Host.
1. Create a user-defined Portability Group that includes a Virtual Connect domain group and
at least one ESX Host.
a. From the Virtualization Manager Physical and Virtual perspective, select a Virtual
Connect domain group and all selected ESX Host to include in the user-defined
Defining a network 69