From owner-freebsd-net@FreeBSD.ORG Thu Aug 1 23:01:44 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 8AA678B0 for ; Thu, 1 Aug 2013 23:01:44 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by mx1.freebsd.org (Postfix) with ESMTP id 4CAB62FD4 for ; Thu, 1 Aug 2013 23:01:43 +0000 (UTC) Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 01 Aug 2013 16:01:36 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.89,797,1367996400"; d="scan'208";a="340381039" Received: from orsmsx106.amr.corp.intel.com ([10.22.225.133]) by azsmga001.ch.intel.com with ESMTP; 01 Aug 2013 16:01:26 -0700 Received: from orsmsx102.amr.corp.intel.com ([169.254.1.106]) by ORSMSX106.amr.corp.intel.com ([169.254.5.238]) with mapi id 14.03.0123.003; Thu, 1 Aug 2013 16:01:25 -0700 From: "Pieper, Jeffrey E" To: Jack Vogel , Joe Moog Subject: RE: Intel 4-port ethernet adaptor link aggregation issue Thread-Topic: Intel 4-port ethernet adaptor link aggregation issue Thread-Index: AQHOjwlrQsYLWr38Sk2IgxeYf9cL9pmA9pVg Date: Thu, 1 Aug 2013 23:01:23 +0000 Message-ID: <2A35EA60C3C77D438915767F458D65687DE5C1AF@ORSMSX102.amr.corp.intel.com> References: <2A0C085A-1AAF-42D7-867B-6CDD1143B4AC@ebureau.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.139] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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:01:44 -0000 -----Original Message----- From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] = On Behalf Of Jack Vogel Sent: Thursday, August 01, 2013 3:49 PM To: Joe Moog Cc: freebsd-net; Ryan Stone Subject: Re: Intel 4-port ethernet adaptor link aggregation issue On Thu, Aug 1, 2013 at 3:14 PM, Joe Moog wrote: > 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 tha= n > 2 ports rather than the driver, especially given that it is the igb drive= r > 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 SF= Ps > -- 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 thi= rd > interface, that third interface fails to respond despite showing "active" > both in ifconfig and on the switch. > > If there is anything else I could try that would be useful to help > identify where the issue may reside, please let me know. > > >Well, you're using a PRERELEASE of 9.1, leads me to wonder how old the ig= b >driver is also. First step would be to try all this >on more recent bits... I'd go for HEAD or at least 9.2 BETA as a start. We >don't use or test lagg within Intel, but we've tested the >quad port adapter and not seen an issue with a third port not working. > >Good luck, > >Jack I can ping to 4 different subnets using all 4 ports simultaneously with an = I350-T4 using 9.1-RELEASE and igb-2.3.9 (in-kernel driver) connected to a C= isco 4948, so the issue is definitely not with the igb driver. Jeff _______________________________________________ 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"