08 — THE OSI MODEL (PRACTICALLY)

7 layers, but only 4 you'll touch daily.

Estimated 10 minutes.

A model, not a recipe.

The OSI model is a 7-layer stack used to describe how networks work. It was standardized in 1984 (ISO 7498). No real network strictly follows it — but it's the universal vocabulary engineers use to talk about problems.

The 7 layers.

Practical layers in gold. Layers 5 and 6 rarely matter on the plant floor.

Each layer adds something.

Data starts at the top (your application). As it goes down, each layer wraps the data with its own header — IP address, MAC, etc. On the other side, each layer peels its header off until the application sees the original data.

Tap a layer.

Explore at least 4 layers to continue.

Why bother with layers?

Because problems live at one layer. If you know which layer, you know what to check. A bad cable is L1. An IP conflict is L3. A wrong Modbus register is L7. The wrong tool at the wrong layer wastes hours.

Peel the packet.

Tap the packet to expand it. Hover any layer to see what it carries. Hit SEND — watch the packet travel and de-encapsulate at the other end.

Symptom → layer.

A field engineer's shortcut.

No link light.

You plug in an Ethernet cable and the link light on the switch never comes on. Which layer?

  • L1 Physical
  • L3 Network
  • L7 Application

Wrong register.

Communication works. You read register 40001 and get a value that doesn't match the documentation. Which layer?

  • L3 Network
  • L4 Transport
  • L7 Application

Tools by layer.

Different layers need different tools. L1: a cable tester or a link light. L2/L3: ping, ARP, the switch's port table. L4: telnet to the port, nmap. L7: a protocol-specific client like ModScan or KEPServerEX.

Ping works, Modbus times out.

Ping replies normally. Modbus times out. Where's the problem?

  • L1 — bad cable
  • L3 — IP routing
  • L4 — port blocked, or L7 — Modbus disabled

Layers 5 and 6 — skip them.

Session and Presentation rarely come up in industrial work. Most modern protocols collapse them into the application layer. Don't waste time learning them in detail. Knowing they exist is enough.

You can locate any problem.

  • 7 layers; in practice, focus on L1, L2, L3, L4, L7.
  • Each layer wraps data with its own header.
  • Symptom tells you the layer. Layer tells you the tool.
  • Skip L5 and L6 unless you have a specific reason.

Lesson 08 complete.

  • You can name the layers that matter.
  • You can map a symptom to a layer.
  • You know which tool to reach for.