From: Ding Tianhong <dingtianhong@huawei•com>
To: Krisztian Ivancso <github-ivan@ivancso•net>
Cc: <netdev@vger•kernel.org>
Subject: Re: [PATCH net-next] bonding: lacp_port_id setting for 802.3ad
Date: Tue, 13 Aug 2013 17:39:08 +0800 [thread overview]
Message-ID: <5209FEBC.4050305@huawei.com> (raw)
In-Reply-To: <5209FA49.6030800@ivancso.net>
On 2013/8/13 17:20, Krisztian Ivancso wrote:
> On 08/13/2013 03:07 AM, Ding Tianhong wrote:
>> On 2013/8/12 19:19, Krisztian Ivancso wrote:
>>> >From 472fffa5a8f170daed9e4cc677af8e2560b86be2 Mon Sep 17 00:00:00 2001
>>> From: Krisztian Ivancso <github-ivan@ivancso•net>
>>> Date: Sun, 11 Aug 2013 20:30:44 +0200
>>> Subject: [PATCH net-next] bonding: lacp_port_id setting for 802.3ad ports
>>>
>>> By setting this parameter to different values on different hosts
>>> it's possible to add more Linux boxes to the same Link Aggregation.
>>>
>>
>> I think the port id was made by negotiation, if the negotiation failed, the bonding slave
>> could not get the port id you gave, which lie on the hardware message.
>
> Port id is currently preset to 1 in bonding driver for first slave.
> (SLAVE_AD_INFO(new_slave).id = 1; this id is used as
> actor_port_number in slave initialization)
> Port id parameter modifies just this starting value and new slaves
> get incremented port ids as in current implementation.
>
> As I see in documentation port id (port number) set by each
> participating devices by it's own and given values are used by
> the other side.
>
> In Cisco and Juniper documentations port id is mentioned, the value
> is derived from port number which is unique within a switch.
>
> Cisco:
>> LACP uses the port priority with the port number to form the
>> port identifier.
>
> Juniper:
>> The LACP port ID consists of the port priority as the two
>> most-significant octets and the port number as the two
>> least-significant octets.
>
>
> Cisco:
>> The LACP system ID is the combination of the LACP system priority
>> value and the MAC address.
>
> This is why we need to use the same MAC for all participating bonding
> device in different linux boxes.
>
>
> The solution is tested with Cisco devices.
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger•kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
ok, for example: the bonding has four slave, slave1 and slave2 aggregation to 1 group,
and slave3 and slave4 aggregtion to 2 group, how you distinguish the 1 and 2 group by initialize id.
--Ding Tianhong
next prev parent reply other threads:[~2013-08-13 9:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 11:19 [PATCH net-next] bonding: lacp_port_id setting for 802.3ad Krisztian Ivancso
2013-08-13 1:07 ` Ding Tianhong
2013-08-13 9:20 ` Krisztian Ivancso
2013-08-13 9:39 ` Ding Tianhong [this message]
2013-08-13 11:00 ` Krisztian Ivancso
2013-08-13 18:25 ` Jay Vosburgh
2013-08-13 23:34 ` Krisztian Ivancso
2013-08-14 1:46 ` Ding Tianhong
2013-08-16 2:07 ` Krisztian Ivancso
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=5209FEBC.4050305@huawei.com \
--to=dingtianhong@huawei$(echo .)com \
--cc=github-ivan@ivancso$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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