NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
SXK80 aggregation and AP Mode
Hi there, just bought a RBK852 but I misread the specs, no possible aggregation in AP Mode, just wanted to know if any of you know if it is possible with the SXK80, always time to send back to ch...
Please allow me to add some history to thie thread. Some earlier routers supported port aggregation for two LAN ports. Initially, this was indeed 802.3ad LACP based. With the introduction of the Nighthawk Switch (S8000, technically GS808E) and Nighthawk Gaming Switch (SX10, technically GS810EMX), static LAG [with Balanced XOR TX policy from wally brain] was added to some routers, e.g. the R9000/R8900 at least - simply to gain compatibility in these product lines.
JohnD333 wrote:
Just a heads up the SXR80 and SXS80 only support Balanced XOR aggregation. That feature was added some time ago via firmware update. I do not know if it is possible to add the more advanced port aggregation capabilities via firmware.
Yes, there was a very vague on the SXR80 Firmware Version 3.1.0.104 stating "Supports link aggregation on Ethernet ports." To which ports/devices this does apply, if this does apply to the router WAN side on the router only, if/how this does apply to satellites, if/hot this does apply to AP mode, ... is more than non-transparent. YeZ
JohnD333 wrote:
Unlike the Nighthawk routers that did support IEEE 802.3ad Dynamic Link (LACP), the OrbiProWiFi6 needs an additional advanced switch that supports IEEE 802.3ad, LACP or LAG.
Five-by-one - something mixed up here, in my reading it's completely wrong.
To establish a 802.3ad Dynamic Link LACP LAG, you need devices which can be configured to dynamic LACP LAG on both sides - lack of LACP support on the Orbi Pro WiFi 6 here, this requirement isn't applicable.
To establish a static LAG with Balance XOR TX policy, you need devices which allow the configuration of a static LAG. This would apply to the connection for the SXR80 and SXS80 with some aggregation config based on your observations.
JohnD333 wrote:
For netgear switches, you will need one of its more advanced ones (level 3 if I recall).
No. Almost all Smart Managed Plus and Pro switches - very few exceptions (mostly small port number models) - are supporting static LAG (static Etherchannel by some vendors) config - so perfectly sufficient for this environment.
Schumaker,
What you say about switches sounds much smarter than what I was explicitly told by two different Level 3 Netgear SXR80 tech support people.
So if the SXR80 is not capable of of IEEE..., a fancy switch won’t help? Boy would I have been pissed if I followed their advice to buy one to get my NAS back to IEee configuration after spending $ to upgrade from Nighthawk router to SXR80.
PS, the SXR80 is much better speeds, coverage and IoT separation, just a shame to lose IEee failover.
What you say about switches sounds much smarter than what I was explicitly told by two different Level 3 Netgear SXR80 tech support people.
So if the SXR80 is not capable of of IEEE..., a fancy switch won’t help? Boy would I have been pissed if I followed their advice to buy one to get my NAS back to IEee configuration after spending $ to upgrade from Nighthawk router to SXR80.
PS, the SXR80 is much better speeds, coverage and IoT separation, just a shame to lose IEee failover.
There is no direct relation between NAS LAG/aggregation and the SXx80 aggregation - except if you are going to link these direct.
Please let me know about your intentions on how to connect and wire your network. Not sure I understand it right - you want to put up a wired backhaul with dual Ethernet links aggregation (in router and/or AP mode), and there is a NAS where you want the best speed access of course.
- Schumaku,
Thanks for your guidance.
My Synology NAS is directly connected to SXR80’s aggregated ports. My AV devices and pc’s needing access are wired back to the SCR80 via switches used with the now discarded Nighthawk. A couple are the old dumb switches and a couple are manageable via insight. Devices wanting access to the NAS occasionally on a single switch, but much more common is a single device on each of several switches want that fast access simultaneously. Portable roaming devices occasionally access the NAS.
My switch to SXR80 with SXS80 satellites versus my Nighthawk with WiFi extenders was for much better WiFi for portable devices particularly in areas where I cannot get wire, and of course better speeds and smooth handoffs with roaming devices. Aside from a few initial setup issues and untimely and protracted crashes during/after firmware upgrades, this has worked very well.
Release notes for firmware 3.2.3.100 states “ When link aggregation applies on WAN ports, removing the cable from one of the ports disconnects Internet access. Workaround: Keep two cables on aggregated WAN ports.” I believe the earlier firmware had the same “workaround” text. While the aggregation available on the SXR80 allows fast access to NAS for multiple devices, the failover protection that the Nighhawk had with its IEEE... aggregation is not available on Netgear’s premier business mesh system at the present time. Whether that can be improved with firmware is unknown.
I do understand your point that if I had my NAS connected to a level 3 switch that supported IEEE.... aggregation and all of my devices were wired to that switch directly rather than to the SCR80 those devices would have both speed and NAS failover protection in the event one cable went down. However, that would require such a switch and require me to run a lot more wire.Yes, your environment reflects the typical higher end deployment for home or SOHO.
JohnD333 wrote:
Release notes for firmware 3.2.3.100 states “ When link aggregation applies on WAN ports, removing the cable from one of the ports disconnects Internet access. Workaround: Keep two cables on aggregated WAN ports.” I believe the earlier firmware had the same “workaround” text. While the aggregation available on the SXR80 allows fast access to NAS for multiple devices, the failover protection that the Nighhawk had with its IEEE... aggregation is not available on Netgear’s premier business mesh system at the present time. Whether that can be improved with firmware is unknown.Based on the very limited information, in my understanding this limitation applied to the router mode and the two aggregated links to the router WAN/Internet side. No word of LAN side.
Most static aggregation (static LAG) can and do provide fail-over capability, 802.3ad LACP isn't the only choice. In fact, the most simple static LAG config e.g. on a Linux host does does support fail-over only.
Talking risks - how likely is it that "just" a link fails in such a set-up? The >99.9% reason for aggregation is just providing more bandwidth.
JohnD333 wrote:
I do understand your point that if I had my NAS connected to a level 3 switch that supported IEEE.... aggregation and all of my devices were wired to that switch directly rather than to the SCR80 those devices would have both speed and NAS failover protection in the event one cable went down. However, that would require such a switch and require me to run a lot more wire.The availability of 802.3ad LACP is not something specific to a L3 switch (these would be primarily for supporting IPv4 and IPv6 routing applications among a few others) - this desinformation seems to come from other sources, I've never said this.
I'm having discussions with Netgear why the WAC540 and 564 port LAG (or port aggregation if you want) and similar the SXx80 aren't properly reflected in Insight. In my limited understanding of networking (happy that I can always learn) all these devices should become visible like the switches LAG config on Insight. As a side question, I've challenged them for offering 802.3ad LACP as an alternate aggregation mode.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
