Hello, we have encountered a situation where replacing an IAP with a spare unit that is on older firmware and is in a default state can cause the existing IAP cluster to reassociate with this "new" AP and thus cause them to downgrade and wipe their config. We have had this happen in different scenarios, but it has happened during a refresh or scenario when the normal VC is offline.
Is there a way to configure the cluser to not re-home to another VC that is not part of the existing cluster and same firmware level? I am not sure if setting the preferred master option would accompish this or not. All of our IAP are managed by Airware as well.
IAP are on 6.5.1 code and Airwave is on 8.2.3.1.