05-17-2019 09:51 AM
I'm trying to get a clearer understanding of when to use MLAG with LACP and when not. I did read the note in https://extremeportal.force.com/ExtrArticleDetail?an=000079895 that reads "if the downstream device (e.g. switch, server, etc..) is using LACP LAG sharing on its ports, it will be necessary to enable LACP LAG on the MLAG ports", but I'm still a little fuzzy - probably because I don't understand the "black magic" fully.
Here's my layout - we're running EXOS 16.x:ISC (ports 1:24/2:24) BD8800-1 ==== BD8800-2 1:1| 2:1\ 1:1/ |2:1 | \ / | | X | | / \ | 23| 24/ 23\ |24 Switch-1 Switch-2 5| 5| | | | | Server (Linux or Microsoft) with LACP share
Shared port group between the BD8800s for the ISC (enable sharing 1:24 grouping 1:24,2:24)
1-port shared "port group" to Switch-1 on the 8800 (enable sharing 1:1 grouping 1:1)
Same to Switch 2 (enable sharing 2:1 grouping 2:1)
Shared port group on Switch-1/2 to the BD8800s (sharing 23 grouping 23,24)
Single-port share-group on Switch-1 and Switch-2 on the port 5 to the server
mlag: enable mlag port 1:1 peer "8800-1/2" id 123 (on the 8800s)
On top of that: The BD8800s are the "default gateway" in a VRRP configuration for the vlan that the attached server is in (in case it matters)
Question 1:
In the scenario above, what shares on which switches/shares would have to be done with LACP - for instance "enable sharing X grouping ... L3_L4 LACP" (since I'd like to use L3_L4 on the server side)?
Question 2:
If I were to add an ISC link between Switch-1 and Switch-2, would the only LACP share configuration be on Switch-1/2 (and not on BDs)?
Question 3:
Are there any advantages/disadvantages to using "LACP" as opposed to not using it and going with Extreme's "pure purple magic"?
Thank you for looking at this!
Solved! Go to Solution.
05-21-2019 06:34 PM
05-22-2019 08:33 AM
05-21-2019 06:34 PM
05-21-2019 11:36 AM
You must add the ISC to every VLAN that has an MLAG link as a member port
05-21-2019 08:09 AM