Start here: the Foundations path and the VLAN big picture
Picture a large office building with one shared corridor. Every time someone shouts a question in the corridor, every person on every floor hears it, stops working and checks whether the question is for them. Now give each department its own floor with its own corridor. Shouting on the fourth floor only disturbs the fourth floor, and visitors need to pass reception (a router) to move between floors. A VLAN (virtual LAN) is that private floor, built inside a switch with configuration instead of concrete.
What you will learn in this module
- How an Ethernet switch learns MAC addresses, floods unknown frames and forms a broadcast domain.
- How to create VLANs on Arista EOS, name them and place access ports into them.
- How 802.1Q trunks carry many VLANs between switches, and how the allowed VLAN list and native VLAN work.
- How to verify VLANs with
show vlan,show interfaces trunkandshow mac address-table. - A repeatable troubleshooting workflow for "one VLAN works, another does not" tickets.
Prerequisites
You should be comfortable with IPv4 addresses and subnet masks, know what a MAC address is, and be able to log in to a network device CLI. If subnetting is new to you, finish the CCNA addressing modules first. No previous Arista experience is needed: every EOS command is explained the first time it appears.
Where this course fits
This track prepares you for the Arista Network Foundations Associate level. Arista Academy's exam datasheet (version 3.0, reviewed 10 October 2026) describes a two-hour, hands-on, proctored, lab-based exam. It is open-book but timed, so there is no time to research fundamentals during the exam. The published topics are VLANs, spanning tree, MLAG with trunk groups and port-channels, VARP and SVIs, static routing, OSPF in one or several areas, ACL types, basic IPv6, hardening of the control plane and management interfaces with auditable logging, and verification with show commands. Each topic has its own module in this track, and the last module is a leaf-spine capstone that joins them all.
Independent preparation. This course is original material mapped to the published topics. It is not an Arista course, an Arista question bank or a credential, and finishing it does not guarantee a pass. Always read the current official datasheet before you book.
The nine modules of the Network Foundations track. VLANs come first because MLAG, VARP and the capstone all depend on them.
Three evidence levels
Treat your preparation like learning to drive. Explain means you can say why a feature exists and predict what a change will do. Simulate means you can build and repair the feature in the CONFIG simulator without copying the solution. Validate on EOS means you repeat the task on a real or virtual EOS switch that you are allowed to use and keep the output you saw. The simulator models EOS behaviour closely enough to rehearse, but a green tick is a rehearsal, never a replacement for the real platform.
The VLAN big picture
A switch without VLANs is one big broadcast domain: an ARP request from any host reaches every port. That is fine for ten hosts and painful for a thousand. VLANs split the switch into separate broadcast domains. Hosts in VLAN 10 never see broadcasts from VLAN 20, and they cannot talk to VLAN 20 at all unless a router or a Layer 3 switch interface (an SVI, covered in the VARP module) moves the traffic between them.
In this module you will work with two leaves, L1 and L2. WEB1 and APP1 hang off L1 on Ethernet5 and Ethernet6; WEB2 and APP2 hang off L2 on the same ports. VLAN 10 (named WEB) uses 10.10.10.0/24 and VLAN 20 (named APP) uses 10.10.20.0/24. Ethernet1 links the two leaves and becomes a trunk.
Worked example. WEB1 is 10.10.10.11/24 on L1 Ethernet5 and WEB2 is 10.10.10.12/24 on L2 Ethernet5. For WEB1 to ping WEB2: both ports must be access ports in VLAN 10, VLAN 10 must exist on both leaves, and the Ethernet1 trunk must allow VLAN 10 on both sides. Remove any one of those four facts and the ping fails, even though the cable is perfectly fine.
How to use each chapter
Read the concept, type the configuration yourself, then compare your verification output with the sample. At the end of each module write down three things: the command that proved the feature, the line in the output that proved it, and one mistake you made. That log becomes your personal revision sheet for the practical exam.
Common mistake. Racing through simulator labs by copying hints. In a practical exam nobody hands you the starting point; you must read the current state first. Practise reading show output before every change.
Exam trap. Hosts in the same IP subnet but different VLANs cannot communicate at Layer 2. The VLAN decides the broadcast domain, not the IP address.
Green ticks, red face
Priya finished every simulator lab in a weekend and booked her practical. On the real switch she could not remember whether switchport trunk allowed vlan adds to the list or replaces it, because the simulator always gave her a working starting point. She lost twenty minutes testing it on a live trunk.
Lesson: Learn the behaviour, not the keystrokes, and rehearse on real EOS too.
"How are you preparing for a networking certification?"
A strong answer separates understanding, building and proving. Say that you explain each feature in your own words, build it from a topology and addressing table without notes, verify it with show commands, and keep a log of the output lines that proved it. Mention that you redo any lab where you needed a hint.
Key takeaways
- A VLAN is a separate broadcast domain inside a switch.
- Hosts in different VLANs need a Layer 3 device to communicate.
- The track follows the published Network Foundations topics; this module is the base for all others.
- Use Explain, Simulate and Validate on EOS as separate milestones.
- Always verify with show commands before you claim a feature works.