Hi,

 

Please find attached the code changes done on openais-0.70 release to
fix the below mentioned bond interface issue. If you find the changes
appropriate then could you please incorporate them in the openais source
tree?

 

As mentioned in my previous update the issue is because the multicast
address is attached to the slave interface rather than the master bond
interface. Also 'noarp' entry added to the system refers to the wrong
device. 

 

This was happening because the kernel picks up wrong interface matching
against the 'openais' specified address in
IP_MULTICAST_IF/IP_ADD_MEMBERSHIP socket options since in case of bond
interface configuration the system has multiple network interfaces with
the same IP.

 

Changes are being made to 'openais' so as to pass the right interface
index i.e. Master interface index to kernel rather than passing the
address.

 

With regards,

Vivek Gupta

 

________________________________

From: Vivek Gupta 
Sent: Tuesday, April 29, 2008 7:41 PM
To: '[EMAIL PROTECTED]'
Subject: Failed to run openais on bond0 interface

 

Hi,

 

One of my (HA) high availability application is trying to run 'openais'
on top of Linux bond0 (eth1 and eth2 are the slave interfaces) interface
but somehow fails to learn about the peer node. As such the two nodes
are able to communicate with each other. What I have observed that
'openais' attaches multicast address to the 'eth1' interface which is
actually the slave interface rather attaching it to the bond0 interface.
Following is the output of 'ipmaddr show ipv4' command:

 

1:      lo

        inet  224.0.0.1

3:      eth0

        inet  224.0.0.1

4:      eth1

        inet  226.94.1.1

        inet  224.0.0.1

5:      eth2

        inet  224.0.0.1

6:      eth3

        inet  224.0.0.1

7:      eth4

        inet  224.0.0.1

8:      eth5

        inet  224.0.0.1

10:     bond0

        inet  224.0.0.1

 

Here, 226.94.1.1 is the 'openais' multicast address.

 

Following is the link which talks about multicast communication issue
with bond interface incase the multicast address is attached to the one
of the slave interfaces:

http://www.usenet-forums.com/linux-networking/65445-mcast-troubles-bond-
interface.html

 

Have any one noticed this issue before? Any clues??

 

With regards,

Vivek Gupta

 

 

Attachment: totemnet.openais-0.70.diff
Description: totemnet.openais-0.70.diff

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

Reply via email to