[f-nsp] linux 802.3ad bonding with foundry switch

[Mike Allen]

Off-hand, I think you want to go with link-agg active as opposed to
passive.  Not sure about the trunk commands, normally that would be for
setting up static trunks, but I don't remember the exact process in older
versions of switch and code (which I am guessing this is).  If you could
send model and version, that would probably help, the link aggregation
config has changed pretty dramatically over the years.

Mike
On Thu, Sep 22, 2011 at 7:51 PM, panicloop <panicloop at gmail.com> wrote:

> We did the connection test between cisco switch and linux server
> for "802.3ad bonding" mode.
>
> And we confirmed the following cisco's configuration works OK.
>
> --- begin ---
> !
> interface Port-channel1
>  switchport mode access
> !
> interface GigabitEthernet0/1
>  switchport mode access
>  channel-group 1 mode active
> !
> interface GigabitEthernet0/2
>  switchport mode access
>  channel-group 1 mode active
> !
> --- end ---
>
> And this time, we need to replace the cisco with the foundry switch.
> We did the foundry settings like following, but this doesn't works.
>
> --- begin ---
> !
> interface ethernet 9
>  link-aggregate passive
> !
> interface ethernet 10
>  link-aggregate passive
> !
> --- end ---
>
> Please anyone tell me how shoud I configure foundry switch.
> Should we do like following?
>
> --- begin ---
> trunk ethernet 9 to 10
> write memory
> trunk deploy
> --- end ---
>
> Sorry , I'm a linux guy and don't know much about switch.
> We need to connect the foundry switch and linux server using "802.3ad
> bonding mode".
> Thanks in advance.
>
> ______________________________**_________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/**mailman/listinfo/foundry-nsp<http://puck.nether.net/mailman/listinfo/foundry-nsp>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20110922/3fd48fca/attachment.html>