Alex Sidorenko wrote:

On September 15, 2008 02:00:15 pm Jeff Garzik wrote:

quoted

On Mon, Sep 15, 2008 at 01:35:16PM -0400, Alex Sidorenko wrote:

quoted

Hello,

I suspect that there are some problems while switching slaves manually on
IPv6-only bonds. I have tested that this does not work on 2.6.18 kernel
(RHEL5). I looked at recent sources (2.6.26) and even though there were
multiple changes in bonding code, I still don't see how this could work.

Testing setup
-------------

Two ethernets enslaved (eth2 and eh3), active-backup bond has IPv6-only
address (no IPv4)

Everything works fine, but if we switch the slave doing

# ifenslave -c bond0 eth3

the incoming ping6 to this host stops for up to several minutes (waiting
until the switch updates its caches).

We _just_ put in an IPv6 fix, FWIW...

Hi Jeff,

do you mean the patch for ALB/TLB bonds? I looked at it but I still don't 
understand how this helps for active-backup case.

It doesn't.  What appears to happen in the active-backup case the MLD reports
are not generated on all of the slave devices, just the active one.  Thus the
switch knows only about the active device.

When you force the failover, no reports happen because the device believes that
the MLD group was already reported.  Thus there needs to be some trigger after
the failover to tell the switch that the mac address and multicast group have
moved to a different port.

-vlad