<?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 Routing to a common vlan in a fabric deployment in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/routing-to-a-common-vlan-in-a-fabric-deployment/m-p/74295#M1046</link>
    <description>&lt;P&gt;Can anyone offer me some guidance on the best approach to routing between C-VLAN’s on a vIST core switch cluster. I am replacing a small campus network with a new Fabric implementation with a pair of VSP 7254XSQ’s configured as an vIST cluster for the core.&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;In the old network routing was enabled between trusted VLAN’S on the core, and there was a default route to an interface on the firewall to reach the internet. The firewall has routes for each of the networks on the core and uses one VLAN interface IP as the next hop to send traffic back to the core.&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;I am looking to implement this functionality on the VSP’s, but now instead of a single core switch I have a vIST cluster, and the design goal of maintaining connectivity with one of the core switches down. I have setup all my UNI links to the firewall, IDF and top of rack switches using SMLT, and have enabled RSMLT on VLAN’s where I need redundancy. The part I am unsure about is the right approach to routing. I see inter-vsn routing, and L3VSN’s, and IP Shortcuts, and am not sure what is the best fit here.&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;&lt;BR /&gt; &amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 28 May 2020 03:25:04 GMT</pubDate>
    <dc:creator>David_Nelson</dc:creator>
    <dc:date>2020-05-28T03:25:04Z</dc:date>
    <item>
      <title>Routing to a common vlan in a fabric deployment</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/routing-to-a-common-vlan-in-a-fabric-deployment/m-p/74295#M1046</link>
      <description>&lt;P&gt;Can anyone offer me some guidance on the best approach to routing between C-VLAN’s on a vIST core switch cluster. I am replacing a small campus network with a new Fabric implementation with a pair of VSP 7254XSQ’s configured as an vIST cluster for the core.&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;In the old network routing was enabled between trusted VLAN’S on the core, and there was a default route to an interface on the firewall to reach the internet. The firewall has routes for each of the networks on the core and uses one VLAN interface IP as the next hop to send traffic back to the core.&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;I am looking to implement this functionality on the VSP’s, but now instead of a single core switch I have a vIST cluster, and the design goal of maintaining connectivity with one of the core switches down. I have setup all my UNI links to the firewall, IDF and top of rack switches using SMLT, and have enabled RSMLT on VLAN’s where I need redundancy. The part I am unsure about is the right approach to routing. I see inter-vsn routing, and L3VSN’s, and IP Shortcuts, and am not sure what is the best fit here.&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;&lt;BR /&gt; &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 28 May 2020 03:25:04 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/routing-to-a-common-vlan-in-a-fabric-deployment/m-p/74295#M1046</guid>
      <dc:creator>David_Nelson</dc:creator>
      <dc:date>2020-05-28T03:25:04Z</dc:date>
    </item>
    <item>
      <title>Re: Routing to a common vlan in a fabric deployment</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/routing-to-a-common-vlan-in-a-fabric-deployment/m-p/74296#M1047</link>
      <description>&lt;P&gt;I assume you have a routed VLAN between your existing core to your firewall?&amp;nbsp;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;so I would just treat your Firewall like an IDF.&amp;nbsp;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;VSP1-------VSP2&amp;nbsp;&amp;nbsp; VSPs in viST cluster&amp;nbsp;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;&amp;lt;VLAN to Firewall&amp;gt; /30 or /29&amp;nbsp; enabled with MLT/RSMLT&lt;/P&gt;  &lt;P&gt;.2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .3&lt;/P&gt;  &lt;P&gt;|&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /&lt;/P&gt;  &lt;P&gt;|&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /&lt;/P&gt;  &lt;P&gt;|&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /&lt;/P&gt;  &lt;P&gt;|&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /&lt;/P&gt;  &lt;P&gt;| /&lt;/P&gt;  &lt;P&gt;.1&lt;/P&gt;  &lt;P&gt;[FW]&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;The only thing you might need to do is enabled an LACP enabled RSMLT.&amp;nbsp;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;You then need to replicate the default route(or static routes) on both VSPs.&amp;nbsp;&lt;/P&gt;  &lt;P&gt;0.0.0.0 0.0.0.0&amp;nbsp; next hop XX.XX.XX.1&lt;/P&gt;</description>
      <pubDate>Fri, 29 May 2020 21:32:04 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/routing-to-a-common-vlan-in-a-fabric-deployment/m-p/74296#M1047</guid>
      <dc:creator>EXTR_Paul</dc:creator>
      <dc:date>2020-05-29T21:32:04Z</dc:date>
    </item>
  </channel>
</rss>

