Link aggregation goes by many different names. Trunking and Etherchannel are both pretty much the same thing..
----- Original Message ----- From: "Francis Avila" <[EMAIL PROTECTED]> To: "Conrad Lawes" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "LTSP discussion list" <[EMAIL PROTECTED]> Sent: Saturday, October 19, 2002 10:05 PM Subject: Re: [Ltsp-discuss] Link aggregation [Was: Colision when using ltsp] > ----- Original Message ----- > From: "Conrad Lawes" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]>; "LTSP discussion list" > <[EMAIL PROTECTED]> > Sent: Saturday, October 19, 2002 19:48 > Subject: Re: [Ltsp-discuss] Link aggregation [Was: Colision when using ltsp] > [...] > > The problem with this strategy is that most of the link aggregation > technologies are NIC vendor dependant where NIC drivers and switches would > communicate using proprietary protocol. The IEEE 802.3ad Port Aggregation > standard will address this issue. Also, the link aggregation NIC driver > software is usually written primarily for NetWare or Windows network > operating system. So you may have to do some research to find a Linux-based > solution. > [end] > > What you're referring to is also (I believe) called trunking, EtherChannel, > or channel bonding. If this is not the same technology, then it's an > alternative that does pretty much the same thing, plus works with Linux. > It's included in all kernels >2.4.12, although you might need to recompile. > > Look at Documentation/networking/bonding.txt in any recent kernel source. > > You'll also need a small userspace utility to actually bond the interfaces, > but the source for this is also included with the kernel source: > Documentation/networking/ifenslave.c > > There are three different transmission policies: > > Round robin, based on the order of enslaving, the output device > is selected base on the next available slave. Regardless of > the source and/or destination of the packet. > > XOR, based on (src hw addr XOR dst hw addr) % slave cnt. This > selects the same slave for each destination hw address. > > Active-backup policy that ensures that one and only one device will > transmit at any given moment. Active-backup policy is useful for > implementing high availability solutions using two hubs (see > section on HA). > > If you only want high availability, you don't need any special hardware. If > you want load balancing, you will almost certainly need a switch that > supports bonding. A small, representative list is included in the > bonding.txt files (in my experience, any mid-range or better switch has > support for this). However, bonding is independent of Ethernet drivers. > You can even mix makes and models of cards in a single channel. > > > Stolen from bonding.txt: > Resources and links > =================== > > Current developement on this driver is posted to: > - http://www.sourceforge.net/projects/bonding/ > > Donald Becker's Ethernet Drivers and diag programs may be found at : > - http://www.scyld.com/network/ > > You will also find a lot of information regarding Ethernet, NWay, MII, etc. > at > www.scyld.com. > > For new versions of the driver, patches for older kernels and the updated > userspace tools, take a look at Willy Tarreau's site : > - http://wtarreau.free.fr/pub/bonding/ > - http://www-miaif.lip6.fr/willy/pub/bonding/ > > To get latest informations about Linux Kernel development, please consult > the Linux Kernel Mailing List Archives at : > http://boudicca.tux.org/hypermail/linux-kernel/latest/ > > -- > Francis Avila > > ------------------------------------------------------- This sf.net email is sponsored by: Access Your PC Securely with GoToMyPC. Try Free Now https://www.gotomypc.com/s/OSND/DD _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
