HP Insight Dynamics 6.2 Release Notes

add SLVM VGs to the storage pool on the VM Host for the CreateVirtual Disk operation to run
successfully. Local storage is not supported for Integrity VM virtual machines.
In addition, the Integrity VM virtual machine guest must have an HP-UX operating system type.
Windows and Linux guests are not supported.
Logical servers upgraded from Insight Dynamics 6.0 and 6.1, which allowed physical SAN disk
storage and Windows or Linux guest operating system types for Integrity VM logical servers, will
have limited features; for example, they can be moved and powered on and off.
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.
Multi-initiator N-Port ID Virtualization (NPIV) features on Integrity blades running HP-UX and HP
OpenVMS
See “Multi-initiator N-Port ID Virtualization (NPIV) features on Integrity blades are not supported”
(page 19) for a limitation on defining storage pool entries.
Major issues
Unable to get detailed disk information on Microsoft Hyper-V VM host with a QLogic HBA
See “Unable to get detailed disk information on Microsoft Hyper-V VM host with a QLogic HBA”
(page 15) for information about downloading the QLogic HBA driver for Windows. Without this
driver, logical server management fails to operate correctly on Hyper-V cluster shared volumes
and cluster volumes with a QLogic driver.
Using a remote CMS database with components that use ESA for storage provisioning and server
operations
See “Using a remote CMS database with components that use ESA for storage provisioning and
server operations ” (page 16) for information about an issue that may affect logical server
operations.
LSA service may run out of memory on large scale systems
On large scale systems, with large numbers (1000+) of managed nodes and/or large numbers
(1000+) of logical servers on a 64-bit CMS, the HP Logical Server Automation service may run
out of memory and display out of memory errors in the /logs/hp_lsa_service.log or /logs/
vselog.lsm.log file. You may see the following errors:
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: PermGen space
Suggested action 1
To correct the GC overhead limit and/or Java heap space errors, modify the configuration file to
increase memory allocation, as follows.
1. Modify the configuration file (shown in the default location) at C:\Program Files\HP\
Virtual Server Environment\conf\hp_lsa_service.conf.
2. Increase the value of wrapper.java.maxmemory=1024. HP suggests a value of 2048.
3. Restart the HP Logical Server Automation service.
Logical Server Management 31