šŸ” Access Restricted

This training content is password protected

Enter your master password to access

āŒ Incorrect Password - Access Denied!

šŸŒ Lab 2.2: Spine-Leaf Topology Configuration

Cisco CCNP 350-401 (ENCOR) & 300-410 (ENARSI) Enterprise Data Center Architecture

Scalable Non-Blocking Fabric Design | Password Protected

šŸ”’ Protected

šŸ“‹ Lab Objectives

šŸŽÆ Scenario Overview

Your organization is designing a new data center infrastructure to support :

šŸ’” Key Concept: Spine-Leaf architecture is the modern standard for data center networks, providing non-blocking fabrics with multiple high-speed paths, enabling efficient server-to-server (east-west) communication .

šŸ—ļø Spine-Leaf Architecture Overview

Architecture Components

šŸ”— Spine Layer

Description: High-speed backbone switches or routers forming the core of the fabric

Characteristics:

šŸ‚ Leaf Layer

Description: Switches connecting directly to endpoints (servers, storage, virtualization hosts)

Characteristics:

āœØ Advantages of Spine-Leaf Architecture

Advantage Description Business Impact
Non-Blocking Multiple high-speed paths reduce bottlenecks and provide maximum throughput between any two endpoints Maximum server-to-server performance
Low Latency Direct connections between leaf and spine switches provide efficient communication with minimal delay Sub-millisecond response times
Linear Scalability New leaf switches can be added without affecting overall network performance or requiring topology redesign Growth without architecture changes
East-West Optimized Specifically designed for server-to-server communication rather than client-server (north-south) traffic Data center efficiency
Simplified Ops Predictable, symmetric design makes network easier to manage and troubleshoot Reduced operational complexity
High Redundancy Multiple independent paths provide natural fault tolerance and improved security through network segmentation Business continuity assurance

āš ļø Design Considerations

Primary Design Concern: The leading concern for Spine-Leaf architecture is the number of cables and network equipment required to scale the bandwidth. A full-mesh topology between spine and leaf layers requires significant cabling and port density .

Bandwidth Scaling Formula

Switch BW Capacity = (Inter-slot Switching Capacity Ɨ Number of I/O Slots) + [(Number of SE Modules Ɨ Inter-slot Switching Capacity) / 2] Full Duplex Switch BW Capacity = (Switch BW Capacity) Ɨ 2

šŸ”Œ Cisco Data Center Switches for Spine-Leaf

Switch Series Description Port Density Interface Types Best Use
Nexus 9500 Modular switches with comprehensive line card support Scalable 1-400 Gbps 1G, 10G, 25G, 40G, 50G, 100G, 200G, 400G Ethernet Spine layer for large-scale deployments
Nexus 9000 Operates in Cisco ACI or Cisco NX-OS mode 48-128 ports 10G, 25G, 40G, 100G Ethernet Spine or leaf layer with ACI fabric capabilities
Nexus 7000 Designed for top-of-rack deployments 24-128 ports 10G, 40G, 100G Ethernet Leaf layer connecting servers and storage
Nexus 3550 Ultra-low latency platform with programmable capabilities 16-32 ports 400G 400G Ethernet High-speed leaf or spine layer

šŸ› ļø Lab Equipment Setup

Component Quantity Specification Purpose
Spine Switches 2-4 Cisco Nexus 9500 or 9000 Series Core fabric layer
Leaf Switches 4-8 Cisco Nexus 9000 or 7000 Series Access layer for servers
Server/Endpoint Connections 16-64 ports Virtual machines or physical servers Generate traffic for testing
100G Ethernet Cables 20-40 DAC or optical connections Spine-Leaf interconnections
10G/25G Ethernet Cables 20-40 DAC or optical connections Server-to-Leaf connections

šŸ“ Minimal Lab Topology (Recommended for Learning)

Topology Details :
ā€¢ 2 Spine switches providing redundant paths
ā€¢ 4 Leaf switches each connecting to both spine switches
ā€¢ Each leaf can support 12-16 server connections
ā€¢ Total potential: 48-64 connected servers
ā€¢ All leaf-to-spine connections are 100Gbps
ā€¢ All server-to-leaf connections are 10Gbps or 25Gbps

āš™ļø Spine-Leaf Configuration Steps

1Phase 1: Physical Setup - Cable Interconnections in Full-Mesh

For a 2-Spine, 4-Leaf topology :

Connection Pattern:

Spine-1 Eth1 ā†” Leaf-1 Eth49
Spine-1 Eth2 ā†” Leaf-2 Eth49
Spine-1 Eth3 ā†” Leaf-3 Eth49
Spine-1 Eth4 ā†” Leaf-4 Eth49
(Repeat pattern for Spine-2 on Ethernet 50 of each Leaf)

2Phase 2: Device Configuration - Spine Switches

Configure basic Spine switch parameters:

! Access Spine-1 Console configure terminal
hostname Spine-1
interface Ethernet 1/1-4
description Leaf-facing ports
no shutdown
exit
exit
! Repeat for Spine-2 with similar configuration

3Phase 2: Device Configuration - Leaf Switches

Configure basic Leaf switch parameters:

! Access Leaf-1 Console configure terminal
hostname Leaf-1
interface Ethernet 1/49-50
description Spine-facing ports
no shutdown
exit
interface Ethernet 1/1-12
description Server-facing ports
no shutdown
exit
exit
! Repeat for Leaf-2, Leaf-3, and Leaf-4

4Phase 3: Connectivity Verification

Verify all connections are active :

Spine-1# show interface brief
Spine-1# show interface Ethernet 1/1-4 status
Spine-1# show interface Ethernet 1/1-4 transceiver

Expected Output:

5Phase 4: Bandwidth Calculation

Using Cisco formulas for bandwidth calculation :

Example Calculation for Nexus 9500 Spine:

Inter-slot Switching Capacity = 38.4 Tbps Number of I/O Slots = 2 Switch BW Capacity = (38.4 Tbps Ɨ 2) + [(0 Ɨ 38.4 Tbps) / 2] = 76.8 Tbps Full Duplex Capacity = 76.8 Tbps Ɨ 2 = 153.6 Tbps

Lab Calculation Task:

6Phase 5: Traffic Testing

Deploy traffic generation tools to test topology:

! Monitor traffic on spine ports Spine-1# show interface Ethernet 1/1 stats
Spine-1# show interface Ethernet 1/1 counters

šŸ“¦ Lab Deliverables & Verification

Required Deliverables

āœ… Lab Completion Checklist

āœ“ Lab Completion Indicator: You have successfully completed Lab 2.2 when you can design a complete spine-leaf topology, calculate bandwidth capacity, configure all devices, verify connectivity, and understand how the architecture optimizes for east-west data center traffic flows .