<?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: MLAG. ISC-link is LAG, MLAG-link is LACP. in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/mlag-isc-link-is-lag-mlag-link-is-lacp/m-p/51530#M14078</link>
    <description>There is no such restriction. ISC can be Static sharing and MLAG can be LACP or Static or mixed. On CLIENT also, you need to enable LACP sharing on ports connecting to both X670s&lt;BR /&gt;
Example:&lt;BR /&gt;
enable sharing 16 grouping 16,17 lacp</description>
    <pubDate>Wed, 11 Mar 2015 16:57:00 GMT</pubDate>
    <dc:creator>Masadi__Ravi</dc:creator>
    <dc:date>2015-03-11T16:57:00Z</dc:date>
    <item>
      <title>MLAG. ISC-link is LAG, MLAG-link is LACP.</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/mlag-isc-link-is-lag-mlag-link-is-lacp/m-p/51529#M14077</link>
      <description>Hi everybody.&lt;BR /&gt;
&lt;BR /&gt;
I have two x670 switches which are MLAG peers. The ISC link between them is LAG actually. All "clients" connect to this switches with static LAG, but I have to connect one LACP client. Is it possible to use LACP MLAG with static LAG ISC link. So much terms... My diagram below.&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="44d4c89580214786bd45d95291fad74c_RackMultipart20150311-9033-1j7cgak-20150311_134100_inline.jpg"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/2989iC45DC566C7029A38/image-size/large?v=v2&amp;amp;px=999" role="button" title="44d4c89580214786bd45d95291fad74c_RackMultipart20150311-9033-1j7cgak-20150311_134100_inline.jpg" alt="44d4c89580214786bd45d95291fad74c_RackMultipart20150311-9033-1j7cgak-20150311_134100_inline.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
As I understand it, config on MLAG peers should be like that&lt;BR /&gt;
&lt;BR /&gt;
PEER1&lt;BR /&gt;
enable sharing 16 grouping 16 lacp&lt;BR /&gt;
enable mlag ports 16 peer PEER2 id 100&lt;BR /&gt;
&lt;BR /&gt;
PEER2&lt;BR /&gt;
enable sharing 16 grouping 16 lacp&lt;BR /&gt;
enable mlag ports 16 peer PEER1 id 100&lt;BR /&gt;
&lt;BR /&gt;
CLIENT&lt;BR /&gt;
configure LACP&lt;BR /&gt;
configure lower LACP priority&lt;BR /&gt;
&lt;BR /&gt;
Should I configure something else?&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Mar 2015 16:45:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/mlag-isc-link-is-lag-mlag-link-is-lacp/m-p/51529#M14077</guid>
      <dc:creator>eyeV</dc:creator>
      <dc:date>2015-03-11T16:45:00Z</dc:date>
    </item>
    <item>
      <title>RE: MLAG. ISC-link is LAG, MLAG-link is LACP.</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/mlag-isc-link-is-lag-mlag-link-is-lacp/m-p/51530#M14078</link>
      <description>There is no such restriction. ISC can be Static sharing and MLAG can be LACP or Static or mixed. On CLIENT also, you need to enable LACP sharing on ports connecting to both X670s&lt;BR /&gt;
Example:&lt;BR /&gt;
enable sharing 16 grouping 16,17 lacp</description>
      <pubDate>Wed, 11 Mar 2015 16:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/mlag-isc-link-is-lag-mlag-link-is-lacp/m-p/51530#M14078</guid>
      <dc:creator>Masadi__Ravi</dc:creator>
      <dc:date>2015-03-11T16:57:00Z</dc:date>
    </item>
    <item>
      <title>RE: MLAG. ISC-link is LAG, MLAG-link is LACP.</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/mlag-isc-link-is-lag-mlag-link-is-lacp/m-p/51531#M14079</link>
      <description>Thanks!&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Mar 2015 16:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/mlag-isc-link-is-lag-mlag-link-is-lacp/m-p/51531#M14079</guid>
      <dc:creator>eyeV</dc:creator>
      <dc:date>2015-03-11T16:57:00Z</dc:date>
    </item>
    <item>
      <title>RE: MLAG. ISC-link is LAG, MLAG-link is LACP.</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/mlag-isc-link-is-lag-mlag-link-is-lacp/m-p/51532#M14080</link>
      <description>eyeV, &lt;BR /&gt;
&lt;BR /&gt;
Your configuration looks good on the client side and is totally independent of the ISC link.  The unintended benefit of configuring a single port lag per switch is that you can dynamically add ports without killing the mlag port pairs for the client. &lt;BR /&gt;
&lt;BR /&gt;
Bill&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Mar 2015 17:58:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/mlag-isc-link-is-lag-mlag-link-is-lacp/m-p/51532#M14080</guid>
      <dc:creator>Bill_Stritzinge</dc:creator>
      <dc:date>2015-03-11T17:58:00Z</dc:date>
    </item>
    <item>
      <title>RE: MLAG. ISC-link is LAG, MLAG-link is LACP.</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/mlag-isc-link-is-lag-mlag-link-is-lacp/m-p/51533#M14081</link>
      <description>I believe I have the same situation but I'm not understanding this fully.  I have an ISC link between my black diamonds (MLAG peer doesn't have lacp configured).  The sharing between them is L3-L4 lacp.  But I have MLAG client (460) set up as a static LAG.   If I understand this right I can change the client to L3-L4 lacp and configure the MLAG peer lacp-mac auto and wouldn't cause an issue - because both ends can support either static or LACP?  Is there any other benefit with LACP vs static like better load distribution than just peering the LAG connections?&lt;BR /&gt;
&lt;BR /&gt;
Thank you&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 23 Sep 2015 18:22:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/mlag-isc-link-is-lag-mlag-link-is-lacp/m-p/51533#M14081</guid>
      <dc:creator>treese</dc:creator>
      <dc:date>2015-09-23T18:22:00Z</dc:date>
    </item>
    <item>
      <title>RE: MLAG. ISC-link is LAG, MLAG-link is LACP.</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/mlag-isc-link-is-lag-mlag-link-is-lacp/m-p/51534#M14082</link>
      <description>Yes, you can change the client sharing to LACP and it wouldn't cause an issue. Morover, I didn't configure the mlag peer lacp-mac auto then I installed LACP. I definetly prefer static, because I like hardcoding everithing. &lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 23 Sep 2015 18:22:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/mlag-isc-link-is-lag-mlag-link-is-lacp/m-p/51534#M14082</guid>
      <dc:creator>eyeV</dc:creator>
      <dc:date>2015-09-23T18:22:00Z</dc:date>
    </item>
    <item>
      <title>RE: MLAG. ISC-link is LAG, MLAG-link is LACP.</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/mlag-isc-link-is-lag-mlag-link-is-lacp/m-p/51535#M14083</link>
      <description>config LACP on MLAG doesn't seem easy but if I understand it right LACP will detact a bad gbic or fiber cable and will down the LAG.  I'm leaning toward static MLAG LAG too.  I have it currently set this way but our FW images support LACP LAG and was seeing if we could get some real benefit to it.   Thank you.&lt;BR /&gt;</description>
      <pubDate>Wed, 23 Sep 2015 18:22:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/mlag-isc-link-is-lag-mlag-link-is-lacp/m-p/51535#M14083</guid>
      <dc:creator>treese</dc:creator>
      <dc:date>2015-09-23T18:22:00Z</dc:date>
    </item>
  </channel>
</rss>

