<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div><div>Hi Kraishak,</div><div> Why would you want to stop the secondary HA server? What </div><div>are you trying to achieve?</div><div><br></div><div>In answer to your questions: </div><div>1/2) When a HA server loses its connection to its partner, it starts a "failure </div><div>detection" process. When the value of max-unacked-clients is not "0", the server </div><div>uses the values of the "max-ack-delay" and "max-unacked-clients" to discover if </div><div>it should take over processing its partner's clients' requests.</div><div>Your settings are:</div><div> "max-ack-delay": 10000,</div><div> "max-unacked-clients": 13</div><div><br></div><div>This means that after communication has been interrupted for "max-response-delay" </div><div>(10000 milisecs), the primary will start the "failure detections" process. The </div><div>process will wait until it has "seen" 13 DHCP packets that have a "secs" field </div><div>with a value of 10000 or greater before starting to process the partners' client </div><div>requests.</div><div><br></div><div>see: https://kea.readthedocs.io/en/kea-2.3.7/arm/hooks.html#load-balancing-configuration</div><div><br></div><div>3) There are commands to manipulate the state the servers are in. See the "host-</div><div>ha-maintenance" commands at:</div><div>https://kea.readthedocs.io/en/kea-2.3.7/arm/hooks.html#control-commands-for-high-availability</div><div><br></div><div>But why would you want to do this? Supposing you want all client requests to be processed by </div><div>one server and have the secondary active only when the primary is unavailable. In that case, </div><div>you should consider using the "hot-standby" HA configuration.</div><div><br></div><div>Kind Regards Peter</div></div></div></body></html>