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

Table 3 Additional validation of Site Controller packages (continued)
Checks whether the managed or critical
package type is either multi node or
failover.
cmapplyconf
# cmapplyconf -P
<Metrocluster_pkg.conf>
Check the managed and critical
package types
cmcheckconf [-P/-p]
# cmcheckconf -P
<Metrocluster_pkg.conf>
# cmcheckconf -p
<Metrocluster_pkg.conf>
Checks whether the site values in this
package are the sites that are
configured in the cluster configuration.
cmapplyconf
# cmapplyconf -P
<Metrocluster_pkg.conf>
Check if the Site values are valid
cmcheckconf [-P/-p]
# cmcheckconf -P
<Metrocluster_pkg.conf>
# cmcheckconf -p
<Metrocluster_pkg.conf>
Checks whether the Site Controller EMS
resource dependency is configured on
cmapplyconf
# cmapplyconf -P
<Metrocluster_pkg.conf>
Verify whether the Site Safety Latch
dependencies are configured properly
for a complex workload all the packages that are the foremost
predecessors in the dependency order
cmcheckconf [-P/-p]
among the packages that are
configured to be managed by the Site
Controller Package on both sites.
# cmcheckconf -P
<Metrocluster_pkg.conf>
# cmcheckconf -p
<Metrocluster_pkg.conf>
NOTE: The checks and validations mentioned in “Validating Metrocluster package” (page 39)
is not applicable for legacy packages. HP recommends that you add the location of the package
environment file available in the Metrocluster package or the Site Controller package directory to
the list of files in /etc/cmcluster/cmfiles2check.
42 Metrocluster Features