HP StorageWorks XP Cluster Extension Software Administrator Guide (T1656-96035, April 2010)

MSCS-specific error handling
XP Cluster Extension related messages are logged by MSCS to the following locations:
• %ClusterLog%\cluster.log.
• 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
MSCS configurations do not require a UCF.cfg file if the default COMMON objects are used
(recommended).
MSCS 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 MSCS returns a local error and fails the resource if a
configuration error occurs. This could be a problem with the XP 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 XP disk array
status indicates that the problem experienced locally would not be solved on another system connected
to the same XP 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 an XP 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 an 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 group for this resource group.
None of the previously mentioned scenarios will allow automatic recovery because the XP Cluster
Extension resource cannot decide which copy of the data is the most current copy. In those cases, a
storage or cluster administrator must investigate what happened to the environment.
In any case, restarting a failed resource group without investigating the problem is not recommended.
A failed XP Cluster Extension resource indicates the need to check the status of the XP disk pair on
each copy and decide whether it is safe to continue or not.
Figure 11 on page 154 shows examples of an incompatible XP disk pair state shown in the
clxmscs.log file. The same messages can be found in the MSCS cluster log file if the XP Cluster
Extension LogLevel object is set to INFO; this, however, requires creating a UCF.cfg file.
XP Cluster Extension Software Administrator Guide 153