HP 3PAR StoreServ Cluster Extension Software Administrator Guide

Line 31: Online status of Cluster Extension resources.
Line 32: Creating <CLX resource name>.online file to check resource health.
Line 33: End of the Cluster Extension execution process.
HP 3PAR StoreServ Storage log or sysmgr log
A task, identified by task IDs is generated for each operation in the 3PAR StoreServ Storage. Task
manager commands provides information regarding the tasks in the system.
For more information, see Managing Tasks section in HP 3PAR CLI Administrator’s Manual.
NOTE: Match the 3PAR StoreServ Storage time with the cluster node time so that tasks can be
easily mapped to Cluster Extension operations.
For detailed log messages from HP 3PAR StoreServ Storage, do the following:
1. Login with the 3parsvc user using HP 3PAR CLI.
2. Run showsys.
This will indicate the master node on that system.
3. On the CLI shell, enter copyfile <nodeid>:/var/log/tpd/sysmgr /tmp/xxxsysmgr.
If master node ID is 1, then copyfile 1:/var/log/tpd/sysmgr /tmp/sysmgr.
4. In the above example, the file sysmgr will be copied to the <SystemDrive:>\tmp directory.
Error return codes
HP 3PAR StoreServ Cluster Extension provides the following error return codes for failover operations:
DescriptionError return codes
Prohibits an application service startup on the local system.
This can be caused by the inability of HP 3PAR StoreServ
local error
Cluster Extension to enable disk access, or the
misconfiguration of the storage system environment.
Prohibits an application service startup on any system in
the local data center. This error is returned if the disk state
data center error
indicates that it makes no sense to allow any other system
connected to the same storage system to access the disks.
Windows clustering does not allow cluster-wide or
data-center-wide disabling of resources. This is local error
behavior.
Returned if the configuration or the disk state do not allow
an automatic application service startup process. Manual
global error
intervention is required in such cases. Windows clustering
does not allow cluster-wide or data-center-wide disabling
of resources. This is local error behavior.
Replication I/O between the primary and secondary
Remote Copy volume group is not started. Use HP 3PAR
Replication I/O not started error
StoreServ Management GUI or CLI to check if the
replication status is started or not. You can manually
start the Remote Copy replication using HP 3PAR StoreServ
Management GUI or CLI when required.
Replication I/O between the primary and secondary
Remote Copy volume group is started. Use HP 3PAR
Replication I/O starting error
StoreServ Management GUI or CLI to check if the
replication status is started or not. You can manually
start the Remote Copy replication using HP 3PAR StoreServ
Management GUI or CLI when required.
86 Troubleshooting