CCNA lab 24 of 46
DHCPv4 server and relay with a router as a DHCP client
Run DHCP for three LANs from one head-office router: build pools with exclusions, relay requests from a branch router, see how the server picks the right pool, and make the edge router take its own Internet address from the provider by DHCP.
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 CCNA 200-301 guided labs, then 24 - DHCPv4 server and relay with a router as a DHCP client
- Level
- Intermediate
- Time
- About 55 minutes
- Nodes need
- 6 vCPU, 5,632 MB
- Smallest plan
- Lite
The scenario
Lynwood Veterinary has a head office (R1) and a branch (R2) with two LANs: staff and a guest Wi-Fi network. The IT contractor wants a single DHCP server for everything, so all scopes live on R1, and the branch router relays its clients' requests across the WAN. At the same time, the new Internet line from the ISP hands R1 its public address by DHCP.
| Device | Interface | Address |
|---|---|---|
| R1 | Gi0/1 HQ LAN | 10.24.1.1/24 (PC1 by DHCP) |
| R1 | Gi0/0 WAN | 10.0.12.1/30 |
| R1 | Gi0/2 Internet | DHCP from the ISP (203.0.113.0/29) |
| R2 | Gi0/0 WAN | 10.0.12.2/30 |
| R2 | Gi0/1 branch staff | 10.24.2.1/24 (PC2 by DHCP) |
| R2 | Gi0/2 branch guest | 10.24.3.1/24 (H1 by DHCP) |
| ISP | Gi0/0 / Lo0 | 203.0.113.1/29 / 198.51.100.1 (Internet server) |
R1 already routes 10.24.2.0/23 (both branch LANs) to R2, and R2 has a default route to R1.
What you’ll practise
- Explain DORA, the ports DHCP uses and what a lease contains
- Configure DHCP pools with exclusions, gateways, DNS servers, domain names and lease times
- Configure a DHCP relay agent and explain how giaddr selects the pool
- Configure a router interface as a DHCP client and recognise the DHCP-learned default route
- Verify and troubleshoot DHCP from the server and from Windows, macOS and Linux clients
The tasks
- Understand DORA
- Build the head-office pool
- Add the branch pools
- Relay the branch requests
- Make R1 a DHCP client of the ISP
- Verify from the server's side
- Read the client side on three systems
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 ISPGi0/0 - R2
Gi0/1to PC2eth0 - R2
Gi0/2to H1eth0
| 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 |
| ISP | 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 |
| H1 | 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
CCNA 200-301 guided labs.Open
24 - DHCPv4 server and relay with a router as a DHCP clientand 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.