The seven-layer map 10 min read
The OSI and TCP/IP Models
Use the seven-layer model as a troubleshooting map—not certification trivia—and connect each layer to familiar AV equipment and failures.
- Name the seven OSI layers and the practical job of each.
- Relate the OSI model to the simpler TCP/IP model.
- Place common AV protocols and failures at the appropriate layers.
- Use bottom-up troubleshooting without becoming trapped by the model.
A model, not a machine
The OSI model divides network communication into seven conceptual layers. Your packet does not physically stop at seven little departments. The model gives engineers a common vocabulary for describing where a function or failure belongs.
The TCP/IP model groups the same work into fewer layers. Real products do not always fit perfectly into either diagram, and that is fine. Their value is helping us ask the next useful question.
The layers from the cable upward
Layer 1 is Physical: copper, fiber, radio, connectors, light levels, link speed, and electrical signaling. Layer 2 is Data Link: Ethernet frames, MAC addresses, switching, VLAN tags, and link-local discovery. Layer 3 is Network: IP addresses, subnets, gateways, and routing.
Layer 4 is Transport: primarily TCP and UDP. TCP emphasizes reliable, ordered delivery; UDP minimizes overhead and delay. Layers 5 through 7 describe sessions, representation, and applications. In day-to-day IT work, those upper layers are often discussed together as the application layer.
- 7 Application — services visible to software and users
- 6 Presentation — data format, encoding, compression, encryption
- 5 Session — establishing and maintaining conversations
- 4 Transport — TCP/UDP delivery behavior and port numbers
- 3 Network — IP addressing and routing
- 2 Data Link — Ethernet, MAC addresses, switching, VLANs
- 1 Physical — signals, media, connectors, optics, and radio
Troubleshoot from evidence
Bottom-up troubleshooting starts with power and the physical path, then progresses through link, VLAN, addressing, routing, and the application. This prevents an engineer from changing multicast settings when the fiber is dark.
Do not treat the order as a religion. If logs show an expired certificate, start at the application and security layer. The model organizes evidence; it does not replace judgment.
Put it in an AV system.
Decoder has no link
Start at Layer 1: PoE, patching, copper certification, SFP type, polarity, and optical level. There is no reason to debug IP addressing until the link exists.
Web interface works, video does not
Layers 1–3 may be healthy. Investigate transport and application requirements such as multicast membership, stream format, clocking, bandwidth, or authorization.
- OSI
- Open Systems Interconnection; the seven-layer conceptual network model.
- TCP/IP
- The practical protocol suite and simpler layered model used by modern IP networks.
- TCP
- A connection-oriented transport protocol with ordered delivery and retransmission.
- UDP
- A connectionless transport protocol with low overhead and no built-in retransmission.
Place the fault
A camera links at 1 Gbps, receives the expected IP address, answers a ping, and opens its webpage, but its video stream never appears. List the layers already supported by evidence and the higher-layer items you would test next.
Three quick questions.
01Which layer contains VLAN tags and MAC addresses?
Layer 2, the Data Link layer.
02Which layer contains IP addressing and routing?
Layer 3, the Network layer.
03Does a working ping prove an AV application works?
No. It supports basic Layer 3 reachability but does not test every transport, security, timing, or application requirement.