Network Insight Data Centre Networking

Data Centre Network Workspace

Explore how modern data-centre networks are designed, connected and operated. Learn through network architecture, traffic paths, routing, overlays and practical troubleshooting — in one connected learning environment.

Leaf–Spine Fabrics BGP Underlay VXLAN / EVPN Fabric Troubleshooting
Interactive learning environment
Network Insight · Learning Centre

Explore the Learning Journey

Choose a stage to explore data centre fabric architecture, trace packet forwarding, investigate faults, practise safe changes and test your understanding. Your learning progress is reflected across the workspace.

Overall Learning Progress 0 of 10 activities · 0%

Network Insight · Learning Workspace

Learning Control Bar

0 of 5 stages complete
Overall Learning Progress 0 / 10 activities · 0%
Understand the Fabric 0 of 2 activities complete

Progress is self-reported and stored locally in this browser. Marking a stage complete updates all its activities.
Network Insight · Your Learning Dashboard

Continue Your Data Centre Networking Journey

Pick up where you left off, explore your next interactive activity and track your progress across five learning stages.

Your Learning Progress 0%
0 of 10 activities completed 0 of 5 stages complete
Recommended Next Activity Interactive Leaf–Spine Fabric

Begin by exploring the architecture of the fabric.

Open Activity
Your Five Learning Stages

Complete each interactive activity and mark it finished in your stage completion tracker. Progress is shared across the workspace.

View Full Progress Tracker
Workspace Navigation Check
Network Insight · Self-reported learning progress. Saved locally in this browser where storage is available.

Stage A — Understand the Fabric

STAGE 01 Architecture · Fabric foundations

Understand the Fabric

Explore the leaf–spine architecture, identify the role of each switch, and understand how endpoints connect to the fabric before investigating traffic or diagnosing failures.

Fabric Explorer / 01

Explore the network fabric

Start with the physical and logical structure. Select a switch, server or connection to inspect its role, then trace an illustrative journey between endpoints through the leaf-spine fabric.

Interactive educational model
2 Spine switches
3 Leaf switches
3 Connected endpoints
9 Illustrated links
Explore topology
SPINE LAYER FABRIC TRANSIT LEAF LAYER ACCESS SWITCHING SERVER ACCESS ENDPOINTS ⇄ Spine 1 SPINE SWITCH ⇄ Spine 2 SPINE SWITCH ⇄ Leaf 1 LEAF SWITCH ⇄ Leaf 2 LEAF SWITCH ⇄ Leaf 3 LEAF SWITCH ▤ Server 1 HOST ▤ Server 2 HOST ▤ Server 3 HOST Illustrative fabric · Select any device or connection
Fabric connection Highlighted traffic path Selected device

Illustrative endpoint journey

The highlighted links show one possible route through the example fabric.

Leaf switch

Leaf 1

A leaf switch connects endpoints to the fabric and forwards traffic toward other destinations.

Access layer Server connectivity

Ready. Select a device or connection to explore the topology. This is an illustrative model, not a live network simulation.

Data Center Network Workspace · Lab 06

Fabric Health Dashboard

Assess link availability, device status, path redundancy, and forwarding state. Select a simulated fault to see how the fabric changes, then run a health check to interpret the evidence.

Healthy
All simulated devices and links are operational.
Fabric links up
Devices operational
4/4
Two leaves and two spines
Path redundancy
2 paths
Two simplified paths available
Forwarding state
Ready
Illustrative destination entry present

Fabric topology

Two-leaf, two-spine fabric health model Each leaf connects to both spine switches. The highlighted route shows a simplified path between the leaves through Spine 2. Leaf 1 Leaf 2 Spine 1 Spine 2 Illustrative inter-leaf path Leaf 1 → Spine 2 → Leaf 2
Operational Degraded / investigate Failed
Current view: All four uplinks are available. The highlighted path illustrates one possible route through Spine 2.

Teaching model only. The displayed paths are illustrative; real traffic paths depend on the network design, forwarding state, and traffic destination.

Link status

ConnectionStateRole
Leaf 1 – Spine 1UpUplink
Leaf 1 – Spine 2UpUplink
Leaf 2 – Spine 1UpUplink
Leaf 2 – Spine 2UpUplink

Active incidents

No active simulated incidents

Clear

The example fabric is healthy. Select a fault mode to examine a simulated incident.

Engineering interpretation

Healthy links do not prove every service is healthy

Operational links and devices are a useful starting point. Validate the destination, route, and application path before declaring end-to-end service healthy.

Next diagnostic action

Validate a representative traffic path

Recommended

Test endpoint reachability and confirm the expected route and forwarding entry on the relevant devices.

No check run yet. Choose a scenario and run a health check.
Network Insight · Stage 01

Understand the Fabric — Completion Tracker

In Progress

Complete the two architecture activities below to establish your understanding of spine–leaf connectivity, fabric components and network health. Mark each activity complete after working through its interactive lab.

Stage 01 Progress 0 of 2 activities complete
Activity 01

Interactive Leaf–Spine Fabric

Explore spine switches, leaf switches, workloads and the connectivity of the fabric.

Activity 02

Fabric Health Dashboard

Inspect fabric status, link health and the operational indicators of the network.

Stage B — Follow Traffic

Stage 02 · Traffic investigation
Trace · Inspect · Verify

Follow Traffic

Follow traffic across the fabric, inspect the forwarding decisions at each hop, and understand how the network carries packets from source to destination.

Learning focus: packet paths, forwarding tables and reachability

Data Center Workspace / Investigation Lab

Traffic Investigation Lab

Trace a flow across a leaf–spine fabric. Select endpoints, inspect individual devices, advance through the forwarding journey and introduce a teaching fault to practise fault isolation.

Live trace view

Select a router or server to inspect its role and checks.

Fabric link Trace path Fault
LEAF–SPINE FABRIC Illustrative forwarding topology Server 1 10.10.1.11 Server 2 10.10.2.22 Server 3 10.10.3.33 Leaf 1 Access / L3 Leaf 2 Access / L3 Leaf 3 Access / L3 Spine 1 Transit Spine 2 Transit
Cross-leaf path · awaiting trace

Tip: select a node to open its engineering checks.

Investigation · Ready

Start at the source endpoint

Select the endpoints, then start the trace. Follow the illustrative forwarding path and verify each stage using device state and evidence.

Engineering checks
  • Confirm source IP address and subnet.
  • Check local link state and gateway configuration.
  • Identify the directly connected leaf.

Engineering insight

A topology shows possible connectivity. Forwarding tables, route lookups and packet evidence establish what is actually happening.

Ready. Choose endpoints and start the investigation.

Educational model only. The packet marker and fault scenarios are illustrative, not live packet forwarding or real device configuration. The selected spine represents one possible path; actual path selection depends on forwarding state, ECMP hashing, topology, policies and failures. A simulated fault does not calculate real network convergence.

Data Center Workspace / Fabric Investigation

Packet Path Visualizer

Trace a packet through a leaf–spine fabric, inspect each forwarding decision and compare local traffic with cross-leaf traffic. Follow the illustrative path one hop at a time.

Leaf–spine topology Ready to trace
Server A 10.0.1.10 Spine 1 Transit tier Spine 2 Transit tier Leaf 1 Access tier Leaf 2 Access tier Server C 10.0.1.20 Server B 10.0.2.10
Current device Visited device Destination reached
Source endpoint Server A · 10.0.1.10
Current forwarding device Awaiting start
Destination endpoint Server B · 10.0.2.10
Step 0 of 5 0% complete
READY

Choose a traffic scenario

Start the path to inspect the source, ingress leaf, transit device where required, destination leaf and receiving endpoint.

Forwarding observation This teaching model does not query live devices or forwarding tables.
Engineering checks
  • Select a scenario and start the trace.
  • Inspect each hop before advancing.
  • Compare the forward path with return-path requirements.

Path sequence

The highlighted entry identifies the current device. Select a step below to inspect it directly.

Model limitation: this is an illustrative forwarding walkthrough, not a live packet capture, network emulator or telemetry feed. Spine selection is a teaching choice, not a calculated ECMP result. Real forwarding depends on routing and forwarding state, topology, encapsulation, policy, hashing, link state and configuration. Same-leaf delivery also depends on the actual VLAN, subnet, routing and security design.

Network Insight · Interactive Lab 09

Forwarding Table Explorer

Trace how a fabric device uses a destination IP address, the most specific matching prefix and its programmed forwarding entry to decide the next action.

Example: 10.0.2.10
Illustrative forwarding state Leaf 1 · L3 forwarding
Fabric forwarding path Leaf 1 is checking the destination prefix.
Selected path Local delivery Other links
Leaf-spine forwarding topology Server A connects to Leaf 1, both leaf switches connect through two spine switches, and Leaf 2 connects to Server B. The selected forwarding path is highlighted after lookup. Server A 10.0.1.10 Spine 1 Transit Spine 2 Transit Leaf 1 Access / L3 Leaf 2 Access / L3 Local endpoint Leaf 1 subnet Server B 10.0.2.10 Awaiting lookup
Choose a device and run a lookup to highlight the modeled forwarding direction. Links represent a simplified fabric, not live telemetry.
Forwarding entries Select a row to test an address within that prefix.
Destination prefixNext hopInterface
Lookup result Longest-prefix match
Queried destination
10.0.2.10
Next hop selected

The best matching entry determines the next forwarding action in this example.

Matched prefix10.0.2.0/24
Next hop192.0.2.2
Outgoing interfaceEthernet1/2
Entry typeFabric next hop
Lookup methodLongest-prefix match

How the lookup works

1
Read the destination address

The device examines the destination IP address in the packet and performs a lookup in the relevant forwarding context.

2
Compare matching prefixes

Several entries may match. The longest matching prefix is the most specific route and is preferred within this simplified table.

3
Apply the forwarding action

The selected entry supplies a modeled connected interface, next hop, multipath group or no-forwarding result.

RIB versus FIB: the routing information base (RIB) holds routes used by routing processes. The forwarding information base (FIB) is programmed for packet forwarding. This lab models simplified forwarding entries; it does not query a real switch or prove that a physical adjacency is operational.
Network Insight · Stage 02

Follow Traffic — Completion Tracker

Not Started

Complete the three forwarding activities below to understand how traffic moves through the data centre fabric. Investigate traffic paths, visualise packet forwarding and inspect forwarding-table decisions. Mark each activity complete after finishing its lab.

Stage 02 Progress 0 of 3 activities complete
Activity 01

Traffic Investigation Lab

Investigate traffic flows, compare forwarding paths and observe traffic behaviour across the fabric.

Activity 02

Packet Path Visualizer

Trace packet movement between workloads and inspect the sequence of forwarding devices along the selected path.

Activity 03

Forwarding Table Explorer

Inspect forwarding-table entries and understand how next-hop information influences packet delivery.

Stage 03 — Diagnose and Recover

Stage 03 · Troubleshooting
Detect · Isolate · Recover

Diagnose and Recover

Investigate fabric failures, isolate the affected links or devices, verify routing and reachability, and work through the steps needed to restore connectivity.

Learning focus: failure scenarios, routing and end-to-end reachability
Diagnostic sequence
Data Center Network Workspace · Lab 05

Fabric Failure Lab

Investigate a fabric incident by examining the fault location, comparing the evidence, and choosing checks that isolate the failure boundary before attempting a fix.

Fabric topology · Fault map Scenario ready
Leaf-spine fabric fault map Two leaf switches connect to two spine switches. Each leaf also connects to an endpoint. Select a scenario to highlight the simulated fault. Server A Server B Leaf 1 Access / L3 Leaf 2 Access / L3 Spine 1 Transit Spine 2 Transit Traffic test Server A → Server B Choose a scenario to locate the fault
Leaf layer Spine layer Simulated fault Available link
The diagram represents an illustrative fabric, not live network telemetry.

Your investigation

Select the checks you would perform, then submit your diagnostic plan. More than one check may be appropriate.

Start with the evidence. Choose checks that help isolate the fault rather than guessing at the cause.
Educational simulation · No live switches, telemetry or packet captures are accessed.
Network Insight · Interactive Lab 10

Routing and Reachability Lab

Trace a destination through a leaf–spine fabric. Separate route presence from next-hop resolution, forwarding-path health and return-path availability.

Simulated fabric path Ready to test
Leaf–spine reachability topology Two servers connect to separate leaf switches. Both leaves connect to two spine switches. The highlighted path and fault markers update when a scenario is selected. ENDPOINTS SPINE TIER LEAF TIER Server A 10.0.1.10 Spine 1 Fabric switch Spine 2 Fabric switch Leaf 1 Ingress / egress Leaf 2 Ingress / egress Server B 10.0.2.10 ROUTE MISSING NEXT HOP LINK DOWN RETURN ROUTE MISSING Illustrative forwarding model · No live device state
Selected forward path Return path Failed link Red node = fault location
Test outcome

Ready to investigate

Choose a scenario and run the test to inspect the simulated route and forwarding state.

Route to destination Not tested
Next-hop resolution Not tested
End-to-end reachability Not tested

Diagnostic checklist

0 of 4 checks selected

Engineer’s task: run a scenario, then select the checks needed to isolate the fault.

Investigation findings

1
Route presence

Does the ingress device have a usable route to the destination?

2
Next-hop usability

Can the selected next hop resolve to a usable adjacency?

3
Path and return

Are the forward fabric path and return direction available?

Engineering principle: a route in the control plane does not guarantee packet delivery. Next-hop resolution, hardware forwarding programming, link state, policy and the return path can all affect reachability.

Teaching simulation with predefined outcomes. It does not send real packets, query routers, or verify actual network state. The selected ingress changes the direction of the modeled test; the scenarios are illustrative rather than a vendor-specific routing implementation.

Network Insight · Interactive Lab 11

Troubleshooting Challenge

Investigate the evidence, select the checks that matter, and build a defensible diagnosis. Each challenge tests a different failure domain in a simplified data centre fabric.

Incident briefing Ready to investigate

Intermittent server connectivity

Your objective

Engineering approach: collect evidence, isolate the failure domain, and verify the hypothesis before changing production configuration.
Data centre leaf–spine troubleshooting topology Server A connects to Leaf 1, which connects to two spine switches. The spines connect to Leaf 2 and Server B. Highlighted nodes and links illustrate the current challenge. SOURCE SPINE TIER DESTINATION Server A10.0.1.10 Spine 1Fabric switch Spine 2Fabric switch Leaf 1Source leaf Leaf 2Destination leaf Server B10.0.2.10 FAULT Illustrative topology · Not live telemetry
Available link Investigation path Suspected fault
Choose your diagnostic actions Select all appropriate checks before declaring a root cause.
Challenges submitted0 / 4
Best challenge score—
Current challenge scoreNot submitted

Educational simulation with predefined evidence and expected diagnostic actions. It does not query switches or verify actual network state. A diagnostic score measures alignment with this exercise, not real-world engineering competence.

Network Insight · Stage 03

Diagnose and Recover — Completion Tracker

Not Started

Work through three troubleshooting activities to understand how the fabric behaves under failure, diagnose routing and reachability problems, and apply a structured engineering investigation. Mark each activity complete after finishing its lab.

Stage 03 Progress 0 of 3 activities complete
Activity 01

Fabric Failure Lab

Simulate fabric device and link failures, observe traffic disruption and investigate recovery behaviour.

Activity 02

Routing and Reachability Lab

Investigate route availability, forwarding reachability and connectivity between network endpoints.

Activity 03

Troubleshooting Challenge

Use the available evidence to identify the likely fault, select an investigation path and verify the outcome.

Stage 04 — Make Safe Changes

Stage 04 · Change management
Plan · Apply · Validate

Make Safe Changes

Explore proposed network changes, assess their likely impact, and validate the result before treating a change as complete. Practise making controlled adjustments while protecting connectivity.

01
Plan the change

Identify the intended adjustment, affected devices and expected outcome.

Prepare
02
Apply carefully

Simulate the adjustment and observe how the fabric responds.

Execute
03
Validate the result

Check connectivity and confirm whether the intended outcome was achieved.

Verify
Learning focus: change impact, safe configuration and post-change verification
Validate before completion
Network Insight · Stage 04

Make Safe Changes — Completion Tracker

Not Started

Network changes should be deliberate, measurable and reversible. Use the Network Change Simulator to examine the effect of a proposed change, observe the network's response and validate the outcome before marking this stage complete.

Stage 04 Progress 0 of 1 activity complete
Activity 01

Network Change Simulator

Explore controlled changes to the network fabric, examine the resulting connectivity and operational state, and evaluate whether the change achieved the intended result.

Stage 05 — Test Knowledge

Stage 05 · Knowledge validation
Review · Test · Consolidate

Test Knowledge

Bring the learning journey together. Test your understanding of fabric architecture, packet forwarding, troubleshooting and safe network changes before reviewing your progress and identifying areas for further practice.

Your learning journey 5 stages · From foundations to validation
Understand
the Fabric
Follow
Traffic
Diagnose
and Recover
Make Safe
Changes
Test
Knowledge
Check understanding

Review key concepts and the reasoning behind network behaviour.

Find knowledge gaps

Identify topics that need another explanation or practical exercise.

Plan the next step

Use your results to guide further practice and investigation.

Learning focus: knowledge checks, learning progress and next steps
Learning review
Data Center Network Workspace · Lab 07

Network Change Simulator

Evaluate a proposed fabric change before implementation. Inspect the affected topology, check the baseline and safeguards, assess residual risk, then record an evidence-based go/no-go decision.

1 Review
2 Assess
3 Decide

Temporarily remove one uplink from service for maintenance while preserving a possible alternate path.

Fabric topology

Baseline view
Illustrative leaf-spine fabric topology Server A connects to Leaf 1. Leaf 1 connects to Spine 1 and Spine 2. Both spines connect to Leaf 2, which connects to Server B. The highlighted link indicates the selected change area, not live network state. SERVER EDGE LEAF–SPINE FABRIC UPLINK 1 UPLINK 2 PATH A PATH B Server A Endpoint Leaf 1 Leaf Spine 1 Spine Spine 2 Spine Leaf 2 Leaf Server B Endpoint Illustrative baseline · not live telemetry
Other links Change area Temporarily unavailable Proposed addition

Select a change to highlight the relevant area. The diagram is illustrative and does not represent a discovered or verified network.

Illustrative baseline

Active uplinks 4 / 4 Before change
Fabric devices 4 2 leaf · 2 spine
Leaf–spine paths 2 Illustrative paths

Pre-change checklist

0 of 5 checked
Select a proposed change, review the topology and checklist, then assess the risk before deciding whether to proceed.
Network Insight · Stage 05

Test Knowledge — Completion Tracker

Not Started

Consolidate your understanding of data centre networking by completing the Knowledge Check and Learning Progress activity. Review your answers, identify any areas requiring further practice, and mark the activity complete when you have finished.

Stage 05 Progress 0 of 1 activity complete
Activity 01

Knowledge Check and Learning Progress

Review essential fabric, forwarding, troubleshooting and change-management concepts. Check your understanding and identify your next learning goals.

Network Insight · Learning Centre

Your Data Centre Networking Progress

Review your learning journey across five stages. Track completed activities, revisit interactive labs and continue from your next unfinished task.

Overall Progress 0%
Activities Complete 0 / 10
Stages Complete 0 / 5
Total Learning Completion 0 of 10 complete
Next Recommended Activity Interactive Leaf–Spine Fabric

Continue your learning journey.

Learning Stage Breakdown

Progress is stored locally in this browser.

☕
Support Network Insight
Help support the development of interactive networking labs, BGP simulations, and educational content.
Support the Project
From theory to interactive practice

Don't Just Read the Network. Explore It.

You've explored data centre architecture, routing and resilient design. Now take the next step. Use the interactive simulator to investigate how network components and paths work together. Move beyond diagrams and start exploring network behaviour.

Network topology Traffic paths Routing decisions Failure scenarios
LAUNCH THE BGP CORE SIMULATOR Opens in a new browser tab.
Network in motion Illustrative
Illustrative leaf-spine topology Two spine switches connect to two leaf switches. Endpoint devices connect to the leaf switches. Animated dashed lines represent example traffic paths. SPINE 1 SPINE 2 LEAF 1 LEAF 2 HOST A HOST B HOST C HOST D
STEP 01 / OBSERVE Inspect the network Explore the topology, devices and available network state.
STEP 02 / TRACE Follow the behaviour Investigate routes, forwarding decisions and the paths traffic can take.
STEP 03 / INVESTIGATE Think like an engineer Use what you observe to reason about changes, redundancy and failures.
The topology above is illustrative. Open the simulator to explore the functionality it provides.