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

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 P9000 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
P9000 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 P9000 Cluster Extension resource indicates the need to check the status
of the disk pair on each copy and decide whether it is safe to continue or not.
“Incompatible disk pair state ” (page 101) shows examples of an incompatible disk pair state shown
in the clxmscs.log file. The same messages can be found in the MSCS cluster log file if the
P9000 Cluster Extension LogLevel object is set to INFO.
TIP: Use a UCF.cfg file to set the LogLevel object.
Figure 8 Incompatible disk pair state
MSCS-specific error handling 101