<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic RE: LACP connected host --- two tier MLAG --- LACP connected host in Network Architecture &amp; Design</title>
    <link>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13597#M1001</link>
    <description>Hi Roy,&lt;BR /&gt;
&lt;BR /&gt;
I have tried to show this in this picture below - we want to migrate the EAPS Setup (BLACK) to the MLAG Setup (RED) without any interruption if possible&lt;BR /&gt;
&lt;BR /&gt;
1. first we have the EAPS setup (black connections) - some devices are connected with LACP some just have a single connection&lt;BR /&gt;
&lt;BR /&gt;
2. we want to configure the MLAG setup with ports shutdown - break up the EAPS -  and migrate the attached devices step by step to the MLAG&lt;BR /&gt;
&lt;BR /&gt;
to aviod loops we decided to shudown one port of any LAG/LACP connected device (e.g. the dual-homed Access Switches ) so we just have to add a single connection to the MLAG ports by adding them like this (enable mlag port &amp;lt;&amp;gt; peer isc-test-2 id 71)&lt;BR /&gt;
&lt;BR /&gt;
so i think we dont run into any problems , if half of the MLAG ports (lsc-test-1 - lsc-test-2) are configured with (enable mlag port &amp;lt;&amp;gt; peer isc-test-2 id 71) and the others without - as long as we ensure that we do not have any LACP dual-homed devices connected to MLAG ports  (lsc-test-1 - lsc-test-2) without an enabled mlag port (enable mlag port &amp;lt;&amp;gt; peer isc-test-2 id 71) configuration.&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;A href="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20170126-58229-1vdqhpl-2017-01-26_16_40_14-2017-01-26_16_04_11-Protokoll_eaps.pdf.png_-_Paint_inline.png" rel="image" class="fancybox"&gt;&lt;IMG src="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20170126-58229-1vdqhpl-2017-01-26_16_40_14-2017-01-26_16_04_11-Protokoll_eaps.pdf.png_-_Paint_inline.png" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
greetings&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Thu, 26 Jan 2017 23:04:00 GMT</pubDate>
    <dc:creator>enrico_kunert</dc:creator>
    <dc:date>2017-01-26T23:04:00Z</dc:date>
    <item>
      <title>LACP connected host --- two tier MLAG --- LACP connected host</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13592#M996</link>
      <description>Hi all,&lt;BR /&gt;
&lt;BR /&gt;
we have the following testsetup and i have a question regarding the different ping behavior as shown below... plz have a look and thank you in advance&lt;BR /&gt;
&lt;BR /&gt;
two tier MALG with two connected LACP Hosts/switches&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;A href="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20170124-98732-awq573-2017-01-24_17_10_30-Protokoll_V2.pdf_inline.png" rel="image" class="fancybox"&gt;&lt;IMG src="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20170124-98732-awq573-2017-01-24_17_10_30-Protokoll_V2.pdf_inline.png" /&gt;&lt;/A&gt;&lt;/P&gt;﻿&lt;BR /&gt;
&lt;BR /&gt;
config as shown below....&lt;BR /&gt;
&lt;BR /&gt;
﻿&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;A href="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20170124-29329-1pwbs68-2017-01-24_17_12_29-Protokoll_V2.pdf_inline.png" rel="image" class="fancybox"&gt;&lt;IMG src="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20170124-29329-1pwbs68-2017-01-24_17_12_29-Protokoll_V2.pdf_inline.png" /&gt;&lt;/A&gt;&lt;/P&gt;﻿&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;A href="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20170124-112870-x97gdf-2017-01-24_17_13_25-Protokoll_V2.pdf_inline.png" rel="image" class="fancybox"&gt;&lt;IMG src="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20170124-112870-x97gdf-2017-01-24_17_13_25-Protokoll_V2.pdf_inline.png" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
testcases.....&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;A href="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20170124-55643-b6ao6j-2017-01-24_17_14_12-Protokoll_V2.pdf_inline.png" rel="image" class="fancybox"&gt;&lt;IMG src="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20170124-55643-b6ao6j-2017-01-24_17_14_12-Protokoll_V2.pdf_inline.png" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
﻿&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;A href="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20170124-2050-5otejs-2017-01-24_17_14_24-Protokoll_V2.pdf_inline.png" rel="image" class="fancybox"&gt;&lt;IMG src="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20170124-2050-5otejs-2017-01-24_17_14_24-Protokoll_V2.pdf_inline.png" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
﻿&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;A href="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20170124-91126-1mk4xgz-2017-01-24_17_14_35-Protokoll_V2.pdf_inline.png" rel="image" class="fancybox"&gt;&lt;IMG src="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20170124-91126-1mk4xgz-2017-01-24_17_14_35-Protokoll_V2.pdf_inline.png" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
thx&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 24 Jan 2017 23:16:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13592#M996</guid>
      <dc:creator>enrico_kunert</dc:creator>
      <dc:date>2017-01-24T23:16:00Z</dc:date>
    </item>
    <item>
      <title>RE: LACP connected host --- two tier MLAG --- LACP connected host</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13593#M997</link>
      <description>Hello Enrico,&lt;BR /&gt;
It seems all of ISC ports do not have data vlan "v_test" as tagged.&lt;BR /&gt;
Can you check again after you assign the ISC ports to the vlan as tagged port on all the switches?&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 25 Jan 2017 12:44:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13593#M997</guid>
      <dc:creator>Roy_Noh</dc:creator>
      <dc:date>2017-01-25T12:44:00Z</dc:date>
    </item>
    <item>
      <title>RE: LACP connected host --- two tier MLAG --- LACP connected host</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13594#M998</link>
      <description>I think this article also will be helpful for better understanding.&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-configure-MLAG-in-Extreme-switches/?q=mlag+vlan&amp;amp;#38;l=en_US&amp;amp;#38;c=Extreme_Software%3AExtremeXOS_EXOS&amp;amp;#38;fs=Search&amp;amp;#38;pn=1" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-configure-MLAG-in-Extreme-switches/...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Please check &lt;B&gt;"Step 5: Add data carrying VLANs."&lt;/B&gt; carefully.&lt;BR /&gt;</description>
      <pubDate>Wed, 25 Jan 2017 12:52:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13594#M998</guid>
      <dc:creator>Roy_Noh</dc:creator>
      <dc:date>2017-01-25T12:52:00Z</dc:date>
    </item>
    <item>
      <title>RE: LACP connected host --- two tier MLAG --- LACP connected host</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13595#M999</link>
      <description>Hey Roy,&lt;BR /&gt;
&lt;BR /&gt;
yep thx, u´re right^^ it´s working now.&lt;BR /&gt;
&lt;BR /&gt;
I have another question, regarding migrating the hole system from EAPS Domain to this two Tier MLAG design.&lt;BR /&gt;
&lt;BR /&gt;
- currently we use LACP connected devices or single connected devices&lt;BR /&gt;
&lt;BR /&gt;
- we want to migrate them Step by Step to the MLAG&lt;BR /&gt;
&lt;BR /&gt;
e.g.: enable mlag port 3:2 peer isc-test-2 id 71&lt;BR /&gt;
&lt;BR /&gt;
- is it a problem to run "normal" connected devices without a mlag peer configuration at the edge port, with devices at mlag peer configured edge ports at the same MLAG switch?&lt;BR /&gt;
&lt;BR /&gt;
Are there any known challenges or best practices to get this done without greater interruptions?&lt;BR /&gt;
&lt;BR /&gt;
thx in advance!&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 25 Jan 2017 20:44:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13595#M999</guid>
      <dc:creator>enrico_kunert</dc:creator>
      <dc:date>2017-01-25T20:44:00Z</dc:date>
    </item>
    <item>
      <title>RE: LACP connected host --- two tier MLAG --- LACP connected host</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13596#M1000</link>
      <description>Hello Enrico,&lt;BR /&gt;
&lt;BR /&gt;
I actually didn't get the assumption that you are saying with "normal connected devices without a mlag peer configuration at the   edge port, with devices at mlag peer configured edge ports at the same   MLAG switch".&lt;BR /&gt;
Do you mean by that there's no mlag peer configuration between two dist switches and connect a access switch to both of them? Then it definitely makes a loop.&lt;BR /&gt;
Can you explain it for better understanding? &lt;BR /&gt;
 &lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 26 Jan 2017 12:42:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13596#M1000</guid>
      <dc:creator>Roy_Noh</dc:creator>
      <dc:date>2017-01-26T12:42:00Z</dc:date>
    </item>
    <item>
      <title>RE: LACP connected host --- two tier MLAG --- LACP connected host</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13597#M1001</link>
      <description>Hi Roy,&lt;BR /&gt;
&lt;BR /&gt;
I have tried to show this in this picture below - we want to migrate the EAPS Setup (BLACK) to the MLAG Setup (RED) without any interruption if possible&lt;BR /&gt;
&lt;BR /&gt;
1. first we have the EAPS setup (black connections) - some devices are connected with LACP some just have a single connection&lt;BR /&gt;
&lt;BR /&gt;
2. we want to configure the MLAG setup with ports shutdown - break up the EAPS -  and migrate the attached devices step by step to the MLAG&lt;BR /&gt;
&lt;BR /&gt;
to aviod loops we decided to shudown one port of any LAG/LACP connected device (e.g. the dual-homed Access Switches ) so we just have to add a single connection to the MLAG ports by adding them like this (enable mlag port &amp;lt;&amp;gt; peer isc-test-2 id 71)&lt;BR /&gt;
&lt;BR /&gt;
so i think we dont run into any problems , if half of the MLAG ports (lsc-test-1 - lsc-test-2) are configured with (enable mlag port &amp;lt;&amp;gt; peer isc-test-2 id 71) and the others without - as long as we ensure that we do not have any LACP dual-homed devices connected to MLAG ports  (lsc-test-1 - lsc-test-2) without an enabled mlag port (enable mlag port &amp;lt;&amp;gt; peer isc-test-2 id 71) configuration.&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;A href="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20170126-58229-1vdqhpl-2017-01-26_16_40_14-2017-01-26_16_04_11-Protokoll_eaps.pdf.png_-_Paint_inline.png" rel="image" class="fancybox"&gt;&lt;IMG src="https://d1uyvls174j03l.cloudfront.net/extremenetworks-us/attachment/RackMultipart20170126-58229-1vdqhpl-2017-01-26_16_40_14-2017-01-26_16_04_11-Protokoll_eaps.pdf.png_-_Paint_inline.png" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
greetings&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 26 Jan 2017 23:04:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13597#M1001</guid>
      <dc:creator>enrico_kunert</dc:creator>
      <dc:date>2017-01-26T23:04:00Z</dc:date>
    </item>
    <item>
      <title>RE: LACP connected host --- two tier MLAG --- LACP connected host</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13598#M1002</link>
      <description>Enrico, Sorry for late response.&lt;BR /&gt;
Yes, I think there should be no issue if you stick to your plan.&lt;BR /&gt;
ELRP can be helpful to detect a temporary loop just in case.&lt;BR /&gt;
You can easily be noticed by switch logs if there's any loop.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Feb 2017 09:21:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13598#M1002</guid>
      <dc:creator>Roy_Noh</dc:creator>
      <dc:date>2017-02-01T09:21:00Z</dc:date>
    </item>
    <item>
      <title>RE: LACP connected host --- two tier MLAG --- LACP connected host</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13599#M1003</link>
      <description>Hi Roy,&lt;BR /&gt;
&lt;BR /&gt;
thank you for your help.&lt;BR /&gt;
&lt;BR /&gt;
ELRP just need to be configured at non MLAG ports, right?&lt;BR /&gt;
&lt;BR /&gt;
greetings&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Feb 2017 15:40:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13599#M1003</guid>
      <dc:creator>enrico_kunert</dc:creator>
      <dc:date>2017-02-01T15:40:00Z</dc:date>
    </item>
    <item>
      <title>RE: LACP connected host --- two tier MLAG --- LACP connected host</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13600#M1004</link>
      <description>I guess there should be no loop based on your scenario, but a loop may produced by mistake on configuration or by edge switches. EXOS user guide introduces some cases and how to prevent it with ELRP egress port disable with MLAG configuration.&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="http://documentation.extremenetworks.com/exos_16/EXOS_16_2/Troubleshooting/c_elrp-egress-port-disable.shtml" target="_blank" rel="nofollow noreferrer noopener"&gt;http://documentation.extremenetworks.com/exos_16/EXOS_16_2/Troubleshooting/c_elrp-egress-port-disabl...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Feb 2017 17:32:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/lacp-connected-host-two-tier-mlag-lacp-connected-host/m-p/13600#M1004</guid>
      <dc:creator>Roy_Noh</dc:creator>
      <dc:date>2017-02-01T17:32:00Z</dc:date>
    </item>
  </channel>
</rss>

