I can confirm that this issue exists beyond Redhat 4, I'm using Ubuntu 8.10 (2.6.27).<br><br>I'm using ib-bond and I've also tried adding he bonds directly with <br><br>echo +bond0 > /sys/class/net/bonding_masters<br>
echo 1 > /sys/class/net/bond0/bonding/mode<br>echo 100 > /sys/class/net/bond0/bonding/miimon<br>echo +ib0 > /sys/class/net/bond0/bonding/slaves<br>echo +ib1 > /sys/class/net/bond0/bonding/slaves<br>ifconfig bond0 <a href="http://192.168.47.102/24">192.168.47.102/24</a><br>
route add -net <a href="http://224.0.0.0/3">224.0.0.0/3</a> gw 192.168.47.100<br><br>I will be happy to open a ticket on this issue.<br><br>Thank you,<br>Dennis P.<br><br><br><div class="gmail_quote">On Mon, Apr 20, 2009 at 8:05 AM, Moni Shoua <span dir="ltr"><<a href="mailto:monis@voltaire.com">monis@voltaire.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">Dennis Portello wrote:<br>
> Hello,<br>
><br>
> I seem to be experiencing the exact issue discussed below (back in<br>
> December). I'm using the 2.6.27 kernel and the bonding drivers available<br>
> in that kernel. Was there ever a solution or patch to solve this? I have<br>
</div>Not really, a patch was sent a long time ago but it wasn't accepted. The claim was that it takes<br>
care of a phenomena that exists only with Redhat 4 (I tend to agree).<br>
You can read the discussion here <a href="http://kerneltrap.org/mailarchive/linux-netdev/2008/4/10/1391984" target="_blank">http://kerneltrap.org/mailarchive/linux-netdev/2008/4/10/1391984</a><br>
<div class="im"><br>
> been using the ib-bond scripts as well, but using other approaches like<br>
> standard OS tools or adding the bond through sysfs all seem to have the<br>
> same results.<br>
><br>
</div>As I recall, this shouldn't happen when working with ib-bond. However, ib-bond is a deprecated tool<br>
so I wouldn't tell you to use it as a solution but I do wonder why do you still see the -22 status in d,esg<br>
<div class="im">> Regular TCP/IP unicast works, though dmesg is full of warning about<br>
> multicast failing. Multicast does not work at all.<br>
</div>Multicast that is not working is not related to the issue you describe. I suggest that<br>
you open a bug here <a href="https://bugs.openfabrics.org/" target="_blank">https://bugs.openfabrics.org/</a> and describe what you do and what you get<br>
in details.<br>
<br>
thanks<br>
MoniS<br>
<br>
</blockquote></div><br>