<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Hello, I'm having a problem with my setup and am hoping someone can help me find out what's going on.<div><br></div><div>My setup: 2 centOS servers with dhcpd 3.0.5-Redhat (i've tried building from source and had the same problem, wound up going back to the centos rpm).</div><div><br></div><div>A network that the dhcp failover pair is serving dhcp for has computers suddenly failing to get an IP; the logs show this on the primary:</div><div><div>Jul 15 09:23:37 dhcp-01 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leases</div><div>Jul 15 09:23:41 dhcp-01 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leases</div><div>Jul 15 09:24:37 dhcp-01 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leases</div><div>Jul 15 09:24:40 dhcp-01 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leases</div><div>Jul 15 09:24:48 dhcp-01 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leases</div><div>Jul 15 09:25:04 dhcp-01 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leases</div></div><div><br></div><div>and this on the secondary:</div><div><div>Jul 15 09:21:46 dhcp-02 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leases</div><div>Jul 15 09:22:03 dhcp-02 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leases</div><div>Jul 15 09:22:35 dhcp-02 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leases</div><div>Jul 15 09:22:37 dhcp-02 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leases</div><div>Jul 15 09:22:45 dhcp-02 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leases</div><div>Jul 15 09:23:02 dhcp-02 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leases</div></div><div><br></div><div>yes, the time was off by 2 minutes on the secondary; I have since fixed this, but this continues to happen though. </div><div><br></div><div><div>here's the relevant snippets from my dhcpd.conf on the primary (the secondary's config is the same (except for the failover part) :</div><div><br></div><div>ddns-update-style ad-hoc;</div><div>allow client-updates;</div><div>ddns-domainname "sub.domain.tld";</div><div>option ntp-servers 172.16.16.239, 172.16.16.241;</div><div>option domain-name "sub.domain.tld";</div><div>option domain-name-servers 172.16.16.241, 172.16.16.239;</div><div>option netbios-node-type 8;</div><div>option netbios-name-servers 172.16.16.242, 172.16.16.239;</div><div>default-lease-time 28800;</div><div>max-lease-time 28800;</div><div>authoritative;</div><div><br></div><div>failover peer "dhcp-failover" {</div><div> primary; # declare this to be the primary server</div><div> address 172.16.8.86;</div><div> port 647;</div><div> peer address 172.16.8.87;</div><div> peer port 647;</div><div> max-response-delay 30;</div><div> max-unacked-updates 10;</div><div> load balance max seconds 3;</div><div> mclt 1800;</div><div> split 128;</div><div>}</div><div><br></div><div><br></div><div># Use this to send dhcp log messages to a different log file (you also</div><div># have to hack syslog.conf to complete the redirection).</div><div>log-facility local6;</div><div><br></div><div><div># printer-shared-network</div><div>shared-network Printers {</div><div> # Printers</div><div> option routers 10.187.0.1;</div><div> ddns-updates on;</div><div> ddns-domainname "sub.domain.tld";</div><div> # 10.187.0.0 Printers</div><div> subnet 10.187.0.0 netmask 255.255.255.0 {</div><div> authoritative;</div><div> ddns-domainname "sub.domain.tld";</div><div> ddns-updates on;</div><div> }</div><div> # 10.187.1.0 Printers</div><div> subnet 10.187.1.0 netmask 255.255.255.0 {</div><div> authoritative;</div><div> ddns-domainname "sub.domain.tld";</div><div> ddns-updates on;</div><div> }</div><div> # 10.187.10.0 Staff Printers</div><div> subnet 10.187.10.0 netmask 255.255.255.0 {</div><div> authoritative;</div><div> ddns-domainname "sub.domain.tld";</div><div> ddns-updates on;</div></div><div> pool {</div><div> range 10.187.0.80 10.187.0.254;</div><div> range 10.187.1.2 10.187.1.254;</div><div> failover peer "dhcp-failover";</div><div> deny dynamic bootp clients;</div><div> }</div><div><br></div><div><br></div><div>The network has roughly 100 devices on it; certainly no more than 150. </div><div>The pool's got 420-odd IP addresses available; even with the time mismatch there should be more than enough IP addresses to hand out. </div><div>Why is this going on? </div><div>Have I done something boneheaded with the failover section?</div><div><br></div><div>I've looked through the archives and google, but to little success. Any help on this would be greatly appreciated.</div><div><br></div>--<div>a bell is a cup . . . until it is struck</div><br><br></div>
<br /><hr />The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. <a href='http://www.windowslive.com/campaign/thenewbusy?tile=multicalendar&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5' target='_new'>Get busy.</a></body>
</html>