Free tools Windows power users keep installed
One-click scans. No signup required.
The OSI model divides the work of moving information between networked computers into seven numbered layers, from Physical (1) at the bottom to Application (7) at the top. It works well as a shared vocabulary for saying where a function or a fault belongs. It is not a literal diagram of every modern network stack, and many real protocols do not sit neatly inside a single box.
The seven layers at a glance
Cisco’s documentation describes the reference model as dividing the tasks involved in moving information between networked computers into seven smaller, more manageable task groups. IBM’s documentation numbers the layers 1 through 7 and stresses that each layer describes a function, not a required list of specific protocols. The table below lists each layer with its function and the example most often used to anchor it.
![Computer Networking Bible: [3 in 1] The Complete Crash Course to Effectively Design, Implement and Manage Networks. Including Sections on Security, Performance and Scalability](https://m.media-amazon.com/images/I/412FG7F+RjL._SL160_.jpg)
As an Amazon Associate I earn from qualifying purchases.
| Layer number | Layer name | Function as described in the reference model | Common example |
|---|---|---|---|
| 1 | Physical | Transmission of signals and bits over a physical medium | The cable, fiber, or radio link itself |
| 2 | Data Link | Local link delivery and framing | Ethernet (placed at Layer 2 in Cisco technical material) |
| 3 | Network | Logical addressing and movement between networks | IP (placed at Layer 3 in Cisco technical material) |
| 4 | Transport | End-to-end transport services | TCP and UDP (placed at Layer 4 in Cisco technical material) |
| 5 | Session | Organization and management of communication sessions | Not separately defined in TCP/IP; IBM folds it into its application layer |
| 6 | Presentation | Representation and formatting of data | Not separately defined in TCP/IP; IBM folds it into its application layer |
| 7 | Application | Network-facing services used by applications | Application protocols such as those an application uses to send or fetch data |
Why seven boxes help
A network request involves cables, addressing, routing, reliable delivery, data formatting, and the program that wants the data. Putting these into one undifferentiated process makes it hard to discuss any single part. The layer numbers give engineers shorthand: “this is a Layer 3 problem” points to addressing or routing, while “this is a Layer 4 problem” points to connection or delivery behavior. That shorthand is the model’s real value.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Using the layers to reason about a problem
Layer numbers are most useful as a checklist for narrowing down where a fault could be. A common approach, which is a reasoning method rather than a guaranteed procedure, works upward from the bottom:
#1 Best Overall
- Confirm the physical link (Layer 1). Check that the interface is up and the cable or radio link is connected before looking at anything else.
- Check local delivery (Layer 2). Confirm that frames reach the local segment and that the device is seeing its neighbours on that segment.
- Check addressing and routing (Layer 3). Confirm that the host has a valid IP address and a route to the destination network.
- Check transport (Layer 4). If the network path works but a connection fails, look at whether TCP or UDP traffic is being accepted, blocked, or reset on the destination port.
- Check the upper layers (5 to 7). Once lower layers are confirmed, examine the application’s session handling, data formatting, and the service’s own behaviour.
Treat each step as a hypothesis to rule out, not as proof. A symptom that appears to be an application error can originate lower down, and a problem found at one layer can be caused by a dependency at another.
Where the boxes mislead
The layers are a reasoning aid, and several limits matter when you apply them:
- Protocols do not always follow the model. IBM explicitly notes that many protocols do not closely follow OSI.
- Dependencies cross boundaries. Name resolution, encryption, and address assignment each depend on functions in more than one layer, so a single fault can surface at several.
- Layer 5 and Layer 6 are often blurred. In the model they are distinct, but many real implementations handle session and formatting inside the application or inside a library the application uses.
- Layer numbers are not universal labels. Vendor documents and textbooks sometimes use the same number for different emphasis, so check which source you are reading before comparing notes.
How OSI compares with TCP/IP
Most of the networks people use run the TCP/IP protocol suite, which is commonly described with four layers rather than seven. IBM’s comparison maps the TCP/IP layers onto OSI as follows:
| OSI layer(s) | Common example or concept | TCP/IP layer |
|---|---|---|
| Application, Presentation, Session (7, 6, 5) | Application protocols, data representation, and session functions | Application |
| Transport (4) | TCP, UDP | Transport |
| Network (3) | IP | Internet |
| Data Link, Physical (2, 1) | Ethernet link and transmission medium | Network access |
These are teaching correspondences. The mapping is broad, not exact: TCP/IP’s transport layer corresponds broadly to OSI transport, and its internet layer corresponds broadly to OSI network. IBM describes TCP/IP as the protocol suite used in most networks and OSI as a standardized framework for describing communication, which is why OSI is best used as a vocabulary rather than as the architecture of a running system.
Anchor examples to remember
Three examples cover the most common references. Each one is a fair teaching anchor, but real technologies can span or interact with more than one layer.
- Ethernet at Layer 2. Cisco technical material places Ethernet here, handling framing and delivery on the local link.
- IP at Layer 3. IP handles logical addressing and moves packets between networks.
- TCP and UDP at Layer 4. These are the transport protocols that sit above IP and define how end-to-end delivery is handled, with TCP providing connection-oriented delivery and UDP providing a lighter, connectionless service.
Further study
For a structured treatment of these layers, a networking fundamentals textbook or a CCNA study guide covers the model alongside protocol detail. Cisco Press lists a Networking Essentials companion guide as an official supplemental textbook, which is one place to look for that material.
Rank #4
Sources cited in this article: IBM Documentation, Networks, AIX 7.1; IBM Think, What Is the OSI Model?; Cisco Systems, The Seven Layer Model; Cisco Press, Network Communication Models (5.3) > Communication Principles. The source materials do not provide quantitative figures for how often the model is used or how effective it is in troubleshooting, so this article makes no such claims.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThe Bottom Line
Use the OSI model as a common language for locating functions and faults: seven layers, numbered from Physical to Application, with Ethernet, IP, and TCP/UDP as useful anchors at Layers 2, 3, and 4. Do not expect every protocol to fit one box, and do not treat the layer number as proof of where a problem lives.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
