From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 09:37:43 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2B86106564A for ; Tue, 9 Dec 2008 09:37:43 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 71EC18FC19 for ; Tue, 9 Dec 2008 09:37:43 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id 12DA1172D8; Tue, 9 Dec 2008 20:22:12 +1100 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.20.30.101] (60.218.233.220.exetel.com.au [220.233.218.60]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id BDCD41732D; Tue, 9 Dec 2008 20:21:59 +1100 (EST) Message-ID: <493E38B5.30608@modulus.org> Date: Tue, 09 Dec 2008 20:21:57 +1100 From: Andrew Snow User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Tom Samplonius References: <11397385.9861228809480949.JavaMail.root@ly.sdf.com> In-Reply-To: <11397385.9861228809480949.JavaMail.root@ly.sdf.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, Pete French , Peter Jeremy , eugen@kuzbass.ru, bseklecki@collaborativefusion.com, Marian Hettwer Subject: Re: lagg(4) and failover 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: Tue, 09 Dec 2008 09:37:43 -0000 > lagg is ultimately a problem as a high-availability solution since most switches do not support multi-switch 802.3ad yet, and most probably never well. So you are limited to a single switch. So 802.3ad is good only for aggregation, and not for high availability. What about using STP or RSTP instead of lagg? Which L2 managed switches like 3com and HP support. Then you could connect each of two NICs to a different switch, as well as connect the switches to each other.