[NEBULA] smart-mesh event: Repeater AP Disconnected cause by Beacon miss
Hello ZyXel staff
This is the continuation of my previous post, namely https://businessforum.zyxel.com/discussion/2906/smart-mesh-link-speed#latest
I have dully observed that every time after the wireless AP reboots the uplink is always over 5GHz;
However after some time (a few hours) the smart-mesh Repeater AP Disconnected cause by Beacon Miss event can be seen in the logs; the wifi connection is lost momentarily and the uplink reconnects over 2.4GHz as stays there until I can forcibly reboot the repeater AP;
As I have not found a way how to reboot an AP from NCC (I have a free NCC version) I reboot the NWA 1123 ACv2 from the command line with the reboot command.
Could ZyXel staff explain why the mesh uplink "bugs" and reverts to lower 2.4GHz backhaul channel ? That's very annoying....
As said earlier I would have uploaded the logs but the free NCC blocks this feature.
best regards;
Comments
-
Hi @RTH10,
The log you mentioned is showed when the repeater didn't detect the beacon of root AP in a time period, and then the repeater would disconnect from the root to reconnect. Usually, it would follow a re-connection after this log as you said.
However, the beacon lost might be caused of interference or packet conflicting. So, it should not be a bug but a log to record the re-connection. May I know is there any 3G/4G repeater or complex wireless environment of your test?
Thanks.
0 -
Hi @RTH10,
After re-checking the first photo you posted and found out the 5GHz channel seems to use DFS channels (radar ones), so it might be that a radar signal is causing interference.
Would you enable "Avoid DFS channels" in AP radio setting and check if the issue will happen or not?
Thanks.
0 -
many thanks for the hint with the DFS channels; It seems that this has addressed the mesh uplink instabilities and disconnections.
Small question: there is no access to the "Avoid DFS channels" in AP radio setting in NCC;
So what I did I switched to the manual configuration and ticked the 36, 40, 44, 48 channels.
Maybe a word of explanation why I opted to use the band B and C doppler channels. This is because I have observed the APs emit a stronger 5GHz signal (like 26 or 21 dBm), With the lower band A 5GHz channels the signal strength is weaker and below 20 dBm.
But since I have been hit by another problem. Netconf is unable to connect NCC.
So I assigned a fixed IP address (outside of the DHCP range) to the repeater AP.
But now it shows the following event in the logs, namely: Netconf is unable to connect NCC. Relevant to DNS queries failed.
This has happened several times overnight and only on the repeater AP (with the fixed IP address)
Thanks
0 -
actually after rechecking the event logs on both APs separately I can see the event Netconf is unable to connect NCC. Relevant to DNS queries failed. occurred on both the repeater AP and the root AP at the same time .
This was probably due the NCC infrastructure access issue because can be seen on the either AP at the same time....
Thanks
PS.
The repeater AP's logs:
2019-07-30 01:39:45
system
Netconf connection is disconnected.
2019-07-30 01:41:06
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:42:26
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:43:46
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:45:06
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:46:27
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:47:47
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:49:07
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:50:27
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:51:47
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:53:08
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
The root AP's logs:
2019-07-30 01:39:06
system
Netconf connection is disconnected.
2019-07-30 01:40:27
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:41:47
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:43:07
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:44:27
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:45:47
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:47:08
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:48:28
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:49:48
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:51:08
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
2019-07-30 01:52:28
system
Netconf is unable to connect NCC. Relevant to DNS queries failed.
0 -
Hi @RTH10,
The log showed the reason for disconnecting from NCC, so if it happened on both root and repeater APs, please check the wired connection. Or, you can use ping tool in detail AP information page to check if there's problem to query GW and DNS.
Thanks.
0
Categories
- All Categories
- 415 Beta Program
- 2.4K Nebula
- 146 Nebula Ideas
- 96 Nebula Status and Incidents
- 5.7K Security
- 262 USG FLEX H Series
- 271 Security Ideas
- 1.4K Switch
- 74 Switch Ideas
- 1.1K Wireless
- 40 Wireless Ideas
- 6.4K Consumer Product
- 249 Service & License
- 387 News and Release
- 84 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.5K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 73 Security Highlight