TrueNAS Scale forgets about bond Interface

tmkrvs

Dabbler
Joined
Jan 3, 2024
Messages
12
Hi there,

I'm facing a problem with TrueNAS Scale Cobia and interface bonding configuration

It's running on a HPE Proliant DL380 Gen9 with a 2 port Intel 10Gbit NIC (bnx2x). Everything runs just smooth (currently still building it) - but if I configure a bond with eno49 and eno50 and reboot afterwards, the bond just disappears and the configured IP address is set on eno49. Resetting the configuration of this interface doesn't work, as it throws a Python error. Only thing I can do then is, restoring factory defaults.

Anyone ever encountered a similar issue?

BR
Tim
 

tmkrvs

Dabbler
Joined
Jan 3, 2024
Messages
12
Ok, I removed the single 1Gbit/s connection eno2 from the system, resetted everything and build a new bond over eno2, eno49 and eno50. And voila, it's working. Don't know why TrueNAS seems to have an issue with a bonded interface in combination with a non-bonded interface on a totally different NIC.
 

tmkrvs

Dabbler
Joined
Jan 3, 2024
Messages
12
And now it just happened again ... The interface vlan813 is missing and the configuration is now attached to eno49 ... I don't get it ...

Screen Shot 2024-01-09 at 15.24.41 PM.png
 

tmkrvs

Dabbler
Joined
Jan 3, 2024
Messages
12
And again - no visible traces in dmesg for any reconfiguration of bond0 - does nobody has ever encountered such a problem?
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,776
I am using an LACP interface named bond0 and I haven't. Anything you want me to share for comparison?
 

tmkrvs

Dabbler
Joined
Jan 3, 2024
Messages
12
Thanks for replying - what are the underlying NICs? Which type / chip?
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,776
Code:
13:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
    DeviceName: pciPassthru1
    Subsystem: Super Micro Computer Inc I350 Gigabit Network Connection
    Physical Slot: 224
    Flags: bus master, fast devsel, latency 64, IRQ 16
    Memory at fda20000 (32-bit, non-prefetchable) [size=128K]
    I/O ports at 3020 [disabled]
    Memory at fda44000 (32-bit, non-prefetchable) [size=16K]
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
    Capabilities: [70] MSI-X: Enable+ Count=10 Masked-
    Capabilities: [a0] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Device Serial Number 3c-ec-ef-ff-ff-46-f8-d0
    Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
    Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
    Capabilities: [1a0] Transaction Processing Hints
    Capabilities: [1c0] Latency Tolerance Reporting
    Capabilities: [1d0] Access Control Services
    Kernel driver in use: igb
    Kernel modules: igb

13:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
    Subsystem: Super Micro Computer Inc I350 Gigabit Network Connection
    Physical Slot: 224
    Flags: bus master, fast devsel, latency 64, IRQ 17
    Memory at fda00000 (32-bit, non-prefetchable) [size=128K]
    I/O ports at 3000 [disabled] 
    Memory at fda40000 (32-bit, non-prefetchable) [size=16K]
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
    Capabilities: [70] MSI-X: Enable+ Count=10 Masked-
    Capabilities: [a0] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Device Serial Number 3c-ec-ef-ff-ff-46-f8-d0
    Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
    Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
    Capabilities: [1a0] Transaction Processing Hints
    Capabilities: [1d0] Access Control Services
    Kernel driver in use: igb
    Kernel modules: igb
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,776
Now the same problem hit me, too. I had configured all of the networking in bluefin, then upgraded to cobia recently. Now the first time I edited my network settings everything is b0rked after a reboot.

The topology should be vlan2 --> bond0 --> ens224f0,ens224f1

After reboot vlan2 was gone and the IP address configuration assigned to ens224f0 instead.
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,776
 
Top