Summary of "ACI Part 3 | Going beyond the Data Center | A look at extended ACI topologies."

The video titled "ACI Part 3 | Going beyond the Data Center | A look at extended ACI topologies" provides an in-depth overview of Cisco ACI (Application Centric Infrastructure) extended topologies beyond traditional data center deployments. The main focus is on how to expand ACI fabrics to remote and multi-location environments while maintaining consistent policy enforcement and network architecture.

Key Technological Concepts and Product Features:

Remote Leaf Architecture
- Deploy leaf switches at remote locations connected via an IP network to spine switches in the main data center.
- The IP network must support VXLAN, matching MTU sizes, and sub-100ms latency.
- Minimum bandwidth: 10 Mbps bidirectional (recommended 100 Mbps).
- Remote leaf switches are treated as uplinks, not remote L3 outlinks, facilitating ACI discovery.
- Requires DHCP relay configuration and static route setup during initialization.
- Benefits: Policy consistency across sites, avoiding legacy L3/L2 out configurations and reducing configuration errors.
ACI Stretched Fabric vs. Multi-Pod
- Stretched Fabric:
  - Extends the fabric physically with spine and leaf switches at remote sites.
  - Requires direct connections (e.g., dark fiber) between spines and leafs across sites.
- Multi-Pod:
  - Multiple pods (up to 12) connected over an IP routed network.
  - Spine switches connect only to leaf switches within their pod.
  - More scalable and versatile than stretched fabric.
  - Limits: 200 leaf switches per pod; total leaf switches depend on the number of APIC controllers (e.g., 3 APICs = 80 leaves max, 7 APICs = 400 leaves max).
  - Inter-pod network requires VXLAN support with protocols such as PIM bi-directional multicast, DHCP relay, OSPF, and optionally BGP, plus MTU considerations.
ACI Multi-Site
- Multiple self-contained ACI fabrics (sites), each with its own spine, leaf switches, and odd number of APICs (minimum 3).
- Sites connected via an inter-site network using border routers supporting 802.1q VLAN tagging (VLAN 4 mandatory).
- No strict latency requirements since fabrics are separate.
- Management via Multi-Site Orchestrator (MSO), integrated into Nexus Dashboard Orchestrator in ACI 5.2+.
- Allows creation of local policies per fabric and global policies spanning multiple sites, including EPGs, VRFs, bridge domains, and contracts.
- Demonstrated through a demo with two sites (Seattle and London) showing policy and EPG synchronization and traffic flow across sites.

Tutorials and Guides Highlighted:

Configuration considerations for remote leaf setup, including DHCP relay and static routes.
Differences and use cases for remote leaf, stretched fabric, Multi-Pod, and multi-site topologies.
Protocol and network requirements for inter-pod and inter-site communication (VXLAN, multicast, routing protocols).
Practical demonstration of Multi-Site Orchestrator usage within Nexus Dashboard, including tenant and application profile management across sites.

Speaker / Source:

Rich, host of the "Rich Tech Guy" YouTube channel, who provides detailed explanations and demos related to Cisco ACI technologies.

Overall, the video serves as a comprehensive guide for network engineers and architects looking to extend Cisco ACI fabrics beyond traditional data centers into remote sites, Multi-Pod deployments, and multi-site environments, emphasizing scalability, consistency, and orchestration.