[Kea-users] Configure a subnet in Kea configuration backend
Brian Candler
b.candler at pobox.com
Thu Dec 5 11:41:53 UTC 2019
You can run the queries by hand to see if they return zero results or
not. The most interesting one might be this:
> SELECT s.subnet_id, s.subnet_prefix, s.4o6_interface, s.4o6_interface_id, s.4o6_subnet, s.boot_file_name, s.client_class, s.interface, s.match_client_id, s.modification_ts, s.next_server, s.rebind_timer, s.relay, s.renew_timer, s.require_client_classes, s.reservation_mode, s.server_hostname, s.shared_network_name, s.user_context, s.valid_lifetime, p.id, p.start_address, p.end_address, p.subnet_id, p.modification_ts, x.option_id, x.code, x.value, x.formatted_value, x.space, x.persistent, x.dhcp4_subnet_id, x.scope_id, x.user_context, x.shared_network_name, x.pool_id, x.modification_ts, o.option_id, o.code, o.value, o.formatted_value, o.space, o.persistent, o.dhcp4_subnet_id, o.scope_id, o.user_context, o.shared_network_name, o.pool_id, o.modification_ts, s.calculate_tee_times, s.t1_percent, s.t2_percent, s.authoritative, s.min_valid_lifetime, s.max_valid_lifetime, p.client_class, p.require_client_classes, p.user_context, srv.tag FROM dhcp4_subnet AS s INNER JOIN dhcp4_subnet_server AS a ON s.subnet_id = a.subnet_id INNER JOIN dhcp4_server AS srv ON (a.server_id = srv.id) LEFT JOIN dhcp4_pool AS p ON s.subnet_id = p.subnet_id LEFT JOIN dhcp4_options AS x ON x.scope_id = 5 AND p.id = x.pool_id LEFT JOIN dhcp4_options AS o ON o.scope_id = 1 AND s.subnet_id = o.dhcp4_subnet_id WHERE s.modification_ts > ? ORDER BY s.subnet_id, p.id, x.option_id, o.option_id
Replace "?" with date 1970-01-01. If you get zero rows, then you can
dig down to see why it's not finding the subnets.
However, that's a "Prepare" and I don't see it being executed. These are
the only ones I see executed:
$ grep -v Prepare mysql-log.txt
1059 Query SET SESSION wait_timeout = 30 * 86400
1059 Query SET SESSION sql_mode ='STRICT_ALL_TABLES'
1059 Query set autocommit=1
191205 11:21:53 1059 Execute SELECT address, hwaddr, client_id,
valid_lifetime, expire, subnet_id, fqdn_fwd, fqdn_rev, hostname, state,
user_context FROM lease4 WHERE state != 2 AND expire <
TIMESTAMP'2019-12-05 11:32:31' ORDER BY expire ASC LIMIT 101
191205 11:22:03 1059 Execute SELECT address, hwaddr, client_id,
valid_lifetime, expire, subnet_id, fqdn_fwd, fqdn_rev, hostname, state,
user_context FROM lease4 WHERE state != 2 AND expire <
TIMESTAMP'2019-12-05 11:32:41' ORDER BY expire ASC LIMIT 101
191205 11:22:08 1059 Execute DELETE FROM lease4 WHERE state = 2
AND expire < TIMESTAMP'2019-12-05 10:32:46'
Odd. Oh well, good luck with further digging. It might also help to
crank up Kea's logging to maximum (debuglevel 99) if you haven't done so
already:
"Logging":
{
"loggers": [
{
"name": "kea-dhcp4",
"output_options": [
{
"output": "stdout",
"pattern": "%-5p %m\n"
}
],
"severity": "DEBUG",
"debuglevel": 99
}
]
}
Regards,
Brian.
More information about the Kea-users
mailing list