<?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 VSP same platform VLAN ID's, but different subnets, on same cluster? in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vsp-same-platform-vlan-id-s-but-different-subnets-on-same/m-p/69166#M850</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;So here is the problem I am trying to solve.&lt;BR /&gt;&lt;BR /&gt;Have a cluster pair in location A and another cluster pair in location B.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;These are being replaced by VSP's and fabric. Each location has a local VLAN 10, but different subnets, say:&lt;BR /&gt;&lt;BR /&gt;
&lt;UL&gt;
&lt;LI&gt;Location A VLAN 10 = 10.10.10.x/24&lt;/LI&gt;
&lt;LI&gt;Location B VLAN 10 = 10.10.20.x/24&lt;/LI&gt;
&lt;/UL&gt;
&lt;BR /&gt;These VLANs can coexist within the fabric by simply putting them into different i-SIDs.&lt;BR /&gt;&lt;BR /&gt;The issue is the design requires that both subnets remain routable should any one location fail.&lt;BR /&gt;&lt;BR /&gt;Although I could create flex-uni's (as an example) to get the VLAN / I-SID where ever I want, I can only create one VLAN 10 platform per cluster i.e:&lt;BR /&gt;&lt;BR /&gt;
&lt;UL&gt;
&lt;LI&gt;Location A houses VLAN 10 as platform VLAN for 10.10.10.x/24&lt;/LI&gt;
&lt;LI&gt;Location B houses VLAN 10 as platform VLAN for 10.10.20.x/24&lt;/LI&gt;
&lt;/UL&gt;
So this would mean if any one location fails, the VLAN 10 / i-sid associated to that location looses its routed interface and is no longer reachable.&lt;BR /&gt;&lt;BR /&gt;So wondering if anyone has any bright ideas, or can maybe point out something obvious I might be missing.&lt;BR /&gt;&lt;BR /&gt;Many thanks in advance.</description>
    <pubDate>Sat, 07 May 2022 00:58:03 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2022-05-07T00:58:03Z</dc:date>
    <item>
      <title>VSP same platform VLAN ID's, but different subnets, on same cluster?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vsp-same-platform-vlan-id-s-but-different-subnets-on-same/m-p/69166#M850</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;So here is the problem I am trying to solve.&lt;BR /&gt;&lt;BR /&gt;Have a cluster pair in location A and another cluster pair in location B.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;These are being replaced by VSP's and fabric. Each location has a local VLAN 10, but different subnets, say:&lt;BR /&gt;&lt;BR /&gt;
&lt;UL&gt;
&lt;LI&gt;Location A VLAN 10 = 10.10.10.x/24&lt;/LI&gt;
&lt;LI&gt;Location B VLAN 10 = 10.10.20.x/24&lt;/LI&gt;
&lt;/UL&gt;
&lt;BR /&gt;These VLANs can coexist within the fabric by simply putting them into different i-SIDs.&lt;BR /&gt;&lt;BR /&gt;The issue is the design requires that both subnets remain routable should any one location fail.&lt;BR /&gt;&lt;BR /&gt;Although I could create flex-uni's (as an example) to get the VLAN / I-SID where ever I want, I can only create one VLAN 10 platform per cluster i.e:&lt;BR /&gt;&lt;BR /&gt;
&lt;UL&gt;
&lt;LI&gt;Location A houses VLAN 10 as platform VLAN for 10.10.10.x/24&lt;/LI&gt;
&lt;LI&gt;Location B houses VLAN 10 as platform VLAN for 10.10.20.x/24&lt;/LI&gt;
&lt;/UL&gt;
So this would mean if any one location fails, the VLAN 10 / i-sid associated to that location looses its routed interface and is no longer reachable.&lt;BR /&gt;&lt;BR /&gt;So wondering if anyone has any bright ideas, or can maybe point out something obvious I might be missing.&lt;BR /&gt;&lt;BR /&gt;Many thanks in advance.</description>
      <pubDate>Sat, 07 May 2022 00:58:03 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vsp-same-platform-vlan-id-s-but-different-subnets-on-same/m-p/69166#M850</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2022-05-07T00:58:03Z</dc:date>
    </item>
  </channel>
</rss>

