Date: Mon, 03 Feb 2014 09:40:30 +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: <52EF55FE.8030901@niessen.ch> In-Reply-To: <1C608452-6F29-486D-BC0F-CCC7853665C7@yahoo.com> References: <52EF50A7.1050205@niessen.ch> <1C608452-6F29-486D-BC0F-CCC7853665C7@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 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. Can 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’re probably running into the consequences of r253687. Check to see the value of ‘sysctl net.link.lagg.0.lacp.lacp_strict_mode’. If it’s ‘1’ then set it to 0. My original intention was for this to default to 0, but apparently that didn’t happen. However, the fact that strict mode doesn’t seem to work at all for you might hint that your switch either isn’t configured correctly for LACP, or doesn’t 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 FreeBSD 10.0-RELEASE: http://tinypic.com/view.php?pic=28jvgpw&s=5#.Uu9PXT1dVPM >> >> A PR is currently open: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/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! > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52EF55FE.8030901>