A national retailer cabled a new ACI spine only to the APICs, and that spine never joins the fabric. Where must the spine be connected so the fabric can discover it?
Select an answer to reveal the explanation.
Short Explanation
The controller finds the core of the building by walking through the wings, not by plugging the core into the front desk. You connect this spine to the leaves, because that is the path an APIC uses to discover it after a leaf has joined. A cable from the spine straight to the APIC is not a fabric discovery path.
Full Explanation
ACI discovery starts at the APIC, which attaches to a leaf. That leaf is discovered first, then the spines attached to it, then the other leaves attached to those spines. A spine that is cabled only to the APICs has no leaf adjacency, so the retailer fabric never sees it as a spine. The required connection is from the spine to the leaves. Cabling spines to each other in a ring is not how a standard fabric discovers or forwards, and it does not replace leaf-to-spine links. Server ports are for endpoints. A spine is not commissioned as a host on a leaf access port, and that cabling does not create a spine fabric link. A vPC peer-link is an NX-OS construct between a pair of switches. ACI spine discovery does not ride a leaf peer-link, and adding one does not register the new spine. Caveat: multi-pod designs also use an inter-pod network between spines, and that path is still not a substitute for leaf-to-spine links inside the pod. Operational check: move the spine uplinks onto leaves that are already in the fabric, then confirm the spine appears as a discovered fabric node and the APIC shows its leaf adjacencies.