Insight Dynamics 6.1 Release Notes

Imported Integrity VM logical servers with file-based storage and Windows or Linux guests are not
supported
An Integrity VM virtual machine can be imported as a logical server if the Integrity VM uses
direct-mapped SAN storage, which is similar to RDM storage on ESX virtual machines. File-based
storage is not supported for Integrity VM virtual machines.
In addition, the imported Integrity VM virtual machine guest must have an HP-UX operating
system type. Windows and Linux guests are not supported.
Note that logical server management does not prevent you from importing a logical server with
Windows or Linux guest operating system types or file-based storage.
Reactivating and moving logical servers created on ESX 4x VM Hosts to ESX 3x VM Hosts
The ESX 4 virtual hardware version prevents virtual machine logical servers that were first
activated on an ESX 4x VM host from being moved or reactivated on an ESX 3x VM host.
ESX 4x supports virtual hardware version 4 and version 7 VM guests, but ESX 3x supports only
version 4 VM guests.
You can successfully move a virtual machine logical server first activated on ESX 3x to an ESX
4x VM host. If you attempt to move a logical server first activated on ESX 4.x to an ESX 3.x VM
host, logical server management checks the version and rejects the targets correctly.
Configure logical server storage for multiple storage ports before activation
If you modify a storage entry to add additional ports (to implement multi-pathing of storage)
and then attempt to reactivate its associated Virtual Connect logical server, the activation fails
with the error "No such fabric in VCEM” and the logical server can no longer be activated. This
issue occurs only if the storage entry is associated with a logical server, and the logical server
has been previously activated.
To avoid this problem, HP recommends configuring the logical server's storage for multiple
ports before activating the logical server, and using either SAN zoning or storage presentation
to limit the server's access to a single path as needed. If you configured the logical server with
one port, activated the logical server, and now need to add additional ports, perform the following
steps.
Suggested action
1. Ensure that the logical server's storage entry has been inserted into the storage pool. Pool
entries are listed in the Storage Pool Entries table viewable by selecting Modify→Logical
Server Storage Pools....
If you are unsure if the logical server's storage entry is a pool entry, select the logical server,
then use the Modify→Logical Server... menu selection and select the Storage tab. The
Storage Assignments table shows the storage entry for the logical server. If the Modify button
is not available (and only the View button is shown), then the storage entry is already in the
storage pool, and you can continue to step 2. If the Modify button is available, click Modify
to view the next screen. Check the "Insert Storage Entry into Pool" checkbox at the top of
the screen, and click Save.
2. Deactivate the logical server if it is currently active, using Tools→Logical
Servers→Deactivate....
3. Use Delete→Delete Logical Server... to delete the logical server. The storage pool entry is
not deleted. (You will recreate the logical server in step 5.)
4. Modify the storage pool entry using the Modify→Logical Server Storage Pools... screen.
Select the storage pool entry noted in step 1 and press the Modify button. Change the storage
pool entry to add additional ports as needed, and click Save.
5. Use the Create→Logical Server... screens to recreate the logical server. On the storage
screen, select the storage pool entry noted in step 1 from the Select Pool Entry drop-down
30 Issues and suggested actions