<br><br><div class="gmail_quote">On 29 September 2010 21:01, Andreas Hofmeister <span dir="ltr"><<a href="mailto:andi@collax.com">andi@collax.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff"><div class="im">
On 29.09.2010 19:59, Mike A Meyer wrote:
<blockquote type="cite">
We have two nodes that we have the IP address
assigned to a bond0 network interface instead of the usual eth0 network
interface. We are wondering if there are issues with trying to
configure
corosync/pacemaker with an IP assigned to a bond0 network interface.
We
are seeing that corosync/pacemaker will start on both nodes, but it
doesn't
detect other nodes in the cluster. We do have SELinux and the firewall
shut off on both nodes. Any information would be helpful. <br>
</blockquote>
<br></div>
We run the cluster stuff on bonding devices (actually on a VLan on top
of a bond) and it works well. We use it in a two-node setup in
round-robin mode, the nodes are connected back-to-back (i.e. no Switch
in between).<br>
<br>
If you use bonding over a Switch, check your bonding mode - round-robin
just won't work. Try LACP if you have connected each node to a single
switch or if your Switches support link aggregation over multiple
Devices (the cheaper ones won't). Try "active-backup" with multiple
switches.<br>
<br>
To check your configuration, use "ping" and check the "icmp_seq" in the
replies. If some sequence number is missing, your setup is probably
broken.<br>
<br></div></blockquote><div><br>It is quite common to connect both interfaces of a bond on the same switch and then face issues.<br>Mike you need to tell us a bit more on the layer 2 connectivity and how it does look like.<br>
<br>We also use active-backup mode on our bond interfaces, but we use 2 switches and it works without any problem<br><br>Cheers,<br>Pavlos<br><br></div></div><br>