<?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 IdentiFi Wireless Controller Advice regarding Upgrading Between Firmware Lines in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/identifi-wireless-controller-advice-regarding-upgrading-between/m-p/45839#M353</link>
    <description>Article ID: 15070 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
IdentiFi / Enterasys / HiPath Wireless Controller&lt;BR /&gt;
C20, C20N, C25, C35, C2400, C4110, C5110, C5210, CRBT-8110, CRBT-8210, V2110 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Discussion&lt;/B&gt;&lt;BR /&gt;
It is always recommended that, prior to upgrading hardware, the user read the product &lt;A href="https://extranet.enterasys.com/downloads/Pages/WirelessControllers.aspx" target="_blank" rel="nofollow noreferrer noopener"&gt;release notes&lt;/A&gt; for any background or advice it has to offer.This is especially true when upgrading between firmware lines, for example from somewhere within the V6R1 line to the 8.31 line. &lt;BR /&gt;
&lt;BR /&gt;
One item which is listed in the firmware "INSTALLATION INFORMATION" section looks something like: &lt;BR /&gt;
&lt;B&gt;Note:&lt;/B&gt; The minimum system software version is &lt;I&gt;xx.xx.xx.xxxx&lt;/I&gt; to upgrade to this software version. &lt;BR /&gt;
&lt;BR /&gt;
If the user violates this guideline by upgrading past too many versions in a single operation, what may result is somewhat unpredictable. The upgrade operation could fail, or it could succeed but result in device misbehavior either immediately or over time. For this reason, it is strongly advised to heed this guideline and, as necessary, perform a staged upgrade to reach the desired firmware version. &lt;BR /&gt;
&lt;BR /&gt;
Here is a summary of such information culled from a broad set of release notes:   Minimum required                 to upgrade to within this range&lt;BR /&gt;
 &lt;BR /&gt;
    9.21.18.0001          -&amp;gt;         10.41.01.0080 -10.41.XX.XXXX&lt;BR /&gt;
    9.21.01.0179          -&amp;gt;         10.01.01.0001 -10.31.XX.XXXX&lt;BR /&gt;
    8.32.01.0035          -&amp;gt;          9.21.01.0179 - 9.21.XX.XXXX&lt;BR /&gt;
    8.32.01.0035          -&amp;gt;          9.15.01.0121 - 9.15.XX.XXXX&lt;BR /&gt;
    8.32.01.0035          -&amp;gt;          9.12.01.0067 - 9.12.04.0003&lt;BR /&gt;
    8.21.12.0006          -&amp;gt;          9.01.01.0228 - 9.01.03.0008&lt;BR /&gt;
    8.01.01.0251          -&amp;gt;          8.32.01.0035 - 8.32.16.0001&lt;BR /&gt;
    8.01.01.0251          -&amp;gt;          8.31.01.0189 - 8.31.03.0011&lt;BR /&gt;
    8.01.01.0251          -&amp;gt;          8.21.01.0198 - 8.21.13.0002&lt;BR /&gt;
    7.41.07.0007          -&amp;gt;          8.11.01.0161 - 8.11.11.0003&lt;BR /&gt;
    7.31.06.0007          -&amp;gt;          8.01.01.0251 - 8.01.09.0002&lt;BR /&gt;
    V6R1.10507 (V6R1FR5)  -&amp;gt;          7.41.01.0192 - 7.41.12.0001&lt;BR /&gt;
    V6R1.10507 (V6R1FR5)  -&amp;gt;          7.31.01.0138 - 7.31.08.0005&lt;BR /&gt;
    V6R1.10507 (V6R1FR5)  -&amp;gt;          7.21.01.0140 - 7.21.06.0005&lt;BR /&gt;
    V6R1.10507 (V6R1FR5)  -&amp;gt;          7.11.00.0087 - 7.11.02.0004&lt;BR /&gt;
    V6R1.10507 (V6R1FR5)  -&amp;gt;          7.00.00.0183 - 7.00.01.0004&lt;BR /&gt;
    V5R0.100&lt;I&gt;xx&lt;/I&gt; (V5R0FR0)  -&amp;gt;  V6R1.10029 (V6R1FR0) - V6R1.10901 (V6R1FR9)&lt;BR /&gt;
    V5R0.100&lt;I&gt;xx&lt;/I&gt; (V5R0FR0)  -&amp;gt;  V6R0.10019 (V6R0FR0) - V6R0.10107 (V6R0FR1)&lt;BR /&gt;
    V5R0.100&lt;I&gt;xx&lt;/I&gt; (V5R0FR0)  -&amp;gt;  V5R3.10034 (V5R3FR0) - V5R3.10700 (V5R3FR7)&lt;BR /&gt;
So for example, if a C20 controller is running V6R1.10029 and it needs an upgrade to 8.21.08.0005, you would&lt;UL&gt;upgrade from V6R1.10029 to V6R1.10507; 
then upgrade from V6R1.10507 to 7.41.12.0001; 
then upgrade from 7.41.12.0001 to 8.11.11.0003; 
then upgrade from 8.11.11.0003 to 8.21.08.0005.&lt;/UL&gt;
On the other hand if starting from 8.01.06.0010, you would simply upgrade to 8.21.08.0005 in a single operation. &lt;BR /&gt;
&lt;BR /&gt;
A second point to understand when considering upgrade (and reviewing release notes) is that some controller (and Access Point!) models are only supported in a subset of the released firmware lines. In general:&lt;UL&gt;10.01 supports C25, C35, C4110, C5110, C5210, V2110; 
 9.21 supports C25, C35, C4110, C5110, C5210, V2110; 
 9.15 supports C25, C4110, C5110, C5210, V2110; 
 9.12 supports C25, C4110, C5110, C5210, V2110; 
 9.01 supports C25, C4110, C5110, C5210, V2110; 
 8.31 supports C20, C25, C4110, C5110, C5210, V2110; 
 8.21 supports C20, C25, C4110, C5110, C5210, V2110; 
 8.11 supports C20, C25, C4110, C5110, V2110; 
 8.01 supports C20, C25, C4110, C5110, V2110; 
 7.41 supports C20, C20N, C25, C2400, C4110, C5110, CRBT-8110, CRB-8210; 
 7.31 supports C20, C20N, C2400, C4110, C5110, CRBT-8110, CRBT-8210; 
 7.21 supports C20, C20N, C2400, C4110, C5110, CRBT-8110, CRBT-8210; 
 7.11 supports C20, C20N, C2400, C4110, C5110, CRBT-8110, CRBT-8210; 
 7.00 supports C20, C20N, C2400, C4110, C5110, CRBT-8110, CRBT-8210; 
 V6R1 supports C20, C20N, C2400, C4110, C5110, CRBT-8110, CRBT-8210; 
 V6R0 supports C20, C20N, C2400, C5110, CRBT-8110, CRBT-8210; and 
 V5R3 supports C20, C20N, C2400 (but not all versions for all products).&lt;/UL&gt;
In the V6R1.10029 to 8.21.08.0005 example used above, even the recommended four-stage upgrade would not be successful for a C2400, because that controller model is not supported past 7.41.12.0001 (upgrade stage 2). Here, simply avoid trying to upgrade a controller higher - or lower - than is supported. &lt;BR /&gt;
&lt;BR /&gt;
All of this is Functions as Designed (FAD).</description>
    <pubDate>Tue, 12 Nov 2013 22:19:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-11-12T22:19:00Z</dc:date>
    <item>
      <title>IdentiFi Wireless Controller Advice regarding Upgrading Between Firmware Lines</title>
      <link>https://community.extremenetworks.com/t5/faqs/identifi-wireless-controller-advice-regarding-upgrading-between/m-p/45839#M353</link>
      <description>Article ID: 15070 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
IdentiFi / Enterasys / HiPath Wireless Controller&lt;BR /&gt;
C20, C20N, C25, C35, C2400, C4110, C5110, C5210, CRBT-8110, CRBT-8210, V2110 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Discussion&lt;/B&gt;&lt;BR /&gt;
It is always recommended that, prior to upgrading hardware, the user read the product &lt;A href="https://extranet.enterasys.com/downloads/Pages/WirelessControllers.aspx" target="_blank" rel="nofollow noreferrer noopener"&gt;release notes&lt;/A&gt; for any background or advice it has to offer.This is especially true when upgrading between firmware lines, for example from somewhere within the V6R1 line to the 8.31 line. &lt;BR /&gt;
&lt;BR /&gt;
One item which is listed in the firmware "INSTALLATION INFORMATION" section looks something like: &lt;BR /&gt;
&lt;B&gt;Note:&lt;/B&gt; The minimum system software version is &lt;I&gt;xx.xx.xx.xxxx&lt;/I&gt; to upgrade to this software version. &lt;BR /&gt;
&lt;BR /&gt;
If the user violates this guideline by upgrading past too many versions in a single operation, what may result is somewhat unpredictable. The upgrade operation could fail, or it could succeed but result in device misbehavior either immediately or over time. For this reason, it is strongly advised to heed this guideline and, as necessary, perform a staged upgrade to reach the desired firmware version. &lt;BR /&gt;
&lt;BR /&gt;
Here is a summary of such information culled from a broad set of release notes:   Minimum required                 to upgrade to within this range&lt;BR /&gt;
 &lt;BR /&gt;
    9.21.18.0001          -&amp;gt;         10.41.01.0080 -10.41.XX.XXXX&lt;BR /&gt;
    9.21.01.0179          -&amp;gt;         10.01.01.0001 -10.31.XX.XXXX&lt;BR /&gt;
    8.32.01.0035          -&amp;gt;          9.21.01.0179 - 9.21.XX.XXXX&lt;BR /&gt;
    8.32.01.0035          -&amp;gt;          9.15.01.0121 - 9.15.XX.XXXX&lt;BR /&gt;
    8.32.01.0035          -&amp;gt;          9.12.01.0067 - 9.12.04.0003&lt;BR /&gt;
    8.21.12.0006          -&amp;gt;          9.01.01.0228 - 9.01.03.0008&lt;BR /&gt;
    8.01.01.0251          -&amp;gt;          8.32.01.0035 - 8.32.16.0001&lt;BR /&gt;
    8.01.01.0251          -&amp;gt;          8.31.01.0189 - 8.31.03.0011&lt;BR /&gt;
    8.01.01.0251          -&amp;gt;          8.21.01.0198 - 8.21.13.0002&lt;BR /&gt;
    7.41.07.0007          -&amp;gt;          8.11.01.0161 - 8.11.11.0003&lt;BR /&gt;
    7.31.06.0007          -&amp;gt;          8.01.01.0251 - 8.01.09.0002&lt;BR /&gt;
    V6R1.10507 (V6R1FR5)  -&amp;gt;          7.41.01.0192 - 7.41.12.0001&lt;BR /&gt;
    V6R1.10507 (V6R1FR5)  -&amp;gt;          7.31.01.0138 - 7.31.08.0005&lt;BR /&gt;
    V6R1.10507 (V6R1FR5)  -&amp;gt;          7.21.01.0140 - 7.21.06.0005&lt;BR /&gt;
    V6R1.10507 (V6R1FR5)  -&amp;gt;          7.11.00.0087 - 7.11.02.0004&lt;BR /&gt;
    V6R1.10507 (V6R1FR5)  -&amp;gt;          7.00.00.0183 - 7.00.01.0004&lt;BR /&gt;
    V5R0.100&lt;I&gt;xx&lt;/I&gt; (V5R0FR0)  -&amp;gt;  V6R1.10029 (V6R1FR0) - V6R1.10901 (V6R1FR9)&lt;BR /&gt;
    V5R0.100&lt;I&gt;xx&lt;/I&gt; (V5R0FR0)  -&amp;gt;  V6R0.10019 (V6R0FR0) - V6R0.10107 (V6R0FR1)&lt;BR /&gt;
    V5R0.100&lt;I&gt;xx&lt;/I&gt; (V5R0FR0)  -&amp;gt;  V5R3.10034 (V5R3FR0) - V5R3.10700 (V5R3FR7)&lt;BR /&gt;
So for example, if a C20 controller is running V6R1.10029 and it needs an upgrade to 8.21.08.0005, you would&lt;UL&gt;upgrade from V6R1.10029 to V6R1.10507; 
then upgrade from V6R1.10507 to 7.41.12.0001; 
then upgrade from 7.41.12.0001 to 8.11.11.0003; 
then upgrade from 8.11.11.0003 to 8.21.08.0005.&lt;/UL&gt;
On the other hand if starting from 8.01.06.0010, you would simply upgrade to 8.21.08.0005 in a single operation. &lt;BR /&gt;
&lt;BR /&gt;
A second point to understand when considering upgrade (and reviewing release notes) is that some controller (and Access Point!) models are only supported in a subset of the released firmware lines. In general:&lt;UL&gt;10.01 supports C25, C35, C4110, C5110, C5210, V2110; 
 9.21 supports C25, C35, C4110, C5110, C5210, V2110; 
 9.15 supports C25, C4110, C5110, C5210, V2110; 
 9.12 supports C25, C4110, C5110, C5210, V2110; 
 9.01 supports C25, C4110, C5110, C5210, V2110; 
 8.31 supports C20, C25, C4110, C5110, C5210, V2110; 
 8.21 supports C20, C25, C4110, C5110, C5210, V2110; 
 8.11 supports C20, C25, C4110, C5110, V2110; 
 8.01 supports C20, C25, C4110, C5110, V2110; 
 7.41 supports C20, C20N, C25, C2400, C4110, C5110, CRBT-8110, CRB-8210; 
 7.31 supports C20, C20N, C2400, C4110, C5110, CRBT-8110, CRBT-8210; 
 7.21 supports C20, C20N, C2400, C4110, C5110, CRBT-8110, CRBT-8210; 
 7.11 supports C20, C20N, C2400, C4110, C5110, CRBT-8110, CRBT-8210; 
 7.00 supports C20, C20N, C2400, C4110, C5110, CRBT-8110, CRBT-8210; 
 V6R1 supports C20, C20N, C2400, C4110, C5110, CRBT-8110, CRBT-8210; 
 V6R0 supports C20, C20N, C2400, C5110, CRBT-8110, CRBT-8210; and 
 V5R3 supports C20, C20N, C2400 (but not all versions for all products).&lt;/UL&gt;
In the V6R1.10029 to 8.21.08.0005 example used above, even the recommended four-stage upgrade would not be successful for a C2400, because that controller model is not supported past 7.41.12.0001 (upgrade stage 2). Here, simply avoid trying to upgrade a controller higher - or lower - than is supported. &lt;BR /&gt;
&lt;BR /&gt;
All of this is Functions as Designed (FAD).</description>
      <pubDate>Tue, 12 Nov 2013 22:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/identifi-wireless-controller-advice-regarding-upgrading-between/m-p/45839#M353</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-11-12T22:19:00Z</dc:date>
    </item>
  </channel>
</rss>

