On Wed, Feb 8, 2017 at 12:38 PM, Joseph L. Casale <[email protected]> wrote: >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Kurt Buff >> Sent: Wednesday, February 8, 2017 1:22 PM >> To: ntsysadm <[email protected]> >> Subject: [NTSysADM] Odd problem with DHCP > > >> I didn't have time to set up a packet capture on the firewall, but I >> was able to tail the dhcp log on the firewall, and in each case I >> never saw the request hit the log. > > That does narrow it down. I recently had an odd one where an HPE > switch was replaced with the newer Aruba equivalent and the traffic > management and security wrt dhcp helper, snooping and arp protection > behavior changed causing requests to fail. > > So if the logs do not show anything, either the daemon itself is broken, > mishandling or needing a more verbose logging level to indicate why, or > the broadcast never makes it to the machine. > > I'd start by setting up a filtered capture (for obvious reasons) and letting > it run until the problem manifests again. Depending on your topology, you > might set up more than one cap. Once a client fails, you will probably have > your answer.
I suppose I should. Dammit, now I have to make time for that. Kurt
