Help with upgrading firmware.

  • 1
  • Question
  • Updated 1 year ago
  • Answered
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.
Photo of Conan Lindsey

Conan Lindsey

  • 3 Posts
  • 0 Reply Likes

Posted 1 year ago

  • 1
Photo of Hashim Bharoocha

Hashim Bharoocha, Employee

  • 78 Posts
  • 40 Reply Likes


Hi Conan,

We do not recommend running 8080 code.
Why did you go with 8090x Code? 
Did you go with 8090  to use Smart Zone to monitor the ICXs?     If so that would be a good reason to go with 8090x. I would recommend 8090d.  This is the latest code.  If not then you can stick with latest 8070 code.

When you change code from router to switch and vice versa, you will need to fix the ip configuration part of it.

Also there are corner cases for upgrading from pre 8090 so please check documentation about it.  If you are doing stack upgrades using manifest files you have to follow this corrected procedure:

To upgrade a stack from 8030x to 8090x using Manifest method ,  follow the below series of steps :

1.Copy 8080e Non-UFIimage  Manifest file on the system running 8030x ,Moving to 8080e is mandatory and recommended per Engineering .

copy tftp system-manifest x.x.x.x FI08080e_Manifest.txt all-images-primary

2. Reboot the Stack and  make sure all the unit in stack has the image that is upgraded with .

3.Next , copy  8090x UFI image on the system running 8080e

copy tftp flash x.x.x.x SPR08090bufi.bin primary

4.Reboot the stack

5.Copy 8090xUFI image in secondary flash.


Note :

Interim step to move to 8080e is Mandatory per recommendation from Engineering.

These steps are not required on a standalone system.

 
Hope this helps.

Thanks

Hashim






Photo of Conan Lindsey

Conan Lindsey

  • 3 Posts
  • 0 Reply Likes
We went with 8090b because we contracted with a company to configure and replace over 100 switches in our school system.  That was the firmware they recommended based on our discussions.  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.  I was hoping it would be easier then having to touch each switch during the upgrade, but that seems to not be possible.
Photo of Hashim Bharoocha

Hashim Bharoocha, Employee

  • 78 Posts
  • 40 Reply Likes

OK but are you using smart zone to manage the switches?  That would be the key reason to go with 8090X code stream.
Regardless, since you are at 8090b 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.

Hope this helps.
Thanks
Hashim
Photo of Conan Lindsey

Conan Lindsey

  • 3 Posts
  • 0 Reply Likes
We are not using smart zone currently.  I will certainly upgrade to 8090d.
Photo of NETWizz

NETWizz

  • 214 Posts
  • 68 Reply Likes
You an also upgrade the existing 08090b to 08090d with the same command for consistency...

ftp flash x.x.x.x SPR08090bufi.bin primary


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.

You also want to do a "sh clock" to ensure the time is proper.  For example right now I get:

08:09:46.999 Eastern Wed Oct 02 2019

If the time is wrong, check your NTP and time-zone settings via "show run" and "sh ntp associations"


My commands are:
clock summer-time
clock timezone us Eastern
!
!
ntp
 server x.x.x.x
!

From there you can schedule the restart via reload at xx:xx:xx xx-xx-xx for the time and date.


We have 08080e deployed and will be doing the same.

Best regards,

Justin
(Edited)
Photo of Michael Brado

Michael Brado, Official Rep

  • 3298 Posts
  • 523 Reply Likes
Always consider your feature function needs.  Version trains run parallel and add fixes, etc.  If you don't have a problem, why upgrade?  If it ain't broke...