CCNA lab 9 of 46
802.1Q trunks: native VLAN and DTP
Three switches in a row, one link that never became a trunk and another that negotiated itself into a native VLAN mismatch. Replace guesswork with static 802.1Q trunks, an unused native VLAN and a pruned allowed list.
Run this lab
It needs Lite: its 6 nodes are set to 6 vCPU and 6,144 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNA 200-301 guided labs, then 09 - 802-1Q trunks - native VLAN and DTP
- Level
- Intermediate
- Time
- About 50 minutes
- Nodes need
- 6 vCPU, 6,144 MB
- Smallest plan
- Lite
The scenario
Millbrook Engineering has three switches in a row along a corridor. The VLANs and the PC ports were set up last week, but the inter-switch links were left to "sort themselves out". Sales (VLAN 10) on S1 can't reach their colleague on S3, and S2 and S3 keep logging native VLAN complaints. Your job: make every inter-switch link a deliberate, documented 802.1Q trunk.
| Device | Port | Role | Address |
|---|---|---|---|
| S1 | Gi0/0 | link to S2 Gi0/0 | SVI 99: 10.9.99.1/24 |
| S2 | Gi0/0, Gi0/1 | links to S1 and S3 | SVI 99: 10.9.99.2/24 |
| S3 | Gi0/1 | link to S2 Gi0/1 | SVI 99: 10.9.99.3/24 |
| PC1 | S1 Gi1/0 | VLAN 10 SALES | 10.9.10.11/24 |
| PC2 | S3 Gi1/0 | VLAN 10 SALES | 10.9.10.13/24 |
| PC3 | S3 Gi1/1 | VLAN 20 ENGINEERING | 10.9.20.13/24 |
Topology: PC1 — S1 Gi1/0 · S1 Gi0/0 — S2 Gi0/0 · S2 Gi0/1 — S3 Gi0/1 · S3 Gi1/0 — PC2 · S3 Gi1/1 — PC3.
What you’ll practise
- Explain DTP modes and predict whether two ports form a trunk
- Configure static 802.1Q trunks and turn DTP off
- Find and fix a native VLAN mismatch and explain VLAN hopping
- Limit the VLANs on a trunk safely with the allowed list
- Read every section of show interfaces trunk and describe VTP modes
The tasks
- Find out what DTP did
- Configure static trunks without DTP
- Fix the native VLAN mismatch
- Allow only the VLANs that are needed
- Read show interfaces trunk properly
- Know what VTP would do
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
- S1
Gi0/0to S2Gi0/0 - S2
Gi0/1to S3Gi0/1 - S1
Gi1/0to PC1eth0 - S3
Gi1/0to PC2eth0 - S3
Gi1/1to PC3eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| S1 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 1,024 MB |
| S2 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 1,024 MB |
| S3 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 1,024 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 |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
CCNA 200-301 guided labs.Open
09 - 802-1Q trunks - native VLAN and DTPand 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 CCNA labs
Related labs in other courses
CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.