Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy for Linux B.01.00.00, July 2013

Table 3 Error Messages and their Resolution (continued)
ResolutionCauseLog Messages
storage system for the
corresponding user.
• The CLI connections are exhausted.
For more information see
“Managing CLI connections to
3PAR array” (page 30).
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 CLI 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 files are not configured
to connect from the nodes to the
remote storage system is down. The
storage system for the
corresponding user.
package is not allowed to start up on
this node. To allow package startup
• The Remote Copy volume group
for DC1 or DC2 may not exist.
on this node, either fix the connectivity
issue or use FORCEFLAG file.
• The CLI connections are exhausted.
For more information see
“Managing CLI connections to
3PAR array” (page 30).
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 CLI connectivity issues. The replication role, and then restart the
package.
• The TCP/IP connectivity from the
node to the storage system is
down.
role of remote Remote Copy volume
group role is Primary and the status is
started. This implies that the role of
• Password files are not configured
to connect from nodes to the
local Remote Copy volume group is
Secondary. The package is not
storage system for the
corresponding user.
allowed to start up on this node. To
allow package startup on this node,
either fix the connectivity issues or
• The Remote Copy volume group
for DC1 or DC2 may not exist.
reverse the replication using 3PAR
Management Console.
• The CLI connections are exhausted.
For more information see
“Managing CLI connections to
3PAR array” (page 30).
Start the replication group using either
the startrcopygroup command or
The error was caused due to one of
the following reasons:
Not able to determine the status of the
local storage system. This may be
because of CLI 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 from 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
• Password files are not configured
to connect from nodes to the
“Secondary” or “Primary-Rev”, or the
local storage system is down. The
storage system for the
corresponding user.
package is not allowed to start up on
this node. To allow the package
• The Remote Copy volume group
for DC1 or DC2 may not exist.
startup on this node, either fix the
connectivity issue or use FORCEFLAG
file.
• The CLI connections are exhausted.
For more information see
“Managing CLI connections to
3PAR array” (page 30).
28 Troubleshooting