NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
iSCSI and Network Bonding
Good Evening Everyone,
Just wanted to reach out to the guru's here as I am stumpped at the moment. I have a ReadyNas 314 connected to a TP-LInk TL-SG108E switch. This switch supports the provision of Link Aggregation Group (LAG) (thats all is says on the box).
Additionally I have an iSCSI connection from a Windows 10 PC using the Microsoft iSCSI initiator.
I would like to add that I have no Apps running on the Readynas 314 and currently at Firmware 6.10.3
Now current config (no bonding configured);
- I have Eth0 plugged into a standard switched port on the SG108E switch (port 3)
- Eth 1 is not connected
- Successful ping to the ReadNas 314
- RN314 is configured for iSCSI and is successfully connected to the Microsoft iSCSI initiator and iSCSI drive is visable
- RN314 is visable within the WIndows 10 Network Neighbourhood
Proposed Future Config (bonding configured);
- I have read that if you are connecting your ReadyNAS to a managed switch that only supports static LAG, then NETGEAR recommends that you use teaming mode XOR. (https://kb.netgear.com/25509/ReadyNAS-What-Bonding-Teaming-Mode-Should-I-Use)
- With that in mind I proceed to configure Static LAG on the SG108E switch assigning port 3 & 4 to the LAG Group
- On the ReadyNas 314 I create a new bond with Eth0 and Eth1 using XOR (Layer 2) as the teaming mode
- The ping from my WIndows 10 PC to the ReadyNas drops out for a few seconds and returns
- Problem 1: The Microsoft iSCSI initiator cannot connect back to the ReadyNas iSCSI target (connecting...)
- Problem 2: The ReadyNas is no longer visiable within the Network Neighbourhood
I have tried XOR hash type 2, 2+3 and 3+4 without success.
Reaching out to the community for advice on how best I should proceed and get the network bonding working.
Cheers & thanks in advance,
John
Good News Everyone,
I have figured it out !! (I am pretty excited!). The issue seemed to be with the iSCSI setup on the ReadyNas. I went into the iSCSI settings and within the properties of the group the 'Dedicated Link' was set to 'Any'. Changing this to "bond0:x.x.x.x" completely solved the problem.
In answer to your question acwdc, my SMB settings were as follows; Enable SMB (checked), Legacy Windows Discovery (checked), SMB3 Transport Encryption (Configured Globally - Enabled).
Hope this helps someone else out there. I really appreciate everyones help with this - a big thank you !!
Kind of wondered what would be the difference between ANY and the dedicated bond ID. Anyhow, it world now :)
Cheers,John
13 Replies
Replies have been turned off for this discussion
It'd be useful to know what you want to accomplish with bonding. You won't get any performance boost if you only have one client PC running, not matter what teaming mode you use.
Are you connecting to the NAS using it's hostname? If so, perhaps try a test using the IP address instead.
Good Morning StephenB,
Thank you so much for responding to my query. I do appriciaite your time. The reasons for wanting to implement bondingn on the ReadyNas is to provide some sort of fault tollerance in addition to load sharing.
I have several other computers on the same network all connecting the ReadyNas using their own iSCSI and the network neighbourhood and was attempting to just add a little extra load balancing.
I am connecting to the ReadyNas via the iSCSI initiator via IP address.
Cheers and thanks for the advice
You could try round-robin and see if that behaves any differently.
Are you seeing the issue only with iSCSI, or are you also unable to access Network Shares?
or use standard IEEE 802.3ad. I think the tplinks use source/dest by mac address as a hash algorithm.
AC
acwdc wrote:
or use standard IEEE 802.3ad.
No, that won't work. The TL-SG108E only supports static LAGs.
If you are using jumbo frames on the NAS or in the PC, then try turning them off.
think the tplinks use source/dest by mac address as a hash algorithm.In general, the decision about what packets to put on what link is made by the sender, and is not negotiated. So the switch often does use a different algorithm than the NAS. The hash shouldn't affect connectivity, but it can affect performance.
Good morning everyone, thanks so much for the replies. I think what I may be better off doing is getting another switch that fully supports IEEE 802.3ad.
When enabling Round Robin do I still need to set up a LAG group on the switch or is there any switch configuration that is required at all?
Cheers,John
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
