HP Insight Dynamics 6.2 Release Notes

Suggested action
Do not specify redundant paths for XP storage array volumes.
Data disk may not be presented at the end of provisioning when SAN Catalog Storage
Entry is specified
If you include the data volume and the boot volume in the same Storage Pool Entry when specifying
a SAN Catalog Storage Entry, the data volume may not be presented at the end of provisioning
using Insight Orchestration. When you view the Storage Pool Entry, the data volume is unmasked
(the Masked checkbox is unchecked).
Suggested action
Manually check the “Masked” checkbox for the data volume on the Storage Pool Entry screen.
mxsync fails with “Synchronization module com.hp.vse.lsa.mxsync.LsaMxsyncFactory is
not found” error
If Insight Dynamics is installed to a directory other than the default directory, mxsync will fail to
load the “Logical servers and associated SAN-based storage” module and exit with the error
“Synchronization module com.hp.vse.lsa.mxsync.LsaMxsyncFactory is not found.”
Suggested action
Modify the value of JarDirectory in the file <System Insight Manager Installation
Directory>\mxsync\mxsync\conf\module\lsm.xml to correctly point to the directory
containing the lsa-mxsync.jar file, <Insight Dynamics Installation Directory>/
lib/lsa.
Viewing or editing the logical server management properties file may cause failure of the
LSA service
Viewing or editing the lsa.properties file may write lock the file while the HP Logical Server
Automation service is running. This may cause a serious failure of the service.
Suggested action
Use a text editor that does not lock the file, such as Emacs, Notepad, or TextPad.
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.
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