[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967

Graham Perrin  changed:

   What|Removed |Added

   Keywords||patch

--- Comment #20 from Graham Perrin  ---
Keyword: 

patch
or  patch-ready

– in lieu of summary line prefix: 

[patch]

* bulk change for the keyword
* summary lines may be edited manually (not in bulk). 

Keyword descriptions and search interface: 



-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967

Eitan Adler  changed:

   What|Removed |Added

 Status|In Progress |Open

--- Comment #19 from Eitan Adler  ---
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to
double check to see if this bug ought to be closed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967

Palle Girgensohn  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2082
   ||35

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967

--- Comment #18 from Jeroen van Heugten vanheug...@gmail.com ---
In our case the problem was due to a bug in TSO (tcp segment offloading). This
has been resolved in 10.1. You can easily exclude issues TSO by turning it
temporary off for your interfaces (ifconfig ix# -tso).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org

Re: [Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0

[schaman]

Try to change juniper settings to /periodic slow;/



--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Bug-185967-lagg-patch-Link-Aggregation-LAGG-LACP-not-working-in-10-0-tp5952851p5983448.html
Sent from the freebsd-net mailing list archive at Nabble.com.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org

[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967

Joseph Mingrone j...@ftfl.ca changed:

   What|Removed |Added

 CC||j...@ftfl.ca

--- Comment #16 from Joseph Mingrone j...@ftfl.ca ---
I just upgraded our storage server from 9.3 to 10.1 and we're now seeing this
problem as well.

This is what we had in /etc/rc.conf:

cloned_interfaces=lagg0
ifconfig_lagg0=laggproto lacp laggport em0 laggport em1 laggport em2 laggport
em3 192.168.0.102/24

I'll also attach a screenshot of ifconfig -a.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org

[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967

--- Comment #17 from Joseph Mingrone j...@ftfl.ca ---
Screenshots:
https://picasaweb.google.com/104346539473598376650/LaggProblems?authuser=0authkey=Gv1sRgCKjvr5q29ouZLgfeat=directlink

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org

[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967

i...@gcecad-service.nl changed:

   What|Removed |Added

 CC||i...@gcecad-service.nl

--- Comment #15 from i...@gcecad-service.nl ---
Is the patch supposed to be included with 10.1-BETA3?

There does not seem to be a sysctl entry called
net.link.lagg.lacp.lacp_strict_mode

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org

[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967

Jeroen van Heugten vanheug...@gmail.com changed:

   What|Removed |Added

 CC||vanheug...@gmail.com

--- Comment #12 from Jeroen van Heugten vanheug...@gmail.com ---
Created attachment 147795
  -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147795action=edit
Output of ifconfig -a

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org

[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967

--- Comment #13 from Jeroen van Heugten vanheug...@gmail.com ---
We are facing the same problem, running FreeBSD 10.0-p9, connected with LACP to
two Juniper EX4550 switches (virtual-chassis/stacked). In our case the Junipers
are already in active mode, but we still have issues with the connection. We
are experiencing lots of outages (every few mins).

dmesg shows (on -multiple- FreeBSD servers:

ix1: Interface stopped DISTRIBUTING, possible flapping
ix1: Interface stopped DISTRIBUTING, possible flapping
ix1: Interface stopped DISTRIBUTING, possible flapping

Juniper configuration:

ae21 {
description serverX (xe-0/0/17 en xe-1/0/17);
aggregated-ether-options {
link-speed 10g;
lacp {
active;
periodic fast;
}
}
unit 0 {
family ethernet-switching {
port-mode access;
vlan {
members S1_SERVERS;
}
}
}
}


- attached output of ifconfig -a
- attached output of /etc/rc.conf

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org

[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967

--- Comment #14 from Jeroen van Heugten vanheug...@gmail.com ---
Created attachment 147796
  -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147796action=edit
LACP settings in /etc/rc.conf

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org

[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967

--- Comment #11 from oliv...@cochard.me ---
(In reply to kvedulv from comment #10)
 Hi Oliver,
 
 (In reply to olivier from comment #8)
  The patch didn't solve Lagg regression between 9.2 and 10-stable (r267244).
  
  My configuration only use one lagg member (the second will be added later):
 
 _Maybe_ #179926 is your Bug and you could try the patch over there...
 (Although that problem seems to have existed at least in 9.1)

I believe it's not a regression in my case:
On FreeBSD 9.2, the lagg-lacp mode by not implementing a 'strict' mode was
equivalent to a 'static+optionnal LACP' mode.
The behavior of lagg-lacp on 9.2 seems:
- If no LACP detected, allow a minimum of 1 lagg member to transmit.
The behavior on 10 seems:
- If no LACP detected, don't allow any of the lagg member to transmit (even
with strict_mode disabled)
And in my case: I didn't have a LACP device in front of my FreeBSD.
Then I simply need to use a 'static' mode (like loadbalanced or roundrobin).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org

[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967

kved...@kvedulv.de changed:

   What|Removed |Added

 CC||kved...@kvedulv.de

--- Comment #9 from kved...@kvedulv.de ---
This patch did solve my occasional problems with FreeBSD 10-STABLE and a
Netgear GS110TP, so somebody should at least have a look at it (or scottl could
just commit it).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org

[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967

--- Comment #10 from kved...@kvedulv.de ---
Hi Oliver,

(In reply to olivier from comment #8)
 The patch didn't solve Lagg regression between 9.2 and 10-stable (r267244).
 
 My configuration only use one lagg member (the second will be added later):

_Maybe_ #179926 is your Bug and you could try the patch over there... (Although
that problem seems to have existed at least in 9.1)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org

[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0

[bz-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967

oliv...@cochard.me changed:

   What|Removed |Added

 CC||oliv...@cochard.me

--- Comment #8 from oliv...@cochard.me ---
The patch didn't solve Lagg regression between 9.2 and 10-stable (r267244).

My configuration only use one lagg member (the second will be added later):

ifconfig_em0=up
cloned_interfaces=lagg0
ifconfig_lagg0=laggproto lacp laggport em0 SYNCDHCP
ifconfig_lagg0_ipv6=inet6 accept_rtadv

And it's works great on 9.2:

[root@R1]~# uname -a
FreeBSD R1 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255918M: Sat Oct 26 22:41:39
CEST 2013
r...@orange.bsdrp.net:/usr/obj/BSDRP.amd64/usr/local/BSDRP/BSDRP/FreeBSD/src/sys/amd64
 amd64
[root@R1]~# ifconfig lagg0
lagg0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM
ether aa:aa:00:01:01:01
inet6 fe80::a8aa:ff:fe01:101%lagg0 prefixlen 64 scopeid 0x8
inet 10.0.12.1 netmask 0xff00 broadcast 10.0.12.255
inet6 2001:db8:12:0:a8aa:ff:fe01:101 prefixlen 64 autoconf
nd6 options=23PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL
media: Ethernet autoselect
status: active
laggproto lacp lagghash l2,l3,l4
laggport: em0 flags=1cACTIVE,COLLECTING,DISTRIBUTING
[root@R1]~# uname -a
FreeBSD R1 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255918M: Sat Oct 26 22:41:39
CEST 2013
r...@orange.bsdrp.net:/usr/obj/BSDRP.amd64/usr/local/BSDRP/BSDRP/FreeBSD/src/sys/amd64
 amd64

But once upgraded to 10-stable AND DISABLING the strict mode, it didn't works
anymore:

[root@R1]~# uname -a
FreeBSD R1 10.0-STABLE FreeBSD 10.0-STABLE #0 r267244M: Mon Jun  9 03:57:44
CEST 2014
r...@orange.bsdrp.net:/usr/obj/BSDRP.amd64/usr/local/BSDRP/BSDRP/FreeBSD/src/sys/amd64
 amd64

[root@R1]~# echo net.link.lagg.0.lacp.lacp_strict_mode=0  /etc/sysctl.conf

[root@R1]~# ifconfig lagg0
lagg0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM
ether aa:aa:00:01:01:01
inet6 fe80::a8aa:ff:fe01:101%lagg0 prefixlen 64 scopeid 0x7
inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255
nd6 options=23PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL
media: Ethernet autoselect
status: active
laggproto lacp lagghash l2,l3,l4
laggport: em0 flags=0
[root@R1]~# sysctl net.link.lagg.0.
net.link.lagg.0.use_flowid: 1
net.link.lagg.0.flowid_shift: 16
net.link.lagg.0.count: 1
net.link.lagg.0.active: 0
net.link.lagg.0.flapping: 0
net.link.lagg.0.lacp.lacp_strict_mode: 0
net.link.lagg.0.lacp.debug.rx_test: 0
net.link.lagg.0.lacp.debug.tx_test: 0

In debug mode, I've got this output:
lacp_select_tx_port: no active aggregator

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org