<html xmlns:v="urn:schemas-microsoft-com:vml" 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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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.EmailStyle20
{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 experts,<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 modified the config file on both DHCP VMs, and reversed their roles, now kea2 as primary and kea1 as standby. But I can see still the leases are provided by kea1. I did the packet capture on both hosts.<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">As we can see, both hosts have received the DHCPv6 Solicit packet from client which has the link local address as fe80::c40b:ebff:fed1:7298, but kea2 immediately did the address resolution process, and then
sent the Advertise packet, while even kea2 is the primary host now, it just doesn’t respond to the coming Solicit packet from client.
<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">How should I troubleshoot why kea2 didn’t respond to the Solicit packet from the client? Can I have an example?
<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">Kea1:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><img width="1359" height="261" style="width:14.1562in;height:2.7187in" id="Picture_x0020_1" src="cid:image001.png@01DA810F.00DD3300"></span><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"><span style="font-size:11.0pt">Kea2:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><img width="1359" height="253" style="width:14.1562in;height:2.6354in" id="Picture_x0020_2" src="cid:image002.png@01DA810F.24AC5FE0"></span><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"><span style="font-size:11.0pt">Link local Ips:<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">client<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">fe80::c40b:ebff:fed1:7298<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">kea1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">fe80::40f1:11ff:fe7a:de7<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Kea2<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">fe80::a8ca:adff:feb9:5db6<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>
<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 Xiao, Yu (CCI-Atlanta) via Kea-users <kea-users@lists.isc.org><br>
<b>Date: </b>Tuesday, March 26, 2024 at 7:58</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 user's list <kea-users@lists.isc.org><br>
<b>Cc: </b>Xiao, Yu (CCI-Atlanta) <yu.xiao@cox.com><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 Darren,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I am using 2.4.1. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best Regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Yu</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></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>Tuesday, March 26, 2024 at 6:03</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 user's list <kea-users@lists.isc.org><br>
<b>Subject: </b>[EXTERNAL] Re: [Kea-users] kea-2.4.1 // Strange HA related errors</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">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>
</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>