Managing Serviceguard A.11.20, March 2013

Failover and Failback Policies
Failover packages can be configured with one of two values for the failover_policy parameter
(page 241), 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 (page 239).
• 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 (page 242), 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
Script_Parameters:
ITEM STATUS MAX_RESTARTS RESTARTS NAME
Service up 0 0 service1
Service up 0 0 sfm_disk_monitor
Subnet up 0 0 15.13.168.0
Generic Resource up sfm_disk
Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled ftsys9 (current)
Alternate up enabled ftsys10
NODE STATUS STATE
ftsys10 up running
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 28.1 lan0
STANDBY up 32.1 lan1
PACKAGE STATUS STATE AUTO_RUN NODE
pkg2 up running enabled ftsys10
Reviewing Cluster and Package Status 269