<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div><div>Hi Kraishak,</div><div> Looking at your log file, it appears that "Server A" only saw one unacked </div><div>client, so it didn't transform to a partner-down state. I see several </div><div>HA_COMMUNICATION_INTERRUPTED_CLIENT4 messages </div><div>but only one </div><div>HA_COMMUNICATION_INTERRUPTED_CLIENT4_UNACKED message.</div><div><br></div><div>2023-05-15 16:07:30.127 INFO [kea-dhcp4.ha-hooks/32411.139751579436800] HA_COMMUNICATION_INTERRUPTED_CLIENT4_UNACKED [hwtype=1 34:98:b5:dc:1f:99], cid=[no info], tid=0x4be21c7f: partner server failed to respond, 1 clients unacked so far, 13 clients left before transitioning to the partner-down state</div><div><br></div><div>Your configuration contains the following statement: </div><div> "max-unacked-clients": 13</div><div>The "max-ack-delay" parameter has a default value of 10000 ms.</div><div>I suggest you check that your traffic generator correctly increments the "secs" </div><div>field and to modify your HA settings appropriately.</div><div><br></div><div>From the Kea ARM:</div><div><br></div><div>HA_COMMUNICATION_INTERRUPTED_CLIENT4</div><div>%1: new client attempting to get a lease from the partner</div><div>This informational message is issued when the surviving server observes a DHCP </div><div>packet sent to the partner with which the communication is interrupted. The </div><div>the client whose packet is observed is not yet considered “unacked” because the </div><div>secs field value does not exceed the configured threshold specified with </div><div>max-ack-delay.</div><div><br></div><div>HA_COMMUNICATION_INTERRUPTED_CLIENT4_UNACKED</div><div>%1: partner server failed to respond, %2 clients unacked so far, %3 clients left before transitioning to the partner-down state</div><div>This informational message is issued when the surviving server determines that </div><div>its partner failed to respond to the DHCP query and that this client is considered </div><div>to not be served by the partner. The surviving server counts such clients, and if </div><div>the number of such clients exceeds the max-unacked-clients threshold, the server </div><div>will transition to the partner-down state. The first argument contains client </div><div>identification information. The second argument specifies the number of clients </div><div>to which the server has failed to respond. The third argument specifies the number </div><div>of additional clients, which, if not provisioned, will cause the server to transition </div><div>to the partner-down state.</div><div><br data-mce-bogus="1"></div><div>Kind Regards Peter</div></div></div></body></html>