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

Table 26 Error Messages and their Resolution (continued)
ResolutionCauseLog Messages
• Password less SSH is not
configured from the node to the
storage system.
• The Remote Copy volume group
for DC1 or DC2 may not exist.
Create a FORCEFLAG file under the
package directory using touch
The error was caused by one of the
following reasons:
Not able to determine the status of the
local storage system. This might be
because either the storage system is
<package directory>/FORCEFLAG
• The storage system is down.
down or because there are SSH
and restart the package after you
• The TCP/IP connectivity from the
node to the storage system is
down.
connectivity issues. The package is not
allowed to start up.
Fix the problem to allow package
startup. To start the package forcefully,
use FORCEFLAG file.
ensure that the local storage system has
the latest data and the local Remote
Copy volumes are in read/write.
• Password less SSH is not
configured from the node to the
storage system.
• The Remote Copy volume group
for DC1 or DC2 may not exist.
• The maximum number of SSH
connections (16) to the array are
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).
To start the package irrespective of data
currency, create a FORCEFLAG file
The error was caused by one of the
following reasons:
Not able to determine the status of the
remote storage system. This might be
because of SSH connectivity issues or
under the package directory using
• The storage system is down.
because the remote storage system is
touch <package
• The TCP/IP connectivity from the
node to the storage system is
down.
down. The role of local Remote Copy
volume group's is “Primary”. This
means that the role of remote Remote
directory>/FORCEFLAG, and then
restart the package.
NOTE: This can be done only when
the local storage system is up.
Copy volume group's can be either
“Secondary” or “Primary-Rev”, or the
• Password less SSH is not
configured from the node to the
storage system.
remote 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 package startup
on this node, either fix the connectivity
issue or use FORCEFLAG file.
• The maximum number of SSH
connections (16) to the array are
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).
Fix the issue based on the cause
identified. If required, reverse the
The error was caused by one of the
following reasons:
Not able to determine the status of the
local storage system. This might be
because of SSH connectivity issues. replication role, and then restart the
package.
• The TCP/IP connectivity form the
node to the storage system is
down.
The role of remote Remote Copy
volume group role is Primary and the
status is started. This implies that the
• Passwordless SSH is not configured
from the node to the storage
system.
role of local Remote Copy volume
group is Secondary. The package is
not allowed to start up on this node.
To allow package startup on this
• The Remote Copy volume group
for DC1 or DC2 may not exist.
node, either fix the connectivity issues
or reverse the replication using 3PAR
Management Console.
• The maximum number of SSH
connections (16) to the array are
Troubleshooting 333