The OSI model separates communication responsibilities into seven conceptual layers. It does not require every computer to run seven distinct programs, or every real protocol to fit neatly into one box. Its practical value is turning “the network is broken” into smaller, testable questions.
Seven layers, seven kinds of question
| Layer | Responsibility | Diagnostic question |
|---|---|---|
| 7 — Application | Communication services for applications | Is DNS or HTTP returning the expected answer? |
| 6 — Presentation | Data representation and transformation | Do the endpoints interpret the data consistently? |
| 5 — Session | Dialogue and session organization | Is the communication context maintained? |
| 4 — Transport | End-to-end transport services | Can the required transport protocol and port be reached? |
| 3 — Network | Addressing and forwarding across networks | Are the IP configuration and route correct? |
| 2 — Data link | Frame delivery on a local link | Are VLAN membership and local adjacency correct? |
| 1 — Physical | Signals across the medium | Is the physical link present? |
The layer names and architecture come from ITU-T X.200. The diagnostic questions are a practical interpretation, not an exhaustive classification rule.
Do not force TCP/IP into identical boxes
The Internet stack is commonly described using link, internet, transport and application layers. RFC 1122 uses that different architectural framework. Upper-layer functions can be combined in applications and libraries. A website's session cookie is therefore not simply synonymous with the OSI session layer.
Likewise, memorizing TLS as exclusively “Layer 6” does not explain every deployment. Common HTTPS over HTTP/1.1 or HTTP/2 uses TLS over TCP, whereas HTTP/3 uses QUIC. Assuming all web traffic uses TCP can send a diagnosis in the wrong direction.
Break a web failure into observations
- No link: inspect the cable, port, wireless association and interface state.
- Link but no local communication: inspect VLAN membership, addressing and neighbor resolution.
- Local access but no remote access: inspect routes, gateway and access policy.
- IP access but failed name lookup: investigate DNS separately.
- Established connection with a certificate or HTTP error: move to TLS and application evidence.
A successful test is not a certificate of perfect health for every lower-layer behavior. Ping does not test the application's transport port, and a link light does not establish correct VLAN membership.
One device can implement several roles
A home gateway can combine routing, switching, Wi-Fi, DHCP and firewalling. A switch may also support Layer 3 functions. Diagnose the failing function rather than assigning the whole product to one layer; the device-role comparison makes that distinction concrete.
Instead of writing only “Layer 3 issue,” record something verifiable: the client is in the intended VLAN, the gateway responds, but the destination prefix has no route. Use the model to organize evidence, not to replace it.
Related Articles
Comments ()
Leave a Comment
Sponsors
Apps
