Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

Table 26 Error Messages and their Resolution (continued)
ResolutionCauseLog Messages
in use and the failure was caused
because another was not available
to control the array. For more
information, see “Managing SSH
connections to 3PAR array”
(page 335).
Start the replication group using either
the startrcopygroup command or
The error was caused by one of the
following reasons:
Not able to determine the status of the
local storage system. This may be
because of SSH connectivity issues or
the 3PAR Management Console. Restart
the package.
The storage system is down.
because the local storage system is
down. The role of remote Remote
The TCP/IP connectivity form the
node to the storage system is
down.
Copy volume group is “Primary”. This
means that the role of local Remote
Copy volume group can be either
Passwordless SSH is not configured
from the node to the storage
system.
“Secondary” or “Primary-Rev, or the
local storage system is down. The
package is not allowed to start up on
The Remote Copy volume group
for DC1 or DC2 may not exist.
this node. To allow the package
startup on this node, either fix the
The maximum number of SSH
connections (16) to the array are
connectivity issue or use FORCEFLAG
file.
in use and the failure was caused
because another was not available
to control the array. For more
information, see “Managing SSH
connections to 3PAR array”
(page 335).
Start the replication group using either
the startrcopygroup command or
The startrcopygroup command
failed.
Starting of the Remote Copy volume
group
[<remote_copy_volume_group_name>]
has failed to complete. This means that
the 3PAR Management Console. Restart
the package.
Remote Copy is not functioning
between the primary and secondary
volume groups. Manually start Remote
Copy volume group using the
startrcopygroup command.
Fix the issue based on the identified
cause. Restore the replication link, and
start the package.
Either the link is down or the remote
storage system is not up. The local
Remote Copy volume group is
The role of local Remote Copy volume
group is "Secondary-Rev" and the link
is down. The package is not allowed
“Secondary-Rev”. The replicationto startup. Restore the links and ensure
cannot be restored because the link isthe storage systems are up before
restarting this package. down, and there is no way to make
the “Secondary-Rev” volume
read/write.
334 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy