Re: Unbalanced LACP link

2015-03-29 Thread Vitalii Duk
It worked fine, but today I've got one more error: Mar 29 01:03:08 router kernel: igb1: Interface stopped DISTRIBUTING, possible flapping Mar 29 01:08:02 router kernel: igb2: Interface stopped DISTRIBUTING, possible flapping Mar 29 01:08:02 router kernel: igb3: Interface stopped DISTRIBUTING, possi

Re: Unbalanced LACP link

2015-03-19 Thread hiren panchasara
On 03/17/15 at 12:34P, Adrian Chadd wrote: > On 17 March 2015 at 11:33, Jason Wolfe wrote: > > On Mon, Mar 16, 2015 at 2:43 AM, Hans Petter Selasky > > wrote: > >> On 03/16/15 10:37, Vitalii Duk wrote: > >>> > >>> I've changed use_flowid to 0 and it helped! But isn't it setting > >>> significant

Re: Unbalanced LACP link

2015-03-17 Thread Adrian Chadd
On 17 March 2015 at 11:33, Jason Wolfe wrote: > On Mon, Mar 16, 2015 at 2:43 AM, Hans Petter Selasky wrote: >> On 03/16/15 10:37, Vitalii Duk wrote: >>> >>> I've changed use_flowid to 0 and it helped! But isn't it setting >>> significant? In a description it says "Shift flowid bits to prevent >>>

Re: Unbalanced LACP link

2015-03-17 Thread Jason Wolfe
On Mon, Mar 16, 2015 at 2:43 AM, Hans Petter Selasky wrote: > On 03/16/15 10:37, Vitalii Duk wrote: >> >> I've changed use_flowid to 0 and it helped! But isn't it setting >> significant? In a description it says "Shift flowid bits to prevent >> multiqueue collisions". > > > Hi, > > Maybe your ethe

Re: Unbalanced LACP link

2015-03-16 Thread Adrian Chadd
if_igb and ixgbe iirc don't set the full flowid unless you're using RSS. They're just setting the CPU/MSIX id. -a ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-ne

Re: Unbalanced LACP link

2015-03-16 Thread Hans Petter Selasky
On 03/16/15 10:37, Vitalii Duk wrote: I've changed use_flowid to 0 and it helped! But isn't it setting significant? In a description it says "Shift flowid bits to prevent multiqueue collisions". Hi, Maybe your ethernet hardware is not properly setting the m_flowid ... --HPS __

Re: Unbalanced LACP link

2015-03-16 Thread Vitalii Duk
I've changed use_flowid to 0 and it helped! But isn't it setting significant? In a description it says "Shift flowid bits to prevent multiqueue collisions". On 16 March 2015 at 09:50, Konstantin Kulikov wrote: > Hello, Vitalii. > > Make sure following sysctl are set to zero: > sysctl net.link.la

Re: Unbalanced LACP link

2015-03-16 Thread Konstantin Kulikov
Hello, Vitalii. Make sure following sysctl are set to zero: sysctl net.link.lagg.default_use_flowid=0 sysctl net.link.lagg.0.use_flowid=0 sysctl net.link.lagg.1.use_flowid=0 Then adjust lagghash depending on your configuration. For example if you freebsd machine acts as router with single, defaul

Re: Unbalanced LACP link

2015-03-15 Thread hiren panchasara
On 03/15/15 at 12:38P, Vitalii Duk wrote: > Hello, guys. > I have a problem with my LACP link (2*1GbE) between FreeBSD 10 and D-Link > DGS-3610-26G switch. This link worked fine last two years on FreeBSD > 9.2-STABLE, but when I've updated my FreeBSD to 10.1-RELEASE traffic > started to go mostly t

Re: Unbalanced LACP link

2015-03-15 Thread Subscriber
Hello Vitalii, Sunday, March 15, 2015, 12:38:42 PM, you wrote: > Hello, guys. > I have a problem with my LACP link (2*1GbE) between FreeBSD 10 and D-Link > DGS-3610-26G switch. This link worked fine last two years on FreeBSD > 9.2-STABLE, but when I've updated my FreeBSD to 10.1-RELEASE traffic >

Unbalanced LACP link

2015-03-15 Thread Vitalii Duk
Hello, guys. I have a problem with my LACP link (2*1GbE) between FreeBSD 10 and D-Link DGS-3610-26G switch. This link worked fine last two years on FreeBSD 9.2-STABLE, but when I've updated my FreeBSD to 10.1-RELEASE traffic started to go mostly through one interface. lagg0 - input interface (no I