The following rules apply when you make changes to Kea DHCP servers in High Availability setups outside of Micetro.
Note: Any changes made to the configuration file through Micetro are
instantly and automatically propagated to secondary/backup servers in a Kea DHCP High
Availability setup. For immediate synchronization between Micetro and Kea DHCP servers,
it is highly recommended to exclusively edit the configuration file through
Micetro.
- Primary server
- Similar to the standalone server, Micetro synchronizes external changes on the primary Kea server according to a predefined schedule. Automatic propagation of changes to secondary/backup servers occurs only when the servers transition out of and then back into an Active state. To manually propagate the changes, you must make a change (any change) to the configuration through a Micetro feature, initiating a synchronization process.
- Secondary server(s)
- The same rules apply to managing changes in the configuration and the
config-reloadcommand on secondary servers. However, Micetro will prioritize the current in-memory configuration of the primary Kea DHCP server in the High Availability setup, overwriting any external changes.