[Kea-users] problems enabling HA Hot-Standby setup (OPEN)

Weisteen Per per.weisteen at telenor.no
Tue Mar 22 11:53:40 UTC 2022


Hi, I've set up a HA Hot-Standby config according to docs but I can't figure out why the servers doesn't listen on port 8000.
I thought that was the port configured for heartbeat. I'm a little confused and would be very happy if someone could explain how this is supposed to work ?

I'm running KEA on RHEL 8 servers installed from KEA 2.0 repo using yum install. 

My HA config for primary server (pls ignore any missing parentheses ad this is just an extract: 

"library": "/usr/lib64/kea/hooks/libdhcp_ha.so",
                "parameters": {
                        "high-availability": [{
                                "this-server-name": "tst-dhcp01",
                "mode": "hot-standby",
                "heartbeat-delay": 10000,
                "max-response-delay": 10000,
                "max-ack-delay": 5000,
                "max-unacked-clients": 5,
                                "multi-threading": {
                                        "enable-multi-threading": true,
                                        "http-dedicated-listener": true,
                                        "http-listener-threads": 4,
                                        "http-client-threads": 4
                },
                                "peers": [{
                    	"name": "tst-dhcp01",
                        	"url": "http://10.123.10.10:8000/",
                    	"role": "primary",
                            "auto-failover": true
                },{
                              "name": "tst-dhcp02",
                               "url": "http://10.123.20.20:8000/",
                               "role": "standby",
                               "auto-failover": true
                }] 

and for standby server:

"library": "/usr/lib64/kea/hooks/libdhcp_ha.so",
                "parameters": {
                "high-availability": [{
                                "this-server-name": "tst-dhcp02",
                                "mode": "hot-standby",
                                "heartbeat-delay": 10000,
                                "max-response-delay": 10000,
                                "max-ack-delay": 5000,
                                "max-unacked-clients": 5,
                                "multi-threading": {
                                        "enable-multi-threading": true,
                                        "http-dedicated-listener": true,
                                        "http-listener-threads": 4,
                                        "http-client-threads": 4
                                },
                        "peers": [{
                        "name": "tst-dhcp01",
                        "url": "http://10.123.10.10:8000/",
                        "role": "primary",
                                        "auto-failover": true
                        },{
                        "name": "tst-dhcp02",
                        "url": "http://10.123.20.20:8000/",
                        "role": "standby",
                                        "auto-failover": true
                                }] /* peers */
                        }] /* high-availability */
                }

Kea-debug.log shows :

HA_HEARTBEAT_COMMUNICATIONS_FAILED failed to send heartbeat to tst-dhcp02 (http://10.123.20.20:8000/): Connection refused
HA_COMMUNICATION_INTERRUPTED communication with tst-dhcp02 is interrupted

And similar on the standby server but differet IP-address and name of course.

./PerW



More information about the Kea-users mailing list