From owner-freebsd-net@FreeBSD.ORG Mon Aug 5 19:46:04 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C3C73E22 for ; Mon, 5 Aug 2013 19:46:04 +0000 (UTC) (envelope-from joemoog@ebureau.com) Received: from internet06.ebureau.com (internet06.ebureau.com [65.127.24.25]) by mx1.freebsd.org (Postfix) with ESMTP id 8C608235F for ; Mon, 5 Aug 2013 19:46:04 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by internet06.ebureau.com (Postfix) with ESMTP id E467037C69D5 for ; Mon, 5 Aug 2013 14:46:03 -0500 (CDT) X-Virus-Scanned: amavisd-new at ebureau.com Received: from internet06.ebureau.com ([127.0.0.1]) by localhost (internet06.ebureau.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p2BeeGJIrglc for ; Mon, 5 Aug 2013 14:46:02 -0500 (CDT) Received: from nail.office.ebureau.com (nail.office.ebureau.com [10.10.20.23]) by internet06.ebureau.com (Postfix) with ESMTPSA id D63F237C69BD for ; Mon, 5 Aug 2013 14:46:02 -0500 (CDT) From: Joe Moog Message-Id: <7973384E-12E7-4C4A-B21D-526CC94F4194@ebureau.com> Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1786.1\)) Subject: Re: Intel 4-port ethernet adaptor link aggregation issue Date: Mon, 5 Aug 2013 14:46:01 -0500 References: To: freebsd-net@freebsd.org In-Reply-To: X-Mailer: Apple Mail (2.1786.1) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 19:46:04 -0000 > Date: Fri, 02 Aug 2013 09:36:30 +0200 > From: Steve Read > 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