Zero Touch Provisioning

Note

The Zero Touch Provisioning feature is supported on the following platforms:

• SLX 9540
• SLX 9640
• SLX 9250
• SLX 9150-48Y
• SLX 9150-48XT
• Extreme 8720
• Extreme 8520-48Y
• Extreme 8520-48XT

Zero Touch Provisioning (ZTP) is an automated process that uses the DHCP process to download firmware and set up the device configuration.

The ZTP process eliminates the need to log in manually to the console to bring up the device with the correct firmware and required configuration. When the device is in the factory default configuration, ZTP can start automatically upon device bootup.

This process reduces the time taken for firmware download and device configuration. All switches download the same firmware and configuration script from the ZTP configuration file.

The following configuration considerations apply to ZTP:

• ZTP is not supported for customers who do not use DHCP.
• ZTP supports only DHCPv4.
• The DHCP server must be configured with GET options 66 and 67 to set the ZTP configuration file.
• ZTP is triggered on a new device by means of Open Network Install Environment (ONIE), by means of the write erase command.
• ZTP supports both in-band ports and management interfaces in the management VRF.
• After ZTP completes, all the in-band ports return to the default VRF state.
• To establish network connectivity, ZTP retries indefinitely to establish a network connection among in-band ports and management interfaces until the firmware download completes, downloading all firmware packages before the device reboots.
• The interface is selected when it passes the sanity test. The order of selection is based on the response order of GET options 66 and 67 during the DHCP server detection process.
• All the interfaces are scanned in parallel to detect DHCP options 66 and 67.
• If ZTP is enabled and there is no DHCP server configured with options 66 and 67 for ZTP, the device indefinitely tries to discover a DHCP server. The user must disable ZTP by using the dhcp ztp cancel command and must reboot the device before applying any configuration.
• Network connectivity through the management interface has higher priority over connectivity through in-band ports.
• ZTP is supported only in standalone mode.
• Customer configurations are supported with the Python script.
• The ZTP configuration file supports both a common setting or device-specific settings.
• The ZTP progress is displayed on the serial console and is saved in a log file.
• The DHCP client ID of the device must be set up in the device-specific ZTP configuration file.
• The RASlog is disabled during the early stages of the ZTP process.
• Breakout ports are not supported, because a device reboot is required.
• Only the default speeds (10 or 100 G) on in-band ports are supported for the ZTP process.

Routing for ZTP

ZTP supports FTP and HTTP to fetch ZTP configurations, scripts, switch startup configurations, and firmware.

The DHCP and FTP/HTTP server may not be reachable by all the nodes in the IP Fabric. A route must be configured on the first-level node with a connection to DHCP and FTP/HTTP servers. ZTP must first be run on the first-level node by means of the Python script to enable iphelp to forward the traffic to the servers. The ZTP process can then run on the next-level nodes. Eventually the farthest nodes can connect to the servers for ZTP.