Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy

Table 5 Error Messages and their Resolution (continued)
ResolutionCauseLog Messages
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.
• If you are using CLI client, then
password files are not configured
to connect from nodes to the
storage system for the
corresponding user. Otherwise,
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 connections to 3PAR array are
exhausted. For more information
see “Managing connections to
3PAR array” (page 60).
To start the package irrespective of data
currency, create a FORCEFLAG file
The error was caused due to 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
• If you are using CLI client, then
password files are not configured
remote storage system is down. The
to connect from nodes to the
package is not allowed to start up on
storage system for the
this node. To allow package startup
corresponding user. Otherwise,
on this node, either fix the connectivity
issue or use FORCEFLAG file.
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 connections to 3PAR array are
exhausted. For more information
see “Managing connections to
3PAR array” (page 60).
Fix the issue based on the cause
identified. If required, reverse the
The error was caused due to 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 from 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
• If you are using CLI client, then
password files are not configured
role of local Remote Copy volume
group is Secondary. The package is
to connect from nodes to the
not allowed to start up on this node.
storage system for the
To allow package startup on this
corresponding user. Otherwise,
node, either fix the connectivity issues
Password less SSH is not
or reverse the replication using 3PAR
Management Console.
configured from the node to the
storage system.
• The Remote Copy volume group
for DC1 or DC2 may not exist.
• The connections to 3PAR array are
exhausted. For more information
see “Managing connections to
3PAR array” (page 60).
58 Troubleshooting