Networking and TrueNAS scale

[tre4B]

I set my box up initially in my room next to my computer. All seemed to work well and I felt it was time to go into its place in the understairs cabinet.

I moved it down there and I am having real problems getting the thing to connect to the network. Upstairs I had this working using an aggregated link. After struggling for a while downstairs I chose option 5 to reset configuration and it briefly connected using one of the two network ports. On reboot though it again comes up and does not work.

The interface gets an IP address on the correct network. If I go into the shell I can ping 127.0.0.1 but not the router of the subnet that this address sits on. Similarly it is not accessible from anywhere else. This stays the same if I try adding the default route in option 2, or Name servers or anything else! I have tried different ports in the switch and different cables but I just cannot get consistant attachement to the network out of this box.

What am I doing wrong? Where it is currently I only have access to the box via the menu so anything I need to change has to be there. Ideally I am looking to get back to an LACP bound adapter pair...

 

[danb35]

What am I doing wrong?

Not following the forum rules and giving your hardware information, for one thing. Minimally the motherboard (and NICs, if separate), as well as the switch you're using for downstairs, would need to be specified.

 

[tre4B]

Not following the forum rules and giving your hardware information, for one thing. Minimally the motherboard (and NICs, if separate), as well as the switch you're using for downstairs, would need to be specified.

Sorry :-( I'm still trying to decide if TrueNas can replace the QTS that was on this box or whether I should just bite the bullet and live with the QNAP OS and have got lazy and not added to my footer. What little I see of TrueNAS has kept me knocking away at it, and pre-resetting everything I was getting excited.

I am running this on a QNAP NAS, it is a 453BE, and the downstairs switch is a Zyxel GS1900 24E. The QNAP has 16GB Ram, with 4 8TB spinning disks, it also has 2 500GB SSDs and is booted from a pair of small (128GB) USB 3 attached SSD Drives (because the internal SSDs just simply would not allow the QNAP to boot to TrueNAS. Currently I just reset to defaults so it is out of the box, even with the default password while I get the network running.

It may be the LCAP support on the Xycel that is causing this issue, though it did work perfectly with the QTS setup previously. I just managed to get access to the UI by removing all the LAG groups from the Switch. This then becomes confusing though as I am now seeing two independent connections to the same subnet on the TrueNAS.

I have no DHCP for IPV6 on the network, and IPV6 is not supported on the internet router (or rather is disabled on the router).

 

[NugentS]

Why are you trying to use LACP - what is your reason given its a home server?
Also, if I recall correctly, you are doing it wrong. Start by turning off one of the interfaces. Then look up how to do LACP on TrueNAS - I think a bridge is required (emphasis on I think)

 

[danb35]

Then look up how to do LACP on TrueNAS - I think a bridge is required (emphasis on I think)

No, but it's kind of like one. You'd deconfigure every physical NIC involved in the group, then create a new interface (name has to be bondn, which the system doesn't tell you until you enter a different name) of type LACP, attaching the physical interfaces in question to that. You then configure bondn with the IP/netmask/etc.

 

[tre4B]

I think I may have solved it. I was creating the interface using bond1 as the name. Should have thought more C and tried to start from 0. I just tried creating bond0 and it added both interfaces fine and is running perfectly. Will give this a bit of a test and see if it is stable...