<div dir="ltr">Hey Ismael, <br><br>So what you are seeing here is the subnet is being defined as only available for a specific client-class:<br><br>"pools": [ { "pool": "1.2.3.2 - 1.2.3.254", "client-class": "HA_server1" } ],<br><br>This means (as far as I understand) that specific pool in that subnet will only be offered to dhcp requests that are tagged with that HA_server1 client-class. So unless you have a host-reservation defined somewhere that associates your dhcp request with that "HA_server1" client-class that pool you've set up will not be available for your request. <br><br>Client classes are great for allowing you better access control to your subnet pools, but with your original config they'll block your requests unless you are setting those classes in a host reservation:<div><a href="https://kea.readthedocs.io/en/latest/arm/classify.html">https://kea.readthedocs.io/en/latest/arm/classify.html</a></div><div><br></div><div>Here's the ISC provided example I ended up using to set up reservations for my subnets:</div><div><a href="https://kea.readthedocs.io/en/latest/arm/dhcp4-srv.html#reserving-client-classes-in-dhcpv4">https://kea.readthedocs.io/en/latest/arm/dhcp4-srv.html#reserving-client-classes-in-dhcpv4</a><br></div><div><br></div><div>Hope that helps shed some light on how that works. Nice work troubleshooting your way down to the issue. </div><div><br></div><div>All the best,</div><div>Conor Mullen </div><div><br><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jul 6, 2020 at 8:34 AM Ismael Suarez <<a href="mailto:Ismael_Suarez@coqui.com">Ismael_Suarez@coqui.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Turns out, one I removed the following from each subnet (just did them all at once) it started giving out leases.<br>
"client-class": "HA_server1"<br>
This will not be used in cluster for now, so I can manage. But really don't understat why it was not working before. Any setting I am missing where it was hitting a default threshold?<br>
<br>
Kind of bumbed out not finding the culprit of my problem.<br>
<br>
The setting I am testing out has over 130 subnets looking like the following (not real IPs here)<br>
<br>
<br>
NOT WORKING<br>
{<br>
"subnet": "<a href="http://1.2.3.4/18" rel="noreferrer" target="_blank">1.2.3.4/18</a>",<br>
"id": 1008,<br>
"pools": [ { "pool": "1.2.3.2 - 1.2.3.254", "client-class": "HA_server1" } ],<br>
"option-data": [ { "name": "routers", "data": "1.2.3.1" } ]<br>
},<br>
<br>
<br>
WORKING<br>
{<br>
"subnet": "<a href="http://1.2.3.0/18" rel="noreferrer" target="_blank">1.2.3.0/18</a>",<br>
"id": 1008,<br>
"pools": [ { "pool": "1.2.3.2 - 1.2.3.254" } ],<br>
"option-data": [ { "name": "routers", "data": "1.2.3.1" } ]<br>
},<br>
<br>
<br>
NOTE: HA hook is not in use (commented).<br>
<br>
--<br>
<br>
Ism<br>
<br>
<br>
-----Original Message-----<br>
From: Joshua Schaeffer <<a href="mailto:jschaeffer@harmonywave.com" target="_blank">jschaeffer@harmonywave.com</a><mailto:<a href="mailto:Joshua%2520Schaeffer%2520%253cjschaeffer@harmonywave.com" target="_blank">Joshua%20Schaeffer%20%3cjschaeffer@harmonywave.com</a>%3e>><br>
To: <a href="mailto:kea-users@lists.isc.org" target="_blank">kea-users@lists.isc.org</a><mailto:<a href="mailto:kea-users@lists.isc.org" target="_blank">kea-users@lists.isc.org</a>><br>
Subject: Re: [Kea-users] ALLOC_ENGINE_V4_ALLOC_FAIL<br>
Date: Fri, 03 Jul 2020 17:25:15 -0600<br>
<br>
On 7/3/20 4:48 PM, Ismael Suarez wrote:<br>
<br>
Dont have ‘client-classes’ in my config. Not using reservations. Just simple subnets.<br>
<br>
<br>
Used to have it setup in HA but now don’t. Still have de HA_server1 for each subnet. Think that may be bothering somehow?<br>
<br>
<br>
I would recommend turning on DEBUG. You will get far more information as to why the allocation failed, or at least be able to rule out certain situations.<br>
<br>
--<br>
<br>
Thanks,<br>
<br>
Joshua Schaeffer<br>
<br>
_______________________________________________<br>
<br>
ISC funds the development of this software with paid support subscriptions. Contact us at <a href="https://www.isc.org/contact/" rel="noreferrer" target="_blank">https://www.isc.org/contact/</a> for more information.<br>
<br>
<br>
To unsubscribe visit <a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a>.<br>
<br>
<br>
Kea-users mailing list<br>
<br>
<a href="mailto:Kea-users@lists.isc.org" target="_blank">Kea-users@lists.isc.org</a><mailto:<a href="mailto:Kea-users@lists.isc.org" target="_blank">Kea-users@lists.isc.org</a>><br>
<br>
<a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a><br>
<br>
_______________________________________________<br>
ISC funds the development of this software with paid support subscriptions. Contact us at <a href="https://www.isc.org/contact/" rel="noreferrer" target="_blank">https://www.isc.org/contact/</a> for more information.<br>
<br>
To unsubscribe visit <a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a>.<br>
<br>
Kea-users mailing list<br>
<a href="mailto:Kea-users@lists.isc.org" target="_blank">Kea-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a><br>
</blockquote></div>