Case Study

Configuring DHCP Failover in Windows Server

Course Code: CPE232 Program: BSCPE
Course Title: Managing Enterprise Servers Date Performed:
Section: CPE42FB2 Date Submitted: AUGUST 01, 2019
Names: PAGADUAN, JOHN DAVID C. Instructor: ENGR. ALONICA VILLANUEVA
1. Objective(s):

This activity aims to configure a failover using Windows Server.

2. Intended Learning Outcomes (ILOs):

The students should be able to:
2.1 Setup and configure DHCP failover using Windows Server 2016
2.2 Implement and test the DHCP failover in a network of Windows and Linux PCs.
2.3 Document and troubleshoot any errors encountered in configuring DHCP failover.

3. Discussion:
Failover from the dictionary is the constant capability to automatically and seamlessly switch to a highly
reliable backup. DHCP failover is used to load balance client requests among two DHCP servers and
provides fault tolerance. If one of the DHCP servers is down, then the other keeps serving IP addresses to
clients.
Failover automatically and transparently to the user redirects requests from the failed or down system to the
backup system that mimics the operations of the primary system. In this case study the student should able
to test and implement the DHCP failover in the Windows Server 2016.

4. Resources:
Two (2) Windows Server 2016
Two (2) Linux client - Ubuntu and Kali
One (1) Windows 7 client
5. Procedure:

 Configuring Failover

Figure 5.1
 Figure 5.1 shows to manage authorized server which it is register the DHCP service.

Figure 5.2
 Figure 5.2 shows that the 192.168.10.25 (Partner Server) will Authorized in the DHCP Server.
 Figure 5.3
 Figure 5.3 shows it confirms the IP address 192.168.10.25 (server1server) to be authorized in
the DHCP Server.

Figure 5.4
 In the figure above right click the IPv4 and click the Configure Failover like shows in the Figure
5.4
 Figure 5.5
 Figure 5.5 shows the list of scope you want to configure for failover. In the Figure above the scope
used is 192.168.10.0

Figure 5.6
 Figure 5.6 asks to provide a host name or IP address of the Partner DHCP Server which failover
will be configured. The figure above shows that the IP address 192.168.10.25 will be the failover
should configure.
 Figure 5.7
 Figure 5.7 shows the mode I choose in failover relationship.

Figure 5.8
 Figure 5.8 shows the summary of failover relationship, then click finish.
 Figure 5.9
 Figure 5.9 shows the progress of the various task for configuring failover in the figure above is
shows successful progress.

Figure 5.10
 The figure above shows that the scope 192.168.10.0 is **Active**.
 Figure 5.11
 Figure 5.11 shows that the address leases under main server.
  Testing the DHCP failover (Main Server and Partner Server)

The Figure below shows that we try to shut down the main server and test is the partner server is able to
catch the address leases from the main server.

Figure 5.12
 The figure above shows that after shutting down the main server the partner server is able to catch
all the address leases.

Figure 5.13
 Figure 5.13 shows after testing shutting down the partner server we try it vice versa and the main
server is able to catch all the address lease from the partner server.
 Implementing DHCP Failover using Linux clients

Figure 5.14
 Figure 5.14 shows that kali Linux releases the IP address.

Figure 5.15
 Figure 1.5 shows that the kali Linux renews a IP address.
 Figure 5.15.1
 Figure 5.15.1 shows that the Kali Linux new address is 192.168.10.125
 Figure 5.16
 Figure 5.16 shows that the Ubuntu renew an IP address.

Figure 5.17
 Figure 5.17 shows that the Ubuntu Desktop IP Address is new (192.168.10.144).
 Implementing DHCP Failover using Windows client

Figure 5.18
 Figure 5.18 shows that the Windows 7 is to release a IP address.

Figure 5.19
 Figure 5.19 shows that the IP address of Windows 7 is changed to 192.168.10.146.
6. Conclusion

7. Assessment (Rubric for Laboratory Performance):