Hi Martin.
When the FW is on correct version, new APs should join existing cluster without any problems and will inherit configuration from existing cluster.
If you really want to play safe, you can factory reset AP before adding it to the cluster.
Main requirement is, that the cluster is up and running before you add a new AP.
Original Message:
Sent: Jan 21, 2024 02:36 PM
From: Scryden
Subject: Downgrading firmware on IAP-315
Hi Gorazd,
Thank you I will try that. Are there any risks by doing this? I don't want the 2 IAP-315 APs to somehow screw up the existing cluster. Is this safe to do?
Original Message:
Sent: Jan 21, 2024 03:38 AM
From: GorazdKikelj
Subject: Downgrading firmware on IAP-315
Hi Martin.
Try the following.
Upgrade back to 8.11.
Disable activate
Downgrade to 6.5.4.3. Do not reboot.
Connect AP to the existing cluster and power it on.
It should connect to existing cluster and stay on the 6.5.4.3 version.
Just add second AP to the cluster and it will downgrade itself.
Hope it will work.
Best, Gorazd
------------------------------
Gorazd Kikelj
MVP Expert 2023
Original Message:
Sent: Jan 21, 2024 03:21 AM
From: Scryden
Subject: Downgrading firmware on IAP-315
Hi Gorazd,
I tried that command but that command does not exist in version 6.5.4.3. Yet the AP is still automatically checking for updates and automatically upgrading to version 8.11.
(config) # activate-disable
^
% Parse error
Original Message:
Sent: Jan 21, 2024 03:16 AM
From: GorazdKikelj
Subject: Downgrading firmware on IAP-315
Hi Scryden.
Use "activate-disable" command to prevent automatic upgrade of the FW image.
Best, Gorazd
------------------------------
Gorazd Kikelj
MVP Expert 2023
Original Message:
Sent: Jan 21, 2024 02:17 AM
From: Scryden
Subject: Downgrading firmware on IAP-315
The story gets even weirder.
I found that when I upload the old firmware image, the image goes into Backup Partition 1, while the primary partition keeps the 8.11 firmware:
Primary Partition :0
Primary Partition Build Time :2023-12-6 05:38:23 UTC
Primary Partition Build Version :8.11.2.1_88699 SSR (Digitally Signed - Production Build)
Backup Partition :1
Backup Partition Build Time :2017-10-19 20:14:11 PDT
Backup Partition Build Version :6.5.4.3_61959 (Digitally Signed - Production Build)
Now, when the IAP reboots into 6.5.4.3 and I immediately upload the old firmware image again, now the primary partition is overwritten with 6.5.4.3 like so:
Primary Partition :1
Primary Partition Build Time :2017-10-19 20:14:11 PDT
Primary Partition Build Version :6.5.4.3_61959 (Digitally Signed - Production Build)
Backup Partition :0
Backup Partition Build Time :2017-10-19 20:14:11 PDT
Backup Partition Build Version :6.5.4.3_61959 (Digitally Signed - Production Build)
At this point I thought I booked great success! The 8.11 image is gone and both partition now contain 6.5.4.3. However, I celebrated prematurely. When spamming the "show upgrade" command I noticed the following happening:
swarm upgrade status
--------------------
Mac IP Address Seed AP AP Class Status Image Info
--- ---------- ------- -------- ------ ----------
x:x:X:x:x x.x.x.138 Yes Hercules download-done http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Hercules_8.11.2.1_88699
Auto reboot :enable
Use external URL :enable
Master wait Time :6 secs 2 count
Switch Partition :enable
Upgrade in process :Yes
So the AP does in fact automatically check for image upgrades and just goes ahead and performs the upgrade. How do I stop this from happening? I found the "ignore-image-check" command online in the HPE documentation, however this command expects a value:
# ignore-image-check ?
<val> val
Simply pressing enter results in a "incomplete command". I don't know what value it is expecting here and the HPE documentation doesn't specify either.
Original Message:
Sent: Jan 20, 2024 04:29 PM
From: mkk
Subject: Downgrading firmware on IAP-315
Two IAP in the same layer-2 form automatic a cluster. What i think what happens is that you downgrade one it will re-connect the other and upgrade again. Try downgrade again when have one AP in a dedicated vlan to prevent this. Let us known if that's works.
------------------------------
Marcel Koedijk | MVP Expert 2023 | ACEP | ACMP | ACCP | ACDP | Ekahau ECSE | Not an HPE Employee | Opinions are my own