Helpdesk sets an extremely short DHCP lease and leafs churn management addresses mid-ZTP. What is the operational concern?
Select an answer to reveal the explanation.
Short Explanation
Mid-ZTP address churn is like changing the delivery dock number while the truck is still unloading. Tiny leases can yank the management IP during image pull or reboot and break the bring-up. Helpdesk should keep leases stable through the provisioning window.
Full Explanation
Extremely short DHCP leases can renumber leaves during file transfer and reboot cycles, interrupting ZTP before provisioning completes. Short leases do not improve ZTP by forcing faster image downloads. Lease length is not irrelevant; the leased address is used during retrieval and bring-up. Short leases do not automatically map leaves to correct role configs. Exam caveat: Size leases to cover the full image/config/reboot window, then apply steady-state policy afterward if required. Operational check: Watch management IP stability across a ZTP image upgrade; if the address changes mid-transfer, lengthen the lease. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure.