Cloning Switches

ExtremeXOS switches provide a script called clone.py that allows you to clone one switch's setup to another switch in the following scenarios:

Within a stack (see Cloning within a Stack)
Standalone to standalone (see Cloning Standalone to Standalone)
Standalone to stack (see Cloning from Standalone to a Stack)
Standalone to USB (see Copying One Switch's Configuration to Another Switch Using USB Zero Touch Provisioning (ZTP))

The clone.py script copies the following:

All content under:
- /boot
- /exos
- /alt/boot
- /alt/exos
- (optionally) /usr/local/cfg
Specific NVRAM contents:
- Boot selector
- CLI banner
- Failsafe username,password, and action

Limitations

Requires ExtremeXOS 30.3 or later.
Cloning to a standalone switch using a stacking master as the source does not make the standalone switch a stacking master. The configuration cloned from a stacking master to the standalone switch is ignored by ExtremeXOS.
ONIE to non-ONIE or non-ONIE to ONIE cloning cannot be performed.
Most of the newer ExtremeSwitching series switches use the Open Network Install Environment (ONIE) bootloader. All other ExtremeSwitching series switches do not use ONIE.
The ExtremeSwitching X435 only supports USB cloning.
Clone application does not connect through VR-USER.
Synchronize cannot be done for mixed stacking. All nodes in the stack must be the same platform.
If the clone master is started and stopped, the dirty bit is set.

Cloning is supported on all switches.