- tweak your DNS option to match your actual network
+ - the path to the hook libraries. This is very OS specific parameter. The library names are in
+ general the same everywhere, but the path varies.
+
3. If using firewall, make sure the server1 can reach the server2. A nice way to ensure that is to
try to retrieve server2's config from the server1:
// HA requires two hooks libraries to be loaded: libdhcp_lease_cmds.so and
// libdhcp_ha.so. The former handles incoming lease updates from the HA peers.
- // The latter implements high availability feature for Kea.
+ // The latter implements high availability feature for Kea. Note the library name
+ // should be the same, but the path is OS specific.
"hooks-libraries": [
// The lease_cmds library must be loaded because HA makes use of it to
// deliver lease updates to the server as well as synchronize the
// HA requires two hooks libraries to be loaded: libdhcp_lease_cmds.so and
// libdhcp_ha.so. The former handles incoming lease updates from the HA peers.
- // The latter implements high availability feature for Kea.
+ // The latter implements high availability feature for Kea. Note the library name
+ // should be the same, but the path is OS specific.
"hooks-libraries": [
// The lease_cmds library must be loaded because HA makes use of it to
// deliver lease updates to the server as well as synchronize the