Wireless Access

 Hi,

 I have a problem with some access points in my network. They are rebooting randomly and the logs doesn´t teach us a reason.

Nowadays, we have some access points connected through a Cisco switch and a few of them connected directly to the controller.

We only have problems with the aps connected to the controller.

The controller version is 5.0.4.1.

Any ideas?

Thanks

show log network 100

Feb 19 08:24:10 :209801:  <WARN> |fpapps|  Physical link down: port 1/0
Feb 19 08:24:28 :209801:  <WARN> |fpapps|  Physical link down: port 1/2
Feb 19 08:24:43 :209801:  <WARN> |fpapps|  Physical link down: port 1/4
Feb 19 08:24:49 :209801:  <WARN> |fpapps|  Physical link down: port 1/5
Feb 19 08:25:04 :209801:  <WARN> |fpapps|  Physical link down: port 1/7
Feb 19 08:25:12 :209801:  <WARN> |fpapps|  Physical link down: port 1/0
Feb 21 06:03:31 :209801:  <WARN> |fpapps|  Physical link down: port 1/0
Feb 21 06:03:31 :209801:  <WARN> |fpapps|  Physical link down: port 1/1
Feb 21 06:03:31 :209801:  <WARN> |fpapps|  Physical link down: port 1/2
Feb 21 06:03:31 :209801:  <WARN> |fpapps|  Physical link down: port 1/3
Feb 21 06:03:31 :209801:  <WARN> |fpapps|  Physical link down: port 1/4
Feb 21 06:03:31 :209801:  <WARN> |fpapps|  Physical link down: port 1/5
Feb 21 06:03:31 :209801:  <WARN> |fpapps|  Physical link down: port 1/6
Feb 21 06:03:31 :209801:  <WARN> |fpapps|  Physical link down: port 1/7
Feb 21 06:05:39 :209801:  <WARN> |fpapps|  Physical link down: port 1/7
Feb 21 06:06:07 :209801:  <WARN> |fpapps|  Physical link down: port 1/1
Feb 22 02:29:23 :209801:  <WARN> |fpapps|  Physical link down: port 1/0
Feb 22 02:29:23 :209801:  <WARN> |fpapps|  Physical link down: port 1/1
Feb 22 02:29:23 :209801:  <WARN> |fpapps|  Physical link down: port 1/2
Feb 22 02:29:23 :209801:  <WARN> |fpapps|  Physical link down: port 1/3
Feb 22 02:29:23 :209801:  <WARN> |fpapps|  Physical link down: port 1/4
Feb 22 02:29:23 :209801:  <WARN> |fpapps|  Physical link down: port 1/5
Feb 22 02:29:23 :209801:  <WARN> |fpapps|  Physical link down: port 1/6
Feb 22 02:29:23 :209801:  <WARN> |fpapps|  Physical link down: port 1/7
Feb 22 02:30:31 :209801:  <WARN> |fpapps|  Physical link down: port 1/0
Feb 22 02:30:40 :209801:  <WARN> |fpapps|  Physical link down: port 1/1
Feb 22 02:30:55 :209801:  <WARN> |fpapps|  Physical link down: port 1/3
Feb 22 02:31:03 :209801:  <WARN> |fpapps|  Physical link down: port 1/4
Feb 22 02:31:18 :209801:  <WARN> |fpapps|  Physical link down: port 1/6

Feb 19 08:23:48 :311002:  <WARN> |AP PPAL-P3-1@172.16.56.20 sapd|  Rebooting: SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Feb 19 08:23:49 :303086:  <ERRS> |AP PPAL-P3-1@172.16.56.20 nanny| Process Manager (nanny) shutting down - AP will reboot!
Feb 19 08:24:02 :311002:  <WARN> |AP PPAL-P2-2@172.16.56.19 sapd|  Rebooting: SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Feb 19 08:24:03 :303086:  <ERRS> |AP PPAL-P2-2@172.16.56.19 nanny| Process Manager (nanny) shutting down - AP will reboot!
Feb 19 08:24:07 :311002:  <WARN> |AP PPAL-P3-2@172.16.56.21 sapd|  Rebooting: SAPD: Unable to contact switch. Called by sapd_hello_cb:4
Feb 19 08:24:08 :303086:  <ERRS> |AP PPAL-P3-2@172.16.56.21 nanny| Process Manager (nanny) shutting down - AP will reboot!

Feb 22 02:30:49 :303022:  <WARN> |AP PPAL-S0-2@172.16.56.12 nanny|  Reboot Reason: No reboot message found.
Feb 22 02:30:56 :303022:  <WARN> |AP PPAL-S0-1@172.16.56.11 nanny|  Reboot Reason: No reboot message found.
Feb 22 02:31:19 :303022:  <WARN> |AP PPAL-P0-2@172.16.56.14 nanny|  Reboot Reason: No reboot message found.
Feb 22 02:31:26 :303022:  <WARN> |AP PPAL-P1-2@172.16.56.17 nanny|  Reboot Reason: No reboot message found.
Feb 22 02:31:32 :303022:  <WARN> |AP PPAL-P0-1@172.16.56.250 nanny|  Reboot Reason: No reboot message found.
Feb 22 02:31:33 :303022:  <WARN> |AP PPAL-P0-3@172.16.56.15 nanny|  Reboot Reason: No reboot message found.
Feb 22 02:31:41 :303022:  <WARN> |AP PPAL-P2-1@172.16.56.18 nanny|  Reboot Reason: No reboot message found.

Hi,

• It's seems that there are ports in your controller that going down once in a while. (and it's a good reason why some AP will not be able to contact your controller)..its becasue the watchdog of ap doing restart to the unit..or because thoese units unable to contact your switch(controller)  from some reason
  
• so your are using POE? is the distance between the AP to the controller (the problematic ap  units) dosent pass 100meters?

and also my advise :smileywink: - upgrade to a newer AOS version (5.0.4.9) and check if the ap reboot : unknown error continue.

Update us

*i added for u the release notes - pay attention - there are look of fixes since the AOS your are using.

Attachment(s)

ArubaOS 5.0.4.9 Release Notes.pdf   686 KB 1 version

Hi,

yes, the port is going down, but why? The other access point in a cisco switch are working well.

The access points that are failing are connected directly to the controller.

They are all powered by the controller through PoE.

The wire meters are fewer than 100m. I am sure.

I have other controllers with the same AOS version working fine.

In any case, I´ll upgrade to a newer version.

 Thanks for your answer

How many access points are powered by this controller and what controller model do you have?

 Hi cjoseph,

 This controller is a OAW-4324 and I have directly connected only 8 aps. The other 6 aps are connected through a Cisco switch.

  Thanks

on the commandline type show poe.

Here is:

(ssssss) #show poe

PoE Status
----------
Port     Status  Voltage(mV)  Current(mA)  Power (mW)
----     ------  -----------  -----------  ----------
FE 1/0   On      47838        63           2800
FE 1/1   On      47902        59           2619
FE 1/2   On      47870        54           2626
FE 1/3   On      47870        55           2798
FE 1/4   On      47870        54           3064
FE 1/5   On      47966        56           2639
FE 1/6   On      47966        62           2908
FE 1/7   On      47870        62           2826
FE 1/8   Off     N/A          N/A          N/A
FE 1/9   Off     N/A          N/A          N/A
FE 1/10  Off     N/A          N/A          N/A
FE 1/11  Off     N/A          N/A          N/A
FE 1/12  Off     N/A          N/A          N/A
FE 1/13  Off     N/A          N/A          N/A
FE 1/14  Off     N/A          N/A          N/A
FE 1/15  Off     N/A          N/A          N/A
FE 1/16  Off     N/A          N/A          N/A
FE 1/17  Off     N/A          N/A          N/A
FE 1/18  Off     N/A          N/A          N/A
FE 1/19  Off     N/A          N/A          N/A
FE 1/20  Off     N/A          N/A          N/A
FE 1/22  Off     N/A          N/A          N/A
GE 1/24  Off     N/A          N/A          N/A
GE 1/25  Off     N/A          N/A          N/A


Total Power Usage: 22280 (mW)

The "unable to contact switch" message suggests that there is a connectivity issue between your access points and the controller and they rebooted.  You probably have to open a support case to get to the bottom of that.