Am Montag, 25. März 2013, 14:43:00 schrieb Florian Crouzat: > Le 24/03/2013 16:59, deep saran a écrit : > > Hi all, > > > > I am trying to setup a two node cluster where both nodes are in different > > subnet. I am using corosync/pacemaker for this. I am newbie in this field > > and have no idea how to configure corosync/pacemaker to work in different > > subnet. My initial investigation suggest that it is possible using VIPArip > > along with ripd/quagga but i dont understand how to configure them to work > > in my networking environment. Can anyone suggest any document or > > demostrate > > using an example, i will be really grateful. > > > > Please help me if you have any prior experience in this field. > > > > Thanks in advance!!! > > > > Regards, > > Deep > > Wow, you just dropped some heavy words in there: quagga & such.. > What you want to configure is corosync, the messaging layer. > Pacemaker only handles clusterized resources. > What you must do is to configure and use multicast in corosync.conf, see > the man page for corosync.conf and beware that your network equipments > might drop multicast.
Hi, the first problem might be the multicast traffic between the nodes if your network equipment is not prepared for multicast routing. you can avoid this problem using the udpu transport which switches the inter- node communication to to unicast. google for "corosync udpu" for further info. The next problem is the availability of a service if the nodes are located in different subnets. Here you definitely will have to implement a dynamic routing protocol to make sure that the pakets are routed the the subnet with the active node. You can use quagga as a cluster resource. But are you sure that you need all this? Perhaps you can setup your network that you have access to the same subnet for both nodes? That would make clustering much easier. Greetings, -- Dr. Michael Schwartzkopff Guardinistr. 63 81375 München Tel: (0163) 172 50 98 _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
