From owner-freebsd-stable@FreeBSD.ORG Tue Aug 12 12:00:25 2008 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 E74C810657AC for ; Tue, 12 Aug 2008 12:00:25 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.freebsd.org (Postfix) with ESMTP id 7BCBB8FC16 for ; Tue, 12 Aug 2008 12:00:25 +0000 (UTC) (envelope-from max@love2party.net) Received: from vampire.homelinux.org (dslb-088-066-034-213.pools.arcor-ip.net [88.66.34.213]) by mrelayeu.kundenserver.de (node=mrelayeu8) with ESMTP (Nemesis) id 0ML31I-1KSsY02Amn-0006qW; Tue, 12 Aug 2008 14:00:23 +0200 Received: (qmail 36845 invoked from network); 12 Aug 2008 12:00:18 -0000 Received: from fbsd8.laiers.local (192.168.4.151) by laiers.local with SMTP; 12 Aug 2008 12:00:18 -0000 From: Max Laier Organization: FreeBSD To: freebsd-stable@freebsd.org, eugen@kuzbass.ru Date: Tue, 12 Aug 2008 14:00:18 +0200 User-Agent: KMail/1.10.0 (FreeBSD/8.0-CURRENT; KDE/4.1.0; i386; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200808121400.18440.max@love2party.net> X-Provags-ID: V01U2FsdGVkX19PRxNHiCxG7B0L7ZHsHIPk5DWEownFajsXBHQ 8oYHevQmJ+D73tndzYiiW0QwBUcPo7DDKcKMhQmibKQzugwEF9 y/WHWXKzgNdu1j5NWdoag== Cc: Pete French , 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, 12 Aug 2008 12:00:26 -0000 On Tuesday 12 August 2008 13:43:29 Marian Hettwer wrote: > Hi Pete, > > On Tue, 12 Aug 2008 12:30:12 +0100, Pete French > > wrote: > >> However, IMO lacp doesn't solve that problem. lacp is used for link > >> aggregation, not failover. > > > > It does both - if one of the links becomes unavailable then it will > > stop using it. We use this for failover and it works fine, the only > > caveat being that your LACP device at the far end needs to look like > > a single phsyical device (the nicer Cisco switches do this quite happily) > > thanks for that info. > > >> The manpage states "In the event of changes in physical > > > > connectivity...". > > > >> Again, does that mean, the link needs to be physically unavailable? If > > > > so, > > > >> it'll be the same behaviour as in failover mode and doesn't solve my > >> problem of a misconfigured switch... > > > > lagg is to handle failover at the physical layer for when one of your > > ether ports fails, or someone unplugs a cable. If I understand you > > correctly you are looking for something at the next layer up, to handle > > a problem where the ports work fine, but are not going to their expected > > destinations. lagg won't do this. > > Thats unfortunate... > bonding in Linux is capable of doing this and solaris too. > Well then. At least everythings clear now. And in the end, clarifing things > was the reason for that mail thread :) You are looking for net/ifstated -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News