Are you sure you want to migrate host reservations to the database?

You are about to migrate host reservations defined in a configuration file to a database ("host backend"). After the migration, hosts will be deleted from your configuration file and will be kept in the database only. All the hosts selected by the current filter (including those on other pages, if there are more hosts than fit on a single page) will be considered. Those that can't be migrated (e.g. because they're already in a database or are in a conflicted state) will be skipped. The migration is not instantaneous and will take some time.

The number of hosts to be migrated is {{ totalRecords }}. They are selected by the following filter:

{{ entry[0] }} {{ entry[1] }}

This operation will lock the related daemons for modifications. During the migration, the Stork server will not synchronize the Kea data (i.e., the Kea configuration, subnets, shared networks, host reservations).

The migration can be canceled at any time.

{{ err }}
Filters

Hosts in the table below can be filtered by entering text in the search box; the table shows all hosts matching the filter text. The currently supported fields for filtering are:

  • Identifier
  • Identifier Type
  • Address
  • Hostname

Hosts can be filtered by their identifier value, e.g. 00:01:02:03:04:05; a part of the identifier (e.g. the initial three bytes of a MAC address that denotes OUI, a unique identifier of the vendor, effectively showing all devices produced by the same vendor); or identifier type (e.g. hw-address to show all reservations made by a MAC address).

Hosts can be also filtered by a full or partial IP address. For example, all reservations in a 192.0.2.0/24 subnet can found by entering 192.0.2 as the filter text.

The Global checkbox allows users to see global hosts (i.e. the hosts valid for all subnets), hosts associated with specific subnets, or all hosts. When the box is clicked once, the results show all DHCP identifiers set at the global level; when clicked a second time, it excludes the global hosts and shows only hosts that are associated with defined subnets.

Hosts with inconsistent DHCP configurations can be filtered using the Conflict checkbox. When the box is clicked once, the filter returns all hosts whose configurations contain conflicts between the configuration file and host database. When clicked a second time, the results exclude any hosts with configuration conflicts.

In addition, hosts can be filtered by an explicitly selected field using text input filters. The currently supported fields for explicit filtering are:

  • Kea App ID - the ID of the Kea App used by Stork.
  • Subnet ID - the subnet ID used by Stork.
  • Kea Subnet ID - the subnet ID assigned to the subnet in the Kea configuration.

Hosts can be filtered by multiple fields. Currently, all provided filtering conditions are joined using a logical AND.

Global
Conflict
DHCP Identifiers IP Addresses IPv6 Prefixes Hostname Global/Subnet App Name No hosts found. Clear filtering and try again. {{ h.hostname }} global Total: {{ paginatorState.totalRecords | pluralize: 'host' }} No hosts found. Clear filtering and try again.