sleha-join to a cluster using udpu will not join cluster until after restart of corosync on current nodes
This document (7021065) is provided subject to the disclaimer at the end of this document.
SUSE Linux Enterprise High Availability Extension 12
1. Manually add the new nodes' IP Address to the /etc/corosync/corosync.conf configuration.on one of the existing nodes in the cluster. This will be a new "memberaddr:"
2. The new configuration should be distributed to all nodes in the cluster. csync2 -xv | scp | rsync
At this point, the new corosync configuration needs to be reloaded which means "openais" service will need to be stopped / started again.
You can do this like a rolling update, bouncing one node in the cluster at a time allowing resources to migrate to other nodes in the cluster.
3. With the new corosync.conf configuration in the cluster, you can now use the "sleha-join" script on the new node.
The only method is to 'stop' and 'start' the openais service with updated corosync.conf configuration which will update it's member / node list in memory.
This has been fixed in SLES12sp2. The command: "corosync-cfgtool -R" reloads the corosync configuration. The sleha-join scripts will do this automatically for you starting with SLES12sp2.
Corosync.conf related parameters.
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7021065
- Creation Date:06-JUL-17
- Modified Date:06-JUL-17
- SUSESUSE Linux Enterprise High Availability Extension