From owner-freebsd-net@FreeBSD.ORG Fri Sep 22 23:36:19 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 42D0B16A40F for ; Fri, 22 Sep 2006 23:36:19 +0000 (UTC) (envelope-from bart@it-ss.be) Received: from piggy.solidweb.be (piggy.web.bru.it-ss.be [195.28.164.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 789EA43D49 for ; Fri, 22 Sep 2006 23:36:18 +0000 (GMT) (envelope-from bart@it-ss.be) Received: from mobilexp (162.160-201-80.adsl-dyn.isp.belgacom.be [80.201.160.162]) (authenticated bits=0) by piggy.solidweb.be (8.13.6/8.13.6) with ESMTP id k8MNaBIi031275; Sat, 23 Sep 2006 01:36:16 +0200 Message-ID: <000c01c6de9f$e5b79d60$de0b000a@mobilexp> From: "Bart Van Kerckhove - mobile" To: "Antony Mawer" References: <4513A5D1.4000604@mersin.edu.tr><4513AC94.8040609@mawer.org> <45142ED1.1000204@mersin.edu.tr><00ed01c6de77$8968f770$020b000a@bartwrkstxp> <45146FA2.8070208@mawer.org> Date: Sat, 23 Sep 2006 01:36:10 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="ISO-8859-9"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Scanned-By: MIMEDefang 2.45 on 195.28.164.224 Cc: 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:36:19 -0000 >>> 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 can NOT resist taking the bait here: HP has supported these standards for ages. In fact, the cisco-protocols were used to market their stuff as cisco-replacements. They ripped out functionality. IEEE Standards were already supported. Same for their SFP's. Vendor lock-in is a bitch, especially when that means you can't get stuff that was previously possible. (think cwdm gbics, etc) > > 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... I honestly don't know :-/ I'm very interested in the whole topic though, as we're an all-HP (as in procurve) shop. I do know that will only last 'till the next boxes we buy, HP has let us down the past few years. -Bart (sorry for the ranting)