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

Failover error handling
P9000 Cluster Extension automatically fails over application services if the system the application
service is running on becomes unavailable. This also means that if a problem with the disk array
state occurs, an application service startup process will be stopped. The behavior of P9000 Cluster
Extension is highly configurable.
Depending on the customer setting, P9000 Cluster Extension is used to prevent application services
from starting automatically under the wrong conditions. Therefore, P9000 Cluster Extension will
return local, data center-wide, or even cluster-wide errors to prevent accidental access to the disk
array disk set.
P9000 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 P9000 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 P9000 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 72).
MSCS-specific error handling
P9000 Cluster Extension related messages are logged by MSCS to the following locations:
• %ClusterLog%\cluster.log.
• The P9000 Cluster Extension log file is named clxmscs.log.
• The P9000 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 P9000 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 P9000
Cluster Extension will not show the resource name in the error message.
Failover errors
P9000 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 RAID Manager instance configuration
or an error, which will probably require starting the resource group on another system.
P9000 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
100 Troubleshooting