The controller runs the AP Preload Image flow and will instruct the AP to load software based on whichever partition is chosen to be used as the source. The version will not matter, assuming you aren't attempting to use a software version where the AP is unsupported, the controller will just use the software at that partition.
Once a preload job is started the controller must be rebooted to clear the state of any APs that have completed the preload. You cannot double preload any one AP. Completing or cancelling a job will allow for creating another job for loading software on other APs that weren't completed or done.
APs will always pull the current running software image from the controller if there is a version mismatch between the two devices. AP Preload Image is there to reduce the amount of time required for that AP image upgrade upon controller reboot.
------------------------------
Carson Hulcher, ACEX#110
------------------------------
Original Message:
Sent: Jan 05, 2024 10:22 AM
From: cauliflower
Subject: Understanding AP image preload
Hello,
I am looking at using the API to start the AP image preload process (we have several controllers so being able to script this would be handy, the API looks like it'll do it). My queries are really about how ap image preload behaves, mainly so I know the expected behaviour when I'm testing:
- What happens if you try to preload an image that the AP is currently running (or an image that has already been pre-loaded to an AP)? Does it just skip that AP?
- Can you preload a previous version (ie downgrade)?
- What happens if you get part way through a pre-load (ie some APs have completed the pre-load) and then cancel it? How do you get back to your original state? Do you just run ap image preload again but with the previous image partition so that all APs revert to the original?
- What happens if the controller reloads part-way through the preload (but doesn't upgrade) - so some APs would boot into the new version - can these APs come up?
Thank you,
Guy