Home ›

Corosync

Configuring Corosync

Submitted by florian on Tue, 2012-12-04 11:57

You now need configure Corosync. The following example configuration file assumes that your cluster nodes have two network interfaces, using the 192.168.122.0/24 and 192.168.133.0/24 networks. You will need to adjust this to your own network configuration.

Set the contents of /etc/corosync/corosync.conf as follows:

What's a Totem "Retransmit List" all about in Corosync?

Occasionally, you may see errors similar to this in your system logs:

corosync [TOTEM ] Retransmit List: e4 e5 e7 e8 ea eb ed ee

Here's what causes them, and what you can do to fix the issue.

Checking Corosync cluster membership

It's simple and easy to get Pacemaker's view of the status of members in a cluster – just invoke crm_mon. But what if you want to check on the cluster membership when Pacemaker is not running, or you want to make sure whether Corosync's view of the cluster is identical to Pacemaker's? Here's how.

hastexo High Availability Expert Training

You know how to install DRBD, Corosync and Pacemaker and how to get them set up for everyday's business? That's great, because then you're ready take your Linux and High Availability knowledge to the next level.

Corosync

Corosync is a framework for reliable cluster communications, the "lower" half of the high availability software stack. (The "upper" half is cluster resource management, such as Pacemaker).

We have collected multiple years of experience with setting up and maintaining Corosync-based clusters. We're actively involved in its development by sending bug reports and patches. We're frequently in touch with the Corosync core developers.

Syndicate content