Managing Serviceguard A.11.20, March 2013

Status After Halting a Node
After we halt ftsys10 with the following command
cmhaltnode ftsys10
we’ll see the following output from cmviewcl:
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 can be seen on both ftsys9 and ftsys10.
Viewing Information about Unowned Packages
The following example shows packages that are currently unowned, that is, not running on any
configured node. cmviewcl provides information on monitored resources for each node on which
the package can run; this 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 disabled 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
Generic Resource unknown manx sfm_disk
Resource up burmese /resource/random
Subnet up burmese 192.8.15.0
Generic Resource unknown burmese sfm_disk
Resource up tabby /resource/random
Subnet up tabby 192.8.15.0
Generic Resource unknown tabby sfm_disk
Resource up persian /resource/random
Subnet up persian 192.8.15.0
Generic Resource unknown persian sfm_disk
Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled manx
Alternate up enabled burmese
Alternate up enabled tabby
Alternate up enabled persian
Viewing Information about System Multi-Node Packages
The following example shows a cluster that includes system multi-node packages as well as failover
packages. The system multi-node packages are running on all nodes in the cluster, whereas the
standard packages run on only one node at a time.
274 Cluster and Package Maintenance