A leaf ZTP loop repeatedly fetches the wrong role configuration. Which factor is most critical to correct in the ZTP design?
Select an answer to reveal the explanation.
Short Explanation
Wrong config on repeat is usually a labeling problem: the leaf is being pointed at the wrong locker. Fix DHCP options or identity mapping so role files match the right serial or circuit ID. Twiddling BGP keepalives will not stop a mis-mapped download.
Full Explanation
Repeated wrong-role ZTP pulls are fixed by accurate device-to-config mapping via DHCP options or identifiers so each leaf receives the intended role file. Raising BGP keepalives on spines does not repair identity-to-artifact binding errors. Disabling logging removes debug evidence and does not correct file selection. Advertising a default only from a border leaf does not replace correct option scopes or serial/MAC maps. Exam caveat: Shared templates still need per-device parameter maps; mapping bugs look like “ZTP succeeded on the wrong device.” Operational check: Correlate chassis serial/MAC to DHCP options and filename, fix the map, and re-ZTP to confirm the municipal role. 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.