From owner-freebsd-questions@FreeBSD.ORG Thu Mar 15 19:47:52 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56A281065670 for ; Thu, 15 Mar 2012 19:47:52 +0000 (UTC) (envelope-from dweimer@dweimer.net) Received: from webmail.dweimer.net (adsl-70-129-195-213.dsl.ksc2mo.swbell.net [70.129.195.213]) by mx1.freebsd.org (Postfix) with ESMTP id D34F58FC0A for ; Thu, 15 Mar 2012 19:47:51 +0000 (UTC) Received: from www.dweimer.net (localhost [127.0.0.1]) by webmail.dweimer.net (8.14.5/8.14.5) with ESMTP id q2FJljET092996 for ; Thu, 15 Mar 2012 14:47:45 -0500 (CDT) (envelope-from dweimer@dweimer.net) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 15 Mar 2012 14:47:45 -0500 From: "Dean E. Weimer" To: Mail-Reply-To: In-Reply-To: <1331838392.1453.5.camel@blackfriar.inhio.eu> References: <1331838392.1453.5.camel@blackfriar.inhio.eu> Message-ID: X-Sender: dweimer@dweimer.net User-Agent: RoundCube Webmail/0.6 Subject: Re: LAGG bug or misconfiguration??? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dweimer@dweimer.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2012 19:47:52 -0000 On 15.03.2012 14:06, Snoop wrote: > Hi there, > a while after setting up my new server (with 8 jails in it) I've > decided > (after postponing several times) to properly check the functionality > of > the lagg and the result was very disappointing. > > The test I've done is very simple. > I've started copying a file from one site to another of my VPN > network > (from the server I've been testing the net to another node somewhere > else) and in the meantime I've been physically disconnecting the main > network cable to check the responsiveness of the lagg configuration. > Then I've plugged the cable back to check if the traffic would switch > back to the main NIC as it should. > > The result was basically this (lagg0 members: bge0 primary, bge1 > secondary) > > - when bge0 unplugged the traffic switched almost instantaneously to > bge1 > - when bge0 plugged back in, the network stopped working completely > with > the two NICs polling synchronously until I manually unplug bge1. Then > within 2-4 seconds traffic goes back on bge0 (I've been waiting for a > little more than a minute maximum to avoid all the active connections > on > the server to timeout). > > Now, I've repeated the same test about 10-15 times randomly waiting > for > different times between the unplug-replug procedure. The result was > always the same. > > So, below are the ipconfig outputs > - before to start the test > - when bge0 gets unplugged > - when bge0 gets plugged back in > > I couldn't see anything odd. > > ___________________________________________________________________________________ > lagg0: flags=8843 metric 0 > mtu > 1500 > > > options=8009b > ether 00:14:ee:00:8a:c0 > inet xxx.xx.xx.224 netmask 0xffffff00 broadcast xxx.xx.xx.255 > inet xxx.xx.xx.227 netmask 0xffffffff broadcast xxx.xx.xx.227 > inet xxx.xx.xx.225 netmask 0xffffffff broadcast xxx.xx.xx.225 > inet 172.16.3.2 netmask 0xffffffff broadcast 172.16.3.2 > inet 172.16.3.3 netmask 0xffffffff broadcast 172.16.3.3 > inet 172.16.3.4 netmask 0xffffffff broadcast 172.16.3.4 > inet 172.16.3.5 netmask 0xffffffff broadcast 172.16.3.5 > inet 172.16.3.6 netmask 0xffffffff broadcast 172.16.3.6 > inet xxx.xx.xx.226 netmask 0xffffffff broadcast xxx.xx.xx.226 > media: Ethernet autoselect > status: active > laggproto failover > laggport: bge1 flags=0<> > laggport: bge0 flags=5 > > ___________________________________________________________________________________ > lagg0: flags=8843 metric 0 > mtu > 1500 > > > options=8009b > ether 00:14:ee:00:8a:c0 > inet xxx.xx.xx.224 netmask 0xffffff00 broadcast xxx.xx.xx.255 > inet xxx.xx.xx.227 netmask 0xffffffff broadcast xxx.xx.xx.227 > inet xxx.xx.xx.225 netmask 0xffffffff broadcast xxx.xx.xx.225 > inet 172.16.3.2 netmask 0xffffffff broadcast 172.16.3.2 > inet 172.16.3.3 netmask 0xffffffff broadcast 172.16.3.3 > inet 172.16.3.4 netmask 0xffffffff broadcast 172.16.3.4 > inet 172.16.3.5 netmask 0xffffffff broadcast 172.16.3.5 > inet 172.16.3.6 netmask 0xffffffff broadcast 172.16.3.6 > inet xxx.xx.xx.226 netmask 0xffffffff broadcast xxx.xx.xx.226 > media: Ethernet autoselect > status: active > laggproto failover > laggport: bge1 flags=4 > laggport: bge0 flags=1 > > ___________________________________________________________________________________ > > lagg0: flags=8843 metric 0 > mtu > 1500 > > > options=8009b > ether 00:14:ee:00:8a:c0 > inet xxx.xx.xx.224 netmask 0xffffff00 broadcast xxx.xx.xx.255 > inet xxx.xx.xx.227 netmask 0xffffffff broadcast xxx.xx.xx.227 > inet xxx.xx.xx.225 netmask 0xffffffff broadcast xxx.xx.xx.225 > inet 172.16.3.2 netmask 0xffffffff broadcast 172.16.3.2 > inet 172.16.3.3 netmask 0xffffffff broadcast 172.16.3.3 > inet 172.16.3.4 netmask 0xffffffff broadcast 172.16.3.4 > inet 172.16.3.5 netmask 0xffffffff broadcast 172.16.3.5 > inet 172.16.3.6 netmask 0xffffffff broadcast 172.16.3.6 > inet xxx.xx.xx.226 netmask 0xffffffff broadcast xxx.xx.xx.226 > media: Ethernet autoselect > status: active > laggproto failover > laggport: bge1 flags=0<> > laggport: bge0 flags=5 > > __________________________________________________________________________________ > Also nothing unusual on dmesg: > > ....... > bge0: link state changed to DOWN > bge0: link state changed to UP > bge1: link state changed to DOWN > bge1: link state changed to UP > bge0: link state changed to DOWN > bge0: link state changed to UP > bge1: link state changed to DOWN > bge1: link state changed to UP > bge0: link state changed to DOWN > bge0: link state changed to UP > bge1: link state changed to DOWN > bge1: link state changed to UP > ....... > > The following is the related configuration in rc.conf: > > ....... > ifconfig_bge0="up" > ifconfig_bge1="up" > cloned_interfaces="lagg0" > ifconfig_lagg0="laggproto failover laggport bge0 laggport bge1 > xxx.xx.xx.224/24" > ifconfig_lagg0_alias_0="inet xxx.xx.xx.225/32" > ifconfig_lagg0_alias_1="inet xxx.xx.xx.226/32" > ifconfig_lagg0_alias_2="inet xxx.xx.xx.227/32" > ifconfig_lagg0_alias_3="inet 172.16.3.2/27" > ifconfig_lagg0_alias_4="inet 172.16.3.3/27" > ifconfig_lagg0_alias_5="inet 172.16.3.4/27" > ifconfig_lagg0_alias_6="inet 172.16.3.5/27" > ifconfig_lagg0_alias_7="inet 172.16.3.6/27" > ....... > > The system is an IBM xSeries 336 type 8837 > kern.version: FreeBSD 8.2-RELEASE-p3 #0: Tue Sep 27 18:45:57 UTC 2011 > > Just for the record, I've done the test from the host > (xxx.xx.xx.224/24) > not from any of the jail in place. > Any idea or similar issue around? Am I missing something? > Thanks. > > > > -- > Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e > SMTP autenticato? GRATIS solo con Email.it http://www.email.it/f > > Sponsor: > Offerta speciale: a partire da soli Euro 18.90 puoi stampare le tue > Foto su vera Tela Pittorica e creare Quadri fino a 80x50 cm! > Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=11453&d=15-3 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" Is this system connected to a switch with management capability? If so how is the switch configured for the ports? -- Thanks, Dean E. Weimer dweimer@dweimer.net http://www.dweimer.net/