<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'><font size="3">I set up the 3rd node ("quorum") yesterday by only installing heartbeat, not pacemaker. Is pacemaker necessary as well? I commented out the following lines in its ha.cf since it is always going to be running in standby:</font><div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">autojoin none</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">mcast eth0 239.0.0.43 694 1 0</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">bcast eth0</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">warntime 5</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">deadtime 15</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">initdead 60</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">keepalive 2</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">node node1</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">node node2</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">node quorum</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">#crm respawn</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">#respawn hacluster /usr/lib/heartbeat/dopd</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">#apiauth dopd gid=haclient uid=hacluster</font></div><div style="color: rgb(0, 0, 0); font-size: 12pt; font-family: 'Times New Roman'; "><br></div><div style="color: rgb(0, 0, 0); font-size: 12pt; font-family: 'Times New Roman'; ">Since this quorum node only has a single ethernet interface, can it be used for both the mcast and bcast parameters? How are both the multicast and broadcast pathways used for node communication? After saving these parameters and reloading heartbeat on all nodes, the "quorum" node is listed as offline in the cluster. Is there something missing in my configuration that is preventing it from communicating with the rest of the cluster?<br></div><div style="color: rgb(0, 0, 0); font-size: 12pt; font-family: 'Times New Roman'; "><br></div><div style="color: rgb(0, 0, 0); font-size: 12pt; font-family: 'Times New Roman'; ">Also, another more general question about the failover - node1 and node2 are each connected to the shared network over br0 and connected directly to each other with a crossover cable over br1:</div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2"> -------------------- ----------</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2"> | Shared Network |------| quorum |</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2"> -------------------- ----------</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2"> |</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2"> br0 / \ br0</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2"> / \</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2"> --------- ---------</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2"> | node1 | --------- | node2 | </font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2"> --------- br1 ---------</font></div><div style="color: rgb(0, 0, 0); font-size: 12pt; font-family: 'Times New Roman'; "><br></div><div style="color: rgb(0, 0, 0); font-size: 12pt; font-family: 'Times New Roman'; ">The corresponding configuration in ha.cf is</div><div><div><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">autojoin none</font></div><div><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">mcast br0 239.0.0.43 694 1 0</font></div><div><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">bcast br1</font></div><div><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">warntime 5</font></div><div style="color: rgb(0, 0, 0); "><font face="'courier new', courier, monaco, monospace, sans-serif" size="2">....</font></div></div><div style="color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-size: 12pt; "><br></div><div style="color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-size: 12pt; ">If br0 to one of the nodes were to be cut when the "quorum" node was down, would they still be able to communicate over br1 (e.g. to maintain quorum between themselves and fail over to the other node that still has an active br0)? </div><div style="color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-size: 12pt; "><br></div><div style="color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-size: 12pt; ">Thanks,</div><div style="color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-size: 12pt; "><br></div><div style="color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-size: 12pt; ">Andrew</div><br><hr id="zwchr" style="color: rgb(0, 0, 0); font-size: 12pt; font-family: 'Times New Roman'; "><div style="color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica, Arial, sans-serif; font-size: 12pt; "><b>From: </b>"Andreas Kurz" <andreas@hastexo.com><br><b>To: </b>pacemaker@oss.clusterlabs.org<br><b>Sent: </b>Monday, January 23, 2012 1:53:27 PM<br><b>Subject: </b>Re: [Pacemaker] Configuring 3rd Node as Quorum Node in 2 Node Cluster<br><br>On 01/23/2012 03:36 PM, Andrew Martin wrote:<br>> I think I will configure the 3rd (quorum) node in standby mode. In the<br>> near future I am looking into setting up 2 additional clusters (each of<br>> these are also 2-node clusters) and would like to use this same server<br>> as the quorum node for those clusters as well. Is this possible? If so,<br>> how do I have to configure heartbeat (or multiple instances of<br>> heartbeat) to join multiple clusters at once and act as the quorum node<br>> in each?<br><br>No, multiple heartbeat instances per node are not supported ... but why<br>not creating minimal VM instances ... though not to minimal, as you have<br>a good chance that theses standby instances become DC role.<br><br>Regards,<br>Andreas<br><br>-- <br>Need help with Pacemaker?<br>http://www.hastexo.com/now<br><br>> <br>> Thanks,<br>> <br>> Andrew<br>> <br>> ------------------------------------------------------------------------<br>> *From: *"Andreas Kurz" <andreas@hastexo.com><br>> *To: *pacemaker@oss.clusterlabs.org<br>> *Sent: *Friday, January 13, 2012 6:35:48 AM<br>> *Subject: *Re: [Pacemaker] Configuring 3rd Node as Quorum Node in 2<br>> Node Cluster<br>> <br>> On 01/13/2012 12:32 PM, Ivan Savčić | Epix wrote:<br>>> On 1/11/2012 8:28 AM, Florian Haas wrote:<br>>>> Another option would be to permanently run the 3rd node in standby mode.<br>>><br>>> Just wondering, wouldn't the standby mode prevent that node from<br>>> performing the fencing actions? Also, can it act as DC then?<br>> <br>> It would run no resources (including stonith resources) but can be the DC.<br>> <br>> Another option for running a "pure" quorum node would be to only start<br>> CCM but not pacemaker ... though that setup looks quite strange e.g. in<br>> crm_mon output ....<br>> <br>> Regards,<br>> Andreas<br>> <br>> -- <br>> Need help with Pacemaker?<br>> http://www.hastexo.com/now<br>> <br>>><br>>> Thanks,<br>>> Ivan<br>>><br>>> _______________________________________________<br>>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker<br>>><br>>> Project Home: http://www.clusterlabs.org<br>>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf<br>>> Bugs: http://bugs.clusterlabs.org<br>> <br>> <br>> <br>> <br>> _______________________________________________<br>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker<br>> <br>> Project Home: http://www.clusterlabs.org<br>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf<br>> Bugs: http://bugs.clusterlabs.org<br>> <br>> <br>> <br>> _______________________________________________<br>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker<br>> <br>> Project Home: http://www.clusterlabs.org<br>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf<br>> Bugs: http://bugs.clusterlabs.org<br><br><br><br>_______________________________________________<br>Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>http://oss.clusterlabs.org/mailman/listinfo/pacemaker<br><br>Project Home: http://www.clusterlabs.org<br>Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf<br>Bugs: http://bugs.clusterlabs.org<br></div><br></div></div></body></html>