Yeah, that's because the ArubaOS-Switch and ArubaOS-CX grammars differ: the show images belongs to the latter, the show flash belongs to the former...and the show version is found on both. On ArubaOS-CX - IIRC - there isn't an equivalent command like the verify signature flash available on ArubaOS-Switch (Edit: on ArubaOS-CX platforms, the software image check happens automatically during the AOS-CX boot by means of Service OS preliminary booting actions).
Original Message:
Sent: 9/30/2024 4:06:00 AM
From: Heinrich
Subject: RE: Upgrading Firmware on a stack
Good Day,
Thank you very much for below instructions worked like a charm, turned out there was a couple of 6000 series switches we also had to upgrade those did not take the "sh flash" command but rather the "sh images" command and after uploading the new firmware to these 6000 switches the switches automatically did the firmware verification.
Thanks again,
Regards
Hello Heinrich! Given that you're dealing with a (backplane) stack of Aruba 3810M you've to consider that such of a stack is Commander driven so...
Original Message:
Sent: 9/27/2024 6:16:00 AM
From: parnassus
Subject: RE: Upgrading Firmware on a stack
Hello Heinrich!
Given that you're dealing with a (backplane) stack of Aruba 3810M you've to consider that such of a stack is Commander driven so basically anything is driven by the Commander, let me copy and paste this paragraph (taken from this document <- old but good):
Software upgrades
In order to upgrade software on a 2930M or 3810M backplane stack, the new software image must be loaded into either the primary or secondary flash on the Commander, the new image must be automatically synchronized to the same flash storage on all other stack members (this occurs in the background), then the stack must be rebooted into the new software version (there is no capability to perform an in-service software upgrade on either platform).
To load the software image from an SFTP server (or use another supported method), use the following command (replace server IP, username/password, and software image filename as appropriate):
switch# copy sftp flash sftpuser@10.10.10.1 WC_16_08_0003.swi primary
To reboot the stack into the new software version, use this command:
switch# boot system flash primary
The entire stack will reboot; once the boot process is complete, a Commander election will occur as normal.
Clearly the above is just an example. In your case the SWI is going to be 16.11.0020 and the Flash partition to be booted at next boot (the one you want to flash with the new code) is the secondary.
If, as example, you are going to use a TFTP Server instead of an SFTP Server, the command to download the SWI file from the TFTP Server to the Commander would be:
stack# copy tftp flash <TFTP-Server-IP-or-FQDN> WC_16_11_0020.swi secondary
or, alternatively, you can just upload it through the WebUI and then via CLI execute those commands to check that the SWI was uploaded on the right flash partition and that the file has a valid signature...and finally execute the command to (re)boot the Commander (and so the whole backplane stack) using the flashed Secondary partition (which is holding the new code):
stack# show flash
stack# verify signature flash secondary
stack# boot system flash secondary
Perform all required checks post reboot and if you see "green light" (as one would expect) then continue with:
stack# show version
stack# show flash
stack# copy flash flash primary
stack# show flash
stack# verify signature flash primary
The copy flash flash primary command above will pair the software versions on both Flash partitions copying it from the Secondary partition (updated) to the Primary partition (which - we are implying - still holds an older code).
No need to say that you need to prepare your stack upgrade/update with running configuration backups (so write memory then show running-configuration status and then backup your running-configuration elsewhere with the method you like most). Do read Release Notes of the target software release (ArubaOS-Switch 16.11.0020) and be eventually prepared to see your stack to automatically reboot twice if BootROM requires and update too (Release Note reports which BootROM is included with the latest ArubaOS-Switch software version and compare that BootROM version with the one you see doing a show flash/show version).
Original Message:
Sent: Sep 27, 2024 01:45 AM
From: Heinrich
Subject: Upgrading Firmware on a stack
Good Day,
Apologies I am re-posting this just in case.
We have the following Core switch setup, all four switches are stacked, one 16porter as the commander two others as members and one standby.
Aruba 3810M-16SFP+-2-slot Switch (JL075A)
1 Commander & One Member
Aruba JL074A 3810M-48G-PoE+-1-slot Switch (JL074A)
1 Member & One Standby
If I use the GUI (HTTP) to do the firmware upgrade, I will upload the latest Firmware (KB_16_11_0020.swi) to the Secondary Image, then reboot & confirm the secondary image is uploaded then rinse and repeat on the Primary Image?
Last question am I correct in assuming the Commander will copy the uploading Firmware, Both Secondary & Primary to all the members including the standby?
As always feedback will be apricated