Connect to the AP’s WebUI or CLI and set the preference role to controller-less. In the WebUI, go to Maintenance > Access Point > Convert to instant mode .
If using a Mobility Controller, always verify that your controller firmware version is equal to or higher than the minimum supported version required by the AP-505 hardware baseline.
: You can set a "Firmware Compliance" policy to ensure any new AP added to a group automatically upgrades to a specific version. 2. Via Virtual Controller (Instant Mode) For local, controllerless clusters:
Use Aruba Central for automated, scheduled firmware rollouts if you have more than a handful of APs.
Ensure you downloaded the image. Verify the MD5/SHA256 checksum of the file. AP stuck in boot loop Corrupt flash partition or power deficiency.
The AP-505 requires ArubaOS or Aruba Instant version 8.6.0.0 or later. Version 8.6.x was the first to support the AP-505. This is also the last version to support older APs like the AP-105.
Aruba APs can operate under different architectures, impacting the firmware version you should use:
The hardware is identical, but the firmware images are different. Installing the wrong image (e.g., Instant firmware on a campus-mode AP) will brick the device until corrected via console cable.
AOS 10 represents a paradigm shift. It eliminates the traditional "Instant" local virtual controller.