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.
The 7 OSI Layers and Their Protocols

| No. | Layer | Function | Data unit | Hardware | Protocols |
|---|---|---|---|---|---|
| 7 | Application | Human-computer interaction through applications that access network services | Message/data | Gateway | UPnP, DHCP, DNS, HTTP, HTTPS, NFS, NTP, POP3, SMTP, SNMP, FTP, Telnet, SSH, TFTP, IMAP |
| 6 | Presentation | Data formatting and encryption/decryption | Message/data | Gateway redirector | TLS, SSL, AFP |
| 5 | Session | Inter-host communication | Message/data | Gateway | NetBIOS, RPC, SMB, Socks |
| 4 | Transport | Data transmission | TCP: segment; UDP: datagram | Gateway | TCP, UDP, SCTP |
| 3 | Network | Path determination and logical addressing | Packet, datagram | Router, Brouter | ARP, IP, NAT, ICMP, IPsec, ICMP (ping) |
| 2 | Data Link | Physical addressing | Frame, cell | Switch, bridge, NIC | ARP, Ethernet, L2TP, LLDP, MAC, NDP, PPP, PPTP, VTP, VLAN |
| 1 | Physical | Binary signal transmission over physical media | Bit, frame | Cables, modem, hub, repeater, NIC, multiplexer | Ethernet, IEEE802.11, ISDN, USB, Bluetooth |
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. If VLANs are still fuzzy, start at what a VLAN is and work up.
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.
How an Email Actually Moves Through All 7 Layers
Picture an email landing on your phone. Working backward from that “new message” notification shows every layer doing its one job.
At layer 1, radio signals from your Wi-Fi access point arrive as a raw stream of bits. The physical layer strips off the preamble and start frame delimiter (the markers that say a frame is starting) and the frame check sequence at the end (the error check), then hands the rest up as a frame.
At layer 2, your phone’s networking hardware reads the source and destination MAC addresses. If the destination MAC matches your device, the frame moves up as a packet. If it doesn’t, it’s dropped right there, MAC addresses only mean something inside one local network.
At layer 3, the network layer reads IP addresses instead of MAC addresses, using ARP to resolve one into the other and, often, NAT to translate addresses at the edge of your network. If the destination IP is yours, the IP header comes off and what’s left, usually a TCP segment or a UDP datagram, moves up to transport.
At layer 4, TCP reassembles the segments. An Ethernet frame only carries so much (1500 bytes is the common limit), so a real email arrives split across several segments that transport stitches back into one message. For the full list of ports these protocols use, see our Common Ports Cheat Sheet.
At layer 5, the session layer tracks which port number your mail app is listening on, so the reply, or an error if your mailbox was full, goes back to the right place.
At layer 6, if your mail uses POP3S, IMAPS, or an end-to-end encrypted provider, TLS/SSL at the presentation layer decrypts the message into something the app can actually read.
At layer 7, the application layer is just your email client doing its job, and the same layer handles the APIs that send automated mail in the other direction, receipts, resets, newsletters.
Sending works in reverse: each layer wraps the data in its own header on the way down (encapsulation), and the receiving side strips those headers off one by one on the way back up (decapsulation). That’s the whole model, in one email.

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.
Go deeper
This sheet gets the model into your head. The CCNA Workbook puts it to work across 75 hands-on labs, so OSI stops being theory the moment you start subnetting and troubleshooting for real.See the CCNA Workbook →
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 cheat sheet and BGP vs OSPF guides are the next step up.
No questions yet. Ask the first one.