NWA55AXE Nebula Cloud — Beacon Interval and DTIM local changes: preserved or overwritten on cloud sy

ultradj83

Hi everyone,

I have a setup with three NWA55AXE access points running firmware V7.10(ABZL.4), all managed via Nebula Cloud Control.

The APs are deployed in separate areas with no overlapping coverage. When moving between zones, client devices (mainly smartphones) take 10-15 seconds to detect and connect to the next AP. To improve passive scanning discovery time, I made the following changes locally via CLI (zysh-cgi):

- Beacon Interval: 100ms → 50ms (on all three APs)
- DTIM Period: 2 → 1 (on two of the three APs)

These changes are working as expected. However, since the APs are in Nebula Cloud mode, I have a concern:

Beacon Interval and DTIM Period do not appear to be configurable from the Nebula Cloud dashboard. So my question is:

1. Will these locally applied settings survive a Nebula cloud sync, given that Nebula does not seem to manage these specific parameters?
2. Has anyone experienced local CLI changes being reverted after a cloud configuration push?
3. If they do get overwritten, is there any workaround to make them persistent without switching to standalone mode?

Any insight from someone running a similar setup would be greatly appreciated.

Thanks in advance.

Zyxel_Judy

Hi @ultradj83 ,

Regarding your question about Beacon Interval and DTIM Period — please note that these custom values set locally via CLI will be reset to default whenever a configuration change is made through the Nebula Cloud on the radio settings.
There is currently no workaround to preserve custom Beacon Interval and DTIM settings when other radio configurations are modified via Nebula.
For improving roaming performance, we would suggest exploring the Assisted Roaming and 802.11r features available in Nebula, which may help reduce the roaming delay you are experiencing.

Understanding roaming and 802.11 k/v/r — Zyxel Community