From owner-freebsd-net@freebsd.org  Mon Oct  5 07:52:20 2015
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0681FA10F98
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Mon,  5 Oct 2015 07:52:20 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id E6F86E96
 for <freebsd-net@FreeBSD.org>; Mon,  5 Oct 2015 07:52:19 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t957qJOL083461
 for <freebsd-net@FreeBSD.org>; Mon, 5 Oct 2015 07:52:19 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 156226] [lagg]: failover does not announce the failover to switch
Date: Mon, 05 Oct 2015 07:52:19 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords: feature, needs-qa, patch
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: weberge42@gmail.com
X-Bugzilla-Status: Open
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: mfc-stable9? mfc-stable10?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-156226-2472-ReuixGXsZ8@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-156226-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-156226-2472@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Oct 2015 07:52:20 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=156226

--- Comment #12 from weberge42@gmail.com ---
Yes, but each switch has different default and miniumum values.
Fortiswitch: 10s, HP Procurve 60s, don't know about cisco.

So that would mean XXs no service in case of a failover which may be acceptable
if its short enough. But what if you can't (or not allowed) to change this
settings ? 

I don't quite understand what you mean with:

>And yes, lagg's failover needs that NIC drivers bring link down in case of >voluntary "ifconfig down"

Who issues the ifconfig down ? I just don't see any relationship between manual
ifconfig in case of a failover.
Can you please elaborate this a bit more ? Maybe i'm missing something.

-- 
You are receiving this mail because:
You are the assignee for the bug.