From owner-freebsd-net@freebsd.org  Sat Feb  4 21:38:44 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id DAA57CD0398
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Sat,  4 Feb 2017 21:38:44 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9DEDF3DB;
 Sat,  4 Feb 2017 21:38:44 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1ca82W-0002IO-55; Sun, 05 Feb 2017 00:38:36 +0300
Date: Sun, 5 Feb 2017 00:38:36 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Sean Bruno <sbruno@freebsd.org>
Cc: freebsd-net@FreeBSD.org
Subject: Re: NFSROOT and lagg(4)
Message-ID: <20170204213836.GA5366@zxy.spb.ru>
References: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Feb 2017 21:38:45 -0000

On Sat, Feb 04, 2017 at 01:44:21PM -0700, Sean Bruno wrote:

> "what I want" is to pxe/netboot and then switch over to using a lagg(4)
> interface that includes the interface used in the pxe/netboot boot up.
> I suspect, I have to switch to MDROOT to do this, but I thought I'd ask
> if anyone is doing this type of configuration in their labs?
> 
> What seems to happen is that I lose the nfsroot when I reconfigure the
> lagg, and I no longer have access to reconfigure.
> 
> e.g. pxeboot from em0, then reconfigure networking to use em0/em1 in lagg0:
> 
> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> 
> options=5259b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO>
>         ether 00:30:18:c5:0a:a9
>         nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>         media: Ethernet autoselect (1000baseT <full-duplex>)
>         status: active
> em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> 
> options=5259b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO>
>         ether 00:30:18:c5:0a:a9
>         nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>         media: Ethernet autoselect (1000baseT <full-duplex>)
>         status: active
> lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> 
> options=5259b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO>
>         ether 00:30:18:c5:0a:a9
>         inet 192.168.100.53 netmask 0xffffff00 broadcast 192.168.100.255
>         nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>         media: Ethernet autoselect
>         status: active
>         groups: lagg
>         laggproto lacp lagghash l2,l3,l4
>         laggport: em0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
>         laggport: em1 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
> 

How to you plan to have em0 in LACP and independed from switch side?
Know to me, if switch port put to LACP you can't use it indepened.

Also, if port on switch side don't put to LACP mode -- you can't UP
laggo from FreeBSD side.