Using Serviceguard Extension for RAC, 9th Edition, September 2010

CLUSTER STATUS
example up
NODE STATUS STATE
ftsys9 up running
PACKAGE STATUS STATE AUTO_RUN NODE
pkg1 up running enabled ftsys9
pkg2 up running enabled ftsys9
NODE STATUS STATE
ftsys10 up running
Both packages are now running on ftsys9 and pkg2 is enabled for switching. Ftsys10 is
running the daemon and no packages are running on ftsys10.
Status After Halting a Node
After halting ftsys10, with the following command:
# cmhaltnode ftsys10
the output of cmviewcl is as follows on ftsys9:
CLUSTER STATUS
example up
NODE STATUS STATE
ftsys9 up running
PACKAGE STATUS STATE AUTO_RUN NODE
pkg1 up running enabled ftsys9
pkg2 up running enabled ftsys9
NODE STATUS STATE
ftsys10 down halted
This output is seen on both ftsys9 and ftsys10.
Viewing Data on Unowned Packages
The following example shows packages that are currently unowned—not running on any
configured node. Information on monitored resources is provided for each node. This information
allows you to identify the cause of a failure and decide where to start the package up again.
UNOWNED_PACKAGES
PACKAGE STATUS STATE AUTO_RUN NODE
PKG3 down halted enabled unowned
Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover min_package_node
Failback automatic
Script_Parameters:
ITEM STATUS NODE_NAME NAME
Resource up manx /resource/random
Subnet up manx 192.8.15.0
Resource up burmese /resource/random
Subnet up burmese 192.8.15.0
Resource up tabby /resource/random
Subnet up tabby 192.8.15.0
Resource up persian /resource/random
Subnet up persian 192.8.15.0
Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Reviewing Cluster and Package States with the cmviewcl Command 117