Question 320
A data center architect wants to reuse a ToR design with different supported vendors, but their planning object hard-codes physical port names instead of capabilities. 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. Validate logical port capacity and role allocation before approving physical device models for a template. Capability-first modeling separates network design intent from the implementation details of a particular switch chassis.
Incorrect Answers
Recompute spine port and bandwidth demand before modifying the number of racks or uplinks per leaf. That concerns spine-capacity planning from oversubscription, while the issue here is logical device capability abstraction. Create or choose a logical device with the required spine, host and generic port roles, reserving actual hardware mapping for the interface-map stage.
An Apstra rack type models repeated rack structure using logical leaf/access/generic devices and their intended links independent of vendor model. However, the present prevention decision is grounded in: A data center architect wants to reuse a ToR design with different supported vendors, but their planning object hard-codes physical port names instead of capabilities. For this issue, create or choose a logical device with the required spine, host and generic port roles, reserving actual hardware mapping for the interface-map stage.
Record breakout limitations in the device profile compatibility review for every new rack type. Here, an Apstra logical device models port counts, speeds and roles without requiring a specific vendor hardware platform at the initial design stage.