HP StorageWorks P9000 Cluster Extension Software Administrator Guide (TB534-96009, February 2011)

8 Troubleshooting
To troubleshoot problems with P9000 Cluster Extension, you must understand Continuous Access
environments. Many issues can be attributed to incompatible disk pair states. See the Continuous
Access and RAID Manager documentation before assuming that a problem has been caused by
P9000 Cluster Extension.
CAUTION:
P9000 Cluster Extension cannot handle device/copy group states automatically and correctly
when they result from manual manipulations. P9000 Cluster Extension will try to automatically
recover suspended RAID Manager device/copy group states if the AutoRecover object is set to
YES. However, if the recovery procedure experiences a problem, P9000 Cluster Extension will
not stop unless fence level DATA is used or the ApplicationStartup object is set to RESYNCWAIT.
Therefore, ensure that the device/copy group PAIR state has been recovered before the next failure
occurs.
Always disable automatic application service failover when resynchronizing disk pairs. A failure
of the resynchronization source while resynchronizing can lead to unrecoverable data on the
resynchronization target. The resynchronization process does not copy data in transactional order.
For more information, see “Implementing rolling disaster protection” (page 93).
P9000 Cluster Extension log files
P9000 Cluster Extension provides log messages to the cluster software as well as to the P9000
Cluster Extension log file. The P9000 Cluster Extension log file includes disk status information.
• The P9000 Cluster Extension log file is located in the following directories:
Linux
/var/opt/hpclx/log
Windows
By default, the location is defined as:
%ProgramFiles%\Hewlett-Packard\Cluster Extension XP\log\
• For the configuration tool, the clxXPcfg.log file resides in:
%ProgramFiles%\Hewlett-Packard\Cluster Extension XP\log\
If the log file needs to be cleared and reset, for example, to reduce disk space usage, archive the
log file and then delete it. A new log file is generated automatically.
For information about log levels, see “LogLevel” (page 82).
Start errors
Start errors can occur when the path to the RAID Manager binaries has not been set in the PATH
environment variable. If a user configuration file is not found in the correct directory location,
P9000 Cluster Extension returns a local error.
A start error occurs if the APPLICATION name tag value in the P9000 Cluster Extension resource
configuration file does not match the service name (RHCS) or the App value of P9000 Cluster
Extension resource (SLE HA).
P9000 Cluster Extension returns a local error if it does not find the P9000 Cluster Extension resource
configuration file for in the correct directory location (RHCS and SLE HA).
P9000 Cluster Extension log files 99