o The resulting URL must end in .opg or .xml (an optional ?query-string is permitted). It is doesn't, then it is
skipped and the next URL is tried.
o In secure mode, the URL must use the https scheme or it is skipped.
o Otherwise the available schemes are: http https tftp ftp ftps
o The curl program is used to download the URL.
o In secure mode, the server's certificate must validate against the ca-bundle.crt. The (reqiured) client.pem
file is provided to authenticate the client to the server. Please see the curl documentation for the format of
these files.
• The URL is downloaded. For .opg files its header is checked to see if it is compatible with the current device. For
.xml files, a parse check is made. If the check fails, the downloaded file is abandoned and the next URL is tried.
• The file is imported into the current configuration.
• The system checks to see if a hostname has been set in the config. If not, it is set to ${model}-${mac}.
• The system checks to see if it is still in an unconfigured state. If it is, then the network interface mode is set to
DHCP. This effectively forces the system into a configured state, preventing a future reboot loop.
• The system reboots
Note: If all the URLs were skipped or failed, the system will wait for 30 seconds before retrying again. It will retry all the
URLs up to 10 times. After the 10th retry, the system reboots. If the system has been manually configured in the
meantime, the retries stop and ZTP is disabled.
Note: If no option 43 is received over DHCP, no URLs are downloaded and no reboots occur: the system must be
manually configured. Once configured (manually or by ZTP), a Console server will no longer request option 43 from the
DHCP server, and it will ignore any option 43 configuration URLs presented to it.
To Next Page
Loading...
