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

alert up 1 min --
PACKAGE RECOVERY GROUP hpgroup10
PACKAGE ROLE STATUS
PTST_sanfran/PACKAGE1 primary down
TST_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
cmviewclcommand on both clusters. On each cluster, make note of which nodes the primary
packages are running on, as well as data sender and data receiver packages, if they are being
used for logical data replication. 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
NODE STATUS STATE
nynode1 up running
Network Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 12.1 lan0
PRIMARY up 56.1 lan2
NODE STATUS STATE:
nynode2 up running
Network Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 4.1 lan0
PRIMARY up 56.1 lan1
PACKAGE STATUS STATE PKG_SWITCH NODE
ccmonpkg up running enabled nynode2
Script_Parameters:
ITEM NAME STATUS MAX_RESTARTS RESTARTS
Service ccmonpkg.srv up 20 0
Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled nynode2 (current)
Alternate up enabled nynode1
UNOWNED Packages:
PACKAGE STATUS STATE PKG_SWITCH NODE
salespkg_bak down unowned
Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover unknown
Failback unknown
Script_Parameters:
110 Designing Continentalclusters