[Kea-users] Configuring HA with multiple interfaces on both the appliances
Kraishak Mahtha
kraishak.edu at gmail.com
Thu Oct 19 06:52:01 UTC 2023
Hi,
yes I have to use the URL directive for sure, I am in sync with that. the
only doubt was when we have multiple interfaces like eth0, eth1, and eth2
and I want kea-dhcp listening only on the eth1 and eth2 interface which IP
should I need to use in URL directive
Should be able to use any one of the addresses you have for that server.
----> Yes I am also thinking the same way that I will be using eth0 IP
address in URL directive by default, but just want to confirm is that a
correct way of proceeding?
On Wed, Oct 18, 2023 at 11:47 PM Rick Frey <gribnut at gmail.com> wrote:
> In reading
> https://kea.readthedocs.io/en/kea-2.4.0/arm/hooks.html#multi-threaded-configuration-ha-mt,
> you still configure the “url” directive of the HA hook with single URL for
> control commands even when using HA+MT mode with http-dedicated-listener
> = true. Thus the URL would need to be pointed to an IP address (or
> hostname that resolves) of that server and is routable between the two HA
> nodes. I’ve not used Kea in with http-dedicated-listener, but assuming
> you can use any IP address on the host. Should be able to use any one of
> addresses you have for that server.
>
> Not sure I understand your question. Are you concerned if using an URL w/
> single IP address, that the address or interface may fail on the server?
>
>
>
>
> On Oct 18, 2023, at 10:15 AM, Kraishak Mahtha <kraishak.edu at gmail.com>
> wrote:
>
> Hi Rick,
>
> Thanks for your response and explanation but I a using the kea-dhcp with
> (HA + MT) mode hence I will be not using the kea-control agent in my
> regular use case, so the IPs for the URLs will be of interface IP address
> but as said if we have different listening interfaces ......I am a bit
> confused about the configuration.
>
> Thanks
> Kraishak
>
> On Mon, Oct 16, 2023 at 9:09 PM Rick Frey <gribnut at gmail.com> wrote:
>
>> You can have different number of listening interfaces for HA pair
>> (assuming they are able to receive requests for all subnets). The “url”
>> directive in the HA hook configuration is for the Control-Agent (CA). The
>> addr/port of the Control-Agent is independent of the DHCP4 server and is
>> specified in its config (kea-ctrl-agent.conf). The address for the
>> Control-Agent can be different than address(es) you configure for the DHCP4
>> server.
>>
>> On Oct 16, 2023, at 8:37 AM, Kraishak Mahtha <kraishak.edu at gmail.com>
>> wrote:
>>
>> Hi all,
>>
>> Re-sending the mail once again to check if anyone is familiar with this
>> case, and can guide me.
>>
>> On Tue, Oct 3, 2023 at 12:32 PM Kraishak Mahtha <kraishak.edu at gmail.com>
>> wrote:
>>
>>> Hi all,
>>> I have a few doubts in a case where we have multiple interfaces
>>> listening in the kea dhcp and configured in HA/Failover mode.
>>> For instance: I have server A with four interfaces
>>> eth0 (192.168.0.51), eth1 (192.168.0.52), eth2 (192.168.0.53), eth3
>>> (192.168.0.54) and server B I have three interfaces
>>> eth1(192.168.0.61), eth2(192.168.0.62), eth2(192.168.0.63).
>>>
>>> Case 1) Can we define failover configuration with servers A and B
>>> specifying server A listening on three interfaces and server B listening on
>>> two interfaces? (no same number of interfaces on both appliances).
>>>
>>> Case 2) When we have such a configuration how do we deal with the
>>> failover configuration where we specify only one IP?
>>> "peers": [
>>> {
>>> "role": "primary",
>>> "name": "dhcp1",
>>> "auto-failover": true,
>>> "url": "http://192.168.0.51:8001"
>>> },
>>> {
>>> "role": "secondary",
>>> "name": "dhcp2",
>>> "auto-failover": true,
>>> "url": "http://192.168.0.61:8001"
>>> }
>>> ],
>>> Should we specify all the listening interface IP's in the failover
>>> section?
>>>
>>> Can someone who is familiar with such setups and has faced similar
>>> issues guide me?
>>>
>>> Thanks in Advance
>>> Kraishak
>>>
>>>
>>> --
>> ISC funds the development of this software with paid support
>> subscriptions. Contact us at https://www.isc.org/contact/ for more
>> information.
>>
>> To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
>>
>> Kea-users mailing list
>> Kea-users at lists.isc.org
>> https://lists.isc.org/mailman/listinfo/kea-users
>>
>>
>> --
>> ISC funds the development of this software with paid support
>> subscriptions. Contact us at https://www.isc.org/contact/ for more
>> information.
>>
>> To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
>>
>> Kea-users mailing list
>> Kea-users at lists.isc.org
>> https://lists.isc.org/mailman/listinfo/kea-users
>>
>
> --
> ISC funds the development of this software with paid support
> subscriptions. Contact us at https://www.isc.org/contact/ for more
> information.
>
> To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
>
> Kea-users mailing list
> Kea-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20231019/5b88629b/attachment-0001.htm>
More information about the Kea-users
mailing list