DHCP failover problems - still
David W. Hankins
dhankins at isc.org
Fri Nov 20 00:15:05 UTC 2009
On Wed, Nov 18, 2009 at 09:57:57PM -0800, Matt Causey wrote:
> If I'm looking at a rash of random 'dhcpd: failover peer failover: I
> move from normal to communications-interrupted' events - is there a
> good way for me to know which happened? i.e. was it a lack of contact
> messages, or a disruption of the TCP socket? I'm going to try to run
> some tcpdump on the system to catch when the disconnect happens
> (tcpdump -w failver.pcap -xX -s0 -n -i eth0 'port 519 or port 520 and
> tcp') but I wondered if you knew of a better way to track down a
> problem where 2 server randomly stop communicating via the failover
> channel.....but all other services on the boxen are fine.
Unfortunately there is not a great deal of useful logging around
these events. A socket suddenly closing or resetting I think only
results in the state changes, whereas a CONTACT message timeout
causes a message with the word "timeout" in it to be logged before
the state change is logged.
David W. Hankins BIND 10 needs more DHCP voices.
Software Engineer There just aren't enough in our heads.
Internet Systems Consortium, Inc. http://bind10.isc.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: not available
More information about the dhcp-users