dhcp server + failover : peer holds all free leases/load balance0 ...

[li jun]

  I 'm troubled by the same problem,and looked about for the solution
somewhere,Some one said,generally, it is  happened when  a pool does not
have enough ip to lease,and  a  tool "omshell" can slove the problem.but I
do not figure out how to use the tool untill now.Could  anyone tell me the
answer here ?
Thank in advance

---------------------
LIJUN
IS DEPARTMENT
HITACHI DISPLAYS DEVICES(SUZHOU)
CN
 

> -----Original Message-----
> From: dhcp-users-bounce at isc.org 
> [mailto:dhcp-users-bounce at isc.org] On Behalf Of Sebastien CRAMATTE
> Sent: Wednesday, July 30, 2008 7:15 AM
> To: dhcp-users at isc.org
> Subject: dhcp server + failover : peer holds all free 
> leases/load balance0 ...
> 
> Hello,
> 
> I've just setup 2 dhcp server  to use  failover. I'm running 
> debian lenny with dhcpd 3.1.1
> 2 servers seems to be synchronised but won't  ACK leases
> 
> On the slave I can see this message in syslog  :  'peer holds 
> all free leases/load balance0'
> 
> I found some post about this but nothing that help to solve 
> me this issue.
> 
> On my network I've got various dhcp relay () on diferent network
> segment)  that point to  these main servers.
> I never use directly these servers. Main dhcp servers receive 
> only unicast petition from port 67 to 67.
> 
> If I disable failover it works as a charm. Might be due to 
> dhcp relay mode ?
> 
> 
> ---------- master configuration --------- failover peer 
> "failover1" { primary; address 10.0.0.8; port 519; peer 
> address 10.0.0.9; peer port 519; max-response-delay 60; 
> max-unacked-updates 10; load balance max seconds 3; split 
> 128; mclt 3600; }
> 
> default-lease-time 86400;
> max-lease-time 604800;
> ddns-update-style interim;
> one-lease-per-client on;
> deny duplicates;
> ignore declines;
> authoritative;
> use-host-decl-names on;
> ignore client-updates;
> 
> subnet 10.0.0.0 netmask 255.254.0.0 {
> }
> 
> subnet 10.8.0.0 netmask 255.255.0.0 {
> deny unknown-clients;
> server-identifier 10.8.0.1;
> option broadcast-address 10.8.255.255;
> option routers 10.8.0.1;
> pool {
> range 10.8.0.2 10.8.127.255;
> max-lease-time 86400;
> default-lease-time 86400;
> failover peer "failover1";
> }
> }
> 
> subnet 10.9.0.0 netmask 255.255.0.0 {
> deny unknown-clients;
> server-identifier 10.9.0.1;
> option broadcast-address 10.9.255.255;
> option routers 10.9.0.1;
> pool {
> range 10.9.0.2 10.9.255.255;
> max-lease-time 86400;
> default-lease-time 86400;
> failover peer "failover1";
> }
> }
> 
> ---- slave configuration -----
> failover peer "failover1" {
> secondary;
> address 10.0.0.9;
> port 519;
> peer address 10.0.0.8;
> peer port 519;
> max-response-delay 60;
> max-unacked-updates 10;
> load balance max seconds 3;
> }
> 
> default-lease-time 86400;
> max-lease-time 604800;
> one-lease-per-client on;
> deny duplicates;
> ignore declines;
> authoritative;
> use-host-decl-names on;
> ignore client-updates;
> 
> subnet 10.0.0.0 netmask 255.254.0.0 {
> }
> 
> subnet 10.8.0.0 netmask 255.255.0.0 {
> deny unknown-clients;
> server-identifier 10.8.0.1;
> option broadcast-address 10.8.255.255;
> option routers 10.8.0.1;
> pool {
> range 10.8.0.2 10.8.127.255;
> max-lease-time 86400;
> default-lease-time 86400;
> failover peer "failover1";
> }
> }
> 
> subnet 10.9.0.0 netmask 255.255.0.0 {
> deny unknown-clients;
> server-identifier 10.9.0.1;
> option broadcast-address 10.9.255.255;
> option routers 10.9.0.1;
> pool {
> range 10.9.0.2 10.9.255.255;
> max-lease-time 86400;
> default-lease-time 86400;
> failover peer "failover1";
> }
> }
> 
> 
> Thank you for you help
> 
> 

Disclaimer:
The contents of this e-mail, and its attachments, if any, are confidential and may be protected
by law against any unauthorized use.  If you have received this e-mail by mistake or have
reason to believe that you are not the intended recipient, please notify the sender by reply
e-mail as soon as possible and delete it from your computer system immediately thereafter.
If you are not the intended recipient, you must not copy this e-mail or attachment or disclose
the contents to any other person.  While we have made every effort to keep our network virus free,
we take no responsibility for any computer virus which might be transferred by way of this e-mail.