With just two nics, setting up a lagg interface is not for the faint hearted.
It would be nice to be able to do this from the console.
This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
LAGG network at console
-
Ecnerwal
- NewUser
- Posts: 4
- Joined: 24 Jul 2013 23:50
- Status: Offline
Re: LAGG network at console
Trying this on my test system now. Odds seem high that it will flip out. Console access would be handy, but then, so would simply a good FAQ - it's not all that clear how to proceed - the lagg0 device comes up as a new interface (Opt2 - had LAN and Opt1 before that for the NICs) Do I set it to the same address as the current LAN, or a new address, or what? Am I supposed to somehow free the current LAN interface? Looks like perhaps I tell the LAN that it's on lagg0 before I reboot? Deleting opt1 and opt2? Clear as mud, clear as mud.
Without walking a quarter mile to the console, I don't recall if shell is a console option - assuming it is, the freeBSD man page might be a way into bare-metal console lagg configuration: http://www.freebsd.org/cgi/man.cgi?quer ... ormat=html
This NAS4Free page is fairly unenlightening (descriptive, but not much use for what to actually DO with a LAGG one is crafting from interfaces one of which is currently the LAN...)
http://wiki.nas4free.org/doku.php?id=do ... 5B%5D=lagg
Well, odds are I'm about to blow up my test system again... Had LAN on bge0, Opt1 on bge1, made lagg0 from bge0 and bge1 (became Opt2), set LAN to lagg0, deleted opt1 and opt2 - my best bet in light of lack of a clear guide. We'll see if it's there when I reboot it and configure the switch for LACP
<time passes...>
Nope.... Clear as mud, indeed. <more time passes...> wait, it's up now. That was an unreasonably long reboot, but might be correct. Seems to be working. I'll try to massage this note into an actual FAQ, though I expect I'll just post it over in the newbie forum as I'm not sure I can actually get something into the FAQ/doc Wiki without some sort of blessing I probably don't have.
Without walking a quarter mile to the console, I don't recall if shell is a console option - assuming it is, the freeBSD man page might be a way into bare-metal console lagg configuration: http://www.freebsd.org/cgi/man.cgi?quer ... ormat=html
This NAS4Free page is fairly unenlightening (descriptive, but not much use for what to actually DO with a LAGG one is crafting from interfaces one of which is currently the LAN...)
http://wiki.nas4free.org/doku.php?id=do ... 5B%5D=lagg
Well, odds are I'm about to blow up my test system again... Had LAN on bge0, Opt1 on bge1, made lagg0 from bge0 and bge1 (became Opt2), set LAN to lagg0, deleted opt1 and opt2 - my best bet in light of lack of a clear guide. We'll see if it's there when I reboot it and configure the switch for LACP
<time passes...>
Nope.... Clear as mud, indeed. <more time passes...> wait, it's up now. That was an unreasonably long reboot, but might be correct. Seems to be working. I'll try to massage this note into an actual FAQ, though I expect I'll just post it over in the newbie forum as I'm not sure I can actually get something into the FAQ/doc Wiki without some sort of blessing I probably don't have.