Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 3 Apr 2012 13:17:50 +0300
From:      Beeblebrox <zaphod@berentweb.com>
To:        freebsd-net@freebsd.org
Subject:   Re: lagg problems on diskless client
Message-ID:  <CAPSTskueYtD%2B=zdwLFJkTvxHPXnpDvb4SQGHsb=RA8vq6iiewQ@mail.gmail.com>
In-Reply-To: <20120403074954.GA19241@server.vk2pj.dyndns.org>
References:  <CAPSTskviJ26uuoAhRVN7tLBj7AhAPVuQz5GSBCd%2BszGPF2VOfw@mail.gmail.com> <20120329072054.GA45082@server.vk2pj.dyndns.org> <CAPSTsktpDXHXDR1-MgWBZRTwXvHGrdZ=g5wH-=Lkd-JwMmJ95A@mail.gmail.com> <20120403074954.GA19241@server.vk2pj.dyndns.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 3, 2012 at 10:49 AM, Peter Jeremy <peterjeremy@acm.org> wrote:

> 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
>


> Please don't top post.
Wasn't aware I was doing that. This is better I hope?

> Assuming you're netbooting off re0, that looks correct.
YES, re0 is the BIOS detected NIC

> Are you sure you installed /etc/rc.d/lagg or an equivalent script?
I had not noticed the link to the script at the bottom - I placed script in
DC's private conf/<ip>/etc/rc.d then booted the DC. I got system freeze and
1 message:
ifconfig: interface re0 cannot change link address!
looking through the script I found the problem: lagg_tmp:=/mnt. My DC /root
is *ro* so I'll have to change it to another tmp. Considering that my /var
and /etc are md-mounted, using either seems out of the question. I also
have /tmp mounted as tmpfs. Can I mkdir -p /tmp/lagg and mount lagg_tmp
there or does it have to be an NFS shared location - what do you suggest?

Thanks.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPSTskueYtD%2B=zdwLFJkTvxHPXnpDvb4SQGHsb=RA8vq6iiewQ>