Procedure for failover partner replacement.
perl-list
perl-list at network1.net
Thu May 11 14:00:09 UTC 2017
If you are using the same version of DHCP, then it should work fine.
I have done exactly that before and it has worked for me. The DHCP servers returned to both partners normal mode after a very brief (not responding startup) state. The DHCP servers did not appear to in any way realize they were on a different cluster.
> From: "Bob McDonald" <bmcdonaldjr at gmail.com>
> To: dhcp-users at lists.isc.org
> Sent: Thursday, May 11, 2017 9:35:42 AM
> Subject: Procedure for failover partner replacement.
> I've got a failing dhcp failover partner. (the partner is a HA cluster and both
> nodes are being RMAed. Long story)
> My question is this. Is the following procedure ok for the replacement? (I've
> already confirmed the new version of DHCP is exactly the same as the old one)
> 1) before shutting down the failing partner cluster, stop DHCP and save the
> dhcpd.leases file and the DHCPD.conf file.
> 2) shut down the failing partner cluster completely.
> 3) bring up the replacement partner cluster while leaving DHCPD turmed off.
> 4) restore the DHCPD.leases and DHCPD.conf files.
> 5) restart DHPCD on the replacement partner cluster.
> My contention is that this will result in the failover pair going into
> partner-interrupted state for about 5 or 10 minutes while the HA cluster is
> replaced and then should restart communications as if nothing happened when the
> replacement partner comes live. Thoughts?
> Regards,
> Bob
> _______________________________________________
> 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/20170511/2e0ec4b6/attachment.html>
More information about the dhcp-users
mailing list