From owner-freebsd-net@FreeBSD.ORG Mon Feb 3 09:25:16 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 6E7D0FC9 for ; Mon, 3 Feb 2014 09:25:16 +0000 (UTC) Received: from nm13.bullet.mail.ne1.yahoo.com (nm13.bullet.mail.ne1.yahoo.com [98.138.90.76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1F42B10DB for ; Mon, 3 Feb 2014 09:25:15 +0000 (UTC) Received: from [98.138.100.117] by nm13.bullet.mail.ne1.yahoo.com with NNFMP; 03 Feb 2014 09:25:09 -0000 Received: from [98.138.226.56] by tm108.bullet.mail.ne1.yahoo.com with NNFMP; 03 Feb 2014 09:25:09 -0000 Received: from [127.0.0.1] by smtp207.mail.ne1.yahoo.com with NNFMP; 03 Feb 2014 09:25:09 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1391419509; bh=8+1u7DVz81MFZYdczfqv2n5Co8wbDIj/G2D2oXy8MoA=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer; b=1hfzr2rKhjAPhbRdTOFb/ev8cjh0wXknj2QIy1duNwXmeIBA/bb9SIYinSBEoBlcIlzk/x0CET2umTJCvqh+E0g+1hhZcy6QDYEZcdOm2IMRPvV9RogVNMB+qW+J0d4qLpKrJrsyDNLRxaTNXkExRQUuQo/vAAV4hW17E5NZ2QQ= X-Yahoo-Newman-Id: 616816.82018.bm@smtp207.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: nh1qtLcVM1muDQCx3vnWjqwkdchMlIH_E30pjq1ELr1L5iV o2ssr7ovuZmc0loHstlcAlrDCXdjWMaUkJ3ytNp_g_uTmIYnqlH3QGH5TvlY GzJVpkdgyY3kKc_molBEXjh5tttMT4VVFU9b_ob5fmO5zP7zlnPBgSkZ603X lQOwSxNZBoSfyO80gcot9M2PmBWJ4LvXthi4Zlo3NsIbMpIlrg.8MJLb08ti nJk1W7iJZB5Xw7EEfcrQg5e2Hjxhe06f_f4A28ECXFyomo3rwHMhGaHnUrLa D4AEXEFp2L8D8GPHD3m5CoktkUufqYpn9t9Y04kM1lLaQA7NHM3BlpCytKGD FRyET0lW5vqtZvFaR5SxUipjfxl6bf0eJYLz1GIMiXXtNypqwE8sWD2Tk1sa OLsk8h18OS6FxsC8HYRYK.FsabNgkiCSBOoMlBB6x4D.aIlv8ZNXNG9WTmBk tX4KfunxwtR0g1DUgzus1oeKCWl35K.jLPP1cXQfxDTU3UZv0qV62VrU4hGC HBB9U7LqNVTKswXrjSHjudrenmSOtC__GIgtI.GM.FqoLbMP59B1.GhjvdxI 3n9jzs6Jfb8uwfbRzRBubekO.ZY57bkYXmm4Cj1wfCLaXYj4ugVpKpStNcd7 xH0QSW_IIISrXJwTiIwN40KTP_nbLn1Tw19MNqlsPQt273jLUNf4- X-Yahoo-SMTP: clhABp.swBB7fs.LwIJpv3jkWgo2NU8- X-Rocket-Received: from [10.64.24.117] (scott4long@69.53.236.251 with plain [98.138.105.21]) by smtp207.mail.ne1.yahoo.com with SMTP; 03 Feb 2014 01:25:09 -0800 PST Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: kern/185967: Link Aggregation LAGG: LACP not working in 10.0 From: Scott Long In-Reply-To: <52EF5D1E.2000306@niessen.ch> Date: Mon, 3 Feb 2014 02:25:06 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <52EF50A7.1050205@niessen.ch> <1C608452-6F29-486D-BC0F-CCC7853665C7@yahoo.com> <52EF55FE.8030901@niessen.ch> <1798FE17-5718-4125-8B00-1B00DC44B828@yahoo.com> <52EF5D1E.2000306@niessen.ch> To: Ben X-Mailer: Apple Mail (2.1827) Cc: FreeBSD Net 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 09:25:16 -0000 Did you set it to 0 via the sysctl? You might need to wait for several = minutes if you set it after setting up the links. Also, the message that you=92re seeing is from your machine transmitting = PDU packets. Are you seeing any "lacpdu receive=94 messages on the = console? Thanks, Scott On Feb 3, 2014, at 2:10 AM, Ben wrote: > Hi, >=20 > I set strict mode to 0 but no use. I do receive PDU messages. >=20 > igb0: lacpdu transmit > actor=3D(...) > actor.state=3D4d > partner=3D(...) > partner.state=3D0 > maxdelay=3D0 >=20 > Thanks > Ben >=20 > On 03.02.2014 10:03, Scott Long wrote: >> Hi, >>=20 >> Unfortunately, you can=92t control the strict mode globally. My = apologies for this mess, I=92ll make sure that it=92s fixed for FreeBSD = 10.1. If the sysctl doesn=92t help then maybe consider compiling a = custom kernel with it defaulted to 0. You=92ll need to open = /sys/net/ieee802ad_lacp.c and look for the function lacp_attach(). = You=92ll see the strict_mode assign underneath that. I=92ll also send = you a patch in a few minutes. Until then, try enabling = net.link.lagg.lacp.debug=3D1 and see if you=92re receiving heartbeat = PDU=92s from your switch. >>=20 >> Scott >>=20 >> On Feb 3, 2014, at 1:40 AM, Ben wrote: >>=20 >>> Hi Scott, >>>=20 >>> I had tried to set it in /etc/sysctl.conf but seems it didnt work. = But will I try again and report back. >>>=20 >>> The settings of the switch have not been changed and are set to = LACP. It worked before so I guess the switch should not be the problem. = Maybe some incompatibility between FreeBSD + igb-driver + switch = (Juniper EX3300-48T). >>>=20 >>> I will update you after setting the sysctl setting. It seems to be = "dynamic", I guess 0 reflects the index of LACP lagg devices. Can I = switch off the strict mode globally in /etc/sysctl.conf? >>>=20 >>> Thanks for your help. >>>=20 >>> Regards >>> Ben >>>=20 >>> On 03.02.2014 09:31, Scott Long wrote: >>>> Hi, >>>>=20 >>>> You=92re probably running into the consequences of r253687. Check = to see the value of =91sysctl net.link.lagg.0.lacp.lacp_strict_mode=92. = If it=92s =911=92 then set it to 0. My original intention was for this = to default 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 switch either isn=92t configured correctly for LACP, or doesn=92t = actually support LACP at all. You might want to investigate that. >>>>=20 >>>> Scott >>>>=20 >>>> On Feb 3, 2014, at 1:17 AM, Ben wrote: >>>>=20 >>>>> Hi, >>>>>=20 >>>>> I upgraded from FreeBSD 9.2-RELEASE to 10.0-RELEASE. FreeBSD 9.2 = was configured to use LACP with two igb devices. >>>>>=20 >>>>> Now it stopped working after the upgrade. >>>>>=20 >>>>> 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= >>>>>=20 >>>>> A PR is currently open: = http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/185967 >>>>>=20 >>>>> 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. >>>>>=20 >>>>> The suggested fix "use failover" seems not to work. >>>>>=20 >>>>> Thank you for your help. >>>>>=20 >>>>> 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" >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>> _______________________________________________ >>> 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" >>=20 >> !DSPAM:1,52ef5c19888823082815771! >>=20 >>=20 >=20 > _______________________________________________ > 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"