Wireless Access

You will also have to convert the AP back to a CAP WAP. 

convert-aos-ap cap <controller-address>

Covered here - in Section "Revert to AOS 8 Firmware Version"

That was the missing piece, it worked!

You will also have to convert the AP back to a CAP WAP. 

convert-aos-ap cap <controller-address>

Covered here - in Section "Revert to AOS 8 Firmware Version"

New link for posterity: https://www.arubanetworks.com/techdocs/aos/aos10/migrate/aps/cap/#revert-to-aos-8-firmware-version

That was the missing piece, it worked!

You will also have to convert the AP back to a CAP WAP. 

convert-aos-ap cap <controller-address>

Covered here - in Section "Revert to AOS 8 Firmware Version"

Thank you, I can add as well that I noticed that this method worked for any Access-points I had running in Aruba Central, regardless of the fact that they were previously associated with the controller. 

New link for posterity: https://www.arubanetworks.com/techdocs/aos/aos10/migrate/aps/cap/#revert-to-aos-8-firmware-version

That was the missing piece, it worked!

You will also have to convert the AP back to a CAP WAP. 

convert-aos-ap cap <controller-address>

Covered here - in Section "Revert to AOS 8 Firmware Version"

The command is used for converting any AP running IAP or AOS 10 to a campus AP.

Note, only one of the two images on the AP is converted to the campus AP image, you can end up in a situation where the AP will boot to the non-campus image and the AP doesn't behave as expected.

Downgrade from AOS 10 to AOS 8 should only be done when absolutely necessary.

Thank you, I can add as well that I noticed that this method worked for any Access-points I had running in Aruba Central, regardless of the fact that they were previously associated with the controller. 

New link for posterity: https://www.arubanetworks.com/techdocs/aos/aos10/migrate/aps/cap/#revert-to-aos-8-firmware-version

That was the missing piece, it worked!

You will also have to convert the AP back to a CAP WAP. 

convert-aos-ap cap <controller-address>

Covered here - in Section "Revert to AOS 8 Firmware Version"

Thanks Carson

This is currently all simulation of course but I want to be sure when performing this in the production network I am not overlooking anything. 

I can see indeed that the backup is still set to AOS10 by issuing the show ap image version output below.

The command is used for converting any AP running IAP or AOS 10 to a campus AP.

Note, only one of the two images on the AP is converted to the campus AP image, you can end up in a situation where the AP will boot to the non-campus image and the AP doesn't behave as expected.

Downgrade from AOS 10 to AOS 8 should only be done when absolutely necessary.

Thank you, I can add as well that I noticed that this method worked for any Access-points I had running in Aruba Central, regardless of the fact that they were previously associated with the controller. 

New link for posterity: https://www.arubanetworks.com/techdocs/aos/aos10/migrate/aps/cap/#revert-to-aos-8-firmware-version

That was the missing piece, it worked!

You will also have to convert the AP back to a CAP WAP. 

convert-aos-ap cap <controller-address>

Covered here - in Section "Revert to AOS 8 Firmware Version"

The controller will only ever upgrade the primary partition, the secondary is left untouched to provide a fallback.  What you'd probably have to do is, while running AOS 10, load a version of IAP to the secondary partition before converting back to CAP.  As long as DHCP discovery is configured properly, even the IAP image will eventually find the controller automatically and convert again.

Note though, AOS 10 is moving away from having two complete images stored in flash as we move towards a more services based architecture for the AP software.  That change will impact the ability what I've stated here, I just don't know exactly how at this point.

Thanks Carson

This is currently all simulation of course but I want to be sure when performing this in the production network I am not overlooking anything. 

I can see indeed that the backup is still set to AOS10 by issuing the show ap image version output below.

The command is used for converting any AP running IAP or AOS 10 to a campus AP.

Note, only one of the two images on the AP is converted to the campus AP image, you can end up in a situation where the AP will boot to the non-campus image and the AP doesn't behave as expected.

Downgrade from AOS 10 to AOS 8 should only be done when absolutely necessary.

Thank you, I can add as well that I noticed that this method worked for any Access-points I had running in Aruba Central, regardless of the fact that they were previously associated with the controller. 

New link for posterity: https://www.arubanetworks.com/techdocs/aos/aos10/migrate/aps/cap/#revert-to-aos-8-firmware-version

That was the missing piece, it worked!

You will also have to convert the AP back to a CAP WAP. 

convert-aos-ap cap <controller-address>

Covered here - in Section "Revert to AOS 8 Firmware Version"

So if I understand correctly, try something like:

• Connect to the APs while in Aruba Central through console
• Wipe out flash (?)
• Copy the image to the backup flash 
• Revert back?

The controller will only ever upgrade the primary partition, the secondary is left untouched to provide a fallback.  What you'd probably have to do is, while running AOS 10, load a version of IAP to the secondary partition before converting back to CAP.  As long as DHCP discovery is configured properly, even the IAP image will eventually find the controller automatically and convert again.

Note though, AOS 10 is moving away from having two complete images stored in flash as we move towards a more services based architecture for the AP software.  That change will impact the ability what I've stated here, I just don't know exactly how at this point.

Thanks Carson

This is currently all simulation of course but I want to be sure when performing this in the production network I am not overlooking anything. 

I can see indeed that the backup is still set to AOS10 by issuing the show ap image version output below.

The command is used for converting any AP running IAP or AOS 10 to a campus AP.

Note, only one of the two images on the AP is converted to the campus AP image, you can end up in a situation where the AP will boot to the non-campus image and the AP doesn't behave as expected.

Downgrade from AOS 10 to AOS 8 should only be done when absolutely necessary.

Thank you, I can add as well that I noticed that this method worked for any Access-points I had running in Aruba Central, regardless of the fact that they were previously associated with the controller. 

New link for posterity: https://www.arubanetworks.com/techdocs/aos/aos10/migrate/aps/cap/#revert-to-aos-8-firmware-version

That was the missing piece, it worked!

You will also have to convert the AP back to a CAP WAP. 

convert-aos-ap cap <controller-address>

Covered here - in Section "Revert to AOS 8 Firmware Version"

Thanks Carson

This is currently all simulation of course but I want to be sure when performing this in the production network I am not overlooking anything. 

I can see indeed that the backup is still set to AOS10 by issuing the show ap image version output below.

The command is used for converting any AP running IAP or AOS 10 to a campus AP.

Note, only one of the two images on the AP is converted to the campus AP image, you can end up in a situation where the AP will boot to the non-campus image and the AP doesn't behave as expected.

Downgrade from AOS 10 to AOS 8 should only be done when absolutely necessary.

Thank you, I can add as well that I noticed that this method worked for any Access-points I had running in Aruba Central, regardless of the fact that they were previously associated with the controller. 

New link for posterity: https://www.arubanetworks.com/techdocs/aos/aos10/migrate/aps/cap/#revert-to-aos-8-firmware-version

That was the missing piece, it worked!

You will also have to convert the AP back to a CAP WAP. 

convert-aos-ap cap <controller-address>

Covered here - in Section "Revert to AOS 8 Firmware Version"

Thanks Carson

This is currently all simulation of course but I want to be sure when performing this in the production network I am not overlooking anything. 

I can see indeed that the backup is still set to AOS10 by issuing the show ap image version output below.

The command is used for converting any AP running IAP or AOS 10 to a campus AP.

Note, only one of the two images on the AP is converted to the campus AP image, you can end up in a situation where the AP will boot to the non-campus image and the AP doesn't behave as expected.

Downgrade from AOS 10 to AOS 8 should only be done when absolutely necessary.

Thank you, I can add as well that I noticed that this method worked for any Access-points I had running in Aruba Central, regardless of the fact that they were previously associated with the controller. 

New link for posterity: https://www.arubanetworks.com/techdocs/aos/aos10/migrate/aps/cap/#revert-to-aos-8-firmware-version

That was the missing piece, it worked!

You will also have to convert the AP back to a CAP WAP. 

convert-aos-ap cap <controller-address>

Covered here - in Section "Revert to AOS 8 Firmware Version"

That particular command only works for those specific models, which is why I don't bother mentioning that as an option.

Thanks Carson

This is currently all simulation of course but I want to be sure when performing this in the production network I am not overlooking anything. 

I can see indeed that the backup is still set to AOS10 by issuing the show ap image version output below.

The command is used for converting any AP running IAP or AOS 10 to a campus AP.

Note, only one of the two images on the AP is converted to the campus AP image, you can end up in a situation where the AP will boot to the non-campus image and the AP doesn't behave as expected.

Downgrade from AOS 10 to AOS 8 should only be done when absolutely necessary.

Thank you, I can add as well that I noticed that this method worked for any Access-points I had running in Aruba Central, regardless of the fact that they were previously associated with the controller. 

New link for posterity: https://www.arubanetworks.com/techdocs/aos/aos10/migrate/aps/cap/#revert-to-aos-8-firmware-version

That was the missing piece, it worked!

You will also have to convert the AP back to a CAP WAP. 

convert-aos-ap cap <controller-address>

Covered here - in Section "Revert to AOS 8 Firmware Version"

thanks insightful

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 12:13 PM
From: chulcher
Subject: Migration and Backout processes of Campus APs (half working)

That particular command only works for those specific models, which is why I don't bother mentioning that as an option.

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 18, 2024 12:09 PM
From: VanD
Subject: Migration and Backout processes of Campus APs (half working)

Original Message:
Sent: 3/18/2024 11:54:00 AM
From: mvanoverbeek
Subject: RE: Migration and Backout processes of Campus APs (half working)

Thanks Carson

This is currently all simulation of course but I want to be sure when performing this in the production network I am not overlooking anything. 

I can see indeed that the backup is still set to AOS10 by issuing the show ap image version output below.

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 10:26 AM
From: Carson Hulcher
Subject: Migration and Backout processes of Campus APs (half working)

The command is used for converting any AP running IAP or AOS 10 to a campus AP.

Note, only one of the two images on the AP is converted to the campus AP image, you can end up in a situation where the AP will boot to the non-campus image and the AP doesn't behave as expected.

Downgrade from AOS 10 to AOS 8 should only be done when absolutely necessary.

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 18, 2024 10:18 AM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

Thank you, I can add as well that I noticed that this method worked for any Access-points I had running in Aruba Central, regardless of the fact that they were previously associated with the controller. 

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 09:45 AM
From: chulcher
Subject: Migration and Backout processes of Campus APs (half working)

New link for posterity: https://www.arubanetworks.com/techdocs/aos/aos10/migrate/aps/cap/#revert-to-aos-8-firmware-version

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 16, 2024 09:41 AM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

That was the missing piece, it worked!

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 15, 2024 04:52 PM
From: 802.zak
Subject: Migration and Backout processes of Campus APs (half working)

You will also have to convert the AP back to a CAP WAP. 

convert-aos-ap cap <controller-address>

Covered here - in Section "Revert to AOS 8 Firmware Version"

------------------------------
If my post was useful, please Accept Solution and Give Kudos.
------------------------------
Zak Chalupka
Principal Engineer - HPE Aruba
ACDX | ACMP | ACSP | ACCP
wifizak@hpe.com
------------------------------
Ideas expressed here are solely my own and not necessarily that of HPE Aruba.

Original Message:
Sent: Mar 15, 2024 04:43 PM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company
------------------------------

Just a thought about the revert process. Would it be an idea to create a temporary AOS8 group on Aruba Central and before reverting AOS10 back to the local controller based version, downgrade to AOS8 from Aruba Central and then issue the conversion from Aruba Central? That way at least I would don't have this descrepancy:

So full backout process would be:

Step 1: Move AOS 10 AP to AOS8 group

Step 2: (When AP is reachable and booted from AOS8): aos-convert-ap cap <a.b.c.d>

Step 3: Reboot if required

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 12:42 PM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

thanks insightful

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 12:13 PM
From: chulcher
Subject: Migration and Backout processes of Campus APs (half working)

That particular command only works for those specific models, which is why I don't bother mentioning that as an option.

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 18, 2024 12:09 PM
From: VanD
Subject: Migration and Backout processes of Campus APs (half working)

Original Message:
Sent: 3/18/2024 11:54:00 AM
From: mvanoverbeek
Subject: RE: Migration and Backout processes of Campus APs (half working)

Thanks Carson

This is currently all simulation of course but I want to be sure when performing this in the production network I am not overlooking anything. 

I can see indeed that the backup is still set to AOS10 by issuing the show ap image version output below.

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 10:26 AM
From: Carson Hulcher
Subject: Migration and Backout processes of Campus APs (half working)

The command is used for converting any AP running IAP or AOS 10 to a campus AP.

Note, only one of the two images on the AP is converted to the campus AP image, you can end up in a situation where the AP will boot to the non-campus image and the AP doesn't behave as expected.

Downgrade from AOS 10 to AOS 8 should only be done when absolutely necessary.

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 18, 2024 10:18 AM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

Thank you, I can add as well that I noticed that this method worked for any Access-points I had running in Aruba Central, regardless of the fact that they were previously associated with the controller. 

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 09:45 AM
From: chulcher
Subject: Migration and Backout processes of Campus APs (half working)

New link for posterity: https://www.arubanetworks.com/techdocs/aos/aos10/migrate/aps/cap/#revert-to-aos-8-firmware-version

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 16, 2024 09:41 AM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

That was the missing piece, it worked!

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 15, 2024 04:52 PM
From: 802.zak
Subject: Migration and Backout processes of Campus APs (half working)

You will also have to convert the AP back to a CAP WAP. 

convert-aos-ap cap <controller-address>

Covered here - in Section "Revert to AOS 8 Firmware Version"

------------------------------
If my post was useful, please Accept Solution and Give Kudos.
------------------------------
Zak Chalupka
Principal Engineer - HPE Aruba
ACDX | ACMP | ACSP | ACCP
wifizak@hpe.com
------------------------------
Ideas expressed here are solely my own and not necessarily that of HPE Aruba.

Original Message:
Sent: Mar 15, 2024 04:43 PM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company
------------------------------

If that method works for you, then sure.

Just a thought about the revert process. Would it be an idea to create a temporary AOS8 group on Aruba Central and before reverting AOS10 back to the local controller based version, downgrade to AOS8 from Aruba Central and then issue the conversion from Aruba Central? That way at least I would don't have this descrepancy:

So full backout process would be:

Step 1: Move AOS 10 AP to AOS8 group

Step 2: (When AP is reachable and booted from AOS8): aos-convert-ap cap <a.b.c.d>

Step 3: Reboot if required

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 12:42 PM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

thanks insightful

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 12:13 PM
From: chulcher
Subject: Migration and Backout processes of Campus APs (half working)

That particular command only works for those specific models, which is why I don't bother mentioning that as an option.

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 18, 2024 12:09 PM
From: VanD
Subject: Migration and Backout processes of Campus APs (half working)

Original Message:
Sent: 3/18/2024 11:54:00 AM
From: mvanoverbeek
Subject: RE: Migration and Backout processes of Campus APs (half working)

Thanks Carson

This is currently all simulation of course but I want to be sure when performing this in the production network I am not overlooking anything. 

I can see indeed that the backup is still set to AOS10 by issuing the show ap image version output below.

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 10:26 AM
From: Carson Hulcher
Subject: Migration and Backout processes of Campus APs (half working)

The command is used for converting any AP running IAP or AOS 10 to a campus AP.

Note, only one of the two images on the AP is converted to the campus AP image, you can end up in a situation where the AP will boot to the non-campus image and the AP doesn't behave as expected.

Downgrade from AOS 10 to AOS 8 should only be done when absolutely necessary.

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 18, 2024 10:18 AM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

Thank you, I can add as well that I noticed that this method worked for any Access-points I had running in Aruba Central, regardless of the fact that they were previously associated with the controller. 

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 09:45 AM
From: chulcher
Subject: Migration and Backout processes of Campus APs (half working)

New link for posterity: https://www.arubanetworks.com/techdocs/aos/aos10/migrate/aps/cap/#revert-to-aos-8-firmware-version

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 16, 2024 09:41 AM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

That was the missing piece, it worked!

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 15, 2024 04:52 PM
From: 802.zak
Subject: Migration and Backout processes of Campus APs (half working)

You will also have to convert the AP back to a CAP WAP. 

convert-aos-ap cap <controller-address>

Covered here - in Section "Revert to AOS 8 Firmware Version"

------------------------------
If my post was useful, please Accept Solution and Give Kudos.
------------------------------
Zak Chalupka
Principal Engineer - HPE Aruba
ACDX | ACMP | ACSP | ACCP
wifizak@hpe.com
------------------------------
Ideas expressed here are solely my own and not necessarily that of HPE Aruba.

Original Message:
Sent: Mar 15, 2024 04:43 PM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company
------------------------------

Actually, not quite. When I used this method in Aruba Central and issued the command "show image version" the secondary Flash still had AOS10 running (see below)

If that method works for you, then sure.

Just a thought about the revert process. Would it be an idea to create a temporary AOS8 group on Aruba Central and before reverting AOS10 back to the local controller based version, downgrade to AOS8 from Aruba Central and then issue the conversion from Aruba Central? That way at least I would don't have this descrepancy:

So full backout process would be:

Step 1: Move AOS 10 AP to AOS8 group

Step 2: (When AP is reachable and booted from AOS8): aos-convert-ap cap <a.b.c.d>

Step 3: Reboot if required

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 12:42 PM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

thanks insightful

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 12:13 PM
From: chulcher
Subject: Migration and Backout processes of Campus APs (half working)

That particular command only works for those specific models, which is why I don't bother mentioning that as an option.

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 18, 2024 12:09 PM
From: VanD
Subject: Migration and Backout processes of Campus APs (half working)

Original Message:
Sent: 3/18/2024 11:54:00 AM
From: mvanoverbeek
Subject: RE: Migration and Backout processes of Campus APs (half working)

Thanks Carson

This is currently all simulation of course but I want to be sure when performing this in the production network I am not overlooking anything. 

I can see indeed that the backup is still set to AOS10 by issuing the show ap image version output below.

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 10:26 AM
From: Carson Hulcher
Subject: Migration and Backout processes of Campus APs (half working)

The command is used for converting any AP running IAP or AOS 10 to a campus AP.

Note, only one of the two images on the AP is converted to the campus AP image, you can end up in a situation where the AP will boot to the non-campus image and the AP doesn't behave as expected.

Downgrade from AOS 10 to AOS 8 should only be done when absolutely necessary.

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 18, 2024 10:18 AM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

Thank you, I can add as well that I noticed that this method worked for any Access-points I had running in Aruba Central, regardless of the fact that they were previously associated with the controller. 

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 09:45 AM
From: chulcher
Subject: Migration and Backout processes of Campus APs (half working)

New link for posterity: https://www.arubanetworks.com/techdocs/aos/aos10/migrate/aps/cap/#revert-to-aos-8-firmware-version

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 16, 2024 09:41 AM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

That was the missing piece, it worked!

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 15, 2024 04:52 PM
From: 802.zak
Subject: Migration and Backout processes of Campus APs (half working)

You will also have to convert the AP back to a CAP WAP. 

convert-aos-ap cap <controller-address>

Covered here - in Section "Revert to AOS 8 Firmware Version"

------------------------------
If my post was useful, please Accept Solution and Give Kudos.
------------------------------
Zak Chalupka
Principal Engineer - HPE Aruba
ACDX | ACMP | ACSP | ACCP
wifizak@hpe.com
------------------------------
Ideas expressed here are solely my own and not necessarily that of HPE Aruba.

Original Message:
Sent: Mar 15, 2024 04:43 PM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company
------------------------------

I like that method/result, and you should get consistent results as long as the DHCP scope is configured to instruct UAP/IAP APs to automatically convert to controller based.

Actually, not quite. When I used this method in Aruba Central and issued the command "show image version" the secondary Flash still had AOS10 running (see below)

If that method works for you, then sure.

Just a thought about the revert process. Would it be an idea to create a temporary AOS8 group on Aruba Central and before reverting AOS10 back to the local controller based version, downgrade to AOS8 from Aruba Central and then issue the conversion from Aruba Central? That way at least I would don't have this descrepancy:

So full backout process would be:

Step 1: Move AOS 10 AP to AOS8 group

Step 2: (When AP is reachable and booted from AOS8): aos-convert-ap cap <a.b.c.d>

Step 3: Reboot if required

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 12:42 PM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

thanks insightful

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 12:13 PM
From: chulcher
Subject: Migration and Backout processes of Campus APs (half working)

That particular command only works for those specific models, which is why I don't bother mentioning that as an option.

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 18, 2024 12:09 PM
From: VanD
Subject: Migration and Backout processes of Campus APs (half working)

Original Message:
Sent: 3/18/2024 11:54:00 AM
From: mvanoverbeek
Subject: RE: Migration and Backout processes of Campus APs (half working)

Thanks Carson

This is currently all simulation of course but I want to be sure when performing this in the production network I am not overlooking anything. 

I can see indeed that the backup is still set to AOS10 by issuing the show ap image version output below.

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 10:26 AM
From: Carson Hulcher
Subject: Migration and Backout processes of Campus APs (half working)

The command is used for converting any AP running IAP or AOS 10 to a campus AP.

Note, only one of the two images on the AP is converted to the campus AP image, you can end up in a situation where the AP will boot to the non-campus image and the AP doesn't behave as expected.

Downgrade from AOS 10 to AOS 8 should only be done when absolutely necessary.

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 18, 2024 10:18 AM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

Thank you, I can add as well that I noticed that this method worked for any Access-points I had running in Aruba Central, regardless of the fact that they were previously associated with the controller. 

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 09:45 AM
From: chulcher
Subject: Migration and Backout processes of Campus APs (half working)

New link for posterity: https://www.arubanetworks.com/techdocs/aos/aos10/migrate/aps/cap/#revert-to-aos-8-firmware-version

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 16, 2024 09:41 AM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

That was the missing piece, it worked!

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 15, 2024 04:52 PM
From: 802.zak
Subject: Migration and Backout processes of Campus APs (half working)

You will also have to convert the AP back to a CAP WAP. 

convert-aos-ap cap <controller-address>

Covered here - in Section "Revert to AOS 8 Firmware Version"

------------------------------
If my post was useful, please Accept Solution and Give Kudos.
------------------------------
Zak Chalupka
Principal Engineer - HPE Aruba
ACDX | ACMP | ACSP | ACCP
wifizak@hpe.com
------------------------------
Ideas expressed here are solely my own and not necessarily that of HPE Aruba.

Original Message:
Sent: Mar 15, 2024 04:43 PM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company
------------------------------

Not sure what is going on but the procedure I tested yesterday does not work  as flawlessly as today.

I created a dummy-AOS 8 group, set the firmware compliance but when I migrated two access-points (a 515 and a 345) to this group both did not come back online anymore.

I tested the 515 at my desk with console and there it got back online however TFTP which worked fine to upgrade the device yesterday refused to work today. The TFTP server provided logs stating connection dropped because peer didn't respond.

Eventually I was able to execute the step using ftp. I just find it strange that TFTP worked fine yesterday but not today. 

I like that method/result, and you should get consistent results as long as the DHCP scope is configured to instruct UAP/IAP APs to automatically convert to controller based.

Actually, not quite. When I used this method in Aruba Central and issued the command "show image version" the secondary Flash still had AOS10 running (see below)

If that method works for you, then sure.

Just a thought about the revert process. Would it be an idea to create a temporary AOS8 group on Aruba Central and before reverting AOS10 back to the local controller based version, downgrade to AOS8 from Aruba Central and then issue the conversion from Aruba Central? That way at least I would don't have this descrepancy:

So full backout process would be:

Step 1: Move AOS 10 AP to AOS8 group

Step 2: (When AP is reachable and booted from AOS8): aos-convert-ap cap <a.b.c.d>

Step 3: Reboot if required

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 12:42 PM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

thanks insightful

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 12:13 PM
From: chulcher
Subject: Migration and Backout processes of Campus APs (half working)

That particular command only works for those specific models, which is why I don't bother mentioning that as an option.

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 18, 2024 12:09 PM
From: VanD
Subject: Migration and Backout processes of Campus APs (half working)

Original Message:
Sent: 3/18/2024 11:54:00 AM
From: mvanoverbeek
Subject: RE: Migration and Backout processes of Campus APs (half working)

Thanks Carson

This is currently all simulation of course but I want to be sure when performing this in the production network I am not overlooking anything. 

I can see indeed that the backup is still set to AOS10 by issuing the show ap image version output below.

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 10:26 AM
From: Carson Hulcher
Subject: Migration and Backout processes of Campus APs (half working)

The command is used for converting any AP running IAP or AOS 10 to a campus AP.

Note, only one of the two images on the AP is converted to the campus AP image, you can end up in a situation where the AP will boot to the non-campus image and the AP doesn't behave as expected.

Downgrade from AOS 10 to AOS 8 should only be done when absolutely necessary.

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 18, 2024 10:18 AM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

Thank you, I can add as well that I noticed that this method worked for any Access-points I had running in Aruba Central, regardless of the fact that they were previously associated with the controller. 

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 18, 2024 09:45 AM
From: chulcher
Subject: Migration and Backout processes of Campus APs (half working)

New link for posterity: https://www.arubanetworks.com/techdocs/aos/aos10/migrate/aps/cap/#revert-to-aos-8-firmware-version

------------------------------
Carson Hulcher, ACEX#110

Original Message:
Sent: Mar 16, 2024 09:41 AM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

That was the missing piece, it worked!

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company

Original Message:
Sent: Mar 15, 2024 04:52 PM
From: 802.zak
Subject: Migration and Backout processes of Campus APs (half working)

You will also have to convert the AP back to a CAP WAP. 

convert-aos-ap cap <controller-address>

Covered here - in Section "Revert to AOS 8 Firmware Version"

------------------------------
If my post was useful, please Accept Solution and Give Kudos.
------------------------------
Zak Chalupka
Principal Engineer - HPE Aruba
ACDX | ACMP | ACSP | ACCP
wifizak@hpe.com
------------------------------
Ideas expressed here are solely my own and not necessarily that of HPE Aruba.

Original Message:
Sent: Mar 15, 2024 04:43 PM
From: mvanoverbeek
Subject: Migration and Backout processes of Campus APs (half working)

------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company
------------------------------