Wireless Access

Hello - 

We have a mixed fleet of Aruba 505 and 515 Instant Campus APs.  Last night, I performed the upgrade from 8.12.0.2 to 8.12.0.3, with the correct Gemini and Draco firmware files, via the URL method.  All the 505 models updated fine and restarted, but all our 515s are now disconnected from the virtual controller, and I cannot access any of them.

We can reach the 515's via their IP in the web interface, but cannot log in - the credentials that work on the virtual controller / 505 APs does not work, and the default "Admin / Serial Number" credentials don't work either.  Attempting to SSL to the 515's returns "Network Error: Connection Refused".

We do not have the serial cable for the 515s, and we do not use Central.  I factory reset one of the APs and can see the "Set-Me-Up" SSID, but I cannot determine what IP the AP reverts to  to attempt to access the web GUI or SSL.

Any insight is appreciated.

Try to login with admin/admin.  Factory defaulting an AP shouldn't change the IP that the device pulls upon reboot unless that DHCP lease has timed out and been given to something else in the meantime.

Hello - 

We have a mixed fleet of Aruba 505 and 515 Instant Campus APs.  Last night, I performed the upgrade from 8.12.0.2 to 8.12.0.3, with the correct Gemini and Draco firmware files, via the URL method.  All the 505 models updated fine and restarted, but all our 515s are now disconnected from the virtual controller, and I cannot access any of them.

We can reach the 515's via their IP in the web interface, but cannot log in - the credentials that work on the virtual controller / 505 APs does not work, and the default "Admin / Serial Number" credentials don't work either.  Attempting to SSL to the 515's returns "Network Error: Connection Refused".

We do not have the serial cable for the 515s, and we do not use Central.  I factory reset one of the APs and can see the "Set-Me-Up" SSID, but I cannot determine what IP the AP reverts to  to attempt to access the web GUI or SSL.

Any insight is appreciated.

Thank you - admin / admin turned out to be correct.  Our assumption was the default password would be admin / serial number as specified in documentation. 

Oddly, admin / admin worked on SSL but not for the web GUI.  From the SSL CLI, we confirmed the access point was still running the old firmware.  We used the "upgrade-image" command to update the firmware for the AP from the CLI, and reboot.  From there, we could factory reset it again and it connected to our virtual controller and re-provisioned as expected. 

Try to login with admin/admin.  Factory defaulting an AP shouldn't change the IP that the device pulls upon reboot unless that DHCP lease has timed out and been given to something else in the meantime.

Hello - 

We have a mixed fleet of Aruba 505 and 515 Instant Campus APs.  Last night, I performed the upgrade from 8.12.0.2 to 8.12.0.3, with the correct Gemini and Draco firmware files, via the URL method.  All the 505 models updated fine and restarted, but all our 515s are now disconnected from the virtual controller, and I cannot access any of them.

We can reach the 515's via their IP in the web interface, but cannot log in - the credentials that work on the virtual controller / 505 APs does not work, and the default "Admin / Serial Number" credentials don't work either.  Attempting to SSL to the 515's returns "Network Error: Connection Refused".

We do not have the serial cable for the 515s, and we do not use Central.  I factory reset one of the APs and can see the "Set-Me-Up" SSID, but I cannot determine what IP the AP reverts to  to attempt to access the web GUI or SSL.

Any insight is appreciated.

As you've found, there are some situations where the AP will end up in a situation where the old default username/password ends up being the working state.

Thank you - admin / admin turned out to be correct.  Our assumption was the default password would be admin / serial number as specified in documentation. 

Oddly, admin / admin worked on SSL but not for the web GUI.  From the SSL CLI, we confirmed the access point was still running the old firmware.  We used the "upgrade-image" command to update the firmware for the AP from the CLI, and reboot.  From there, we could factory reset it again and it connected to our virtual controller and re-provisioned as expected. 

Try to login with admin/admin.  Factory defaulting an AP shouldn't change the IP that the device pulls upon reboot unless that DHCP lease has timed out and been given to something else in the meantime.

Hello - 

We have a mixed fleet of Aruba 505 and 515 Instant Campus APs.  Last night, I performed the upgrade from 8.12.0.2 to 8.12.0.3, with the correct Gemini and Draco firmware files, via the URL method.  All the 505 models updated fine and restarted, but all our 515s are now disconnected from the virtual controller, and I cannot access any of them.

We can reach the 515's via their IP in the web interface, but cannot log in - the credentials that work on the virtual controller / 505 APs does not work, and the default "Admin / Serial Number" credentials don't work either.  Attempting to SSL to the 515's returns "Network Error: Connection Refused".

We do not have the serial cable for the 515s, and we do not use Central.  I factory reset one of the APs and can see the "Set-Me-Up" SSID, but I cannot determine what IP the AP reverts to  to attempt to access the web GUI or SSL.

Any insight is appreciated.