| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
DHCP Lease Address Pools, Ranges (Scopes) and Address Management (Page 1 of 4) Simpler host configuration methods such as BOOTP (or DHCP manual allocation for that matter) associate a single IP address with each client machine. DHCP dynamic addressing removes this one-to-one correspondence, in favor of flexible address mapping to clients on an as needed basis. The clients no longer own the addresses but lease them from the true owner, the server. Obviously, then, a primary job of both a DHCP server and the administrator of that server is to maintain and manage these client addresses. The set of all addresses that a DHCP server has available for assignment is most often called the address pool. The first issue related to address management is ensuring that the address pool is large enough to serve all the clients that will be using the server. The number of addresses required depends on a number of factors:
I'm sure you've probably noticed that these issues are similar to those that I raised in discussing lease lengths earlier in this section. In fact, the two matters are intimately related. Generally speaking, having more addresses gives the administrator the luxury of using longer leases. If you are short on addresses you probably need to use shorter leases to reduce the chances of any unused addresses continuing to be allocated to devices not needing them.
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||