<html><head><title>Re: Using OMAPI to release a DHCP lease on a failover pair</title>
<meta charset="utf-8" http-equiv="X-UA-Compatible" content="IE=9; IE=8; IE=7; IE=EDGE" />
</head>
<body>
<span style=" font-family:'Courier New'; font-size: 9pt;">I've been messing with this recently - OMSHell, not releasing leases - and IIRC [and I may well not, but take it for what it's worth]...<br>
you have to expire the lease and then release it.<br>
<br>
You can't go from an active lease to released in one step.<br>
<br>
I think there are some details in the list that I recall reading recently - which is why I *vaguely* know. :)<br>
<br>
HTH<br>
-Greg<br>
<br>
<span style=" color: #800000;"><b>IO> Hello,<br>
<br>
IO> I am having some issues getting the OMAPI method for setting a lease to the<br>
IO> released state to work, in order to allow a new client to get the lease. The<br>
IO> servers in question are in a failover pair. The guidance that I have seen<br>
IO> recommends to do the following to manually release a lease on the server<br>
IO> side via OMAPI:<br>
<br>
IO> server x.x.x.x<br>
IO> port 7911<br>
IO> key omapi_key (key)<br>
IO> connect<br>
IO> new lease<br>
IO> set ip-address = 1.1.1.1<br>
IO> open<br>
IO> set state = 4<br>
IO> update<br>
<br>
IO> In this case, the pool contains only a single address, and it doesn't seem<br>
IO> to work whether I make the change on the just the primary or both the<br>
IO> primary and secondary. In either case, I get the following logs (with the<br>
IO> exception of the state change on the secondary when I have tried not making<br>
IO> any change there):<br>
<br>
IO> Primary:<br>
IO> Jul 30 14:02:54 loc3 dhcpd[25263]: lease 1.1.1.1 state changed from active<br>
IO> to released<br>
IO> Jul 30 14:02:58 loc3 dhcpd[25263]: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via<br>
IO> 1.1.1.0: network 1.1.1.0/31: no free leases<br>
IO> Jul 30 14:03:01 loc3 dhcpd[25263]: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via<br>
IO> 1.1.1.0: network 1.1.1.0/31: no free leases<br>
IO> Jul 30 14:03:04 loc3 dhcpd[25263]: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via<br>
IO> 1.1.1.0: network 1.1.1.0/31: no free leases<br>
IO> Jul 30 14:03:07 loc3 dhcpd[25263]: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via<br>
IO> 1.1.1.0: network 1.1.1.0/31: no free leases<br>
<br>
IO> Secondary:<br>
IO> Jul 30 14:02:55 loc36 dhcpd[19842]: lease 1.1.1.1 state changed from free to<br>
IO> released<br>
IO> Jul 30 14:02:58 loc36 dhcpd[19842]: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via<br>
IO> 1.1.1.0: peer holds all free leases<br>
IO> Jul 30 14:03:01 loc36 dhcpd[19842]: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via<br>
IO> 1.1.1.0: peer holds all free leases<br>
IO> Jul 30 14:03:04 loc36 dhcpd[19842]: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via<br>
IO> 1.1.1.0: peer holds all free leases<br>
IO> Jul 30 14:03:07 loc36 dhcpd[19842]: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via<br>
IO> 1.1.1.0: peer holds all free leases<br>
<br>
IO> The pre-existing lease was for a different MAC address than<br>
IO> aa:bb:cc:dd:ee:ff. The device with the old MAC address is still the only one<br>
IO> that is able to get a new lease, even after releasing that lease via OMAPI.<br>
IO> Any guidance on how to get this to work in this case would be appreciated. I<br>
IO> am not sure if the existence of the failover configuration is the cause of<br>
IO> the issue, or if there is another reason for this behavior, but there don't<br>
IO> seem to be any errors or any other info returned by OMAPI which indicate why<br>
IO> this might be happening.<br>
<br>
IO> Thanks,<br>
IO> Isaiah<br>
<br>
IO> _______________________________________________<br>
IO> ISC funds the development of this software with paid support<br>
IO> subscriptions. Contact us at </b></span></span><a style=" font-family:'courier new'; font-size: 9pt;" href="https://www.isc.org/contact/">https://www.isc.org/contact/</a><span style=" font-family:'courier new'; font-size: 9pt; color: #800000;"><b> for more information.<br>
<br>
IO> dhcp-users mailing list<br>
</b></span><a style=" font-family:'courier new'; font-size: 9pt;" href="mailto:dhcp-users@lists.isc.org">IO> dhcp-users@lists.isc.org</a><br>
<a style=" font-family:'courier new'; font-size: 9pt;" href="https://lists.isc.org/mailman/listinfo/dhcp-users">IO> https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
<br>
<span style=" font-family:'arial'; color: #c0c0c0;"><i>--<br>
Gregory Sloop, Principal: Sloop Network & Computer Consulting<br>
Voice: 503.251.0452 x121<br>
EMail: </i></span><a style=" font-family:'arial';" href="mailto:gregs@sloop.net">gregs@sloop.net</a><br>
<a style=" font-family:'arial';" href="http://www.sloop.net">http://www.sloop.net</a><br>
<span style=" font-family:'arial'; color: #c0c0c0;"><i>---</body></html>