HP 3PAR Cluster Extension Software Administrator Guide (5697-1429, March 2012)

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 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 Cluster
local error
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
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 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
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 Management GUI or CLI when
required.
When HP 3PAR Cluster Extension is integrated into the cluster software, an error message string
and integer value are displayed. For the CLI, a return code is displayed. For more information,
see “CLI commands” (page 68).
Log files
Log files assist you in locating and identifying problems. Timestamps, component IDs, and message
IDs are included.
• HP 3PAR Cluster Extension-related messages are logged by MSCS to the file %ClusterLog%
for Windows 2003. For Windows 2008, HP 3PAR Cluster Extension-related messages are
logged by MSCS to a file in the cluster log directory %SystemRoot%
• HP 3PAR Cluster Extension-related messages are logged by RHCS and SLE HA for each cluster
resource to the file /var/log/messages.
78 Troubleshooting