diff options
| author | Marcin Siodelski <marcin@isc.org> | 2024-01-05 15:38:57 +0100 |
|---|---|---|
| committer | Marcin Siodelski <marcin@isc.org> | 2024-01-05 19:04:19 +0100 |
| commit | 745eff0a0cef8fc7779ee5ec8f90027a5aacf640 (patch) | |
| tree | e727bf5548af5c3334e5b5decd9d2d6f89c8cbc4 /doc/sphinx | |
| parent | [#3178] Added ChangeLog for #3178 (diff) | |
| download | kea-745eff0a0cef8fc7779ee5ec8f90027a5aacf640.tar.xz kea-745eff0a0cef8fc7779ee5ec8f90027a5aacf640.zip | |
[#3178] Small ARM edits after review
Diffstat (limited to 'doc/sphinx')
| -rw-r--r-- | doc/sphinx/arm/hooks-ha.rst | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/sphinx/arm/hooks-ha.rst b/doc/sphinx/arm/hooks-ha.rst index 15e56564f1..155e0f64d0 100644 --- a/doc/sphinx/arm/hooks-ha.rst +++ b/doc/sphinx/arm/hooks-ha.rst @@ -2579,7 +2579,8 @@ can be any of the peer names in the relationship. Suppose a relationship contain ``server2``. In both cases, it associates a subnet with that relationship. It is not required to specify the ``ha-server-name`` in the branch servers, assuming that the -branch servers only contain the subnets they serve. Consider the following configuration. +branch servers only contain the subnets they serve. Consider the following configuration for +branch ``server3``: .. code-block:: json @@ -2646,7 +2647,7 @@ branch servers only contain the subnets they serve. Consider the following confi .. note:: Even though it is not required to include the ``ha-server-name`` user context parameters in the - branch servers, we recommend including them nevertheless. The servers fetch all leases from the + branch servers, we recommend including them. The servers fetch all leases from the partners during the database synchronization. If the subnets are not explicitly associated with the relationship, the branch server inserts all fetched leases from the central server (including those from other relationships) into its database. Specifying ``ha-server-name`` parameter for |