NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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 o...
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.
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] NULL
2023-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 table
2023-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 table
2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077801] IEEE80211_LCI_ADD_NW_INFO 16885952, 16777215 updated in vap table
2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077790] CONFIG->GW=16885952 CONFIG->AP=0 CONFIG->NETMASK= 16777215,FLAG=0
2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077771] VAP->GW=0, VAP->AP=0, VAP->netmask =0, flag=0
2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077652] NULL
2023-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 table
2023-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 table
2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077607] IEEE80211_LCI_ADD_NW_INFO 16885952, 16777215 updated in vap table
2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077595] CONFIG->GW=16885952 CONFIG->AP=0 CONFIG->NETMASK= 16777215,FLAG=0
2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077579] VAP->GW=0, VAP->AP=0, VAP->netmask =0, flag=0
2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077408] NULL
2023-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 table
2023-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 table
2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077360] IEEE80211_LCI_ADD_NW_INFO 16885952, 16777215 updated in vap table
2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077347] CONFIG->GW=16885952 CONFIG->AP=0 CONFIG->NETMASK= 16777215,FLAG=0
2023-10-30 12:45:09 Kernel.Informational 192.168.1.3 kernel: [ 62.077323] VAP->GW=0, VAP->AP=0, VAP->netmask =0, flag=0
2023-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--
- The interesting entries I'd expect would be the last 10....30 entries before the WAC540 does restart, like crash dump information if any.
Thanks again. I logged the messages during 3 reboots today. The avalanche of log entries starts in all three cases after this entry:
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--
In the picture attached are the syslog entries immediately prior to the line above for 3 reboots (12:44, 14:48 and 15:24)
Edwin
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
