[f-nsp] Loadbalacing (Trunking/LACP) on foundry MLX: unequal loaddistribution.

[Gunther Stammwitz]

Hello everyone,

Thanks a lot for your feedback.

The solution was simple: 'trunk server' instead of 'trunk switch' solved the
problem.

By the way there's a bug in the 3.2-software: Show interface will show you
only half of the real load on the interface.


Gunther


> -----Ursprüngliche Nachricht-----
> Von: foundry-nsp-bounces at puck.nether.net 
> [mailto:foundry-nsp-bounces at puck.nether.net] Im Auftrag von 
> Gunther Stammwitz
> Gesendet: Montag, 5. Februar 2007 20:01
> An: foundry-nsp at puck.nether.net
> Betreff: [f-nsp] Loadbalacing (Trunking/LACP) on foundry MLX: 
> unequal loaddistribution.
> 
> Hello colleagues,
> 
> I'm using a foundry mlx that connects to an IXP with 2 GIGEs.
> We have created an LACP-Trunk but the traffic doesn't really 
> balance as
> intended:
> 
> One interface is at 922mbits outgoing while the other is just 
> at 550 mbits.
> 
> Any idea how we could optimize this? How does the 
> loadbalancing algorith on the mlx work? Is it 
> per-mac-destination or per-flow? To me it looks like per mac 
> and the algorith seems to be too stupid to move some load 
> from one interface to the other.
> 
> Any idea what to do?
> 
> Thanks,
> Gunther
> 
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
> 
>