[Kea-users] kea-dhcp4 1.4.0-P1 HA features

Ivan Stenda jaivast at gmail.com
Thu Sep 13 12:09:34 UTC 2018


Hello Marcin,

what I see on working host is:

2018-09-13 13:52:53.079 WARN  [kea-dhcp4.ha-hooks/2558]
HA_LEASE_UPDATE_COMMUNICATIONS_FAILED [hwtype=1 08:3e:5d:10:53:54], cid=[no
info], tid=0x70b576d2: failed to communicate with dhcp-12 (
http://10.58.0.12:8080/): Connection refused
2018-09-13 13:52:53.789 WARN  [kea-dhcp4.ha-hooks/2558]
HA_HEARTBEAT_COMMUNICATIONS_FAILED failed to send heartbeat to dhcp-12 (
http://10.58.0.12:8080/): Connection refused
2018-09-13 13:52:54.820 WARN  [kea-dhcp4.ha-hooks/2558]
HA_HEARTBEAT_COMMUNICATIONS_FAILED failed to send heartbeat to dhcp-12 (
http://10.58.0.12:8080/): Connection refused
2018-09-13 13:52:55.957 WARN  [kea-dhcp4.ha-hooks/2558]
HA_HEARTBEAT_COMMUNICATIONS_FAILED failed to send heartbeat to dhcp-12 (
http://10.58.0.12:8080/): Connection refused
2018-09-13 13:52:55.957 INFO  [kea-dhcp4.ha-hooks/2558] HA_STATE_TRANSITION
server transitions from LOAD-BALANCING to PARTNER-DOWN state, partner state
is UNDEFINED
2018-09-13 13:52:55.957 INFO  [kea-dhcp4.ha-hooks/2558]
HA_LEASE_UPDATES_DISABLED lease updates will not be sent to the partner
while in PARTNER-DOWN state

and can confirm that OFFERs are not send out  from working host.


configuration  snippets here:
{
    "interfaces-config": {
        "interfaces": [ "ens192" ],
        "dhcp-socket-type": "udp"
    },

{
            "subnet": "10.187.0.0/24",
            "pools": [
                {
                    "pool": "10.187.0.10 - 10.187.0.127"
                },
                {
                    "pool": "10.187.0.128 - 10.187.0.250"
                }
            ],

            "option-data": [
                {
                    "name": "routers",
                    "data": "10.187.0.1"
                }
            ]

        },

  "hooks-libraries": [
{
            "library": "/opt/kea/usr/lib/hooks/libdhcp_lease_cmds.so",
            "parameters": { }
        },
{
            "library": "/opt/kea/usr/lib/hooks/libdhcp_ha.so",
            "parameters": {
                "high-availability": [ {
                    "this-server-name": "dhcp-11",
                    "mode": "load-balancing",
                    "heartbeat-delay": 10,
                    //"max-response-delay": 10000,
                    "max-ack-delay": 5,
                    "max-unacked-clients": 5,
                    "peers": [
                        {
                            "name": "dhcp-11",
                            "url": "http://10.58.0.11:8080/",
                            "role": "primary",
                            "auto-failover": true
                        },
                        {
                            "name": "dhcp-12",
                            "url": "http://10.58.0.12:8080/",
                            "role": "secondary",
                            "auto-failover": true
                        }
                    ]
                } ]
            }
        }

  ]

},


regards
i

št 13. 9. 2018 o 13:23 Marcin Siodelski <marcin at isc.org> napísal(a):

> On 13.09.2018 09:03, Ivan Stenda wrote:
> > Hello guys,
> >
> > I am trying to set up HA on $subj with no luck. Managed peers to talk in
> > between via kea-ctrl-agent, lease updates send from host to host and
> > vice versa but on simulated failure clients are not served seamless.
> > They are doing whole DORA because working host does not send OFFER from
> > failed peer pool ...
> >
> > Maybe I am wrong about networking around KEA. Could someone guide me for
> > networking setup in case of UDP socket and relay hosts ?
> >
> > regards
> > i
> >
> >
> > _______________________________________________
> > Kea-users mailing list
> > Kea-users at lists.isc.org
> > https://lists.isc.org/mailman/listinfo/kea-users
> >
>
> Hello Ivan,
>
> It is hard to say without looking into configurations of both of your HA
> peers.
>
> I guess the first question is whether the server that takes over the
> traffic from the failed partner sends an OFFER (according to your logs)
> and this OFFER doesn't go through the network, or the OFFER is not
> generated by the server. Also, when you're expecting those offers do you
> observe the server which should send this offer being in the
> "partner-down" state (according to logs)?
>
> Marcin Siodelski
> ISC DHCP Engineering
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20180913/4080f289/attachment.htm>


More information about the Kea-users mailing list