Forum Discussion

Aspirant

Jul 15, 2017

Solved

WAC510 Frequent power cycling

I bought a 3 pack of WAC510's. I installed them and am happy with their performance. Up until recently everything worked as expected but i believe since the firmware update 1.2.5.12 my AP's started r...

Firmware

Troubleshooting

Dsmalley
Jul 21, 2017
At Raghu's suggestion I turned RRM off on both devices and that appears to have done the trick. Both of WAPs have been up for 3+ days with no restarts.

Sounds like there might be a bug in RRM that will get addressed with the next update.

Disabling this hasn't appeared to significantly impact our network performance, although andecodally one android client user is complaining that his device is not acquiring/holding connections as well. Could easily be something else going on there.

Dsmalley

Tutor

Jul 17, 2017

I've been experiencing the exact same issue with my two WAC510s. They are also on 1.2.5.12 but I noticed this occurring on 1.2.5.11 as well but wasn't noting the frequency as closely.

My devices are wired via poe to a GS108PEv3 and share the same SSID.

I have attempted to identify a pattern but can't see any. Traffic is always very low on our network so it doesn't seem activity related?

It's a significant issue - they are rebooting > 10 times per day.

Log snippet - any way to increase the verbosity?

Sun Jul 16 20:51:22 CDT 2017 nddmp[2148]: alarm : seqNo-[1], level-[INFO], info-[System UP]
Sun Jul 16 20:51:22 CDT 2017 nddmp[2148]: alarm : seqNo-[2], level-[INFO], info-[Reboot reason - WDT]
Sun Jul 16 20:51:22 CDT 2017 nddmp[2148]: alarm : seqNo-[3], level-[INFO], info-[Radio 2.4GHz On]
Sun Jul 16 20:51:22 CDT 2017 nddmp[2148]: alarm : seqNo-[4], level-[INFO], info-[Radio 5GHz On]
Sun Jul 16 20:51:22 CDT 2017 nddmp[2148]: alarm : seqNo-[5], level-[INFO], info-[00-23-CC-56-C3-DD connected]
Sun Jul 16 20:51:22 CDT 2017 nddmp[2148]: alarm : seqNo-[6], level-[INFO], info-[28-56-5A-3A-0D-FC connected]
Sun Jul 16 20:51:22 CDT 2017 nddmp[2148]: alarm : seqNo-[7], level-[INFO], info-[00-25-4B-99-08-7C connected]
Sun Jul 16 20:51:22 CDT 2017 nddmp[2148]: alarm : seqNo-[8], level-[INFO], info-[88-66-A5-6D-10-77 connected]
Sun Jul 16 20:51:22 CDT 2017 nddmp[2148]: alarm : seqNo-[9], level-[INFO], info-[F4-31-C3-1F-5D-03 connected]
Sun Jul 16 20:51:22 CDT 2017 nddmp[2148]: alarm : seqNo-[10], level-[INFO], info-[B8-E9-37-EA-D9-82 connected]
Sun Jul 16 20:51:22 CDT 2017 nddmp[2148]: alarm : seqNo-[11], level-[INFO], info-[C0-33-5E-E9-F2-3D connected]
Sun Jul 16 20:51:22 CDT 2017 nddmp[2148]: alarm : seqNo-[12], level-[INFO], info-[8C-F5-A3-BA-E0-30 connected]
Sun Jul 16 20:51:26 CDT 2017 hostapd: wifi0vap0: STA 40:b4:cd:84:2b:69 IEEE 802.11: associated
Sun Jul 16 20:51:26 CDT 2017 hostapd: wifi0vap0: STA 40:b4:cd:84:2b:69 WPA: pairwise key handshake completed (RSN)
Sun Jul 16 20:51:26 CDT 2017 nddmp[2148]: alarm : seqNo-[13], level-[INFO], info-[40-B4-CD-84-2B-69 connected]
Sun Jul 16 20:51:27 CDT 2017 syslog: password matched
Sun Jul 16 20:53:55 CDT 2017 syslog: password matched

Dsmalley
Tutor
Jul 17, 2017
Detailed log file is here:
https://eleventwenty-my.sharepoint.com/personal/dougsmalley_eleventwenty_com/_layouts/15/guestaccess.aspx?docid=014700a1ace014047be1a202080fac005&authkey=AXhxFigHHFqjJvuAfFGM8iY

WAP config is here:
https://eleventwenty-my.sharepoint.com/personal/dougsmalley_eleventwenty_com/_layouts/15/guestaccess.aspx?docid=07e28cf4e49364b7ca4ea2e85841c64d0&authkey=ASbNP_U7TdJ_L6X5fjyUVDU
- BoT
  Aspirant
  Jul 17, 2017
  Thanks Dsmalley, i am glad i am not the only one. i also noticed that you have the same message "[Reboot reason - WDT]" in your log.
  i hope we can find out what WDT is.
  
  Ssome more info on my APs had firmware 1.2.5.1 to 1.2.5.11 and now 1.2.5.12.
  I have one with power adapter and one with PoE.
  - Dsmalley
    Tutor
    Jul 17, 2017
    I think "WDT" refers to a "watchdog timer" (see wiki). If so then I think this points to some pile of errors or some other threshold condition that is getting hit making the devices decide to reboot.
    
    Hopefully the support team can figure it out looking at the detailed logs and config and it's just something simple with the setup/config.