<?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: New wireless AP's join the secondary (availability) controller? in ExtremeWireless (Identifi)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-identifi/new-wireless-ap-s-join-the-secondary-availability-controller/m-p/30981#M592</link>
    <description>How do the APs dicover the controller - same subnet, DHCP option, DNS.&lt;BR /&gt;
&lt;BR /&gt;
I'd just disable AP registration on #2 and all should register on #1.&lt;BR /&gt;
GUI &amp;gt; AP &amp;gt; Global &amp;gt; Registration &amp;gt; Security Mode &amp;gt; Allow only approved Wireless APs to connect&lt;BR /&gt;
&lt;BR /&gt;
Cheers,&lt;BR /&gt;
Ron</description>
    <pubDate>Fri, 19 May 2017 18:06:00 GMT</pubDate>
    <dc:creator>Ronald_Dvorak</dc:creator>
    <dc:date>2017-05-19T18:06:00Z</dc:date>
    <item>
      <title>New wireless AP's join the secondary (availability) controller?</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/new-wireless-ap-s-join-the-secondary-availability-controller/m-p/30980#M591</link>
      <description>It seems like ever since I created an availability pair, any new AP's I add are being added to the secondary controller.&lt;BR /&gt;
&lt;BR /&gt;
Perhaps I shouldn't care. Because it works okay. But I would rather keep all of my AP's on one controller unless there is a situation where they need to shift to the secondary controller.&lt;BR /&gt;
&lt;BR /&gt;
Am I doing something wrong that they are finding the secondary and joining it?&lt;BR /&gt;
&lt;BR /&gt;
AP's are 3825's and the firmware is 10.31.01.0048 &lt;BR /&gt;</description>
      <pubDate>Fri, 19 May 2017 18:00:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/new-wireless-ap-s-join-the-secondary-availability-controller/m-p/30980#M591</guid>
      <dc:creator>Steve_Ballantyn</dc:creator>
      <dc:date>2017-05-19T18:00:00Z</dc:date>
    </item>
    <item>
      <title>RE: New wireless AP's join the secondary (availability) controller?</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/new-wireless-ap-s-join-the-secondary-availability-controller/m-p/30981#M592</link>
      <description>How do the APs dicover the controller - same subnet, DHCP option, DNS.&lt;BR /&gt;
&lt;BR /&gt;
I'd just disable AP registration on #2 and all should register on #1.&lt;BR /&gt;
GUI &amp;gt; AP &amp;gt; Global &amp;gt; Registration &amp;gt; Security Mode &amp;gt; Allow only approved Wireless APs to connect&lt;BR /&gt;
&lt;BR /&gt;
Cheers,&lt;BR /&gt;
Ron</description>
      <pubDate>Fri, 19 May 2017 18:06:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/new-wireless-ap-s-join-the-secondary-availability-controller/m-p/30981#M592</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2017-05-19T18:06:00Z</dc:date>
    </item>
    <item>
      <title>RE: New wireless AP's join the secondary (availability) controller?</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/new-wireless-ap-s-join-the-secondary-availability-controller/m-p/30982#M593</link>
      <description>Hey, thanks! That's an easy solution I hadn't thought of.&lt;BR /&gt;</description>
      <pubDate>Fri, 19 May 2017 18:06:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/new-wireless-ap-s-join-the-secondary-availability-controller/m-p/30982#M593</guid>
      <dc:creator>Steve_Ballantyn</dc:creator>
      <dc:date>2017-05-19T18:06:00Z</dc:date>
    </item>
    <item>
      <title>RE: New wireless AP's join the secondary (availability) controller?</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/new-wireless-ap-s-join-the-secondary-availability-controller/m-p/30983#M594</link>
      <description>Also the move function is working great in case the AP is on the wrong controller.&lt;BR /&gt;
&lt;BR /&gt;
On #2 go to &amp;gt; AP &amp;gt; APs &amp;gt; set checkmark on the AP that you'd like to move &amp;gt; Actions &amp;gt; approve as foreign.&lt;BR /&gt;
&lt;BR /&gt;
It will take only a moment and the AP is now local to #1.</description>
      <pubDate>Fri, 19 May 2017 18:09:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/new-wireless-ap-s-join-the-secondary-availability-controller/m-p/30983#M594</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2017-05-19T18:09:00Z</dc:date>
    </item>
    <item>
      <title>RE: New wireless AP's join the secondary (availability) controller?</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/new-wireless-ap-s-join-the-secondary-availability-controller/m-p/30984#M595</link>
      <description>I was actually trying to take that route and it didn't seem to be working. But I was doing it backwards. I was on the second controller, and was approving it as "local". I just had the context wrong.   Approve as foreign moved it right away.&lt;BR /&gt;</description>
      <pubDate>Fri, 19 May 2017 18:09:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/new-wireless-ap-s-join-the-secondary-availability-controller/m-p/30984#M595</guid>
      <dc:creator>Steve_Ballantyn</dc:creator>
      <dc:date>2017-05-19T18:09:00Z</dc:date>
    </item>
  </channel>
</rss>

