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

Table 26 Error Messages and their Resolution (continued)
ResolutionCauseLog Messages
Wait till the Remote Copy volume group
is fully synchronized and is in “Synced”
state. Restart the package.
The data is being synchronized from
the remote storage system to the local
storage system and the Remote Copy
Resyncwait timeout has occurred. The
package is not allowed to start up on
this node. Either data copy is still in
volume group volumes are inprogress between the virtual volumes
“Syncing” state. Metrocluster packageof the primary and secondary Remote
startup failed because theCopy volume groups
synchronization of the volumes did not(<remote_copy_volume_group_name>)
complete within the time intervalor the status of the volume
specified in the parameter
RESYNC_WAIT_TIMEOUT.
group/virtual volume is not “Started
or Synced”.
Fix the issue based on the cause
identified.
The error was caused by one of the
following reasons:
Metrocluster failed to discover the
properties of both the remote and local
Remote Copy volume groups. The
package is not allowed to start up.
• The storage system is down.
• The TCP/IP connectivity form the
node to the storage system is
down.
• Passwordless SSH is not configured
from the node to the storage
system.
• The Remote Copy volume group
for DC1 or DC2 may not exist.
Managing SSH connections to 3PAR array
The maximum number of SSH connections to a 3PAR storage array is16. Metrocluster configuration
or package startup operations use SSH connections to get information about the remote copy
groups from the storage array. Therefore, more than 16 Metrocluster packages cannot be configured
in a cluster.
To decide the actual number of Metrocluster packages that can be configured, consider the
following:
• The number of SSH connections consumed by other Metrocluster configurations to failover
applications from the storage array.
• Any external SSH connections made by connecting to the array via a SSH client or by using
3PAR Inform Management Console (IMC). IMC internally may use SSH connection for
connecting to the array.
If the Metrocluster packages fail to start because 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 then to restart the package do the following:
• For example, if a Serviceguard node fails to start 5 out of 16 Metrocluster packages, wait
until the remaining 11 package startups are complete. After the startups are complete, the 11
connections are released. Restart the failed packages.
• Verify the number of users connected to the array via SSH client, by using the showuserconn
command. Notify the administrators to close the idle sessions. After the number of available
connections is increased, restart the packages. This can also be done if Metrocluster packages
could not be configured.
Connecting Problem to HP 3PAR storage system
During Metrocluster configuration, if you are unable to connect to the HP 3PAR storage system,
ensure that the storage system is up and running, and the network ports are functioning properly.
To check for response from the storage system over the network, use the ping command from
cluster nodes to the storage system's network name or IP address.
Troubleshooting 335