From: rama nichanamatlu <rama.nichanamatlu@oracle.com>
To: Veaceslav Falico <vfalico@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] bonding: If IP route look-up to send an ARP fails, mark in bonding structure as no ARP sent.
Date: Thu, 21 Nov 2013 12:34:08 -0800 [thread overview]
Message-ID: <528E6E40.6020201@oracle.com> (raw)
In-Reply-To: <20131121111022.GA30998@redhat.com>
On 11/21/2013 3:10 AM, Veaceslav Falico wrote:
> On Wed, Nov 20, 2013 at 04:53:20PM -0800, rama nichanamatlu wrote:
>> During the creation of VLAN's atop bonding the underlying interfaces
>> are made part of VLAN's, and at the same bonding driver gets aware
>> that VLAN's exists above it and hence would consult IP routing for
>> every ARP to be sent to determine the route which tells bonding
>> driver the correct VLAN tag to attach to the outgoing ARP packet. But,
>> during the VLAN creation when vlan driver puts the underlying
>> interface into default vlan and then actual vlan, in-between this if
>> bonding driver consults the IP for a route, IP fails to provide a
>> correct route and upon which bonding driver drops the ARP packet. ARP
>> monitor when it
>> comes around next time, sees no ARP response and fails-over to the
>> next available slave. Consulting for a IP route,
>> ip_route_output(),happens in bond_arp_send_all().
>
> bonding works as expected - nothing to fix here. And even as a
> workaround/hack - I'm not sure we need that to suppress one failover *only*
> when vlan is added on top.
>
>>
Thank U.
With *out* this change our systems failed system testing, to
consistently be on designated primary interface on *every* single
reboot. With this change the behavior was as expected even after a few
thousand reboots & System testing could move to next level catching an
another bug in sr-iov :). And Without, the outcome was less predictable
after a reboot and bonding was on a different slave each time.
-Rama
>> To prevent this false fail-over, when bonding driver fails to send an
>> ARP out it marks in its private structure, bonding{}, not to expect
>> an ARP response, when ARP monitor comes around next time ARP sending
>> will be tried again.
>>
>> Extensively tested in a VM environment; sr-iov intf->bonding
>> intf->vlan intf. All virtual interfaces created at boot time.
>>
next prev parent reply other threads:[~2013-11-21 20:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 0:53 [PATCH] bonding: If IP route look-up to send an ARP fails, mark in bonding structure as no ARP sent rama nichanamatlu
2013-11-21 1:10 ` Ding Tianhong
2013-11-21 1:18 ` Jay Vosburgh
2013-11-21 2:23 ` rama nichanamatlu
2013-11-21 6:01 ` rama nichanamatlu
2013-11-21 11:10 ` Veaceslav Falico
2013-11-21 20:34 ` rama nichanamatlu [this message]
2013-11-21 21:12 ` Jay Vosburgh
2013-11-22 0:34 ` rama nichanamatlu
2013-11-22 2:43 ` Jay Vosburgh
2013-11-22 8:28 ` rama nichanamatlu
-- strict thread matches above, loose matches on Subject: below --
2013-11-21 1:36 rama nichanamatlu
[not found] <528D5DF7.6060103@oracle.com>
2013-11-21 1:40 ` rama nichanamatlu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=528E6E40.6020201@oracle.com \
--to=rama.nichanamatlu@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=vfalico@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).