<?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: Help with upgrading firmware. in ICX Switches</title>
    <link>https://community.ruckuswireless.com/t5/ICX-Switches/Help-with-upgrading-firmware/m-p/14402#M348</link>
    <description>&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;OK but are you using smart zone to manage the switches?&amp;nbsp; That would be the key reason to go with 8090X code stream.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Regardless, since you are at 8090b&amp;nbsp;I would recommend going with 8090d at this point as there are many defect fixes in 8090b that was being addressed in 8090 code stream.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Hope this helps.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Thanks&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Hashim&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
    <pubDate>Tue, 01 Oct 2019 19:31:37 GMT</pubDate>
    <dc:creator>hashim_bharooc1</dc:creator>
    <dc:date>2019-10-01T19:31:37Z</dc:date>
    <item>
      <title>Help with upgrading firmware.</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/Help-with-upgrading-firmware/m-p/14399#M345</link>
      <description>I am looking into upgrading firmware on our icx 7150 switches and I wanted to verify upgrade options. We currently have a number of switches running 08.0.80caT211 and some that are running 08.0.90bT213. The older version is a non router firmware and the others are router firmware. I would like to have all switches on the 08.0.90bT213 firmware. My main question is if I upgrade a non router switch to router capable firmware will they go offline until I change the ip information, or will they convert the current information to match new configuration options? Will I have to use a console connection to manually change the settings to the proper default gateway and add a routable virtual interface.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Tue, 01 Oct 2019 13:33:41 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/Help-with-upgrading-firmware/m-p/14399#M345</guid>
      <dc:creator>conan_lindsey</dc:creator>
      <dc:date>2019-10-01T13:33:41Z</dc:date>
    </item>
    <item>
      <title>Re: Help with upgrading firmware.</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/Help-with-upgrading-firmware/m-p/14400#M346</link>
      <description>&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Hi Conan,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;We do not recommend running 8080 code.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Why did you go with 8090x Code?&amp;nbsp; &lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Did you go with 8090 &amp;nbsp;to use Smart Zone to monitor the ICXs?&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; If so that would be a good reason to go with 8090x. I would recommend 8090d.&amp;nbsp; This is the latest code.&amp;nbsp; If not then&amp;nbsp;you can stick with latest 8070 code.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;When you change code from router to switch and vice versa, you will need to fix the ip configuration part of it.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Also there are corner cases for upgrading from pre 8090 so please check documentation about it.&amp;nbsp; If you are doing stack upgrades using manifest files you have to follow this corrected procedure:&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;To upgrade a stack from 8030x to 8090x using Manifest method ,&amp;nbsp; follow the below series of steps :&lt;/P&gt;&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;1.Copy 8080e Non-UFIimage&amp;nbsp; Manifest file on the system running 8030x ,Moving to 8080e is mandatory and recommended per Engineering .&lt;/P&gt;&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;copy tftp system-manifest x.x.x.x FI08080e_Manifest.txt all-images-primary&lt;/P&gt;&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;2. Reboot the Stack and&amp;nbsp; make sure all the unit in stack has the image that is upgraded with .&lt;/P&gt;&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;3.Next , copy&amp;nbsp; 8090x UFI image on the system running 8080e&lt;/P&gt;&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;copy tftp flash x.x.x.x SPR08090bufi.bin primary&lt;/P&gt;&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;4.Reboot the stack&lt;/P&gt;&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;5.Copy 8090xUFI image in secondary flash.&lt;/P&gt;&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Note :&lt;/P&gt;&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;Interim step to move to 8080e is Mandatory per recommendation from Engineering.&lt;/P&gt;&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;These steps are not required on a standalone system.&lt;/P&gt;&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Hope this helps.&lt;/P&gt;&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;Thanks&lt;/P&gt;&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;Hashim&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Oct 2019 18:55:06 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/Help-with-upgrading-firmware/m-p/14400#M346</guid>
      <dc:creator>hashim_bharooc1</dc:creator>
      <dc:date>2019-10-01T18:55:06Z</dc:date>
    </item>
    <item>
      <title>Re: Help with upgrading firmware.</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/Help-with-upgrading-firmware/m-p/14401#M347</link>
      <description>We went with 8090b because we contracted with a company to configure and replace over 100 switches in our school system.&amp;nbsp; That was the firmware they recommended based on our discussions.&amp;nbsp; We currently still have about 100 switches with 8080ca firmware and from a management standpoint I would like to keep consistent firmware across the board.&amp;nbsp; I was hoping it would be easier then having to touch each switch during the upgrade, but that seems to not be possible.</description>
      <pubDate>Tue, 01 Oct 2019 19:23:51 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/Help-with-upgrading-firmware/m-p/14401#M347</guid>
      <dc:creator>conan_lindsey</dc:creator>
      <dc:date>2019-10-01T19:23:51Z</dc:date>
    </item>
    <item>
      <title>Re: Help with upgrading firmware.</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/Help-with-upgrading-firmware/m-p/14402#M348</link>
      <description>&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;OK but are you using smart zone to manage the switches?&amp;nbsp; That would be the key reason to go with 8090X code stream.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Regardless, since you are at 8090b&amp;nbsp;I would recommend going with 8090d at this point as there are many defect fixes in 8090b that was being addressed in 8090 code stream.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Hope this helps.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Thanks&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Hashim&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Tue, 01 Oct 2019 19:31:37 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/Help-with-upgrading-firmware/m-p/14402#M348</guid>
      <dc:creator>hashim_bharooc1</dc:creator>
      <dc:date>2019-10-01T19:31:37Z</dc:date>
    </item>
    <item>
      <title>Re: Help with upgrading firmware.</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/Help-with-upgrading-firmware/m-p/14403#M349</link>
      <description>We are not using smart zone currently.&amp;nbsp; I will certainly upgrade to 8090d.</description>
      <pubDate>Tue, 01 Oct 2019 19:33:55 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/Help-with-upgrading-firmware/m-p/14403#M349</guid>
      <dc:creator>conan_lindsey</dc:creator>
      <dc:date>2019-10-01T19:33:55Z</dc:date>
    </item>
    <item>
      <title>Re: Help with upgrading firmware.</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/Help-with-upgrading-firmware/m-p/14404#M350</link>
      <description>You an also upgrade the existing 08090b to 08090d with the same command for consistency...&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;ftp flash x.x.x.x SPR08090bufi.bin primary&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I would also do a "write memory" or "wr mem" before the restart just incase the vendor did not save all configurations for some reason.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;You also want to do a "sh clock" to ensure the time is proper.&amp;nbsp; For example right now I get:&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;08:09:46.999 Eastern Wed Oct 02 2019&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;If the time is wrong, check your NTP and time-zone settings via "show run" and "sh ntp associations"&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;B&gt;My commands are:&lt;/B&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;clock summer-time&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;clock timezone us Eastern&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;ntp&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;server x.x.x.x&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR /&gt;From there you can schedule the restart via reload at xx:xx:xx xx-xx-xx for the time and date.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;We have 08080e deployed and will be doing the same.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Best regards,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Justin</description>
      <pubDate>Wed, 02 Oct 2019 12:08:19 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/Help-with-upgrading-firmware/m-p/14404#M350</guid>
      <dc:creator>netwizz</dc:creator>
      <dc:date>2019-10-02T12:08:19Z</dc:date>
    </item>
    <item>
      <title>Re: Help with upgrading firmware.</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/Help-with-upgrading-firmware/m-p/14405#M351</link>
      <description>Always consider your feature function needs.&amp;nbsp; Version trains run parallel and add fixes, etc.&amp;nbsp; If you don't have a problem, why upgrade?&amp;nbsp; If it ain't broke...</description>
      <pubDate>Fri, 04 Oct 2019 21:45:11 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/Help-with-upgrading-firmware/m-p/14405#M351</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2019-10-04T21:45:11Z</dc:date>
    </item>
  </channel>
</rss>

