<!DOCTYPE html><html><head><title></title><style type="text/css">#qt p.qt-MsoNormal{margin-top:0in;margin-right:0in;margin-bottom:0in;margin-left:0in;font-size:11pt;font-family:"Calibri", sans-serif;}
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Thu, Jan 5, 2023, at 12:16, Frey, Rick E via Kea-users wrote:<br></div><blockquote type="cite" id="qt" style="overflow-wrap:break-word;"><div class="qt-WordSection1"><div><div><div><div><p class="qt-MsoNormal"> <br></p><p class="qt-MsoNormal">Example:<br></p><p class="qt-MsoNormal">server1 not receiving DHCP requests from clients but is communicating with server2. server2 is receiving DHCP requests from all clients but ignoring some requests due to client should be serviced by server1 (via internal algorithm of client
ID).<br></p><p class="qt-MsoNormal">If server2 sees that server1 is not sending any updates/leases for said client requests, server1 is put into state that allows server2 to service requests. Tricky part would be in determining if/when server1 should auto change state if
begins to see client requests. Perhaps an option to put node in maintenance mode that requires manually enabling server1?<br></p></div></div></div></div></div><div><br></div></blockquote><div>This would be my choice; if server1 is unhealthy (even if it is caused by the network connection and the software on server1 is unaware of the problem), then bringing it back online should require administrator action.<br></div></body></html>