Using USB Zero Touch Provisioning

To use USB Zero Touch Provisioning (ZTP):

Gather the files that you need from the source switch by using one of the following methods:
- Run the command:
```
run script clone.py usb –o
```
  Use the -e option if you want to only clone the ExtremeXOS partitions and not copy the switch configuration:
```
run script clone.py usb –o -e
```
  The following appears:
```
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+   Clone EXOS partitions on this switch to the file:   +
+   /usr/local/ext/xos1405G-00125_2017-01-21_1757.cln   +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Do you want to continue cloning? [y/N]: y
......................................
-rwxr-xr-x    1 root     root    453981696 Jan 21 17:58 /usr/local/ext/xos1405G-00125_2017-01-21_1757.cln

 1K-blocks      Used Available Use%
   7958912    443428   7515484   6%

************************
*   Cloning COMPLETE   *
************************ 
```
  Skip Step 2.
- Use tar or WinZip to create a compressed file containing all of the files from the source switch, and then rename it ztp.lst.
- Create a plain text file with a list of all of the file names from the source switch, and then reanme it ztp.lst.
- Select .xos, .xmod, .cfg, .xsf, and .py files as needed, and then append "ztp" (not case sensitive) to the beginning of each file name.
Copy the necessary file(s) dependant on which method you used) to the USB drive:
- ztp.lst (compressed file).
- ztp.lst (plain text list), plus the files listed in ztp.lst.
- ExtremeXOS image, configuration, and script files, as needed.
Ensure that the receiving switch is unconfigured—either "just out-of-the-box" or run unconfigure switch {all | erase [all | nvram]}.
Insert the USB drive in the receiving switch.
- If you used clone.py, run the command run script clone.py usb -i filename -e, where -i enables the copying from the source switch, -e only copies the ExtremeXOS partitions (not the switch configuration), and filename is the name of the file created from running the clone.py script on the original switch. The file is in the format: xosserialnumber_date.cln, where
  - xos—constant identifying that this file was created from ExtremeXOS.
  - serialnumber—the serial number of the switch used to create the clone image file.
  - date—the date and time the clone image file was created.
  - .cln – file suffix indicating this file was created by clone.py.
  Note
  Use the command run script clone.py usb -v filename to view the ExtremeXOS versions that are in the file. For example:
```
# run script clone.py usb -v xos1405G-00125_2017-01-21_1757.cln
File: /usr/local/ext/xos1405G-00125_2017-01-21_1757.cln
Contains:
EXOS: 22.2.0.38
EXOS: 22.3.0.7
```
  For example:
```
run script clone.py usb -i xos1405G-00125_2017-01-21_1757.cln
```
  The following appears:
```
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+                         C A U T I O N                          +
+   Cloning will replace the EXOS partitions and configuration   +
+        on this switch with the contents of the usb file        +
+       /usr/local/ext/xos1405G-00125_2017-01-21_1757.cln        +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Do you want to continue cloning? [y/N]: y
DO NOT REMOVE POWER or REBOOT the switch until the operation is COMPLETE
Switch will reboot when cloning is COMPLETE

Transferring /usr/local/cfg directory
...
Transferring inactive EXOS partition
...........
Transferring active EXOS partition
..............
****************************
*   USB Cloning COMPLETE   *
****************************
...reboot: Restarting system
```
- If you did not use clone.py (the file is named ztp), the cloning starts automatically.
  Files found on the USB drive are processed in the following order:
  - ztp.xos is installed to the inactive partition
  - ztp.xmod is installed in the inactive parttion
  - ztp.cfg is copied to primary.cfg
    Note
    When a configuration file is present, some processing is deferred until after reboot by using the ExtremeXOS autoexec.xsf capability. The deferred actions are:
    - Configuration files—autoexec.xsf issues a use configuration command, since ExtremeXOS does not recognize .cfg file unless the file is present at bootup.
    - Script files—Since script files are likely to modify the configuration, scripts are processed after implementing the configuration (.cfg) by autoexec.xsf.
    - Save—the last action of autoexec.xsf is to save.
    - Remove autoexec.xsf—autoexec.xsf file is automatically removed after it is processed for USB ZTP.
  - ztp.xsf is run using the load script ztp.xsf command
  - ztp.py is run using the run script ztp.py command

If the switch supports it, during the USB ZTP process the front panel LEDs display a flashing pattern instead of the usual link activity. If a stacking slot seven-segment display is available and the hardware supports it, the switch scrolls the letters "U S b". When USB ZTP finishes, the LEDs resume their normal behavior.