how to setup secondary nic (without GUI drop)?

[MisterE2002]

I have two systems. The new one is Scale. I want to do data transfer over a separate direct 10Gb cable between the two.
My old system has static 172.16.0.2. My Scale system must have static 172.16.0.3.

All systems have a own LAN NIC with DHCP MAC-reserved IP's: 192.168.1.x

I select the enp2s0 and enter all details.
Afterwards TN gives me two options. "Test and revert". It is also warning the main connection can drop.

And this is actually what happens. I press " test" and i can ping 172.16.0.3 at that point.
But my main connection drops so i can not access the GUI anymore. I assume i should have a "confirm" button. But have can i confirm something without GUI? After some time it reverts the changes.

I do not understand why it is resetting the main NIC. I just add a secondary interface.

 

[Patrick M. Hausen]

Seems like you are changing the IP address of your primary NIC ... 100% sure that is not the case?

As for the UI - the idea is to press "Test", then within 60 seconds (can be extended by entering a larger number) reconnect to the UI wich will present you with a "Save" option to make the changes permanent. If you don't do that, the system will revert your changes. This is the TrueNAS anti-lockout measure and I find it pretty well done.

Now as to why you are losing the connection to your primary address - possibly with the main connection set to DHCP it drops the lease and tries to acquire a new (or the same) one and you only temporarily lose connectivity. Increase the timeout and try again. After making sure you are not changing the wrong NIC. Also if a NIC toggles it might take up to 30 seconds until the connection to the switch is re-established due to STP. With a 60 second timeout for the entire procedure timing can get tight.

BTW: it's not advisable to have servers get their configuration via DHCP. You might want to set the primary interface to static, too. In the 192.168.1.0/24 range.

HTH,
Patrick

 

[MisterE2002]

Whoops, i think enp2s0 is the physical NIC and eno1 the virtual. So it makes sense.

But that said. eno1 and eno2 seems the 2 motherboard NIC's. I am missing the interface for my (old) Chelsio S310E-CR

 

[MisterE2002]

According to "lshw"

*-network
description: Ethernet interface
product: S310-CR 10GbE Single Port Adapter
vendor: Chelsio Communications Inc
physical id: 0
bus info: pci@0000:02:00.0
logical name: enp2s0
version: 00

 

[Patrick M. Hausen]

Then it's possibly the "general reset of evrything" that times out after 60 seconds. I'd change the eno1 to static configuration instead of a DHCP reservation. Don't forget to also set default gateway and nameserver statically if you want to do that. And increase the timeout

 

[MisterE2002]

So, not sure why Scale is resetting everything. Feels like a bug (or add at lease a "forced apply"). But this works fine. Although it will not be persistent.

ip addr add 172.16.0.3/24 dev enp2s0

Your suggestion about static IP's is not wrong. But the default is DHCP. And for my homelab i never run into issues with reserved mac-mappings. But if the default for scale is DHCP and for (all?) network changes it resets the entire network stack than the "confirm logic" seems broken to me? And now i should workaround-this with increasing the timeout.

Still wondering if i did something completely wrong and/or should create a bug report. The lack of the "without testing" irks me.