3-Node-Cluster Networking with TP-Link and LACP (802.3ad)
Hello Community!
I have a "feature request" for 3-Node-Cluster Networking with two TP-Link T1700X-16TS and TP-Link T1700G-28TQ switches with real working LACP (802.3ad).
Is this scheme feasible with these switches, and if so, how?
Best regards.
Rainair
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
See this FAQ for T1700 switches, first paragraph.
As for mixed active/active and active/standby behavior of a LA group as experienced by the author of the blog post you linked to, see the first answer to the question here: https://serverfault.com/questions/619574/freebsd-link-aggregation-no-faster-than-single-link
Quote:
The default load balancing mode on the Linux bonding driver's LACP mode, and on older Cisco switches like the 2950, is to balance based on MAC address only.
This means if all your traffic is going from one system (file server) to one other MAC (either a default gateway or a Switched Virtual Interface on the switch) then the source and destination MAC will be the same, so only one slave will ever be used.
Quote end.
- Copy Link
- Report Inappropriate Content
I'm not sure what your question is.
Is the question whether the switches support LACP? Yes, they do.
Is the question whether your physical network topology avoids a SPoF? No, it doesn't. If the core switch (the 28TQ) fails, services will be down.
Is the question how to set up a topology for high availability? See this network topology for how to set up a HA cluster.
As for the switches you will need to set up LACP, STP/RSTP and VLANs in my opinion.
For routing you need a routing protocol on the cluster nodes (e.g. OSPF).
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Rainair wrote
The question is: Have the designated TP-Link Switches the spezification for Link Aggregation Group (LAG) with typ IEEE 802.1AX-2008 (previously IEEE 802.3ad). As I read, bonding plays a big role, if it is dynamic or Static LAG (LACP).
I think there is some confusion about terms. LAG stands for Link Aggregation Group, which is just an instace of aggregated ports, while LACP is a protocol to dynamically create such LAGs (versus a static LAG config). What adds to the confusion is that several vendors/systems use other terms for link aggregation such as bonding, trunking , teaming, port aggregation, EtherChannel etc.
Regarding the standards 802.3ad is the name of the workgroup at IEEE which once did standardize link aggregation. The workgroup was moved to the 802.1AX workgroup in 2008, however link aggregation is sometimes still referred to as 802.3ad. LACP is part of the IEEE 802.1AX standard, but it is not the entirety of the 802.1AX standard. Also, there are many more LA methods such as pinning or even port channels which are neither in 802.1AX nor in any other standard and which might need or not need LACP.
So, to answer your question: Yes, T1700X-16TS and T1700G-28TQ both support 802.3ad/802.1AX link aggregation using static and dynamic (LACP) LAGs according to the specs on the TP-Link product website.
- Copy Link
- Report Inappropriate Content
I read about problems with 802.3ad LAG/LACP, because there are only one direction with full bandwidth.
Read: Problem 802.3ad LAG/LACP
The problem was ultimately on the device (firmware). I would like to check in advance whether I have to fear similar problems with TP-Link.
- Copy Link
- Report Inappropriate Content
See this FAQ for T1700 switches, first paragraph.
As for mixed active/active and active/standby behavior of a LA group as experienced by the author of the blog post you linked to, see the first answer to the question here: https://serverfault.com/questions/619574/freebsd-link-aggregation-no-faster-than-single-link
Quote:
The default load balancing mode on the Linux bonding driver's LACP mode, and on older Cisco switches like the 2950, is to balance based on MAC address only.
This means if all your traffic is going from one system (file server) to one other MAC (either a default gateway or a Switched Virtual Interface on the switch) then the source and destination MAC will be the same, so only one slave will ever be used.
Quote end.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @Mitya,
as I understand the thread opener was concerned about compliance with 802.3ad LACP, not stacking. Right, T1700X-16TS is not stackable, only T1700G-28TQ is.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 4807
Replies: 7
Voters 0
No one has voted for it yet.