In my experience, LAG/LACP won't provide aggregatation, only failover and fault tolerance. For link aggregation, you don't need to configure the switch ports - just set bonding to mode=6 for balanced transmit/receive and plug up the the NICs to a group of ports on the switch. However, balance-alb doesn't help with single stream rsync/FTP sessions, etc, but helps a lot with concurrent transmits/receives as encountered in typical fileserver scenarios.
- c
On 06/08/12 17:00, centos-request@centos.org wrote:
Message: 30 Date: Mon, 06 Aug 2012 13:56:41 +0100 From: Giles Coochey giles@coochey.net Subject: Re: [CentOS] Configure LAGG Interface? To: centos@centos.org Message-ID: 501FBF09.5080206@coochey.net Content-Type: text/plain; charset="iso-8859-1"
On 02/08/2012 02:00, Tim Nelson wrote:
----- Original Message -----
On 01.08.2012 21:17, Tim Nelson wrote:
> Greetings- I'd like to configure multiple copper NICs on a server > running CentOS 6.2 in a LAGG configuration for better throughput to > the core switch. After quite a bit of searching, I'm not seeing > anything of the sort. Is LAGG specific to the BSD world and the HP > switches I'm running? Or, does it go by a different name? Bonding > perhaps? If so, is bonding compatible with LAGG? > > --Tim > _______________________________________________ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos
Hi Tim,
In Centos you would be doing "nic bonding", it's the same thing.
The big question though, can I bond two NICs on a CentOS system, and connect those interfaces to two LAGG ports on my switches?
http://centoshelp.org/networking/nic-bonding/
Configure the switches as a LACP port-channel, you probably want to use a host mode (e.g. silent) configuration.
-- Regards, Giles Coochey, CCNA, CCNAS NetSecSpec Ltd +44 (0) 7983 877438 http://www.coochey.net http://www.netsecspec.co.uk giles@coochey.net
Am 06.08.2012 um 19:22 schrieb Cal Sawyer cal-s@blue-bolt.com:
In my experience, LAG/LACP won't provide aggregatation, only failover and fault tolerance. For link aggregation, you don't need to configure the switch ports - just set bonding to mode=6 for balanced transmit/receive and plug up the the NICs to a group of ports on the switch. However, balance-alb doesn't help with single stream rsync/FTP sessions, etc, but helps a lot with concurrent transmits/receives as encountered in typical fileserver scenarios.
On FreeBSD, you don't get 2*1 Gbit from A to B, but 1*1 Gbit from A to B and another 1*1 Gbit from C to B. "B" being the server with the LAGG interface.
How is that in CentOS?
Am 06.08.2012 19:44, schrieb Rainer Duffner:
Am 06.08.2012 um 19:22 schrieb Cal Sawyer cal-s@blue-bolt.com:
In my experience, LAG/LACP won't provide aggregatation, only failover and fault tolerance. For link aggregation, you don't need to configure the switch ports - just set bonding to mode=6 for balanced transmit/receive and plug up the the NICs to a group of ports on the switch. However, balance-alb doesn't help with single stream rsync/FTP sessions, etc, but helps a lot with concurrent transmits/receives as encountered in typical fileserver scenarios.
On FreeBSD, you don't get 2*1 Gbit from A to B, but 1*1 Gbit from A to B and another 1*1 Gbit from C to B. "B" being the server with the LAGG interface.
How is that in CentOS?
It is of course the same, as long as we speak about standardized 802.3ad protocol.
Alexander
-
Alexander Dalloz -
Cal Sawyer -
Rainer Duffner