HP 3PAR Cluster Extension Software Administrator Guide (5697-1429, March 2012)

NOTE: When configuring the HP 3PAR storage system password file for Cluster Extension usage,
user in the password file should have access to all the domains of Remote Copy virtual volumes
managed by Cluster Extension.
Promote issue
When the data copy is going on between the primary and the secondary Remote Copy volume
groups, if the Remote Copy link is broken for some reason, the Remote Copy volume groups go
to the stopped state and the snapshots of the secondary volumes start getting promoted to the
base volumes. This is the design of 3PAR Remote Copy. This activity may take some time to complete.
At this time, if the start or restore operation is attempted on the Remote Copy volume groups,
then this operation may fail with the error Promote operation is going on. At this time, if
the local replication role is secondary, the remote replication role is primary, and the remote copy
link is up, Cluster Extension executes stop, reverse, and start operations for the Remote Copy
volume group. If the stop and reverse operation succeed, then the secondary volumes become
read-write and Cluster Extension resource comes online even though the start operation may
fail. If the start operation fails, replication I/O does not start from the new primary volumes to
the new secondary volumes. In case of Windows OS, Cluster Extension will continuously attempt
to start the group during the monitoring interval of the Cluster Extension resource. In case of RHEL
and SUSE, manual start of the group is necessary in order to resume the replication IO between
the primary and secondary RC volume groups. At this time, if the local replication role is
secondary-rev, the remote replication role is primary-rev, and the remote copy link is up,
the restore operation fails due to promoting of the snapshot, and the Cluster Extension resource
does not come online.
Cluster Extension Autopass troubleshooting
Cluster Extension uses Autopass as a framework for licensing checks. Autopass provides Graphical
User Interface and a Command Line Interface to perform licensing specific operations, and they
are well integrated in to Cluster Extension. For the GUI, Autopass needs a compatible JRE version
installed on the system. For the supported JRE version refer to Cluster Extension SPOCK. In case
the GUI is not working due to environmental issues related to JRE, CLI can be used to perform the
licensing specific operations like install and uninstall.
The FC link is down (RHCS)
In RHCS, the detection of a storage outage due to failure of all paths to the storage depends on
the monitoring capability of resources configured in the RHCS service. For example, the LVM and
filesystem resource agents distributed with RHCS can detect the loss of storage and take appropriate
actions. The stop operation on a service might fail due to the inability to stop individual resources
cleanly. This may be caused by the loss of paths to the storage. When the stop operation on a
service fails, RHCS marks the service as failed and the service does not automatically fail over to
another node.
To recover from this situation, use the following procedure:
1. Remove the node that lost access to the storage by shutting down the node.
2. Follow the steps required to bring up a service in a failed state, as documented in the RHCS
administration guide. This process involves disabling the service, and then enabling it on the
node where the service is allowed to come online.
82 Troubleshooting