Managing HP Serviceguard for Linux, Tenth Edition, September 2012

NODE STATUS STATE
ftsys10 down halted
This output can be seen on both ftsys9 and ftsys10.
Viewing Information about Unowned Packages
The following example shows packages that are currently unowned, that is, not running
on any configured node.
UNOWNED_PACKAGES
PACKAGE STATUS STATE AUTO_RUN NODE
PKG3 down halted enabled unowned
Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover min_package_node
Failback automatic
Script_Parameters:
ITEM STATUS NODE_NAME NAME
Subnet up manx 192.8.15.0
Subnet up burmese 192.8.15.0
Subnet up tabby 192.8.15.0
Subnet up persian 192.8.15.0
Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled manx
Alternate up enabled burmese
Alternate up enabled tabby
Alternate up enabled persian
Managing the Cluster and Nodes
This section describes the following tasks:
• Starting the Cluster When all Nodes are Down (page 244)
• Adding Previously Configured Nodes to a Running Cluster (page 244)
• Removing Nodes from Participation in a Running Cluster (page 245)
• Halting the Entire Cluster (page 246)
• Automatically Restarting the Cluster (page 246)
In Serviceguard A.11.16 and later, these tasks can be performed by non-root users with
the appropriate privileges. See Controlling Access to the Cluster (page 186) for more
information about configuring access.
You can use Serviceguard Manager or the Serviceguard command line to start or stop
the cluster, or to add or halt nodes. Starting the cluster means running the cluster daemon
on one or more of the nodes in a cluster. You use different Serviceguard commands to
Managing the Cluster and Nodes 243