Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA A.05.01

7 Troubleshooting
Troubleshooting Metrocluster
Analyse Metrocluster and SMI-S/Command View log files to understand the problem in the respective
environment and follow a recommended action based on the error or warning messages.
Metrocluster log
Make sure you periodically review the following files for messages, warnings, and recommended
actions. HP recommends 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.
HP P6000/EVA storage system log
Analyse the CIMOM or Provider logs to understand the problem with the SMI-S layer. For more
information on SMI-S logs see the SMI-S EVA Provider user guide and for Command View logs
see the HP P6000 Command View user guide.
Troubleshooting Metrocluster SADTA
Logs and files
This section describes the guidelines to be considered before working with files that need to be
configured for SADTA.
Consider the following guidelines:
• The Site Controller package control log file can be specified using the following 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.
• HP recommends that you 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 must 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
does not clean any of the managed packages 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 fails, the following message appears in the Site Controller
package log file on the node where it was last running or was last started:
Troubleshooting Metrocluster 69