NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
__EHH__
Oct 29, 2023Tutor
WAC540 access-point suddenly reboots multiple times a day.
Dear ppl,
This WAC540 AccessPoint is powered by a Netgear GS116PP PoE/PoE+ switch, which is powered by a 200 Watt adapter, giving this Switch a total PoE budget of 183 Watt. The WAC540 is the only PoE/PoE+ device powered by this Switch. The Switch doesn't complain that its max PoE budget is exceeded.
I have used this combination of Switch and AccessPoint for over 6 months in my current home w/o any problems and, before that, it worked absolutely fine since June 2020 in my previous home with the same Switch powering it.
Since a week or two the WAC540 reboots multiple times a day which is very annoying since my modem/router/wifi is located many meters away from the spot where I use my mobile devices. To give you an idea: this morning the WAC540 rebooted at 10:32, 11:03, 11:25, 11:52, 12:33, 12:43, 12:53, 13:03, 13:15.
The WAC540 has f/w V9.9.1.3 installed which is the latest. Should I switch back to an older f/w? Is that even an option? I do regularly have the WAC540 check whether a new f/w is available.
I did a factory reset on the WAC540 and re-configured it again for my use.
I searched this website for similar issues with the WAC540 and I checked whether Band Steering was disabled.
Any suggestions to make the WAC540 behave like it used to do are appreciated.
Devices that use the WAC540 are 2 iPhones, 1 iPad and 1 MacBook.
Edwin
BTW: below is a line from the LOG of the WAC540:
Sun Oct 29 12:34:44 CET 2023 nddmp[3346]: alarm : seqNo-[8], level-[MINOR], info-[Reboot reason - Unknown]
12 Replies
- schumakuGuru - Experienced User
Hello Edwin,
As it's impossible to state we're facing a hardware issue here, being on the GS116PP or the WAX540. What I would do is to run a syslog server at the customers location, and capture all syslog sent by the WAX540 in question. In absence of an easy accessible console port this is the maximum one could do. Easy to say, in absence of a better option. Potentially, Netgear support can arrange some specially crafted diagnostics firmware hnagaraju BruceGuo JohnC_V please.
Sorry, hardcore engineer here, tend to run a syslog and collect everything on my networks with syslog capabilities we can collect for operational and security reasons.
- __EHH__Tutor
Thank you schumaku for your suggestion.
It took me a while to find a free syslog-server but managed to find one that works on my MacBook (SysLogCenter by Lan-Secure).
After 3 1/2 hour the Accesspoint rebooted and I managed to save all the events and notifications recorded by the syslog server. The TXT file is 909kB in size, can I post it here?
The first few events recorded are listed below. The WAC540 has IP address 192.168.1.3 and my Router is 192.168.1.1.
Edwin
2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077847] NULL2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077842] LCI_allow_list:2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077834] [wifi0vap2]IEEE80211_LCI_ADD_NW_INFO flag=0, GW=16885952, netmask=16777215, AP_IP=0 updated in vap table2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077820] [wifi0vap2]IEEE80211_LCI_ADD_NW_INFO GW=192.168.1.1, netmask=255.255.255.0, AP_IP=0.0.0.0 updated in vap table2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077801] IEEE80211_LCI_ADD_NW_INFO 16885952, 16777215 updated in vap table2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077790] CONFIG->GW=16885952 CONFIG->AP=0 CONFIG->NETMASK= 16777215,FLAG=02023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077771] VAP->GW=0, VAP->AP=0, VAP->netmask =0, flag=02023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077652] NULL2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077646] LCI_allow_list:2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077639] [wifi0vap1]IEEE80211_LCI_ADD_NW_INFO flag=0, GW=16885952, netmask=16777215, AP_IP=0 updated in vap table2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077626] [wifi0vap1]IEEE80211_LCI_ADD_NW_INFO GW=192.168.1.1, netmask=255.255.255.0, AP_IP=0.0.0.0 updated in vap table2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077607] IEEE80211_LCI_ADD_NW_INFO 16885952, 16777215 updated in vap table2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077595] CONFIG->GW=16885952 CONFIG->AP=0 CONFIG->NETMASK= 16777215,FLAG=02023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077579] VAP->GW=0, VAP->AP=0, VAP->netmask =0, flag=02023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077408] NULL2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077402] LCI_allow_list:2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077394] [wifi0vap0]IEEE80211_LCI_ADD_NW_INFO flag=0, GW=16885952, netmask=16777215, AP_IP=0 updated in vap table2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077380] [wifi0vap0]IEEE80211_LCI_ADD_NW_INFO GW=192.168.1.1, netmask=255.255.255.0, AP_IP=0.0.0.0 updated in vap table2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077360] IEEE80211_LCI_ADD_NW_INFO 16885952, 16777215 updated in vap table2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077347] CONFIG->GW=16885952 CONFIG->AP=0 CONFIG->NETMASK= 16777215,FLAG=02023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077323] VAP->GW=0, VAP->AP=0, VAP->netmask =0, flag=02023-10-30 12:45:09 User.Error 192.168.1.3 syslog: apply_lci_parameters:1086 called brtrunk-192.168.1.3-192.168.1.1-255.255.255.0--- schumakuGuru - Experienced UserThe interesting entries I'd expect would be the last 10....30 entries before the WAC540 does restart, like crash dump information if any.
- CyrilFAspirant
Hello
Same probem witch WAC540 insight managed with firmware 9.9.1.3
Multiple "Reboot reason - Unknown" per day
Any solution ?
Thx- __EHH__Tutor
Hi
Short answer: no, no solution yet.I realised I never registered the AP and so I did and noticed the device was still under warranty. I opened a support case with the Netgear Support and talked to someone over the phone and - after a few questions - he suggested to swap the AP for a new sample.I received the new sample and upon installing and setup I had high hopes as it was WAY more responsive compared to the old one. I sometimes needed 3 attempts to setup the old AP as it wouldn’t accept my inputs (you know the Day Zero Easy Setup with Country, DHCP enable/disable, password to access the AP, SSID etcetera).Setting up the new AP was a breeze (like the old one used to be) but the reboots are still there. They are more rare but still do happen a few times per day, whereas the old AP sometimes rebooted every 10 minutes.The new AP is running f/w V8.0.0.36 btw and I havent updated it.I just started running a syslog server to capture the reboot events to see whether the cause is still the same. Later I will open a new support case.EdwinBtw: kudos to the Netgear support team. On Monday I delivered the old AP to a local UPS service point and I received the new AP on Thursday 👍👍- CYRMIL59Aspirant
Thanks
i opened a ticket too ..
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!