From owner-freebsd-net@FreeBSD.ORG Fri Sep 22 23:21:18 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FAB516A40F for ; Fri, 22 Sep 2006 23:21:18 +0000 (UTC) (envelope-from fbsd-net@mawer.org) Received: from mail-ihug.icp-qv1-irony4.iinet.net.au (ihug-mail.icp-qv1-irony4.iinet.net.au [203.59.1.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 338E943D4C for ; Fri, 22 Sep 2006 23:21:16 +0000 (GMT) (envelope-from fbsd-net@mawer.org) Received: from 203-206-173-235.perm.iinet.net.au (HELO [127.0.0.1]) ([203.206.173.235]) by mail-ihug.icp-qv1-irony4.iinet.net.au with ESMTP; 23 Sep 2006 07:21:16 +0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.09,205,1157299200"; d="scan'208"; a="908085103:sNHT27649978" Message-ID: <45146FA2.8070208@mawer.org> Date: Sat, 23 Sep 2006 09:20:02 +1000 From: Antony Mawer User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Bart Van Kerckhove References: <4513A5D1.4000604@mersin.edu.tr> <4513AC94.8040609@mawer.org> <45142ED1.1000204@mersin.edu.tr> <00ed01c6de77$8968f770$020b000a@bartwrkstxp> In-Reply-To: <00ed01c6de77$8968f770$020b000a@bartwrkstxp> Content-Type: text/plain; charset=ISO-8859-9; format=flowed Content-Transfer-Encoding: 8bit Cc: =?ISO-8859-9?Q?=D6zkan_KIRIK?= , freebsd-net@freebsd.org Subject: Re: LACP 802.3ad and ng_fec ? 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: Fri, 22 Sep 2006 23:21:18 -0000 On 23/09/2006 4:47 AM, Bart Van Kerckhove wrote: > Özkan KIRIK wrote: >> Thanks for your reply, >> >> It seems that HP ProCurve 5400 series doesn't support fec trunking : >> >> hp(config)# trunk A3-a5 trk1 fec >> Invalid input: fec >> >> hp(config)# trunk A3-a5 trk1 ? >> trunk Do not use any protocol to create or maintain >> the trunk. >> lacp Use IEEE 802.1ad Link Aggregation protocol. >> >> hp(config)# >> >> Can ng_fec handshake with switch via "trunk" option instead of "fec" ? > According to HP docs, FEC should "work" with the 'trunk' setting. > It will loose all features tough, and just become a 'dumb' bonding-style > thing, with no redundancy and other features. Yes, I was reading some HP docs yesterday and they implied that they were removing FEC on newer switches in favour of using the IEEE standards-based methods of trunking. I wonder how dissimilar FEC and IEEE LACP are from one another? ie. how much of the code from ng_fec could be used to implement an ng_lacp... --Antony