From: Thomas Markwalder Date: Wed, 17 Jun 2026 18:54:05 +0000 (-0400) Subject: [#4362] Updated HA section with a note X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=8ca7d89e799bd03e3c224ee71ab5545604a78e09;p=thirdparty%2Fkea.git [#4362] Updated HA section with a note modified: doc/sphinx/arm/hooks-ha.rst --- diff --git a/doc/sphinx/arm/hooks-ha.rst b/doc/sphinx/arm/hooks-ha.rst index 3c5e682293..07b3c22588 100644 --- a/doc/sphinx/arm/hooks-ha.rst +++ b/doc/sphinx/arm/hooks-ha.rst @@ -2463,6 +2463,22 @@ can be any of the peer names in the relationship. For example, if a relationship ``server1`` and ``server2``, it does not matter whether the ``ha-server-name`` is ``server1`` or ``server2``. In both cases, it associates a subnet with that relationship. +It is important to note that each relationship on a given Kea server must use a unique +listener IP.port combination as the relationships do not share listener pools between them. +If the same IP and port are defined for multiple relationships, the Kea service will fail to start with an error something like: DHCP4_INIT_FAIL failed to initialize Kea server: configuration error using file 'kea-dhcp4.conf': Error initializing hooks: CmdHttpListener::run failed: unable to setup TCP acceptor for listening to the incoming HTTP requests: bind: Address already in use + +.. note:: + + It is important to note that each peer on a given Kea server must use a unique a listener + IP/port combination. If the same IP and port are defined for multiple peers, the Kea service + will fail to start with an error similar to the following: + + .. code:: + + DHCP4_INIT_FAIL failed to initialize Kea server: configuration error using file 'kea-dhcp4.conf': + Error initializing hooks: CmdHttpListener::run failed: unable to setup TCP acceptor for listening + to the incoming HTTP requests: bind: Address already in use + 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 for branch ``server3``: