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.
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.
Learning Control Bar
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.
Begin by exploring the architecture of the fabric.
Open ActivityComplete each interactive activity and mark it finished in your stage completion tracker. Progress is shared across the workspace.
View Full Progress TrackerStage A — Understand the Fabric
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.
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.
Ready. Select a device or connection to explore the topology. This is an illustrative model, not a live network simulation.
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.
Fabric topology
Teaching model only. The displayed paths are illustrative; real traffic paths depend on the network design, forwarding state, and traffic destination.
Link status
| Connection | State | Role |
|---|---|---|
| Leaf 1 – Spine 1 | Up | Uplink |
| Leaf 1 – Spine 2 | Up | Uplink |
| Leaf 2 – Spine 1 | Up | Uplink |
| Leaf 2 – Spine 2 | Up | Uplink |
Active incidents
No active simulated incidents
ClearThe example fabric is healthy. Select a fault mode to examine a simulated incident.
Engineering interpretation
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
RecommendedTest endpoint reachability and confirm the expected route and forwarding entry on the relevant devices.
Understand the Fabric — Completion Tracker
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.
Interactive Leaf–Spine Fabric
Explore spine switches, leaf switches, workloads and the connectivity of the fabric.
Fabric Health Dashboard
Inspect fabric status, link health and the operational indicators of the network.
Stage B — Follow Traffic
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.
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.
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.
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.
Choose a traffic scenario
Start the path to inspect the source, ingress leaf, transit device where required, destination leaf and receiving endpoint.
- 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.
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.
| Destination prefix | Next hop | Interface |
|---|
The best matching entry determines the next forwarding action in this example.
How the lookup works
The device examines the destination IP address in the packet and performs a lookup in the relevant forwarding context.
Several entries may match. The longest matching prefix is the most specific route and is preferred within this simplified table.
The selected entry supplies a modeled connected interface, next hop, multipath group or no-forwarding result.
Follow Traffic — Completion Tracker
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.
Traffic Investigation Lab
Investigate traffic flows, compare forwarding paths and observe traffic behaviour across the fabric.
Packet Path Visualizer
Trace packet movement between workloads and inspect the sequence of forwarding devices along the selected path.
Forwarding Table Explorer
Inspect forwarding-table entries and understand how next-hop information influences packet delivery.
Stage 03 — Diagnose and 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.
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.
Your investigation
Select the checks you would perform, then submit your diagnostic plan. More than one check may be appropriate.
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.
Ready to investigate
Choose a scenario and run the test to inspect the simulated route and forwarding state.
Diagnostic checklist
0 of 4 checks selected
Investigation findings
Does the ingress device have a usable route to the destination?
Can the selected next hop resolve to a usable adjacency?
Are the forward fabric path and return direction available?
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.
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.
Intermittent server connectivity
Your objective
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.
Diagnose and Recover — Completion Tracker
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.
Fabric Failure Lab
Simulate fabric device and link failures, observe traffic disruption and investigate recovery behaviour.
Routing and Reachability Lab
Investigate route availability, forwarding reachability and connectivity between network endpoints.
Troubleshooting Challenge
Use the available evidence to identify the likely fault, select an investigation path and verify the outcome.
Stage 04 — Make Safe Changes
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.
Identify the intended adjustment, affected devices and expected outcome.
Simulate the adjustment and observe how the fabric responds.
Check connectivity and confirm whether the intended outcome was achieved.
Make Safe Changes — Completion Tracker
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.
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
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.
the Fabric Follow
Traffic Diagnose
and Recover Make Safe
Changes Test
Knowledge
Review key concepts and the reasoning behind network behaviour.
Identify topics that need another explanation or practical exercise.
Use your results to guide further practice and investigation.
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.
Temporarily remove one uplink from service for maintenance while preserving a possible alternate path.
Fabric topology
Baseline viewSelect a change to highlight the relevant area. The diagram is illustrative and does not represent a discovered or verified network.
Illustrative baseline
Pre-change checklist
0 of 5 checkedTest Knowledge — Completion Tracker
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.
Knowledge Check and Learning Progress
Review essential fabric, forwarding, troubleshooting and change-management concepts. Check your understanding and identify your next learning goals.
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.
Continue your learning journey.
Learning Stage Breakdown
You have marked all 10 networking activities complete. You can revisit any lab or reopen activities for further practice. Completion is self-reported and does not represent a formal certification.
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.
Recommended Reading
Build on what you have learned about data centre networking. Follow this reading path to connect network architecture with routing behaviour, resilient design and the topologies that bring it all together.
SDN in the Data Centre
Explore software-defined networking and the relationship between network control, infrastructure and traffic management. Consider how a programmable approach changes the way a data centre is designed and operated.
IP Forwarding and Routing Protocols
Connect route learning with actual packet delivery. Understand the different roles of routing protocols, routing tables and the forwarding process when traffic travels through a network.
Data Centre Active-Active Design
Move from individual routing decisions to the broader question of how a design can keep services available. Examine active-active thinking in the context of paths, traffic distribution and resilient infrastructure.
Data Centre Topologies
Explore how network devices and links are arranged into a complete design. Relate topology choices to scalability, redundant paths, traffic movement and the practical limits of a data centre fabric.
Where to go next
Read the articles in sequence. As you progress, ask yourself three questions: Where is the path determined? Which device forwards the packet? And what happens when a link or device fails? Use those questions to connect the concepts to real data centre designs.