<br><font size=2><tt>Hello,<br>
</tt></font>
<br><font size=2><tt>I currently have two two-node clusters running heartbeat
and drbd(see<br>
background below). I also have a two-node test which I decided to update<br>
to the latest releases of all. In so doing I downloaded and installed<br>
drbd 8.3.0(drbd-8.3.0.tar.gz) which includes three-node setups using<br>
stacked clusters. Specifically havng a third backup/brp node<br>
geograghically removed from our production cluster is very appealing.</tt></font>
<br>
<br><font size=2><tt>I have looked at the online manual(http://www.drbd.org/users-guide/)<br>
and read the current information for three-node setups and have some<br>
observations/questions :<br>
- An illustraion/figure of a three-node setup would help.<br>
- From your "Creating a three-node setup" example on which machine
does</tt></font>
<br><font size=2><tt>the stacked-on-top-of address run(ie 192.168.42.1)
? In my case my third<br>
node is not on the same ip segment as my two other nodes.</tt></font>
<br><font size=2><tt>- After doing some searching I hit on the http://drbd-plus.linbit.com<br>
page which mentions configuraion keywords "ignore-on" and "use-csums".<br>
Neither of these exist in the drbd.conf man page. Are they needed ?</tt></font>
<br><font size=2><tt>- The manual talks about the drbdupper resource used
in R1 style<br>
clusters. What about CRM style clusters ?</tt></font>
<br><font size=2><tt>- In the R1 style configuraion you state :<br>
"The third node, which is set aside from the Heartbeat cluster, will</tt></font>
<br><font size=2><tt>have the “other half†of the stacked resource
available permanently."<br>
I presume by this you mean that if the two-node cluster disappears that<br>
the mounting/application startup on the backup node is done manually ?</tt></font>
<br><font size=2><tt>Other Questions :</tt></font>
<br><font size=2><tt>- Is the manual available for download/printing ?<br>
- Has anyone used the nx_lsa(Linx Sockets Acceration) driver to run drbd
?</tt></font>
<br>
<br><font size=2><tt>Background :<br>
1. Current two-node production clusters :</tt></font>
<br><font size=2><tt>- HW : - Proliant DL380G5<br>
- Crossover for drbd : HP NC510C(NetXen) 10GB using nx_nic</tt></font>
<br><font size=2><tt>- SW : - RHEL5 and kernel-PAE-2.6.18-92.1.10.el5<br>
- drbd : drbd-8.2.6-3, drbd-km-2.6.18_92.1.10.el5PAE-8.2.6-3,<br>
- heartbeat/pacemaker :</tt></font>
<br><font size=2><tt>heartbeat-2.99.0-3.1<br>
heartbeat-common-2.99.0-3.1<br>
heartbeat-resources-2.99.0-3.1<br>
pacemaker-heartbeat-0.6.6-17.2<br>
pacemaker-pygui-1.4-5.1</tt></font>
<br>
<br><font size=2><tt>1. Test two-node cluster :<br>
- HW : - Proliant DL380G4<br>
- SW : - Latest RHEL5 and kernel-2.6.18-128.1.1.el5</tt></font>
<br><font size=2><tt>- drbd : drbd-8.3.0-3, drbd-km-2.6.18_128.1.1.el5-8.3.0-3<br>
- heartbeat/pacemaker :</tt></font>
<br><font size=2><tt>heartbeat-2.99.2-6.1.i386.rpm<br>
heartbeat-common-2.99.2-6.1.i386.rpm<br>
heartbeat-resources-2.99.2-6.1.i386.rpm<br>
pacemaker-1.0.1-3.1.i386.rpm<br>
pacemaker-pygui-1.4-11.9.i386.rpm</tt></font>
<br>
<br>