<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
<br><div>> > > The second lease entry had an "atsfp" entry added to it; which I<br>> >> seem to recall is related to failover.<br>> <br>> >So if it's normal, and like in memory the DHCPd had 2 lease for the <br>> >same IP and MAC (tested via omshell), how can i use OMAPI/omshell to <br>> >get a lease in this condition?<br>> <br>> Are you using failover ? If so, then first thing would be to upgrade. <br>> 3.1.3 is very old and I think you'll find the release notes for later <br>> versions make mentions of bug fixes and improvements related to <br>> failover.<br>> <br><br><br>
I just was able to found release notes to these versions on site (there are more?):<br>
DHCP 4.2<br>
DHCP 4.1-ESV-R3<br>
<br>
Found:<br>
Client lease records are recorded at most once every 15 seconds.
This keeps the client from filling the lease database disk quickly on
very small lease times. [ISC-Bugs #19660]<br>
and<br>
[ISC-Bugs #19615] update the includes in dhcpctl/dhcpctl.3 to be more correct<br>
<br><br><br>The second one is to vague but the first one is related to the memory dump to dhcp.leases file right? I m testing some code that i have done that uses OMAPI and i tested it in home with dhcpd 4.1 (no failover) and i never face this behavior (more than one lease with the same IP and MAC). Now i m testing my code in a real network infra-structure (more traffic) that as the V3.1.3 with failover, but i m not the owner or responsible for the network so i can't upgrade :(<br><br><br>it could be due the fact that in V4.1.2 the dump/clean of leases in memory is done more often (15 seconds) then in V3.1.3 (don't know the time)? and so its more unlikely to catch such situation?<br> <br>Do you have any other idea?<br><br>Thanks!<br><br><br>
<br></div> </div></body>
</html>