This is achieved by running separate instances of fabric control planes (IS-IS, COOP, MP-BGP) across Pods.Īt the same time, the tenant change domain is common for all the Pods, since a configuration or policy definition applied to any of the APIC nodes would be propagated to all the Pods managed by the single APIC cluster. The entire network hence runs as a single large fabric from an operational perspective however, ACI Multi-Pod introduces specific enhancements to isolate as much as possible the failure domains between Pods, contributing to increase the overall design resiliency. Those design options are usually fulfilling the requirements of interconnecting Data Centers deployed in Active/Active fashion, so to offer the freedom of deploying the various application components across separate Pods. Note: For more information on ACI Stretched Fabric please refer to: Both models leverage a single APIC controller cluster representing the single point of management and policy definition for the entire network, independently from the number of separate ACI fabrics (Pods) compounding it. Single APIC Cluster/Single Domain: Under this family we find the ACI Stretched Fabric and its natural evolution named Multi-Pod, which is the main focus of this paper. Design Option for Interconnecting ACI FabricsĪs highlighted above, there are two separate families of solutions:ġ.

Safe distance for mac external drives