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: Reg: dhcp service unresponsive frequently (Niall O'Reilly)
----------------------------------------------------------------------
Message: 1
Date: Sat, 25 Jan 2020 17:27:37 +0000
From: "Niall O'Reilly" <niall.orei...@ucd.ie>
To: "Purva Rawan" <pur...@cdac.in>, "Users of ISC DHCP"
<dhcp-users@lists.isc.org>
Subject: Re: Reg: dhcp service unresponsive frequently
Message-ID: <7700ea5b-f4dc-4f23-830c-e1e0e95fe...@ucd.ie>
Content-Type: text/plain; format=flowed; markup=markdown
On 24 Jan 2020, at 7:14, Purva Rawan wrote:
> We have not configured dhcp relay agent in both dhcp server's
> configuration .
That would be right; see below: the relay belongs to the network, not to
the
server.
> In one of the server ,dhcp service listening on each interfaces.
> For another dhcp server ,dhcp relay agent is serving through Layer 3
> switch.
>
> But we are facing this issue for both the servers.
It may help to think about this from the client back to the server,
rather than from the server(s) outwards.
I don't have a good picture of your network topology, or where the
relays and servers are sitting, or what experience you have, so I may
be explaining at the wrong level. If so, apologies.
Each client is connected to a layer-2 network, and needs a local DHCP
service on this network.
The local DHCP service must be provided either by a relay or by a
server;
it's unusual to have a server connected to every client network.
The relay is typically part of the router configuration.
Each relay must be configured with the address of one or more servers;
one is enough; a second gives resilience; I wouldn't suggest more.
The server(s) can be on a network where no clients are connected; except
for very simple topologies, I prefer to keep the server on a non-client
network.
Each relay must be able to reach, and be reachable from, the server(s);
access lists and routing errors can obstruct reachability, perhaps
asymmetrically.
Each client network must be specified in the server configuration.
Log entries on the server will show you what the server thinks is going
on.
You should see the DORA sequence: DISCOVER, OFFER, REQUEST, ACK; for
renewals, you'll normally just see REQUEST, ACK.
If you know or expect that the client is sending DISCOVER, but don't see
it in the server log, then you'll need to look at your network and work
out why the DISCOVER is not reaching the server either from the relay or
from a client on the same network as the server.
If you see OFFER in the server logs, but no REQUEST, you'll need to look
at the network in the opposite direction, and work out why the OFFER is
not reaching the client or relay.
I hope this helps.
Niall O'Reilly
------------------------------
Subject: Digest Footer
_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 135, Issue 15
*******************************************
