Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF

Table 7 Error messages and their resolution (continued)
ResolutionCauseLog Messages
dependency configured
for the packages that
Check for any error messages in the package
log file on all the nodes in the site siteA for the
packages managed by Site Controller.
4. Clean the site using the cmresetsc
tool.
failed is not met on this
site.
5. Restart the Site Controller package.
Fix any issue reported in the package log files
and enable node switching for the packages
on nodes they have failed.
Reset the site siteA using cmresetsc command
and start the Site Controller package again.
Site Controller startup failed.
This message is logged
because the previous
Starting Site Controller package on site siteA.
Previous startup of Site Controller package on
the site siteA has failed
1. Check the log files of all the packages
managed by Site Controller package
on the site.startup of the Site
Controller package failed
on the local site, siteA.
2. Identify the issues and fix them.
Clean up the site siteA and start the Site
Controller package again
3. Enable node switching for the package
managed by the Site Controller package
on the site.
Check for any error messages in the package
log file on all the nodes in the site siteA for the
4. Clean the site using the cmresetsc
tool.
packages managed by Site Controller
package.
5. Restart the Site Controller package.
Fix any issue reported in the package log files
and enable node switching for the packages
on nodes they have failed.
Reset the site siteA using cmresetsc command
and start the Site Controller package again.
Site Controller startup failed.
This message is logged
because the previous
Starting Site Controller package on site siteB.
Site Controller start up on the site siteA has
failed.
1. Check the log files of all the packages
managed by Site Controller package
on the remote site.start-up of the Site
Controller package failed
2. Identify the issues and fix them.
Clean up the site siteA and start the Site
Controller package.
on the remote site. In this
case, the remote site is
siteB.
3. Enable node switching for the package
managed by Site Controller Package on
the other site.
Fix any issue reported in the package log files
and enable node switching for the packages
on nodes they have failed.
4. Clean the remote site using the
cmresetsc tool on a node in the other
site.
Reset the site siteA using cmresetsc command
and start the Site Controller package again.
5. Restart the Site Controller package.
Site Controller startup failed.
This message is logged
because one of the
Executing: cmrunpkg <List of packages
managed by Site Controller package>.
1. Check the log file of the package on the
nodes where node switching is not
enabled.packages managed by
the Site Controller
siteA_mg3.
Unable to run package <Package managed
by Site Controller>on node <node name>, the
node switching is disabled.
2. Clean any stray resources owned by the
package that are still online on the
node.
package has failed to
start at this site.
3. Enable node switching for the package
on the nodes.
cmrunpkg: Unable to start some package or
package instances.
4. Clean the site using the cmresetsc
tool.
Check the log files of the packages managed
by Site Controller for more details.
5. Start the Site Controller package.
Check for any error messages in the package
log file on all the nodes in the site siteA for the
packages managed by Site Controller
package.
Fix any issue reported in the package log files
and enable node switching for the packages
on nodes they have failed.
76 Troubleshooting