Skip to main content

New Series: A-Z Protocols

Image created by ChatGPT

So far, I have finished two certifications: A+ and Network+. Do you want to know some of my favorite parts from studying for both exams? Protocols. 

If you look at the exam objectives for any CompTIA exam, you will notice that there are many port numbers, protocols, and plenty (nailed the alliteration) of abbreviations and acronyms you could be tested on. It can feel like a whirlwind to remember each one. If that's not enough, some acronyms are spelled the same but have entirely new meanings. I mean think about when you hear STP, what do you think of first?

Spanning Tree Protocol

Spanning Tree Protocol

Shielded Twisted Pair

Shielded Twisted Pair


I am starting a new series: an A-Z of Protocols, Ports, and Acronyms. I will go down the alphabet list discussing some of the most popular, useful, and historical terms used in the IT field. There will be:
  •  Definitions
  •  Examples
  •  Demos
  •  Troubleshooting Tips

This is my first time doing something like this and I'm excited to learn about ones I've never really heard of yet that keep (or have kept) our networks alive, past, present, and future. Whether you are preparing for a certification, troubleshooting in a home lab, or reminiscing on previous work on legacy systems, I hope you can join me along on this ride and learn together.

Is there a protocol that you would like to see explained? Feel free to drop the name in the comments!


Comments

Popular posts from this blog

How to Set Up a Cisco Router as a DHCP Server (Step-by-Step Guide)

Lab time! Want to build a DHCP server?  In this lab, I will show you how to build your own DHCP server on a router using Cisco Packet Tracer, as shown above. By the end of this post, you will be able to create your own DHCP server with a Cisco 2911 router, perhaps in a home lab setting, and prepare you to build your own on other hardware.  Why a Router?  A DHCP server is a centralized, automated service that assigns important network configuration details to devices on a network, such as IP addresses. Without it, we would have to create manual entries for our entire network, which can be time-consuming and lead to errors. Traditionally, there are dedicated servers to handle these functions. There are many ways to implement a DHCP server in your topology, including a dedicated physical server, a virtual machine, cloud-based gateways, and firewalls. However, there are specific benefits to using a router as your DHCP server: Reduced infrastructur...

Understanding OSI and TCP/IP Models

Visual breakdown of the OSI Model's 7 layers Whether you are new to IT or a seasoned admin, chances are you have heard of the OSI or the TCP/IP model. These frameworks help us understand how data flows across our networks — from online shopping to high-speed data transfers. However, many job postings require knowledge of TCP/IP but not OSI. Why is that? Is one favored over the other? Let's take a look at both. What is the OSI Model?  Introduced in the 1980s, the Open System Interconnect — OSI — breaks down network communication into seven layers, each with a specific function. Layer Functions 7. Application User and device interaction for network services (web browsing, email, file transfer) 6. Presentation Formats data for applications, ensures readable and secure data 5. Session Establishes, maintains, and ends connections between devices. For example: Online shop...

New Series: IP in Practice

I have done a few posts on subnetting and the inner workings of DHCP. I wanted to do a post on IPv6 and a hands-on demo on implementing DHCP on actual networking equipment. However, I missed a few parts that I would like to cover that would particularly help in understanding how IP works and why it is needed. Unlike the previous series, this will be a direct approach to a certain protocol: Internet Protocol (IP). I recently started my first series, covering important ports, protocols, and acronyms used in the networking field. However, I realized not only is it difficult to address the ones to mention, but for some letters it's hard to find. The intended structure was to have several per letter not just one. The idea seemed fun and engaging, however, doing over 20 posts alphabetically on acronyms, ports, and protocols lacks order and deviates from the direct approach I want this blog to have. For that reason, I am putting it on hold indefinitely. It was fun at first, but it was not...