8. At any node, using the cl ustat utility, verify that the HA services are running as expected. In
addition, cl ustat displays status of the cluster nodes. For example:
[root@ example-01 ~]#clustat
Cluster Status for mycluster @ Wed Nov 17 05:40:00 2010
Member Status: Quorate
Member Name ID Status
------ ---- ---- ------
node-03.example.com 3 Online, rgmanager
node-02.example.com 2 Online, rgmanager
node-01.example.com 1 Online, Local,
rgmanager
Service Name Owner (Last)
State
------- ---- ----- ------ ---
--
service:example_apache node-01.example.com
started
service:example_apache2 (none)
disabled
9. If the cluster is running as expected, you are done updating the configuration.
8.4 .2. Updat ing a Configurat ion Using scp
To update the configuration using the scp 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. Validate the updated file against the cluster schema (cluster. rng ) by running the
ccs_co nfi g _val i d ate command. For example:
[root@ example-01 ~]# ccs_co nfi g _val i d ate
Configuration validates
5. If the updated file is valid, use the scp command to propagate it to /etc/cl uster/ in each
cluster node.
6. Verify that the updated configuration file has been propagated.
7. To reload the new configuration, execute the following command on one of the cluster nodes:
cman_tool version -r
If you do not have ri cci installed, you can use the following command:
cman_tool version -s
Comentarios a estos manuales