Wireless Access

Hi Team.

I install a new wireless infrastructure with aruba 315 AP models, with 6 units.

I have one of them is rebooting randomly, all APs are on the Version 8.3.0.6.

Does anyone have any ideia why and how do I resolve this?

The AP is connected to the PoE converter that came with the AP. My switch don't have PoE ports.

Sounds like they are not getting an IP Address or didn´t find the controller.

Are you using Instant (IAP-315) or controllerbase (AP-315) APs?

The AP gain IP everytime, and we are using controllerbase (AP-315) APs.

I am monitoring the APs and one of them from no reasing stop responding severeal times during the day.

Today already fail more then 12 times.

Normally an AP when it reboots, it will log a reason into the controller:

#show log all | include "Reboot"
May 18 23:16:21  nanny[2314]: <303022> <WARN> |AP HR-RAP-DV15@192.168.37.140 nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:33:36 PST 1969; Unable to set up IPSec tunnel after 85 tries
May 27 22:37:38  sapd[2771]: <311002> <WARN> |AP NLPD-AP315@192.168.31.76 sapd|  Rebooting: Reboot requested by controller
May 27 22:37:43  sapd[2771]: <311002> <WARN> |AP NLPD-AP315@192.168.31.76 sapd|  Rebooting: SAPD: Reboot requested by controller
May 27 22:39:17  nanny[2748]: <303022> <WARN> |AP NLPD-AP315@192.168.31.76 nanny|  Reboot Reason: AP rebooted Mon May 27 22:37:44 CEST 2019; SAPD: Reboot requested by controller

Do you see logs like those in your controller? The reboot reason may point you in the right direction.

Please check the POE injector (we would not have included one with the AP, it would have been purchased separately (if from Aruba a PowerDsine model) and if not purchased from Aruba we would want the make/model. Also you may try to replace the cable if it's super long or if it's not testing out well. 

As Herman notes, in the controller there should be a reason for reboot.

This infastructure is far away from my office.

I will provide to check the cables and the PoE injector.

When I test update the information.

Thanks

To give the update from the problem.

We change the cables and the problem persist.

We change the PoE injector and the problem persist.

The PoE injector was connected to a switch TL-SG5428, we remove the PoE injector and change the connection to other type of switch WITH PoE, and the problem was solved.

Thank you all.