Date: Mon, 03 Feb 2014 10:10:54 +0100 From: Ben <mailinglists@niessen.ch> To: freebsd-net@freebsd.org Subject: Re: kern/185967: Link Aggregation LAGG: LACP not working in 10.0 Message-ID: <52EF5D1E.2000306@niessen.ch> In-Reply-To: <1798FE17-5718-4125-8B00-1B00DC44B828@yahoo.com> References: <52EF50A7.1050205@niessen.ch> <1C608452-6F29-486D-BC0F-CCC7853665C7@yahoo.com> <52EF55FE.8030901@niessen.ch> <1798FE17-5718-4125-8B00-1B00DC44B828@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I set strict mode to 0 but no use. I do receive PDU messages. igb0: lacpdu transmit actor=3D(...) actor.state=3D4d<ACTIVITY,AGGREGATION,SYNC,DEFAULTED> partner=3D(...) partner.state=3D0 maxdelay=3D0 Thanks Ben On 03.02.2014 10:03, Scott Long wrote: > Hi, > > Unfortunately, you can=92t control the strict mode globally. My apolog= ies 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 kerne= l 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. > > Scott > > On Feb 3, 2014, at 1:40 AM, Ben <mailinglists@niessen.ch> wrote: > >> Hi Scott, >> >> I had tried to set it in /etc/sysctl.conf but seems it didnt work. But= will I try again and report back. >> >> 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 s= ome incompatibility between FreeBSD + igb-driver + switch (Juniper EX3300= -48T). >> >> I will update you after setting the sysctl setting. It seems to be "dy= namic", I guess 0 reflects the index of LACP lagg devices. Can I switch o= ff 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= 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 tha= t 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 actuall= y support LACP at all. You might want to investigate that. >>> >>> Scott >>> >>> On Feb 3, 2014, at 1:17 AM, Ben <mailinglists@niessen.ch> wrote: >>> >>>> Hi, >>>> >>>> I upgraded from FreeBSD 9.2-RELEASE to 10.0-RELEASE. FreeBSD 9.2 was= configured 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=3D= kern/185967 >>>> >>>> It is set to low, but I would like somebody to have a look into it a= s 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.or= g" >>> _______________________________________________ >>> 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" > _______________________________________________ > 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,52ef5c19888823082815771! > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52EF5D1E.2000306>