Hi there, we have a number of remote branch locations, all connected to head office via WAN links, and we have a virtual hivemanager appliance located in head office
When setting up one of our remote branches with wifi, I preconfigure the APs in head office, upload the configuration to the AP, but I don't reboot the AP to apply the config, I just unplug the AP after the configuration upload and send it to the remote site
My understanding is that the uploaded configuration is placed in the backup partition initially, and upon AP startup the current and backup configs are swapped, so the previously uploaded config in the backup partition is now the 'current' config, and the AP will load that
This seems to work most of the time, but sometimes the AP indicator light doesn't go white and I'm not sure why, and I'm not sure what happens to the configuration after that
My question is in a few parts - firstly, is this a valid approach for pre-configuring APs for remote sites?
If the AP wasn't able to make a CAPWAP connection to the hivemanager, does that constitute a failed config load?
If so, and if my uploaded config file is moved to the failed partition, does the AP ever try to re-use it, or does it require administrator intervention to bring the config out of the failed partition and back into the backup or current partition?
The Aerohive Deployment Guide seems light on detail in this area