Example Scenarios of Configuration Sync Suspended Errors - Troubleshooting-Configuration-Sync-Errors/Example-Scenarios-of-Configuration-Sync-Suspended-Errors

Troubleshooting Configuration Sync Suspended Errors

ft:locale
en-US
ft:sourceName
Paligo_Prod
Document Type
Article

Below are some common scenarios that can trigger a Configuration Sync Suspended error. This list is not exhaustive, and other situations may also cause this issue:

  • VLAN Configurations Conflict: When VLAN settings are modified at both the group and individual levels, the router may enter a Configuration Sync Suspended state.

    • Example: A group configuration removes port 1U from VLAN 2 and adds it to VLAN 101, while an individual configuration removes port 4U from VLAN 2 and adds it to VLAN 102. This results in a sync-suspended state, and the configuration editor may display duplicate entries, such as port 3U in VLAN 2. For more details, see Troubleshooting VLAN Port Issues.Overview of Troubleshooting VLAN Ports

  • Port Modification in VLAN: If a port in a VLAN is tagged or untagged in the group configuration but removed in the individual configuration, the port reverts to the default VLAN with its default settings

  • LAN Interface Conflict: If an interface is added to a default LAN in the individual configuration before the device is added to a group, and the group configuration adds a different interface to the same default LAN, only the interface from the individual configuration will be retained after the device joins the group.

Note

There is a 900-second delay before a Configuration Sync Suspended error triggers a configuration rollback.