[CCNAv6 S2] 8.1.3.3 Packet Tracer - Configuring DHCPv4 Using Cisco IOS




Packet Tracer - Configuring DHCP Using Cisco IOS
Addressing Table


Objectives

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

Scenario

A dedicated DHCP server is scalable and relatively easy to manage, but 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 are tasked with configuring a Cisco router as a DHCP server to provide dynamic allocation of addresses to clients on the network. 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.

Configure R2 to exclude the first 10 addresses from the R1 and R3 LANs. All other addresses should be available in the DHCP address pool.

Step 2:     Create a DHCP pool on R2 for the R1 LAN.

a.     Create a DHCP pool named R1-LAN (case-sensitive).

b.    Configure the DHCP pool to include the network address, the default gateway, and the IP address of the DNS server.

Step 3:     Create a DHCP pool on R2 for the R3 LAN.

a.     Create a DHCP pool named R3-LAN (case-sensitive).

b.    Configure the DHCP pool to include the network address, the default gateway, and the IP address of the DNS server.

Part 2:     Configure DHCP Relay
Step 1:     Configure R1 and R3 as a DHCP relay agent.

Step 2:     Set PC1 and PC2 to receive IP addressing information from DHCP.

Part 3:     Configure R2 as a DHCP Client
a.     Configure the Gigabit Ethernet 0/1 interface on R2 to receive IP addressing from DHCP and activate the interface.

Note: Use Packet Tracer’s Fast Forward Time feature to speed up the process or wait until R2 forms an EIGRP adjacency with the ISP router.

b.    Use the show ip interface brief command to verify that R2 received an IP address from DHCP.

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.



Configuration R2:

enable
configure terminal
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
 exit
interface GigabitEthernet0/1
 ip address dhcp
 no shutdown
 end
write memory
!

Configuration R1:

enable
configure terminal
interface GigabitEthernet0/0
 ip helper-address 10.1.1.2
  end
write memory

!

Configuration R3:

enable
configure terminal
interface GigabitEthernet0/0
 ip helper-address 10.2.2.2
 end
write memory
!

Configuration PC1:




Configuration PC2:




END !~!


Nhận xét

Bài đăng phổ biến từ blog này

[CCNAv6 S4] 8.2.4.14 Packet Tracer - Troubleshooting Enterprise Networks 3

[CCNAv6 S2] 2.2.2.4 Packet Tracer - Configuring IPv4 Static and Default Routes

[CCNAv6 S2] 7.3.2.4 Packet Tracer - Troubleshooting Standard IPv4 ACLs