Date: Tue, 3 Apr 2012 17:49:54 +1000 From: Peter Jeremy <peterjeremy@acm.org> To: Beeblebrox <zaphod@berentweb.com> Cc: freebsd-net@freebsd.org Subject: Re: lagg problems on diskless client Message-ID: <20120403074954.GA19241@server.vk2pj.dyndns.org> In-Reply-To: <CAPSTsktpDXHXDR1-MgWBZRTwXvHGrdZ=g5wH-=Lkd-JwMmJ95A@mail.gmail.com> References: <CAPSTskviJ26uuoAhRVN7tLBj7AhAPVuQz5GSBCd%2BszGPF2VOfw@mail.gmail.com> <20120329072054.GA45082@server.vk2pj.dyndns.org> <CAPSTsktpDXHXDR1-MgWBZRTwXvHGrdZ=g5wH-=Lkd-JwMmJ95A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Please don't top post. On 2012-Apr-02 12:25:06 +0300, Beeblebrox <zaphod@berentweb.com> wrote: >I had looked into failover with wireless and tried it before posting, but >got nowhere. Wired/wireless on a diskfull system should be trivial. >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" Assuming you're netbooting off re0, that looks correct. >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 This is wrong - there should't be an IP address on re0 at this point. >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. lagg0 shows only one laggport so there's no failover. Are you sure you installed /etc/rc.d/lagg or an equivalent script? >PS- I mistakenly double-posted: >http://docs.freebsd.org/cgi/getmsg.cgi?fetch=39210+0+current/freebsd-net I replied to this one because it had a meaningful subject. -- Peter Jeremy [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk96q6IACgkQ/opHv/APuIdRwACgsuzqqwfUKxIiruUpKN9ZAHOs 4owAn2MscXvMvMNUxJy3ydl7VQsjtPkN =u2Wf -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120403074954.GA19241>