On 2011/05/19, at 15:59, Duvvuru, Venkata Kumar wrote:

> To keep my question simple, Does corosync work on a cluster spanning across 
> different subnets. If yes, what is the bind network address on the nodes?
>  
> /Venkat 

Hi Venkat,
In a word, no. One bind address maps to a single interface, and the underlying 
protocol uses link-local multicast on that subnet to communicate. As Steve 
alluded to, you can specify multiple redundant bind addresses (RRP mode), but 
that doesn't sound like exactly what you want either.

Two possible things to try:
1) Configure the transport to udpu (UDP Unicast). You then need to specify the 
IP addresses of all members of the cluster explicitly. The bind network address 
in this case would be the one with the IP address that you have specified as a 
member on the other nodes. A quick look at the code didn't reveal any checks to 
ensure that all members are in the same subnet as the bind address, but I have 
no idea if this is actually supported. It should be quick to try out though.

2) Failing that, you could add tagged VLANs to each ethernet interface and try 
creating a bridge between the VLANs. Be prepared to spend a lot of time 
debugging STP issues ;)

The best (and highest-performance) solution is to have an L2 switch in 
hardware, but obviously that is not always possible.

regards,
Zane.

> From: Duvvuru, Venkata Kumar 
> Sent: Thursday, May 19, 2011 7:01 PM
> To: '[email protected]'
> Subject: Bind Network Address
>  
> Hi,
> I am running corosync on 4 linux nodes (actually these nodes are configured 
> as routers using Quagga) and each node has 3 network interfaces (eth0, eth1, 
> eth2). Each of the interfaces are in a different subnet.
> These nodes are connected in a torus network.
> What would be the bind net address in case of such a scenario?
>  
> I had put 135.24.0.0 as the bindnetaddr but that is not working.
>  
> Let’s assume for reference purpose 135.24.220.xxx to 135.24.225.xxx are the 
> networks and netmask is 255.255.255.0
>  
> /Venkat
> _______________________________________________
> Openais mailing list
> [email protected]
> https://lists.linux-foundation.org/mailman/listinfo/openais

_______________________________________________
Openais mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/openais

Reply via email to