Table 26 Error Messages and their Resolution (continued)

Log Messages

Cause

Resolution

 

• 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.

 

 

 

 

Not able to determine the status of the

The error was caused by one of the

Create a FORCEFLAG file under the

local storage system. This might be

following reasons:

package directory using touch

because either the storage system is

• The storage system is down.

<package directory>/FORCEFLAG

down or because there are SSH

and restart the package after you

• The TCP/IP connectivity from the

connectivity issues. The package is not

ensure that the local storage system has

allowed to start up.

node to the storage system is

the latest data and the local Remote

Fix the problem to allow package

down.

Copy volumes are in read/write.

• Password less SSH is not

 

startup. To start the package forcefully,

 

use FORCEFLAG file.

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).

 

 

 

 

Not able to determine the status of the

The error was caused by one of the

To start the package irrespective of data

remote storage system. This might be

following reasons:

currency, create a FORCEFLAG file

because of SSH connectivity issues or

• The storage system is down.

under the package directory using

because the remote storage system is

• The TCP/IP connectivity from the

touch <package

down. The role of local Remote Copy

directory>/FORCEFLAG, and then

volume group's is “Primary”. This

node to the storage system is

restart the package.

means that the role of remote Remote

down.

NOTE: This can be done only when

Copy volume group's can be either

• Password less SSH is not

the local storage system is up.

“Secondary” or “Primary-Rev”, or the

configured from the node to the

 

remote storage system is down. The

storage system.

 

package is not allowed to start up on

• The Remote Copy volume group

 

this node. To allow package startup

for DC1 or DC2 may not exist.

 

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).

 

 

 

 

Not able to determine the status of the

The error was caused by one of the

Fix the issue based on the cause

local storage system. This might be

following reasons:

identified. If required, reverse the

because of SSH connectivity issues.

• The TCP/IP connectivity form the

replication role, and then restart the

The role of remote Remote Copy

package.

node to the storage system is

volume group role is Primary and the

 

down.

 

status is started. This implies that the

 

• Passwordless SSH is not configured

 

role of local Remote Copy volume

 

group is Secondary. The package is

from the node to the storage

 

not allowed to start up on this node.

system.

 

To allow package startup on this

• The Remote Copy volume group

 

node, either fix the connectivity issues

for DC1 or DC2 may not exist.

 

or reverse the replication using 3PAR

• The maximum number of SSH

 

Management Console.

 

connections (16) to the array are

 

 

 

 

 

Troubleshooting 333