[f-nsp] link aggreagtion (lacp) with load balancing

[Mike Allen]

Edward, seems like there is confusion about trunking lately on the
list...:)  So as mentioned in my previous post to the list, there are two
different trunking options in the FastIron code base.  You are already
configured for 802.3ad Link Aggregation dynamically, and your trunk is up
and operational.  You do not need the static trunking, and that is why you
see that error.

As for the hash diversity, it all depends on what your flows look like.  By
default for ip traffic, it uses Source and destination IP addresses, and
source and destination TCP/UDP ports for the hash, so as long as those are
different, you should see outbound traffic spread accordingly.  Note that
unknown unicast, broadcast, and multicast traffic will all usually take on
the first port.  Unicast traffic is what would be load balanced.

Mike

On Mon, Jun 4, 2012 at 6:11 PM, Edward Rosinzonsky <ed at entetel.com> wrote:

> **
> Shameless bump.
> When I try to trunk the lacp ports, I get an error:
>
> trunk ethernet 3/3 to 3/4
> error - trunk ports contain LACP-enabled ports.
>
>
>
> Here's the relevant part of the config:
>
> interface ethernet 3/3
>  mtu 9000
>  link-aggregate configure key 10000
>  link-aggregate active
> !
> interface ethernet 3/4
>  link-aggregate configure key 10000
>  link-aggregate active
> !
>
>
>
>
> show link-ag:
> System ID: 000c.dba5.e840
> 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]
> 3/3        1        1   10000   Yes   L   Agg  Syn  Col  Dis  No   No   Ope
> 3/4        1        1   10000   Yes   L   Agg  Syn  Col  Dis  No   No   Ope
>
>
>
>
>
> show trunk:
> Configured trunks:
>
> Trunk ID: 66
> Type: Switch
> Ports_Configured: 2
> Primary Port Monitored: Jointly
>
> Ports         3/3     3/4
> Port Names    none    none
> Port_Status   enable  enable
> Monitor       off     off
> Mirror Port   N/A     N/A
> Monitor Dir   N/A     N/A
>
> Operational trunks:
>
> Trunk ID: 66
> Type: Switch
> Duplex: Full
> Speed: 1G
> Tag: No
> Priority: level0
> Active Ports: 2
>
>
> Ports         3/3     3/4
> Link_Status   active  active
> LACP_Status   ready   ready
> Load Sharing
>  Mac Address  6       5
>  IP           0       0
>  IPX          0       0
>  Apple Talk   0       0
>  Multicast    0       0
>
>
>
> On 04/12/2012 07:16 PM, Edward Rosinzonsky wrote:
>
> Hi,
>
> I'm trying to setup LAG between my si350 and the cisco switch.  I set up
> the LAG without problems, but all traffic just defaults to the first port
> in the LAG.
>
> On the cisco, I solve this problem with the following command:
> *port-channel load-balance src-dst-ip*
>
> But, I can't find anything similar for the foundry.  Anyone know how to do
> this?
>
> Thanks.
>
>
> _______________________________________________
> foundry-nsp mailing listfoundry-nsp at puck.nether.nethttp://puck.nether.net/mailman/listinfo/foundry-nsp
>
>
>
> _______________________________________________
> 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/20120604/8b617a9d/attachment.html>