Table 26 Error Messages and their Resolution (continued)

Log Messages

Cause

Resolution

 

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

Start the replication group using either

local storage system. This may be

following reasons:

the startrcopygroup command or

because of SSH connectivity issues or

• The storage system is down.

the 3PAR Management Console. Restart

because the local storage system is

• The TCP/IP connectivity form the

the package.

down. The role of remote Remote

 

Copy volume group is “Primary”. This

node to the storage system is

 

means that the role of local Remote

down.

 

Copy volume group can be either

• Passwordless SSH is not configured

 

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

from the node to the storage

 

local storage system is down. The

system.

 

package is not allowed to start up on

• The Remote Copy volume group

 

this node. To allow the package

for DC1 or DC2 may not exist.

 

startup on this node, either fix the

 

 

 

connectivity issue or use FORCEFLAG

• The maximum number of SSH

 

file.

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

 

 

 

 

Starting of the Remote Copy volume

The startrcopygroup command

Start the replication group using either

group

failed.

the startrcopygroup command or

[<remote_copy_volume_group_name>]

 

the 3PAR Management Console. Restart

 

the package.

has failed to complete. This means that

 

 

 

Remote Copy is not functioning

 

 

between the primary and secondary

 

 

volume groups. Manually start Remote

 

 

Copy volume group using the

 

 

startrcopygroup command.

 

 

 

 

 

The role of local Remote Copy volume

Either the link is down or the remote

Fix the issue based on the identified

group is "Secondary-Rev" and the link

storage system is not up. The local

cause. Restore the replication link, and

is down. The package is not allowed

Remote Copy volume group is

start the package.

to startup. Restore the links and ensure

“Secondary-Rev”. The replication

 

the storage systems are up before

cannot be restored because the link is

 

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