This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
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 restarting about once a day and usually in the middle of the day. In the last couple days it happened even more frequently. All AP's have the same and latest firmware.
i checked the logs and this is the only thing i could find that might have seemed a bit abnormal:
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.
Hi Edward
Welcome to the Netgear Community. Apologize for your issue. Can you confirm your previous firmware 1.2.5.11 and it there you found no issues right?
Did you observed any sequence in this AP restart? What I am trying to understand here to see if you connect any particular wireless client then AP is restarting ? or any particular traffic is causing this? (like skype video call , youtube etc?)
Can you please download the detailed from log from the monitoring page and share? Also attach AP configuration to debug further,
Thanks
Raghu
Thanks Raghu, i have not noticed a recognizable pattern in the power cycles. I did notice that all APs do it at just about the same time. Almost in sync. There are over a dozen devices connected so it is hard to tell whih device or type of traffic this might cause. We do watch Youtube but Skype rarely. There are multiple tablets, phones, 1 Xbox One and a Nest connected to it. There are also some Nest Protect devices connected and some other smarthome devices that don't occupy the APs in the house.
i got the config and log file as a .tar.gz but i do not see an option to upload it
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.
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.
Thanks for sharing additional details. I guess power source is not the culprit based on your description (PoE connected/with power adapter)
Have you ever tried any other firmware & see AP is not restarting apart from those you have mentioned? I have sent you PM regarding config and log files.
@Dsmalley Sorry it appears the logs and config file are removed/moved from your shared location. I have PMd you too.
Kindly note that we are actively workig on this issue with top most priority
Also - I installed kiwi, enabled syslog, and attached that log data as well. It looks like one of the devices restarted 3 times overnight - very low / no activity.
Are you seeing the WAC510 restart and after restart wireless clients do not reconnect to WAC510 . I'm just trying to understand your issue in more detail. Nice if you can add more details
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.
