Date: Mon, 3 Feb 2014 10:30:00 GMT From: Benedikt Niessen <info@bhash.de> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/185967: Link Aggregation LAGG: LACP not working in 10.0 Message-ID: <201402031030.s13AU0hF012569@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/185967; it has been noted by GNATS. From: Benedikt Niessen <info@bhash.de> To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/185967: Link Aggregation LAGG: LACP not working in 10.0 Date: Mon, 03 Feb 2014 11:24:10 +0100 Scott Long helped to fix this issue for me: "The difference between FreeBSD 9.x and 10 is that in 9.x, it ran in=20 =93optimistic=94 mode, meaning that it didn=92t rely on getting receive=20 messages from the switch, and only took a channel down if the link state=20 went down. In strict mode, it looks for the receive messages and only=20 transitions to a full operational state if it gets them. So while I know=20 it=92s easy to point at the problem being FreeBSD 10, seeing as FreeBSD 9= =20 worked for you, please check to make sure that your switch is set up=20 correctly." Setting up my Juniper switch to "active" LACP mode it worked again: "The LACP mode can be active or passive. If the actor and partner are=20 both in passive mode, they do not exchange LACP packets, which results=20 in the aggregated Ethernet links not coming up. If either the actor or=20 partner is active, they do exchange LACP packets. By default, LACP is=20 turned off on aggregated Ethernet interfaces. If LACP is configured, it=20 is in passive mode by default. To initiate transmission of LACP packets=20 and response to LACP packets, you must configure LACP in active mode." If you have this issue please check if you have a similar setting. Best regards Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201402031030.s13AU0hF012569>