After the node enters ZTP mode, the auto-discovery process is executed to provision the necessary hardware for node discovery.
The following are the operational steps of the auto-discovery process.
DHCP is used to discover the IP address of the node.
Options 66 and 67, or Option 43 is used to find and download the provisioning file.
The provisioning file includes the location of necessary files, such as configuration information, system image, and licenses, along with the DNS needed to resolve these location URLs. The file also includes BOF information required to boot the node into operational mode.
The provisioning file is executed to download the named files to the node.
After all files are successfully downloaded, the node is rebooted and the auto-boot flag is cleared from the BOF.
After the node reboots, it comes up in normal operational mode.
The node can be put back into ZTP mode by editing the BOF to include the auto-boot flag and saving the BOF. Doing this causes the node to enter ZTP mode after it is rebooted.
Use one of the following methods to run the auto-provisioning process.
automatic execution
The auto-boot process automatically executes the auto-provisioning process if the auto-boot flag is set in the BOF.
manual execution
The auto-provisioning process can be executed manually using the tools>perform>system>auto-node-provisioning command.
If the auto-provisioning process is executed manually, only interfaces without IP addresses are considered part of the discovery mechanism. Additionally, while the process is running, it attempts to discover DHCP servers using all card or MDA slots and ports with Layer 3 interfaces that do not have IP addresses.