Operating Environment Software User Manual

Suggested action

Systems Insight Manager Single-Sign-On is properly configured. Then rediscover the iLO or Onboard

Administrator on the Central Management System.

Logical server operations cannot be cancelled

After a logical server operation is started, you can view its status on the Report→Logical Server

Job Status... screen, but you cannot cancel it. Running jobs do not time out. If a job seems to be

running for a long period of time (more than two hours), the job may have completed but some

issues may have been encountered with the underlying software. The job will continue to run and

the logical server will be locked. The lock is released on the next restart of the Logical Server

Automation service.

Do not stop or restart Logical Server Automation service while operations

are in progress

Unpredictable results can occur if you stop or restart the LSA service while logical server operations

are in progress. “Error saving storage pool entry after Logical Server Automation service is restarted”

(page 83) is an example of one such result.

Suggested action

Check the Report→Logical Server Job Status... screen to make sure that no logical server operations

are in progress before stopping or restarting the LSA service.

Logical Server Automation service fails to start if TCP layer ports are in use

The HP Logical Server Automation service reads the TCP layer port from the file

lsaclient.properties. By default, the LSA service uses the following port numbers:

LSA_RMI_PORT=51001

LSA_JMS_PORT=51002

If either of these ports is currently in use, logical server management searches for another free port

number and, if found, updates the file and restarts the service. If a free port cannot be found, the

LSA service will fail to start with the following message, where nnn is RMI or JMS:

The nnn port {number} used by the Logical Server Automation

service is currently in use. Ensure that there is a free port,

edit the lsaclient.properties file to replace the port

in use with a free port, and restart the service.

Suggested action

Modify lsaclient.properties and replace the port in use with a free port, and restart the

service. To determine a free port, use the command netstat -A.

Logical Server Automation 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.

82 Troubleshooting