2
0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-08-28 12:37:55 +00:00

[#2139] Additional text edits (still interim save through line 996)

This commit is contained in:
Suzanne Goldlust 2021-11-09 22:37:42 +00:00 committed by Thomas Markwalder
parent 98646b0822
commit 0dbb77fc5c

View File

@ -182,10 +182,10 @@ clocks and restart the servers.
.. note:: .. note::
Prior to Kea 1.7.8, to recover from the terminated Prior to Kea 1.7.8, to recover from the terminated
state, the administrator had to shut down both servers and then start state, the administrator had to shut down both servers and then restart
both of them. Since Kea 1.7.8, it is possible to restart the both of them. Since Kea 1.7.8, it is possible to restart the
servers sequentially, i.e. restart one server and then restart the other servers one at a time, in sequence. The clocks must be in sync
one. The clocks must be in sync before restarting the servers. before restarting the servers.
.. note:: .. note::
@ -660,8 +660,9 @@ behavior with respect to HA:
``communication-recovery`` state. This parameter was introduced in ``communication-recovery`` state. This parameter was introduced in
Kea 1.9.4. The special value of 0 configures the server to Kea 1.9.4. The special value of 0 configures the server to
never transition to the ``communication-recovery`` state and the never transition to the ``communication-recovery`` state and the
server behaves as in earlier Kea versions. The default value of this server behaves as in earlier Kea versions, i.e. if the server
parameter is 100. cannot reach its partner, it goes straight into the ``partner-down`` state.
The default value of this parameter is 100.
The values of ``max-ack-delay`` and ``max-unacked-clients`` must be The values of ``max-ack-delay`` and ``max-unacked-clients`` must be
selected carefully, taking into account the specifics of the network in selected carefully, taking into account the specifics of the network in