partner-down still peer holds all free leases

Thomas Zenz Thomas.Zenz at oenb.at
Fri Sep 12 08:56:49 UTC 2008


Hi all,

Today we do a redundancy Test. 
Over Failover Pair runs on Version 3.10

After we shut down the secondary server,
I edited the leases file to partner state down:

     failover peer "BackUP" state {
       my state partner-down at 4 2008/09/11 16:29:54;
       partner state normal at 5 2006/05/26 05:48:34;
     }

This mornig some PXE CLients get no lease:
peer holds all free leases

So I reduced the load balance max seconds from 1 to 0.
No effekt.

Then I tried omshell:
Set the local-state to 1
No reaction allways goes back to 4  - resolution interrupted

     > server 127.0.0.1
     > connect
     obj: <null>
     > new "failover-state"
     obj: failover-state
     > set name ="BackUP"
     obj: failover-state
     name = "BackUP"
     > open
     obj: failover-state
     name = "BackUP"
     partner-address = 20:e0:69:00:00:00:00:00
     partner-port = 00:00:02:08
     local-address = 70:df:69:00:00:00:00:00
     local-port = 00:00:02:07
     max-outstanding-updates = 00:00:00:0a
     mclt = 00:12:75:00
     load-balance-max-secs = 00:00:00:03
     load-balance-hba = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00
     partner-state = 00:00:00:02
     local-state = 00:00:00:04
     partner-stos = 44:76:96:b2
     local-stos = 48:c9:47:82
     hierarchy = 00:00:00:00
     last-packet-sent = 00:00:00:00
     last-timestamp-received = 00:00:00:00
     skew = 00:00:00:00
     max-response-delay = 00:00:00:3c
     cur-unacked-updates = 00:00:00:00
     >
     set local-state
           local-state integer examine, modify
                 Indicates the present state of the DHCP server  in  this  failover
                 relationship.   Possible values for state are:
     
                      1  - partner down
                      2  - normal
                      3  - communications interrupted
                      4  - resolution interrupted
                      5  - potential conflict
                      6  - recover
                      7  - recover done
                      8  - shutdown
                      9  - paused
                      10 - startup
                      11 - recover wait
     update


Then I set the lease from backup to free.
Still no change.

What did we do wrong?

In my oppinion, the sever, that know's it's partner is down, should answer ALL requests (DHCPDISCOVER).
Why has the Server a problem to answer a lease for that he knows the IP.

See the lease:
     lease 10.14.102.151 {
       starts 4 2008/09/11 15:04:49;
       ends 4 2008/09/11 15:04:48;
       tstp 4 2008/09/11 15:04:49;
       tsfp 4 2008/09/11 15:04:49;
       atsfp 4 2008/09/11 15:04:49;
       cltt 4 2008/09/11 14:32:19;
       binding state backup;
       hardware ethernet 00:90:dc:06:bf:f9;
     }

My Workaroung was:
   a) increase the hosts for the Subnet.
   b) enter host entries for the Clients with the problem


Please help 
kind regards
Tom



More information about the dhcp-users mailing list