Require two 10Gb SFP+ PCI-e NICs (ideally eight in total) functioning on Windows 10, supporting link aggregation.
Require two 10Gb SFP+ PCI-e NICs (ideally eight in total) functioning on Windows 10, supporting link aggregation.
The issue lies in the secondary component, I can always purchase fiber or Twinax. The core problem is the NIC—it supports Windows 10 and handles link aggregation, and it works with non-branded Twinax or transceivers at 20Gbps (two 10Gbps links combined on Windows 10).
This approach won't function as intended. Link Aggregation processes separate client sessions and distributes them across several physical connections. It doesn't consolidate one session into multiple bandwidth tiers (like 2.25GB/s). In the best case, you'd observe around 1.123GB/s, with switching between interfaces each time a file transfer starts. It could also serve as a failover mechanism if desired.
LACP documentation on the official FS community site explains the protocol for link aggregation.
Consider avoiding LACP and opt for MPIO instead. MPIO merges the full bandwidth of your NICs without needing teaming or LACP.
For transfers exceeding 1.125GB/s, standard LACP won't suffice—it's not meant for that purpose. MPIO does require iSCSI, isn't it? I considered suggesting SMB3.0 Multichannel, but there are concerns.
We dive into the rabbit hole... So SMB3.0 Multichannel is available. Many people still use unmanaged switches between PCs and servers or NAS, plus a DHCP router on the same setup. Will there be issues if my main gateway—just the gateway—is connected to an integrated Intel LAN 1Gb using SMB3.0 Multichannel? I’m curious about internet connectivity too. The big question remains: can I use an IBM INTEL X520-DA2 10GB SFP+ with some random Twinax or transceiver cards on Windows 10? I haven’t found official support for Windows 10 drivers for IBM, and there’s no mention of a white list for those components. My main interest is that the original X520-DA2 has official Windows 10 support and works with all compatible transceivers. I’m struggling to locate a good price for the original model, while the newer one costs around 290$ (about 200$ more than the old one), which includes the NIC but not the same chipset as the IBM version.
SMB3.0 Multi-Channel works with two peer-to-peer links. The best setup is assigning each group of interfaces to separate networks (for example, 10.0.0.0/30 and 10.0.0.0.4/30). Windows handles the protocol independently on its own. You can initiate a file transfer and verify balanced traffic between both ports. On my systems, I've seen speeds reaching up to 1.61GB/s, though this was due to other issues. The main challenge comes when connecting across different platforms—SAMBA enables Multi-Channel for Linux, but I'm unsure about QNAP support. If it doesn't function, another approach might be MPIO, which typically relies on iSCSI.