PowerConnect 2748 + Linux + link aggregation

[Thomas_Chenault at Dell.com]

Based on a quick browse through the documentation, it appears that the
2748 may not support 802.3ad/LACP. Assuming that this is true, the
appropriate solution would be to choose a different mode for the bond,
balance-xor perhaps.


Thomas

-----Original Message-----
From: Steve Thompson [mailto:smt at vgersoft.com] 
Sent: Friday, March 02, 2007 5:31 AM
To: Chenault, Thomas
Cc: linux-poweredge-Lists
Subject: RE: PowerConnect 2748 + Linux + link aggregation


On Thu, 1 Mar 2007, Thomas_Chenault at dell.com wrote:

> To me it sounds like the 802.3ad bond is failing to aggregate its
> members. The contents of /proc/net/bonding/bond<x> should provide more
> information. Specifically, the active aggregator for the bond should
be
> listed and the aggregator ID for each slave should be listed. If one
or
> more of the slaves has a different aggregator ID than the bond then
the
> aggregation has been less than fully successful.

Thomas,

Thanks very much for your rapid reply!

Mmm. I did check the /proc/net/bonding/bondX; it looked good, and 
certainly had the correct slaves. I'm going back down to bare metal
switch 
configuration, and then I'll look again. I need to also check that the 
ethX devices aren't getting reordered when the bonding module is loaded.

> One possible cause of failure to aggregate is configuring static link 
> aggregation groups on the switch rather than LACP groups.

Ah, so it appears that I may have have missed something in the switch 
configuration. I don't see any options in the web interface to configure

anything but LAG membership. The documentation doesn't appear to address

this at all; under the LAG section, it just shows an image of the LAG 
membership screen.

Steve