<?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 I/G/C/B/A-Series f/w 6.51/6.61 Upgrade considerations in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/i-g-c-b-a-series-f-w-6-51-6-61-upgrade-considerations/m-p/48052#M502</link>
    <description>Article ID: 14480 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
I-Series, firmware 6.61.02.0007 and higher&lt;BR /&gt;
G-Series, firmware 6.61.02.0007 and higher&lt;BR /&gt;
C5-Series, firmware 6.51.02.0018 and higher&lt;BR /&gt;
C3-Series, firmware 6.61.02.0007 and higher&lt;BR /&gt;
B5-Series, firmware 6.51.02.0018 and higher&lt;BR /&gt;
B3-Series, firmware 6.61.02.0007 and higher&lt;BR /&gt;
A4-Series, firmware 6.61.02.0007 and higher &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Discussion&lt;/B&gt;&lt;BR /&gt;
When considering a firmware upgrade, it is always good practice to review the release notes. This is particularly true for customers who will be upgrading one of the above-stated products from pre-6.51 to 6.51+, or who will be back-reving one of the above-stated products from 6.51+ to pre-6.51. &lt;BR /&gt;
Note: Since the 6.51 firmware line does apply to the C5/B5 but does not apply to the I/G/C3/B3/A4, the simplest way to consider this issue for all products is to use the "pre-6.51" (= 1.0&lt;I&gt;x&lt;/I&gt;, 6.03, 6.41, 6.42, etc) and "6.51+" (= 6.51, 6.61, 6.71, etc) markers generally cited in this document to designate the cutoff point of concern. &lt;BR /&gt;
&lt;BR /&gt;
C5/B5 firmware 6.51.02.0018 &lt;A href="http://extranet.enterasys.com/downloads/" target="_blank" rel="nofollow noreferrer noopener"&gt;release notes&lt;/A&gt; state, in the 'Installation and Configuration Notes' section:&lt;BR /&gt;
WARNING: Configuration files containing a login banner may suspend&lt;BR /&gt;
operation of images prior to 6.51. This state can only be corrected by&lt;BR /&gt;
clearing the configuration through the boot PROM. Use extreme caution&lt;BR /&gt;
when using a configuration file. Login banners will automatically be&lt;BR /&gt;
removed from the configuration when back revving to pre-6.51 images.&lt;BR /&gt;
 &lt;BR /&gt;
Note: As a best practice, Enterasys recommends that prior to upgrading&lt;BR /&gt;
or downgrading the firmware on your switch, you save the existing&lt;BR /&gt;
working configuration of the system by using the show config outfile&lt;BR /&gt;
configs/ command. Please note that you will need a copy of&lt;BR /&gt;
your previous configuration if you need to back-rev from 6.51.xx.xxxx&lt;BR /&gt;
to the previous firmware version.&lt;BR /&gt;
 &lt;BR /&gt;
To download the new software to a stack of switches, simply follow the&lt;BR /&gt;
instructions to upgrade a switch with new software. The system will&lt;BR /&gt;
automatically download the new software to all the members in the stack&lt;BR /&gt;
controlled by that stack manager.&lt;BR /&gt;
C5/B5 firmware 6.51.02.0018 &lt;A href="http://extranet.enterasys.com/downloads/" target="_blank" rel="nofollow noreferrer noopener"&gt;release notes&lt;/A&gt; state, in the 'Known Issues in 6.51.02.0018' section: &lt;BR /&gt;
Setting the security profile to c2 changes certain system defaults&lt;BR /&gt;
including encryption algorithms used for storing passwords, shared&lt;BR /&gt;
secrets, and routing keys. As a result, configuration files for devices&lt;BR /&gt;
operating in different security profiles are not fully compatible and&lt;BR /&gt;
may result in some loss of configuration if loaded.&lt;BR /&gt;
 &lt;BR /&gt;
The 6.51 image will not stack with earlier versions of code, due to the&lt;BR /&gt;
use of VLAN 4094. When adding a new unit to an existing stack running&lt;BR /&gt;
6.51 or higher, the unit will (first) need to be running 6.51 or higher.&lt;BR /&gt;
When adding a new unit to an existing stack running a pre-6.51 image,&lt;BR /&gt;
the new unit will (first) need to be downgraded to that pre-6.51 image.&lt;BR /&gt;
Equivalent information is contained in C3/B3/A4 firmware 6.61.02.0007 release notes, in reference to upgrade from pre-6.61 to 6.61+ firmware, or back-rev from 6.61+ to pre-6.61 firmware. &lt;BR /&gt;
&lt;BR /&gt;
Finally; for the I, G, C3, and B3-Series products, these guidelines assume that the upgrade starting point is somewhere in the 6.42 firmware line (&lt;A href="http://bit.ly/I7AmoT" target="_blank" rel="nofollow noreferrer noopener"&gt;14711&lt;/A&gt;). &lt;BR /&gt;
&lt;BR /&gt;
In short:&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;Before upgrading from pre-6.51 to 6.51+; you should save a copy of the pre-6.51 configuration (&lt;A href="http://bit.ly/1nz1lHy" target="_blank" rel="nofollow noreferrer noopener"&gt;5623&lt;/A&gt;), which will be needed if you ever decide to back-rev to pre-6.51. 
&lt;/LI&gt;&lt;LI&gt;When upgrading from pre-6.51 to 6.51+; with the exception of what is stated in &lt;A href="http://bit.ly/I7AmoT" target="_blank" rel="nofollow noreferrer noopener"&gt;14711&lt;/A&gt; the system will make the necessary configuration changes, so the standard upgrade procedure (&lt;A href="http://bit.ly/WhsfvZ" target="_blank" rel="nofollow noreferrer noopener"&gt;5605&lt;/A&gt;) applies. 
&lt;/LI&gt;&lt;LI&gt;After the upgrade, as desired and as applicable reload a saved &lt;I&gt;6.51+ &lt;/I&gt;configuration (&lt;A href="http://bit.ly/1nz1lHy" target="_blank" rel="nofollow noreferrer noopener"&gt;5623&lt;/A&gt;).&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt; 
&lt;LI&gt;Before back-reving from 6.51+ to pre-6.51; you should save a copy of the 6.51+ configuration (&lt;A href="http://bit.ly/1nz1lHy" target="_blank" rel="nofollow noreferrer noopener"&gt;5623&lt;/A&gt;), which could be handy if you ever decide to re-upgrade to 6.51+. 
&lt;/LI&gt;&lt;LI&gt;When back-reving from 6.51+ to pre-6.51; first clear the majority of the configuration ('clear config', &lt;A href="http://bit.ly/1cDGAW0" target="_blank" rel="nofollow noreferrer noopener"&gt;5628&lt;/A&gt;), then use the standard procedure (&lt;A href="http://bit.ly/WhsfvZ" target="_blank" rel="nofollow noreferrer noopener"&gt;5605&lt;/A&gt;). 
&lt;/LI&gt;&lt;LI&gt;After the back-rev, as desired and as applicable reload a saved &lt;I&gt;pre-6.51 &lt;/I&gt;configuration (&lt;A href="http://bit.ly/1nz1lHy" target="_blank" rel="nofollow noreferrer noopener"&gt;5623&lt;/A&gt;).&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt; 
&lt;LI&gt;Ensure that any switches to be added to a stack (&lt;A href="http://bit.ly/1BetvzD" target="_blank" rel="nofollow noreferrer noopener"&gt;7086&lt;/A&gt;) already match the stack in their pre-6.51 vs 6.51+ firmware status, before being added to the stack. Otherwise, the condition will result in a "Code Version Mismatch" error (&lt;A href="http://bit.ly/18qG1jv" target="_blank" rel="nofollow noreferrer noopener"&gt;7326&lt;/A&gt;) that cannot be corrected by an attempted direct copy operation ("set switch copy-fw...') from the manager. Note that the I/G-Series are not stackable products.&lt;/LI&gt;&lt;/UL&gt;See also: &lt;A href="http://bit.ly/I6jFtu" target="_blank" rel="nofollow noreferrer noopener"&gt;14942&lt;/A&gt;.&lt;BR /&gt;</description>
    <pubDate>Thu, 05 Sep 2013 06:02:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-09-05T06:02:00Z</dc:date>
    <item>
      <title>I/G/C/B/A-Series f/w 6.51/6.61 Upgrade considerations</title>
      <link>https://community.extremenetworks.com/t5/faqs/i-g-c-b-a-series-f-w-6-51-6-61-upgrade-considerations/m-p/48052#M502</link>
      <description>Article ID: 14480 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
I-Series, firmware 6.61.02.0007 and higher&lt;BR /&gt;
G-Series, firmware 6.61.02.0007 and higher&lt;BR /&gt;
C5-Series, firmware 6.51.02.0018 and higher&lt;BR /&gt;
C3-Series, firmware 6.61.02.0007 and higher&lt;BR /&gt;
B5-Series, firmware 6.51.02.0018 and higher&lt;BR /&gt;
B3-Series, firmware 6.61.02.0007 and higher&lt;BR /&gt;
A4-Series, firmware 6.61.02.0007 and higher &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Discussion&lt;/B&gt;&lt;BR /&gt;
When considering a firmware upgrade, it is always good practice to review the release notes. This is particularly true for customers who will be upgrading one of the above-stated products from pre-6.51 to 6.51+, or who will be back-reving one of the above-stated products from 6.51+ to pre-6.51. &lt;BR /&gt;
Note: Since the 6.51 firmware line does apply to the C5/B5 but does not apply to the I/G/C3/B3/A4, the simplest way to consider this issue for all products is to use the "pre-6.51" (= 1.0&lt;I&gt;x&lt;/I&gt;, 6.03, 6.41, 6.42, etc) and "6.51+" (= 6.51, 6.61, 6.71, etc) markers generally cited in this document to designate the cutoff point of concern. &lt;BR /&gt;
&lt;BR /&gt;
C5/B5 firmware 6.51.02.0018 &lt;A href="http://extranet.enterasys.com/downloads/" target="_blank" rel="nofollow noreferrer noopener"&gt;release notes&lt;/A&gt; state, in the 'Installation and Configuration Notes' section:&lt;BR /&gt;
WARNING: Configuration files containing a login banner may suspend&lt;BR /&gt;
operation of images prior to 6.51. This state can only be corrected by&lt;BR /&gt;
clearing the configuration through the boot PROM. Use extreme caution&lt;BR /&gt;
when using a configuration file. Login banners will automatically be&lt;BR /&gt;
removed from the configuration when back revving to pre-6.51 images.&lt;BR /&gt;
 &lt;BR /&gt;
Note: As a best practice, Enterasys recommends that prior to upgrading&lt;BR /&gt;
or downgrading the firmware on your switch, you save the existing&lt;BR /&gt;
working configuration of the system by using the show config outfile&lt;BR /&gt;
configs/ command. Please note that you will need a copy of&lt;BR /&gt;
your previous configuration if you need to back-rev from 6.51.xx.xxxx&lt;BR /&gt;
to the previous firmware version.&lt;BR /&gt;
 &lt;BR /&gt;
To download the new software to a stack of switches, simply follow the&lt;BR /&gt;
instructions to upgrade a switch with new software. The system will&lt;BR /&gt;
automatically download the new software to all the members in the stack&lt;BR /&gt;
controlled by that stack manager.&lt;BR /&gt;
C5/B5 firmware 6.51.02.0018 &lt;A href="http://extranet.enterasys.com/downloads/" target="_blank" rel="nofollow noreferrer noopener"&gt;release notes&lt;/A&gt; state, in the 'Known Issues in 6.51.02.0018' section: &lt;BR /&gt;
Setting the security profile to c2 changes certain system defaults&lt;BR /&gt;
including encryption algorithms used for storing passwords, shared&lt;BR /&gt;
secrets, and routing keys. As a result, configuration files for devices&lt;BR /&gt;
operating in different security profiles are not fully compatible and&lt;BR /&gt;
may result in some loss of configuration if loaded.&lt;BR /&gt;
 &lt;BR /&gt;
The 6.51 image will not stack with earlier versions of code, due to the&lt;BR /&gt;
use of VLAN 4094. When adding a new unit to an existing stack running&lt;BR /&gt;
6.51 or higher, the unit will (first) need to be running 6.51 or higher.&lt;BR /&gt;
When adding a new unit to an existing stack running a pre-6.51 image,&lt;BR /&gt;
the new unit will (first) need to be downgraded to that pre-6.51 image.&lt;BR /&gt;
Equivalent information is contained in C3/B3/A4 firmware 6.61.02.0007 release notes, in reference to upgrade from pre-6.61 to 6.61+ firmware, or back-rev from 6.61+ to pre-6.61 firmware. &lt;BR /&gt;
&lt;BR /&gt;
Finally; for the I, G, C3, and B3-Series products, these guidelines assume that the upgrade starting point is somewhere in the 6.42 firmware line (&lt;A href="http://bit.ly/I7AmoT" target="_blank" rel="nofollow noreferrer noopener"&gt;14711&lt;/A&gt;). &lt;BR /&gt;
&lt;BR /&gt;
In short:&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;Before upgrading from pre-6.51 to 6.51+; you should save a copy of the pre-6.51 configuration (&lt;A href="http://bit.ly/1nz1lHy" target="_blank" rel="nofollow noreferrer noopener"&gt;5623&lt;/A&gt;), which will be needed if you ever decide to back-rev to pre-6.51. 
&lt;/LI&gt;&lt;LI&gt;When upgrading from pre-6.51 to 6.51+; with the exception of what is stated in &lt;A href="http://bit.ly/I7AmoT" target="_blank" rel="nofollow noreferrer noopener"&gt;14711&lt;/A&gt; the system will make the necessary configuration changes, so the standard upgrade procedure (&lt;A href="http://bit.ly/WhsfvZ" target="_blank" rel="nofollow noreferrer noopener"&gt;5605&lt;/A&gt;) applies. 
&lt;/LI&gt;&lt;LI&gt;After the upgrade, as desired and as applicable reload a saved &lt;I&gt;6.51+ &lt;/I&gt;configuration (&lt;A href="http://bit.ly/1nz1lHy" target="_blank" rel="nofollow noreferrer noopener"&gt;5623&lt;/A&gt;).&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt; 
&lt;LI&gt;Before back-reving from 6.51+ to pre-6.51; you should save a copy of the 6.51+ configuration (&lt;A href="http://bit.ly/1nz1lHy" target="_blank" rel="nofollow noreferrer noopener"&gt;5623&lt;/A&gt;), which could be handy if you ever decide to re-upgrade to 6.51+. 
&lt;/LI&gt;&lt;LI&gt;When back-reving from 6.51+ to pre-6.51; first clear the majority of the configuration ('clear config', &lt;A href="http://bit.ly/1cDGAW0" target="_blank" rel="nofollow noreferrer noopener"&gt;5628&lt;/A&gt;), then use the standard procedure (&lt;A href="http://bit.ly/WhsfvZ" target="_blank" rel="nofollow noreferrer noopener"&gt;5605&lt;/A&gt;). 
&lt;/LI&gt;&lt;LI&gt;After the back-rev, as desired and as applicable reload a saved &lt;I&gt;pre-6.51 &lt;/I&gt;configuration (&lt;A href="http://bit.ly/1nz1lHy" target="_blank" rel="nofollow noreferrer noopener"&gt;5623&lt;/A&gt;).&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt; 
&lt;LI&gt;Ensure that any switches to be added to a stack (&lt;A href="http://bit.ly/1BetvzD" target="_blank" rel="nofollow noreferrer noopener"&gt;7086&lt;/A&gt;) already match the stack in their pre-6.51 vs 6.51+ firmware status, before being added to the stack. Otherwise, the condition will result in a "Code Version Mismatch" error (&lt;A href="http://bit.ly/18qG1jv" target="_blank" rel="nofollow noreferrer noopener"&gt;7326&lt;/A&gt;) that cannot be corrected by an attempted direct copy operation ("set switch copy-fw...') from the manager. Note that the I/G-Series are not stackable products.&lt;/LI&gt;&lt;/UL&gt;See also: &lt;A href="http://bit.ly/I6jFtu" target="_blank" rel="nofollow noreferrer noopener"&gt;14942&lt;/A&gt;.&lt;BR /&gt;</description>
      <pubDate>Thu, 05 Sep 2013 06:02:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/i-g-c-b-a-series-f-w-6-51-6-61-upgrade-considerations/m-p/48052#M502</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-09-05T06:02:00Z</dc:date>
    </item>
  </channel>
</rss>

