Course 45 - IE Data Center Network Design | Episode 2: Modern Layer 3 Data Center Design

Designing Resilient Layer 3 Data Center Networks: Mobility, Convergence, and Service IntegrationEpisode OverviewModern data centers increasingly rely on routed Layer 3 fabrics to achieve the scalability, availability, and operational flexibility demanded by virtualized workloads.In this two-part episode, we explore the architecture behind resilient Layer 3 data center networks, focusing on three foundational objectives:- IP mobility and optimized ingress paths- High availability and rapid convergence- Layer 4–7 service integrationThe episode builds upon modern leaf-spine and VXLAN architectures, showing how distributed gateways, host-mobility technologies, fast failure detection, resilient control planes, multicast redundancy, and VRF-based service insertion work together to create highly available data center fabrics.Part I: IP Mobility and High Availability1. Moving Beyond Traditional Data Center GatewaysTraditional data center designs often rely on centralized distribution-layer gateways and first-hop redundancy protocols such as HSRP or VRRP.Modern VXLAN-based fabrics can distribute the default gateway across multiple leaf switches instead.With an Anycast Gateway, multiple leaf switches can share the same gateway IP and MAC address within a tenant VRF.This provides a consistent first-hop gateway regardless of which leaf switch a workload connects to.The result is a more distributed architecture that supports:- Workload mobility.- Consistent default-gateway addressing.- Reduced dependence on centralized gateways.- Improved traffic locality.- Greater scalability.2. VXLAN and Anycast Gateway MobilityVirtual machines may move between physical hosts or leaf switches while retaining their existing IP addressing.A distributed Anycast Gateway helps preserve the first-hop network identity of the workload throughout the fabric.Instead of forcing traffic toward a centralized gateway, the workload can use the locally available gateway on whichever leaf it is attached to.This reduces unnecessary traffic traversal and allows the data center fabric to remain aligned with workload placement.The conceptual architecture becomes:Workload → Local Anycast Gateway → VXLAN Fabric → Destination WorkloadRather than:Workload → Centralized Gateway → Distribution Layer → Destination3. Extending Connectivity Across Multiple FabricsWorkload mobility may sometimes extend beyond a single data center fabric.Technologies such as VXLAN EVPN and OTV can provide mechanisms for extending Layer 2 connectivity across Layer 3 transport between different locations.This allows organizations to build interconnected fabrics while maintaining logical network continuity where the architecture requires it.However, extending Layer 2 across sites introduces additional design considerations around:- Failure domains.- Broadcast and unknown-unicast traffic.- Routing efficiency.- Convergence.- Operational complexity.The objective should therefore be controlled extension rather than simply creating one enormous Layer 2 domain.4. Optimizing Ingress Traffic with LISPMulti-site workload mobility introduces another challenge: where should incoming traffic enter the network?Consider a workload whose subnet is advertised from multiple data center locations.Traditional routing may select a border location based on the available routing topology rather than the actual location of the individual workload.This can produce inefficient traffic paths sometimes described as trombone routing, where traffic enters one location and then travels across the network to reach the workload's actual location.5. Separating Endpoint Identity from LocationLocation Identifier Separation Protocol (LISP) addresses this challenge by separating two concepts:- Endpoint Identifier (EID): Identifies the endpoint.- Routing Locator (RLOC): Identifies where the endpoint is reachable.A mapping system associates the endpoint identity with its current routing location.This allows the network to determine where a particular workload actually resides instead of relying exclusively on aggregate subnet routing.The conceptual process becomes:Endpoint Identity → Mapping Lookup → Current Fabric Location → Optimized IngressHost-specific routing information can then direct traffic toward the fabric currently hosting the workload.This approach is particularly useful when the same logical network is available across multiple data center locations.Part II: Rapid Convergence and Service Integration6. Scaling Through a Clos ArchitectureHigh availability begins with the physical topology.Modern data centers commonly use a Clos or leaf-spine architecture, where additional capacity can be introduced by scaling horizontally.Instead of relying on