How can I propagate changes I've made to /etc/cluster/cluster.conf to all the nodes in my cluster?

Solution Verified - Updated -

Environment

Issue

  • How can I activate a changed Red Hat Enterprise Linux cluster configuration file manually?
  • Does the cluster.conf change need to be done on both cluster nodes?
  • How can I copy my cluster.conf to my other nodes?
  • Can "ccs -h host name --sync --activate" command be used instead of "cman_tool version -r" for propagating cluster changes?

Resolution

The procedure for manually modifying the /etc/cluster/cluster.conf is different for each version of Red Hat Enterprise Linux (RHEL). Below is the the procedure for each version of RHEL.

Red Hat Enterprise Linux 4:

The config_version option in the file /etc/cluster/cluster.conf needs to be incremented up after changes are made. Then ccsd needs to be informed of the new changes to the configuration file /etc/cluster/cluster.conf. Then the new configuration file needs to be propagated to all the nodes in the cluster. This requires two commands to inform ccs of the changes and propagate the /etc/cluster/cluster.conf file:

# ccs_tool update <path to modified cluster.conf>
# cman_tool version -r <new_config_version_number>
Red Hat Enterprise Linux 5:

The config_version option in the file /etc/cluster/cluster.conf needs to be incremented after changes are made. Then ccsd needs to be informed of the new changes to the configuration file /etc/cluster/cluster.conf. Then the new configuration file needs to be propagated to all the nodes in the cluster. Only one command is needed to inform ccsd of the changes and propagate the /etc/cluster/cluster.conf file:

# ccs_tool update <path to modified cluster.conf>
Red Hat Enterprise Linux Server 6:

The config_version option in the file /etc/cluster/cluster.conf needs to be incremented after changes are made. The service ricci must be started on all nodes because this service is what propagates the /etc/cluster/cluster.conf to all nodes in the cluster. Only one command is needed to inform corosync of the changes and propagate the /etc/cluster/cluster.conf file:

# cman_tool version -r

or

Without incrementing the config_version option in the file /etc/cluster/cluster.conf the following command can be run on any one node after making changes to the cluster configuration file for propagating the changes across the cluster nodes.

# ccs -h <hostname from which this command is run> --sync --activate

All releases
To verify that /etc/cluster/cluster.conf file was properly propagated run the following command before and after editing and propagating the file to all nodes in the cluster:

# cman_tool status | grep "Config Version:"

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments