<?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 Mixing VDX long-distance isl and lossy isl to same RBRIDGE in Data Center (VDX)</title>
    <link>https://community.extremenetworks.com/t5/data-center-vdx/mixing-vdx-long-distance-isl-and-lossy-isl-to-same-rbridge/m-p/76569#M452</link>
    <description>In general can long-distance lossless ISL links and lossy ISL links to link same &lt;BR /&gt;
In my specific case: Would it be a good practice to add long-distance lossless 10G ISL links to a VCS logical chassis that has two 40G-LR isl links?</description>
    <pubDate>Fri, 20 Sep 2019 02:03:48 GMT</pubDate>
    <dc:creator>wgs</dc:creator>
    <dc:date>2019-09-20T02:03:48Z</dc:date>
    <item>
      <title>Mixing VDX long-distance isl and lossy isl to same RBRIDGE</title>
      <link>https://community.extremenetworks.com/t5/data-center-vdx/mixing-vdx-long-distance-isl-and-lossy-isl-to-same-rbridge/m-p/76569#M452</link>
      <description>In general can long-distance lossless ISL links and lossy ISL links to link same &lt;BR /&gt;
In my specific case: Would it be a good practice to add long-distance lossless 10G ISL links to a VCS logical chassis that has two 40G-LR isl links?</description>
      <pubDate>Fri, 20 Sep 2019 02:03:48 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-vdx/mixing-vdx-long-distance-isl-and-lossy-isl-to-same-rbridge/m-p/76569#M452</guid>
      <dc:creator>wgs</dc:creator>
      <dc:date>2019-09-20T02:03:48Z</dc:date>
    </item>
    <item>
      <title>Re: Mixing VDX long-distance isl and lossy isl to same RBRIDGE</title>
      <link>https://community.extremenetworks.com/t5/data-center-vdx/mixing-vdx-long-distance-isl-and-lossy-isl-to-same-rbridge/m-p/76570#M453</link>
      <description>WGS,&lt;BR /&gt;
&lt;BR /&gt;
For Best practices, I would recommend you review &lt;A href="https://www.extremenetworks.com/extreme-validated-solutions/" target="_blank" rel="nofollow noreferrer noopener"&gt;Extreme Validated Designs&lt;/A&gt; page.  Also regarding ISLs I would recommend reviewing the&lt;A href="https://gtacknowledge.extremenetworks.com/articles/Q_A/What-are-limitations-for-using-long-distance-ISL" target="_blank" rel="nofollow noreferrer noopener"&gt; guidelines and restrictions for long distance ISLs&lt;/A&gt;.&lt;BR /&gt;
&lt;BR /&gt;
Thanks, &lt;BR /&gt;
&lt;BR /&gt;
Michael Morey &lt;BR /&gt;
Principal Technical Support Engineer – Switching, Routing &amp;amp; Analytics</description>
      <pubDate>Fri, 20 Sep 2019 02:20:57 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-vdx/mixing-vdx-long-distance-isl-and-lossy-isl-to-same-rbridge/m-p/76570#M453</guid>
      <dc:creator>Michael_Morey</dc:creator>
      <dc:date>2019-09-20T02:20:57Z</dc:date>
    </item>
    <item>
      <title>Re: Mixing VDX long-distance isl and lossy isl to same RBRIDGE</title>
      <link>https://community.extremenetworks.com/t5/data-center-vdx/mixing-vdx-long-distance-isl-and-lossy-isl-to-same-rbridge/m-p/76571#M454</link>
      <description>Hi Michael,&lt;BR /&gt;
&lt;BR /&gt;
I have review those documents, but confused slight by conflicting information in the release notes for NOS 7.3.&lt;BR /&gt;
&lt;BR /&gt;
I am looking to create VCS logical chassis between data centers that are about 2.5km distant. I could use 10G-LR ISL with long distance.  The release notes imply that lossy 40G ISL are a valid choice: &lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
• The 40G and 100G interfaces do not support “long-distance isl” command, however can extend distances for non-lossless traffic up to 40Km using standard ISLs. &lt;BR /&gt;
&lt;BR /&gt;
This is for client to server traffic and L3 routing.</description>
      <pubDate>Fri, 20 Sep 2019 02:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-vdx/mixing-vdx-long-distance-isl-and-lossy-isl-to-same-rbridge/m-p/76571#M454</guid>
      <dc:creator>wgs</dc:creator>
      <dc:date>2019-09-20T02:57:00Z</dc:date>
    </item>
    <item>
      <title>Re: Mixing VDX long-distance isl and lossy isl to same RBRIDGE</title>
      <link>https://community.extremenetworks.com/t5/data-center-vdx/mixing-vdx-long-distance-isl-and-lossy-isl-to-same-rbridge/m-p/76572#M455</link>
      <description>I think perhaps I am overthinking this. We are not on WAN/METRO setup. This is all the same L2, just direct 2.5Km fiber between two rbridges.</description>
      <pubDate>Fri, 20 Sep 2019 04:00:42 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-vdx/mixing-vdx-long-distance-isl-and-lossy-isl-to-same-rbridge/m-p/76572#M455</guid>
      <dc:creator>wgs</dc:creator>
      <dc:date>2019-09-20T04:00:42Z</dc:date>
    </item>
    <item>
      <title>Re: Mixing VDX long-distance isl and lossy isl to same RBRIDGE</title>
      <link>https://community.extremenetworks.com/t5/data-center-vdx/mixing-vdx-long-distance-isl-and-lossy-isl-to-same-rbridge/m-p/76573#M456</link>
      <description>WGS,&lt;BR /&gt;
&lt;BR /&gt;
As the release notes state, the 40G and 100G interfaces do not support the Lossless "long-distance isl" command.  The optics do however support distances up to 40Km and can be used as a standard "lossy" ISL.&lt;BR /&gt;
&lt;BR /&gt;
Lossless support on 40G and 100G interfaces is limited to 1Km&lt;BR /&gt;
&lt;BR /&gt;
Thanks,&lt;BR /&gt;
&lt;BR /&gt;
Michael Morey&lt;BR /&gt;
Principal Technical Support Engineer – Switching, Routing &amp;amp; Analytics</description>
      <pubDate>Fri, 20 Sep 2019 04:02:32 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-vdx/mixing-vdx-long-distance-isl-and-lossy-isl-to-same-rbridge/m-p/76573#M456</guid>
      <dc:creator>Michael_Morey</dc:creator>
      <dc:date>2019-09-20T04:02:32Z</dc:date>
    </item>
  </channel>
</rss>

