Re: [Kea-users] HA heartbeat communications failure

2023-12-27 Thread CS
Kea 2.4.0 On Wed, Dec 27, 2023, 03:18 Darren Ankney wrote: > Hi, > > If I may ask, what version of Kea are you using? Some defaults have > changed across versions. > > Thank you, > > Darren Ankney > > On Tue, Dec 26, 2023 at 4:31 PM CS wrote: > > > > >Please describe what you mean by "it

Re: [Kea-users] HA heartbeat communications failure

2023-12-27 Thread Darren Ankney
Hi, If I may ask, what version of Kea are you using? Some defaults have changed across versions. Thank you, Darren Ankney On Tue, Dec 26, 2023 at 4:31 PM CS wrote: > > >Please describe what you mean by "it doesn't work". > I mean I get a pretty useless error: "Unable to connect to Kea

Re: [Kea-users] HA heartbeat communications failure

2023-12-27 Thread CS
They made it through. With minor changes (ip addresses, library locations, and logging) the files are accepted and daemons are running but... no dice. server1$ tail -f /var/log/kea/kea-dhcp4.log 2023-12-27 22:24:48.486 INFO [kea-dhcp4.dhcpsrv/1495687] DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading

Re: [Kea-users] HA heartbeat communications failure

2023-12-27 Thread Thijs Blok
Hi, Your control agent needs to run on the same port as the HA configuration parameters. Please make sure you don't listen on the localhost only which is the default for the control agent. "Control-agent": { "http-host": "x.x.x.x", "http-port": 8000, Micetro is not using port

Re: [Kea-users] HA heartbeat communications failure

2023-12-27 Thread Darren Ankney
Hi, See attached four files: ca-server1.json (config for kea-ctrl-agent) ca-server2.json (config for kea-ctrl-agent) dhcp4-server1.json (config for kea-dhcp4) dhcp4-server2.json (config for kea-dhcp4) These files use port 8000 for kea-ctrl-agent and 8001 for kea-dhcp4 on version 2.4.0. They

Re: [Kea-users] HA heartbeat communications failure

2023-12-27 Thread CS
telneting around it appears server1 can reach 8001 on itself but not 2. server 2 can telnet 8001 on server 1 but not itself. I see nothing logged that indicates a conflict tho and both of these besides being on different subnets these servers are virtually identical and firewall free. CS,