From owner-freebsd-net@FreeBSD.ORG Thu Aug 1 23:16:59 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 51F7AC2C for ; Thu, 1 Aug 2013 23:16:59 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2DD8E2081 for ; Thu, 1 Aug 2013 23:16:58 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r71NGie1098776 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Aug 2013 16:16:44 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r71NGii7098775; Thu, 1 Aug 2013 16:16:44 -0700 (PDT) (envelope-from jmg) Date: Thu, 1 Aug 2013 16:16:43 -0700 From: John-Mark Gurney To: Joe Moog Subject: Re: Intel 4-port ethernet adaptor link aggregation issue Message-ID: <20130801231643.GB94127@funkthat.com> Mail-Followup-To: Joe Moog , Ryan Stone , freebsd-net References: <2A0C085A-1AAF-42D7-867B-6CDD1143B4AC@ebureau.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2A0C085A-1AAF-42D7-867B-6CDD1143B4AC@ebureau.com> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Thu, 01 Aug 2013 16:16:44 -0700 (PDT) Cc: freebsd-net , Ryan Stone 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: Thu, 01 Aug 2013 23:16:59 -0000 Joe Moog wrote this message on Thu, Aug 01, 2013 at 17:14 -0500: > On Aug 1, 2013, at 4:27 PM, Joe Moog wrote: > > > On Aug 1, 2013, at 3:55 PM, Ryan Stone wrote: > > > >> Have you tried using only two ports, but both from the NIC? My suspicion would be that the problem is in the lagg's handling of more than 2 ports rather than the driver, especially given that it is the igb driver in all cases. > > > > Ryan: > > > > We have done this successfully with two ports on the NIC, on another hardware-identical host. That said, it is entirely possible that this is a shortcoming of lagg. > > > > Can you think of any sort of workaround? Our desired implementation really requires the inclusion of all 4 ports in the lagg. Failing this we're looking at the likelihood of 10G ethernet, but with that comes significant overhead, both cost and administration (before anybody tries to force the cost debate, remember that there are 10G router modules and 10G-capable distribution switches involved, never mind the cabling and SFPs -- it's not just a $600 10G card for the host). I'd like to defer that requirement as long as possible. 4 aggregated gig ports would serve us perfectly well for the near-term. > > > > Thanks > > > > Joe > > UPDATE: After additional testing, I'm beginning to suspect the igb driver. With our setup, ifconfig identifies all the ethernet ports as igb(0-5). I configured igb0 with a single static IP address (say, 192.168.1.10), and was able to connect to the host administratively. While connected, I enabled another port as a second standalone port, again with a unique address (say, 192.168.1.20), and was able to access the host via that interface as well. The problem arises when we attempt to similarly add a third interface to the mix -- and it doesn't seem to matter what interface(s) we use, or in what order we activate them. Always on the third interface, that third interface fails to respond despite showing "active" both in ifconfig and on the switch. Can you show an ifconfig -au from the host when it fails, and which was the third interface that you added? Above, you talk about adding ips in the same subnet to different interfaces, which with modern switchs can cause issues with which port to deliver packets, etc. Do you have any firewalling enabled on the host? > If there is anything else I could try that would be useful to help identify where the issue may reside, please let me know. > > Thanks > > Joe > > _______________________________________________ > 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" -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."