Multi-vendor troubleshooting lab 8 of 12
DHCP relay and options across vendors
One Cisco DHCP server now serves three sites through Arista, MikroTik and FortiGate relays, and each site fails differently: a reply that can't get home, a relay that stamps the wrong address, and a firewall that still answers for itself. Fix all three and check the options that clients receive.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 5,376 MB in total. That fits the free demo too.
In your workspace: Shared, then Multi-vendor interoperability and troubleshooting guided labs, then 08 - DHCP relay and options across vendors
- Level
- Intermediate
- Time
- About 65 minutes
- Nodes need
- 5 vCPU, 5,376 MB
- Smallest plan
- Lite
The scenario
Larkfield is moving every site onto one central DHCP server, a Cisco router, R1. The three sites each have a different gateway vendor, and H1 stands in for a PC at each one, with one network card per site. Today none of the three sites gets the right lease.
| Device | Interface | Address | Role |
|---|---|---|---|
| R1 | Gi0/0 | 10.50.0.1/24 | DHCP server |
| EOS1 | Ethernet1 / Ethernet2 | 10.50.0.11/24 / 10.61.0.1/24 | Relay for site A |
| CHR1 | ether1 / ether2 | 10.50.0.12/24 / 10.62.0.1/24 | Relay for site B |
| FGT1 | port1 / port2 | 10.50.0.13/24 / 10.63.0.1/24 | Relay for site C |
| H1 | eth0 / eth1 / eth2 | DHCP | A PC at site A, B and C |
Every lease should carry: an address from .21 upwards in the site's subnet (R1 excludes .1 to .20), the site's gateway, DNS server 10.50.0.53, the domain site-x.larkfield.example and option 150, the TFTP server 10.50.0.69 for desk phones.
What you’ll practise
- Explain giaddr, and how a DHCP server uses it to choose a pool and reach the relay
- Configure and read DHCP relay on EOS, RouterOS and FortiOS
- Find a return-route fault from the server's own view
- Find a relay that sets the wrong giaddr
- Find a rogue local DHCP server on a firewall
- Check the options a client really receives, including vendor options such as option 150
The tasks
- Prepare H1
- Test all three sites
- Site A, the reply that can't get home
- Site B, the wrong giaddr
- Site C, the firewall that answers first
- Check the options
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 Server-LAN (network) - EOS1
Ethernet1to Server-LAN (network) - CHR1
ether1to Server-LAN (network) - FGT1
port1to Server-LAN (network) - EOS1
Ethernet2to H1eth0 - CHR1
ether2to H1eth1 - FGT1
port2to H1eth2
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| EOS1 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| CHR1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| FGT1 | Fortinet FortiGate | fortinet-FGT-v7.0.17.M-build0682 | 1 vCPU, 2,048 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
Multi-vendor interoperability and troubleshooting guided labs.Open
08 - DHCP relay and options across vendorsand 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 Multi-vendor troubleshooting labs
All Multi-vendor troubleshooting labs
Related labs in other courses
CloudLabBox is independent of Arista Networks, Cisco, CompTIA, Fortinet, HPE, Juniper Networks and MikroTik. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.