ReadyNas link aggregation, bonding, teaming

Maybe it can be faster, but I tried on my Pro6, with one old Seagate 500GB HDD. (My Ultra6 is the "production" NAS now,with the real data, because the Pro6 have crashing issues under OS6.x, and 2 month ago I lost all of my data, 16TB)

But I will test under Ultra6 (6x3TB WD Red) too, think it will slower.

Write speed: There is a lot of settings, and I have no idea about them. Jumbo frame, etc...

I can use this modes ( https://www.intel.com/content/www/us/en/support/network-and-i-o/ethernet-products/000005667.html ):

• Switch Fault Tolerance (SFT)
  Uses two adapters connected to two switches and provides a fault tolerant network connection if the first adapter, its cabling, or the switch fails. Only two adapters can be assigned to an SFT team.
• Adapter Fault Tolerance (AFT)
  Allows mixed models and mixed connection speeds as long as there is at least one Intel® PRO server adapter in the team. A 'failed' primary adapter passes its MAC and Layer 3 address to the failover (secondary) adapter. All adapters in the team should be connected to the same hub or switch with Spanning Tree (STP) set to Off.

• Adaptive Load Balancing (ALB)
  Offers increased network bandwidth by allowing transmission over two to eight ports to multiple destination addresses, and incorporates AFT. Only the primary adapter receives incoming traffic. Broadcasts/multicasts and non-routed protocols are only transmitted via the primary adapter in the team. The Intel® ANS software load balances transmissions, based on Destination Address, and can be used with any switch. Simultaneous transmission only occurs at multiple addresses. This mode can be connected to any switch.

• Receive Load Balancing (RLB)
  • Offers increased network bandwidth by allowing reception over two to eight ports from multiple addresses.
  • Can only be used in conjunction with ALB.
  • RLB is enabled by default when an ALB team is configured unless you are using Microsoft Hyper-V*.
  • RLB mode is not compatible with Microsoft Hyper-V*. Use Virtual Machine Load Balancing mode if you want to balance both transmit and receive traffic.
  • Only the adapters connected at the fastest speed are used to load balance incoming TCP/IP traffic. Regardless of speed, the primary adapter receives all other RX traffic.
  • Can be used with any switch. Any failover increases network latency until ARPs are resent. Simultaneous reception only occurs from multiple clients.
• Virtual Machine Load Balancing (VMLB)

  VMLB teaming mode was created specifically for use with Microsoft Hyper-V*. VMLB provides transmit and receive traffic load balancing across Virtual Machines bound to the team interface. The LMLB team also provides fault tolerance in the event of switch port, cable, or adapter failure. This teaming type works with any switch.

  The driver analyzes the transmit and receive load on each member adapter and balances the traffic across member ports. In a VMLB team, each Virtual Machine is associated with one team member port for its TX and RX traffic.
  
  For example: If you have three virtual machines and two member ports, and if VM1 has twice as much traffic as the combination of VM2 and VM3, then VM1 is assigned to team member port 1, and VM2 and VM3 share team member port 2.

  If only one virtual NIC is bound to the team, or if Hyper-V is removed, then the VMLB team acts like an AFT team.

• Static Link Aggregation (SLA):

  • Equivalent to EtherChannel or Link Aggregation.
  • Must be used with an 802.3ad, FEC/GEC, or Link Aggregation capable switch.

     

• IEEE 802.3ad DYNAMIC mode
  • Requires 802.3ad DYNAMIC capable switches.
  • Active aggregators in software determine team membership between the switch and the ANS software (or between switches).
  • There is a maximum of two aggregators per server and you must choose either maximum bandwidth or maximum adapters.

• Both 802.3ad modes include adapter fault tolerance and load balancing capabilities. However in DYNAMIC mode load balancing is within only one team at a time.