<?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: Shortest path with ISLs? in Data Center (SLX)</title>
    <link>https://community.extremenetworks.com/t5/data-center-slx/shortest-path-with-isls/m-p/20875#M174</link>
    <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
as I understand your post the shortest path is used, but due to a fixed link cost the metric is practically just the hop-count between the end points.&lt;BR /&gt;
&lt;BR /&gt;
Thanks,&lt;BR /&gt;
Erik&lt;BR /&gt;</description>
    <pubDate>Wed, 19 Sep 2018 19:55:00 GMT</pubDate>
    <dc:creator>Erik_Auerswald</dc:creator>
    <dc:date>2018-09-19T19:55:00Z</dc:date>
    <item>
      <title>Shortest path with ISLs?</title>
      <link>https://community.extremenetworks.com/t5/data-center-slx/shortest-path-with-isls/m-p/20873#M172</link>
      <description>Hello,&lt;BR /&gt;
&lt;BR /&gt;
Sorry if it has been cleared before, but is there any short-path intelligence with ISL links?&lt;BR /&gt;
&lt;BR /&gt;
We have a fabric of six 6740T-1G VDXs running NOS 6.0.2b in a triangle (L2, stretched), and would like to ensure that when the server from Switch1 talks to the server from Switch2 it doesn't traverse via Switch3. &lt;BR /&gt;
&lt;BR /&gt;
Thank you.</description>
      <pubDate>Wed, 19 Sep 2018 19:17:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-slx/shortest-path-with-isls/m-p/20873#M172</guid>
      <dc:creator>Roman_Serbski</dc:creator>
      <dc:date>2018-09-19T19:17:00Z</dc:date>
    </item>
    <item>
      <title>RE: Shortest path with ISLs?</title>
      <link>https://community.extremenetworks.com/t5/data-center-slx/shortest-path-with-isls/m-p/20874#M173</link>
      <description>Unfortunately there is no any short-path intelligence with ISL links&lt;BR /&gt;
&lt;BR /&gt;
VCS uses the Fabric Shortest Path First (FSPF) routing protocol to distribute link-state information of all ISLs. FSPF is a Link State Path Selection protocol, similar to OSPF, which is an Interior Gateway Protocol (IGP) widely used in IP networks.&lt;BR /&gt;
&lt;BR /&gt;
FSPF protocol keeps track of the state of the links on all switches in the Ethernet fabric. It also associates a cost with each link. The protocol computes paths from a switch to all the other switches in the fabric, by adding the cost of all the links traversed by the path, and choosing the path that minimizes the cost.&lt;BR /&gt;
&lt;BR /&gt;
FSPF is similar to Layer 3 routing protocols like OSPF. Although it has roots from OSPF, FSPF only defines and implements point-to-point links. In other words, there is no concept of a designated router (DR) and a backup designated router (BDR), areas or summarization, or anything similar like that being managed in FSPF.&lt;BR /&gt;
&lt;BR /&gt;
FSPF forms a single adjacency per fabric trunk.&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;FSPF Link Cost&lt;/B&gt;&lt;BR /&gt;
ECMP in an Ethernet fabric behaves slightly differently from the traditional L3 ECMP. Link cost is a metric value assigned to the transmit (Tx) side of each ISL port. The link cost (metric) value for all interfaces is 500, regardless of bandwidth. A 10 Gbps interface has the same link cost as an 80 Gbps fabric trunk. If a neighbor switch is reachable through several interfaces of various link speeds, all of them are treated as ECMP routes.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 19 Sep 2018 19:55:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-slx/shortest-path-with-isls/m-p/20874#M173</guid>
      <dc:creator>Yulia_Abitbul</dc:creator>
      <dc:date>2018-09-19T19:55:00Z</dc:date>
    </item>
    <item>
      <title>RE: Shortest path with ISLs?</title>
      <link>https://community.extremenetworks.com/t5/data-center-slx/shortest-path-with-isls/m-p/20875#M174</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
as I understand your post the shortest path is used, but due to a fixed link cost the metric is practically just the hop-count between the end points.&lt;BR /&gt;
&lt;BR /&gt;
Thanks,&lt;BR /&gt;
Erik&lt;BR /&gt;</description>
      <pubDate>Wed, 19 Sep 2018 19:55:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-slx/shortest-path-with-isls/m-p/20875#M174</guid>
      <dc:creator>Erik_Auerswald</dc:creator>
      <dc:date>2018-09-19T19:55:00Z</dc:date>
    </item>
    <item>
      <title>RE: Shortest path with ISLs?</title>
      <link>https://community.extremenetworks.com/t5/data-center-slx/shortest-path-with-isls/m-p/20876#M175</link>
      <description>The protocol FSPF (Fabric Shortest Path First) will be used and this will ensure that the path with the least cost will be used.&lt;BR /&gt;
&lt;BR /&gt;
Of all of links should have the same cost therefore the single hop link will always be preferred as it will have the lowest cost.</description>
      <pubDate>Wed, 19 Sep 2018 20:01:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-slx/shortest-path-with-isls/m-p/20876#M175</guid>
      <dc:creator>Mick_Day</dc:creator>
      <dc:date>2018-09-19T20:01:00Z</dc:date>
    </item>
    <item>
      <title>RE: Shortest path with ISLs?</title>
      <link>https://community.extremenetworks.com/t5/data-center-slx/shortest-path-with-isls/m-p/20877#M176</link>
      <description>Correct hop count is effectively the only metric used</description>
      <pubDate>Thu, 20 Sep 2018 15:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-slx/shortest-path-with-isls/m-p/20877#M176</guid>
      <dc:creator>Mick_Day</dc:creator>
      <dc:date>2018-09-20T15:57:00Z</dc:date>
    </item>
  </channel>
</rss>

