... | ... | @@ -120,7 +120,7 @@ The filtering box placed above the list of host reservations can be used to sear |
|
|
|
|
|
The reservations observed in the previous step were only those that are specified within the Kea configuration files. Kea also supports defining host reservations within a database via `host_cmds` premium hooks library. Those reservations are available in the same view as previously. They are fetched when the Kea app is configured to use `host_cmds` hooks library. The demo setup optionally includes such machine if the demo is started with the `cs_repo_access_token` variable.
|
|
|
|
|
|
In order to see the reservations stored in the host database on this machine, start monitoring this machine by adding it to Stork. The machine name is `agent-kea-hosts`. Stork is currently configured to fetch and refresh the reservations from the hosts backend at the 60 seconds interval. Thus, you may need to wait a little while before the host reservations appear on the list. If the fetch is successful, you should observe new IPv4 reservations starting with IP address of 192.0.2.200 and higher.
|
|
|
In order to see the reservations stored in the host database on this machine, start monitoring this machine by adding it to Stork. The machine name is `agent-kea-premium`. Stork is currently configured to fetch and refresh the reservations from the hosts backend at the 60 seconds interval. Thus, you may need to wait a little while before the host reservations appear on the list. If the fetch is successful, you should observe new IPv4 reservations starting with IP address of 192.0.2.200 and higher.
|
|
|
|
|
|
## 14. DHCP Dashboard
|
|
|
|
... | ... | |