1.1Network components and basic concepts

In network support, behind a single complaint like "the web will not open" the real cause could be an unplugged cable (physical), a switch issue (L2), a wrong IP setting (L3), or a name-resolution failure (application)—all very different. The first map for separating these is the layer model. This section nails the correspondence between the TCP/IP model and the OSI reference model, the encapsulation by which data gains a header at each layer on the way down, and the "two kinds of address"—frame vs. packet and MAC address vs. IP address—learned not as rote facts but through the lens of which layer a symptom maps to.

1.1.1Two models and their correspondence

• The OSI reference model is the textbook model that divides communication into seven layers, bottom to top: physical (L1) / data link (L2) / network (L3) / transport (L4) / session (L5) / presentation (L6) / application (L7). Each layer uses only the service below and hands one up, so changing a lower layer does not affect the upper layers (layer independence).
• The TCP/IP model is the four-layer model used in practice: network access (roughly OSI L1+L2) / internet (L3) / transport (L4) / application (L5-L7). The key difference is collapsing OSI's top three layers into one; the actual internet is built on this model.
• The two are not rivals but maps of the same communication at different granularity. On the support floor, people speak in OSI layer numbers ("L3 reachability," "an L2 switch") while the mechanism runs on TCP/IP; keeping that correspondence in mind keeps conversations aligned.

1.1.2Encapsulation, frames, and packets

• Encapsulation is the process by which, on the sending side, each layer adds its own header (L2 also a trailer) and passes it down; the receiving side strips headers layer by layer. Each layer's chunk of data has a different name: data (L7) -> segment (L4) -> packet (L3) -> frame (L2) -> bits (L1).
• A packet is the L3 (IP) chunk carrying source/destination IP addresses and is carried across networks. A frame is the L2 chunk that wraps a packet with source/destination MAC addresses—the unit for delivery to the next device within the same segment. The two differ in how far they are meant to travel.
• The wording of a fault report is a hint: "many frame errors" points to L2/physical, "packets not arriving / cannot reach another network" to L3, "name will not resolve" to the application layer. Telling which layer and unit a symptom belongs to is the first step of support.

Suppose the help desk gets a call: "I can share files with the colleague at my own cluster of desks, but I cannot reach the server on another floor at all." With a layer-model view you can quickly narrow the cause. First, "communication within my own cluster (the same segment) works" strongly suggests that this PC's LAN cable and switch port (physical/L2) and the frame forwarding by MAC address are functioning. The problem is that "only another floor—another network—is unreachable," which is an L3 matter of sending a packet to a different network. Reaching another network needs IP settings (notably the default gateway you will study in a later chapter), so a sound next move is to check this PC's IP address and gateway with ipconfig (Windows). Conversely, if even the same-cluster colleague were unreachable, you would drop the suspicion down to physical/L2. The key point: if you know the division of roles—"within one segment it is a frame = MAC, across networks it is a packet = IP"—you can narrow the culprit layer from the scope of the symptom (how far communication reaches). Not memorizing terms but this habit of translating a symptom into a layer is what sets support speed.

1.1.3Section summary

• The OSI 7 layers and TCP/IP 4 layers are maps of the same communication at different granularity; TCP/IP collapses OSI's top three (L5-L7) into one
• With encapsulation each layer adds a header, and the PDU changes name by layer: data/segment/packet/frame/bits
• A frame uses MAC within one segment; a packet uses IP across networks—narrowing the culprit layer from the symptom's scope is the basic skill