Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Cluster and Package Maintenance
Reviewing Cluster and Package Status
Chapter 7 247
Failover and Failback Policies
Failover packages can be configured with one of two values for the
failover_policy parameter (see page 214), 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 210).
• min_package_node. The package fails over to the node in the cluster
with the fewest running packages on it.
Failover packages can also be configured with one of two values for the
failback_policy parameter (see page 214), 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 NAME
PRIMARY up eth0
PRIMARY up eth1
PACKAGE STATUS STATE AUTO_RUN NODE
pkg1 up running enabled ftsys9
Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual