Aruba & ProVision-based
cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Aruba firmware updates

 
SOLVED
Go to solution
Highlighted
Occasional Contributor

Aruba firmware updates

Aruba noob question...

Is it best practice to update the firmware on Aruba switches (ie. 2530-48G J9775A etc)  from one major version to another in one hit?

For example, I have inherited some gear that is on firmware version YA.16.05.0008. Can I bump them straight to the latest version (currently YA.16.10.0007) or should I go via 16.06 - 16.09 first and eventually end up at the latest version.

Thanks

2 REPLIES 2
Highlighted
HPE Pro
Solution

Re: Aruba firmware updates

Hi SharkyMp.

I see that you are currently running YA.16.05.0008

You will need to upgrade to 16.06 >> 16.08>>YA.16.10.0007

You will find this information after u click the select tab of the firmware. 

Software release YA.16.10.0007 UPGRADE NOTE: HPE recommends that you update to this software from one of the three previous releases (YA.16.08.xxxx - YA.16.10.xxxx)

Software: YA.16.08.0001  UPGRADE NOTE: HPE recommends that you update to this software from one of the three previous releases (YA.16.06.xxxx - YA.16.08.xxxx).

YA.16.06.0006 HPE recommends that you update to this software from one of the three previous releases (YA.16.03.xxxx - YA.16.05.xxxx)

 Software download page :- https://h10145.www1.hpe.com/downloads/SoftwareReleases.aspx?ProductNumber=J9775A

I hope this helps !

Thank you,
I am an HPE employee
-------------------------------------------------------------------------
Was the post useful? Click on Kudos Thumb below
Highlighted
Honored Contributor

Re: Aruba firmware updates

Hi! It's also true that suggested upgrade steps are not reported inside any YA.16.05, YA.16.06, YA.16.07, YA.16.08, YA.16.09 or YA.16.10 Release Notes.

Technically the BootROM will remain (if it currently is) YA.15.20 (eventually it updates automatically being embedded into the SWI file)...the application software, distributed as a SWI file, can instead be updated directly - one step - from YA.16.05 to YA.16.10 (I've performed, as example, a direct upgrade - one step - from YA.16.07 to YA.16.10 on four of our access switches today without any issue).

The process is, as usual, to flash the non booted Flash Area (Primary of Secondary, if the booted one is the Secondary or Primary respectively) and then boot the Switch from that flashed area.

Via CLI is a two commands process:

  1. flashing (example: copy tftp flash <ip-of-tftp-server> YA_16_10_0007.swi secondary to flash on Secondary Flash Area)
  2. booting (example: boot system flash secondary to set the Switch to boot from the flashed Secondary Flash Area during next reboot)
  3. Optionally: to pair both Flash Areas by copying the updated one over the non updated one once you verify all is good with the updated software (example: copy flash flash primary to copy the updated Secondary over non updated Primary)

 

 


I'm not an HPE Employee
Kudos and Accepted Solution banner