In release 19.10, Nebula Control Center (NCC) introduced important enhancements for configuration synchronization. Previously, administrators had only a site-wide settings sync option, which copied general parameters across sites. This option was removed in 19.10, and the focus shifted to more granular synchronization of specific objects: Port Profiles, PoE Schedules, and SSIDs.
This change is significant because it gives admins more control. Instead of duplicating all settings, they can now choose only what matters for their environment. For example, an MSP managing several small offices can push standardized SSIDs but keep unique VLAN or firewall policies.
Looking forward, Zyxel has also announced that in a planned release (19.20), the site-wide settings sync will be reintroduced in a redesigned way, allowing selection of individual APs, switches, or firewalls instead of an “all-or-nothing” approach.
Q2: Can I synchronize Port Profiles and PoE Schedules across sites?
A2:
Yes, this is one of the biggest improvements. Administrators can now select Port Profiles and PoE Schedules during site-to-site synchronization. This means that standardized configurations for switch ports (such as VLAN assignments, trunk/access mode, or security settings) can be replicated quickly across multiple sites.
The behavior is straightforward:
If the target site does not have a profile with the same name, NCC automatically creates a new profile.
If a profile with the same name already exists, NCC will overwrite it with the source version.
This ensures consistency but also means admins must be careful: if local customizations exist under the same name, they will be lost. A best practice is to use clear naming conventions (e.g., “HQ-VoIP-Profile”) to avoid accidental overwrites.
Q3: What if a Port Profile in the source site uses a PoE Schedule?
A3:
This situation is common in real deployments, for example when a Port Profile for office phones uses a schedule that powers them off outside working hours.
NCC handles this dependency automatically:
If a Port Profile references a PoE Schedule, that schedule is also synchronized.
If the schedule already exists in the target site, it will be overwritten.
If it does not exist, it will be created.
This design ensures that Port Profiles are never “broken” after synchronization. Without this feature, admins would have to manually recreate schedules before copying profiles, which was error-prone and time-consuming.
Q4: Are there limits on PoE Schedules?
A4:
Yes, and this is a critical point for administrators to understand. NCC itself does not limit how many schedules you can create, but the hardware does. Zyxel switches support a maximum of five PoE schedules per device.
If a sync operation would push a sixth schedule onto a switch, the synchronization is blocked. The error is reported in NCC so that the admin knows why the sync failed.
Practical example: If a site already has 5 schedules configured locally and you synchronize a Port Profile that references a new one, NCC will prevent the sync. The admin would need to either remove unused schedules or consolidate them.
Q5: Does synchronizing Port Profiles or PoE Schedules change switch settings immediately?
A5:
No — and this distinction is important. Synchronization only transfers the profiles into the target site’s configuration database. For the changes to take effect, an administrator must assign the Port Profile or PoE Schedule to a specific switch port.
This is designed intentionally to give admins more control. Imagine you synchronize a new “IP Camera Profile” with high PoE power and VLAN 30. You may not want all sites to apply it immediately — but once it’s available in the target site, local admins can selectively apply it where needed.
Q6: How has SSID synchronization improved?
A6:
Before this enhancement, SSID synchronization was “all or nothing”: admins had to copy all SSID profiles from one site to another, even if they only needed one or two. This often created conflicts and unnecessary configurations.
Now, NCC allows selective SSID synchronization. An admin can choose specific SSID profiles (e.g., “CorpWiFi” and “Guest”) to sync. NCC will automatically:
Add missing slots in the target site.
Fill any empty slots with default values.
This makes multi-site management far easier. For example, an MSP managing 10 branch offices can push only the standard “Guest WiFi” SSID while leaving the “Local Staff WiFi” SSID different in each site.
| |
Q7: Are there restrictions with SSID synchronization?
A7:
Yes, there are several important limitations:
AP Grouping – If the source or target site uses AP grouping, SSID synchronization is not supported.
Tags – SSID tags are not synchronized. Admins must recreate them manually in the target site.
Microsoft Entra ID sign-in – If the source site uses this authentication method, it is disabled in the target site after sync. This is because Entra ID metadata is specific to each site and cannot be copied.
These restrictions are important to remember when planning large-scale SSID deployments across sites.
Q8: What happens if synchronization is started on a site already in progress?
A8:
When NCC begins synchronization, the site is marked as “synchronization in-progress.” If another admin tries to start a new synchronization for the same site during this process, the request is ignored, and an error message is shown.
This mechanism prevents conflicts and protects data integrity. Without it, simultaneous syncs could result in corrupted or inconsistent profiles between sites.
Q9: How can I check if synchronization succeeded?
A9:
After the process finishes, NCC updates the notification bell with the result. If the sync succeeded, it is confirmed there. If it failed, the message includes the reason — for example:
Exceeding the 5-schedule limit on a switch.
SSID conflicts due to grouping.
Unsupported settings such as Entra ID authentication.
This feedback loop is crucial for troubleshooting. Admins should always check the notifications after a sync to ensure everything was applied as intended.
Summary
The Configuration Management Enhancements in NCC 19.10 give administrators far more flexibility and control. Instead of syncing entire site-wide settings, they can now choose exactly which profiles and schedules to share across sites. This reduces errors, improves efficiency, and supports modern MSP workflows.
The changes are especially useful for organizations managing multiple branch offices, where consistency of core services (e.g., SSIDs, VLANs, PoE policies) matters, but site-specific variations must also be preserved.
Looking ahead, Zyxel has indicated that in a planned 19.20 release, site-wide synchronization will return in a redesigned form, enabling even more fine-grained control over AP, switch, and firewall configurations.
Comments
0 commentsPlease sign in to leave a comment.