From owner-freebsd-net@FreeBSD.ORG Mon Feb 3 08:40:55 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ACC8634C for ; Mon, 3 Feb 2014 08:40:55 +0000 (UTC) Received: from mail.niessen.ch (btx02.niessen.ch [85.10.192.239]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 34D701C41 for ; Mon, 3 Feb 2014 08:40:54 +0000 (UTC) Received: from mail.niessen.ch (mail.niessen.ch [127.0.10.3]) by mail.niessen.ch (Postfix) with ESMTP id 296EF102AA4 for ; Mon, 3 Feb 2014 09:40:53 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=niessen.ch; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; s=dkim-2012; bh=qqTLKiA hbwR5Hgm18Av6Xin2egFXy5t9hKafm2hS/UE=; b=DvW1RZkuRrE85/SRP2wSULa 4Ci4DvspkrK42X2MdlCQ4n5Ys6eqbcd7F/ec8fKgIL7384C9oRtPTfbZCRQCDjjA +7r3k3LwsebZ79m5n5lNXS3RizhoiKNc9351iTeTIMuXlqWudnWawjYOORxq7PVG a1YeyFXaK5xnIEJExBBw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=niessen.ch; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=dkim-2012; b=f Dch9NVZ6Rb+ENG6DN615GM9/mrESO3Bpy1yYyNqzzehkvYaUp0LytqLCHzUPLv7q +Y5SPKhis4IYgTjNNCyCN6/9vz1Zj6u9KS9CpflYF1Y/B+lOZL44cx0Pb9aXDejW xIwnlsMLRaXPsbtI1HQWC/2a+TGbkIorh+6h0N/SB0= Received: from [172.20.10.3] (unknown [178.197.236.128]) by mail.niessen.ch (Postfix) with ESMTPSA id F313D102AA3 for ; Mon, 3 Feb 2014 09:40:52 +0100 (CET) Message-ID: <52EF55FE.8030901@niessen.ch> Date: Mon, 03 Feb 2014 09:40:30 +0100 From: Ben User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: kern/185967: Link Aggregation LAGG: LACP not working in 10.0 References: <52EF50A7.1050205@niessen.ch> <1C608452-6F29-486D-BC0F-CCC7853665C7@yahoo.com> In-Reply-To: <1C608452-6F29-486D-BC0F-CCC7853665C7@yahoo.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Feb 2014 08:40:55 -0000 Hi Scott, I had tried to set it in /etc/sysctl.conf but seems it didnt work. But=20 will I try again and report back. The settings of the switch have not been changed and are set to LACP. It=20 worked before so I guess the switch should not be the problem. Maybe=20 some incompatibility between FreeBSD + igb-driver + switch (Juniper=20 EX3300-48T). I will update you after setting the sysctl setting. It seems to be=20 "dynamic", I guess 0 reflects the index of LACP lagg devices. Can I=20 switch off the strict mode globally in /etc/sysctl.conf? Thanks for your help. Regards Ben On 03.02.2014 09:31, Scott Long wrote: > Hi, > > You=92re probably running into the consequences of r253687. Check to s= ee the value of =91sysctl net.link.lagg.0.lacp.lacp_strict_mode=92. If i= t=92s =911=92 then set it to 0. My original intention was for this to de= fault to 0, but apparently that didn=92t happen. However, the fact that = strict mode doesn=92t seem to work at all for you might hint that your sw= itch either isn=92t configured correctly for LACP, or doesn=92t actually = support LACP at all. You might want to investigate that. > > Scott > > On Feb 3, 2014, at 1:17 AM, Ben wrote: > >> Hi, >> >> I upgraded from FreeBSD 9.2-RELEASE to 10.0-RELEASE. FreeBSD 9.2 was c= onfigured to use LACP with two igb devices. >> >> Now it stopped working after the upgrade. >> >> This is a screenshot of ifconfig -a after the upgrade to FreeBSD 10.0-= RELEASE: http://tinypic.com/view.php?pic=3D28jvgpw&s=3D5#.Uu9PXT1dVPM >> >> A PR is currently open: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dk= ern/185967 >> >> It is set to low, but I would like somebody to have a look into it as = it obviously has a great influence on our infrastructure. The only way to= "solve" it is currently switching back to FreeBSD 9.2. >> >> The suggested fix "use failover" seems not to work. >> >> Thank you for your help. >> >> Best regards >> Ben >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > !DSPAM:1,52ef53f7888821422342440! > >