Introduction to Networking: Understanding the OSI Model (Simple Explanation for CCNA & CCNP)

Understanding the OSI Model




What is Data Encapsulation?

Before you understand the OSI model, you must first understand data encapsulation.

Let’s use a simple example.

Imagine you want to send a wedding invitation letter to your friend in another city. If you just write the letter and drop it into the mailbox without an envelope, address, or stamp — will it reach your friend?

Of course not.

The postal service needs extra information:

  • Sender name

  • Sender address

  • Recipient name

  • Recipient address

  • Postcode

  • Stamp

Without this information, the letter cannot be delivered.

This process of putting a letter inside an envelope with proper details is similar to data encapsulation in networking.


What is Data Encapsulation in Networking?

In computer networks, we cannot send raw data directly.

For example, when you send a Facebook message:

  1. You type the message.

  2. The browser sends it to the Operating System.

  3. The OS sends it to the Network Interface Card (NIC).

  4. The NIC sends it to the network.

At each step, extra information is added to your data. This extra information is called a header.

These headers include:

  • Source address (where it came from)

  • Destination address (where it is going)

  • Protocol type

  • Port numbers

  • Error-checking information

This process of adding extra information to data is called:

Encapsulation = Adding headers to data so it can travel across the network properly.

At the receiving side, the process is reversed. Headers are removed one by one. This is called de-encapsulation.


Why Do We Need the OSI Model?

In the early days of networking, different companies created their own networking systems. These systems did not follow common rules.

As a result:

  • Devices from different vendors could not communicate.

  • Troubleshooting was difficult.

  • There was no standard structure.

To solve this problem, engineers created a standard framework called the OSI Model.


What is the OSI Model?

OSI stands for Open Systems Interconnection.

It is a 7-layer model that explains how data moves from one device to another.

Each layer has a specific job.

The OSI model helps:

  • Standardize networking

  • Ensure devices from different vendors work together

  • Make troubleshooting easier

  • Explain how data is encapsulated step by step


The 7 Layers of the OSI Model

  1. Layer 7 – Application
    Handles user applications like web browsers, email, etc.

  2. Layer 6 – Presentation
    Handles data formatting, encryption, and compression.

  3. Layer 5 – Session
    Manages sessions between devices.

  4. Layer 4 – Transport
    Handles reliable communication (TCP/UDP).
    Data is called a segment here.

  5. Layer 3 – Network
    Handles IP addressing and routing.
    Data is called a packet here.

  6. Layer 2 – Data Link
    Handles MAC addresses and switching.
    Data is called a frame here.

  7. Layer 1 – Physical
    Sends bits over cables or wireless signals.

#OSIModel #CCNA #CCNP #NetworkingBasics #DataEncapsulation #TCPIP #NetworkEngineer #CiscoNetworking #Subnetting #ITStudents

How Encapsulation Works in the OSI Model

When data is sent:

Application Data
↓
Transport Layer adds TCP/UDP header → Segment
↓
Network Layer adds IP header → Packet
↓
Data Link Layer adds MAC header + trailer → Frame
↓
Physical Layer sends bits

At the destination, headers are removed in reverse order.


OSI Model vs TCP/IP Model

Even though we use the TCP/IP model in real networks, many engineers still refer to OSI layers.

For example:

  • “Is this a Layer 2 issue?”

  • “Do you need a Layer 3 port?”

  • “This is a Layer 7 protocol.”

The modern TCP/IP model has 5 layers, but it maps closely to the lower 4 layers of the OSI model.

For CCNA and CCNP students, understanding both models is very important.


Important Note for CCNA & CCNP Students

The CCNA exam does not deeply test the OSI model anymore. However, networking professionals still use OSI layer terminology daily.

If you want to:

  • Troubleshoot networks

  • Work as a network engineer

  • Pass CCNA or CCNP

  • Understand packet flow

You must clearly understand the OSI model.


#OSIModel
#CCNA
#CCNP
#NetworkingBasics
#DataEncapsulation
#TCPIP
#NetworkEngineer
#CiscoNetworking
#Subnetting
#ITStudents




Understanding VTP Versions, Revision Numbers, and VTP Pruning in Cisco Networks

 Understanding VTP Versions, Revision Numbers, and VTP Pruning in Cisco Networks


VLAN Trunking Protocol (VTP) is a vital tool for simplifying VLAN management in large Layer 2 networks. But not all VTP versions are created equal. Understanding the evolution from VTP v1 to VTP v3, along with the role of the VTP Revision Number and VTP Pruning, is essential for every network engineer.



🔁 VTP Version Comparison

➡ VTP Version 1

  • Default on older Cisco switches

  • Supports VLANs 1–1005

  • Transparent mode relays only matching domain/version messages

  • Drops unknown TLVs

➡ VTP Version 2

  • Default on newer switches

  • Adds support for extended VLANs (1006–4094) in transparent mode

  • Forwards unknown TLVs

  • Relays VTP messages regardless of domain/version in transparent mode

  • Skips consistency checks if MD5 digest is valid

➡ VTP Version 3

  • Major upgrade with extended VLAN support in advertisements

  • Supports Private VLANs and MST (Multiple Spanning Tree)

  • Introduces Primary/Secondary server roles to prevent rogue overwrites

  • Allows complete VTP disablement

  • Improved authentication with hidden/secret passwords


🔄 VTP Revision Number

Each VLAN change increases the revision number. All switches in a VTP domain should maintain the same number. The higher revision number always wins, which can lead to accidental overwrites if a rogue switch with a high revision joins the network.

➡ Tip: Reset the revision number by setting the switch to transparent mode and back to client/server.


🚫 VTP Pruning

Without pruning, every VLAN floods BUM (Broadcast, Unknown unicast, Multicast) traffic through all trunk links—even to switches with no hosts in that VLAN.

VTP Pruning solves this by:

  • Automatically removing VLANs from trunk links that don’t need them

  • Reducing unnecessary traffic

  • Optimizing bandwidth usage

Only needs to be enabled on one VTP Server, and it takes effect across the domain.


🧠 Final Thoughts

Proper understanding of VTP versions, pruning, and revision control is critical for secure, scalable, and efficient network management. VTP is powerful, but misconfigurations can disrupt entire VLAN topologies.


#VTP #CiscoNetworking #VLANTrunking #VTPv3 #NetworkOptimization #Layer2Switching #CCNAStudy #CiscoVLANs #VTPPruning #VTPRevision #NetworkSecurity #CCNP

Featured Post

Day 41 — BGP Confederations: Sub-AS Design, External View and Migration

1. Opening Confederations are another way to scale BGP inside a large administrative domain. They divide the domain into member autonomous systems while presenting a single confederation identifier to external peers. They are powerful, but their operational model is more complex than simply 'using private ASNs inside.' The engineering goal is not to memorize another BGP command. It is to understand what information each speaker is allowed to propagate, what path information can be hidden, and what failure domain is created by the chosen control-plane architecture . 2. Concept and standards behavior RFC 5065 defines AS_CONFED_SEQUENCE and AS_CONFED_SET and how member-AS relationships are represented. Confederation external sessions have eBGP-like properties inside the confederation, while the confederation is presented externally as one AS. Modern guidance must also account for the fact that RFC 9774 prohibits new origination of AS_SET/AS_CONFED_SET in ordinary aggregation c...