Managing HP Serviceguard for Linux Ninth Edition, April 2009

Service Status
Services have only status, as follows:
• Up. The service is being monitored.
• Down. The service is not running. It may not have started, or have halted or failed.
• Unknown. Serviceguard cannot determine the status.
Network Status
The network interfaces have only status, as follows:
• Up.
• Down.
• Unknown. Serviceguard cannot determine whether the interface is up or down.
Failover and Failback Policies
Failover packages can be configured with one of two values for the failover_policy
parameter (page 201), 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 197).
• 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 (page 201), 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
Reviewing Cluster and Package Status 225