Seven layers. Everyone tells you to memorise them. Almost nobody tells you why you’d bother.
Here’s the why. The OSI model is a fault-finding tool. When a user says “the internet is down,” the model turns that into a list you can work through in order until you find the layer that’s lying to you. Cable, MAC, IP, port, session, format, app. That’s the whole trick.
The model itself comes from ISO/IEC 7498-1, first published in 1984 and revised in 1994. It was never meant to be built, only to be reasoned with. And that’s still what it’s good for.
How to memorise the 7 layers
Two mnemonics. Learn one, not both, or you’ll mix up the direction.
Layer 1 up to layer 7:
Please Do Not Throw Sausage Pizza Away
Physical, Data link, Network, Transport, Session, Presentation, Application
Layer 7 down to layer 1:
All People Seem To Need Data Processing
Application, Presentation, Session, Transport, Network, Data link, Physical
Pick the pizza one if you think bottom-up, which is how most troubleshooting goes. Pick the other if you’re mapping an app down to the wire.
Honestly, the mnemonic is the easy part. Knowing that a switch is layer 2 and a router is layer 3 without pausing is what exams and interviews actually test. The PDU column in the table above is worth more study time than either rhyme.
OSI model vs TCP/IP model
The OSI model has seven layers. The TCP/IP model, the one defined in RFC 1122 and the one the internet actually runs on, has four. TCP/IP came first, so it’s more accurate to call OSI the alternative rather than the other way round.
Here’s how they line up.
| OSI (7 layers) | TCP/IP (4 layers) |
|---|---|
| 7 Application | Application |
| 6 Presentation | Application |
| 5 Session | Application |
| 4 Transport | Transport (host to host) |
| 3 Network | Internet |
| 2 Data link | Network access (link) |
| 1 Physical | Network access (link) |
Short version: TCP/IP folds OSI’s top three into one application layer, and OSI’s bottom two into one link layer. Layers 3 and 4 map one to one.
So which one should you learn? Both, and for different reasons. TCP/IP describes what’s running on your network right now. OSI gives you the vocabulary everyone uses to talk about it. Nobody says “a network access layer problem.” They say “it’s a layer 2 issue.” That’s OSI language, on a TCP/IP network, every day.
Troubleshoot with the OSI model
This is the part most cheat sheets skip. Three approaches, pick one and stick to it for the whole ticket.
Bottom-up. Start at layer 1 and climb. Cable in? Link light on? Right VLAN? IP address correct? Port open? Best when the fault smells physical, or when a whole site is dark.
Top-down. Start at layer 7 and descend. Does the app work for anyone? Does the URL resolve? Best when one application is broken and everything else is fine.
Divide and conquer. Start at layer 3. Ping the gateway. Up from there if it works, down from there if it doesn’t. Fastest on a network you already know. This is what experienced engineers do by reflex.
The quick check that saves the most time: ping the default gateway. Success means layers 1 through 3 are alive and you can stop looking down there. Failure means stop looking up.
What’s inside the PDF
- The full 7-layer table with function, PDU, devices and protocols per layer, sized to stay readable when printed on A4 or Letter
- Both mnemonics with the direction marked, so you don’t learn them backwards
- The OSI to TCP/IP map side by side
- PDU flow diagram showing encapsulation down the stack and decapsulation back up
- Devices by layer strip covering hub, switch, router, firewall and load balancer
- Common ports quick list for the protocols on the sheet
- Troubleshooting order card with the three approaches and when to reach for each
- Ten self-test questions on the back, answers upside down at the bottom
One page, both sides. No fluff, no 40-page textbook.
Who it’s for
- CCNA 200-301 candidates who need layer 2 and layer 3 straight before subnetting makes sense
- CompTIA Network+ and Security+ students, where OSI questions turn up in nearly every practice set
- Help desk and NOC staff who want a repeatable order for working a ticket
- Anyone sitting a technical interview where “what layer does a switch operate at” is question three
- Instructors who want a printable handout for a classroom
This one’s beginner level. If you’re already comfortable here, our EIGRP and BGP guides are the next step up.
