The address distribution isn't going to do much for load balancing. It is all determined by which server answers first. That will be the busy one. I am with the others that do 100 - 100.
DHCP clients do try to renew on reboot. They always try to renew directly with the original server, they only broadcast if they have not gotten a renewal. You can control some of this through the dhcp scope options, for example you can have them release at shutdown. > -----Original Message----- > From: Jim Dandy [mailto:[email protected]] > Sent: Friday, May 01, 2009 2:41 PM > To: NT System Admin Issues > Subject: RE: DHCP 80-20 rule > > I still don't get the 80-20 thing. 50-50 would distribute the load > better and would potentially give you more leases if one fails. > Perhaps > the hope is that the one that fails is the one with 20% and that 80% > would give you adequate addresses to be fully functional while you fix > the 20. > > Thanks for the info on the no-broadcast for renewals. Here is another > question ... > > 3) Let's say you reboot your client before the lease expires. On > reboot > does it do a broadcast to get a new address or does it just try to > renew > from the DHCP server from which it got its original lease? > > Curt > > > -----Original Message----- > > From: Kennedy, Jim [mailto:[email protected]] > > Sent: Friday, May 01, 2009 11:17 AM > > To: NT System Admin Issues > > Subject: RE: DHCP 80-20 rule > > > > > > > -----Original Message----- > > > From: Jim Dandy > > > > > 1) Why 80-20? Why not 50-50? If one server fails, wouldn't it be > > > better for the other server to have a larger range from which to > > > distribute addresses? > > > > The 20 is designed to keep you alive and running while you fix the 80 > server. > > Certainly a full range on both servers to serve all your clients > would > be > > great, if your subnetting and available addresses allow it. > > > > > > > > 2) Let's say everything is working perfectly and both DHCP servers > are > > > up. Client1 requests an address and receives address 192.168.0.1 > from > > > DHCPServer1. Time passes until half of the lease time has expired > so > > > Client1 requests an address. This time DHCPServer2 is a little > faster > > > and provides address 192.168.0.129. > > > > At 50 percent the client contacts the original leasing server > directly > to > > renew that lease. It does not do a brand new lease broadcast. It will > continue > > to ask directly until it gets an answer. If it can't it will then > broadcast > > for a brand new lease. > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
