In this guide, you will learn how to factory reset an Aruba 505 Access Point, identify its IP address using a DHCP server, and establish an SSH connection to manage the device via the CLI.
To ensure a clean configuration, we begin by factory resetting the Aruba 505 AP. This process requires physical access to the device.
Unplug the power cable from the Access Point. Press and hold the physical reset button (usually located near the Ethernet port).
While holding the reset button, plug the power cable back in. Continue holding the button for approximately 10 to 15 seconds until the LED starts flashing.
Once the light flashes, release the button. The AP will go solid green briefly, cycle its power, and eventually begin flashing again to indicate the reset is in progress.
The easiest way to connect to a factory-reset Aruba AP is to place it on a network with a DHCP server. In this example, we use a FortiGate firewall, but any router or DHCP server will work.
Plug an Ethernet cable into the Access Point and connect it to your LAN.
The AP will flash while it attempts to provision. Wait until the LED turns solid green. This indicates it has stopped trying to provision externally and has entered "Instant AP" mode.
Log into your router or firewall's web interface and navigate to the DHCP monitor or lease table. Look for the new device (often labeled "Aruba") to find its assigned IP address.
Once you have the IP address (e.g., 192.168.1.11), you can connect using an SSH client like PuTTY.
Open PuTTY, enter the IP address, and ensure Port 22 is selected. Click Open.
For most modern Aruba Access Points, the default credentials are as follows:
Copy the serial number from the sticker on the back of the AP and paste it into the password field.
Upon the first successful login, the system will immediately prompt you to set a new management password. Enter and confirm your new password to proceed.
Once logged in, you can use the command line to troubleshoot or verify settings.
To see the current image version and model information:
show versionTo see a list of all available commands, simply type a question mark:
?If the AP is not connecting to a controller as expected, you can view the provisioning logs to identify errors (e.g., DNS or DHCP failures).
show log provision