Zyxel_Freda  Zyxel Employee

Hi @bymusty, The cloud saving mode disabled failed issue has been fixed, so may I know is there still any problem I can help?

The power is limited by the regulation in 160MHz channel width. When the power is big, it might be able to interfere the other non-wifi bands, so the regulation is limited the transmit power lower. For the 5GHz wireless channel and channel width information, please refer to below photo. As the photo, there's no band 4…

Hi @bymusty, The issue has been fixed and all organizations that the local support reported are disabled cloud-saving mode now. Please check and let me know if there's any problem. Thanks.

Hi @bymusty, After investigating, it's a bug for disabling the could-saving mode, so we'll fix it and update for you asap.

Hi @stjohnson, The transmit power is related to the channel and the channel width. When you use the same channel, the lowest channel width (20MHz) will be the max transmit power. As your screenshot, the channel is 48, but channel width is 160MHz, so the power is low. If you change the channel width to 20MHz, it would be…

Hi @bymusty, Thanks for update detail to us. We are investigating this issue and the local support has already opened a ticket for this case. So, let's keep tracing the issue via the ticket and I'll update on the ticket if there's any progress.

Hi @bymusty, Would you let me know the organization name and enable Zyxel support in HELP> Support request of these organizations? We'll check them after getting the information. BTW, did you clear the cache or use private browsing on the browser before you access these organizations?

Hi @bymusty, I checked your organization to check the issue you mentioned, but the organization is currently in base pack without cloud-saving now. So, we are checking the time period between your two posts. I'll update for you asap, and if you got the issue again, please clear the cache or use a private browsing on the…

Hi @Ian_ML,Thanks for update and please do not hesitate to let me know if the issue happened again. @@bymusty When you login to the organization of NCC, you would see the "Welcome back" message with below information:You haven't logged in to this Organization over 30 days.NCC has deactivated the collection of the traffic…

Hi @Ian_ML, I just checked the site, and currently there's no client connected on the AP. So, I checked the connected clients in 24 hours, and they are shown in the client list. And, the client traffic info is shown in the summary report as well. So, are above pages that you monitor for the client? If not, please…

Hi @kunz, Because the AP seems to keep connecting to the NCC, please check that if the AP is removed from the organization first. You may check it in device information of Organization-wide> Configure> License & inventory. If the AP is still in the organization-wide, please remove it to let it in standalone mode.…

Hi @Ian_ML, When the client connects to the AP, the client information will update to the Access point> Monitor> Clients in few minutes because the NCC needs to sync the information from the AP. If you don't get any client information on this page after waiting over 5 minutes, please let us know the name of the…

Hi @Ark, The neighbor information is come from the LLDP (Link Layer Discovery Protocol) packet, so the AP will get the neighbor's info when the neighbor supports LLDP as well. As Greenlight mentioned, the un-managed switch does not support LLDP and broadcast the LLDP packet, so when the other APs connected to the…

Hi @ThierryGolo, After checking the event logs in your site for the station, the disconnected reason code is 3, 8, or 34. The reason 3 and 8 is station is leaving (or has left) BSS, so it's station's behavior to leave the AP. The reason 34 is AP kicks the station because AP didn't get station's reply or poor channel…

Hi @ThierryGolo, Thanks for your information. We have collected the debug message for analyzing and will update to you asap. BTW, I checked the AP status and there's an alert for the AP's IP. After checking, the IP is set to DHCP with VLAN 1 tagged, so if the VLAN1 in your environment is untagged, please correct the…