Network+ lab 5 of 27
VLANs and trunking between switches
Split an office into department VLANs across two switches. You build the VLAN database, assign data and voice VLANs to access ports, join the switches with an 802.1Q trunk on an unused native VLAN, and manage both switches through a management SVI.
Run this lab
It needs Lite: its 6 nodes are set to 6 vCPU and 5,632 MB in total. That fits the free demo too.
In your workspace: Shared, then CompTIA Network Plus N10-009 guided labs, then 05 - VLANs and trunking between switches
- Level
- Beginner
- Time
- About 50 minutes
- Nodes need
- 6 vCPU, 5,632 MB
- Smallest plan
- Lite
The scenario
Harbour Logistics' head-office floor has Sales and Accounts staff on both sides of the building, each side with its own switch. Today everyone shares one flat network, so Accounts' traffic (payroll) reaches every Sales PC and a broadcast storm on one side hits the other. You'll split the floor into VLANs, carry them between the switches on a trunk, and give each switch a management address.
| VLAN | Name | Subnet | Members |
|---|---|---|---|
| 10 | SALES | 10.10.10.0/24 | PC1 (SW1 Gi0/1), PC3 (SW2 Gi0/1) |
| 20 | ACCOUNTS | 10.10.20.0/24 | PC2 (SW1 Gi0/2), PC4 (SW2 Gi0/2) |
| 30 | VOICE | (phones) | voice VLAN on the Sales desk ports |
| 99 | MGMT | 10.99.99.0/24 | SW1 10.99.99.11, SW2 10.99.99.12 |
| 999 | NATIVE-UNUSED | none | trunk native VLAN only |
The PCs already have their addresses. There's no router yet (lab 06 adds one), so only hosts in the same VLAN can talk.
What you’ll practise
- Create VLANs and name them in the VLAN database
- Configure access ports with data and voice VLANs
- Configure an 802.1Q trunk with a restricted allowed list and an unused native VLAN, with DTP off
- Configure a management SVI and test it across the trunk
- Show that VLANs are separate broadcast domains and recognise a native VLAN mismatch
The tasks
- Build the VLAN database
- Configure the access ports, data and voice
- Build the trunk between the switches
- Add the management SVI
- Prove the VLANs are separate
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
- SW1
Gi0/0to SW2Gi0/0 - SW1
Gi0/1to PC1eth0 - SW1
Gi0/2to PC2eth0 - SW2
Gi0/1to PC3eth0 - SW2
Gi0/2to PC4eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| SW1 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 768 MB |
| SW2 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 768 MB |
| PC1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PC2 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PC3 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PC4 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
CompTIA Network Plus N10-009 guided labs.Open
05 - VLANs and trunking between switchesand 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 Network+ labs
Related labs in other courses
CloudLabBox is independent of CompTIA, Cisco and Netgate. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.