Question 380
A data center doubles rack count while keeping a fixed two-spine hardware selection, ignoring both the physical fabric port budget and desired uplink headroom. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
The preventive practice is aligned with the diagnosed mechanism, not an unrelated protection. Recompute spine port and bandwidth demand before modifying the number of racks or uplinks per leaf. A high-level Clos drawing is feasible only when supported physical port capacity satisfies the modeled connectivity.
Incorrect Answers
Apstra design catalog elements may be embedded or instantiated into blueprints and existing blueprint-local configuration must be reviewed when global definitions change. For the current prevention question, the evidence instead states: A data center doubles rack count while keeping a fixed two-spine hardware selection, ignoring both the physical fabric port budget and desired uplink headroom. Here, spine port inventory and fabric uplink demand must reconcile with the topology's link count, speed and growth assumptions.
Record breakout limitations in the device profile compatibility review for every new rack type. That concerns interface breakout capabilities in design, while the issue here is spine-capacity planning from oversubscription. Calculate required spine-facing port counts and bandwidth from planned leaf uplinks, compare compatible device capacity and reserve documented growth margin.
Validate logical port capacity and role allocation before approving physical device models for a template. Here, spine port inventory and fabric uplink demand must reconcile with the topology's link count, speed and growth assumptions. Specifically for the prevention question, the case to validate is: A data center doubles rack count while keeping a fixed two-spine hardware selection, ignoring both the physical fabric port budget and desired uplink headroom.