4.1.0a1 Failover sync speed

Michael Kaegler Michael.Kaegler at marist.edu
Fri May 23 13:23:25 UTC 2008

Up until now, we've had static assignments for every machine in our 
network. Don't ask, it was the requirement! Having multiple servers 
in this environment without failover was fine.

Now that we're moving to pools, we're needing to configure failover 
for them. And so we decided to start testing the latest (4.1.0a1, 
despite the 'a') so that we could get the inevitable move to the 4.0 
branch over with during the off-semester.

We loaded it up on a pair of test servers, and found the initial sync 
took over 4 hours! We do have 140 subnets (mostly /21s), but still it 
should go much faster than that. The load averages on the test 
servers were high (4.00 - 6.00) but the interfaces were only pushing 

We can't keep our dhcp servers down for the 4 hour initial sync. I'm 
also worried about working problems and having to restart this 4-hour 
process as part of the debug steps!

Is this unreasonable? Should it take 4 hours? Am I being overly 
aggressive in getting to 4.0?

Michael "Porkchop" Kaegler, Sr. Network Analyst
(845) 575-3061 Marist College, Poughkeepsie, NY

More information about the dhcp-users mailing list