Ref: https://learn.cantrill.io/courses/2022818/lectures/45662102

YouTube: https://www.youtube.com/watch?v=otG3cDbqi2E

• Summary:
• Contents:

Physical LAN scaling problems

• 🔧 Physical Local Area Network (LAN) = devices connected to a L2 Switch
  • Separate collision domains (one for each “device↔switch port” connection)
    • Better performance than LAN with just a L1 Hub
  • Shared broadcast domain → All-Fs frames received by all devices
• ❗ Poor scaling
  • Add more devices → more broadcasts
  • Devices could belong to different logical groups (testers, sale, finance…), but have same physical LAN and same broadcast domain → not ideal

• Scaling problems worse if LANs extend over different locations (floors, buildings…)
  • e.g. different buildings for logical group (testing, finance, sales…)
  • L2 Switches can connect for cross-location communication, but broadcast domain gets much bigger (Switch 1 domain + Switch 2 domain)
  • Staff member changes role (e.g. testing to sales) but not location → needs physical cable between locations → gets messy

Virtual Local Area Network (VLAN) - 802.1Q Standard

• 🔧 Virtual Local Area Network (VLAN) = logical L2 network
  • Can divide a physical LAN into several virtual LANs (VLANs)…
  • …using 802.1Q standard (colloquially .1Q - “dot one Q”)
    • 💡 Used in e.g. AWS Direct Connect → DX private & public VIFs use 802.1Q VLANs

• 802.1Q adds extra field (32b) to MAC Header in frames
  • Out of 32b, 12 of those bits store VID (VLAN ID)
  • Different VLANs have different VIDs → multiple VLANs can operate on same LAN
    • ❗ Each VLAN is isolated from each other VLAN → separate broadcast domain!
• VID is 12b → 4000+ VLANs possible

802.1Q Switches and Trunk Ports

• 🔧 802.1Q Switch = L2 Switch with .1Q capability
  • ❗ Sets ports to Access port (single VID) or Trunk port (all VIDs)
    • Access ports communicate with devices using standard Ethernet (no VLAN tags)
    • Trunk port = connection between two .1Q switches → carries all VIDs