Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy
The following information is displayed by this tool:
• Number of critical and managed packages at each site.
• Status of the Site Controller managed packages (halted or started).
• Site Controller managed packages halted cleanly or not.
• Site is active or passive.
• Site Safety Latch value on each node. The value can be Close, Open, or Intermediate.
For more information on using cmviewsc, see cmviewsc(1m).
Identifying and cleaning MNP stack packages that are halted
The Site Controller package does not start if the MNP stack packages are not halted clean. An
MNP package is halted unclean when the halt script does not run successfully on all the configured
nodes of the package. This implies that there might be some stray resources configured with the
package, that are online in the cluster. The Site Controller package logs the following message in
its log file on the node where it failed to start:
Package <package name> has not halted cleanly on node <node name>
The following command shows whether an MNP package halt was clean or unclean:
# cmviewcl –v –f line <MNP Package name>
Check for the field last_halt_failed under each instance of the MNP package. When set to
Yes, that instance of the MNP package did not successfully execute the halt script when it was
halted. Check for all instances.
The unclean nodes might have stray resources. See the MNP package log file on the corresponding
node to identify the reason for the halt script run failure. Clean any stray resources that are still
online in the node and enable node switching on the node for the package. This clears the flag
and allows the Site Controller Package to start. Complete this procedure for all nodes where the
MNP package instance has halted unclean.
# cmmodpkg –e -n <node name> <MNP Package name>
Understanding Site Controller package logs
This section describes the various messages that are logged in the log files and the methods to
resolve those error messages.
Table 6 describes the displayed error messages and their recommended resolution.
Table 6 Error Messages and their Resolution
ResolutionCauseLog Messages
The critical package at
siteA is still running.
Starting Site Controller (hrdb_sc) on site siteB.
Site safety latch at site siteA is open.
1. Clean the nodes on siteA and
enable node switching for the Site
Controller package.
Checking if site failover conditions are met.
2. Restart the Site Controller package
on siteA.
Critical package hrdb at site siteA is up.
Error: Site failover conditions are not met.
Unexpected Site Controller startup.
Unable to initiate site failover at site SiteB.
Site Controller startup failed.
An MNP package
managed by the Site
Starting Site Controller (hrdb_sc) on siteB.
Site safety latch at site siteA is open.
1. Check the MNP package log on all
the nodes on which it failed to run the
halt script successfully.Controller package at
siteA has not halted
Checking if site failover conditions are met.
2. Clean any stray resources that are
still online on the node.
clean on at least one of its
nodes.
Package hrdb has not halted cleanly on node
<node name>.
62 Troubleshooting