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

Table 6 Additional validation of Site Controller Packages
RemarkCommandValidations/Checks
Checks the state of the resource using
the resls command.
cmcheckconf [–v]Check whether the Site Controller EMS
resource is accessible.
Checks if the path specified by the
dts/dts/dts_pkg_dir attribute exists. This
cmapplyconf
cmcheckconf [-P/-p]
Verify that the package directory
exists.
is usually set up automatically by the
Metrocluster module.
Checks if the node_name attribute is
not set to *
cmapplyconf
cmcheckconf [-P/-p]
Check the node_name attribute of the
Site Controller package.
Checks if the managed or critical
package type is either multi node or
failover.
cmapplyconf
cmcheckconf [-P/-p]
Check the managed and critical
package types
Checks if the site values in this package
are the sites that are configured in the
cluster configuration.
cmapplyconf
cmcheckconf [-P/-p]
Check if the Site values are valid
Checks if the Site Controller EMS
resource dependency is configured on
cmapplyconf
cmcheckconf [-P/-p]
Verify if the Site Safety Latch
dependencies are configured properly
for a complex workload all the packages that are the foremost
predecessors in the dependency order
among the packages that are
configured to be managed by the Site
Controller package on both sites.
NOTE: The checks and validations mentioned in “Validating Metrocluster Package” (page 50)
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.
Volume monitor configuration
The Volume Monitor must be configured as a service within a Metrocluster package. In case of
Site Controller packages, the volume monitor must be configured as a service in the workload
packages that uses VxVM or LVM storage volumes. For Example, to configure a service for
monitoring a single VxVM volume, /dev/vx/dsk/cvm_dg0/lvol2, at log level 3, with a polling
interval of 60 seconds, and prints all log messages to /log/monlog.log.
service_name service_vol_mon
service_cmd “/usr/sbin/cmvolmond -O /log/monlog.log -D 3
/dev/vx/dsk/cvm_dg0/lvol2”
service_restart none
service_fail_fast_enabled no
service_halt_timeout 300
Rolling upgrade for Metrocluster
Use rolling Upgrade to upgrade the softwares components of the cluster with minimal downtime
to the applications managed by Metrocluster. See Rolling upgrade for the procedure.
Live Application Detach
There may be circumstances in which you want to do maintenance that involves halting a node,
or the entire cluster, without halting or failing over the affected packages. Such maintenance might
consist of anything short of rebooting the node or nodes, but a likely case is networking changes
that will disrupt the heartbeat. New command options in Serviceguard A.11.20 (collectively known
as Live Application Detach (LAD)) allows you to do this kind of maintenance while keeping the
Volume monitor configuration 51