Support DHCP Windows Failover Clustering in IPAM

Our environment has dual Windows 2008 DHCP servers in an active/passive configuration, per: Understand and Deploy DHCP Failover:

"DHCP in a Windows failover cluster. This option places a DHCP server in a cluster with another DHCP server that assumes the load if the primary DHCP server fails. The clustering deployment option uses a single shared storage. The storage unit is a single point of failure, and requires an additional investment to achieve redundancy. Clustering can be relatively complex to configure and maintain."

This is currently not supported, per this article: https://support.solarwinds.com/Success_Center/IP_Address_Manager_(IPAM)/Merge_multiple_DHCP_scopes_into_single_subnet

We would like to see support for this configuration. Thanks.

Find more posts tagged with

windows failover clustering

dhcp

ipam

Failover

Windows

clusters

Status: None

Comments

martinforster

We use it with 2012 R2 in a active active Configuration

Which really increases the need for this feature.

It would ease the process of modifying Scope properties.

Now you have to ensure that you not forget to replicate the scope changes.

ddevore9

We need this as well. It's been part of server since 2012, I'm really surprised support for this has not been added at some point.

simonu

The IPAM module and the DHCP monitoring is no longer working correctly after a recent 2012 R2 DHCP failover implementation.

The issue is that IPAM DHCP monitoring of multiple servers and the Microsoft DHCP failover system operate differently.

MS DHCP is setup to synchronise the scopes between the two DHCP servers DHCP-1 & 2 and should one fail the other will take over as it has an exact copy.
However SolarWinds DHCP monitoring of multiple servers wants to split the scopes between the two servers by the use of exclusions.

Example:
10.x.x1 - 10.x.x.100 is allowed on DHCP server 1
10.x.x.101 - 10.x.x.249 is excluded on DHCP server 1
10.x.x1 - 10.x.x.100 is excluded on DHCP server 2
10.x.x.101 - 10.x.x.249 is allowed on DHCP server 2

As you can see both implementations work differently and as a result SolarWinds reports IP duplication errors between the two servers which is actually not the case.

It would be good to see the next IPAM 4.6 resolve this issue.