Send dhcp-users mailing list submissions to
        dhcp-users@lists.isc.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
        dhcp-users-requ...@lists.isc.org

You can reach the person managing the list at
        dhcp-users-ow...@lists.isc.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."


Today's Topics:

   1. Re: OMAPI Reservations and peer/failover (Gregory Sloop)
   2. Re: OMAPI Reservations and peer/failover (Gregory Sloop)
   3. dhcrelay prints these logs and doesn't live normally. [Can't
      initialize context: not enough free resources.] (???)


----------------------------------------------------------------------

Message: 1
Date: Thu, 27 May 2021 10:08:33 -0700
From: Gregory Sloop <gr...@sloop.net>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: OMAPI Reservations and peer/failover
Message-ID: <7445653.20210527100...@sloop.net>
Content-Type: text/plain; charset="iso-8859-15"

Anyone?
I kinda want to get this handled and off my plate, so I'm probably a little 
impatient. :)

Thanks again!



I finally got around to attempting to set the reservation flag on some dhcp 
leases using omapi.
(I'd asked about how to do this with OMAPI ages ago ... since I can do it live 
and not have to stop the DHCP servers and hand edit the leases file.)

I'm running a pair of peers/failover/load-balance machines for dhcp.

So, I set the reserved flag on one server, but the leases file on the other 
server doesn't see/reflect the reservation for that same lease.
(I see the lease on both machines, but there's no reservation on the second 
server. The one I didn't target with the omapi connection/change.)

Do I have to run OMAPI against both servers?
(I guess I kind of thought since it's a change to the lease, it would get 
communicated between the peers. That looks like a bad assumption.)

Can someone, (probably ISC) confirm the "right" way to do this?

TIA
-Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/dhcp-users/attachments/20210527/6169781a/attachment-0001.htm>

------------------------------

Message: 2
Date: Thu, 27 May 2021 13:22:54 -0700
From: Gregory Sloop <gr...@sloop.net>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: OMAPI Reservations and peer/failover
Message-ID: <1674175033.20210527132...@sloop.net>
Content-Type: text/plain; charset="iso-8859-15"

Following up on my own post.
Given what I've been able to dig up on the subject of omapi and peers, I'm 
pretty sure you have to run against both, explicitly. 

But, additional complication arise!

As noted, a fair bit of reading and searching seems to indicate you have to run 
the omshell commands against each server.
However, this is particularly interesting (or perhaps troubling.)
See: https://lists.isc.org/mailman/htdig/dhcp-users/2006-July/001102.html

To save you the click, I'll quote...
---
"You will have to rerun the statement on both peers. 
Take careful note of servers that lose their dhcpd.leases files, you'll have to 
be able to 0-to-60 them by replaying everything. "
---

There was no expansion on this - and my understanding of it is somewhat 
ambiguous.
Does this mean that if I have a peer that gets rebuild and the leases file is 
deleted, it won't get a copy of the "original" leases file from it's peer and 
that all the "reservation" flags will be lost and I will have to re-run all the 
omapi commands against the peer which lost the leases file?

Assuming that's the correct interpretation...
I suppose that it's best then, to copy the leases file from the "still-up' peer 
to the rebuilt peer. (I can't see a reason not to do this, but perhaps I'm 
missing something.)

I'd be thrilled for the grizzled old-timers out there to weigh in and offer me 
some of that sage advice! :) 
[On this list, anyway, that usually means super-helpful and awesome posts. That 
isn't the usual response of the old veterans from other lists, however!]

Perhaps this is all done way better in Kea, I dunno. Perhaps I ought to start 
looking at that.

Thanks in advance!
-Greg


Anyone?
I kinda want to get this handled and off my plate, so I'm probably a little 
impatient. :)

Thanks again!



I finally got around to attempting to set the reservation flag on some dhcp 
leases using omapi.
(I'd asked about how to do this with OMAPI ages ago ... since I can do it live 
and not have to stop the DHCP servers and hand edit the leases file.)

I'm running a pair of peers/failover/load-balance machines for dhcp.

So, I set the reserved flag on one server, but the leases file on the other 
server doesn't see/reflect the reservation for that same lease.
(I see the lease on both machines, but there's no reservation on the second 
server. The one I didn't target with the omapi connection/change.)

Do I have to run OMAPI against both servers?
(I guess I kind of thought since it's a change to the lease, it would get 
communicated between the peers. That looks like a bad assumption.)

Can someone, (probably ISC) confirm the "right" way to do this?

TIA
-Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/dhcp-users/attachments/20210527/af1a78d9/attachment-0001.htm>

------------------------------

Message: 3
Date: Fri, 28 May 2021 12:17:22 +0900
From: ??? <pkd...@naver.com>
To: <dhcp-users@lists.isc.org>
Subject: dhcrelay prints these logs and doesn't live normally. [Can't
        initialize context: not enough free resources.]
Message-ID: <278e872b3a744051686af707aa6...@cweb015.nm.nfra.io>
Content-Type: text/plain; charset="utf-8"

thanks for reply Glenn.Both dhcpd and dhcrelay can be run on one system, but 
only dhcrelay is currently used.
In addition, dhcrelay was well run and restarted, but logs occurred, and the 
restart failed continuously. The restart process is as follows.
kill -9 xxx; /usr/sbin/dhcrelay -i vlan200 A.B.C.D -i vlan100

The result of ulimit-n is 1024.
ISC_R_NORESOURCES is returned to its location: 
bind/bind-9.9.5/lib/isc/unix/socket.c.
The problem is when the fd value of the socket is greater than 1024, and when 
the fd value of the socket is less than 0.
I think the fd value is less than zero, what is the situation? It's not easy to 
reproduce.
regards, pkd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/dhcp-users/attachments/20210528/b239a667/attachment-0001.htm>

------------------------------

Subject: Digest Footer

_______________________________________________
ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.

dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users


------------------------------

End of dhcp-users Digest, Vol 151, Issue 11
*******************************************

Reply via email to