<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:PMingLiU;
panose-1:2 2 5 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
@font-face
{font-family:"\@PMingLiU";
panose-1:2 1 6 1 0 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Hi Darren,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thank you for the explanation. I tested again and I do see now the clients could extend their addresses without losing it.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I have another question, I re-enabled the primary kea-01 again, after that, I noticed Kea-01 seems to have retaken the role of the primary again automatically. Is there a way we can keep the standby continue
serve as temporary primary instead of revert automatically? Also, is there a convenient way to check both hosts which one is serving the DHCP lease now instead of checking the details of the debug logs? I don’t remember see those details from the 2.4.1 documentation.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Kea-01:<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:49:40.239 DEBUG [kea-dhcp6.alloc-engine/41273.139801047443200] ALLOC_ENGINE_V6_EXTEND_LEASE duid=[00:04:bf:aa:9f:84:51:61:0b:20:44:a6:6a:ec:1b:99:8b:b3], tid=0xe8593b: extending lifetime of the
lease type IA_NA, address fd74:5656:15e2:10::202<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:49:40.239 DEBUG [kea-dhcp6.alloc-engine/41273.139801047443200] ALLOC_ENGINE_V6_EXTEND_LEASE_DATA duid=[00:04:bf:aa:9f:84:51:61:0b:20:44:a6:6a:ec:1b:99:8b:b3], tid=0xe8593b: detailed information
about the lease being extended: Type: IA_NA(0)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Address: fd74:5656:15e2:10::202<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Prefix length: 128<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">IAID: 3394439514<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Pref life: 300<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Valid life: 400<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Cltt: 1712238385<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">DUID: 00:04:bf:aa:9f:84:51:61:0b:20:44:a6:6a:ec:1b:99:8b:b3<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Hardware addr: (none)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Subnet ID: 1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Pool ID: 0<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">State: default<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:49:40.239 DEBUG [kea-dhcp6.alloc-engine/41273.139801047443200] ALLOC_ENGINE_V6_EXTEND_NEW_LEASE_DATA duid=[00:04:bf:aa:9f:84:51:61:0b:20:44:a6:6a:ec:1b:99:8b:b3], tid=0xe8593b: new lease information
for the lease being extended: Type: IA_NA(0)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Address: fd74:5656:15e2:10::202<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Prefix length: 128<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">IAID: 3394439514<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Pref life: 300<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Valid life: 400<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Cltt: 1712238580<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">DUID: 00:04:bf:aa:9f:84:51:61:0b:20:44:a6:6a:ec:1b:99:8b:b3<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Hardware addr: (none)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Subnet ID: 1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Pool ID: 0<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">State: default<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:49:40.239 DEBUG [kea-dhcp6.dhcpsrv/41273.139801047443200] DHCPSRV_MEMFILE_UPDATE_ADDR6 updating IPv6 lease for address fd74:5656:15e2:10::202<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:49:40.239 INFO [kea-dhcp6.leases/41273.139801047443200] DHCP6_LEASE_RENEW duid=[00:04:bf:aa:9f:84:51:61:0b:20:44:a6:6a:ec:1b:99:8b:b3], tid=0xe8593b: lease for address fd74:5656:15e2:10::202
and iaid=3394439514 has been allocated<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:49:40.239 DEBUG [kea-dhcp6.callouts/41273.139801047443200] HOOKS_CALLOUTS_BEGIN begin all callouts for hook leases6_committed<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:49:40.239 DEBUG [kea-dhcp6.http/41273.139801047443200] HTTP_CLIENT_REQUEST_SEND sending HTTP request POST / HTTP/1.1 to
<a href="http://192.168.100.70:8000/">http://192.168.100.70:8000/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:49:40.239 DEBUG [kea-dhcp6.http/41273.139801047443200] HTTP_CLIENT_REQUEST_SEND_DETAILS detailed information about request sent to
<a href="http://192.168.100.70:8000/">http://192.168.100.70:8000/</a>:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">POST / HTTP/1.1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Host: 192.168.100.70<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Content-Length: 427<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Content-Type: application/json<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">{ "arguments": { "deleted-leases": [ ], "leases": [ { "duid": "00:04:bf:aa:9f:84:51:61:0b:20:44:a6:6a:ec:1b:99:8b:b3", "expire": 1712238980, "fqdn-fwd": false, "fqdn-rev": false, "hostname": "", "iaid": 3394439514,
"ip-address": "fd74:5656:15e2:10::202", "preferred-lft": 300, "state": 0, "subnet-id": 1, "type": "IA_NA", "valid-lft": 400 } ], "origin": "ha-partner" }, "command": "lease6-bulk-apply", "service": [ "dhcp6" ] }<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Kea-03:<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:48:02.103 DEBUG [kea-dhcp6.http/41298.140241352439552] HTTP_SERVER_RESPONSE_SEND_DETAILS detailed information about response sent to 192.168.100.197:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">HTTP/1.1 200 OK<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Content-Length: 184<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Content-Type: application/json<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Date: Thu, 04 Apr 2024 13:48:02 GMT<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">[ { "arguments": { "date-time": "Thu, 04 Apr 2024 13:48:02 GMT", "scopes": [ ], "state": "hot-standby", "unsent-update-count": 4 }, "result": 0, "text": "HA peer status returned." } ]<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:48:06.081 DEBUG [kea-dhcp6.packets/41298.140241550008320] DHCP6_BUFFER_RECEIVED received buffer from fe80::7cbe:6ff:fe66:e263:546 to ff02::1:2:0 over interface ens18<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:48:06.081 DEBUG [kea-dhcp6.callouts/41298.140241419581184] HOOKS_CALLOUTS_BEGIN begin all callouts for hook buffer6_receive<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:48:06.081 DEBUG [kea-dhcp6.ha-hooks/41298.140241419581184] HA_BUFFER6_RECEIVE_NOT_FOR_US duid=[00:04:bf:aa:9f:84:51:61:0b:20:44:a6:6a:ec:1b:99:8b:b3], tid=0x816669: dropping query to be processed
by another server<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:48:06.081 DEBUG [kea-dhcp6.callouts/41298.140241419581184] HOOKS_CALLOUT_CALLED hooks library with index 2 has called a callout on hook buffer6_receive that has address 0x7f8c802af060 (callout
duration: 0.121 ms)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:48:06.081 DEBUG [kea-dhcp6.callouts/41298.140241419581184] HOOKS_CALLOUTS_COMPLETE completed callouts for hook buffer6_receive (total callouts duration: 0.121 ms)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:48:06.081 DEBUG [kea-dhcp6.hooks/41298.140241419581184] DHCP6_HOOK_BUFFER_RCVD_DROP received buffer from fe80::7cbe:6ff:fe66:e263 to ff02::1:2 over interface ens18 was dropped because a callout
set the drop flag<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:48:09.444 DEBUG [kea-dhcp6.packets/41298.140241550008320] DHCP6_BUFFER_RECEIVED received buffer from fe80::c40b:ebff:fed1:7298:546 to ff02::1:2:0 over interface ens18<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:48:09.445 DEBUG [kea-dhcp6.callouts/41298.140241411188480] HOOKS_CALLOUTS_BEGIN begin all callouts for hook buffer6_receive<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:48:09.445 DEBUG [kea-dhcp6.ha-hooks/41298.140241411188480] HA_BUFFER6_RECEIVE_NOT_FOR_US duid=[00:04:a3:35:01:e3:85:15:e1:76:3e:47:e3:b0:c5:f8:55:10], tid=0x852612: dropping query to be processed
by another server<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2024-04-04 09:48:09.445 DEBUG [kea-dhcp6.callouts/41298.140241411188480] HOOKS_CALLOUT_CALLED hooks library with index 2 has called a callout on hook buffer6_receive that has address 0x7f8c802af060 (callout
duration: 0.127 ms)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Yu<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Kea-users <kea-users-bounces@lists.isc.org> on behalf of Darren Ankney <darren.ankney@gmail.com><br>
<b>Date: </b>Thursday, April 4, 2024 at 5:48</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span><span style="font-size:12.0pt;color:black">AM<br>
<b>To: </b>Kea-users@lists.isc.org <kea-users@lists.isc.org><br>
<b>Subject: </b>Re: [Kea-users] [EXTERNAL] Re: kea-2.4.1 // Strange HA related errors<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Hi Yu,<br>
<br>
Basically you are not waiting for clients to go down. Clients will<br>
attempt to renew at lease half-life. "max-unacked-clients" is a way<br>
of confirming that the other server is actually down. In certain<br>
scenarios it would be possible that the two servers couldn't see each<br>
other but COULD see the clients. If they were both answering the<br>
clients, that could lead to duplicate IP address assignment and the<br>
like.<br>
<br>
Thank you,<br>
Darren Ankney<br>
<br>
On Wed, Apr 3, 2024 at 5:32</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><span style="font-size:11.0pt">PM Xiao, Yu (CCI-Atlanta) <yu.xiao@cox.com> wrote:<br>
><br>
> Hi Darren,<br>
><br>
><br>
><br>
> Thank you for your information. I adjusted the parameter and now it is working. But I have a question, why should we need this "max-unacked-clients" parameter? Because imagine we have 1k devices in this network, and they all have their IP assigned by dhcp_1,
then suddenly dhcp_1 went down, but at this moment, all devices still have their assigned IPs. Then if we design dhcp_2 to become primary after losing sync time, we may be able to bring dhcp_2 to primary before T2, so there won’t be large number of devices
offline. But if we wait until offline devices observed, then it could be too late and many devices already offline.<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> Best Regards,<br>
><br>
> Yu<br>
><br>
><br>
><br>
><br>
><br>
> From: Kea-users <kea-users-bounces@lists.isc.org> on behalf of Xiao, Yu (CCI-Atlanta) via Kea-users <kea-users@lists.isc.org><br>
> Date: Wednesday, April 3, 2024 at 9:12</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><span style="font-size:11.0pt">AM<br>
> To: Darren Ankney <darren.ankney@gmail.com>, Kea user's list <kea-users@lists.isc.org><br>
> Cc: Xiao, Yu (CCI-Atlanta) <yu.xiao@cox.com><br>
> Subject: Re: [Kea-users] [EXTERNAL] Re: kea-2.4.1 // Strange HA related errors<br>
><br>
> Hi Darren,<br>
><br>
><br>
><br>
> Thank you for the explanation. Let me investigate further.<br>
><br>
><br>
><br>
><br>
><br>
> Best Regards,<br>
><br>
> Yu<br>
><br>
><br>
><br>
><br>
><br>
> From: Darren Ankney <darren.ankney@gmail.com><br>
> Date: Wednesday, April 3, 2024 at 9:06</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><span style="font-size:11.0pt">AM<br>
> To: Kea user's list <kea-users@lists.isc.org><br>
> Cc: Xiao, Yu (CCI-Atlanta) <yu.xiao@cox.com><br>
> Subject: Re: [Kea-users] [EXTERNAL] Re: kea-2.4.1 // Strange HA related errors<br>
><br>
> Hi Yu,<br>
><br>
> Look in your logs for messages containing<br>
> HA_COMMUNICATION_INTERRUPTED_CLIENT4_UNACKED. These messages indicate<br>
> how many clients are still needed before the failover will occur.<br>
> Your settings specify:<br>
><br>
> "max-ack-delay": 300,<br>
> "max-unacked-clients": 5,<br>
><br>
> max-ack-delay is specified in milliseconds so pretty much every client<br>
> that reaches one in the "elapsed time" option in DHCPv6 will meet the<br>
> criteria of an "unacked" client. Once the sixth client shows up,<br>
> failover should occur. That log message should repeat with each new<br>
> client being tracked giving statistics about how many more are needed.<br>
><br>
> Thank you,<br>
> Darren Ankney<br>
><br>
><br>
> On Tue, Apr 2, 2024 at 12:39</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><span style="font-size:11.0pt">PM Xiao, Yu (CCI-Atlanta) via Kea-users<br>
> <kea-users@lists.isc.org> wrote:<br>
> ><br>
> > Hi experts,<br>
> ><br>
> ><br>
> ><br>
> > I have tested further in my lab and found the answers to my questions. HA works when I don’t enable the control agent. As for the debug log, I think there’s a potential document bug for 2.4.1 document. Cause you can’t assign the log to /var/log folder,
you need to assign it to /tmp/ folder.<br>
> ><br>
> ><br>
> ><br>
> > I found a problem on myside on firewall, after I fixed it. Now seems the HA is working. But still having one problem. When I used “systemctl stop kea-dhcp6” on the primary, for example, kea01, then the standby DHCPv6 server kea03 won’t process the DHCP
packets from clients. I waited for more time, but the behaviors won’t change. The standby server just drop those DHCP packets from clients due to “dropping query to be processed by another server”.<br>
> ><br>
> ><br>
> ><br>
> > According to Kea documentation, this happens when:<br>
> ><br>
> ><br>
> ><br>
> > “%1: dropping query to be processed by another server<br>
> ><br>
> ><br>
> ><br>
> > This debug message is issued when the received DHCPv6 query is dropped by this server because it should be served by another server. This is the case when the remote server was designated to process the packet as a result of load balancing or because it
is a primary server in the hot standby configuration. The argument provides client identification information retrieved from the query.”<br>
> ><br>
> ><br>
> ><br>
> > But now since the primary service is down, so the standby server should become the primary one, right? But seems not the case. Also from the debug logs, I can’t see the current status of the remaining server, technically we should be able to see its status
changed from standby to primary, right? But I only see the role information from the logs before I shut down the kea service on primary server.<br>
> ><br>
> ><br>
> ><br>
> > Config:<br>
> ><br>
> > # HA related hooks configuration<br>
> ><br>
> > "hooks-libraries": [{<br>
> ><br>
> > "library": "/usr/lib64/kea/hooks/libdhcp_lease_cmds.so",<br>
> ><br>
> > "parameters": { }<br>
> ><br>
> > }, {<br>
> ><br>
> > "library": "/usr/lib64/kea/hooks/libdhcp_ha.so",<br>
> ><br>
> > "parameters": {<br>
> ><br>
> > "high-availability": [{<br>
> ><br>
> > "this-server-name": "kea_home3",<br>
> ><br>
> > "mode": "hot-standby",<br>
> ><br>
> > "heartbeat-delay": 100,<br>
> ><br>
> > "max-response-delay": 200,<br>
> ><br>
> > "max-ack-delay": 300,<br>
> ><br>
> > "max-unacked-clients": 5,<br>
> ><br>
> > "peers": [{<br>
> ><br>
> > "name": "kea_home1",<br>
> ><br>
> > "url": <a href="https://urldefense.com/v3/__http:/192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$">
https://urldefense.com/v3/__http://192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$</a> ,<br>
> ><br>
> > "role": "primary",<br>
> ><br>
> > "auto-failover": true<br>
> ><br>
> > }, {<br>
> ><br>
> > "name": "kea_home3",<br>
> ><br>
> > "url": <a href="https://urldefense.com/v3/__http:/192.168.100.70:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvU0f5KAX$">
https://urldefense.com/v3/__http://192.168.100.70:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvU0f5KAX$</a> ,<br>
> ><br>
> > "role": "standby",<br>
> ><br>
> > "auto-failover": true<br>
> ><br>
> > }]<br>
> ><br>
> > }]<br>
> ><br>
> > }<br>
> ><br>
> > }],<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > Logs:<br>
> ><br>
> > 2024-04-02 12:03:41.696 DEBUG [kea-dhcp6.http/15314.139903918055424] HTTP_CLIENT_REQUEST_SEND_DETAILS detailed information about request sent to
<a href="https://urldefense.com/v3/__http:/192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$">
https://urldefense.com/v3/__http://192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$</a> :<br>
> ><br>
> > POST / HTTP/1.1<br>
> ><br>
> > Host: 192.168.100.197<br>
> ><br>
> > Content-Length: 53<br>
> ><br>
> > Content-Type: application/json<br>
> ><br>
> ><br>
> ><br>
> > { "command": "ha-heartbeat", "service": [ "dhcp6" ] }<br>
> ><br>
> > 2024-04-02 12:03:41.696 DEBUG [kea-dhcp6.http/15314.139903754057472] HTTP_BAD_SERVER_RESPONSE_RECEIVED bad response received when communicating with
<a href="https://urldefense.com/v3/__http:/192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$">
https://urldefense.com/v3/__http://192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$</a> : Connection refused<br>
> ><br>
> > 2024-04-02 12:03:41.696 WARN [kea-dhcp6.ha-hooks/15314.139903754057472] HA_HEARTBEAT_COMMUNICATIONS_FAILED failed to send heartbeat to kea_home1 (https://urldefense.com/v3/__http://192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$
): Connection refused<br>
> ><br>
> > 2024-04-02 12:03:41.696 WARN [kea-dhcp6.ha-hooks/15314.139903754057472] HA_COMMUNICATION_INTERRUPTED communication with kea_home1 is interrupted<br>
> ><br>
> > 2024-04-02 12:03:41.773 DEBUG [kea-dhcp6.packets/15314.139903918055424] DHCP6_BUFFER_RECEIVED received buffer from fe80::c40b:ebff:fed1:7298:546 to ff02::1:2:0 over interface ens18<br>
> ><br>
> > 2024-04-02 12:03:41.773 DEBUG [kea-dhcp6.callouts/15314.139903787628288] HOOKS_CALLOUTS_BEGIN begin all callouts for hook buffer6_receive<br>
> ><br>
> > 2024-04-02 12:03:41.773 DEBUG [kea-dhcp6.ha-hooks/15314.139903787628288] HA_BUFFER6_RECEIVE_NOT_FOR_US duid=[00:04:a3:35:01:e3:85:15:e1:76:3e:47:e3:b0:c5:f8:55:10], tid=0x65a570: dropping query to be processed by another server<br>
> ><br>
> > 2024-04-02 12:03:41.773 DEBUG [kea-dhcp6.callouts/15314.139903787628288] HOOKS_CALLOUT_CALLED hooks library with index 2 has called a callout on hook buffer6_receive that has address 0x7f3de3bc3060 (callout duration: 0.161 ms)<br>
> ><br>
> > 2024-04-02 12:03:41.773 DEBUG [kea-dhcp6.callouts/15314.139903787628288] HOOKS_CALLOUTS_COMPLETE completed callouts for hook buffer6_receive (total callouts duration: 0.161 ms)<br>
> ><br>
> > 2024-04-02 12:03:41.773 DEBUG [kea-dhcp6.hooks/15314.139903787628288] DHCP6_HOOK_BUFFER_RCVD_DROP received buffer from fe80::c40b:ebff:fed1:7298 to ff02::1:2 over interface ens18 was dropped because a callout set the drop flag<br>
> ><br>
> > 2024-04-02 12:03:42.774 DEBUG [kea-dhcp6.http/15314.139903918055424] HTTP_CLIENT_REQUEST_SEND sending HTTP request POST / HTTP/1.1 to
<a href="https://urldefense.com/v3/__http:/192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$">
https://urldefense.com/v3/__http://192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$</a><br>
> ><br>
> > 2024-04-02 12:03:42.774 DEBUG [kea-dhcp6.http/15314.139903918055424] HTTP_CLIENT_REQUEST_SEND_DETAILS detailed information about request sent to
<a href="https://urldefense.com/v3/__http:/192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$">
https://urldefense.com/v3/__http://192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$</a> :<br>
> ><br>
> > POST / HTTP/1.1<br>
> ><br>
> > Host: 192.168.100.197<br>
> ><br>
> > Content-Length: 53<br>
> ><br>
> > Content-Type: application/json<br>
> ><br>
> ><br>
> ><br>
> > { "command": "ha-heartbeat", "service": [ "dhcp6" ] }<br>
> ><br>
> > 2024-04-02 12:03:42.775 DEBUG [kea-dhcp6.http/15314.139903728879360] HTTP_BAD_SERVER_RESPONSE_RECEIVED bad response received when communicating with
<a href="https://urldefense.com/v3/__http:/192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$">
https://urldefense.com/v3/__http://192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$</a> : Connection refused<br>
> ><br>
> > 2024-04-02 12:03:42.775 WARN [kea-dhcp6.ha-hooks/15314.139903728879360] HA_HEARTBEAT_COMMUNICATIONS_FAILED failed to send heartbeat to kea_home1 (https://urldefense.com/v3/__http://192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$
): Connection refused<br>
> ><br>
> > 2024-04-02 12:03:42.775 WARN [kea-dhcp6.ha-hooks/15314.139903728879360] HA_COMMUNICATION_INTERRUPTED communication with kea_home1 is interrupted<br>
> ><br>
> > 2024-04-02 12:03:43.776 DEBUG [kea-dhcp6.http/15314.139903918055424] HTTP_CLIENT_REQUEST_SEND sending HTTP request POST / HTTP/1.1 to
<a href="https://urldefense.com/v3/__http:/192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$">
https://urldefense.com/v3/__http://192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$</a><br>
> ><br>
> > 2024-04-02 12:03:43.776 DEBUG [kea-dhcp6.http/15314.139903918055424] HTTP_CLIENT_REQUEST_SEND_DETAILS detailed information about request sent to
<a href="https://urldefense.com/v3/__http:/192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$">
https://urldefense.com/v3/__http://192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$</a> :<br>
> ><br>
> > POST / HTTP/1.1<br>
> ><br>
> > Host: 192.168.100.197<br>
> ><br>
> > Content-Length: 53<br>
> ><br>
> > Content-Type: application/json<br>
> ><br>
> ><br>
> ><br>
> > Server status from debug logs:<br>
> ><br>
> ><br>
> ><br>
> > 2024-04-02 11:50:32.503 DEBUG [kea-dhcp6.dhcp6/15314.139903918055424] DHCP6_CONFIG_START DHCPv6 server is processing the following configuration: { "control-socket": { "socket-name": "/tmp/kea6-ctrl-socket", "socket-type": "unix" }, "hooks-libraries": [
{ "library": "/usr/lib64/kea/hooks/libdhcp_lease_cmds.so", "parameters": { } }, { "library": "/usr/lib64/kea/hooks/libdhcp_ha.so", "parameters": { "high-availability": [ { "heartbeat-delay": 100, "max-ack-delay": 300, "max-response-delay": 200, "max-unacked-clients":
5, "mode": "hot-standby", "peers": [ { "auto-failover": true, "name": "kea_home1", "role": "primary", "url":
<a href="https://urldefense.com/v3/__http:/192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$">
https://urldefense.com/v3/__http://192.168.100.197:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvY8Qy6Ik$</a> }, { "auto-failover": true, "name": "kea_home3", "role": "standby", "url":
<a href="https://urldefense.com/v3/__http:/192.168.100.70:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvU0f5KAX$">
https://urldefense.com/v3/__http://192.168.100.70:8000/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvU0f5KAX$</a> } ], "this-server-name": "kea_home3" } ] } } ], "interfaces-config": { "interfaces": [ "ens18" ], "service-sockets-require-all":
true }, "lease-database": { "name": "/var/lib/kea/dhcp6.leases", "persist": true, "type": "memfile" }, "loggers": [ { "debuglevel": 99, "name": "kea-dhcp6", "output_options": [ { "maxsize": 40480000, "maxver": 8, "output": "/tmp/kea-debug.log" } ], "severity":
"DEBUG" } ], "preferred-lifetime": 300, "rebind-timer": 200, "renew-timer": 100, "subnet6": [ { "id": 1, "interface": "ens18", "pools": [ { "pool": "fd74:5656:15e2:10::200-fd74:5656:15e2:10::9999" } ], "subnet": "fd74:5656:15e2:10::/64" } ], "valid-lifetime":
400 }<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > Best Regards,<br>
> ><br>
> > Yu<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > From: Kea-users <kea-users-bounces@lists.isc.org> on behalf of Xiao, Yu (CCI-Atlanta) via Kea-users <kea-users@lists.isc.org><br>
> > Date: Monday, April 1, 2024 at 5:18</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><span style="font-size:11.0pt">PM<br>
> > To: Kea user's list <kea-users@lists.isc.org><br>
> > Cc: Xiao, Yu (CCI-Atlanta) <yu.xiao@cox.com><br>
> > Subject: Re: [Kea-users] [EXTERNAL] Re: kea-2.4.1 // Strange HA related errors<br>
> ><br>
> > Hi Darren/experts,<br>
> ><br>
> ><br>
> ><br>
> > I have changed to 8000 port, but still the HA is not working. I have the following questions:<br>
> ><br>
> ><br>
> ><br>
> > Do I need to enable kea-ctrl-agent to make HA work? Or they are separate?<br>
> > I configured the logger related configuration, but I don’t see the log file has been created, did I miss something? Here’s my config:<br>
> ><br>
> ><br>
> ><br>
> > "loggers": [<br>
> ><br>
> > {<br>
> ><br>
> > "name": "kea-dhcp6",<br>
> ><br>
> > "output_options": [<br>
> ><br>
> > {<br>
> ><br>
> > "output": "/var/log/kea-debug.log",<br>
> ><br>
> > "maxver": 8,<br>
> ><br>
> > "maxsize": 204800,<br>
> ><br>
> > "flush": true,<br>
> ><br>
> > "pattern": "%d{%j %H:%M:%S.%q} %c %m\n"<br>
> ><br>
> > }<br>
> ><br>
> > ],<br>
> ><br>
> > "severity": "DEBUG",<br>
> ><br>
> > "debuglevel": 99<br>
> ><br>
> > }<br>
> ><br>
> ><br>
> ><br>
> > ]<br>
> ><br>
> ><br>
> ><br>
> > [root@kea_home3 kea]# systemctl status kea-dhcp6.service<br>
> ><br>
> > ● kea-dhcp6.service - Kea DHCPv6 Service<br>
> ><br>
> > Loaded: loaded (/usr/lib/systemd/system/kea-dhcp6.service; enabled; vendor preset: disabled)<br>
> ><br>
> > Active: active (running) since Mon 2024-04-01 17:08:48 EDT; 4min 30s ago<br>
> ><br>
> > Docs: man:kea-dhcp6(8)<br>
> ><br>
> > Main PID: 4085 (kea-dhcp6)<br>
> ><br>
> > Tasks: 13 (limit: 10999)<br>
> ><br>
> > Memory: 4.3M<br>
> ><br>
> > CGroup: /system.slice/kea-dhcp6.service<br>
> ><br>
> > └─4085 /usr/sbin/kea-dhcp6 -c /etc/kea/kea-dhcp6.conf<br>
> ><br>
> ><br>
> ><br>
> > Here’s a kea folder but no kea-debug.log as I defined:<br>
> ><br>
> ><br>
> ><br>
> > [root@kea_home3 kea]# ll /var/log/ |grep kea<br>
> ><br>
> > drwxr-x---. 2 kea kea 6 Nov 23 14:06 kea<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > Best Regards,<br>
> ><br>
> > Yu<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > From: Kea-users <kea-users-bounces@lists.isc.org> on behalf of Xiao, Yu (CCI-Atlanta) via Kea-users <kea-users@lists.isc.org><br>
> > Date: Friday, March 29, 2024 at 10:47</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><span style="font-size:11.0pt">AM<br>
> > To: Kea user's list <kea-users@lists.isc.org><br>
> > Cc: Xiao, Yu (CCI-Atlanta) <yu.xiao@cox.com><br>
> > Subject: Re: [Kea-users] [EXTERNAL] Re: kea-2.4.1 // Strange HA related errors<br>
> ><br>
> > Thank you for the advice, Darren. Let me test on them.<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > Best Regards,<br>
> ><br>
> > Yu<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > From: Kea-users <kea-users-bounces@lists.isc.org> on behalf of Darren Ankney <darren.ankney@gmail.com><br>
> > Date: Friday, March 29, 2024 at 6:58</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><span style="font-size:11.0pt">AM<br>
> > To: Kea user's list <kea-users@lists.isc.org><br>
> > Subject: Re: [Kea-users] [EXTERNAL] Re: kea-2.4.1 // Strange HA related errors<br>
> ><br>
> > Hi Yu,<br>
> ><br>
> > You will need to enable multi-threading dedicated listener for HA as<br>
> > described here:<br>
> > <a href="https://urldefense.com/v3/__https:/kea.readthedocs.io/en/kea-2.4.1/arm/hooks.html*multi-threaded-configuration-ha-mt__;Iw!!Hit2Ag!zoh5xPnvNfIYnDVa8fKOaBy5jIIQIMWT5qUv1AwVKSJJWw6Sv4JGdCWpcT1787WpOLtTS--cCCJ1garUIhR_$">
https://urldefense.com/v3/__https://kea.readthedocs.io/en/kea-2.4.1/arm/hooks.html*multi-threaded-configuration-ha-mt__;Iw!!Hit2Ag!zoh5xPnvNfIYnDVa8fKOaBy5jIIQIMWT5qUv1AwVKSJJWw6Sv4JGdCWpcT1787WpOLtTS--cCCJ1garUIhR_$</a><br>
> > or alter your "url" in each in the peers blocks to port 8001 so that<br>
> > they communicate via the kea-ctrl-agent. I think that should fix it.<br>
> ><br>
> > Thank you,<br>
> > Darren Ankney<br>
> ><br>
> > On Tue, Mar 26, 2024 at 7:58</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><span style="font-size:11.0pt">AM Xiao, Yu (CCI-Atlanta) via Kea-users<br>
> > <kea-users@lists.isc.org> wrote:<br>
> > ><br>
> > > Hi Darren,<br>
> > ><br>
> > ><br>
> > ><br>
> > > I am using 2.4.1.<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > Best Regards,<br>
> > ><br>
> > > Yu<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > From: Kea-users <kea-users-bounces@lists.isc.org> on behalf of Darren Ankney <darren.ankney@gmail.com><br>
> > > Date: Tuesday, March 26, 2024 at 6:03</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><span style="font-size:11.0pt">AM<br>
> > > To: Kea user's list <kea-users@lists.isc.org><br>
> > > Subject: [EXTERNAL] Re: [Kea-users] kea-2.4.1 // Strange HA related errors<br>
> > ><br>
> > > Hello Yu,<br>
> > ><br>
> > > What version of Kea are you running on these servers, out of curiosity?<br>
> > ><br>
> > > Thank you,<br>
> > > Darren Ankney<br>
> > ><br>
> > > On Mon, Mar 25, 2024 at 10:55</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><span style="font-size:11.0pt">AM Xiao, Yu (CCI-Atlanta) via Kea-users<br>
> > > <kea-users@lists.isc.org> wrote:<br>
> > > ><br>
> > > > Hi experts,<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > I have configured two VMs in the same hypervisor as hot-standby mode HA. I believe they are successfully communicating with each other with heart beat packets, as we can see the primary VM kea-1 has successfully received the “ha-heartbeat” from the
standby VM kea-2 in green logs. But the red logs indicate that the ha_hooks think the HA heartbeat communications failed due to “no route”. But this is a LAN network, and there’s indeed route installed as we can see below and we can ping the 69 ip.<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > [yxiao322@kea_home1 ~]$ ip route<br>
> > > ><br>
> > > > 192.168.100.0/24 dev ens18 proto kernel scope link src 192.168.100.197 metric 100 <<< This should be the route to 192.168.100.69<br>
> > > ><br>
> > > > 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > [root@kea_home1 yxiao322]# ping 192.168.100.69<br>
> > > ><br>
> > > > PING 192.168.100.69 (192.168.100.69) 56(84) bytes of data.<br>
> > > ><br>
> > > > 64 bytes from 192.168.100.69: icmp_seq=1 ttl=64 time=0.342 ms<br>
> > > ><br>
> > > > 64 bytes from 192.168.100.69: icmp_seq=2 ttl=64 time=0.302 ms<br>
> > > ><br>
> > > > 64 bytes from 192.168.100.69: icmp_seq=3 ttl=64 time=0.236 ms<br>
> > > ><br>
> > > > ^Z<br>
> > > ><br>
> > > > [1]+ Stopped ping 192.168.100.69<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > And if I stop the kea service on primary, then we can see standby server will complain “communication with kea_home1 is interrupted”. And as soon as I start kea service again on primary, then the database began sync again. Thus, I believe there’s indeed
communications and syncs between primary and standby VMs. But for some reason, if I shut the kea service on primary, then the standby won’t distribute DHCP leases even after I waited for a long time. Did I miss something here?<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > Primary logs:<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > Mar 25 10:35:37 kea_home1 kea-dhcp6[1224]: 2024-03-25 10:35:37.198 INFO [kea-dhcp6.commands/1224.139988007651072] COMMAND_RECEIVED Received command 'ha-heartbeat'<br>
> > > ><br>
> > > > Mar 25 10:35:37 kea_home1 kea-dhcp6[1224]: 2024-03-25 10:35:37.627 WARN [kea-dhcp6.ha-hooks/1224.139988049614592] HA_HEARTBEAT_COMMUNICATIONS_FAILED failed to send heartbeat to kea_home2 (https://urldefense.com/v3/__http://192.168.100.69:8000/__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTi1Q4B1j$
): No route to host<br>
> > > ><br>
> > > > Mar 25 10:35:37 kea_home1 kea-dhcp6[1224]: 2024-03-25 10:35:37.627 WARN [kea-dhcp6.ha-hooks/1224.139988049614592] HA_COMMUNICATION_INTERRUPTED communication with kea_home2 is interrupted<br>
> > > ><br>
> > > > Mar 25 10:35:38 kea_home1 kea-dhcp6[1224]: 2024-03-25 10:35:38.199 INFO [kea-dhcp6.commands/1224.139988016043776] COMMAND_RECEIVED Received command 'ha-heartbeat'<br>
> > > ><br>
> > > > Mar 25 10:35:38 kea_home1 kea-dhcp6[1224]: 2024-03-25 10:35:38.627 WARN [kea-dhcp6.ha-hooks/1224.139988032829184] HA_HEARTBEAT_COMMUNICATIONS_FAILED failed to send heartbeat to kea_home2 (https://urldefense.com/v3/__http://192.168.100.69:8000/__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTi1Q4B1j$
): No route to host<br>
> > > ><br>
> > > > Mar 25 10:35:38 kea_home1 kea-dhcp6[1224]: 2024-03-25 10:35:38.627 WARN [kea-dhcp6.ha-hooks/1224.139988032829184] HA_COMMUNICATION_INTERRUPTED communication with kea_home2 is interrupted<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > Standby logs:<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > Mar 25 10:10:24 kea_home2 kea-dhcp6[2836]: 2024-03-25 10:10:24.129 WARN [kea-dhcp6.ha-hooks/2836.139717198915328] HA_COMMUNICATION_INTERRUPTED communication with kea_home1 is interrupted<br>
> > > ><br>
> > > > Mar 25 10:10:25 kea_home2 kea-dhcp6[2836]: 2024-03-25 10:10:25.130 WARN [kea-dhcp6.ha-hooks/2836.139717207308032] HA_HEARTBEAT_COMMUNICATIONS_FAILED failed to send heartbeat to kea_home1 (https://urldefense.com/v3/__http://192.168.100.197:8000/__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTiEJ4bVb$
): Connection refused<br>
> > > ><br>
> > > > Mar 25 10:10:25 kea_home2 kea-dhcp6[2836]: 2024-03-25 10:10:25.130 WARN [kea-dhcp6.ha-hooks/2836.139717207308032] HA_COMMUNICATION_INTERRUPTED communication with kea_home1 is interrupted<br>
> > > ><br>
> > > > Mar 25 10:10:26 kea_home2 kea-dhcp6[2836]: 2024-03-25 10:10:26.132 WARN [kea-dhcp6.ha-hooks/2836.139717190522624] HA_HEARTBEAT_COMMUNICATIONS_FAILED failed to send heartbeat to kea_home1 (https://urldefense.com/v3/__http://192.168.100.197:8000/__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTiEJ4bVb$
): Connection refused<br>
> > > ><br>
> > > > Mar 25 10:10:26 kea_home2 kea-dhcp6[2836]: 2024-03-25 10:10:26.132 WARN [kea-dhcp6.ha-hooks/2836.139717190522624] HA_COMMUNICATION_INTERRUPTED communication with kea_home1 is interrupted<br>
> > > ><br>
> > > > Mar 25 10:10:27 kea_home2 kea-dhcp6[2836]: 2024-03-25 10:10:27.136 INFO [kea-dhcp6.ha-hooks/2836.139717215700736] HA_STATE_TRANSITION server transitions from PARTNER-DOWN to WAITING state, partner state is PARTNER-DOWN<br>
> > > ><br>
> > > > Mar 25 10:10:27 kea_home2 kea-dhcp6[2836]: 2024-03-25 10:10:27.137 INFO [kea-dhcp6.ha-hooks/2836.139717215700736] HA_LEASE_UPDATES_DISABLED lease updates will not be sent to the partner while in WAITING state<br>
> > > ><br>
> > > > Mar 25 10:10:27 kea_home2 kea-dhcp6[2836]: 2024-03-25 10:10:27.137 INFO [kea-dhcp6.ha-hooks/2836.139717215700736] HA_LOCAL_DHCP_DISABLE local DHCP service is disabled while the kea_home2 is in the WAITING state<br>
> > > ><br>
> > > > Mar 25 10:10:27 kea_home2 kea-dhcp6[2836]: 2024-03-25 10:10:27.137 INFO [kea-dhcp6.ha-hooks/2836.139717215700736] HA_STATE_TRANSITION server transitions from WAITING to SYNCING state, partner state is PARTNER-DOWN<br>
> > > ><br>
> > > > Mar 25 10:10:27 kea_home2 kea-dhcp6[2836]: 2024-03-25 10:10:27.137 INFO [kea-dhcp6.ha-hooks/2836.139717215700736] HA_LEASE_UPDATES_DISABLED lease updates will not be sent to the partner while in SYNCING state<br>
> > > ><br>
> > > > Mar 25 10:10:27 kea_home2 kea-dhcp6[2836]: 2024-03-25 10:10:27.137 INFO [kea-dhcp6.ha-hooks/2836.139717215700736] HA_SYNC_START starting lease database synchronization with kea_home1<br>
> > > ><br>
> > > > Mar 25 10:10:27 kea_home2 kea-dhcp6[2836]: 2024-03-25 10:10:27.140 INFO [kea-dhcp6.ha-hooks/2836.139717215700736] HA_LEASES_SYNC_LEASE_PAGE_RECEIVED received 3 leases from kea_home1<br>
> > > ><br>
> > > > Mar 25 10:10:27 kea_home2 kea-dhcp6[2836]: 2024-03-25 10:10:27.141 INFO [kea-dhcp6.ha-hooks/2836.139717215700736] HA_SYNC_SUCCESSFUL lease database synchronization with kea_home1 completed successfully in 4.350 ms<br>
> > > ><br>
> > > > Mar 25 10:10:27 kea_home2 kea-dhcp6[2836]: 2024-03-25 10:10:27.142 INFO [kea-dhcp6.ha-hooks/2836.139717215700736] HA_STATE_TRANSITION server transitions from SYNCING to READY state, partner state is PARTNER-DOWN<br>
> > > ><br>
> > > > Mar 25 10:10:27 kea_home2 kea-dhcp6[2836]: 2024-03-25 10:10:27.142 INFO [kea-dhcp6.ha-hooks/2836.139717215700736] HA_LEASE_UPDATES_DISABLED lease updates will not be sent to the partner while in READY state<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > Primary Config:<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > # HA related hooks configuration<br>
> > > ><br>
> > > > "hooks-libraries": [{<br>
> > > ><br>
> > > > "library": "/usr/lib64/kea/hooks/libdhcp_lease_cmds.so",<br>
> > > ><br>
> > > > "parameters": { }<br>
> > > ><br>
> > > > }, {<br>
> > > ><br>
> > > > "library": "/usr/lib64/kea/hooks/libdhcp_ha.so",<br>
> > > ><br>
> > > > "parameters": {<br>
> > > ><br>
> > > > "high-availability": [{<br>
> > > ><br>
> > > > "this-server-name": "kea_home1",<br>
> > > ><br>
> > > > "mode": "hot-standby",<br>
> > > ><br>
> > > > "heartbeat-delay": 200,<br>
> > > ><br>
> > > > "max-response-delay": 600,<br>
> > > ><br>
> > > > "max-ack-delay": 800,<br>
> > > ><br>
> > > > "max-unacked-clients": 5,<br>
> > > ><br>
> > > > "send-lease-updates": true,<br>
> > > ><br>
> > > > "sync-leases": true,<br>
> > > ><br>
> > > > "sync-page-limit": 200,<br>
> > > ><br>
> > > > "sync-timeout": 600,<br>
> > > ><br>
> > > > "delayed-updates-limit": 0,<br>
> > > ><br>
> > > > "peers": [{<br>
> > > ><br>
> > > > "name": "kea_home1",<br>
> > > ><br>
> > > > "url": <a href="https://urldefense.com/v3/__http:/192.168.100.197:8000/__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTiEJ4bVb$">
https://urldefense.com/v3/__http://192.168.100.197:8000/__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTiEJ4bVb$</a> ,<br>
> > > ><br>
> > > > "role": "primary",<br>
> > > ><br>
> > > > "auto-failover": true<br>
> > > ><br>
> > > > }, {<br>
> > > ><br>
> > > > "name": "kea_home2",<br>
> > > ><br>
> > > > "url": <a href="https://urldefense.com/v3/__http:/192.168.100.69:8000/__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTi1Q4B1j$">
https://urldefense.com/v3/__http://192.168.100.69:8000/__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTi1Q4B1j$</a> ,<br>
> > > ><br>
> > > > "role": "standby",<br>
> > > ><br>
> > > > "auto-failover": true<br>
> > > ><br>
> > > > }]<br>
> > > ><br>
> > > > }]<br>
> > > ><br>
> > > > }<br>
> > > ><br>
> > > > }],<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > "Control-agent": {<br>
> > > ><br>
> > > > "http-host": "192.168.100.197",<br>
> > > ><br>
> > > > // If enabling HA and multi-threading, the 8000 port is used by the HA<br>
> > > ><br>
> > > > // hook library http listener. When using HA hook library with<br>
> > > ><br>
> > > > // multi-threading to function, make sure the port used by dedicated<br>
> > > ><br>
> > > > // listener is different (e.g. 8001) than the one used by CA. Note<br>
> > > ><br>
> > > > // the commands should still be sent via CA. The dedicated listener<br>
> > > ><br>
> > > > // is specifically for HA updates only.<br>
> > > ><br>
> > > > "http-port": 8001,<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > Standby config:<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > # HA related hooks configuration<br>
> > > ><br>
> > > > "hooks-libraries": [{<br>
> > > ><br>
> > > > "library": "/usr/lib64/kea/hooks/libdhcp_lease_cmds.so",<br>
> > > ><br>
> > > > "parameters": { }<br>
> > > ><br>
> > > > }, {<br>
> > > ><br>
> > > > "library": "/usr/lib64/kea/hooks/libdhcp_ha.so",<br>
> > > ><br>
> > > > "parameters": {<br>
> > > ><br>
> > > > "high-availability": [{<br>
> > > ><br>
> > > > "this-server-name": "kea_home2",<br>
> > > ><br>
> > > > "mode": "hot-standby",<br>
> > > ><br>
> > > > "heartbeat-delay": 200,<br>
> > > ><br>
> > > > "max-response-delay": 600,<br>
> > > ><br>
> > > > "max-ack-delay": 800,<br>
> > > ><br>
> > > > "max-unacked-clients": 5,<br>
> > > ><br>
> > > > "delayed-updates-limit": 0,<br>
> > > ><br>
> > > > "send-lease-updates": true,<br>
> > > ><br>
> > > > "sync-leases": true,<br>
> > > ><br>
> > > > "sync-page-limit": 200,<br>
> > > ><br>
> > > > "sync-timeout": 600,<br>
> > > ><br>
> > > > "peers": [{<br>
> > > ><br>
> > > > "name": "kea_home1",<br>
> > > ><br>
> > > > "url": <a href="https://urldefense.com/v3/__http:/192.168.100.197:8000/__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTiEJ4bVb$">
https://urldefense.com/v3/__http://192.168.100.197:8000/__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTiEJ4bVb$</a> ,<br>
> > > ><br>
> > > > "role": "primary",<br>
> > > ><br>
> > > > "auto-failover": true<br>
> > > ><br>
> > > > }, {<br>
> > > ><br>
> > > > "name": "kea_home2",<br>
> > > ><br>
> > > > "url": <a href="https://urldefense.com/v3/__http:/192.168.100.69:8000/__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTi1Q4B1j$">
https://urldefense.com/v3/__http://192.168.100.69:8000/__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTi1Q4B1j$</a> ,<br>
> > > ><br>
> > > > "role": "standby",<br>
> > > ><br>
> > > > "auto-failover": true<br>
> > > ><br>
> > > > }]<br>
> > > ><br>
> > > > }]<br>
> > > ><br>
> > > > }<br>
> > > ><br>
> > > > }],<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > "Control-agent": {<br>
> > > ><br>
> > > > "http-host": "192.168.100.69",<br>
> > > ><br>
> > > > // If enabling HA and multi-threading, the 8000 port is used by the HA<br>
> > > ><br>
> > > > // hook library http listener. When using HA hook library with<br>
> > > ><br>
> > > > // multi-threading to function, make sure the port used by dedicated<br>
> > > ><br>
> > > > // listener is different (e.g. 8001) than the one used by CA. Note<br>
> > > ><br>
> > > > // the commands should still be sent via CA. The dedicated listener<br>
> > > ><br>
> > > > // is specifically for HA updates only.<br>
> > > ><br>
> > > > "http-port": 8001,<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > Best Regards,<br>
> > > ><br>
> > > > Yu<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > --<br>
> > > > ISC funds the development of this software with paid support subscriptions. Contact us at
<a href="https://urldefense.com/v3/__https:/www.isc.org/contact/__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTl3O_IGO$">
https://urldefense.com/v3/__https://www.isc.org/contact/__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTl3O_IGO$</a> for more information.<br>
> > > ><br>
> > > > To unsubscribe visit <a href="https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTp7W6GPF$">
https://urldefense.com/v3/__https://lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTp7W6GPF$</a> .<br>
> > > ><br>
> > > > Kea-users mailing list<br>
> > > > Kea-users@lists.isc.org<br>
> > > > <a href="https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTp7W6GPF$">
https://urldefense.com/v3/__https://lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTp7W6GPF$</a><br>
> > > --<br>
> > > ISC funds the development of this software with paid support subscriptions. Contact us at
<a href="https://urldefense.com/v3/__https:/www.isc.org/contact/__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTl3O_IGO$">
https://urldefense.com/v3/__https://www.isc.org/contact/__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTl3O_IGO$</a> for more information.<br>
> > ><br>
> > > To unsubscribe visit <a href="https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTp7W6GPF$">
https://urldefense.com/v3/__https://lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTp7W6GPF$</a> .<br>
> > ><br>
> > > Kea-users mailing list<br>
> > > Kea-users@lists.isc.org<br>
> > > <a href="https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTp7W6GPF$">
https://urldefense.com/v3/__https://lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!xbrgKugiAG9Ig2_84VjCtBW6x-DpB9Aox3x1n_oCHrMu1W-ZDDMlKiorN7OVohqT2UUHSGoJ3ePqTp7W6GPF$</a><br>
> > ><br>
> > > --<br>
> > > ISC funds the development of this software with paid support subscriptions. Contact us at
<a href="https://urldefense.com/v3/__https:/www.isc.org/contact/__;!!Hit2Ag!zoh5xPnvNfIYnDVa8fKOaBy5jIIQIMWT5qUv1AwVKSJJWw6Sv4JGdCWpcT1787WpOLtTS--cCCJ1gbTSITyu$">
https://urldefense.com/v3/__https://www.isc.org/contact/__;!!Hit2Ag!zoh5xPnvNfIYnDVa8fKOaBy5jIIQIMWT5qUv1AwVKSJJWw6Sv4JGdCWpcT1787WpOLtTS--cCCJ1gbTSITyu$</a> for more information.<br>
> > ><br>
> > > To unsubscribe visit <a href="https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!zoh5xPnvNfIYnDVa8fKOaBy5jIIQIMWT5qUv1AwVKSJJWw6Sv4JGdCWpcT1787WpOLtTS--cCCJ1gf4IdHNb$">
https://urldefense.com/v3/__https://lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!zoh5xPnvNfIYnDVa8fKOaBy5jIIQIMWT5qUv1AwVKSJJWw6Sv4JGdCWpcT1787WpOLtTS--cCCJ1gf4IdHNb$</a> .<br>
> > ><br>
> > > Kea-users mailing list<br>
> > > Kea-users@lists.isc.org<br>
> > > <a href="https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!zoh5xPnvNfIYnDVa8fKOaBy5jIIQIMWT5qUv1AwVKSJJWw6Sv4JGdCWpcT1787WpOLtTS--cCCJ1gf4IdHNb$">
https://urldefense.com/v3/__https://lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!zoh5xPnvNfIYnDVa8fKOaBy5jIIQIMWT5qUv1AwVKSJJWw6Sv4JGdCWpcT1787WpOLtTS--cCCJ1gf4IdHNb$</a><br>
> > --<br>
> > ISC funds the development of this software with paid support subscriptions. Contact us at
<a href="https://urldefense.com/v3/__https:/www.isc.org/contact/__;!!Hit2Ag!zoh5xPnvNfIYnDVa8fKOaBy5jIIQIMWT5qUv1AwVKSJJWw6Sv4JGdCWpcT1787WpOLtTS--cCCJ1gbTSITyu$">
https://urldefense.com/v3/__https://www.isc.org/contact/__;!!Hit2Ag!zoh5xPnvNfIYnDVa8fKOaBy5jIIQIMWT5qUv1AwVKSJJWw6Sv4JGdCWpcT1787WpOLtTS--cCCJ1gbTSITyu$</a> for more information.<br>
> ><br>
> > To unsubscribe visit <a href="https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!zoh5xPnvNfIYnDVa8fKOaBy5jIIQIMWT5qUv1AwVKSJJWw6Sv4JGdCWpcT1787WpOLtTS--cCCJ1gf4IdHNb$">
https://urldefense.com/v3/__https://lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!zoh5xPnvNfIYnDVa8fKOaBy5jIIQIMWT5qUv1AwVKSJJWw6Sv4JGdCWpcT1787WpOLtTS--cCCJ1gf4IdHNb$</a> .<br>
> ><br>
> > Kea-users mailing list<br>
> > Kea-users@lists.isc.org<br>
> > <a href="https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!zoh5xPnvNfIYnDVa8fKOaBy5jIIQIMWT5qUv1AwVKSJJWw6Sv4JGdCWpcT1787WpOLtTS--cCCJ1gf4IdHNb$">
https://urldefense.com/v3/__https://lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!zoh5xPnvNfIYnDVa8fKOaBy5jIIQIMWT5qUv1AwVKSJJWw6Sv4JGdCWpcT1787WpOLtTS--cCCJ1gf4IdHNb$</a><br>
> ><br>
> > --<br>
> > ISC funds the development of this software with paid support subscriptions. Contact us at
<a href="https://urldefense.com/v3/__https:/www.isc.org/contact/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvXwmzyK4$">
https://urldefense.com/v3/__https://www.isc.org/contact/__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvXwmzyK4$</a> for more information.<br>
> ><br>
> > To unsubscribe visit <a href="https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvXS0EXvM$">
https://urldefense.com/v3/__https://lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvXS0EXvM$</a> .<br>
> ><br>
> > Kea-users mailing list<br>
> > Kea-users@lists.isc.org<br>
> > <a href="https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvXS0EXvM$">
https://urldefense.com/v3/__https://lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!yteZar1VMg4V2QncUrW9qHJR12Fao76aOPAzxE4bRwaXFdrveqPfJanYcIlzufpSJtigEMc_AtWEvXS0EXvM$</a><br>
-- <br>
ISC funds the development of this software with paid support subscriptions. Contact us at
<a href="https://urldefense.com/v3/__https:/www.isc.org/contact/__;!!Hit2Ag!zYf21dDIQNcAF6xDwkGGjmHCI7R_PeM__xtOhpG1x8Uu7R2N95aufWvO8-tvevlBdEJ4PPD7U_xYHuGVs7jO$">
https://urldefense.com/v3/__https://www.isc.org/contact/__;!!Hit2Ag!zYf21dDIQNcAF6xDwkGGjmHCI7R_PeM__xtOhpG1x8Uu7R2N95aufWvO8-tvevlBdEJ4PPD7U_xYHuGVs7jO$</a> for more information.<br>
<br>
To unsubscribe visit <a href="https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!zYf21dDIQNcAF6xDwkGGjmHCI7R_PeM__xtOhpG1x8Uu7R2N95aufWvO8-tvevlBdEJ4PPD7U_xYHns6h9X9$">
https://urldefense.com/v3/__https://lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!zYf21dDIQNcAF6xDwkGGjmHCI7R_PeM__xtOhpG1x8Uu7R2N95aufWvO8-tvevlBdEJ4PPD7U_xYHns6h9X9$</a> .<br>
<br>
Kea-users mailing list<br>
Kea-users@lists.isc.org<br>
<a href="https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!zYf21dDIQNcAF6xDwkGGjmHCI7R_PeM__xtOhpG1x8Uu7R2N95aufWvO8-tvevlBdEJ4PPD7U_xYHns6h9X9$">https://urldefense.com/v3/__https://lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!zYf21dDIQNcAF6xDwkGGjmHCI7R_PeM__xtOhpG1x8Uu7R2N95aufWvO8-tvevlBdEJ4PPD7U_xYHns6h9X9$</a>
<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>