- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- HPE Aruba Networking & ProVision-based
- >
- Aruba firmware updates
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2020 05:16 AM
06-18-2020 05:16 AM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2020 06:15 AM - edited 06-18-2020 07:01 AM
06-18-2020 06:15 AM - edited 06-18-2020 07:01 AM
SolutionHi 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 !
I am an HPE employee
-------------------------------------------------------------------------
Was the post useful? Click on Kudos Thumb below
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2020 03:04 PM
06-18-2020 03:04 PM
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:
- flashing (example: copy tftp flash <ip-of-tftp-server> YA_16_10_0007.swi secondary to flash on Secondary Flash Area)
- booting (example: boot system flash secondary to set the Switch to boot from the flashed Secondary Flash Area during next reboot)
- 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
