Date: Mon, 2 Apr 2012 12:25:06 +0300 From: Beeblebrox <zaphod@berentweb.com> To: freebsd-net@freebsd.org Subject: Re: lagg problems on diskless client Message-ID: <CAPSTsktpDXHXDR1-MgWBZRTwXvHGrdZ=g5wH-=Lkd-JwMmJ95A@mail.gmail.com> In-Reply-To: <20120329072054.GA45082@server.vk2pj.dyndns.org> References: <CAPSTskviJ26uuoAhRVN7tLBj7AhAPVuQz5GSBCd%2BszGPF2VOfw@mail.gmail.com> <20120329072054.GA45082@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Peter. I had looked into failover with wireless and tried it before posting, but got nowhere. I delayed posting an answer because I needed to do more fiddleing; and I made some headwy, but still problems: 1. With below setup in diskless client's rc.conf, the client is able to boot and gets to login screen: ifconfig_re1="up ether 00:30:67:91:6c:c2" cloned_interfaces="lagg0" ifconfig_lagg0="up laggproto failover laggport re1 192.168.2.2 netmask 255.255.255.0" 2. ifconfig at that point shows all good: same mac addr and lagg0 active. re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE> ether 00:30:67:91:6c:c2 inet 192.168.2.2 netmask 0xffffff00 broadcast 192.168.2.255 media: Ethernet autoselect (100baseTX <half-duplex>) status: active re1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE> ether 00:30:67:91:6c:c2 media: Ethernet autoselect (1000baseT <full-duplex>) status: active lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE> ether 00:30:67:91:6c:c2 media: Ethernet autoselect status: active laggproto failover laggport: re1 flags=5<MASTER,ACTIVE> Now if I go and unplug NIC10/100 on diskless client and "list folder", the client will freeze - so failover does not switch. After some time passes, client informs that NFS server 192.168.2.1 is not responding. PS- I mistakenly double-posted: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=39210+0+current/freebsd-net *************************************************************** On Thu, Mar 29, 2012 at 10:20 AM, Peter Jeremy <peterjeremy@acm.org> wrote: > On 2012-Mar-28 13:16:06 +0300, "Raif S. Berent" <rsb@berentweb.com> wrote: > >I have some problems implementing lagg(4) on dual NIC's on the diskless > >client side. It may be because my switch is a cheap, un-managed Gbit > switch > >or hopefully some other reason. I would like to either get lagg working > >properly or find an alternative method of solving the problem. > > Whilst I haven't specifically done this, I have done diskless booting > on a wired NIC and then switched to a wired/wifi lagg. Have a look at > http://www.bugs.au.freebsd.org/dokuwiki/doku.php/laggdiskless > > >I concede that under this structure lagg's loadbalance or LACP are > probably > >not going to work. > > FEC & LACP require support at both ends and so won't work. loadbalance > & roundrobin should work but aren't really appropriate unless your > interfaces are identical. > > >In general, as soon as lagg is brought up, NIC pool no longer responds to > >pings and gives an "I'm busy now" message. > > Yes. Once you create the lagg, the interfaces comprising it will no > longer work standalone and you can't atomically migrate the IP address > from re0 to lagg0 - hence the script linked from the above page. > > -- > Peter Jeremy >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPSTsktpDXHXDR1-MgWBZRTwXvHGrdZ=g5wH-=Lkd-JwMmJ95A>