Wireless Access

Reply
Occasional Contributor I
Posts: 5
Registered: ‎06-02-2016

Access Point uptime is not equal on all AP

We've 18 APs in Master - Local configurtation.

 

When i look into Monitoring > Access Points

i Found one Acess Point which uptime is less than a day while others is up for 20 days.

This is not the first time of this AP reboot.

 

Does any circumstance controller force AP to reboot?

 

Best Regards,

Supakij K.

 

Guru Elite
Posts: 8,460
Registered: ‎09-08-2010

Re: Access Point uptime is not equal on all AP

It may have lost network connectivity. It really could have been anything. Run: show log system 500 | include (ap-name) 

Tim Cappalli | Aruba Security TME
@timcappalli | timcappalli.me | ACMX #367 / ACCX #480
Guru Elite
Posts: 21,029
Registered: ‎03-29-2007

Re: Access Point uptime is not equal on all AP

Try this

 

show ap debug system-status ap-name Office-225 | begin Rebootstrap

Replace "Office-225" with the name of the AP.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor I
Posts: 5
Registered: ‎06-02-2016

Re: Access Point uptime is not equal on all AP

I don't understand what the output said. Are these messages mean that it reboot everyday without an info?

 

Thank you for reply 

 

(WLC1) #show log system 500 | include AP18 show log system 500 | include AP04 May 13 21:23:49 :303022: |AP AP04@192.168.100.244 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:07:37 PST 1999; SAPD: Unable to contact switch: HELLO-TIMEOUT. Last rebootstrap reason: IPSec not successful. Error: RC_OPCODE_MAX. Switching to clear, 265 sec before: Last Ctrl msg: HELLO len=1305 dest=192.168.100.10 tries=10 se May 13 21:25:33 KERNEL(AP04@192.168.100.244): RESTARTING ALL TX May 14 08:35:36 :303022: |AP AP04@192.168.100.244 nanny| Reboot Reason: No reboot message found.

May 14 08:35:36 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 14 08:37:16  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 17 11:17:26 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 17 11:19:05  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 18 08:39:59 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 18 08:41:39  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 18 10:08:22 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 18 10:10:02  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 18 15:52:09 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 18 15:53:48  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 19 05:06:18 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
--More-- (q) quit (u) pageup (/) search (n) repeat
                                                 
May 19 05:07:58  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 20 01:01:22 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 20 01:03:01  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 20 05:45:13 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 20 05:46:52  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 21 06:50:56 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 21 06:52:35  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 22 16:17:46 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 22 16:19:25  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 24 07:16:11 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 24 07:17:50  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 24 14:25:45 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 24 14:27:24  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 24 18:57:23 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 24 18:59:03  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
--More-- (q) quit (u) pageup (/) search (n) repeat
                                                 
May 24 21:08:12 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 24 21:09:52  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 25 02:59:31 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 25 03:01:11  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 25 14:52:09 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 25 14:53:49  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 27 10:19:01 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 27 10:20:40  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 28 16:18:09 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 28 16:19:49  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 28 22:11:13 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 28 22:12:53  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 29 00:58:28 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 29 01:00:08  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 29 13:03:22 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
--More-- (q) quit (u) pageup (/) search (n) repeat
                                                 
May 29 13:05:02  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 29 14:28:36 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 29 14:30:16  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 29 15:18:56 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 29 15:20:35  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 30 04:03:44 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 30 04:05:23  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 30 04:59:40 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 30 05:01:19  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 30 07:20:43 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 30 07:22:23  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 30 11:23:14 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 30 11:24:53  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 31 12:31:34 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 31 12:33:13  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
--More-- (q) quit (u) pageup (/) search (n) repeat
                                                 
May 31 12:50:30 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 31 12:52:10  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
May 31 23:08:47 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
May 31 23:10:26  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
Jun 1 05:56:18 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
Jun  1 05:57:57  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
Jun 1 14:29:49 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
Jun  1 14:31:28  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
Jun 1 16:56:46 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
Jun  1 16:58:26  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
Jun 2 00:37:11 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
Jun  2 00:38:51  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
Jun 2 05:51:58 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found.
Jun  2 05:53:37  KERNEL(AP04@192.168.100.244): RESTARTING ALL TX
Jun 2 09:29:14 :303022:  <WARN> |AP AP04@192.168.100.244 nanny|  Reboot Reason: No reboot message found

Occasional Contributor I
Posts: 5
Registered: ‎06-02-2016

Re: Access Point uptime is not equal on all AP

Thank you for reply but debug log information is very long i don't know which part i've to look for.

Guru Elite
Posts: 21,029
Registered: ‎03-29-2007

Re: Access Point uptime is not equal on all AP

If AP04 is the one with the problem, "no reboot message found" means that the reboot was unnatural; and the power was removed from the AP.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
Showing results for 
Search instead for 
Did you mean: