Configuring Windows DHCP failover relationships - BlueCat Address Manager - 8.3.2

Address Manager Administration Guide

prodname
BlueCat Address Manager
version_custom
8.3.2

You must define a Windows DHCP failover relationship which can then be applied when selecting a DHCP Role for Managed Windows Servers. Both a split scope and a DHCP Failover Relationship cannot be defined on a scope. Therefore, Address Manager will prevent you from trying to deploy such a configuration.

Configuring a Windows DHCP Failover relationship in Address Manager requires you to set the following:

  • Unique relationship name
  • Primary Windows DHCP server (already under Address Manager control)
  • Secondary Windows DHCP server (already under Address Manager control)
  • Maximum Client Lead Time (MCLT)
  • Failover mode: either Load Balance (default) or Hot Standby
  • Percentage distribution between primary and secondary servers
  • State Switchover Interval (optional)
  • Shared Secret (optional)

Prerequisites

Ensure you have met the following prerequisites prior to adding a Windows DHCP failover relationship in Address Manager:

  • Primary managed Windows DHCP server in Read-Write mode
  • Secondary managed Windows DHCP server in Read-Write mode
  • Defined Windows Servers interfaces in Address Manager
  • Set a DHCP block or network in Address Manager

Limitations

  • Due to the limitation of current Windows DHCP failover implementation, you cannot define more than 31 failover relationships for a single Windows DHCP server.
  • BlueCat does not support updating existing Windows DHCP failover relationships that are being used by unmanaged DHCP scopes during DHCP deployment.
  • BlueCat does not support moving a managed DHCP scope from an existing unmanaged DHCP failover relationship to a managed relationship during DHCP deployment.
  • BlueCat Address Manager for Windows Server does not support operations between Microsoft server clusters. As such, the BlueCat Windows DHCP Failover implementation does not support the configuration or deployment of DHCP failover between two Microsoft Server clusters.
  • Windows supports DHCP failover relationships at the scope / network level. Therefore, BlueCat’s implementation of DHCP failover for Windows also supports the configuration and deployment of DHCP failover at the scope / network level.
  • No API coverage exists for BlueCat Address Manager for Windows Server. As such you can only configure and deploy of Windows DHCP Failover from the Address Manager interface.