<html><body><div style="font-family: Andale Mono; font-size: 10pt; color: #000000"><div style="font-family: Andale Mono; font-size: 10pt; color: #000000">When you bring the failover peer back into the loop after a partner down, it will take awhile before the returning peer starts to respond to DHCP packets but that doesn't stop the existing peer that never left from still answering. </div><div style="font-family: Andale Mono; font-size: 10pt; color: #000000"><br data-mce-bogus="1"></div><div style="font-family: Andale Mono; font-size: 10pt; color: #000000">Basically, there wouldn't be an outage but it would be some period of time (MCLT) until the returning peer begins to answer. </div><div style="font-family: Andale Mono; font-size: 10pt; color: #000000"><br data-mce-bogus="1"></div><div style="font-family: Andale Mono; font-size: 10pt; color: #000000">Don't set MCLT low, however, set it to at least 3600 as if the primary goes away, the secondary will only issue new leases and renew existing ones for the length of MCLT. I usually set MCLT to the length of the lease i have set (usually I do 8 hours).<br><br><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Sandra Schlichting" <littlesandra88@gmail.com><br><b>To: </b>"Users of ISC DHCP" <dhcp-users@lists.isc.org><br><b>Sent: </b>Wednesday, August 1, 2018 10:33:47 AM<br><b>Subject: </b>Re: How to sync a Linux secondary DHCP server?<br></blockquote></div><div data-marker="__QUOTED_TEXT__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;">> > So if I made sure that each dhcp server served dynamic leases in<br>> > different ranges, so no overlap, would it then be a good setup?<br>><br>> Yes you could do that. But I can think of a few problems:<br>><br>> If one server was faster it could have more of the clients getting<br>> addresses from it and fewer from the second server. There is no load<br>> balancing or sharing.<br><br>That would be acceptable in my setup.<br><br>> If one server is shutdown or fails, then the clients would eventually<br>> expire their leases, and would get a different address frm the other<br>> server. So persistent connections, such as ssh, web page logns, etc, would<br>> disconenct or need to re-authenticate.<br><br>Hmm. Ok, that is not optimal.<br><br>> While failover might look difficult, it is actually quite simple to set up<br>> and works very reliably. The failover code has been around for a really<br>> long time, early 2000s, so all the kinks have been well and truly worked<br>> out.<br><br>Based on Paul's reply, I got the impression that the failover were<br>risky, when he wrote:<br><br>"<br>DHCP failover is a very fragile protocol under failure. It works<br>amazingly well under normal circumstances but if you ever get to the<br>point where you're thinking about doing partner-down, be prepared to<br>have resync take hours or lose leases.<br>"<br><br>But that is not your experience, I can guess?<br>_______________________________________________<br>dhcp-users mailing list<br>dhcp-users@lists.isc.org<br>https://lists.isc.org/mailman/listinfo/dhcp-users</blockquote></div></div><div><br></div></div></body></html>