HP XP Cluster Extension Software Administrator Guide

XP Cluster Extension provides the following error return codes for failover operations:
Prohibits an application service startup on the local system. This can be caused
by the inability of XP Cluster Extension to enable disk access, or misconfiguration
of the disk array environment.
local error
Prohibits an application service startup on any system in the local data center.
This error is returned if the disk state indicates that it makes no sense to allow
any other system connected to the same disk array to access the disks.
data center error
A global error is returned if the configuration or the disk state does not allow
an automatic application service startup process. In such cases, manual
intervention is required.
global error
When XP Cluster Extension is integrated, an error message string and integer value are displayed.
For the CLI, a return code is displayed. For more information, see “CLI commands” (page 41).
MSFC-specific error handling
XP Cluster Extension related messages are logged by MSFC to the following locations:
• cluster.log in the location "%windir%\Cluster\Reports"
• The XP Cluster Extension log file is named clxmscs.log.
• The XP Cluster Extension configuration tool log resides in the
%ProgramFiles%\Hewlett-Packard\Cluster Extension XP\log\ directory.
Resource start errors
MSFC configurations do not require a UCF.cfg file if the default COMMON objects are used
(recommended).
MSFC will fail the XP Cluster Extension resource on the local system if the clxpcf file is not present.
If the program is in a very early state of processing, the operation might fail and XP Cluster Extension
will not show the resource name in the error message.
Failover errors
XP Cluster Extension's integration with MSFC returns a local error and fails the resource if a
configuration error occurs. This could be a problem with the RAID Manager instance configuration
or an error, which will probably require starting the resource group on another system.
XP Cluster Extension resources return a data center error and fail the resource if the disk array
status indicates that the problem experienced locally would not be solved on another system
connected to the same disk array. This means all systems specified in the DC_A_Hosts resource
property or the DC_B_Hosts resource property would fail to bring the resource group online.
Depending on the resource group and resource property values, the resource tries to start on
different nodes several times. If the remote data center is down, this would look like the resource
group is alternating between the surviving systems. This happens until the previously mentioned
resource and resource group property values are reached or you disable the restarting of the
resource. This could be also the case if the ApplicationStartup resource property has been set to
FASTFAILBACK.
If a disk array state has been discovered that does not allow bringing the resource group online
on any system in the cluster, a cluster error would be reported and the resource would fail on all
systems. This could lead to the same behavior as described for a XP Cluster Extension data center
error.
Examples of such a state could be a SMPL state on both primary and secondary disks, a suspended
(PSUS/SSUS) state on either site, or a state mismatch in the device/copy group for this resource
group. None of the previously mentioned scenarios will allow automatic recovery because the XP
66 Troubleshooting