HP 3PAR Cluster Extension Software Administrator Guide for Windows (5697-1821, April 2012)

A data center is down (SLE HA and RHCS)
RHCS and SLE HA expect an acknowledgement from the fencing device before services are failed
over to another node. In the event of complete site failure, including fencing devices, clusters do
not automatically fail over services to surviving cluster nodes at the remote site. Manual intervention
is required in this situation. For instructions on bringing a service online, see the cluster software
documentation.
HP 3PAR Target arrays not configured with Remote Copy Links
Sometimes CLX Configuration Tool is not able to add an array even through the password file
exists and PATH variable is set properly for the HP 3PAR Inform CLI and you can execute HP 3PAR
Inform CLI command locally. The root cause for this problem is that the HP 3PAR Inform CLI command
showrcopy for this array does not show any target information (in case if target array is not
configured). So configure the 3PAR remote copy for the array first, then add the array to CLX
configuration through CLX configuration tool.
Secondary-Secondary Issue
If the local replication role is secondary, the remote replication role is primary, and the remote
copy link is up, Cluster Extension (CLX) executes stop, reverse (setrcopygroup reverse), and
start operations (startrcopygroup) for the Remote Copy volume group during the online
operation. At this time, if the HP 3PAR CLI command setrcopygroup reverse executed by
CLX fails (which may occur very rarely), the replication roles of the volume group may go to the
secondary roles on both the datacenters. At this time, CLX resource cannot be brought online on
any datacenter servers since the replication roles are secondary on both the datacenters and
manual intervention is required.
In order to recover from this situation, user has to identify the correct primary side and execute the
below command manually using the HP 3PAR Inform CLI in order to bring the replication role from
secondary to primary.
setrcopygroup reverse -local <group_name>
HP 3PAR CLI Command Timeout Issue
CLX uses HP 3PAR CLI for communicating with the HP 3PAR arrays. CLX has a default timeout
value of 60 seconds for each CLI command it executes. If the CLI command does not return a value
in the default time out value, the operation fails. If any of the CLX operations (configuration or
functionality) fails, one of the reasons could be that the corresponding operation is not completed
in the default time of 60 seconds. In this scenario, you should increase the CLI command time out
value in the ucf.cfg file located at <CLX Install directory>/conf directory.
The parameter to configure the timeout value is "HP3PARCLICommandTimeout". Set a value more
than the default value and see if the desired operations succeed or not.
A data center is down (SLE HA and RHCS) 87