NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Retired_Member
May 08, 2019GS516T problem 802.3ad LAG/LACP - only one direction full bandwidth
Hi all In reference to this post: https://community.netgear.com/t5/Managed-Switches/XS728T-problem-802-3ad-LAG-LACP-only-one-direction-full/m-p/1079353/highlight/true#M1786 I have the same probl...
schumaku
May 09, 2019Guru - Experienced User
Retired_Member wrote:
Cisco supports those hashing configurations:
Cisco does offer Mac and MAC/IP up to the Cisco 550X Series Stackable Managed Switches class - that's the counterpart to Netgear's top-of-the-line stackable switches - and does leave any further details open, too:
Retired_Member wrote:
I have the same problem with the GS516T that i‘ve buyed today.
That would be an almost 20 year old switch - so a GS516TP probably.
What is the exact use and test case in your deployment?
schumaku
May 09, 2019Guru - Experienced User
Can't speak for the GS516TP (no such device here) - when pushing data from multiple systems [so different source MAC] to an IP address (QTS NAS here) served by a teo or more LACP LAGs operated on various similar switches like the mentioned XS728T/XS748T (v6.5.1.36) or an MS510TX (v6.7.0.37) we find the upload traffic flowing over multiple members of the port channel - so the impression is there is (at least) a src-dst-mac hash used.
- Retired_MemberMay 09, 2019
As far as i understand; in case you want to be able to configure the hashing algorythms for LACP (regardless if L2 or L3) you have to go by the M-Series. Check: Usermanual Page 200 - there is a screenshot of the configuration options available.
The GS Series seems to be for amateurs only when it comes to LACP - senselessly castrated from software perspective, because the hardware is fast as hell.
This are L2 options:
- src-mac — Source MAC addresses
- dst-mac — Destination MAC addresses
- src-dst-mac — Source and destination MAC addresses
This are L3 options:
- src-ip — Source IP addresses
- dst-ip — Destination IP addresses
- src-dst-ip — Source and destination IP addresses (Default)
This are L4 options:
- src-port — Source Layer 4 port
- dst-port — Destination Layer 4 port
- src-dst-port — Source and destination Layer 4 port
On the Cisco boxes you can connect to it by using SSH and then you can configure the exact settings by using the CLI.
Conclusion: What a brain releases a switch that is doing dst-mac only; that just angers the customers. Support it properly or leave it is my suggestion.- schumakuMay 09, 2019Guru - Experienced User
Retired_Member wrote:
As far as i understand; in case you want to be able to configure the hashing algorythms for LACP (regardless if L2 or L3) you have to go by the M-Series.
This might be correct, however, this is not the subject here.
We're operating a reasonable number of Smart Managed Pro with LACP trunks for switch interconnections as well as for servers, storage, and high performance workstations .. and don't experience the same issue. There are some very specific use case where L3 and more L4 hashing can bring an advantage - but there are not that many.
There are a few limitations in the implementation, undoubted, ... the perfomance and the cost-per-port comes at a price. The same applies by the way when we go one "class" below, the Smart Managed Plus units which are selling at a fraction of the per-port price, and some people expect at least enterprise if not data center feature sets.
Last but not least, there might be a bug, too.
You still have not shown us your use case, the deployment, and the exact test scenario leading to this issue.
- Retired_MemberMay 09, 2019
As long the switch only supports dst-mac for the hashing, then you always have this situation:
- One to many hosts: Able to use more than one link; because the destination MAC in the tcp package is different.- Many to one host: Unable to use more than one link; because the destination MAC in the tcp package is always the same.
Solution: You should use the src & dst to generate different hashes for many to one associations. This will not affect other use cases.IMHO there is no reason _not_ to use src-dst-mac hashing.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!