Managing Serviceguard Eighteenth Edition, September 2010

The following states are possible only for multi-node packages:
• blocked — The package has never run on this node, either because a dependency
has not been met, or because auto_run is set to no.
• changing — The package is in a transient state, different from the status shown,
on some nodes. For example, a status of starting with a state of changing
would mean that the package was starting on at least one node, but in some other,
transitory condition (for example, failing) on at least one other node.
Package Switching Attributes
cmviewcl shows the following package switching information:
• AUTO_RUN: Can be enabled or disabled. For failover packages, enabled means
that the package starts when the cluster starts, and Serviceguard can switch the
package to another node in the event of failure.
For system multi-node packages, enabled means an instance of the package can
start on a new node joining the cluster (disabled means it will not).
• (Switching for a node.) Every failover package is marked enabled or disabled
for each node that is either a primary or adoptive node for the package.
For failover packages, enabled means that the package can switch to the specified
node. disabled means that the package cannot switch to the specified node until
the node is enabled to run the package via the cmmodpkg command.
For multi-node packages, node switching disabled means the package cannot
start on that node.
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.
Network Status
The network interfaces have only status, as follows:
• Up.
• Down.
• Unknown. Serviceguard cannot determine whether the interface is up or down. A
standby interface has this status.
Reviewing Cluster and Package Status 325