01 / ONE SWITCH FOR A RACK
Meet the Top-of-Rack switch
A Top-of-Rack (ToR) switch is a network switch deployed at the rack level. Servers in that rack connect their NICs to server-facing ports on the switch. The ToR switch then links those local connections toward the wider network through one or more uplinks.
“Top-of-Rack” describes a common network architecture or deployment pattern. The switch does not have to occupy the highest rack unit. Placing switching near the servers can organize local connections, keep many server-facing cable runs within the rack, and make rack designs repeatable.
ToR is one common approach, not a universal best choice. Facility size, cabling, capacity, operations, and network architecture all affect where switching equipment belongs.

MANY SERVERS · ONE RACK SWITCH
How one rack connects upstream
Each server uses a NIC and a physical link to reach a server-facing port on the rack switch. Multiple local connections converge at that switch; the switch’s uplink or uplinks then connect toward upstream network equipment.
- SERVER 1NIC → server-facing link
- SERVER 2NIC → server-facing link
- SERVER 3NIC → server-facing link
- SERVER 4NIC → server-facing link
- UPLINK(S)From the rack switch
- UPSTREAM NETWORKAdditional switching and wider connectivity
02 / TWO LINK ROLES
Server-facing links and uplinks have different jobs
A server-facing link connects a local endpoint—such as a server NIC—to a ToR switch port. An uplink connects that rack switch toward additional network infrastructure.
“Downlink” and “uplink” describe the link’s place in a topology. They do not mean traffic only travels down or up: network communication can flow in either direction. The number of links and their speeds depend on the design; there is no single bandwidth ratio that applies to every rack.

LOCAL CONNECTIONS
Server-facing links / downlinks
- Connect local servers and endpoints
- Run from server NICs to ToR switch ports
- Terminate at the rack switch
UPSTREAM CONNECTIONS
Uplinks
- Connect the rack switch to other network infrastructure
- Carry rack connectivity beyond the rack
- May be one or multiple links, depending on design
03 / FROM ONE RACK TO MANY
Each rack switch needs a path beyond its rack
A data center row can contain many racks, each with its own servers and rack-level switch. Each ToR switch needs upstream connectivity. Those rack-by-rack connections become part of a larger network architecture.
The mental model expands from one server, to one rack, to many racks, and then to the larger network that connects systems and services across the facility.

RACK 1
- Servers
- ToR 1
- Uplink(s)
RACK 2
- Servers
- ToR 2
- Uplink(s)
RACK 3
- Servers
- ToR 3
- Uplink(s)
THE NEXT ARCHITECTURE QUESTION
Where do all the ToR uplinks go?
They connect into additional switching infrastructure that forms the larger data-center network fabric. Spine-leaf is one common modern architecture for connecting many rack or leaf switches through a wider set of switches.
Explore how that architecture connects racks in Network 101 Lesson 04. For now, remember that the ToR switch is one layer in a larger path—not the final destination.
TRACE SERVICE DEPENDENCIES
A healthy server can still lose network connectivity
A server may have power, healthy compute, a working NIC, and a healthy local cable—but still lose required service connectivity if its only ToR switch fails or its required upstream path disappears. The actual impact depends on the network design, alternate paths, configuration, and application architecture.
Follow every step and ask what depends on it. What happens to the service if this switch or path disappears?
- SERVER✓ HEALTHY
- NIC✓ HEALTHY
- LOCAL LINK✓ HEALTHY
- ToR SWITCH✓ HEALTHY
- UPLINK! FAILED
- UPSTREAM CONNECTIVITY! IMPACTED
A PREVIEW OF NETWORK REDUNDANCY
More than one path can help—but trace both
Some designs connect a server over Path A to Switch A and over Path B to Switch B. Multiple paths can provide another route, but two paths do not automatically mean two independent paths. They may still share upstream equipment, cabling routes, power, or other dependencies.
- SERVER NIC / PATH A
- SWITCH A
- UPSTREAM PATH A
- SERVER NIC / PATH B
- SWITCH B
- UPSTREAM PATH B
We’ll examine network paths and resilience in Network 101 Lesson 05. Before that, Lesson 04 builds the picture of how many rack switches connect into a fabric.
THREE THINGS TO REMEMBER
Carry this mental model forward
- A Top-of-Rack switch connects servers in a rack toward the wider network.
- Server-facing links connect local equipment; uplinks connect the rack switch upstream.
- A healthy server can still lose service connectivity if its ToR or required upstream path fails.
CONNECT THE SYSTEMS THINKING
Keep tracing data-center dependencies
The current DataCenterTwin workstation models facility power, cooling, and their relationships. It does not simulate ToR failures, packet routing, or network topology. You can still use the existing facility-building lab to explore how infrastructure dependencies affect a data center.