Switch from Single DHCP to Master-Slave DHCP setup

Greg Sloop <gregs@sloop.net> gregs at sloop.net
Tue Jul 30 18:35:21 UTC 2013

Yeah, that's what I thought.

You tell the Up machine that the other (down) machine is in partner down
state and then simply rebuild and bring up the "down" box as a new one and
just bring it up as "new."

Thanks for the clairification!

 On Jul 30, 2013 9:34 AM, "Steven Carr" <sjcarr at gmail.com> wrote:

> On 30 July 2013 16:52, Gregory Sloop <gregs at sloop.net> wrote:
>> You say above, you'd put the *primary* in partner down???
>> Do you mean secondary?
>> Then rebuild and bring up the secondary again. And once the secondary
>> comes up out of PD state it will re-sync...
>> Or perhaps you really *do* mean the *primary* - I'm not sure.
> By primary I mean the server which will be left online. The way "partner
> down" works is that you tell the server which is online that their partner
> is down and so therefore it is now allowed to consume all of the remaining
> IP addresses.
> All you need to do on the box which is dead/being rebuilt is make sure
> DHCPD isn't running, or at least isn't running with any DHCP failover
> configuration configured.
> 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/20130730/da380013/attachment.html>

More information about the dhcp-users mailing list