Installation guide

--setrm
--setcman
--setmul ti cast
--setal tmul ti cast
--setfenced aemon
--setl o g g i ng
--setq uo rumd
For example, to reset all of the fence deamon properties, you can run the following command.
# ccs -h ho stname --setfencedaemo n
Note, however, that if you use one of these commands to reset a property, then the other properties of
the command will be reset to their default values. For example, you can use the following command to
set the po st_fai l _d el ay property to 5:
# ccs -h ho stname --setfencedaemo n po st_fai l _d el ay= 5
If, after running that command, you run the following command to reset the po st_jo i n_d el ay
property to 10, the po st_fail _d el ay property will be restored to its default value:
# ccs -h ho stname --setfencedaemo n po st_jo i n_d el ay= 10
To reset both the po st_fai l _d el ay and the po st_jo i n_d el ay properties, you indicate them
both on the same command, as in the following example:
# ccs -h ho stname --setfencedaemo n po st_fai l _d el ay= 5
po st_joi n_d el ay= 10
For more information on configuring fence devices, refer to Section 5.5, “ Configuring Fence
Devices” .
5.1.6. Configurat ion Validat ion
When you use the ccs command to create and edit the cluster configuration file, the configuration is
automatically validated according to the cluster schema. As of the Red Hat Enterprise Linux 6.3
release, the ccs command validates the configuration according to the cluster schema at
/usr/share/cluster/cl uster.rng on the node that you specify with the -h option. Previously
the ccs command always used the cluster schema that was packaged with the ccs command itself,
/usr/share/ccs/cl uster. rng on the local system. When you use the -f option to specify the
local system, the ccs command still uses the cluster schema /usr/share/ccs/cluster. rng that
was packaged with the ccs command itself on that system.
5.2. Configurat ion T asks
Configuring Red Hat High Availability Add-On software with the ccs consists of the following steps:
1. Ensuring that ricci is running on all nodes in the cluster. Refer to Section 5.3, “ Starting
ricci” .
Red Hat Ent erprise Linux 6 Clust er Administ rat ion
70