Installation guide

8.4 .1. Updat ing a Configurat ion Using cman_to o l versi o n -r
To update the configuration using the cman_to o l versio n -r command, perform the following
steps:
1. At any node in the cluster, edit the /etc/cl uster/cl uster. co nf file.
2. Update the co nfi g _versi o n attribute by incrementing its value (for example, changing
from co nfi g _versi o n= "2" to co nfi g _versio n= "3").
3. Save /etc/cl uster/cl uster.co nf.
4. Run the cman_too l versi o n -r command to propagate the configuration to the rest of the
cluster nodes. It is necessary that ri cci be running in each cluster node to be able to
propagate updated cluster configuration information.
5. Verify that the updated cl uster. co nf configuration file has been propagated. If not, use the
scp command to propagate it to /etc/cluster/ in each cluster node.
6. You may skip this step (restarting cluster software) if you have made only the following
configuration changes:
Deleting a node from the cluster configuration—except where the node count changes
from greater than two nodes to two nodes. For information about deleting a node from a
cluster and transitioning from greater than two nodes to two nodes, refer to Section 8.2,
“ Deleting or Adding a Node” .
Adding a node to the cluster configuration—except where the node count changes from
two nodes to greater than two nodes. For information about adding a node to a cluster
and transitioning from two nodes to greater than two nodes, refer to Section 8.2.2,
“ Adding a Node to a Cluster”.
Changes to how daemons log information.
HA service/VM maintenance (adding, editing, or deleting).
Resource maintenance (adding, editing, or deleting).
Failover domain maintenance (adding, editing, or deleting).
Otherwise, you must restart the cluster software as follows:
a. At each node, stop the cluster software according to Section 8.1.2, “Stopping Cluster
Software” .
b. At each node, start the cluster software according to Section 8.1.1, “ Starting Cluster
Software” .
Stopping and starting the cluster software ensures that any configuration changes that are
checked only at startup time are included in the running configuration.
7. At any cluster node, run cman_too l no d es to verify that the nodes are functioning as
members in the cluster (signified as "M" in the status column, " Sts"). For example:
[root@ example-01 ~]# cman_to o l no d es
Node Sts Inc Joined Name
1 M 548 2010-09-28 10:52:21 node-01.example.com
2 M 548 2010-09-28 10:52:21 node-02.example.com
3 M 544 2010-09-28 10:52:21 node-03.example.com
Red Hat Ent erprise Linux 6 Clust er Administ rat ion
14 6