From owner-freebsd-net@FreeBSD.ORG Fri Aug 2 15:49:56 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9518B5F0 for ; Fri, 2 Aug 2013 15:49:56 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qa0-x22c.google.com (mail-qa0-x22c.google.com [IPv6:2607:f8b0:400d:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 573352D71 for ; Fri, 2 Aug 2013 15:49:56 +0000 (UTC) Received: by mail-qa0-f44.google.com with SMTP id hu16so396046qab.17 for ; Fri, 02 Aug 2013 08:49:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=uoYNCIKW6Gigr9F+dH4AeU7FDsKzavl/QjXYpgJeYbw=; b=plJSpQD2zkNj/BvZRqnlqeZMAqi/hK3sLhFdoIMibTfWARDTe9/1PujDA2MN/Vka9f GKKGMStrzEzcAzNcjNsT166Idr6I2d7fSZtcUXCSqQAoiaU3roznAtZaer+v3A5ZzCHS 2stjyRP1svqJS4pIrdpfFfpK1tiq+Mad9XWfgj1zPwlkuJe69o+yvBjF282YVM7mgGb9 N/eu57sSxJjYL5d0WDTh+sK7UWy1P9e3MDts63Tl0WTTZlq0g+u3/NfRs9wkJvJhR2f/ m9Nf/BSwQkilx5cL1IrxK+6OwEFiXk/6SBiJGWS5pudplFOi8pCxjTox/BxOVoXWWrc5 AlBQ== MIME-Version: 1.0 X-Received: by 10.224.160.130 with SMTP id n2mr12165536qax.68.1375458595475; Fri, 02 Aug 2013 08:49:55 -0700 (PDT) Received: by 10.49.49.135 with HTTP; Fri, 2 Aug 2013 08:49:55 -0700 (PDT) In-Reply-To: <51FB617E.2090904@netasq.com> References: <51FB617E.2090904@netasq.com> Date: Fri, 2 Aug 2013 08:49:55 -0700 Message-ID: Subject: Re: Intel 4-port ethernet adaptor link aggregation issue From: Freddie Cash To: Steve Read Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-net 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: Fri, 02 Aug 2013 15:49:56 -0000 On Fri, Aug 2, 2013 at 12:36 AM, Steve Read wrote: > 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. >> >> FreeBSD version: >> FreeBSD 9.1-PRERELEASE #0 r244125: Wed Dec 12 11:47:47 CST 2012 >> >> rc.conf: >> # LINK AGGREGATION >> ifconfig_igb2="UP" >> ifconfig_igb3="UP" >> ifconfig_igb4="UP" >> ifconfig_igb5="UP" >> cloned_interfaces="lagg0" >> ifconfig_lagg0="laggproto lacp laggport igb2 laggport igb3 laggport igb4 >> laggport igb5" >> ifconfig_lagg0="inet 192.168.1.14 netmask 255.255.255.0" >> > > Am I the only one who noticed that you replaced the value of > $ifconfig_lagg0 that specifies the proto and the ports with one that > specifies just the address? > Good catch! > Merge the two ifconfig_lagg0 lines into one, and it will work infinitely > better, or at least no worse. > > ifconfig_lagg0="laggproto lacp laggport igb2 laggport igb3 laggport igb4 > laggport igb5 inet 192.168.1.14 netmask 255.255.255.0" > > Or, if you want to keep them split into two parts (initialise lagg0, then add IP): create_args_lagg0="laggproto lacp laggport igb2 laggport igb3 laggport igb4 laggport igb5" ifconfig_lagg0="inet 192.168.1.14 netmask 255.255.255.0" create_args_* are run first, then ifconfig_* are run. I like this setup, as it separates "create and initialise" from "configure" for cloned/virtual interfaces like vlans, laggs, etc. -- Freddie Cash fjwcash@gmail.com