Corosync is started as a regular system service. Depending on your distribution, it may ship with a LSB (System V style) init script, an upstart job, or a systemd unit file. Either way, the service is usually named corosync: /etc/init.d/corosync start (LSB) service corosync start (LSB, alternate) start corosync (upstart) systemctl start corosync (systemd) You can now check the Corosync connectivity with two tools. The corosync-cfgtool utility, when invoked with the -s option, gives a summary of the health of the communication rings: # corosync-cfgtool -s Printing ring status. Local node ID 435324542 RING ID 0 id = 192.168.42.82 status = ring 0 active with no faults RING ID 1 id = 10.0.42.100 status = ring 1 active with no faults The corosync-objctl utility can be used to dump the Corosync cluster member list: # corosync-objctl runtime.totem.pg.mrp.srp.members runtime.totem.pg.mrp.srp.435324542.ip=r(0) ip(192.168.42.82) r(1) ip(10.0.42.100) runtime.totem.pg.mrp.srp.435324542.join_count=1 runtime.totem.pg.mrp.srp.435324542.status=joined runtime.totem.pg.mrp.srp.983895584.ip=r(0) ip(192.168.42.87) r(1) ip(10.0.42.254) runtime.totem.pg.mrp.srp.983895584.join_count=1 runtime.totem.pg.mrp.srp.983895584.status=joined You should see a status=joined entry for each of your constituent cluster nodes.