HP Serviceguard Continentalcluster manual 335

Table 26 Error Messages and their Resolution (continued)

Log Messages	Cause	Resolution
Resyncwait timeout has occurred. The	The data is being synchronized from	Wait till the Remote Copy volume group
package is not allowed to start up on	the remote storage system to the local	is fully synchronized and is in “Synced”
this node. Either data copy is still in	storage system and the Remote Copy	state. Restart the package.
progress between the virtual volumes	volume group volumes are in
of the primary and secondary Remote	“Syncing” state. Metrocluster package
Copy volume groups	startup failed because the
(<remote_copy_volume_group_name>)	synchronization of the volumes did not
or the status of the volume	complete within the time interval
group/virtual volume is not “Started	specified in the parameter
or Synced”.	RESYNC_WAIT_TIMEOUT.
Metrocluster failed to discover the	The error was caused by one of the	Fix the issue based on the cause
properties of both the remote and local	following reasons:	identified.
Remote Copy volume groups. The	• The storage system is down.
package is not allowed to start up.
	• 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