Date: Fri, 16 Mar 2012 10:45:08 +0100 From: Damien Fleuriot <ml@my.gd> To: Snoop <snoop@email.it> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: LAGG bug or misconfiguration??? Message-ID: <9D882CD7-5BD1-4A49-86AB-DD8A5B86D4EC@my.gd> In-Reply-To: <1331838392.1453.5.camel@blackfriar.inhio.eu> References: <1331838392.1453.5.camel@blackfriar.inhio.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry top posting from phone. Show your switch's port configurations. We're using VLAN tagging over lagg failover interfaces at work and I have al= ready tried the tests you described, to much better results. We're also running 8.2 so the only thing that seems to differ between us is t= he switch config, likely. On 15 Mar 2012, at 20:06, Snoop <snoop@email.it> 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. >=20 > 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. >=20 > The result was basically this (lagg0 members: bge0 primary, bge1 > secondary) >=20 > - 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). >=20 > 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. >=20 > So, below are the ipconfig outputs > - before to start the test > - when bge0 gets unplugged > - when bge0 gets plugged back in >=20 > I couldn't see anything odd. > __________________________________________________________________________= _________ > lagg0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu > 1500 >=20 > options=3D8009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTAT= E> > 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=3D0<> > laggport: bge0 flags=3D5<MASTER,ACTIVE> > __________________________________________________________________________= _________ > lagg0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu > 1500 >=20 > options=3D8009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTAT= E> > 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=3D4<ACTIVE> > laggport: bge0 flags=3D1<MASTER> > __________________________________________________________________________= _________ >=20 > lagg0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu > 1500 >=20 > options=3D8009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTAT= E> > 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=3D0<> > laggport: bge0 flags=3D5<MASTER,ACTIVE> > __________________________________________________________________________= ________ > Also nothing unusual on dmesg: >=20 > ....... > 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 > ....... >=20 > The following is the related configuration in rc.conf: >=20 > ....... > ifconfig_bge0=3D"up" > ifconfig_bge1=3D"up" > cloned_interfaces=3D"lagg0" > ifconfig_lagg0=3D"laggproto failover laggport bge0 laggport bge1 > xxx.xx.xx.224/24" > ifconfig_lagg0_alias_0=3D"inet xxx.xx.xx.225/32" > ifconfig_lagg0_alias_1=3D"inet xxx.xx.xx.226/32" > ifconfig_lagg0_alias_2=3D"inet xxx.xx.xx.227/32" > ifconfig_lagg0_alias_3=3D"inet 172.16.3.2/27" > ifconfig_lagg0_alias_4=3D"inet 172.16.3.3/27" > ifconfig_lagg0_alias_5=3D"inet 172.16.3.4/27" > ifconfig_lagg0_alias_6=3D"inet 172.16.3.5/27" > ifconfig_lagg0_alias_7=3D"inet 172.16.3.6/27" > ....... >=20 > 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 >=20 > 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. >=20 >=20 >=20 > -- > Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP a= utenticato? GRATIS solo con Email.it http://www.email.it/f >=20 > Sponsor: > Offerta speciale: a partire da soli Euro 18.90 puoi stampare le tue Foto s= u vera Tela Pittorica e creare Quadri fino a 80x50 cm! > Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=3D11453&d=3D15-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.or= g"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9D882CD7-5BD1-4A49-86AB-DD8A5B86D4EC>