Stop layer 2 loop with legacy to MLAG pair
Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎04-03-2018 02:04 PM
Hi,
The design intention is to provide connectivity to VLAN X & Y should either one of the legacy cores fail, unfortunately it has to be this way with the VLANs stretched across.
I could equally create a LAG that that goes from one of the legacy cores to each of the new MLAG cores, but in the diagram below I have them directly linked.
The issue here is that I will need to block either LAG A or LAG B to stop a loop. I can't use STP as its not supported on MLAG. Don't think I can really use ELRP, although it will block the loop its not really a redundancy protocol.
Was thinking of perhaps using (SRP) software redundant port, as each of the switches are Extreme, but not sure if that concept will work or how it would work with the below:
Perhaps there is another method I am missing, but just seeing what the community thinks.
Many thanks in advance
The design intention is to provide connectivity to VLAN X & Y should either one of the legacy cores fail, unfortunately it has to be this way with the VLANs stretched across.
I could equally create a LAG that that goes from one of the legacy cores to each of the new MLAG cores, but in the diagram below I have them directly linked.
The issue here is that I will need to block either LAG A or LAG B to stop a loop. I can't use STP as its not supported on MLAG. Don't think I can really use ELRP, although it will block the loop its not really a redundancy protocol.
Was thinking of perhaps using (SRP) software redundant port, as each of the switches are Extreme, but not sure if that concept will work or how it would work with the below:
Perhaps there is another method I am missing, but just seeing what the community thinks.
Many thanks in advance
5 REPLIES 5
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎04-03-2018 02:38 PM
The switches should be the same hardware in order to run a supported MLAG configuration as well.
Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎04-03-2018 02:36 PM
Hi Dorian,
That is a good option. The legacy switches are an X670 and X650, although the problem in this case is the work evolved in reconfiguring the legacy switches is required without disruption as those VLANs currently stretch all over the network too lots of different switches.
Defiantly one worth noting though.
Thanks.
That is a good option. The legacy switches are an X670 and X650, although the problem in this case is the work evolved in reconfiguring the legacy switches is required without disruption as those VLANs currently stretch all over the network too lots of different switches.
Defiantly one worth noting though.
Thanks.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎04-03-2018 02:28 PM
Hi Martin,
What are the legacy core devices? Do they support a multiswitch LAG protocol?
If all 4 switches were EXOS, this would be configured as 2-Tier MLAG.
https://gtacknowledge.extremenetworks.com/articles/How_To/Sample-configuration-for-two-tier-MLAG/?q=...
What are the legacy core devices? Do they support a multiswitch LAG protocol?
If all 4 switches were EXOS, this would be configured as 2-Tier MLAG.
https://gtacknowledge.extremenetworks.com/articles/How_To/Sample-configuration-for-two-tier-MLAG/?q=...
Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎04-03-2018 02:18 PM
Thanks for posting back Patrick.
I should have mentioned EAPS, although I did wonder if it still had a problem when used in conjunction with MLAG. If I configure it as you say then it sounds like a solution.
I'll give that a go.
Cheers.
I should have mentioned EAPS, although I did wonder if it still had a problem when used in conjunction with MLAG. If I configure it as you say then it sounds like a solution.
I'll give that a go.
Cheers.
