Question 10
During a rack migration, a diagram connects one leaf to another leaf as the default interrack path even though the intended Clos fabric uses parallel spines. 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. Validate fabric cabling against the reference topology whenever racks or spine ports are added. That is important in this case because in a conventional leaf–spine Clos fabric, interleaf traffic normally crosses an available spine while servers attach at the leaf edge. The scenario was: During a rack migration, a diagram connects one leaf to another leaf as the default interrack path even though the intended Clos fabric uses parallel spines.
Incorrect Answers
A VTEP endpoint requires an appropriate stable IP identity reachable in the underlay, commonly on a loopback interface. Here, in a conventional leaf–spine Clos fabric, interleaf traffic normally crosses an available spine while servers attach at the leaf edge.
Equal-cost multipath routing can retain forwarding over remaining healthy next hops when one member path disappears. For this issue, trace the actual leaf-to-spine adjacencies and restore the reference topology so each leaf has its intended uplinks to the spine set.
Maintain a tenant service inventory relating bridge domains, EVPN instances and VNIs. Here, in a conventional leaf–spine Clos fabric, interleaf traffic normally crosses an available spine while servers attach at the leaf edge.