Insight Dynamics 6.1 Release Notes

menu and press the Insert Pool Entry button. Note that the newly created logical server is
not identical to the deleted logical server. When a new logical server is created and activated,
it is assigned new MAC addresses. If you are using Virtual Connect virtual identifiers, the
new Virtual Connect profile is assigned a new serial number and UUID.
6. Activate the new logical server using the Tools→Logical Servers→Activate... menu
selection.
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 running HP-UX
or HP OpenVMS not supported” (page 19) for a limitation on defining 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 (on a 64-bit CMS), the HP Logical Server Automation service may run
out of memory and display an out of memory error in the /logs/hp_lsa_service.log file.
The error is similar to the following:
INFO | jvm 1 | 2010/03/08 19:15:14 |
java.lang.OutOfMemoryError: GC overhead limit exceeded
Suggested action Modify the configuration file to increase memory allocation, as follows.
1. Modify the configuration file in the default location at C:\Program Files\HP\
VirtualServerEnvironment\conf\hp_lsa_service.conf.
2. Increase the value of wrapper.java.maxmemory=1024. HP suggests a value of 2048.
Minor issues
Performing operations on logical servers outside of Virtualization Manager may cause
incorrect information to be displayed
If you use tools other than Virtualization Manager to manage logical servers, modifications to
the underlying resources managed by logical server management are not immediately reflected
in the logical server.
For example, if you modify the power state of a managed resource outside of logical server
management, the power state of the logical server is displayed incorrectly until logical server
management resets its data.
Suggested action Wait several minutes for the logical server to reset its data, or use
Tools→Logical Servers→Refresh... to manually refresh server resources.
Logical server management 31