<?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 T300 in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/T300/m-p/6469#M1253</link>
    <description>T300 not discovering smartzone controller. TAC mentioned there was a bug with 100.0.0.127 and the AP needed to be upgraded. we upgraded the AP and it is working now. My question, is there a way to find out the range of serial numbers loaded with this code so when the VAR orders the next 100, they don't have to sit there and manually upgrade all 100 and can just make sure that disti doesn't send in that range?</description>
    <pubDate>Tue, 08 Nov 2016 20:09:25 GMT</pubDate>
    <dc:creator>david_thibodeau</dc:creator>
    <dc:date>2016-11-08T20:09:25Z</dc:date>
    <item>
      <title>T300</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/T300/m-p/6469#M1253</link>
      <description>T300 not discovering smartzone controller. TAC mentioned there was a bug with 100.0.0.127 and the AP needed to be upgraded. we upgraded the AP and it is working now. My question, is there a way to find out the range of serial numbers loaded with this code so when the VAR orders the next 100, they don't have to sit there and manually upgrade all 100 and can just make sure that disti doesn't send in that range?</description>
      <pubDate>Tue, 08 Nov 2016 20:09:25 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/T300/m-p/6469#M1253</guid>
      <dc:creator>david_thibodeau</dc:creator>
      <dc:date>2016-11-08T20:09:25Z</dc:date>
    </item>
    <item>
      <title>Re: T300</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/T300/m-p/6470#M1254</link>
      <description>I was not aware David.&amp;nbsp; Did TAC provide a bug ID that I can look up which might have this detail?&lt;BR /&gt;&lt;BR /&gt;
All T300s can load the latest/recommended 104.0.0.0.1347 Solo AP image too, which may likely &lt;BR /&gt;&lt;BR /&gt;
have the fix for the 100.0 problem.&lt;BR /&gt;&lt;BR /&gt;
&lt;A href="https://support.ruckuswireless.com/documents/1134-access-point-104-0-0-0-1347-release-notes" rel="nofollow"&gt;https://support.ruckuswireless.com/documents/1134-access-point-104-0-0-0-1347-release-notes&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
&lt;A href="https://support.ruckuswireless.com/software/1017-zoneflex-solo-access-point-104-0-0-0-1347-ga-software-release" rel="nofollow" target="_blank"&gt;https://support.ruckuswireless.com/software/1017-zoneflex-solo-access-point-104-0-0-0-1347-ga-softwa...&lt;/A&gt;&amp;nbsp;&lt;SPAN&gt;&lt;/SPAN&gt;</description>
      <pubDate>Tue, 08 Nov 2016 22:05:18 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/T300/m-p/6470#M1254</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2016-11-08T22:05:18Z</dc:date>
    </item>
  </channel>
</rss>

