CCNA lab 2 of 46
IPv4 addressing and VLSM subnetting
Carve one private /22 into right-sized subnets for a dental practice with VLSM, address two routers and three PCs from your own plan, and prove every subnet can reach the others.
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 02 - IPv4 addressing and VLSM subnetting
- Level
- Beginner
- Time
- About 55 minutes
- Nodes need
- 5 vCPU, 5,120 MB
- Smallest plan
- Lite
The scenario
Brightwater Dental has been given the private block 172.16.40.0/22 by its IT partner. The head office router (R1) serves two LANs: Reception (about 100 devices) and Surgery (about 50 devices). A small branch router (R2) serves the Branch LAN (about 20 devices). The two routers are joined by a point-to-point WAN link.
The routers are cabled but nothing is addressed. Your job is to design a subnet plan that wastes as little space as possible, apply it, and prove that every LAN can reach every other LAN.
| Device | Interface | Connects to | Address (you work it out) |
|---|---|---|---|
| R1 | Gi0/1 | PC1 (Reception) | first usable of the Reception subnet |
| R1 | Gi0/2 | PC2 (Surgery) | first usable of the Surgery subnet |
| R1 | Gi0/0 | R2 Gi0/0 (WAN) | first usable of the WAN subnet |
| R2 | Gi0/0 | R1 Gi0/0 (WAN) | second usable of the WAN subnet |
| R2 | Gi0/1 | PC3 (Branch) | first usable of the Branch subnet |
| PC1, PC2, PC3 | eth0 | their router | last usable address of their subnet |
Topology: PC1 — R1 Gi0/1 · PC2 — R1 Gi0/2 · R1 Gi0/0 — R2 Gi0/0 · R2 Gi0/1 — PC3.
What you’ll practise
- Work out the prefix length, block size and usable range a subnet needs from a host count
- Allocate subnets largest first with VLSM and spot boundary-alignment mistakes
- Address router interfaces and hosts with first and last usable addresses
- Explain RFC 1918 private addressing and why it needs NAT to reach the Internet
- Add static and default routes so every subnet is reachable
The tasks
- Design the VLSM plan on paper
- Address and enable R1
- Address and enable R2
- Address the PCs
- Route between the sites
- Private addressing and the Internet
- Plan for growth
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 R2Gi0/0 - R1
Gi0/1to PC1eth0 - R1
Gi0/2to PC2eth0 - R2
Gi0/1to PC3eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 1,024 MB |
| R2 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 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
02 - IPv4 addressing and VLSM subnettingand 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.