HP Insight Dynamics 6.0 Update 1 Release Notes

compartment), using the Tools→Logical Servers→Copy... menu selection results in a null
pointer exception displayed on the Copy Logical Server screen. Subsequent attempts to copy a
logical server by selecting it in the Physical & Virtual or Logical Server perspectives also result
in this error.
Suggested action If a null pointer exception has been displayed, use the back arrow on your
browser to return to the previous screen. Log out of HP SIM and log in again, and be sure that
the LSA service is started before attempting to copy a logical server.
Error when manually restarting LSA service
If you manually restart the Logical Server Automation service, the error “Could not start the
Logical Server Automation service on Local Computer. The service did not respond to the start
or control request in a timely fashion.” is displayed.
Suggested action You can safely ignore this error. The service will restart after a short delay.
XML parsing error if new ESA attributes are not added to serverInfo.xml
Insight Dynamics 6.0 Update 1 contains version 317 of HP Extensible Storage & Server Adapter.
This version adds the rackName and rackPosition attributes for HP Operations Orchestration
Servers.
If you do not include the new attributes in serverInfo.xml, an XML parsing error is displayed
in the esa.log file.
Suggested action Make sure that the new ooServers attributes are present in the user-configured
serverInfo.xml file. The HP Extensible Storage & Server Adapter ESA-OO-RefImpl.zip
file contains an example of serverInfo.xml.
Reactivating and moving logical servers created on ESX 4x VM Hosts to ESX 3x VM Hosts
The new 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.
Process Resource Manager
Limitations
Creating and modifying configuration files with privilege elevation enabled is not supported
If privilege elevation is enabled in Systems Insight Manager, you can monitor Process Resource
Manager (PRM), but you may experience problems performing PRM operations. Specifically,
creating and modifying PRM configuration files may report success even though the operations
hang.
Suggested action Do not change PRM configuration files using the PRM user interface when
privilege elevation is enabled.
34 Issues and suggested actions