New leafs in the city hall DC get an IP address but never learn where the configuration file lives. Beyond assigning an address and gateway, what DHCP role is essential for DC ZTP?
Select an answer to reveal the explanation.
Short Explanation
An IP alone is a street number without a map to city hall’s file room. DHCP for ZTP also carries options that point at the boot/file server. City hall leaves need those pointers, not just a lease, or config stays a mystery.
Full Explanation
For DC ZTP, DHCP must convey boot and file-server information so devices know where to retrieve artifacts—not merely assign an address and gateway. City-hall leaves with an IP but no file location are missing those pointers. DHCP does not replace the underlay IGP on leaves. DHCP does not terminate VXLAN tunnels for the pod. Assigning public Internet addresses to every data-plane interface is unrelated to management ZTP options. Exam caveat: When leases work but files are never located, inspect options and relay behavior before blaming Junos image quirks. Operational check: Capture Offer/Ack and verify boot/file options resolve to reachable municipal file-server URLs. In civic data-center practice, treat the correct concept as part of a controlled management design rather than an isolated checkbox, and document the expected show-command or log evidence so the next on-call engineer can prove the fabric behavior without re-deriving the theory under pressure. In civic data-center practice, treat the correct concept as part of a controlled management design rather than an isolated checkbox, and document the expected show-command or log evidence so the next on-call engineer can prove the fabric behavior without re-deriving the theory under pressure.