: Ensure that both the conductor AP and the new AP are running exactly the same sub‑release (e.g., 8.8.x.x, down to the patch number). If automatic upgrade fails, manually load the same image onto the new AP via the WebUI or TFTP. Additionally, verify that auto‑join is enabled and that the new AP’s MAC address is present in the allowed list on the virtual controller.
Do not use AOS 10.3.0.x with AP-505. That branch contains a known DFS (Dynamic Frequency Selection) false-positive bug causing radio flapping. aruba ap 505 firmware top
| Symptom | Likely Cause | Resolution | |---------|--------------|-------------| | AP stuck in "Upgrading" | Corrupted image or low flash | TFTP recovery via console | | 5 GHz radio missing after upgrade | Regulatory domain mismatch | Re-apply country code & reboot | | Clients failing WPA3 | Older Windows/mobile drivers | Downgrade to WPA2/3 transition mode or upgrade client drivers | | Cluster split-brain | Uplink latency + bug in 8.7.x | Upgrade to 8.10.x or use static VC IP | : Ensure that both the conductor AP and
Select , browse to your downloaded binary, and click Upgrade Now . Do not use AOS 10
If you run your AP-505s in a cluster without a physical hardware controller, you are using InstantOS (Gemini architecture).