Module 3 — The Local Crew

CTRL+STRUM // BUILDER LOG

Module 3 — The Local Crew

Posted on December 19, 2025

Welcome to the venue. The cables are down, power is clean, and the stage is set — now we need the crew that makes sure every piece of gear lands in the right place.

🎛 Module 3 — The Local Crew (Switching, MAC, VLANs)

Networking for Humans • Switching • MAC • VLANs • Network+ V9 aligned
✅ Network+ Focus: This module maps hard to Network Implementation (VLANs, trunks, STP, MTU/jumbo frames) and Troubleshooting (switch tables, VLAN mismatch, loops, interface counters).

On tour, once you’re inside the venue, you don’t “route city-to-city” anymore.

You’re doing local coordination: who goes to which room, which stage box feeds which mixer, which channel belongs to which instrument.

That’s what Layer 2 (Data Link) is: local delivery inside the same network.

📌 Exam Alert: Layer 2 problems feel like: “We’re connected… but we’re not talking.” Think switching, MAC addresses, VLANs, STP, and ARP.

🎭 What Layer 2 Actually Does

  • Delivers frames inside a local network (LAN).
  • Uses MAC addresses to decide “where this goes.”
  • Lets you split one physical switch into multiple logical networks using VLANs.

🪪 MAC Addresses — “Who are you?”

A MAC address is your device’s hardware identifier on the local network — like a backstage wristband with a unique barcode.

Term What it is Tour translation
MAC Address Layer 2 hardware identifier Wristband barcode for local access
Frame Layer 2 “package” Load-in crate with a “deliver-to” label
Switch Forwards frames by MAC Stage manager directing crates to the right room
📌 Exam Alert: MAC addresses are used for local delivery. IP addresses are used for routing between networks.

🔀 Switches — The Stage Manager

Switches learn where devices are by watching traffic and building a table:

  • MAC address table (CAM table) = “I saw this MAC on this port.”
  • Known destination? The switch forwards it to the correct port.
  • Unknown destination? The switch floods it (asks the room).
📌 Exam Alert: Flooding is normal for unknown unicast (until the switch learns). If flooding is constant, think loops, table overflow, or misconfig.

🌪 STP / RSTP — Preventing “Feedback Screech” Loops

Two switches with redundant links is good… until it becomes an endless echo chamber.

That’s what a Layer 2 loop feels like: broadcasts and unknown traffic spin forever and the network melts.

📌 Exam Alert: Spanning Tree Protocol (STP) prevents loops by placing some ports into a blocking state. RSTP is the faster “modern” version you’ll see in real life.
Concept What it means Tour translation
Redundant links Multiple physical paths Two hallways between rooms
Loop Traffic circles forever Mic pointed at the speaker (instant screech)
STP blocking One path is “paused” Security closes a hallway until needed

🏷 VLANs — Splitting the Venue into Rooms

VLANs let you separate traffic logically even if everything is plugged into the same physical switch.

Think: one venue, multiple zones:

VLAN Purpose Tour translation
VLAN 10 Staff / crew devices Backstage staff-only hall
VLAN 20 Guest Wi-Fi General admission floor
VLAN 30 POS / payment systems Merch booth cash box area
📌 Exam Alert: VLANs improve security and performance by reducing who can “hear” what traffic.

🚪 Access Ports vs Trunk Ports

This is one of the most testable VLAN concepts, and it’s not scary:

Port type What it carries Where you use it Tour translation
Access One VLAN End devices (PC, printer, AP) Single-room door
Trunk Multiple VLANs (tagged) Switch-to-switch / switch-to-router Hallway that connects multiple rooms
📌 Exam Alert: Trunks carry VLAN tags (often 802.1Q). Access ports do not. A trunk/access mismatch is a classic “some things work, others don’t” scenario.

📣 ARP — “Who has this IP?”

ARP is how devices map IP → MAC on the local network.

Translation: you know the artist’s name (IP), but you need their wristband barcode (MAC) to hand them the gear.

📌 Exam Alert: ARP is a Layer 2/3 bridge concept: it’s about IP, but it happens on the local LAN.

📏 MTU / Jumbo Frames — When “It Half Works”

Sometimes the network “sort of works”… until you send something big.

That’s where MTU comes in: the maximum frame size a link can carry.

📌 Exam Alert: MTU mismatch can cause weird issues like: some sites load, VPN breaks, large transfers fail, or performance tanks. Jumbo frames are larger-than-standard frames used in some environments.

🧪 Mini Troubleshooting: “Connected… But Not Talking”

When the exam gives you that cursed scenario, run this checklist:

  • Same VLAN?
  • Trunk/access mismatch?
  • Switch needs to relearn the MAC?
  • Loop symptoms? (broadcast storms / flapping) → think STP
  • Interface errors? (CRC/drops) → could be bad cable, duplex mismatch, or port issues
  • Large transfers fail? → think MTU
📌 Exam Alert: If local devices fail but internet works, don’t jump to routing yet. Start at Layer 2.

🛡 Quick L2 Security Tie-In (Just the Stuff They Test)

  • MAC flooding: attacker tries to overflow the switch table so it floods traffic (bad).
  • VLAN hopping: misconfig/trunk issues can let traffic cross VLAN boundaries (also bad).
📌 Exam Alert: If you see “unexpected traffic crossing VLANs,” “tagging,” or “trunk misconfig,” your brain should yell: Layer 2 problem.

🎯 Why This Matters

  • Layer 2 is where “connected but not communicating” lives.
  • VLANs are one of the cleanest, most practical segmentation tools you’ll use.
  • Knowing access vs trunk saves you from hours of pain.
  • STP prevents the network from eating itself alive.
💡 Next stop on the tour: “Finding the Route” — IP addressing, subnets, gateways, and how traffic leaves the venue.
← Back to Tour Map Next Module →

// Last note sent by Ben Tankersley

> Last note sent by Ben Tankersley