CCNP ENARSI lab 30 of 35
DHCPv4 and DHCPv6: server, relay, client and options
Centralise addressing on one IOS DHCP server: relay DHCPv4 for a user LAN and a branch router, fix a pool that hands out the wrong gateway, add options, and give the branch router a stateful DHCPv6 address through a DHCPv6 relay.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 3,584 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP ENARSI 300-410 guided labs, then 30 - DHCPv4 and DHCPv6 - server relay client and options
- Level
- Intermediate
- Time
- About 70 minutes
- Nodes need
- 5 vCPU, 3,584 MB
- Smallest plan
- Lite
The scenario
Buzzard Engineering is moving every subnet's DHCP to one central IOS server, R1. The distribution router R2 serves the office LAN (PC1, PC2) and a link to a new branch router R3, which is to get both its IPv4 and IPv6 WAN addresses from R1. A colleague started the work: R1 already has a pool for the office LAN, but users complain that the PCs, when they get an address at all, can't reach anything outside the LAN.
| Device | Interface | IPv4 | IPv6 | Notes |
|---|---|---|---|---|
| R1 | Gi0/0 | 10.30.12.1/24 | 2001:db8:30:12::1/64 | DHCP server |
| R2 | Gi0/0 | 10.30.12.2/24 | 2001:db8:30:12::2/64 | to R1 |
| R2 | Gi0/1 | 10.30.23.1/24 | 2001:db8:30:23::1/64 | to R3 (relay) |
| R2 | Gi0/2 | 10.30.20.1/24 | 2001:db8:30:20::1/64 | office LAN (relay) |
| R3 | Gi0/0 | DHCP (10.30.23.10–254) | DHCPv6 (2001:db8:30:23::/64) | branch router |
| PC1, PC2 | eth0 | DHCP (10.30.20.50–254) | – | office PCs |
Options for every IPv4 pool: DNS 10.30.12.53, domain buzzard.lab. The office LAN also needs option 150 (TFTP server for the IP phones) = 10.30.12.100 and a 2-day lease. DHCPv6 for R3: DNS 2001:db8:30:12::53, domain buzzard.lab.
What you’ll practise
- Configure IOS DHCPv4 pools, excluded ranges and options (router, DNS, domain, lease, option 150)
- Relay DHCPv4 with ip helper-address and explain the giaddr
- Make a router a DHCP client and read the default route it installs
- Configure a stateful DHCPv6 server, a DHCPv6 relay and a DHCPv6 client, with the M and O flags
- Troubleshoot DHCP with bindings, pool statistics and client output
The tasks
- Find out why the PCs get nothing
- Relay DHCPv4 for the office LAN and fix the pool
- Make R3 a DHCPv4 client through the relay
- Stateful DHCPv6 through a relay
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 - R2
Gi0/1to R3Gi0/0 - R2
Gi0/2to Office-LAN (network) - PC1
eth0to Office-LAN (network) - PC2
eth0to Office-LAN (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R2 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R3 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 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 |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
CCNP ENARSI 300-410 guided labs.Open
30 - DHCPv4 and DHCPv6 - server relay client and optionsand 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 CCNP ENARSI 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.