I don't know your configurations, so I couldn't reproduce your exact
situation. However, I tried adding a new subnet to Kea after having some
subnets already populated to Stork. The new subnet appeared in Stork
without any issues.
I'd start investigating your problem with examining the Stork server
logs from the time when the Kea configuration has been updated to see if
it reported any problems with the fetched subnet.
You could also navigate to Services -> Kea Apps, then select the server
where your subnet is configured in the Status column. Next, click `Raw
Configuration` and check whether or not the new subnet is visible in the
JSON tree.
Kind Regards,
Marcin Siodelski
ISC
On 4.09.2023 22:30, Apu wrote:
kea 2.4.0 and stork 1.12.0
kea-dhcp4 -t /etc/kea/kea-dhcp4.conf shows my original six subnets
(subnet IDs 171, 172, 173, 174, 175 & 176, all of which are /19s taken
from 10.17.x.x), as well as the new subnet (id 16, the whole 10.16.0.0/24).
Kea is handing out IP addresses in the new subnet and Grafana shows IP
addresses assigned in that new subnet's pool.
But Stork shows nothing about the subnet. I've tried restarting each
service as well as the whole server but still do not see the new subnet
in Stork.
Thoughts on what I am missing?
Thanks,
--
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
Kea-users mailing list
Kea-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/kea-users
