[f-nsp] LACP with Foundry and Linux Machine

George B. georgeb at gmail.com
Thu Mar 27 14:32:39 EDT 2014


Did you set the lacp_rate option?

e.g: bonding mode=4 miimon=100 lacp_rate=1

The default is 0 or "slow" (30 sec). set to 1 (fast, 1 sec) and see if that
makes any difference.



On Thu, Mar 27, 2014 at 11:27 AM, Rupesh Basnet <brupesh at subisu.net.np>wrote:

>  Hi George,
>
> First I tried mode 4(802.3ad) at first but LACP didn't formed at all.
>
> Regards,
> --------
> Rupesh Basnet
>
>
> On 03/28/2014 12:09 AM, George B. wrote:
>
> "I have configured my linux box on mode 0"
>
>  Wouldn't you need to use mode 4?
>
>  802.3ad or 4
>
> 		IEEE 802.3ad Dynamic link aggregation.  Creates
> 		aggregation groups that share the same speed and
> 		duplex settings.  Utilizes all slaves in the active
> 		aggregator according to the 802.3ad specification.
>
>
>
> On Thu, Mar 27, 2014 at 10:44 AM, Rupesh Basnet <brupesh at subisu.net.np>wrote:
>
>> Hi All,
>>
>> I have been trying LACP between Foundry and Linux machine since some days
>> but not able to figure out the issue and resolve the issue. I didn't see
>> much configurations thats needs to be done on foundry. I have configured my
>> linux box on mode 0 and bonding seems to be up but still I am not able to
>> pass traffic through it.
>>
>> Serveriron Configurations:
>>
>> interface ethernet 4/2
>>  port-name **LACP-with-Linux***
>>  no spanning-tree
>>  link-aggregate active
>> !
>> interface ethernet 4/3
>>  port-name **LACP-with-Linux***
>>  no spanning-tree
>>  link-aggregate active
>> !
>>
>>
>> SI#show version
>>   SW: Version 09.3.00eTD4 Copyright (c) 1996-2003 Foundry Networks, Inc.
>>       Compiled on Jun 28 2005 at 18:57:32 labeled as WXR09300e
>>   HW: ServerIronGT E-2 Router, SYSIF version 21, Serial #: Non-exist
>> ==========================================================================
>> SL 1: B0GMR WSM2 Management Module, SYSIF 2, M6, ACTIVE
>>       Serial #:   CH39040033
>>     0 MB SHM, 2 Application Processors
>> 16384 KB BRAM, SMC version 1, BM version 21
>>   SW: (1)09.3.00eTF2 (2)09.3.00eTF2
>> ==========================================================================
>> SL 4: J-BxGC16 JetCore Gig Copper Module, SYSIF 2
>>       Serial #:   CH33060779
>>  4096 KB BRAM, JetCore ASIC IGC version 49, BIA version 8a
>> 32768 KB PRAM and 2M-Bit*1 CAM for IGC 12, version 0449
>> 32768 KB PRAM and 2M-Bit*1 CAM for IGC 13, version 0449
>> 32768 KB PRAM and 2M-Bit*1 CAM for IGC 14, version 0449
>> 32768 KB PRAM and 2M-Bit*1 CAM for IGC 15, version 0449
>>
>>
>> SI#show link-aggregate
>> System ID: 000c.db5d.b066
>> Long  timeout: 90, default: 90
>> Short timeout: 3, default: 3
>> Port  [Sys P] [Port P] [ Key ]
>> [Act][Tio][Agg][Syn][Col][Dis][Def][Exp][Ope]
>> 4/2        1        1     483   Yes   S   Agg  Syn  Col  Dis  Def No   Ope
>> 4/3        1        1     483   Yes   S   Agg  Syn  Col  Dis  Def No   Ope
>>
>>
>> Status of linux machine:
>> MII Status: up
>> MII Polling Interval (ms): 30000
>> Up Delay (ms): 0
>> Down Delay (ms): 0
>>
>> Slave Interface: eth0
>> MII Status: up
>> Speed: 1000 Mbps
>> Duplex: full
>> Link Failure Count: 0
>> Permanent HW addr: 00:e0:ed:2b:a1:99
>> Slave queue ID: 0
>>
>> Slave Interface: eth1
>> MII Status: up
>> Speed: 1000 Mbps
>> Duplex: full
>> Link Failure Count: 0
>> Permanent HW addr: 00:e0:ed:2b:a1:98
>> Slave queue ID: 0
>>
>> --
>> Regards,
>> --------
>> Rupesh Basnet
>>
>> _______________________________________________
>> foundry-nsp mailing list
>> foundry-nsp at puck.nether.net
>> http://puck.nether.net/mailman/listinfo/foundry-nsp
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20140327/2eda5536/attachment.html>


More information about the foundry-nsp mailing list