Link Aggregation name won’t work on new truenas scale installation

srv87

Cadet
Joined
Jun 13, 2023
Messages
7
Hi all,
I have used truenas core for the last couple of years, and I decided to switch to truenas scale as a part of my nas upgrade project. The installation went smoothly, but I can’t create a lagg with the network card I added. I can get to the menu for creating a lagg just fine, but whenever I enter a name, I get an error saying that it must be a bond with a unique number. I have tried many names that fit such criteria, like lagg0, LAGG0, lag0, etc, to no prevail. I also tried setting up a lagg from the serial console instead of the web ui, but that still didn’t work. Am I doing something wrong or is this a bug? I have attached images below of the two interface attempts. Thanks in advance for your help.
 

Attachments

  • IMG_1731.jpeg
    IMG_1731.jpeg
    388.9 KB · Views: 194
  • IMG_1735.jpeg
    IMG_1735.jpeg
    227.8 KB · Views: 190
  • IMG_1734.jpeg
    IMG_1734.jpeg
    265.7 KB · Views: 198

PhilD13

Patron
Joined
Sep 18, 2020
Messages
203
Use the name bond1 like the ? information popup for the name field says to do.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
I'm not sure how you posted two screenshots with the answer to your question, but failed to see it. As they both say, 'Link aggregation interface must start with "bond".' I use bond0, since computers start counting at 0, but any unique number would work.
 

srv87

Cadet
Joined
Jun 13, 2023
Messages
7
I am such a dummy. I thought that "bond" meant the protocol used, hence the attempts at "lagg0" and the like. Thank ya'll for clearing that up, and I apologize for the stupid question.
 

PhilD13

Patron
Joined
Sep 18, 2020
Messages
203
Did you actually get it to work after getting the name correct?
 

srv87

Cadet
Joined
Jun 13, 2023
Messages
7
Did you actually get it to work after getting the name correct?
It worked ok until I rebooted it. Then it lost the bond0 config and wouldn’t let me recreate it because apparently 192.168.1.0/24 was already in use by another interface. I was reading online that this could be caused by the loadbalence mode instead of LACP, so I will install a switch I have laying around that has LACP later and see if that resolves the issue.

Just wondering though, could the transmit hash policy have something to do with this? I’m not really sure how that works so I just left it on the default.
 

srv87

Cadet
Joined
Jun 13, 2023
Messages
7
So I just got my switch installed, and I am getting this error whenever I try to create a LACP lagg.

Code:
IntegrityError
(sqlite3.IntegrityError) UNIQUE constraint failed: network_lagginterfacemembers.lagg_physnic [SQL: INSERT INTO network_lagginterfacemembers (lagg_ordernum, lagg_physnic, lagg_interfacegroup_id) VALUES (?, ?, ?)] [parameters: (0, 'enp2s0f0', 10)] (Background on this error at: https://sqlalche.me/e/14/gkpj)


What is causing this? Thanks for the help in advance.
 

srv87

Cadet
Joined
Jun 13, 2023
Messages
7
So I got lacp to work, but it is very unreliable. I decided that I would just dedicate my LAN ports to specific services and split the connection that way. It's not as efficient as lacp, but it is much more reliable and accomplishes the same goal.
 
Top