The OSI and TCP/IP models describe how network communication is divided into layers. Each layer performs a different part of the communication process, from transmitting electrical or wireless signals to displaying information inside an application.

CompTIA A+ technicians do not normally need to analyze every protocol at the same depth as a network engineer. However, understanding the layers provides a useful method for locating connectivity problems.

For example, a damaged Ethernet cable is a different type of problem from an incorrect IP address. An incorrect IP address is also different from a web browser that cannot connect to one specific website. The networking models help technicians place each problem into a general category and decide what to check next.

Why Networking Models Are Used

Network communication involves many separate technologies working together. A user may open a browser, enter a website address, connect through Wi-Fi, send packets through a router, and receive data from a server located hundreds of miles away.

Without an organized model, troubleshooting this process could become confusing.

Networking models divide communication into layers so each function can be examined separately. A technician can begin at the lowest layer and work upward, or begin with the application and work downward.

The models help answer questions such as:

• Is the device physically connected?

• Can the device communicate on the local network?

• Does it have a valid IP address?

• Can it reach a remote network?

• Is the correct network service available?

• Is the application configured correctly?

The models do not replace troubleshooting tools or technical knowledge. Instead, they provide a structured way to think about a problem.

The OSI Model

The Open Systems Interconnection model, commonly called the OSI model, contains seven layers.

From the highest layer to the lowest, the layers are:

1. Application

2. Presentation

3. Session

4. Transport

5. Network

6. Data Link

7. Physical

The OSI model is mainly a conceptual model. It helps technicians, administrators, and engineers describe where network functions occur.

A technician may hear phrases such as “Layer 1 problem,” “Layer 2 connection,” or “Layer 3 addressing.” These descriptions refer to the OSI model.

The TCP/IP Model

The TCP/IP model describes the protocol suite used by modern IP networks and the internet.

It is commonly shown with four layers:

1. Application

2. Transport

3. Internet

4. Network Access

Some sources divide the Network Access layer into separate Data Link and Physical layers, creating a five-layer version. Both versions describe the same general process.

The TCP/IP model is more closely connected to the protocols used on real networks. The OSI model provides more individual layers for discussing and troubleshooting those functions.

Comparing the Models

The OSI and TCP/IP models organize similar networking functions differently.

For A+ troubleshooting, the exact differences between the models are less important than understanding what happens at each functional level.

A Practical Troubleshooting Approach

A technician can use the models to move through a network problem logically.

A bottom-up approach begins with the physical connection and moves toward the application:

1. Check power, cables, Wi-Fi, and link lights.

2. Check the network adapter and local network connection.

3. Check IP addressing, the default gateway, and routing.

4. Check ports, protocols, and service availability.

5. Check the application and user configuration.

A top-down approach begins with the application:

1. Confirm the application is configured correctly.

2. Test whether the required service is available.

3. Test IP connectivity.

4. Check the local network connection.

5. Inspect the physical connection.

The best approach depends on the symptoms. If a user reports that the Ethernet cable was recently moved, beginning at the Physical layer makes sense. If every website works except one web application, beginning at the Application layer may be faster.

Layer 1: Physical

The Physical layer concerns the actual transmission of bits across a connection.

This layer includes:

• Ethernet cables

• Fiber-optic cables

• Connectors

• Network ports

• Patch panels

• Wireless radio signals

• Antennas

• Network interface hardware

• Electrical and light signals

• Link lights

At this layer, information is transmitted as electrical signals, pulses of light, or radio waves.

Common Physical-Layer Problems

Physical-layer problems are among the most common issues handled by A+ technicians.

Examples include:

• An unplugged Ethernet cable

• A damaged cable

• A broken connector

• A disabled wireless radio

• A device outside Wi-Fi range

• A powered-off switch or access point

• A damaged switch port

• A loose wall-jack connection

• Radio-frequency interference

• A failing network interface card

A physical problem can prevent all higher-layer communication. The device cannot exchange frames, receive an IP address, or access an application if the connection itself does not function.

Physical-Layer Troubleshooting

A technician should inspect the simplest possibilities first.

Verify that the cable is securely connected at both ends. Look for damaged clips, bent connectors, crushed cables, or exposed wiring. Check the link lights on the network interface and switch.

When troubleshooting Wi-Fi, confirm that wireless networking is enabled and airplane mode is disabled. Move the device closer to the access point and check the signal strength.

Useful tools may include:

• Cable tester

• Toner probe

• Loopback plug

• Wi-Fi analyzer

• Known-good Ethernet cable

Replacing a suspected cable with a known-good cable is often one of the fastest physical-layer tests.

Physical-Layer Scenario

A desktop computer displays “Network cable unplugged.”

The technician checks the IP configuration, but the device has no active Ethernet connection. The link light is also off.

The technician replaces the Ethernet cable, and the link light turns on.

This was a Physical-layer problem. IP settings were not the first issue because the device could not establish a basic connection.

Layer 2: Data Link

The Data Link layer handles communication across the local network.

At this layer, data is organized into frames. Ethernet and Wi-Fi both operate at this level.

Important Data Link concepts include:

• MAC addresses

• Ethernet frames

• Wireless frames

• Network switches

• Wireless access points

• Virtual LANs

• Error detection

• Local network delivery

A Media Access Control address identifies a network interface on the local network. Switches examine destination MAC addresses and forward frames toward the correct device.

Common Data-Link Problems

Examples of Data Link-layer problems include:

• A disabled network adapter

• A failing network interface card

• A switch port placed in the wrong VLAN

• A switch port that repeatedly goes up and down

• MAC address conflicts or filtering

• Incorrect wireless security settings

• Failure to associate with an access point

• Driver problems affecting the network adapter

A device may have a working cable but still fail to communicate because the network adapter, switch, or wireless connection is not functioning correctly.

Data-Link Troubleshooting

The technician should verify that the operating system recognizes the network adapter and that the adapter is enabled.

Check Device Manager for errors, warning symbols, or missing drivers. Verify that the Ethernet adapter shows a connected status or that the wireless device is associated with the correct SSID.

On a managed network, a network administrator may need to verify the switch-port configuration or VLAN assignment.

Useful indicators include:

• Network adapter status

• MAC address

• Switch-port status

• Wireless association

• Connection speed

• Device Manager messages

• Access-point logs

Data-Link Scenario

A computer has a working Ethernet cable and an active link light, but it cannot access the employee network. Other computers connected to the same switch work normally.

The switch port was recently configured for the guest VLAN instead of the employee VLAN.

The physical connection was working, but the local network configuration was incorrect. This is primarily a Data Link-layer issue.

Layer 3: Network

The Network layer handles logical addressing and communication between different networks.

The TCP/IP model calls this the Internet layer.

Important Network-layer concepts include:

• IPv4 addresses

• IPv6 addresses

• Subnet masks

• Default gateways

• Routers

• Routing

• Internet Control Message Protocol

• Packet forwarding

At this layer, data is organized into packets.