Public-works NOC asks which first-boot behavior starts ZTP on a factory-default Junos data-center switch. Which concept is correct?
Select an answer to reveal the explanation.
Short Explanation
Factory-default is the blank slate where ZTP wakes up—like a new phone activating on first power-on. The public-works NOC should expect ZTP to kick in when the Junos DC switch boots without a saved config, hunting the network for provisioning. You do not need EVPN or a pre-baked hostname for that first-boot dance to start.
Full Explanation
ZTP on Junos data-center platforms is associated with factory-default or equivalent no-config first-boot conditions, where the device seeks DHCP and subsequent file-based provisioning. It is not initiated by committing production configuration first, nor does it require EVPN fabric state or a pre-assigned hostname already stored. Understanding that initiation window helps NOC teams know when ZTP should or should not appear during rack-and-stack.