I recently got my hands on an enterprise-grade Aruba AP-325 access point. It is solid hardware, but it comes with a catch: it requires an Aruba campus controller, which I do not have in my lab.
In this guide, I will show you step-by-step how to convert an Aruba AP-325 into a standalone Instant AP (IAP) that runs completely unmanaged without any central controller.
What you need
- Aruba AP-325 access point
- Serial interface (a native RS-232 port or a reliable USB-to-RS232 adapter)
- Terminal emulator (e.g., PuTTY)
- TFTP server (e.g., OpenTFTPServer)
- Aruba Instant firmware image
Fetching firmware without registration
You do not need an active HPE or Aruba support contract to download the image. You can pull it directly from their public firmware endpoint:
http://common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP/ArubaInstant_Hercules_8.10.0.16_92046
This link points to version 8.10.0.16 (Hercules platform), which is the latest release supported on the AP-325. If you need a specific older release (like 8.10.0.7_83877), simply swap the filename at the end of the URL.
Console cable and RS-232 adapter notes
During my setup, I ran into communication issues using a cheap PL2303 adapter. PuTTY was outputting random garbled characters despite correct baud rate settings. Aruba console ports expect standard RS-232 voltage levels, so make sure to use a proper RS-232 interface.
Making a custom RJ45-to-DB9 console cable is straightforward. Here is the working pinout:
| RJ45 Pin | RS232 Signal |
|---|---|
| Pin 1 | – |
| Pin 2 | – |
| Pin 3 | RxD |
| Pin 4 | GND |
| Pin 5 | GND |
| Pin 6 | TxD |
| Pin 7 | – |
| Pin 8 | – |
A standard Cisco RJ45-to-DB9 rollover cable should also work out of the box.
Step-by-step conversion
1. Set up the TFTP server
Download and run OpenTFTPServer. Place the downloaded firmware binary (ArubaInstant_Hercules_8.10.0.16_92046) into your TFTP root directory (e.g., C:\OpenTFTPServer\).
2. Connect to the device
Connect the serial cable, configure your terminal to 9600 baud (8N1), and power on the AP. As soon as you see the prompt, press Enter:
Hit <Enter> to stop autoboot: 3
The prompt will change to apboot>, confirming you are in the U-Boot bootloader environment.
3. Set the country code (critical step)
An Aruba AP running Instant firmware will not start its wireless radios without a valid country code hash stored in its system inventory.
Generate a SHA1 hash of your region string formatted as RW-<SERIAL_NUMBER> (for Rest of World) or US-<SERIAL_NUMBER> (for United States). You can use any CLI or online SHA1 encoder.
Example string for serial number CN12345678: RW-CN12345678
Apply the command in apboot:
For Rest of World (RW):
proginv system ccode CCODE-RW-<your_sha1_hash>
For United States (US):
proginv system ccode CCODE-US-<your_sha1_hash>
4. Configure networking
Acquire an IP address via DHCP:
dhcp
Or configure a static IP address manually:
setenv ipaddr 192.168.1.2
Then set your TFTP server IP address:
setenv serverip <tftp_server_ip>
5. Flash firmware to both OS partitions
To make sure the AP does not revert to the old controller-based firmware, flash the Instant firmware image to both partition 0 and partition 1:
upgrade os 0 ArubaInstant_Hercules_8.10.0.16_92046
upgrade os 1 ArubaInstant_Hercules_8.10.0.16_92046
6. Save environment and reset
Perform a factory reset, save environment variables, and reboot the unit:
factory_reset
saveenv
reset
Summary
After rebooting, the access point will load Aruba Instant OS. It will either obtain an IP on your network or broadcast the default SetMeUp provisioning Wi-Fi network.
Converting decommissioned enterprise hardware like the AP-325 is a great way to get fast, enterprise-grade Wi-Fi for your home lab without controller licensing fees.