From owner-freebsd-net@FreeBSD.ORG Tue Jul 10 00:38:38 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30E8C106566B for ; Tue, 10 Jul 2012 00:38:38 +0000 (UTC) (envelope-from adarsh.joshi@qlogic.com) Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe004.messaging.microsoft.com [216.32.180.14]) by mx1.freebsd.org (Postfix) with ESMTP id C319D8FC08 for ; Tue, 10 Jul 2012 00:38:37 +0000 (UTC) Received: from mail36-va3-R.bigfish.com (10.7.14.247) by VA3EHSOBE007.bigfish.com (10.7.40.11) with Microsoft SMTP Server id 14.1.225.23; Tue, 10 Jul 2012 00:36:14 +0000 Received: from mail36-va3 (localhost [127.0.0.1]) by mail36-va3-R.bigfish.com (Postfix) with ESMTP id 0883E1C034F for ; Tue, 10 Jul 2012 00:36:14 +0000 (UTC) X-Forefront-Antispam-Report: CIP:198.70.193.64; KIP:(null); UIP:(null); IPV:NLI; H:avexcashub1.qlogic.com; RD:avexcashub2.qlogic.com; EFVD:NLI X-SpamScore: 2 X-BigFish: VPS2(zzc85fhzz1202hzz8275bh8275dh74efjz2fh2a8h668h839hd25hf0ah107ah) Received-SPF: pass (mail36-va3: domain of qlogic.com designates 198.70.193.64 as permitted sender) client-ip=198.70.193.64; envelope-from=adarsh.joshi@qlogic.com; helo=avexcashub1.qlogic.com ; 1.qlogic.com ; Received: from mail36-va3 (localhost.localdomain [127.0.0.1]) by mail36-va3 (MessageSwitch) id 1341880571285400_23475; Tue, 10 Jul 2012 00:36:11 +0000 (UTC) Received: from VA3EHSMHS037.bigfish.com (unknown [10.7.14.254]) by mail36-va3.bigfish.com (Postfix) with ESMTP id 42465100065 for ; Tue, 10 Jul 2012 00:36:11 +0000 (UTC) Received: from avexcashub1.qlogic.com (198.70.193.64) by VA3EHSMHS037.bigfish.com (10.7.99.47) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 10 Jul 2012 00:36:11 +0000 Received: from avexmb1.qlogic.org ([fe80::9545:3a4f:c131:467d]) by avexcashub2.qlogic.org ([::1]) with mapi; Mon, 9 Jul 2012 17:38:27 -0700 From: Adarsh Joshi To: "freebsd-net@freebsd.org" Date: Mon, 9 Jul 2012 17:38:24 -0700 Thread-Topic: lacp lagg port flags do not show correctly resulting in poor traffic distribution/performance Thread-Index: Ac1eMxngSmrEDoCLScCHz4wKHSkMkg== Message-ID: <5E4F49720D0BAD499EE1F01232234BA877435B2E28@AVEXMB1.qlogic.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-OriginatorOrg: qlogic.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: lacp lagg port flags do not show correctly resulting in poor traffic distribution/performance X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2012 00:38:38 -0000 Hi, I am trying to configure lacp lagg interfaces with 2 systems connected back= to back as follows: Ifconfig lagg0 create Ifconfig lagg0 laggproto lacp laggport ql0 laggport ql1 192.168.100.1 netma= sk 255.255.255.0 Sometimes, the lag interface comes up correctly but sometimes the laggport = flags do not show properly. Instead of 1c, = it shows values of 18. I have seen similar issues reported on various forum= s with no solution. Looking at the lagg driver code and reading the standard, I thought the lag= gport flags ( defined in if_lagg.h) are based on the LACP_STATE_BITS in fil= e ieee8023ad_lacp.h. But the following ifconfig -v output does not make any= sense to me. My concern is that when all the interfaces show flags as 1c, the traffic is= distributed across both the interfaces uniformly and I get aggregated thro= ughput. If not, the traffic flows only on 1 interface. Is this a bug? How do I solve this? Or am I doing something wrong? I am using Free-BSD 9.0 release. System 1: # ifconfig -v lagg0 lagg0: flags=3D8843 metric 0 mtu 15= 00 options=3D13b ether 00:0e:1e:08:05:20 inet 192.168.100.1 netmask 0xffffff00 broadcast 192.168.100.255 nd6 options=3D29 media: Ethernet autoselect status: active groups: lagg laggproto lacp lag id: [(8000,00-0E-1E-08-05-20,0213,0000,0000), (8000,00-0E-1E-04-2C-F0,0213,0000,0000)] laggport: ql1 flags=3D18 state=3D7D [(8000,00-0E-1E-08-05-20,0213,8000,000F), (FFFF,00-00-00-00-00-00,0000,FFFF,0000)] laggport: ql0 flags=3D1c state=3D3D [(8000,00-0E-1E-08-05-20,0213,8000,000E), (8000,00-0E-1E-04-2C-F0,0213,8000,000E)] System 2: # ifconfig -v lagg0 lagg0: flags=3D8843 metric 0 mtu 15= 00 options=3D13b ether 00:0e:1e:04:2c:f0 inet 192.168.100.2 netmask 0xffffff00 broadcast 192.168.100.255 nd6 options=3D29 media: Ethernet autoselect status: active groups: lagg laggproto lacp lag id: [(8000,00-0E-1E-04-2C-F0,0213,0000,0000), (FFFF,00-00-00-00-00-00,0000,0000,0000)] laggport: ql1 flags=3D1c state=3D7D [(8000,00-0E-1E-04-2C-F0,0213,8000,000F), (FFFF,00-00-00-00-00-00,0000,FFFF,0000)] laggport: ql0 flags=3D18 state=3D3D [(8000,00-0E-1E-04-2C-F0,0213,8000,000E), (8000,00-0E-1E-08-05-20,0213,8000,000E)] thanks Adarsh ________________________________ This message and any attached documents contain information from QLogic Cor= poration or its wholly-owned subsidiaries that may be confidential. If you = are not the intended recipient, you may not read, copy, distribute, or use = this information. If you have received this transmission in error, please n= otify the sender immediately by reply e-mail and then delete this message.