DHCP failover problems - still
matt.causey at gmail.com
Fri Nov 20 02:41:54 UTC 2009
> 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.
Ok, so we are seeing this:
Nov 20 00:10:51 blah-101 dhcpd: DHCPACK on blah to 00:15:70:89:6d:00 via blah
Nov 20 00:11:32 blah-101 dhcpd: timeout waiting for failover peer failover
Nov 20 00:11:32 blah-101 dhcpd: peer failover: disconnected
Nov 20 00:11:33 blah-101 dhcpd: failover peer failover: I move from
normal to communications-interrupted
I think that my packet capture got this event, so I'll have a look...
> 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/
> dhcp-users mailing list
> dhcp-users at lists.isc.org
More information about the dhcp-users