A regional DC build needs identical leaf roles with unique hostnames and management IPs. How does a sound ZTP workflow support that requirement?
Select an answer to reveal the explanation.
Short Explanation
Same job title, different name badges—that is leaf ZTP done right. A shared role template keeps configs consistent, while per-device parameters stamp unique hostnames and IPs. The regional build does not need thirty totally different playbooks or one cloned identity for every switch.
Full Explanation
ZTP workflows commonly combine a role-consistent configuration baseline with device-specific parameters so leaves share operational behavior yet remain uniquely identified. DHCP options and provisioning logic map each device to the correct parameterized artifact. Cloning one hostname/IP across the pod creates collisions; claiming uniqueness is impossible under ZTP misunderstands how templates and identity mapping work together.