From owner-freebsd-stable@FreeBSD.ORG Fri Feb 4 17:13:44 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9EE1106566C for ; Fri, 4 Feb 2011 17:13:44 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 56D2B8FC0A for ; Fri, 4 Feb 2011 17:13:43 +0000 (UTC) Received: by wwf26 with SMTP id 26so2487200wwf.31 for ; Fri, 04 Feb 2011 09:13:43 -0800 (PST) Received: by 10.227.132.149 with SMTP id b21mr1683187wbt.48.1296839623267; Fri, 04 Feb 2011 09:13:43 -0800 (PST) Received: from dfleuriot.technique-admin.paris.hi-media-techno.com ([83.167.62.196]) by mx.google.com with ESMTPS id x1sm677971wbh.14.2011.02.04.09.13.39 (version=SSLv3 cipher=RC4-MD5); Fri, 04 Feb 2011 09:13:39 -0800 (PST) Message-ID: <4D4C33C3.9070805@my.gd> Date: Fri, 04 Feb 2011 18:13:39 +0100 From: Damien Fleuriot User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Freddie Cash References: <4D4BED80.5060806@my.gd> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "freebsd-stable@freebsd.org" Subject: Re: link aggregation - bundling 2 lagg interfaces together X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Feb 2011 17:13:44 -0000 On 2/4/11 4:55 PM, Freddie Cash wrote: > On Fri, Feb 4, 2011 at 4:13 AM, Damien Fleuriot wrote: >> I have a firewall with 2x Intel pro dual port cards. >> >> On Intel A , port 1 goes to switch 1, port 2 goes to switch 2 >> On Intel B , port 1 goes to switch 1, port 2 goes to switch 2 >> >> I have created the following 2 lagg devices using LACP: >> >> lagg0 = A1 + B1 >> lagg1 = A2 + B2 >> >> This works fine. >> >> Now, what I had in mind was creating a lagg2 device using lagg0 and >> lagg1 with failover. >> >> That would provide redundancy in case of a switch failure. > > Couple different options: > - create a single lagg0 device using all port NIC ports > - create your lagg0 using A1 + B2, and your lagg1 using A2+B1 > > Both of those will give you fail-over support for losing a single NIC > port, an entire NIC, or an entire switch. > > Of course, if your switched aren't stacked to support LACP across > them, then you will be limited to a single links bandwidth. But you > will be extremely safe. :) Well, if I create lagg0 A1 + B2 and lagg1 A2+B1 , I'll end up with 2 laggs. How though, to I bind my vlan interfaces to *both* laggs ? I'm not sure that can be done. Currently and in the interim, I've put our WAN vlan on lagg0 and our 2 internal vlans on lagg1 ;)