Really really excited about TrueNAS Scale! Even so that I installed nearly two identical nodes. I want to join in to test, debug, document and develop.
Hardware specs (2 nodes)
- Supermicro X10SDV-6C+-TLN4F
- Supermicro SuperChassis 721TQ-250B2
- 32 GB RAM (registered ecc). Planning to double that.
- 4x 4TB HDD (6x Toshiba N300 and 2x HGST Deskstar NAS)
- Samsung PM981 256GB (L2ARC)
- Intel Optane 900P PCI-e 280GB (ZIL/SLOG)
- Samsung Evo 250 GB (mirrored boot drives)
- Two bonded 10 GbE (link aggregation LACP)
Bug report
Both nodes are configured identically with TrueNAS Scale (latest available version). Both available 10Gb ethernet ports are bonded together as LACP.
On each node the Mac address for the bonded interface are identical to each other and therefore my DHCP server (pfSense) servers only one fixed IP address to both nodes. That doesn't work as expected.
I suspect that the algorithm for generating the Mac address is not correct.
I expect for each node an unique Mac address so that the DHCP service serves an unique fixed IP address for each dedicated node. Normally - at least what I was used to until now - one of the interfaces within the bond serves the mac address for the bond.
Is there a workaround available for now?
Hardware specs (2 nodes)
- Supermicro X10SDV-6C+-TLN4F
- Supermicro SuperChassis 721TQ-250B2
- 32 GB RAM (registered ecc). Planning to double that.
- 4x 4TB HDD (6x Toshiba N300 and 2x HGST Deskstar NAS)
- Samsung PM981 256GB (L2ARC)
- Intel Optane 900P PCI-e 280GB (ZIL/SLOG)
- Samsung Evo 250 GB (mirrored boot drives)
- Two bonded 10 GbE (link aggregation LACP)
Bug report
Both nodes are configured identically with TrueNAS Scale (latest available version). Both available 10Gb ethernet ports are bonded together as LACP.
On each node the Mac address for the bonded interface are identical to each other and therefore my DHCP server (pfSense) servers only one fixed IP address to both nodes. That doesn't work as expected.
I suspect that the algorithm for generating the Mac address is not correct.
I expect for each node an unique Mac address so that the DHCP service serves an unique fixed IP address for each dedicated node. Normally - at least what I was used to until now - one of the interfaces within the bond serves the mac address for the bond.
Is there a workaround available for now?