Cloning within a Stack

To clone within a stack, you can either:

Run the synchronize {slot slotid} {file_name} command, which invokes the clone.py script. You can only clone one slot/switch at a time. For more information, see synchronize in the Switch Engine v33.4.1 Command References .
Run the clone.py script directly, which allows you to specify multiple slots/switches. If more than one slot is specified, the master is cloned to each slot one at a time.

To clone within a stack by running the clone.py script directly, on the master switch, enter the command:

run script clone.py slot slotlist

Where slotlist can be any number of valid slot positions separated with commas, or all. For example, run script clone.py slot 1,2,3

The following appears on the master switch:

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
+                    C A U T I O N                    +
+   Cloning will erase all contents on these slots:   +
+                    1,3,4,5,6,7,8                    +
+     The switch contents of this stacking master     +
+     will replace the contents of these switches     +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Do you want to continue cloning? [y/N]: y
Cloning slot 1 started
........................................
Slot 1 cloning COMPLETE
Cloning slot 3 started
.........................................................
Slot 3 cloning COMPLETE
Cloning slot 4 started
...........................................................
Slot 4 cloning COMPLETE
Cloning slot 5 started
............................................................
Slot 5 cloning COMPLETE
Cloning slot 6 started
...........................................................
Slot 6 cloning COMPLETE
Cloning slot 7 started
..........................................................
Slot 7 cloning COMPLETE
Cloning slot 8 started
................................................
Slot 8 cloning COMPLETE

On each slot, the following appears:

Cloning stack master. DO NOT REBOOT OR POWER CYCLE this switch
Starting cloning process
Transfering EXOS partitions and configuration

Transferring active EXOS partition.........
Updating active partition
........................
Transferring inactive EXOS partition................
Transferring /usr/local/cfg directory......
Transfering NVRAM information from master switch
Transfering control information from master switch

Rebooting to master switch configuration
You may need to adjust any IP addresses that may have been copied from the master switch
************************
*   Cloning COMPLETE   *
************************
Rebooting ...
reboot: Restarting system

Note

The synchronize {slot slotid} command only works for cloning within the stack.
To clone in a stack containing both 5720 and 5520 switches, you must download the image of the 5520 in a primary and secondary partition in the master slot.
The unconfigure switch all command removes the summit-arm images that have been downloaded and saved in the cross stack.

Note

In mixed stacks containing both standard 5320 switches and 5320-16P-2MXT-2X switches, automatic image upgrades between model types are not supported. If a mismatch is detected, the system will display a warning and skip the upgrade. Similarly, when adding a 5320-16P-2MXT-2X switch to a mixed stack that includes 5520 or 5420 switches, automatic image upgrade for the 5320-16P-2MXT-2X is not supported.

To proceed, manually upgrade the image on the affected switch using the download image CLI command.

Note

In version 33.3.1 and earlier, the clone script used by ZTPStack and sync slot did not support downgrades from 33.4.1. To enable downgrade functionality:

Load both the ZTPStack XMOD and clone XMOD onto the Primary switch.

Once loaded, both ZTPStack and sync slot will perform the downgrade correctly.