The OSI Model for CompTIA Network+: Layers, Devices, and Troubleshooting

Where the OSI model shows up on CompTIA Network+ N10-009

The OSI reference model is objective 1.1 of CompTIA Network+ N10-009, inside Networking Concepts (23% of the exam). The objective lists the seven layers by number and name, from Layer 1, Physical, to Layer 7, Application. The model then comes back in two other places:

• Objective 1.2 asks you to compare appliances, applications, and functions, such as routers, switches, firewalls, IDS and IPS, load balancers, proxies, access points and controllers, QoS, and TTL. Knowing the layer each one works at is the fastest way to tell them apart.
• Objective 5.1, the troubleshooting methodology, names top-to-bottom and bottom-to-top OSI approaches, plus divide and conquer, as ways to form a theory of probable cause.

So the exam rarely asks you to recite the layers. It asks you to use them: to place a device, read a symptom, or pick where to start checking. The troubleshooting methodology guide covers the seven steps that the OSI approaches plug into.

The seven OSI layers with PDUs, devices, and one symptom each

Learn each layer as a job, not a name. The unit of data at each layer is its protocol data unit (PDU). RFC 1122, the IETF's host requirements, defines a frame as the link-layer unit, a packet or IP datagram as the internet-layer unit, and a segment as the unit TCP sends. "Bits" for Layer 1 and "data" for the upper layers are the usual study labels.

Three 1.2 functions are worth placing precisely, because stems use them as clues:

• TTL is a field in the IP header. Each router lowers it before forwarding, as Microsoft's tracert documentation explains, so TTL is a Layer 3 idea.
• QoS can be marked at more than one layer. Cisco's voice VLAN guide, for example, describes Layer 2 class-of-service values and a Layer 3 IP precedence value on the same voice traffic.
• VPN depends on the technology. An IPsec tunnel works at Layer 3, while VPNs built on TLS sit higher. Read the stem for which one it means.

Port numbers belong to Layer 4, which is why the ports and protocols guide pairs each N10-009 service with TCP or UDP. Layer 2 work (VLANs, trunks, spanning tree) is in the switching guide.

Where the OSI model is a teaching model, not a rule

The OSI model gives everyone the same words. It is not a map that every protocol follows exactly, and three facts from public standards show the limits:

• The internet uses fewer layers. RFC 1122 describes the Internet protocol suite in four layers: application, transport, internet, and link. It says the Internet's application layer combines the functions of the OSI presentation and application layers.
• Many devices work across layers. RFC 3234, the IETF catalogue of middleboxes, describes a basic IP firewall as one that filters on IP and transport header fields, while an application firewall acts as an end point for a protocol such as SMTP or HTTP. It classes load balancers that redirect packets as multi-layer.
• Encryption has no single home. Study materials often place encryption and data formatting at Layer 6 in OSI terms, while the TCP/IP model folds that work into its application layer. TLS, for example, is described at different layers by different sources.

On the exam, answer in the model the stem names. If it says "OSI layer", use the seven-layer table above. If a device clearly works at two layers, such as a Layer 3 switch, pick the layer that matches the function the question describes.

Bottom-up vs top-down on one outage

Here is one original outage, worked both ways. At a small office, one PC cannot open the scheduling web app at app.example.com. Email, file shares, and other websites work on the same PC. Other PCs can open the app.

Bottom-up, starting at Layer 1:

1. Layer 1: the link light is on and the PC has traffic. Pass.
2. Layer 2: the switch port is in the staff VLAN, like the other PCs. Pass.
3. Layer 3: the PC has a correct address, mask, and gateway, and it can ping the app server's IP address. Pass.
4. Layer 4: a test connection to TCP 443 on the app server fails from this PC only. Found it.

Top-down, starting at Layer 7:

1. Layer 7: the browser cannot connect. The name resolves to the same address other PCs get, so DNS is not the problem.
2. Layer 4: a test connection to TCP 443 fails from this PC only. Found it. A host firewall rule added during a recent software install is blocking the connection.

Both approaches reach the same cause, but bottom-up spent three steps proving layers that the symptom had already cleared. Email and other websites were working, so Layers 1 to 3 were almost certainly fine. That gives a simple rule for choosing:

After a check like this, the command-line tools guide shows which tool answers each layer's question. The free mixed set has no item that asks you to name a layer, but its troubleshooting scenarios use this same order of checks, so you can work through the mixed set's Network+ troubleshooting scenarios → once the table makes sense.

Building an OSI memory hook you will keep

Borrowed phrases are easy to forget because they mean nothing to you. A sturdier method has two parts.

First, turn each layer into the question it answers:

1. Physical: is there a signal?
2. Data link: which MAC address on this link, and which VLAN?
3. Network: which network, and which route?
4. Transport: which port, and is delivery reliable?
5. Session: is the conversation still open?
6. Presentation: can both ends read the format?
7. Application: does the application protocol answer?

Second, build your own sentence from the first letters, P D N T S P A from the bottom, using words from your own work. One example from a network technician's day: "Port Down? Note The Switch Port Assignment." Read top-down, A P S T N D P, another could be "Always Ping Servers Then Network Devices Patiently." A sentence you wrote yourself is easier to recall under time pressure than one you memorized.

A quick OSI layer drill

Cover the right column and name the layer for each symptom.

If you missed one, go back to the "symptom that points here" column in the layer table, and say the layer's question out loud for the case you missed.