"peer holds all free leases" problem

a.bell.is.a.cup. until.it.is.struck a_bell_is_a_cup_until_it_is_struck at hotmail.com
Thu Jul 15 14:53:48 UTC 2010


Hello, I'm having a problem with my setup and am hoping someone can help me find out what's going on.
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).
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: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 leasesJul 15 09:23:41 dhcp-01 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leasesJul 15 09:24:37 dhcp-01 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leasesJul 15 09:24:40 dhcp-01 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leasesJul 15 09:24:48 dhcp-01 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leasesJul 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
and this on the secondary: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 leasesJul 15 09:22:03 dhcp-02 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leasesJul 15 09:22:35 dhcp-02 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leasesJul 15 09:22:37 dhcp-02 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leasesJul 15 09:22:45 dhcp-02 dhcpd: DHCPDISCOVER from 00:0c:46:81:7f:55 via 10.187.0.1: peer holds all free leasesJul 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
yes, the time was off by 2 minutes on the secondary; I have since fixed this, but this continues to happen though. 
here's the relevant snippets from my dhcpd.conf on the primary (the secondary's config is the same (except for the failover part) :
ddns-update-style ad-hoc;allow client-updates;ddns-domainname "sub.domain.tld";option ntp-servers 172.16.16.239, 172.16.16.241;option domain-name "sub.domain.tld";option domain-name-servers 172.16.16.241, 172.16.16.239;option netbios-node-type 8;option netbios-name-servers 172.16.16.242, 172.16.16.239;default-lease-time 28800;max-lease-time 28800;authoritative;
failover peer "dhcp-failover" {  primary; # declare this to be the primary server  address 172.16.8.86;  port 647;  peer address 172.16.8.87;  peer port 647;  max-response-delay 30;  max-unacked-updates 10;  load balance max seconds 3;  mclt 1800;  split 128;}

# Use this to send dhcp log messages to a different log file (you also# have to hack syslog.conf to complete the redirection).log-facility local6;
# printer-shared-networkshared-network Printers {        # Printers        option routers 10.187.0.1;        ddns-updates on;        ddns-domainname "sub.domain.tld";        # 10.187.0.0 Printers        subnet 10.187.0.0 netmask 255.255.255.0 {                authoritative;                ddns-domainname "sub.domain.tld";                ddns-updates on;                }        # 10.187.1.0 Printers        subnet 10.187.1.0 netmask 255.255.255.0 {                authoritative;                ddns-domainname "sub.domain.tld";                ddns-updates on;                }        # 10.187.10.0 Staff Printers        subnet 10.187.10.0 netmask 255.255.255.0 {                authoritative;                ddns-domainname "sub.domain.tld";                ddns-updates on;       pool {                range 10.187.0.80 10.187.0.254;                range 10.187.1.2 10.187.1.254;                failover peer "dhcp-failover";                deny dynamic bootp clients;                }

The network has roughly 100 devices on it; certainly no more than 150. 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. Why is this going on?  Have I done something boneheaded with the failover section?
I've looked through the archives and google, but to little success. Any help on this would be greatly appreciated.
--a bell is a cup . . . until it is struck


 		 	   		  
_________________________________________________________________
The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. 
http://www.windowslive.com/campaign/thenewbusy?tile=multicalendar&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20100715/338d4495/attachment.html>


More information about the dhcp-users mailing list