Date: Mon, 03 Feb 2014 11:00:45 +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: <52EF68CD.8020501@niessen.ch> In-Reply-To: <CAEW%2BogbYWEGRfR7XWwvqSr%2B-M1yeH3DsZp1FG7hyWUKvk3eRbA@mail.gmail.com> 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> <B2A60D0D-26AA-4EB4-B5E6-D44164C9AE83@yahoo.com> <52EF6194.5060305@niessen.ch> <8585EA2E-116E-45A6-877D-DC8D4460C965@yahoo.com> <52EF6690.3010509@niessen.ch> <CAEW%2BogbYWEGRfR7XWwvqSr%2B-M1yeH3DsZp1FG7hyWUKvk3eRbA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Sorry for not making it clear. Sure I restarted the machine completely=20 and set it at runtime as well. Both made no difference. Regards Ben On 03.02.2014 10:56, Sami Halabi wrote: > Hi, > Changing in/etc/sysctl.conf isnt enough unless you restart the machine. > Do in shell: > sysctl net.link.lagg.0.lacp.lacp_strict_mode=3D0 > > Sami > =D7=91=D7=AA=D7=90=D7=A8=D7=99=D7=9A 3 =D7=91=D7=A4=D7=91=D7=A8 2014 11= :51, "Ben" <mailinglists@niessen.ch> =D7=9B=D7=AA=D7=91: > >> Thank you for your detailed explanation. >> >> If I understand correctly the switch is probably not set up correctly, >> right? >> >> I will try to have it configured correctly first. >> >> Thanks a lot for your help! >> >> Regards >> Ben >> >> On 03.02.2014 10:45, Scott Long wrote: >> >>> Ok, please try the patch I emailed earlier. Since you=E2=80=99re not= seeing any >>> receive messages, it means that your switch isn=E2=80=99t generating = any LACP >>> heartbeats. The difference between FreeBSD 9.x and 10 is that in 9.x= , it >>> ran in =E2=80=9Coptimistic=E2=80=9D mode, meaning that it didn=E2=80=99= t rely on getting receive >>> messages from the switch, and only took a channel down if the link st= ate >>> went down. In strict mode, it looks for the receive messages and onl= y >>> transitions to a full operational state if it gets them. So while I = know >>> it=E2=80=99s easy to point at the problem being FreeBSD 10, seeing as= FreeBSD 9 >>> worked for you, please check to make sure that your switch is set up >>> correctly. >>> >>> I authored the original change that went into FreeBSD 10, and I tried= to >>> make it so that strict_mode=3D0 would keep everything working as it d= id in 9. >>> I guess that since you=E2=80=99re getting no receive messages from = the switch at >>> all that we need to disable strict mode on setup, not afterwards. Ap= ply >>> the patch and everything should work as it did in FreeBSD 9. >>> >>> Scott >>> >>> On Feb 3, 2014, at 2:29 AM, Ben <mailinglists@niessen.ch> wrote: >>> >>> Yes, via sysctl and /etc/sysctl.conf >>>> I waited now roughly 20 minutes without touching it but no differenc= e. >>>> >>>> No, I only see these transmit messages, no receive. >>>> >>>> Thanks >>>> Ben >>>> >>>> On 03.02.2014 10:25, Scott Long wrote: >>>> >>>>> Did you set it to 0 via the sysctl? You might need to wait for sev= eral >>>>> minutes if you set it after setting up the links. >>>>> >>>>> Also, the message that you=E2=80=99re seeing is from your machine t= ransmitting >>>>> PDU packets. Are you seeing any "lacpdu receive=E2=80=9D messages = on the console? >>>>> >>>>> Thanks, >>>>> Scott >>>>> >>>>> On Feb 3, 2014, at 2:10 AM, Ben <mailinglists@niessen.ch> wrote: >>>>> >>>>> 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=E2=80=99t control the strict mode globally= . My >>>>>>> apologies for this mess, I=E2=80=99ll make sure that it=E2=80=99s= fixed for FreeBSD 10.1. >>>>>>> If the sysctl doesn=E2=80=99t help then maybe consider compiling = a custom kernel >>>>>>> with it defaulted to 0. You=E2=80=99ll need to open /sys/net/iee= e802ad_lacp.c and >>>>>>> look for the function lacp_attach(). You=E2=80=99ll see the stri= ct_mode assign >>>>>>> underneath that. I=E2=80=99ll also send you a patch in a few min= utes. Until then, >>>>>>> try enabling net.link.lagg.lacp.debug=3D1 and see if you=E2=80=99= re receiving >>>>>>> heartbeat PDU=E2=80=99s 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 wor= k. >>>>>>>> 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 p= roblem. >>>>>>>> Maybe some incompatibility between FreeBSD + igb-driver + switch= (Juniper >>>>>>>> EX3300-48T). >>>>>>>> >>>>>>>> I will update you after setting the sysctl setting. It seems to = be >>>>>>>> "dynamic", I guess 0 reflects the index of LACP lagg devices. Ca= n I 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=E2=80=99re probably running into the consequences of r25368= 7. Check to >>>>>>>>> see the value of =E2=80=98sysctl net.link.lagg.0.lacp.lacp_stri= ct_mode=E2=80=99. >>>>>>>>> If it=E2=80=99s =E2=80=981=E2=80=99 then set it to 0. My origi= nal intention was for this to >>>>>>>>> default to 0, but apparently that didn=E2=80=99t happen. Howev= er, the fact that >>>>>>>>> strict mode doesn=E2=80=99t seem to work at all for you might h= int that your switch >>>>>>>>> either isn=E2=80=99t configured correctly for LACP, or doesn=E2= =80=99t actually 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 FreeB= SD >>>>>>>>>> 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=3Dkern/185967 >>>>>>>>>> >>>>>>>>>> It is set to low, but I would like somebody to have a look int= o it >>>>>>>>>> as it obviously has a great influence on our infrastructure. T= he 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" >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>> 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" >>>>>> >>>>> _______________________________________________ >>> 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,52ef67e5888828188920253! > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52EF68CD.8020501>