Managing Serviceguard 14th Edition, June 2007

Cluster and Package Maintenance
Reviewing Cluster and Package Status
Chapter 7 323
Failover and Failback Policies Failover packages can be configured
with one of two values for the failover_policy parameter (see
page 285), as displayed in the output of cmviewcl -v:
• configured_node. The package fails over to the next node in the
node_name list in the package configuration file (see page 282).
• min_package_node. The package fails over to the node in the cluster
that has the fewest running packages.
Failover packages can also be configured with one of two values for the
failback_policy parameter (see page 286), and these are also
displayed in the output of cmviewcl -v:
• automatic: Following a failover, a package returns to its primary
node when the primary node becomes available again.
• manual: Following a failover, a package will run on the adoptive node
until moved back to its original node by a system administrator.
Examples of Cluster and Package States
The following sample output from the cmviewcl -v command shows
status for the cluster in the sample configuration.
Normal Running Status Everything is running normally; both nodes
in the cluster are running, and the packages are in their primary
locations.
CLUSTER STATUS
example up
NODE STATUS STATE
ftsys9 up running
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 56/36.1 lan0
STANDBY up 60/6 lan1
PACKAGE STATUS STATE AUTO_RUN NODE
pkg1 up running enabled ftsys9
Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual