Two-Switch Redundancy using LACP 802.3ad for devices and LAG between switches
Two-Switch Redundancy using LACP 802.3ad for devices and LAG between switches
I want to connect two TL-SG3210XHP-M2 together such that a NAS with two 1GbE interfaces can be configured for 802.3ad (mode-4 LACP channel bonding) with one eth port plugged into each switch to provide bandwidth aggregation and fail-over.
I presume the 2 SG switches would use 1 LAG between them (eg: Port 9 using a 10GbE SFP+ TwinAx "copper" cable) and a 2nd LAG on each switch that "up-links" to a non-TPL (Allied Telesys) switch (eg: Port 10 using an SFP 1GbE optical SFP and 65.2 micron fiber).
The goals are:
- Under normal conditions, the NAS device and all NAS clients would use both of the links for LACP bandwidth aggregation (approx 2Gb) with redundancy and also able to reach the core (the Allied Telesys switch) through the LAG up-link.
- If one of the SG3210 fails (or goes offline for maintenance), all NAS traffic would seamlessly use the surviving SG3210 switch (path) and all of its traffic would reach the core at 1Gb.
- Propagate any VLAN details between the core and the 2 SG switches.
Is this as simple as:
- Using the GUI on each SG switch to define a Static LAG on SG-1 and SG-2 for port 9 (using the same Group ID) and then connecting the 10GbE TwinAx cable between the two SG switches on port 9,
- Using the GUI on each SG switch to define a Static LAG on SG-1 and SG-2 for port 10 (using the same Group ID) and then connecting the 1GbE optical cable up to matching ports on the Allied Telesys switch (preconfigured).
- Using the GUI on each SG switch to define an LACP (SG-1, 1/0/1 and SG-2 1/0/1, both active, both using the same Group ID and both using the same Port Priority) for the NAS device (and duplicate as needed).
Thanks