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
NOTE: The password file name must
have the following format:
<3parArrayUserName>_<3parArrayName>.pwf
Managing CLI connections to 3PAR array
The maximum number of CLI connections to a 3PAR storage array is 64. Metrocluster configuration
or package startup operations uses CLI to connect and to get information about the remote copy
groups from the storage array. Therefore, more than 64 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 CLI connections consumed by other Metrocluster configured to failover
applications from the storage array.
• Any external SSH and CLI connections made by storage administrators.
If the Metrocluster packages fail to start because CLI connections are exhausted, to restart the
package do the following:
• Verify the number of users connected to the array by using the showuserconn command.
Notify the administrators to close the idle sessions. After the number of available connections
is increased, restart the packages.
Troubleshooting connectivity issues 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.
# ping <storage system network name or IP address>
If you are using the network name of the storage system, verify it is resolving to proper IP address
using nslookup command from the cluster nodes.
# nslookup <storage system network name>
If the local replication role is secondary, the remote replication role is primary, and the remote
copy link is up, Metrocluster executes stop, reverse, and start operations for the Remote Copy
volume group on the local site. If the stop and reverse operation succeed, the secondary volumes
become read/write and the Metrocluster package comes up even if the start operation fails with
the error "Promote operation is going on". If the start operation fails, replication I/O does not start
from the new primary volumes to the new secondary volumes. In this case, manual intervention is
required to restart the replication using the startcopygroup command.
30 Troubleshooting