DRP server startup

Bob Harold rharolde at umich.edu
Wed Nov 25 16:39:03 UTC 2015


On Wed, Nov 25, 2015 at 10:25 AM, Friesen, Don MTIC:EX <
Don.Friesen at gov.bc.ca> wrote:

>
>   No.  The log shows it receiving nothing.  The prod servers log a lot of
> inbound traffic, and any offers they make.  This server logged nothing at
> all.  Which I find odd.
>
> Don Friesen
>
>
> -----Original Message-----
> From: dhcp-users-bounces at lists.isc.org [mailto:
> dhcp-users-bounces at lists.isc.org] On Behalf Of Glenn Satchell
> Sent: Wednesday, November 25, 2015 7:11 AM
> To: Users of ISC DHCP
> Subject: Re: DRP server startup
>
> Perhaps, because it is at a far away site the reply from the server took
> much longer to get back to the client and the client therefore selected one
> of the closer servers?
>
> I wouldn't like to rely on this behaviour though, so best to configure it
> properly :)
>
> regards,
> -glenn
>
> On Thu, November 26, 2015 1:34 am, Friesen, Don MTIC:EX wrote:
> >
> >    We run a failover configuration.  We have a second set of servers
> > at a DRP site.  All our relays have all four addresses configured.
> > The DRP servers are configured to not start the daemon on reboot.  Or
> > at least they should have been.  The server that was secondary at the
> > DRP site was not properly configured.  On a reboot the daemon started.
> > To my surprise, it served nothing.
> >
> >    I checked the configuration and it is configured to serve.  It has
> > a copy of the lease data from the production pair.  The startup log
> > follows.
> >
> >    Is the reason it served nothing that it is the declared secondary
> > server in the failover and the primary was never started?
> >
> > Wed Nov 25 00:01:00 2015: Internet Systems Consortium DHCP Server
> > 4.3.3 Wed Nov 25 00:01:00 2015: Copyright 2004-2015 Internet Systems
> Consortium.
> > Wed Nov 25 00:01:00 2015: All rights reserved.
> > Wed Nov 25 00:01:00 2015: For info, please visit
> > https://www.isc.org/software/dhcp/
> > Wed Nov 25 00:01:01 2015: Config file: /var/dhcp/dhcpd.conf Wed Nov 25
> > 00:01:01 2015: Database file: /var/dhcp/db/dhcpd.leases Wed Nov 25
> > 00:01:01 2015: PID file: /var/run/dhcpd.pid Wed Nov 25 00:01:04 2015:
> > lease 10.23.218.165: no subnet.
> > Wed Nov 25 00:01:04 2015: lease 10.23.218.157: no subnet.
> > Wed Nov 25 00:01:05 2015: Wrote 0 class decls to leases file.
> > Wed Nov 25 00:01:05 2015: Wrote 0 deleted host decls to leases file.
> > Wed Nov 25 00:01:05 2015: Wrote 0 new dynamic host decls to leases file.
> > Wed Nov 25 00:01:07 2015: Wrote 107752 leases to leases file.
> > Wed Nov 25 00:01:07 2015:
> > Wed Nov 25 00:01:07 2015: No subnet declaration for vnet3 (172.28.8.77).
> > Wed Nov 25 00:01:07 2015: ** Ignoring requests on vnet3.  If this is
> > not what
> > Wed Nov 25 00:01:07 2015:    you want, please write a subnet declaration
> > Wed Nov 25 00:01:07 2015:    in your dhcpd.conf file for the network
> > segment
> > Wed Nov 25 00:01:07 2015:    to which interface vnet3 is attached. **
> > Wed Nov 25 00:01:07 2015:
> > Wed Nov 25 00:01:07 2015:
> > Wed Nov 25 00:01:07 2015: No subnet declaration for vnet2
> (172.28.169.21).
> > Wed Nov 25 00:01:07 2015: ** Ignoring requests on vnet2.  If this is
> > not what
> > Wed Nov 25 00:01:07 2015:    you want, please write a subnet declaration
> > Wed Nov 25 00:01:07 2015:    in your dhcpd.conf file for the network
> > segment
> > Wed Nov 25 00:01:07 2015:    to which interface vnet2 is attached. **
> > Wed Nov 25 00:01:07 2015:
> > Wed Nov 25 00:01:07 2015:
> > Wed Nov 25 00:01:07 2015: No subnet declaration for vnet1 (0.0.0.0).
> > Wed Nov 25 00:01:07 2015: ** Ignoring requests on vnet1.  If this is
> > not what
> > Wed Nov 25 00:01:07 2015:    you want, please write a subnet declaration
> > Wed Nov 25 00:01:07 2015:    in your dhcpd.conf file for the network
> > segment
> > Wed Nov 25 00:01:07 2015:    to which interface vnet1 is attached. **
> > Wed Nov 25 00:01:07 2015:
> > Wed Nov 25 00:01:07 2015: Listening on
> > DLPI/vnet0/00:14:4f:fb:01:01/10_34_43_0
> > Wed Nov 25 00:01:07 2015: Sending on
> > DLPI/vnet0/00:14:4f:fb:01:01/10_34_43_0
> > Wed Nov 25 00:01:07 2015: Sending on   Socket/fallback/fallback-net
> > Wed Nov 25 00:01:07 2015: failover peer PoBCdhcp: I move from
> > communications-interrupted to startup Wed Nov 25 00:01:07 2015: Server
> > starting service.
> > Wed Nov 25 00:01:22 2015: failover peer PoBCdhcp: I move from startup
> > to communications-interrupted Wed Nov 25 01:05:34 2015: Wrote 0 class
> > decls to leases file.
> > Wed Nov 25 01:05:34 2015: Wrote 0 deleted host decls to leases file.
> > Wed Nov 25 01:05:34 2015: Wrote 0 new dynamic host decls to leases file.
> > Wed Nov 25 01:05:36 2015: Wrote 107752 leases to leases file.
> > Wed Nov 25 02:11:52 2015: Wrote 0 class decls to leases file.
> > Wed Nov 25 02:11:52 2015: Wrote 0 deleted host decls to leases file.
> > Wed Nov 25 02:11:52 2015: Wrote 0 new dynamic host decls to leases file.
> > Wed Nov 25 02:11:53 2015: Wrote 107752 leases to leases file.
> >
> > Don Friesen
>

Note that the DRP won't see renew packets, because those are usually
unicast to one DHCP server.  They will only see broadcast packets.  If
there are no 'new' clients, there might not be any.  If a new client (or
release/renew, depending on the client) does not show up, then I would
suggest tracing packets to be sure that discover packets are reaching the
DRP servers.

-- 
Bob Harold
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20151125/8f8f3249/attachment.html>


More information about the dhcp-users mailing list