Future Consideration [FEATURE REQUEST]: ER8411 - add LAN LAG (Link Aggregation) feature
Hi Team, @Fae ,
Could you please tell - do you have in your roadmap a plan to add LAG to ER8411? And can this model support the LAG feature at all?
Thank you!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hopefully somebody from the dev team will notice us requesting this feature.
I am happy with the device, and I am pretty sure the hw is completelly capable of handling LAG , so i don't see why they wouldn't do it .
- Copy Link
- Report Inappropriate Content
Absolutely agree that this is a workaround solution, but:
1. We still have not received a confirmation from TP-Link that this feature is doable for ER8411. However, due to hardware limitations, it is not possible for ER7206 and other ERs.
2. We have no estimations, ETA or any promises that this feature will be available at all.
3. What alternatives do we have? Ubiquiti has the same issue. Fortinet - the price is double + annual licenses.
4. In case we get a new FW with LAG, how risky will it be to use it in production systems without proper testing? This testing will take more time and money than several hundred for additional switches.
Any other ideas?
- Copy Link
- Report Inappropriate Content
Thanks for posting in our business forum.
Warlocc wrote
@Alex_UTS wrote
Absolutely agree that this is a workaround solution, but:
1. We still have not received a confirmation from TP-Link that this feature is doable for ER8411. However, due to hardware limitations, it is not possible for ER7206 and other ERs.
2. We have no estimations, ETA or any promises that this feature will be available at all.
3. What alternatives do we have? Ubiquiti has the same issue. Fortinet - the price is double + annual licenses.
4. In case we get a new FW with LAG, how risky will it be to use it in production systems without proper testing? This testing will take more time and money than several hundred for additional switches.
Any other ideas?
If I am not informed by the dev that is under consideration, I will not change the label of this post.
Future Consideration has explained the status of this thread.
If you are desperate for this feature, please consider an alternative if you think it is crucial to your network.
Evaluation and the road to this feature will take time. I am not gonna guarantee anything without a confirmation from the dev. And dev will not guarantee me as well because there are projects going on as V5.15 will also be a big release and they are preparing for that.
When we evaluate the feature requests, we will take into the moves of our competitors. Put differently, if UBNT does not support LAG on the router, we might not consider it.
Beyond that, the dev will also consider the chipset and architecture of the chip.
For you, it is a missing feature that we did not guarantee from the very beginning of its release. You should keep that in mind not everything is gonna be added by your request. Not absolute. And we still have many other aspects to consider.
Please be patient as I am consulting with the dev again on this.
- Copy Link
- Report Inappropriate Content
Hi @Alex_UTS and all,
LAG for ER8411 is not considered this year. Dev has looked into this feature now and has started market research.
"Even if we are going to develop this, this will be scheduled for next year."
Still in the evaluation phase. I will collect your described use scenario for the dev to mark the priority this week. (This is not a guarantee to any degree either.) For others who did not describe the usage, I cannot write your single line in the report as it does not make any sense in the scenario description.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
In order to have LAG/LACP you must have STP the very least. or else the switch will just loop.
They don't even have STP in the ER8411.
Kinda sad.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 40
Views: 3335
Replies: 38