From owner-freebsd-bugs@freebsd.org Thu Sep 10 23:13:45 2015 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89C8BA01358 for ; Thu, 10 Sep 2015 23:13:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6EF401CD1 for ; Thu, 10 Sep 2015 23:13:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8ANDjVw015971 for ; Thu, 10 Sep 2015 23:13:45 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 203031] LACP problem with FreeBSD 10.2-RELEASE Date: Thu, 10 Sep 2015 23:13:45 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: gondim@bsdinfo.com.br X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Sep 2015 23:13:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203031 Bug ID: 203031 Summary: LACP problem with FreeBSD 10.2-RELEASE Product: Base System Version: 10.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: gondim@bsdinfo.com.br Hi All, We have a router configured with 2 LACP (lagg0 and lagg1): lagg0: flags=8843 metric 0 mtu 1500 options=403bb ether 00:1b:21:7b:ee:98 inet6 fe80::21b:21ff:fe7b:ee98%lagg0 prefixlen 64 scopeid 0x12 nd6 options=21 media: Ethernet autoselect status: active laggproto lacp lagghash l2,l3,l4 laggport: igb6 flags=1c laggport: igb7 flags=1c lagg1: flags=8843 metric 0 mtu 1500 options=403bb ether 00:1b:21:7b:ee:6c inet 189.xxx.xxx.34 netmask 0xfffffffc broadcast 189.113.78.35 inet6 fe80::21b:21ff:fe7b:ee6c%lagg1 prefixlen 64 scopeid 0xf inet6 2804:xxxx:0:8::2 prefixlen 64 nd6 options=21 media: Ethernet autoselect status: active laggproto lacp lagghash l2,l3,l4 laggport: igb4 flags=1c laggport: igb5 flags=1c When my Internet traffic is high at night, my BGP session in lagg1 is giving up and down 4 in 4 minutes. High load in system 40.x After upgraded to FreeBSD 10.2-RELEASE-p2, this problem started. Before we were using the FreeBSD 10.1-STABLE r281235 without any problem. The log have the following messages: /var/log/messages:Sep 9 19:21:43 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 19:21:44 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 19:27:01 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 19:27:01 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 19:29:13 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 19:29:14 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 19:46:10 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 19:46:11 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:01:02 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:01:03 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:02:08 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:02:09 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:03:54 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:03:57 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:07:05 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:07:06 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:20:49 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:20:50 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:25:39 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:25:40 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:28:55 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:28:56 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:31:39 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:31:39 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:33:29 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 20:33:30 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:03:38 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:03:38 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:09:39 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:09:39 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:20:51 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:20:52 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:25:24 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:25:25 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:36:22 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:36:23 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:39:26 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:39:27 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:47:40 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:47:40 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:52:19 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:52:19 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:53:01 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:53:01 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:58:53 rt01 kernel: igb5: Interface stopped DISTRIBUTING, possible flapping /var/log/messages:Sep 9 21:58:53 rt01 kernel: igb4: Interface stopped DISTRIBUTING, possible flapping Has there been any change in the LACP, during this period, which could be causing this problem? Today: I did downgrade the system to 10.1-STABLE r281235 and the problem stopped happening. Some change occurred between 10.1-STABLE r281235 and 10.2-RELEASE-p2 causing this problem in the system. -- You are receiving this mail because: You are the assignee for the bug.