Ops installs a leaf that already has a saved configuration and wonders why ZTP did not run. Which explanation is most accurate?
Select an answer to reveal the explanation.
Short Explanation
If the leaf already has a filled-out playbook in flash, it will not go hunting for a new ZTP script like a blank device would. Ops should expect ZTP on factory-default style boots, not on already-configured gear. That saved config is why the autopilot stayed parked.
Full Explanation
ZTP initiation is tied to factory-default or equivalent unconfigured first-boot behavior. A device that already holds a saved configuration generally boots into that configuration and does not re-enter the ZTP provisioning path. Overlay features in the saved config are unrelated to whether ZTP triggers. Assuming ZTP on every reboot or leaf-only exclusion misstates when the feature engages.