<?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: Update topology to L3 disruptive? in ExtremeWireless (Identifi)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-identifi/update-topology-to-l3-disruptive/m-p/71583#M6877</link>
    <description>&lt;P&gt;It is wonder to get work with latest update which help to run&lt;/P&gt;</description>
    <pubDate>Mon, 06 Apr 2020 19:44:07 GMT</pubDate>
    <dc:creator>Bareiteraw1991</dc:creator>
    <dc:date>2020-04-06T19:44:07Z</dc:date>
    <item>
      <title>Update topology to L3 disruptive?</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/update-topology-to-l3-disruptive/m-p/71578#M6872</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt; &lt;P&gt;Very quick question. I’ve got to make a change to a topology to use L3. Predominantly because we are also going to use that same topology for a new&amp;nbsp;internal captive portal.&lt;/P&gt; &lt;P&gt;Example below:&lt;/P&gt; &lt;FIGURE&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ca813455348a47c0a69ebd9c450d9019_a9a7f224-1e46-4297-98c3-292c60b3fc69.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/678i60EBCD35D4DAA764/image-size/large?v=v2&amp;amp;px=999" role="button" title="ca813455348a47c0a69ebd9c450d9019_a9a7f224-1e46-4297-98c3-292c60b3fc69.png" alt="ca813455348a47c0a69ebd9c450d9019_a9a7f224-1e46-4297-98c3-292c60b3fc69.png" /&gt;&lt;/span&gt;&lt;/FIGURE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;That topology is already in use on another SSID.&lt;/P&gt; &lt;P&gt;Questions is, will making this L3 and applying an IP address&amp;nbsp;cause any disruption?&lt;/P&gt; &lt;P&gt;Many thanks in advance.&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Mar 2020 21:09:58 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/update-topology-to-l3-disruptive/m-p/71578#M6872</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2020-03-30T21:09:58Z</dc:date>
    </item>
    <item>
      <title>Re: Update topology to L3 disruptive?</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/update-topology-to-l3-disruptive/m-p/71579#M6873</link>
      <description>&lt;P&gt;Martin,&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;Doing so, you’ll add a L3 interface to your EWC.&lt;/P&gt; &lt;P&gt;Possible impacts are:&lt;/P&gt; &lt;UL&gt;&lt;LI&gt;routing traffic that is not supposed to be &lt;UL&gt;&lt;LI&gt;routing has to be double checked&lt;/LI&gt; &lt;/UL&gt;&lt;/LI&gt; &lt;LI&gt;asymmetric routing if there is already another default gateway (I suppose there is) &lt;UL&gt;&lt;LI&gt;routing has to be double checked&lt;/LI&gt; &lt;/UL&gt;&lt;/LI&gt; &lt;LI&gt;L3 loop (risk seems very very low here) &lt;UL&gt;&lt;LI&gt;routing has to be double checked&lt;/LI&gt; &lt;/UL&gt;&lt;/LI&gt; &lt;/UL&gt;&lt;P&gt;As conclusion, routing has to be double checked &lt;span class="lia-inline-image-display-wrapper" image-alt="a37faf7f05cf4be8963227094259b20a_1f601.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/3739iEDA933C07E2529E9/image-size/large?v=v2&amp;amp;px=999" role="button" title="a37faf7f05cf4be8963227094259b20a_1f601.png" alt="a37faf7f05cf4be8963227094259b20a_1f601.png" /&gt;&lt;/span&gt;&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;Mig&lt;/P&gt;</description>
      <pubDate>Tue, 31 Mar 2020 02:59:50 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/update-topology-to-l3-disruptive/m-p/71579#M6873</guid>
      <dc:creator>Miguel-Angel_RO</dc:creator>
      <dc:date>2020-03-31T02:59:50Z</dc:date>
    </item>
    <item>
      <title>Re: Update topology to L3 disruptive?</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/update-topology-to-l3-disruptive/m-p/71580#M6874</link>
      <description>&lt;P&gt;Hi Mig,&lt;/P&gt; &lt;P&gt;Thank you for getting back to me, really appreciate it.&lt;/P&gt; &lt;P&gt;Hoping you can help me understand,&amp;nbsp;help me make better choices.&lt;/P&gt; &lt;P&gt;The VLAN this topology belongs to already has a default gateway that is routing traffic as you suspect.&lt;/P&gt; &lt;P&gt;Any device that gets an IP address on this VLAN will maintain that information, so effectively all will stay the same, the DG will be same router.&lt;/P&gt; &lt;P&gt;What I’m not understanding is why and how giving the EWC topology an IP address would cause those effects.&lt;/P&gt; &lt;P&gt;Routing will effectively still point to the same DG i.e. 192.168.0.1. /24 is the mask. The topology L3 interface will get an IP address of 192.168.0.250.&lt;/P&gt; &lt;P&gt;Many thanks&lt;/P&gt; &lt;P&gt;Martin&lt;/P&gt;</description>
      <pubDate>Tue, 31 Mar 2020 04:24:53 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/update-topology-to-l3-disruptive/m-p/71580#M6874</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2020-03-31T04:24:53Z</dc:date>
    </item>
    <item>
      <title>Re: Update topology to L3 disruptive?</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/update-topology-to-l3-disruptive/m-p/71581#M6875</link>
      <description>&lt;P&gt;Martin,&lt;/P&gt; &lt;P&gt;You won’t probably get any issue but there is to few info to be sure.&lt;/P&gt; &lt;P&gt;The EWC is acting as a router so if you add a L3 interface he will start to route this specific VLAN.&lt;/P&gt; &lt;P&gt;If you have other L3 interfaces, you can route them together in the EWC without going through the core.&lt;/P&gt; &lt;P&gt;All is conditional as I don’t know your setup/design (use OSPF on the EWC?, how many L3 interfaces?, detailed routing table, etc.)&lt;/P&gt; &lt;P&gt;Mig&lt;/P&gt;</description>
      <pubDate>Tue, 31 Mar 2020 13:23:03 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/update-topology-to-l3-disruptive/m-p/71581#M6875</guid>
      <dc:creator>Miguel-Angel_RO</dc:creator>
      <dc:date>2020-03-31T13:23:03Z</dc:date>
    </item>
    <item>
      <title>Re: Update topology to L3 disruptive?</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/update-topology-to-l3-disruptive/m-p/71582#M6876</link>
      <description>&lt;P&gt;Hi Mig,&lt;/P&gt; &lt;P&gt;Thanks for getting back.&lt;/P&gt; &lt;P&gt;The EWC doesn’t currently use any other L3 interface, so going to take the plunge and enable this.&lt;/P&gt; &lt;P&gt;Will report back if all goes well.&lt;/P&gt; &lt;P&gt;Many thanks again.&lt;/P&gt;</description>
      <pubDate>Tue, 31 Mar 2020 13:50:03 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/update-topology-to-l3-disruptive/m-p/71582#M6876</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2020-03-31T13:50:03Z</dc:date>
    </item>
    <item>
      <title>Re: Update topology to L3 disruptive?</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/update-topology-to-l3-disruptive/m-p/71583#M6877</link>
      <description>&lt;P&gt;It is wonder to get work with latest update which help to run&lt;/P&gt;</description>
      <pubDate>Mon, 06 Apr 2020 19:44:07 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/update-topology-to-l3-disruptive/m-p/71583#M6877</guid>
      <dc:creator>Bareiteraw1991</dc:creator>
      <dc:date>2020-04-06T19:44:07Z</dc:date>
    </item>
  </channel>
</rss>

