Managing HP Serviceguard for Linux Ninth Edition, April 2009

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 232)
• Adding Previously Configured Nodes to a Running Cluster (page 232)
• Removing Nodes from Participation in a Running Cluster (page 233)
• Halting the Entire Cluster (page 234)
• Automatically Restarting the Cluster (page 234)
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 176) 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 start the cluster depending on whether all nodes are currently down
(that is, no cluster daemons are running), or whether you are starting the cluster daemon
on an individual node.
Note the distinction that is made in this chapter between adding an already configured
node to the cluster and adding a new node to the cluster configuration. An already
configured node is one that is already entered in the cluster configuration file; a new
node is added to the cluster by modifying the cluster configuration file.
Managing the Cluster and Nodes 231