7.2.10 Packet Tracer – Configure DHCPv4 (Instructor Version)
|Device||Interface||IPv4 Address||Subnet Mask||Default Gateway|
|G0/1||DHCP Assigned||DHCP Assigned||N/A|
|PC1||NIC||DHCP Assigned||DHCP Assigned||DHCP Assigned|
|PC2||NIC||DHCP Assigned||DHCP Assigned||DHCP Assigned|
- Part 1: Configure a Router as a DHCP Server
- Part 2: Configure DHCP Relay
- Part 3: Configure a Router as a DHCP Client
- Part 4: Verify DHCP and Connectivity
A dedicated DHCP server is scalable and relatively easy to manage but it can be costly to have one at every location in a network. However, a Cisco router can be configured to provide DHCP services without the need for a dedicated server. As the network technician for your company, you have been assigned the task of configuring a Cisco router as a DHCP server. You are also required to configure the edge router as a DHCP client so that it receives an IP address from the ISP network.
Part 1: Configure a Router as a DHCP Server
Step 1: Configure the excluded IPv4 addresses.
Addresses that have been statically assigned to devices in the networks that will use DHCP must be excluded from the DHCP pools. This avoids errors associated with duplicate IP addresses. In this case the IP addresses of the R1 and R3 LAN interfaces must be excluded from DHCP. In addition, nine other addresses are excluded for static assignment to other devices such servers and device management interfaces.
a. Configure R2 to exclude the first 10 addresses from the R1 LAN.
R2(config)# ip dhcp excluded-address 192.168.10.1 192.168.10.10
b. Configure R2 to exclude the first 10 addresses from R3 LAN.
R2(config)# ip dhcp excluded-address 192.168.30.1 192.168.30.10
Step 2: Create a DHCP pool on R2 for the R1 LAN.
a. Create a DHCP pool named R1-LAN (case-sensitive).
R2(config)# ip dhcp pool R1-LAN
b. Configure the DHCP pool to include the network address, the default gateway, and the IP address of the DNS server.
R2(dhcp-config)# network 192.168.10.0 255.255.255.0 R2(dhcp-config)# default-router 192.168.10.1 R2(dhcp-config)# dns-server 192.168.20.254
Step 3: Create a DHCP pool on R2 for the R3 LAN.
a. Create a DHCP pool named R3-LAN (case-sensitive).
R2(config)# ip dhcp pool R3-LAN
b. Configure the DHCP pool to include the network address, the default gateway, and the IP address of the DNS server. Refer to the Addressing Table.
R2(dhcp-config)# network 192.168.30.0 255.255.255.0 R2(dhcp-config)# default-router 192.168.30.1 R2(dhcp-config)# dns-server 192.168.20.254
Part 2: Configure DHCP Relay
Step 1: Configure R1 and R3 as a DHCP relay agent.
For DHCP clients to obtain an address from a server on a different LAN segment, the interface that the clients are attached to must include a helper address pointing to the DHCP server. In this case, the hosts on the LANs that are attached to R1 and R3 will access the DHCP server that is configured on R2. The IP addresses of the R2 serial interfaces that are attached to R1 and R3 are used as the helper addresses. DHCP traffic from the hosts on the R1 and R3 LANs will be forwarded to these addresses and processed by the DHCP server that is configured on R2.
a. Configure the helper address for the LAN interface on R1.
R1(config)# interface g0/0 R1(config-if)# ip helper-address 10.1.1.2
b. Configure the helper address for the LAN interface on R3.
R3(config)# interface g0/0 R3(config-if)# ip helper-address 10.2.2.2
Step 2: Configure hosts to receive IP addressing information from DHCP.
a. Configure hosts PC1 and PC2 to receive their IP addresses from a DHCP server.
b. Verify that the hosts have received their addresses from the correct DHCP pools.
Part 3: Configure a Router as a DHCP Client
Just as a PC is able to receive an IPv4 address from a server, a router interface has the ability to do the same. Router R2 needs to be configured to receive addressing from the ISP.
a. Configure the Gigabit Ethernet 0/1 interface on R2 to receive IP addressing from DHCP and activate the interface.
R2(config)# interface g0/1 R2(config-if)# ip address dhcp R2(config-if)# no shutdown
Note: Use Packet Tracer Fast Forward Time feature to speed up the process.
b. Use the
show ip interface brief command to verify that R2 received an IP address from DHCP.
R2#show ip int brief Interface IP-Address OK? Method Status Protocol GigabitEthernet0/0 192.168.20.1 YES manual up up GigabitEthernet0/1 126.96.36.199 YES DHCP up up Serial0/0/0 10.1.1.2 YES manual up up Serial0/0/1 10.2.2.2 YES manual up up Serial0/1/0 unassigned YES unset down down Serial0/1/1 unassigned YES unset down down Vlan1 unassigned YES unset administratively down down R2#
Part 4: Verify DHCP and Connectivity
Step 1: Verify DHCP bindings.
R2# show ip dhcp binding IP address Client-ID/ Lease expiration Type Hardware address 192.168.10.11 0002.4AA5.1470 -- Automatic 192.168.30.11 0004.9A97.2535 -- Automatic
Step 2: Verify configurations.
Verify that PC1 and PC2 can now ping each other and all other devices.
enable config t interface g0/0 ip helper-address 10.1.1.2
enable config t ip dhcp excluded-address 192.168.10.1 192.168.10.10 ip dhcp excluded-address 192.168.30.1 192.168.30.10 ip dhcp pool R1-LAN network 192.168.10.0 255.255.255.0 default-router 192.168.10.1 dns-server 192.168.20.254 ip dhcp pool R3-LAN network 192.168.30.0 255.255.255.0 default-router 192.168.30.1 dns-server 192.168.20.254 interface g0/1 ip address dhcp no shutdown
enable config t interface g0/0 ip helper-address 10.2.2.2
Download PDF & PKA file: