<?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: 3935i AP reverts to 10.01.03.0007 after upgrade to 10.01.04.0011 in ExtremeWireless (Identifi)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-identifi/3935i-ap-reverts-to-10-01-03-0007-after-upgrade-to-10-01-04-0011/m-p/33751#M1210</link>
    <description>Hi Jeremy,&lt;BR /&gt;
&lt;BR /&gt;
the AP resides 2 FW codes.&lt;BR /&gt;
If he reboots 3 times it using his backup file.&lt;BR /&gt;
&lt;BR /&gt;
You can download the 10.01.04 a second time to the AP so that the backup code get overwritten .&lt;BR /&gt;
In this case the AP shouldn't go back to a another FW Version.&lt;BR /&gt;
&lt;BR /&gt;
This issue need to be worked via a GTAC case.&lt;BR /&gt;
&lt;BR /&gt;
But I can make some suggestion in order get more stability in your network.&lt;BR /&gt;
&lt;BR /&gt;
- On radio 2 use b/g/n  ( if not)&lt;BR /&gt;
- On 5Ghz use 40 Mhz Channel Bandwith&lt;BR /&gt;
- Disable in the WLAN Services         Management Frame Protection&lt;BR /&gt;
- disable in QoS flexible client access if using&lt;BR /&gt;
- disable 11k support&lt;BR /&gt;
- disable auto tx power&lt;BR /&gt;
- disable DCS&lt;BR /&gt;
-AP - radio Settings-Advance--&amp;gt; set DTIM to 2 &lt;BR /&gt;
- in the same page --&amp;gt; Multicast Settings  &lt;BR /&gt;
Max % of non-unicast traffic per Beacon period  set to from 100 to 10 !&lt;BR /&gt;
&lt;BR /&gt;
Those are some possibility to get more stability but in the end Engineering need to look to the AP Trace logs for the reason of the reboot.&lt;BR /&gt;
&lt;BR /&gt;
Good luck!&lt;BR /&gt;
&lt;BR /&gt;
UMut&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Wed, 04 May 2016 18:50:00 GMT</pubDate>
    <dc:creator>Umut_Aydin</dc:creator>
    <dc:date>2016-05-04T18:50:00Z</dc:date>
    <item>
      <title>3935i AP reverts to 10.01.03.0007 after upgrade to 10.01.04.0011</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/3935i-ap-reverts-to-10-01-03-0007-after-upgrade-to-10-01-04-0011/m-p/33750#M1209</link>
      <description>3935i AP reverts to 10.01.03.0007 after upgrade to 10.01.04.0011 only if a radio is turned on. If both radios are left in the admin off setting the AP keeps the 10.01.04.0011 firmware (This was an observation I made while trying to find a root cause).  As soon as a radio is turned on the AP reboots 3 times and then reverts back to 10.01.03.0007.&lt;BR /&gt;
&lt;BR /&gt;
I have opened a case with GTAC on 4/28 - it was escalated but I thought someone might have some ideas as to anything I could try to remedy this.  The AP's in question are in production, I haven't had many complaints yet, just like to have things fixed.  The AP's are running the 10.01.03.0007 firmware and using DFS channels that were not introduced until the latest .04 release.&lt;BR /&gt;
&lt;BR /&gt;
More food for thought - I have 3825 AP's running this firmware on this same pair of controllers and they do not revert, they work as they should.&lt;BR /&gt;
&lt;BR /&gt;
Thanks for any help you guys can provide.&lt;BR /&gt;</description>
      <pubDate>Mon, 02 May 2016 20:44:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/3935i-ap-reverts-to-10-01-03-0007-after-upgrade-to-10-01-04-0011/m-p/33750#M1209</guid>
      <dc:creator>Jeremy1</dc:creator>
      <dc:date>2016-05-02T20:44:00Z</dc:date>
    </item>
    <item>
      <title>RE: 3935i AP reverts to 10.01.03.0007 after upgrade to 10.01.04.0011</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/3935i-ap-reverts-to-10-01-03-0007-after-upgrade-to-10-01-04-0011/m-p/33751#M1210</link>
      <description>Hi Jeremy,&lt;BR /&gt;
&lt;BR /&gt;
the AP resides 2 FW codes.&lt;BR /&gt;
If he reboots 3 times it using his backup file.&lt;BR /&gt;
&lt;BR /&gt;
You can download the 10.01.04 a second time to the AP so that the backup code get overwritten .&lt;BR /&gt;
In this case the AP shouldn't go back to a another FW Version.&lt;BR /&gt;
&lt;BR /&gt;
This issue need to be worked via a GTAC case.&lt;BR /&gt;
&lt;BR /&gt;
But I can make some suggestion in order get more stability in your network.&lt;BR /&gt;
&lt;BR /&gt;
- On radio 2 use b/g/n  ( if not)&lt;BR /&gt;
- On 5Ghz use 40 Mhz Channel Bandwith&lt;BR /&gt;
- Disable in the WLAN Services         Management Frame Protection&lt;BR /&gt;
- disable in QoS flexible client access if using&lt;BR /&gt;
- disable 11k support&lt;BR /&gt;
- disable auto tx power&lt;BR /&gt;
- disable DCS&lt;BR /&gt;
-AP - radio Settings-Advance--&amp;gt; set DTIM to 2 &lt;BR /&gt;
- in the same page --&amp;gt; Multicast Settings  &lt;BR /&gt;
Max % of non-unicast traffic per Beacon period  set to from 100 to 10 !&lt;BR /&gt;
&lt;BR /&gt;
Those are some possibility to get more stability but in the end Engineering need to look to the AP Trace logs for the reason of the reboot.&lt;BR /&gt;
&lt;BR /&gt;
Good luck!&lt;BR /&gt;
&lt;BR /&gt;
UMut&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 04 May 2016 18:50:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/3935i-ap-reverts-to-10-01-03-0007-after-upgrade-to-10-01-04-0011/m-p/33751#M1210</guid>
      <dc:creator>Umut_Aydin</dc:creator>
      <dc:date>2016-05-04T18:50:00Z</dc:date>
    </item>
  </channel>
</rss>

