From owner-freebsd-net@freebsd.org  Sat Oct  3 21:59:25 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 C3066A0FA80
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Sat,  3 Oct 2015 21:59:25 +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 AF61612D3
 for <freebsd-net@FreeBSD.org>; Sat,  3 Oct 2015 21:59:25 +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 t93LxPsn095247
 for <freebsd-net@FreeBSD.org>; Sat, 3 Oct 2015 21:59:25 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: Sat, 03 Oct 2015 21:59:25 +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: In Progress
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-156226-2472-6KpIAC8dUW@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: Sat, 03 Oct 2015 21:59:25 -0000

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

--- Comment #8 from weberge42@gmail.com ---
(In reply to eugen from comment #7)

Yes, but if you have the following setup:

Server NIC1 - Switch 1
Server NIC2 - Switch 2

If NIC1 is active and Switch 1 fails, NIC2 becomes active and it takes ages to
see traffic flowing again.

I can't remember if the standby link is up but no traffic flowing or if it is
really down (down as in disabled).

I will try to investigate this a little bit further when i have access to the
switches again (tried with fortiswitch 548d, latest firmware)

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