than LAGG.
Anyone who recommends 2 million clearly has no idea what they're doing.
BC
From: Joe Moog
To: freebsd-net
Sent: Wednesday, August 28, 2013 9:36 AM
Subject: Re: Intel 4-port ethernet adaptor link aggregation issue
All:
Thanks again to everyb
All:
Thanks again to everybody for the responses and suggestions to our 4-port lagg
issue. The solution (for those that may find the information of some value) was
to set the value for kern.ipc.nmbclusters to a higher value than we had
initially. Our previous tuning had this value set at 25600,
> 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.2090...@netasq.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
On Aug 1, 2013, at 6:16 PM, John-Mark Gurney wrote:
> 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
On 3 August 2013 06:31, Barney Cordoba wrote:
> You can create your own pipeline with some minor modifications. Why wait
> months
> for the guys who did it wrong to make changes?
Because I get paid now to ensure that this stuff gets done well, the
vendor gets engaged, the fixes get pushed into t
3, 2013 12:21 AM
Subject: Re: Intel 4-port ethernet adaptor link aggregation issue
On 2 August 2013 16:35, Barney Cordoba wrote:
> The stock igb driver binds to all cores, so with multiple igbs you have
> multiple
> nics binding to the same cores. I suppose that might create issues
On 2 August 2013 16:35, Barney Cordoba wrote:
> The stock igb driver binds to all cores, so with multiple igbs you have
> multiple
> nics binding to the same cores. I suppose that might create issues in a lagg
> setup.
> Try 1 queue and/or comment out the bind code.
>
I have thrashed the hell
Cc: Steve Read ; freebsd-net
Sent: Friday, August 2, 2013 5:41 PM
Subject: Re: Intel 4-port ethernet adaptor link aggregation issue
On several machines with large numbers of IGBx interfaces, I've found that
hw.igb.enable_msix=0 is necessary to ensure proper operation.
On Fri, Aug 2, 2013
On 2 August 2013 14:41, Zaphod Beeblebrox wrote:
> On several machines with large numbers of IGBx interfaces, I've found that
> hw.igb.enable_msix=0 is necessary to ensure proper operation.
ixgbe behaves much better now. As of like two days ago.
-adrian
On several machines with large numbers of IGBx interfaces, I've found that
hw.igb.enable_msix=0 is necessary to ensure proper operation.
On Fri, Aug 2, 2013 at 11:49 AM, Freddie Cash wrote:
> On Fri, Aug 2, 2013 at 12:36 AM, Steve Read wrote:
>
> > On 01.08.2013 20:07, Joe Moog wrote:
> >
> >>
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
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-ser
On 8/2/2013 2:44 AM, 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 than 2 ports rather than
the
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
Well, isn't there MAC address reprogramming and such going on when one
enables LAGG on an interface?
-adrian
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-un
-Original Message-
From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-...@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
On Aug 1, 2013, at 5:36 PM, Sean Bruno wrote:
>> 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 c
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 than
On Thu, 2013-08-01 at 17:14 -0500, 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 mo
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 th
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 h
On Thu, Aug 1, 2013 at 2:07 PM, 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
22 matches
Mail list logo
