- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- HPE Aruba Networking & ProVision-based
- >
- What is the prefered firmware (Aruba 2930F-24G-4SF...
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
Forums
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
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
10-14-2020 12:00 PM
10-14-2020 12:00 PM
I just bought a 2930F with the following info (show flash):
Primary Image : 21959829 04/14/17 WC.16.03.0004
Secondary Image : 21959829 04/14/17 WC.16.03.0004
Boot ROM Version
----------------
Primary Boot ROM Version : WC.16.01.0003
Secondary Boot ROM Version : WC.16.01.0003
Default Boot Image : Primary
Default Boot ROM : Primary
I've had a look at det firmware page, and it has a load of firmwares from 16.03.xxxx to 16.10.xxxx, so I need some advice on what firmware to install.
Should I go for 16.10, or just stay at 16.03, and upgrade to that latest version ( december 2017)?
If I go to 16.10, could someone direct me how to do it, and what steps to take to get there? I know I can't upgrade directly, so please guide me through the fw-versions needed.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2020 03:53 PM - edited 10-14-2020 03:57 PM
10-14-2020 03:53 PM - edited 10-14-2020 03:57 PM
SolutionHi! you can update the ArubaOS-Switch software directly jumping between your current WC.16.03.0004 to latest WC.16.10.0010.
My suggestion is to go to latest of WC.16.10 which is WC.16.10.0010.
Upgrade procedure: it depends...you can use the GUI or you can use the CLI (via SSH/Telnet access, if any)...provided that you already have played a little bit with the console and you're already familiar with some basic management commands.
The GUI way is simpler than other methods, it just requires you to login and perform a drag and drop operation of the SWI files in the desired flash partition of choice.
The CLI way provides you more control, basically you need (that's my preference) a TFTP server reacheable by the Switch.
Once you can reach (PING) the TFTP Server place the required SWI file on it and use the command:
copy tftp flash <IP-of-TFTP-Server> <SWI-filename> primary (or secondary, if you want to flash the secondary flash memory area first <- it's your case, read below)
once flashed perform the reboot by selecting the flashed area to be used for next boot:
system boot flash primary (or secondary, if you flashed the secondary as you should in your case, read below)
wait for reboot to complete (if Boot ROM requires to be updated it will automatically and expect a second automatic reboot: first Boot ROM will be updated and then the newly flashed ArubaOS-Switch version will be booted) and check the result with:
show flash
show version
once all is OK you can pair/align the flashed boot (updated at WC.16.10.0010) version and the previous booted flash area version (which still is at WC.16.03.0004)...the main idea is indeed first to flash (update) the boot image not used as "default boot image" (thus in your case you should start by flashing the secondary image), then boot the flashed area and, once post update checks give you a sound "Go" (AKA the flash procedure went perfectly and the running configuration is OK), perform the alignment of the default boot image (you didn't touched yet) to cope with the updated flash (you touched), this is done via:
copy flash flash primary (because you copy the actual booted secondary you flashed into the primary otherwise the command would have been copy flash flash secondary)
You can also verify the signature (during any time so pre/post-update) of flashed memory areas (images) with the command:
verify signature flash primary (or secondary)
Basically, that's it.
I'm not an HPE Employee
