Wish I had procured these with Enterprise Support.
I have two Truenas r20’s Community editions.
Even over IPMI I cannot create a bond with the two SFP+ fiber connections even if they are physically disconnected. What shows as available to bond are a Copper port and 1 SFP port.
I ran into something similar on TrueNAS systems, and it’s usually not a hardware limitation but how the interfaces are being recognized or configured.
First, make sure both SFP+ ports are actually detected correctly by the OS (check Network → Interfaces or via shell using ifconfig). Sometimes one port may not appear as “available” for bonding if it already has a configuration, VLAN, or IP assigned—so try removing any existing config from both SFP+ interfaces before creating the bond.
Also, TrueNAS (especially Community/CORE) can be picky with mixed interface types. Even though they’re both SFP+, they need to be:
Same speed (e.g., both 10Gb)
Same driver/module
Same MTU settings
If one port is negotiating differently or using a different driver, it may not show up as bondable alongside the other.
Another thing to check is whether LACP or lagg is being used correctly:
Try creating the bond from the shell using ifconfig lagg0 create and adding interfaces manually
Then assign it in the UI
Lastly, confirm firmware and NIC drivers are up to date—some SFP+ cards (especially certain Intel or Chelsio models) can behave oddly in TrueNAS Community builds.
If you can share the NIC model and ifconfig output, it’ll be easier to pinpoint exactly why one SFP+ port isn’t being offered for bonding.
ended up following Help with TrueNAS Scale - Link Aggregation Not Working - TrueNAS General - TrueNAS Community Forums and what solved it was “deleting” literally over ipmi. That reset the configurations despite them being…blank. That allowed me to make a bonded interface and it worked. Not the least bit obvious of a path.
