From: "Lewis Li" <lachang.li@zyxel.com.tw>
To: <linux-kernel@vger.kernel.org>
Subject: Re: 2 ports could not bond to a aggregator in 802.3ad mode issue
Date: Thu, 27 Dec 2007 10:48:00 +0800 [thread overview]
Message-ID: <001501c84832$e4bb3d60$431a17ac@ZyXEL.com> (raw)
In-Reply-To: 23058.1198709236@death
Yes, you are right. The incorrect behavior is due to we don't setup the
lacpdu of switch correctly.
The bonding driver is correct. Thanks for your comment!
> I do not believe so.
>
> IEEE 802.3 section 43.3.9 states, in part,
>
> "Links that are not successful candidates for aggregation (e.g.,
> links that are attached to other devices that cannot perform aggregation
> or links that have been manually configured to be non-aggregatable) are
> enabled to operate as individual IEEE 802.3 links. For consistency of
> modeling, such a link is regarded as being attached to a compatible
> Aggregator that can only be associated with a single link. That is, from
> the perspective of Link Aggregation, non-aggregated links are not a
> special case; they compose an aggregation with a maximum membership of
> one link."
>
> I do not see that it is correct to attach the links to a common
> aggregator, as your output indicates that no partner association has
> been created (the Partner MAC is all zeroes) and the links are therefore
> apparently connected to a device that cannot perform aggregation.
>
> ---
> -Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
Regards,
Lewis Li
prev parent reply other threads:[~2007-12-27 2:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-25 7:40 2 ports could not bond to a aggregator in 802.3ad mode issue lewis_zyxel
[not found] ` <20071226141301.8231163b.akpm@linux-foundation.org>
2007-12-26 22:47 ` Jay Vosburgh
2007-12-27 2:48 ` Lewis Li [this message]
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='001501c84832$e4bb3d60$431a17ac@ZyXEL.com' \
--to=lachang.li@zyxel.com.tw \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.