Date: Mon, 5 Aug 2013 14:46:01 -0500 From: Joe Moog <joemoog@ebureau.com> To: freebsd-net@freebsd.org Subject: Re: Intel 4-port ethernet adaptor link aggregation issue Message-ID: <7973384E-12E7-4C4A-B21D-526CC94F4194@ebureau.com> In-Reply-To: <mailman.67.1375444803.80048.freebsd-net@freebsd.org> References: <mailman.67.1375444803.80048.freebsd-net@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Fri, 02 Aug 2013 09:36:30 +0200 > From: Steve Read <steve.read@netasq.com> > To: freebsd-net@freebsd.org > Subject: Re: Intel 4-port ethernet adaptor link aggregation issue > Message-ID: <51FB617E.2090904@netasq.com> > Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed >=20 > On 01.08.2013 20:07, Joe Moog wrote: >> We have an iXsystems 1U server (E5) with an Intel 4-port ethernet NIC = installed, model I350-T4 (manufactured May of 2013). We're trying to = bind the 4 ports on this NIC together into a single lagg port, connected = LACP to a distribution switch (Cisco 4900-series). We are able to = successfully bind the 2 on-board ethernet ports to a single lagg, = however the NIC is not so cooperative. At first we thought we had a bad = NIC, but a replacement has not fixed the issue. We are thinking there = may be a driver limitation with these Intel ethernet NICs when = attempting to bind more than 2 ports to a lagg. >>=20 >> FreeBSD version: >> FreeBSD 9.1-PRERELEASE #0 r244125: Wed Dec 12 11:47:47 CST 2012 >>=20 >> rc.conf: >> # LINK AGGREGATION >> ifconfig_igb2=3D"UP" >> ifconfig_igb3=3D"UP" >> ifconfig_igb4=3D"UP" >> ifconfig_igb5=3D"UP" >> cloned_interfaces=3D"lagg0" >> ifconfig_lagg0=3D"laggproto lacp laggport igb2 laggport igb3 laggport = igb4 laggport igb5" >> ifconfig_lagg0=3D"inet 192.168.1.14 netmask 255.255.255.0" > Am I the only one who noticed that you replaced the value of=20 > $ifconfig_lagg0 that specifies the proto and the ports with one that=20= > specifies just the address? >=20 > Merge the two ifconfig_lagg0 lines into one, and it will work = infinitely=20 > better, or at least no worse. >=20 > ifconfig_lagg0=3D"laggproto lacp laggport igb2 laggport igb3 laggport = igb4 laggport igb5 inet 192.168.1.14 netmask 255.255.255.0" >=20 >=20 > -- Steve >=20 Steve: We have tried the configuration 3 different ways, all taken directly = from examples found in various BSD forums and wikis: 1) Specifying the IP address for the lagg port as seen above (which has = worked with other FreeBSD lagg configs for us) 2) Specifying the IP address in line with the "laggproto" config as = directed above 3) Using the line ipv4_addrs_lagg0=3D"192.168.1.14/24" in place of the = ifconfig_lagg0=3D"inet....." line above Each option yields the same results -- all will work with a 2-port lagg, = but none will enable a lagg with more than 2 ports (igb). FreeBSD = doesn't seem to care which one we use. Thanks Joe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7973384E-12E7-4C4A-B21D-526CC94F4194>