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
Successful ZTP requires reliable binding between a device identity and the configuration (and image) it should fetch. Incorrect DHCP option values or identifier maps cause repeated pulls of the wrong role file. Underlay timer tuning and logging disablement do not fix mapping errors. Validate option scopes, MAC/serial-based selection logic, and artifact naming before re-racking.