Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

NODE_NAME SJC_2
SITE san_jose
........
Use the cmviewcl command to view the list of sites that are configured in the cluster and their
associated nodes. Following is a sample of the command, and the output:
cmviewcl -l node
SITE_NAME san_francisco
NODE STATUS STATE
SFO_1 up running
SFO_2 up running
.........
SITE_NAME san_jose
NODE STATUS STATE
SJC_1 up running
SJC_2 up running
You can configure either of these failover policies for both, the regular Metrocluster failover packages
and Site Controller Packages. To use these policies, you must specify site_preferred or
site_preferred_manual for the failover_policy attribute in the Metrocluster package
configuration file.
NOTE: For a Metrocluster package, it is recommended that the failover_policy parameter
is set to site_preferred.
Volume Monitor Configuration
Starting from HP Serviceguard A.11.20
2
, Volume Monitor is introduced to provide a means for
effective and persistent monitoring of VxVM or LVM storage volumes. A separate service must be
configured within a package that requires access to a VxVM or LVM storage volume. The package
can be a failover package or multi-node package.
The Volume Monitor must be configured as a service within a Metrocluster package. For Site
Controller package, the volume monitor must be configured as part of workload packages that
requires access to VxVM or LVM storage volumes.
Example 1 how 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.
Example 1 Configuring Service for Volume Monitor
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
When a monitored volume fails or becomes inaccessible, the monitor service will exit, causing the
package to fail on the current node. The failover of package depends on its configured settings
and on the application behavior.
For more information, see “About the Volume Monitor” in chapter 4 of Managing Serviceguard,
Nineteenth Edition available at www.hp.com/go/hpux-serviceguard-docs -> HP Serviceguard.
2. HP Serviceguard A.11.20 requires additional patch to enable volume monitor feature.
28 Designing a Metrocluster