Question 400
After adding a second pod, network automation reports address exhaustion and an administrator tries to resolve it by changing tenant VNI numbers rather than underlay address inventory. 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. Reserve and monitor underlay addressing headroom before importing additional rack and spine templates. That is important in this case because underlay interface and loopback addressing requires available appropriately scoped address resources independent of tenant overlay identifiers. The scenario was: After adding a second pod, network automation reports address exhaustion and an administrator tries to resolve it by changing tenant VNI numbers rather than underlay address inventory.
Incorrect Answers
The alternative applies to another Juniper security situation: A new blueprint must use an approved three-stage leaf–spine fabric, but the team chooses a template with an unrelated structure and expects switch placement to correct it later. That situation concerns apstra templates compose reusable design elements and networking policies into a blueprint starting structure, including its supported fabric topology. Its key condition is underlay interface and loopback addressing requires available appropriately scoped address resources independent of tenant overlay identifiers.
Apstra design catalog elements may be embedded or instantiated into blueprints and existing blueprint-local configuration must be reviewed when global definitions change. For this issue, count planned links and loopbacks, verify pool ranges and exclusions, and assign a nonoverlapping resource pool large enough for the design.
Requalify interface maps on hardware model changes, not only the template name. Here, underlay interface and loopback addressing requires available appropriately scoped address resources independent of tenant overlay identifiers.