Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy

Table 6 Error Messages and their Resolution (continued)
ResolutionCauseLog Messages
Unable to initiate site failover at siteB.
3. Enable node switching for the MNP
package on the node.
Site Controller startup failed.
4. Restart the Site Controller package.
Start the Site Controller package on the
site where it was previously halted in the
DETACH mode.
The Site Controller was
halted in the DETACH mode
at site siteA.
Starting Site Controller (hrdb_sc) on siteB.
Site safety latch at site siteA is open.
Checking if site failover conditions are met.
Error: Site failover conditions are not met.
Unexpected Site Controller startup.
Unable to initiate site failover at siteB.
Site Controller startup failed
A package dependency
condition is not met on this
site.
Unable to execute command.
Dependency on the following packages not met:
crspkg.
1. Check the log file of the failed
package.
2. Identify and fix the problem. It is
possible that the CRS MNP packages
are not running.
cmrunpkg: Unable to start some package or
package instances.
3. Enable node switching for the failed
MNP package.
Check the log files of the packages managed
by Site Controller for more details.
4. Clean the site using the cmresetsc
tool.
Refer to Metrocluster documentation for cleanup
procedures needed before restarting the Site
Controller.
5. Restart the Site Controller package.
Site Controller startup failed.
The Site Controller Package
has failed to start on the
local site, siteA.
Starting Site Controller (hrdb_sc) on site siteA.
Previous start up of Site Controller (hrdb_sc) on
the site siteA has failed.
1. Check the log files of all the packages
managed by Site Controller package
on the site.
2. Identify the issues and fix them.
Clean up the site siteA and restart hrdb_sc.
3. Enable node switching for the
package managed by Site Controller
Package on the site.
Refer to Metrocluster documentation for cleanup
procedures needed before restarting the Site
Controller.
4. Clean the site using the cmresetsc
tool.
Site Controller startup failed.
5. Restart the Site Controller package.
The Site Controller Package
has failed to start on the
remote site, siteB.
Starting Site Controller (hrdb_sc) 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 other site.
2. Identify and issues and fix them.
Clean up the site siteA and start hrdb_sc again.
3. Enable node switching for the
package managed by Site Controller
Package on the other site.
Refer to Metrocluster documentation for cleanup
procedures needed before restarting the Site
Controller.
4. Clean the other site using the
cmresetsc tool on a node in the
other site.
Site Controller startup failed.
5. Restart the Site Controller package.
The Site Controller package
shutdown detected that a
Closing site safety latch at site siteA.
Checking all packages managed by Site
Controller at siteA: hrdb hrdb_dg hrdb_mp
flash-dg flash_mp have halted.
1. Check the package log file on the
node it has failed to halt successfully.
package failed to halt
successfully.
2. Clean any stray resources owned by
the package, that are still online on
the node.
Package hrdb has not halted cleanly on node
ccia7.
3. Enable node switching for the
package on the node.
Site Controller halt failed.
Troubleshooting Metrocluster SADTA 63