Network+ lab 13 of 27
DHCP: scopes and options with reservations and relay
Run DHCP for head office and a branch from one server. You relay requests across a router, find and fix an exhausted scope, add options such as DNS and lease time, reserve an address for a printer, and capture the four DORA messages.
Run this lab
It needs Lite: its 6 nodes are set to 6 vCPU and 4,608 MB in total. That fits the free demo too.
In your workspace: Shared, then CompTIA Network Plus N10-009 guided labs, then 13 - DHCP - scopes and options with reservations and relay
- Level
- Intermediate
- Time
- About 60 minutes
- Nodes need
- 6 vCPU, 4,608 MB
- Smallest plan
- Lite
The scenario
Harbour Logistics runs DHCP centrally on its head-office router R1, for head office and for the branch behind R2. Head office works. At the branch, nothing gets an address, and the network printer must always have 10.20.20.20, because the label printers in the warehouse are configured to print to it.
| Device | Interface | Address | Notes |
|---|---|---|---|
| R1 | Gi0/0 | 10.10.10.1/24 | HQ LAN, PC1 |
| R1 | Gi0/1 | 10.0.12.1/30 | to branch R2 |
| R2 | Gi0/0 | 10.0.12.2/30 | to R1 |
| R2 | Gi0/1 | 10.20.20.1/24 | branch LAN: PC2, PC3, PRN1 |
| PRN1 | eth0 | reserved 10.20.20.20 | printer, MAC 02:00:5e:20:00:50 |
Address policy: in both LANs, .1 to .49 are reserved for routers, printers and servers, so DHCP must hand out .50 to .254 only. Clients get the DNS server 10.10.10.53, the domain harbour.lab, and a 12-hour lease.
What you’ll practise
- Explain the DORA exchange and why DHCP needs a relay across routers
- Configure DHCP scopes with exclusions, default gateway, DNS, domain and lease options
- Configure a DHCP relay (IP helper)
- Diagnose and fix address pool exhaustion
- Reserve an address for a device by its client identifier
- Capture DHCP with tcpdump and read the bindings table
The tasks
- Prepare the printer
- Watch DHCP work at head office
- Relay DHCP across the router
- Fix the exhausted scope
- Add the scope options
- Reserve the printer's address and capture DORA
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 PC1eth0 - R1
Gi0/1to R2Gi0/0 - R2
Gi0/1to Branch-LAN (network) - PC2
eth0to Branch-LAN (network) - PC3
eth0to Branch-LAN (network) - PRN1
eth0to Branch-LAN (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| R2 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 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 |
| PRN1 | 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
CompTIA Network Plus N10-009 guided labs.Open
13 - DHCP - scopes and options with reservations and relayand 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.