Managing Serviceguard 12th Edition, March 2006

Cluster and Package Maintenance
Reviewing Cluster and Package Status
Chapter 7 315
• Uninitialized. The service is included in the cluster configuration,
but it was not started with a run command in the control script.
• Unknown.
Network Status The network interfaces have only status, as follows:
• Up.
• Down.
• Unknown. Serviceguard cannot determine whether the interface is up
or down. This can happen when the cluster is down. A standby
interface has this status.
Serial Line Status The serial line has only status, as follows:
• Up. Heartbeats are received over the serial line.
• Down. Heartbeat has not been received over the serial line within 2
times the NODE_TIMEOUT value.
• Recovering. A corrupt message was received on the serial line, and
the line is in the process of resynchronizing.
• Unknown. We cannot determine whether the serial line is up or down.
This can happen when the remote node is down.
Failover and Failback Policies Failover packages can be configured
with one of two values for the FAILOVER_POLICY parameter:
• CONFIGURED_NODE. The package fails over to the next node in the
node list in the package configuration file.
• 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:
• AUTOMATIC. With this setting, a package, following a failover, returns
to its primary node when the primary node becomes available again.
• MANUAL. With this setting, a package, following a failover, must be
moved back to its original node by a system administrator.
Failover and failback policies are displayed in the output of the
cmviewcl -v command.