Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access XP P9000 for Linux B.12.00.00

7 Troubleshooting
Troubleshooting Metrocluster
Analyse Metrocluster and Raid Manager log files to understand the problem in the respective
environment and follow a recommended action based on the error or warning messages.
Metrocluster log file
Regularly review the following files for messages, warnings, and recommended actions. It is good
to review these files after every system, data center, and/or application failures:
• View the system log at /var/log/messages.
• The package log file specified in the script_log_file parameter.
Raid Manager log
If there are problems with Raid Manager, verify the horcmX.conf file first and see if there are any
mistakes in the information. Analyse the Raid Manager logs
/HORCM/log<HORCM instance #>/HORCC_<node name>.log to understand the problem
better.
Understanding Metrocluster Package Log
This section describes the various messages that are logged in the Metrocluster package log file
and the methods to resolve those error messages.
Table 7 (page 48) describes the error messages that are displayed and the recommended resolution.
Table 7 Metrocluster Log Messages and their resolution
ResolutionCauseLog Messages
Get the correct fence level using the
pairdisplay command. Specify the
The fence level specified for the
FENCE parameter in the package
configuration is not same as the one
The configured fencelevel:
<configured_fence_level>does not
match the actual fence level:
correct fence level in the package
configured for the device group during
the pair creation.
<actual_fence_level>.The actual fence
level and the configured fence level
configuration and reapply the package
configuration using the cmapplyconf
command.
for this package must be the same.
Please fix this before continuing.
Exiting.
If some of the volumes are in SMPL
state, reissue the paircreate
The fence level for all the volumes in
the device group is not same. The
reason could be that new volumes are
The fence level for all devices in the
device group must be the same. Please
fix this before continuing. Exiting.
command. Otherwise delete the pair
and recreate it.
added to the RAID Manager
configuration file but the paircreate
command is not re-run on new
volumes.
If application availability is more
important than data currency on the
Device group is configured with fence
level “data” and the replication link is
Executing: /usr/bin/horcmstart.sh 0
2>&1 Failed to start RAID Manager.
other site, create a FORCEFLAG filefailed. Package fails to start on theExiting. The below is the associated
error message — under the package directory usingPVOL side as AUTO_FENCE_LEVEL
parameter is set to “0”.
The CA link has failed with
FENCE=data. The package is
touch <package
directory>/FORCEFLAG and then
restart the package. Once the link is
configured to halt under these
restored, issue pairresync
command to restore the replication
circumstances. Create the file
<FORCEFLAG_FILE> if you really want
to startup the package on this host.
Exiting.
48 Troubleshooting