Question 610
In the fictional Harbor-1 east pod, a staged top-of-rack rollout with a bounded maintenance window, the team reports that a two-tier Clos fabric needs resilient leaf-to-spine paths. A peer suggested: "Place all east-west traffic through one gateway firewall" That did not solve the constraint. What should be chosen instead?
Explanation
Correct Answer
Multiple spine paths avoid a single aggregation dependency and permit ECMP. For Harbor-1, confirm the actual outcome: each leaf has live routed adjacencies to the intended spines.
Incorrect Answers
“Place all east-west traffic through one gateway firewall” targets a different operation from the reported requirement: “a two-tier Clos fabric needs resilient leaf-to-spine paths”. Multiple spine paths avoid a single aggregation dependency and permit ECMP. Use the appropriate method: Connect every leaf to each spine in the same fabric.
“Use a single large Layer 2 ring as the sole interconnect” targets a different operation from the reported requirement: “a two-tier Clos fabric needs resilient leaf-to-spine paths”. Multiple spine paths avoid a single aggregation dependency and permit ECMP. Use the appropriate method: Connect every leaf to each spine in the same fabric.
“Connect each leaf only to its nearest leaf” targets a different operation from the reported requirement: “a two-tier Clos fabric needs resilient leaf-to-spine paths”. Multiple spine paths avoid a single aggregation dependency and permit ECMP. Use the appropriate method: Connect every leaf to each spine in the same fabric.