From owner-freebsd-performance@FreeBSD.ORG Mon Apr 19 07:07:41 2004 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB58016A4CE for ; Mon, 19 Apr 2004 07:07:41 -0700 (PDT) Received: from smtp.housing.ufl.edu (smtp.housing.ufl.edu [128.227.47.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CF0343D48 for ; Mon, 19 Apr 2004 07:07:41 -0700 (PDT) (envelope-from WillS@housing.ufl.edu) Received: (qmail 54656 invoked by uid 98); 19 Apr 2004 14:07:40 -0000 Received: from WillS@housing.ufl.edu by smtp.housing.ufl.edu by uid 82 with qmail-scanner-1.20 (spamassassin: 2.63. Clear:RC:1(128.227.47.18):. Processed in 0.015357 secs); 19 Apr 2004 14:07:40 -0000 X-Qmail-Scanner-Mail-From: WillS@housing.ufl.edu via smtp.housing.ufl.edu X-Qmail-Scanner: 1.20 (Clear:RC:1(128.227.47.18):. Processed in 0.015357 secs) Received: from bragi.housing.ufl.edu (128.227.47.18) by smtp.housing.ufl.edu with RC4-MD5 encrypted SMTP; 19 Apr 2004 14:07:40 -0000 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable x-mimeole: Produced By Microsoft Exchange V6.0.6249.0 Date: Mon, 19 Apr 2004 10:06:45 -0400 Message-ID: <0E972CEE334BFE4291CD07E056C76ED802E869F4@bragi.housing.ufl.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: etherchannel on 5.2.1 - possible? Thread-Index: AcQmFLevX2DKhHLoSlGPaGbiSKwNYAAAGlpw From: "Will Saxon" To: "J.D. Bronson" , X-Mailman-Approved-At: Mon, 19 Apr 2004 12:04:14 -0700 cc: freebsd-questions@freebsd.org Subject: RE: etherchannel on 5.2.1 - possible? X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 14:07:42 -0000 > -----Original Message----- > From: J.D. Bronson [mailto:jbronson@wixb.com] > Sent: Monday, April 19, 2004 9:46 AM > To: freebsd-performance@freebsd.org > Cc: freebsd-questions@freebsd.org > Subject: etherchannel on 5.2.1 - possible? >=20 >=20 > I am looking for performance. Not fail-over.. >=20 > Does anyone have this working with either > intel or broadcom nics? >=20 > Anyone have any good site that talks about what is needed to=20 > make this work > as well? - I do have a Cisco switch and it fully supports this. >=20 > I need a little advice on setting this up... I have used the ng_fec netgraph module with both broadcom 5703X and HP NC7170 nics (uses em driver).=20 This is how to set it up: First you have to have the ng_fec module loaded. Then, # ngctl mkpeer fec dummy fec # ngctl msg fec0: add_iface '"bge0"' # ngctl msg fec0: add_iface '"bge1"' Obviously replace bge with em or whatever other driver you are using. ng_fec supports up to 4 links. At this point, you will have a fec0 interface that you can=20 manipulate normally with ifconfig. I have noticed that sometimes I have to bring the interface up and down a couple of times to get it to start passing traffic. Whenever you 'ifconfig up' or assign an address to fec0 it resets the bundle.=20 One thing that is annoying is that ng_fec doesn't work with vlans. There is an ng_vlan module that was recently released, but ng_fec doesn't work with it because it isn't quite like other netgraph modules.=20 Almost all of my freebsd machines use vlans, so I am not making heavy=20 use of ng_fec. We aren't pushing enough data to make it really necessary = anyway. There is also ng_one2many which does implement failover and channel=20 bonding but not using the etherchannel technique. I think it uses round robin.=20 -Will