Simple explanation
The OSI model breaks networking into 7 conceptual layers, each responsible for one piece of the job of getting data from one device to another. It's a mental map for troubleshooting: "which layer is this problem actually in?"
Technical explanation
From bottom to top:
- Physical — actual bits on the wire/air: cables, connectors, radio signals, voltage.
- Data Link — frames, MAC addresses, switches operate here (physical addressing on the local segment).
- Network — packets, IP addresses, routers operate here (logical addressing and routing between networks).
- Transport — segments, TCP (reliable, connection-oriented) and UDP (unreliable, connectionless), ports.
- Session — establishing, managing, and tearing down communication sessions between applications.
- Presentation — data formatting/translation, encryption, compression (making sure data is in a usable format for the application).
- Application — the actual protocol the end-user application speaks (HTTP, DNS, SMTP) — NOT the application software itself, a common point of confusion.
Each layer only talks to the layer directly above and below it, and each layer on the sending device communicates conceptually with the same layer on the receiving device (encapsulation going down, de-encapsulation coming back up).
Synonyms / related terms
| Term | Means | |---|---| | PDU | Protocol Data Unit — the layer-specific name for data (frame at L2, packet at L3, segment at L4) | | L2/L3/L4 | Shorthand for Data Link / Network / Transport layers | | Encapsulation | Wrapping data with each layer's header as it moves down the stack |
Concept Check
"A user can ping a server by IP address but the switch shows the port as down/down." This isn't a Network layer (IP) problem despite the symptom involving an IP-based test — a down/down port status points to Physical layer (Layer 1): no signal, bad cable, or disabled port, which would prevent the ping from ever getting the chance to succeed in the first place. (In practice this scenario is contradictory — a truly down/down port means the ping shouldn't work at all — which is exactly why real OSI-layer troubleshooting questions ask you to isolate which single symptom points to which single layer.)
Interview-style Q&A
Q: Why bother memorizing all 7 layers instead of just knowing 'networking stuff happens'? A: "Because it gives structured troubleshooting. If DNS resolution fails, that's Application layer — no point checking cables. If a cable's unplugged, that's Physical — no point checking DNS. The model lets you narrow down where to look instead of guessing across the whole stack."
Memory trick
"Please Do Not Throw Sausage Pizza Away" — Physical, Data Link, Network, Transport, Session, Presentation, Application — bottom to top, the classic mnemonic that's stuck around because it works.