Question 330
During a switch refresh, the intended 100G spine ports land on unexpected physical connectors because the new model's interface map was not reviewed. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
This control reduces recurrence of the same class of failure: An Apstra interface map binds a logical device's role and speed abstractions to concrete interfaces in a supported device profile. Apply the recurring practice: Requalify interface maps on hardware model changes, not only the template name. The previous example was: During a switch refresh, the intended 100G spine ports land on unexpected physical connectors because the new model's interface map was not reviewed.
Incorrect Answers
Track object versions and dependencies between shared design catalogs and deployed blueprints. That concerns global design catalog versus blueprint-local copy, while the issue here is interface map matching logical roles to hardware. Inspect and correct the logical-to-physical interface mapping, including selected port groups and supported speeds, before assigning it to the blueprint device.
Apstra resource pools provide managed allocation of identifiers such as ASNs for the chosen fabric policy and must avoid unintended exhaustion or overlap. For this issue, inspect and correct the logical-to-physical interface mapping, including selected port groups and supported speeds, before assigning it to the blueprint device.
Recompute spine port and bandwidth demand before modifying the number of racks or uplinks per leaf. Here, an Apstra interface map binds a logical device's role and speed abstractions to concrete interfaces in a supported device profile.