HP StorageWorks EVA Cluster Extension Software Administrator Guide (T3667-96045, April 2010)

(for example the cluster service) have not recognized the %HPCLX_EVA_PATH% variable. To fix
this problem, restart the cluster service.
• A start error occurs if the APPLICATION name tag value in the EVA Cluster Extension resource
configuration file does not match the service name (RHCS) or the EVA Cluster Extension resource
App (SLE HA).
• If an error occurs because needed components of EVA Cluster Extension are not available, a file
is generated that could help with troubleshooting. The file is clxlog.log. It may be in any dir-
ectory, but is usually in the working directory of the operating system (%SYSTEMROOT%).
• EVA Cluster Extension returns a local error if any of the following occurs:
• EVA Cluster Extension does not find the user configuration file for clxevarun in the correct
directory location.
• EVA Cluster Extension does not find the EVA Cluster Extension resource configuration file for
RHCS or SLE HA integration in the correct directory location.
• An error occurs after initialization.
Failover error handling
EVA Cluster Extension automatically fails over services (RHCS), applications (MSCS), or resource
groups (SLE HA) if the system the service, application, or resource group is running on becomes
unavailable. This is done as part of the cluster functionality. This also means that if a problem occurs
with the EVA DR group state or the HP SMI-S EVA server, any service, application, or resource group
online process is stopped.
EVA Cluster Extension is highly configurable. Depending on the customer setting, EVA Cluster Extension
is used to prevent services, applications, or resource groups from going online automatically under
the wrong conditions.
Therefore, EVA Cluster Extension returns local, data-center-wide, or even cluster-wide errors to prevent
accidental access to the vdisk(s).
EVA Cluster Extension services (RHCS), resources (MSCS), or resource groups (SLE HA) return a data
center error and fail the resource if the DR group status indicates that the problem experienced locally
would not be solved on another system connected to the same EVA storage system. This means that
all systems specified in the DC_A_Hosts resource property or the DC_B_Hosts resource property would
fail to bring the service, application, or resource group online.
Depending on the service, application, or resource group and the resource property values, the
resource tries to start on different nodes several times. If the remote data center is down, this looks
like the service, application, resource group alternates (bounces) between the surviving systems. This
happens until the service, application, or resource group property values are reached or until the user
disables the restart of the resource.
This could be also the case if the ApplicationStartup resource property has been set to FASTFAILBACK.
If a DR group state is discovered that does not allow bringing the service or application/package on
any system in the cluster, a cluster error is reported and the resource fails on all systems. This could
lead to the same behavior as described for an EVA Cluster Extension data center error.
In any case, HP does not recommend restarting a failed service or application/package without
investigating the problem. A failed EVA Cluster Extension resource indicates the need to check the
status of the DR group and its member vdisks and decide whether it is safe to continue or not.
EVA Cluster Extension Software Administrator Guide 103