How to properly break DHCPd failover peer relationship

Bill Shirley bill at c3po.polymerindustries.biz
Thu Mar 15 14:35:03 UTC 2018


I agree.  Also, you should remove the failover preamble from /var/lib/dhcpd/dhcpd.leases
before restarting the master:
failover peer "dhcp-failover" state {
   my state normal at 1 2018/03/12 11:30:52;
   partner state normal at 1 2018/03/12 11:30:52;
}

Bill

On 3/14/2018 10:21 AM, Steven Carr wrote:
> On 13 March 2018 at 13:25, Bob Harold <rharolde at umich.edu> wrote:
>> I would suggest these steps:
>>
>> 1. On the failover server, stop the DHCP process.
>> 2. On the primary server, put in "partner down" mode.  (I don't have the
>> exact command in front of me, I think you use omshell.)
>> 3. Wait for as long as your longest lease time.  You can watch the clients
>> do DHCPREQUESTs to the failover server from half the lease time to 7/8, and
>> then DHCPDISCOVER and get the lease renewed from the primary server.
>> 4. Reconfigure the primary server without the failover options.
> As long as they are both up they should be in sync with each other,
> and both systems have a full copy of the leases, so no need to use
> partner down - it could actually cause you more pain to put it into
> partner down if you are close to running out of leases in any pools -
> on entering partner down you have to wait MCLT before you take over
> the other addresses.
>
> Just remove any mention of failover from the primary configuration,
> shut down the secondary, restart the primary, remove any IP helpers
> pointing to the secondary.
>
> And of course, goes without saying, do this in a maintenance window.
>
> Steve
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20180315/0bd62c96/attachment.html>


More information about the dhcp-users mailing list