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.