Designing Disaster Tolerant High Availability Clusters, 10th Edition, March 2003 (B7660-90013)

Building a Continental Cluster
Maintaining a Continental Cluster
Chapter 5270
alert up 1 min --
RECOVERY CLUSTER PTST_sanfran
PRIMARY CLUSTER STATUS EVENT LEVEL POLLING
INTERVAL
PTST_dts1 Unmonitored unmonitored 1 min
CONFIGURED EVENT STATUS DURATION LAST
NOTIFICATION SENT
alert unreachable 1 min --
alert unreachable 2 min --
alarm unreachable 3 min --
alert down 1 min --
alert down 2 min --
alarm down 3 min --
alert error 0 sec --
alert up 1 min --
PACKAGE RECOVERY GROUP hpgroup10
PACKAGE ROLE STATUS
PTST_sanfran/PACKAGE1 primary down
PTST_dts1/PACKAGE1 recovery down
PACKAGE RECOVERY GROUP hpgroup20
PACKAGE ROLE STATUS
PTST_dts1/PACKAGE1x_ld primary down
PTST_sanfran/PACKAGE1x_ld recovery down
For a more comprehensive status of component clusters, nodes, and
packages, use the cmviewcl command on both clusters. On each cluster,
you should make note of which nodes the primary packages are running
on, as well as data sender and data receiver packages, if you are using
them for logical data replication. You should verify that the monitor is
running on each cluster on which it is configured.
The following is an example of cmviewcl output for a cluster (nycluster)
running a monitor package. Note that the recovery package
salespkg_bak is not running, and is shown as an unowned package. This
is the expected display while the other cluster is running salespkg.
CLUSTER STATUS
nycluster up