synchronize {slot slotid}


The synchronize command replicates all saved images and configurations from the master node to the backup or target node on a SummitStack.

Syntax Description

slotid Specifies the target node that has to be synchronized with the master node. If the slotid is omitted, the target is the backup node.
Note: This parameter is available only with SummitStack.


If you do not specify a node, the backup node is synchroized with the master.

Usage Guidelines



You cannot synchronize a master switch running a version earlier than ExtremeXOS 22.2 to a target node running ExtremeXOS 22.2 or later. The command fails and the following error message appears: Error: the target slot's partitions are not compatible with the Master's for synchronize.

This command:

During a synchronization, half of the switch fabric is lost. When the master node finishes replicating its configurations and images to the backup or target node, the full switch fabric is restored.

To use this command, make sure your SummitStack is running ExtremeXOS 12.0 or later.

When you install a different backup node, you are not prompted to synchronize the images and the configurations from the master. If not synchronized, the backup node uses its image and the master‘s configuration. This image/configuration mismatch will likely cause the switch to operate differently after failover. Use the synchronize command to replicate all saved images and configurations from the master to the backup node.

If you have not saved your runtime configuration, you are prompted to save it when you use this command. A message similar to the following appears:

Do you want to save configuration changes to primary.cfg? (y or n) 

Enter y to save the configuration and continue with synchronizing the nodes. Enter n to cancel the operation. If you enter y, messages similar to the following appear:

 Saving configuration on primary ...... done! Synchronizing configuration to backup .. done! 

After the configuration has been saved and replicated to the backup node, synchronization begins.

After the initial reboot, if the backup node is not available or does not respond within 120 seconds, the synchronize operation fails.

Use the show switch {detail} command to verify that the backup node is in sync with the master node.

While using the command synchronize {slot slot-number} if the slot number is provided, that slot is the target of the synchronize operation. If the slot number is not provided, the backup node is synchronized. This command can be executed only on the master node.

The synchronize command preserves the following stacking configurations on the target node:
  • slot number
  • master-capable configuration
  • alternate IP address, subnetwork mask, and default gateway
  • priority
  • license restriction

Thus a synchronized node comes up in the same place in the active topology that it occupied before the synchronize command was issued.

If the synchronizing switch cannot determine the stacking support configuration on the target switch, the following message is displayed:

 Error: Information for the target switch is temporarily unavailable. Please retry the command. 


The following example assumes you have already saved your runtime configuration. Using synchronize replicates all saved images and configurations from the master node to the backup node.

After you enter the command, status messages similar to the following appear:

# synchronize
Synchronize will reboot the backup, then overwrite all code images
and configs with a copy from the master.
Synchronize currently requires ExtremeXOS version 11 or greater on
the backup
DO NOT interrupt synchronize, the backup may become unbootable!
OK to continue? (y/n) Yes
Rebooting Backup...
NOTE: The command line is locked during synchronize
synchronizing nvram...
synchronizing nvram...
synchronizing nvram...
synchronizing nvram...
synchronizing nvram...
synchronizing nvram...
synchronizing XOS...
[========================================] 100% XOS
Synchronize complete - rebooting backup ...


This command was first available in ExtremeXOS 11.0.

The slot parameter was added to support SummitStack in ExtremeXOS 12.0.

Platform Availability

This command is available only on SummitStacks.