How to optimally configure NIC bonding with ReadyDATA for failover and load balancing.
This configuration combines two or more Network Interface Cards (NIC) into a single logical interface, which provides fault tolerance and load balancing.
When configuring the ReadyDATA for NIC bonding, it is important to note that, in most cases, it is better to first configure the ReadyDATA and then the switch where it is connected. Failure to do so may result in lost connectivity. If you lose connectivity during this process, you can restore all the NIC settings by doing an OS re-install using the boot menu.
- Login into the ReadyDATA GUI and click on NETWORK
- Click on the “gear” icon on one of the NICs (eth0, eth1, eth2 or eth3) and select the additional NIC to complete the bond. 2 NIC with same port speed should be selected.
- Select active or passive mode for LACP (we recommend Passive for NETGEAR switches)
- Select the hash type for LACP for balancing the traffic across the NICs
The 3 options for the bonded adapter are
- Layer 2. The hash is based on the source and destination MAC addresses only.
- Layer 3. The hash is based on the source and destination IP addresses.
- Layer 4. The hash is based on the source and destination port numbers.
Because of how the hash algorithms calculates the channel load, and the sequential way the MAC addresses are arranged on the ReadyDATA, we recommend using L3 and L4 modes. L2 and the short separation of values in the MAC will not provide optimal load balancing.
- Configure the switch hash mode to match the ReadyDATA.
Example for NETGEAR managed switch:
Select “Src/Dest IP and TCP / UDP Port fields” as your hash mode.
Src/Dest IP is correspondent to Layer 3 and TCP / UDP is Layer 4 providing us a perfect match to the settings on the ReadyDATA. On other switches you may need to find an equivalent setting.
Note: If VLANs are involved in your configuration, make certain to have your VLAN participation and PVIDs correctly configured on the LAG on your switch
- Once correctly configured you will see the ReadyDATA with an aggr0, its Virtual NIC (vnic) and IP addresses.
Note: It may take a few moments to assign IP addresses on all VNICs and for the duration of that time, you will not have access to the ReadyDATA. Please be patient.
Once access is restored, the GUI should look like this:
Any additional VNICs that are created will be children of the initial NIC that was used to create the bond, and the MAC address of dependent VNICs will receive an almost identical MAC to said parent NIC, with the exception of the second transmission octet which will be incremented by 1.
Example: 00:0D:A2:C7:91:AF will create as dependent VNIC 00:0E:A2:C7:91:AF
If communication is lost with the ReadyDATA when these settings are applied, you will have to connect to one of the available NICs on the ReadyDATA and attempt connecting that way.
If the ReadyDATA cannot locate a DHCP server, or fails to receive an IP address, ReadyDATA will self-assign an Automatic Private IP Address (APIPA). This IP address is in the 169.254.x.x/16 subnet. The last two octets of the address derive from the MAC. You will need to convert the last two hexadecimal values to decimal to complete the IP address, and then configure the PC to that subnet to connect.