netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Lumby <johnlumby@hotmail.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: WeipingPan <panweiping3@gmail.com>, netdev@vger.kernel.org
Subject: Re: Is 802.3ad mode in bonding useful ?
Date: Fri, 29 Apr 2011 10:04:02 -0400	[thread overview]
Message-ID: <4DBAC552.507@hotmail.com> (raw)
In-Reply-To: <20110429104342.GA22387@hmsreliant.think-freely.org>

On 04/29/11 06:43, Neil Horman wrote:
> On Fri, Apr 29, 2011 at 11:17:48AM +0800, WeipingPan wrote:
>> On 04/28/2011 08:21 PM, Neil Horman wrote:
>>> On Thu, Apr 28, 2011 at 03:33:50PM +0800, WeipingPan wrote:
>>>> Hi, all,
>>>>
>>>> 802.3ad mode in bonding implements 802.3ad standard.
>>>>
>>>> I am just wondering  802.3ad mode is useful,
>>>> since  bonding has many modes like balance-rr, active-backup, etc.
>>>>
>>> Yes, of course its usefull.  For switches which support 802.3ad, this mode
>>> allows for both peers to understand that the links in the bond are acting as an
>>> aggregate, which makes it easier to prevent things like inadvertently looped
>>> back frames, for which the other modes have to have all sorts of hacks to
>>> prevent.


I believe another use for 802.3ad is to monitor the aggregation 
"actively"  (by sending special LACP packets) and to detect any kind of 
failure of the other end of one of the slaves more rapidly (than if 
relying on something like carrier detect).     This may improve 
availability,  although that depends on the specific network topology 
and capabilities in the switch(es).    There is information on this in 
Documentation/networking/bonding.txt.


>> What is looped back frames here ?
> In this case they are frames that get received by the bond, which the bond
> itself sent.  In modes where more than one slave is active, and in which the
> switch has no additional knoweldge of the aggregate (e.g. round robin mode), the
> bond can send a frame on one slave, which the switch may broadcast to all ports,


Isn't this (broadcasting or repeating on all ports other than incoming) 
more associated with simple hubs rather than switches?     I would think 
any switch with layer 2 capability does not do that (does it?)

> causing the frame just sent by the bond to then get received on another slave.
>
>


  parent reply	other threads:[~2011-04-29 14:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28  7:33 Is 802.3ad mode in bonding useful ? WeipingPan
2011-04-28 12:21 ` Neil Horman
     [not found]   ` <0FBC7C9C2640634A8B837C2EFFCFF32F0184732D72@SHEXMB-01.global.atheros.com>
2011-04-28 13:23     ` 答复: " Neil Horman
2011-04-29  3:17   ` WeipingPan
2011-04-29 10:43     ` Neil Horman
2011-04-29 13:59       ` WeipingPan
2011-04-29 14:04       ` John Lumby [this message]
2011-04-29 15:21         ` Rick Jones
2011-04-29 17:01       ` Jay Vosburgh

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=4DBAC552.507@hotmail.com \
    --to=johnlumby@hotmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=panweiping3@gmail.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).