The OSI model explained for Network Plus, without the jargon
Most learners memorize "Please Do Not Throw Sausage Pizza Away" and call it a day. That gets you the names. It does not get you the exam. CompTIA Network Plus objective 1.1 wants you to know what lives at each layer, what breaks at each layer, and where in real troubleshooting you reach for which one. Here is the walkthrough, layer by layer, in plain English.
What is the OSI model, really
The OSI model is a seven-layer reference model that describes how data moves from one application on one machine to an application on another. It was published by ISO in 1984 as ISO/IEC 7498-1. Nobody actually implements pure OSI. Real networks run TCP/IP. But the OSI map is the language the industry, vendors, and CompTIA all use to talk about where a problem lives.
For Network Plus N10-009, you need to know all seven layers, what protocol data unit (PDU) lives at each layer, the primary device, a common protocol or example, and what kind of failure happens there. That is the framework. Let us walk it.
Layer 1: Physical, the road itself
Layer 1 is the physical wire, the radio wave, the fiber strand. PDU is bits, ones and zeros. Primary device is the hub or a transceiver. Common examples are Cat 6 cable, RJ45 connectors, 1000BASE-T, and 802.11 radio. When Layer 1 breaks, you see no link light, you see a dead port, you see a cut fiber.
On the job this is the cable that the cleaning crew unplugged, the port a coworker accidentally yanked, the run that got crushed under a chair leg. You confirm Layer 1 first because if it is broken, everything above it is broken too.
Layer 2: Data Link, addressing the local hop
Layer 2 moves frames between devices on the same network segment. PDU is the frame. Primary device is the switch. Addressing is the MAC address, a 48-bit hardware identifier burned into the network adapter. Common protocols include Ethernet itself, 802.1Q VLAN tagging, and ARP for mapping IP to MAC.
Layer 2 failures look like a workstation that can ping its own subnet but nothing else, a VLAN misconfigured on a trunk port, or a MAC address table flapping. The IEEE 802 standards family lives here. When you read about 802.3 (Ethernet) or 802.11 (Wi-Fi), you are reading Layer 2 specs that also reach down into Layer 1.
Layer 3: Network, getting across the city
Layer 3 is where IP lives. PDU is the packet. Primary device is the router or a Layer 3 switch. Common protocols are IPv4, IPv6, ICMP, and OSPF or BGP for routing. Addressing is the IP address, which is logical, not physical, so it can change.
Layer 3 failures are the ones that feel like "the internet is down" but really mean "my default gateway is unreachable" or "DNS resolved but the route to that subnet is broken." When you run ping or tracert, you are testing Layer 3 reachability and Layer 3 path.
Layer 4: Transport, splitting the load
Layer 4 manages end-to-end delivery between two hosts. PDU is the segment for TCP or the datagram for UDP. There is no dedicated device, though firewalls inspect at Layer 4. TCP is connection-oriented and reliable. UDP is connectionless and fast. Port numbers (0 to 65535) live here, and they identify which application gets the data.
Layer 4 failures look like a connection that opens and immediately drops, a TCP retransmit storm, or a firewall blocking port 443. When you see "the server is up, the network is up, but the app will not connect," check Layer 4 next.
Layers 5, 6, and 7: Session, Presentation, Application
The top three layers in real-world TCP/IP get bundled together as "the application." For Network Plus though, you have to keep them straight.
- Layer 5 Session. Opens, manages, and closes conversations between applications. Examples: NetBIOS, RPC, the SIP session in a VoIP call. Failure looks like a call that drops mid-conversation or a remote desktop session that disconnects.
- Layer 6 Presentation. Translates, encrypts, compresses. Examples: TLS encryption, character encoding (ASCII vs UTF-8), image and video codecs. Failure looks like a TLS handshake error, a certificate mismatch, or garbled characters.
- Layer 7 Application. The actual protocols users interact with. HTTP, HTTPS, DNS, SMTP, FTP, SSH. Failure looks like "the website returns 500" or "DNS resolves but the page will not load."
How a real packet flows when you load a webpage
Walk through what happens when you type gmail.com into a browser. This is the question CompTIA loves to ask in three different ways.
- Browser builds an HTTPS request (Layer 7). Asks DNS for the IP of gmail.com (also Layer 7, using UDP at Layer 4).
- TLS handshake encrypts the request (Layer 6). The session between you and the server opens (Layer 5).
- TCP at Layer 4 chunks the request into segments, numbers them, and waits for acknowledgements.
- IP at Layer 3 wraps each segment in a packet with source and destination IP.
- Ethernet at Layer 2 wraps each packet in a frame with source and destination MAC for the next hop (your default gateway).
- Layer 1 turns the frame into electrical or optical signals on the wire.
Each router along the path strips the Layer 2 frame, looks at the Layer 3 IP, and rebuilds a new Layer 2 frame for the next hop. The Layer 3 packet survives the whole journey. The Layer 2 frame is rewritten at every hop.
What this looks like in our platform
The Study Mode deck for objective 1.1 has a layer-by-layer card set plus PDU and device matching drills. The Help Desk Simulator has tickets where a user reports "internet is down" and your job is to walk the layers to find whether it is a cable, a gateway, DNS, or a blocked port. The Net+ track page has the full objective map.
The exam-day shortcut
When a question describes a symptom and asks "at which OSI layer would you troubleshoot this," map the symptom to the failure mode. No link light is Layer 1. Wrong VLAN is Layer 2. Cannot reach the gateway is Layer 3. Firewall blocking a port is Layer 4. TLS handshake error is Layer 6. HTTP 500 is Layer 7. Read the symptom, name the failure mode, the layer falls out of it. That is the pattern the exam rewards.
Sources
- CompTIA. CompTIA Network+ certification overview. Exam code N10-009. Domain weights and objective list.
- ISO/IEC 7498-1. Open Systems Interconnection Basic Reference Model. The original seven-layer specification.
- IEEE 802 LAN/MAN Standards Committee. IEEE 802 working groups. Authoritative source for 802.3 Ethernet and 802.11 Wi-Fi specs.
About the authors
IT Service Center Manager and former CTE / IT teacher. Owner of Revtek IT Solutions. Writes everything that ships under his name and reviews every line of Revy-assisted drafting before publish.
LinkedIn ↗Revy helps draft and structure these posts. Every piece is reviewed, edited, and fact-checked by Nick before publish. We disclose this here because it is the right thing to do. See the AI Policy for the full stance.