CCNA lab 10 of 46
Inter-VLAN routing with router-on-a-stick
Route between three VLANs through a single router link: build the switch side, create 802.1Q subinterfaces with a native VLAN on the router, then follow a packet as it leaves and re-enters the same cable.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 5,120 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNA 200-301 guided labs, then 10 - Inter-VLAN routing with router-on-a-stick
- Level
- Beginner
- Time
- About 45 minutes
- Nodes need
- 5 vCPU, 5,120 MB
- Smallest plan
- Lite
The scenario
Granite Print has a single router and a single switch in its small office. Sales, engineering and guests are in separate VLANs, and now they need to reach each other (and, later, the Internet) through the router. There's only one free port on the router, so you'll run all the VLANs over one trunk: router-on-a-stick.
| Device | Interface | VLAN | Address |
|---|---|---|---|
| R1 | Gi0/0.10 | 10 SALES | 10.10.10.1/24 |
| R1 | Gi0/0.20 | 20 ENGINEERING | 10.10.20.1/24 |
| R1 | Gi0/0.30 | 30 GUEST | 10.10.30.1/24 |
| R1 | Gi0/0.99 | 99 MGMT (native, untagged) | 10.10.99.1/24 |
| S1 | SVI VLAN 99 | 99 MGMT | 10.10.99.2/24, gateway 10.10.99.1 |
| PC1 | S1 Gi0/1 | 10 | 10.10.10.10/24 |
| PC2 | S1 Gi0/2 | 20 | 10.10.20.10/24 |
| PC3 | S1 Gi0/3 | 30 | 10.10.30.10/24 |
Topology: R1 Gi0/0 — S1 Gi0/0 (802.1Q trunk) · S1 Gi0/1, Gi0/2, Gi0/3 — PC1, PC2, PC3.
What you’ll practise
- Explain why routing between VLANs needs a Layer 3 device
- Build a trunk from a switch to a router with a native management VLAN
- Configure 802.1Q subinterfaces, including the native VLAN
- Verify inter-VLAN routing with show commands, ping and traceroute
- Describe the limits of router-on-a-stick
The tasks
- Understand the design
- Build the switch side
- Create the router's subinterfaces
- Verify routing between the VLANs
- Follow the packet
- Know the limits
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
- R1
Gi0/0to S1Gi0/0 - S1
Gi0/1to PC1eth0 - S1
Gi0/2to PC2eth0 - S1
Gi0/3to PC3eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 1,024 MB |
| S1 | 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
10 - Inter-VLAN routing with router-on-a-stickand 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.