Arista EOS lab 2 of 20
VLANs and trunks with SVIs and LLDP
Segment Northwind's operations floor into VLANs, carry them over an 802.1Q trunk with a deliberate native VLAN, and route between them with switched virtual interfaces on the core switch.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 5,632 MB in total. That fits the free demo too.
In your workspace: Shared, then Arista EOS guided labs, then 02 - VLANs and trunks with SVIs and LLDP
- Level
- Beginner
- Time
- About 55 minutes
- Nodes need
- 5 vCPU, 5,632 MB
- Smallest plan
- Lite
The scenario
Northwind Data's operations floor is one flat network: staff PCs, printers and the build server all share VLAN 1, and a broadcast storm last week took everything down. You will split the floor into VLANs, trunk them from the access switch acc1 to the core switch core1, and make core1 the default gateway for every VLAN.
| Device | Interface | VLAN / mode | Address | Connects to |
|---|---|---|---|---|
| core1 | Ethernet1 | trunk, native 99 | – | acc1 Ethernet1 |
| core1 | Ethernet2 | access 30 | – | srv30 |
| core1 | Vlan10 / Vlan20 / Vlan30 / Vlan99 | SVI | 10.10.10.1 / 10.10.20.1 / 10.10.30.1 / 10.0.99.1 (/24) | – |
| acc1 | Ethernet1 | trunk, native 99 | – | core1 Ethernet1 |
| acc1 | Ethernet2 | access 10 | – | h10 |
| acc1 | Ethernet3 | access 20 | – | h20 |
| acc1 | Vlan99 | SVI | 10.0.99.2/24, gateway 10.0.99.1 | – |
| h10 | eth0 | – | 10.10.10.11/24, gateway 10.10.10.1 | acc1 Ethernet2 |
| h20 | eth0 | – | 10.10.20.11/24, gateway 10.10.20.1 | acc1 Ethernet3 |
| srv30 | eth0 | – | 10.10.30.100/24, gateway 10.10.30.1 | core1 Ethernet2 |
VLAN names: 10 USERS, 20 PRINTERS, 30 SERVERS, 99 MGMT.
What you’ll practise
- Document a topology from LLDP before changing it
- Create named VLANs and assign access ports
- Build an 802.1Q trunk with a native VLAN and an allowed-VLAN list
- Enable IP routing and create SVIs as default gateways
- Give a layer 2 switch a management SVI and default route
- Read the MAC address table, trunk and switchport status
The tasks
- Document what is there
- Create the VLANs
- Assign the access ports
- Build the trunk
- Address the hosts and test inside each VLAN
- Route between the VLANs on core1
- Manage the access switch in VLAN 99
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- core1
Ethernet1to acc1Ethernet1 - core1
Ethernet2to srv30eth0 - acc1
Ethernet2to h10eth0 - acc1
Ethernet3to h20eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| core1 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| acc1 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| srv30 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| h10 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| h20 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Arista EOS guided labs.Open
02 - VLANs and trunks with SVIs and LLDPand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More Arista EOS labs
Related labs in other courses
CloudLabBox is independent of Arista Networks. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.