Question 430
A replacement switch comes online with a new unique device identifier while the Apstra blueprint still references the retired unit for that logical node. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
A lasting control should detect the original error before release. Require serial and rack-location reconciliation during device onboarding and replacement. That is important in this case because correct managed device identity binds each blueprint node to its intended physical hardware and prevents configuration deployment to the wrong rack. The scenario was: A replacement switch comes online with a new unique device identifier while the Apstra blueprint still references the retired unit for that logical node.
Incorrect Answers
The alternative applies to another Juniper security situation: A blueprint has all expected switch models assigned, but deployment validation fails because loopback and underlay resource allocations are incomplete. That situation concerns successful device deployment depends on the required address and identifier resources being assigned consistently to the modeled fabric. Its key condition is correct managed device identity binds each blueprint node to its intended physical hardware and prevents configuration deployment to the wrong rack.
Retest interface-map compatibility and required breakouts for each hardware substitution. That concerns interface map assignment for new hardware, while the issue here is discovering and binding device serial IDs. Inspect discovered system identifiers and serials, verify their physical rack locations and bind only the approved device to each staged blueprint role.
Apstra uses planned physical link relationships and observed neighbor data to validate whether actual cabling matches the staged blueprint. For this issue, inspect discovered system identifiers and serials, verify their physical rack locations and bind only the approved device to each staged blueprint role.