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:
-
Copy the necessary file(s) (dependant on which
method you used) to the USB drive:
- clone.py.
- 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.
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.