DHCP-Load Balance Cluster unter WindowsServer 2012 R2

Übersicht

In giant environments a single DHCP server might develop into overwhelmed by the quantity of shopper DHCP lease requests it receives. Load balancing your Windows DHCP server permits you to enhance efficiency and availability by spreading the load throughout a number of servers.

Wenn ein load stability cluster is created, a partnership between two servers is outlined. Each server is ready to learn and write to the DHCP scope’s database. Any modifications are then replicated to the opposite companion to insure consistency.

Clustering is completed on the scope degree, permitting us to make use of one server, Zum Beispiel, as a cluster companion with a number of distant servers. We can selectively select to cluster all scopes out there on a server or a number of scopes.

This step-by-step tutorial will information you thru configuring a DHCP load stability cluster on Windows Server 2012 R2.

Anforderungen

  • An present Active Directory Domain.
  • Two Windows Server 2012 R2 servers which might be area members.

Install the DHCP Server Role

The DHCP server position have to be put in on each servers earlier than the cluster may be created.

  1. Log onto the primary server with an account that has administrative rights.
  2. Starten Sie die Server-Manager Konsole.
  3. In the highest-proper nook, Klicken Sie auf Verwalten

    Click the Manage link in Server Manager

  4. Klicken Sie auf Hinzufügen von Rollen und Features.
  5. Auf der Bevor Sie beginnen Web-Seite, Klicken Sie auf Nächste.
  6. Auf der Wählen Sie Art einrichten Anzeige, guarantee Role-based mostly or function-based mostly set up is chosen, nach dem Klick auf Nächste.
  7. Auf der Select vacation spot server display, guarantee Select a server from the server pool is chosen, choose the native server within the Server Pool record, nach dem Klick auf Nächste.
  8. Auf der Serverrollen auswählen Anzeige, guarantee DHCP Server wird geprüft. A dialog field referred to as Add Roles and Features Wizard will seem, if dependencies exist. Klicken Sie auf Add Feature to make sure all dependent roles or options are put in along with the DHCP server position.
  9. Klicken Sie auf Nächste.
  10. Auf der Wählen Sie Optionen Anzeige, Klicken Sie auf Nächste.
  11. Auf der DHCP Server Anzeige, Klicken Sie auf Nächste.
  12. Auf der Confirmation display, Klicken Sie auf Installieren.
  13. After the set up course of completes, there ought to be a hyperlink named Complete DHCP Configuration. Click it to start out the DHCP Server Active Directory authorization course of. A DHCP-server have to be approved earlier than it could actually assign DHCP leases.
  14. Auf der Beschreibung display of the DHCP Post-Install Configuration wizard, Klicken Sie auf Nächste.
  15. Auf der Authorization display of the DHCP Post-Install Configuration wizard, choose the suitable choice for choosing a consumer with area admin rights. This is required to authorize the server. When executed, Klicken Sie auf Commit.
  16. Auf der Zusammenfassung Anzeige, evaluation the output to make sure the authorization was profitable. Click Close.
  17. Auf der Results display of the Add Roles and Features Wizard, Klicken Sie auf In der Nähe.
  18. Log onto the second server and repeat steps P by way of 17.

Create a DHCP Scope

The cluster can't be created until a DHCP scope exists. Let’s create a easy scope to start out.

  1. Log onto the primary DHCP server.
  2. Launch the Server Manager console.
  3. On the highest-proper, Klicken Sie auf Extras.
  4. Select DHCP from the Tools drop-down menu.
  5. From the DHCP tree on the left of the console, broaden the node named after the server.
  6. Select the IPv4 node by clicking it.
  7. Right-click on the IPv4 node after which choose New Scope.
  8. Go by means of the New Scope Wizard to create the brand new scope.

Create the Load Balance Cluster

  1. From inside the DHCP console, proper-click on the IPv4 node of the DHCP server tree on the left-aspect.

    WindowsServer 2012 R2 DHCP Console

  2. Klicken Sie auf Configure Failover from the IPv4 context menu.
  3. Wenn die Configure Failover dialog field seems, choose from the obtainable scopes that you want within the cluster. If you need to embrace all of them, verify the Select All field.DHCP Configure Cluster Dialog Box
  4. Klicken Sie auf Nächste.
  5. Click Add Server so as to add the DHCP associate server. Alternativ, you possibly can enter its IP tackle or absolutely-certified area identify into the textual content subject.
  6. Klicken Sie auf weiter.
  7. On the Create a brand new failover relationship display, give the cluster relationship a reputation.

    Configure Cluster - DHCP Load Balance

  8. Legen Sie die Maximum Client Lead Time worth utilizing hours and minutes.
  9. Aus der Modus Drop-Down-Menü, Wählen Sie Load stability.
  10. Verstelle die Load Balance Percentage values of the 2 DHCP servers. The default creates a 50/50 stability between each nodes.
  11. Ensure Enable Message Authentication wird geprüft.
  12. In der Shared Secret textual content subject, enter a posh password that might be utilized by the servers. This ensures that solely servers who know the password can talk within the cluster.
  13. Klicken Sie auf Nächste.
  14. Verify your settings, nach dem Klick auf Fertig stellen.
  15. Log onto the second DHCP server.
  16. Launch the DHCP console and confirm that the scope we created on the primary DHCP server has been replicated to the second server.

Creating a DHCP Failover Cluster utilizing PowerShell

We can accomplish the identical process above utilizing PowerShell. This could be very helpful when administering the servers remotely from a shopper pc.

  1. Launch PowerShell.
  2. Nutzung der Add-DhcpServerv4Failover cmdlet. The instance under creates a partnership (cluster) referred to as Toronto-Loadbalance utilizing servers WS12-DHCP01 and WS12-DHCP02.
    Add-DhcpServerv4Failover -ComputerName ws12-dhcp01.serverlab.intra -Name Toronto-Loadbalance -PartnerServer ws12-dhcp02.serverlab.intra -ScopeId 172.30.zero.zero -LoadBalancePercent 50 -MaxClientLeadTime P:00:00
  3. Verify the cluster’s configuration utilizing the Get-DhcpServerv4Failover cmdlet.
    Name                : Toronto-Loadbalance
    PartnerServer       : ws12-dhcp02.corp.serverlab.intra
    Mode                : LoadBalance
    LoadBalancePercent  : 50
    ServerRole          :
    ReservePercent      :
    MaxClientLeadTime   : 02:00:00
    StateSwitchInterval :
    State               : Normal
    ScopeId             :
    AutoStateTransition : False
    EnableAuth          : True

 

Hinterlasse eine Antwort