dhcpd heartbeat cluster und server-identifier
Glenn.Satchell at uniq.com.au
Thu Oct 29 13:40:01 UTC 2009
>Date: Thu, 29 Oct 2009 11:13:01 +0100
>Subject: dhcpd heartbeat cluster und server-identifier
>From: stefan novak <lms.brubaker at gmail.com>
>To: Users of ISC DHCP <dhcp-users at lists.isc.org>
>X-BeenThere: dhcp-users at lists.isc.org
>I want to build a dhcpd cluster with heartbeat and drbd for fault tolerance.
>I have 2 dhcp server, every with his own ip (192.168.0.1, 192.168.0.2)
>and the active node holds the clusterip 192.168.0.10.
>I've tried to set the server-identifier to 192.168.0.10, that the
>server listens to this ip.
>But as i see the packes to the client are always sent by the primary
>server ip (eg 192.168.0.1).
>Will that be a problem for the clients when they send the DHCPREQUEST
>to 192.168.0.10 and get an answer from 192.168.0.1?
>Is there a solution for this on isc side? I dont want to use nat for
>this. Or can this just be ignored?
That should be fine. The clients look at the contents of the packet for
the server-identifier to see where they should reply. They do not
automatically use the source IP address.
Note that dhcpd also has its own load-sharing failover implementation
which works very well. You may wish to look at that, as the operating
system configuration becomes much simpler than a cluster.
You may also like to read a longer email I wrote on a related topic
some time ago:
More information about the dhcp-users