Study guide
1.10 OSI and TCP/IP Reference Models
Cisco Certified Network Associate CCNA
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About the CCNA 200-301 Exam Domains and Weights Study Strategies and Tips
2 Chapter 1: Network Fundamentals (20%)
1.1 Network Components 1.2 Network Topology Architectures 1.3 Physical Interfaces and Cabling 1.4 TCP vs. UDP 1.5 IPv4 Addressing and Subnetting 1.6 IPv6 Addressing and Prefix 1.7 Wireless Principles 1.8 Virtualization Fundamentals 1.9 Switching Concepts 1.10 OSI and TCP/IP Reference Models 1.11 Verifying IP Parameters on Client Operating Systems
3 Chapter 2: Network Access (20%)
2.1 VLANs — Configuration and Verification 2.2 Trunking and 802.1Q 2.3 Layer 2 Discovery Protocols (CDP and LLDP) 2.4 EtherChannel (Link Aggregation) 2.5 Spanning Tree Protocol (STP) and RSTP 2.6 Wireless Architectures and AP Modes 2.7 Network Access Troubleshooting 2.8 Inter-VLAN Routing — Deep Dive
4 Chapter 3: IP Connectivity (25%)
3.1 Routing Table Components 3.2 Router Forwarding Decisions 3.3 IPv4 and IPv6 Static Routing 3.4 Single-Area OSPFv2 — Concepts 3.5 Single-Area OSPFv2 — Configuration 3.6 First Hop Redundancy Protocols (FHRP) 3.7 Troubleshooting IP Connectivity 3.8 OSPF Troubleshooting Scenarios
5 Chapter 4: IP Services (10%)
4.1 NAT (Network Address Translation) 4.2 DHCP and DNS 4.3 NTP, SNMP, and Syslog 4.4 QoS Fundamentals 4.5 TFTP/FTP and Remote Access 4.6 IP Services — Comprehensive Review
6 Chapter 5: Security Fundamentals (15%)
5.1 Key Security Concepts 5.2 Device Access Control and Password Policies 5.3 VPN Fundamentals 5.4 Access Control Lists (ACLs) 5.5 Layer 2 Security Features 5.6 Network Security Best Practices and Hardening 5.7 Threat Mitigation and Incident Response
7 Chapter 6: Automation and Programmability (10%)
6.1 Impact of Automation on Network Management 6.2 Controller-Based and Software-Defined Architectures 6.3 AI and Machine Learning in Network Operations 6.4 REST-Based APIs 6.5 Configuration Management Tools 6.6 JSON-Encoded Data 6.7 Automation and Programmability — Comprehensive Review
1.10 OSI and TCP/IP Reference Models
Key Takeaways Explain This Topic AI
The OSI model has 7 layers: Physical, Data Link, Network, Transport, Session, Presentation, Application (bottom to top).
The TCP/IP model has 4 layers: Network Access, Internet, Transport, Application, mapping to real protocols.
PDUs by layer: Data (L5-7), Segment (L4), Packet (L3), Frame (L2), Bits (L1).
Encapsulation adds a header at each descending layer; de-encapsulation strips them on the way up.
Know which protocol or device lives at which layer, this mapping is heavily tested.
Last updated: June 2026
Why layered models matter
Questions asking which layer a protocol or device operates at appear throughout the CCNA. Layering also lets vendors build interoperable pieces, each layer serves the one above and relies on the one below.
The OSI model (7 layers)
- # Layer PDU Function Examples
- 7 Application Data User-facing network services HTTP, FTP, SMTP, DNS
- 6 Presentation Data Formatting, encryption, compression TLS, JPEG, ASCII
- 5 Session Data Establish/maintain sessions NetBIOS, RPC
- 4 Transport Segment End-to-end delivery, ports TCP, UDP
- 3 Network Packet Logical addressing, routing IP, ICMP, OSPF
- 2 Data Link Frame MAC addressing, framing Ethernet, ARP, switches
- 1 Physical Bits Signals on the medium Cables, hubs, RJ-45
A mnemonic for layers 7 to 1: A ll P eople S eem T o N eed D ata P rocessing.
The TCP/IP model (4 layers)
- TCP/IP layer Maps to OSI Key protocols
- Application OSI 5-7 HTTP, DNS, FTP, SMTP
- Transport OSI 4 TCP, UDP
- Internet OSI 3 IP, ICMP, ARP
- Network Access (Link) OSI 1-2 Ethernet, cabling
The TCP/IP model is what the real Internet runs on, it collapses OSI's top three layers into one Application layer and the bottom two into Network Access.
Encapsulation and PDUs
As data moves down the stack on the sender, each layer wraps it in a header (and the Data Link layer adds a trailer/FCS). This is encapsulation , and the unit's name (PDU) changes at each layer:
Data (L7-5) -> Segment (L4) -> Packet (L3) -> Frame (L2) -> Bits (L1).
On the receiver the process reverses, each layer strips its header in de-encapsulation until the application gets the original data. The Layer 3 header adds source/destination IP ; the Layer 2 header adds source/destination MAC .
Devices by layer
- Device OSI layer
- Router, Layer 3 switch (routing) 3
- Switch, bridge, NIC 2
- Hub, repeater, cable 1
- Firewall (stateful/NGFW) 3-7
- Worked example
A web request descends the stack: the browser data (L7) is handed to TCP which adds a port header making a segment (L4); IP adds source/dest IP making a packet (L3); Ethernet adds source/dest MAC making a frame (L2); the NIC encodes it as bits on the wire (L1). Each router along the path rewrites the L2 frame but keeps the L3 packet's IPs.
Headers added at each layer
Encapsulation is concrete, each layer prepends specific addressing:
- Layer Adds Key fields
- Transport (4) TCP/UDP header Source/destination ports
- Network (3) IP header Source/destination IP , TTL
- Data Link (2) Frame header + trailer Source/destination MAC , FCS
- Physical (1) none (encoding) Bits as signals
The Layer 2 frame is the only PDU with both a header and a trailer (the FCS , frame check sequence, used for error detection). At each router hop the Layer 2 frame is rebuilt with new MAC addresses while the Layer 3 packet's IPs stay constant, this header rewrite is why "same packet, new frame" is a recurring exam idea.
Mapping protocols to layers (memorize)
Layer 7 Application : HTTP, HTTPS, FTP, SMTP, DNS, DHCP, SNMP, Telnet, SSH.
Layer 4 Transport : TCP, UDP.
Layer 3 Network : IP, ICMP, OSPF, EIGRP (routing protocols ride here logically).
Layer 2 Data Link : Ethernet, ARP, STP, VLAN tagging.
Layer 1 Physical : cables, connectors, hubs, repeaters, RF.
Note ARP spans the boundary, it resolves a Layer 3 IP to a Layer 2 MAC, and the exam usually places it at Layer 2.
Why two models exist
The OSI model is a teaching and troubleshooting reference, its seven layers let you isolate a fault ("is this a Layer 1 cabling issue or a Layer 3 routing issue?"). The TCP/IP model is the practical stack the Internet actually implements. Cisco troubleshooting almost always reasons bottom-up : confirm Physical, then Data Link, then Network, then Transport, then Application, the same order this chapter's client-troubleshooting section follows.
Common traps
A router operates at Layer 3 , not Layer 2, even though it has Ethernet ports.
The segment is the Transport-layer (L4) PDU; the packet is Layer 3, do not mix them.
DNS is an Application-layer (L7) protocol even though it rides on UDP/TCP at L4.
Encapsulation goes down (Data to Bits); the receiver de-encapsulates up .
Only the Layer 2 frame has a trailer (the FCS); other PDUs add only a header.
Layer-by-layer responsibilities
Knowing what each layer is responsible for lets you answer "which layer handles X" questions instantly:
Physical (1) : bit transmission, voltage/light levels, connectors, cabling.
Data Link (2) : framing, MAC addressing, error detection via FCS, media access.
Network (3) : logical IP addressing, path selection, routing between networks.
Transport (4) : segmentation, reliability (TCP), port-based multiplexing.
Session (5) : opening, managing, and closing dialogs between applications.
Presentation (6) : data format translation, encryption, compression.
Application (7) : the interface user applications use to reach the network.
Troubleshooting with the model
The layered model is a diagnostic tool, not just trivia. If a user cannot reach a website, you test bottom-up : is the link up (L1)? Does the switch see the MAC (L2)? Does the host have a valid IP and gateway (L3)? Does a connection establish (L4)? Does the name resolve and the app respond (L7)? Each layer you confirm narrows the fault. This disciplined layer-by-layer isolation is exactly how Cisco frames troubleshooting questions and why the OSI model anchors the entire certification, every later topic, from VLANs to routing to ACLs, maps cleanly onto a specific layer.