Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF

7 Troubleshooting
Troubleshooting Metrocluster
Analyse Metrocluster and symapi log files to understand the problem in the respective environment
and follow a recommended action based on the error or warning messages.
Metrocluster log
Regularly review the following files for messages, warnings, and recommended actions. It is good
to review these files after each system, data center, and/or application failures:
• View the system log at /var/adm/syslog/syslog.log.
• The package log file specified in the script_log_file parameter.
SYMAPI log
Analyse the logs in /var/symapi/log directory to debug failures with resepect to EMC SRDF.
Troubleshooting Metrocluster SADTA
Logs and files
This section describes the guidelines you must consider before working with files that must be
configured for SADTA.
Following are some of the guidelines:
• The Site Controller package control log file can be specified using the attribute
script_log_file in the Site Controller package configuration file.
Serviceguard defaults the Site Controller package logs to the default log destination. The
default log destination for a given Site Controller Package is /var/adm/cmcluster/log
<Site_controller_package_name>.log.
• Specify the Site Controller Package log file under the directory specified for the
dts/dts/dts_pkg_dir attribute in the Site Controller Package configuration file.
• The Metrocluster storage preparation modules will also log to the Site Controller package log
file.
• The Site Safety Latch mechanism logs are saved in the/etc/opt/resmon/log/api.log
file.
Cleaning the site to restart the Site Controller package
The Site Controller package startup on a site can fail for various reasons. The Site Safety Latch will
be in a special state: INTERMEDIATE. In this state, the Site Controller package cannot be started
from either of the sites. A special tool called cmresetsc is provided to cleanup a site under this
condition. This tool cleans the Metrocluster environment in site for the Site Controller package. But,
it does not clean any of the packages managed by for the Site Controller Package. Any issues in
the packages managed by Site Controller package must be fixed by the operator and the package’s
node switching must be enabled before restarting the Site Controller package.
When the Site Controller package has failed, the following message appears in the Site Controller
package log file on the node where it was last running or was last started:
Check the package log files on all the nodes of all other packages
managed by the Site Controller package to identify issues in those
packages.
To clean a site for a SADTA application :
Troubleshooting Metrocluster 71