DHCP Lease Address Pools, Ranges (Scopes) and Address Management
(Page 4 of 4)
Address Assignment With Multiple Scopes
Instead of putting all of its addresses (except excluded ones) in a single scope, a server may use multiple scopes. One common reason for the latter approach is to support more than one subnet on a server. Multiple scopes are also commonly used when multiple DHCP servers are used to serve the same clients. There are two ways to do this: either by having overlapping or non-overlapping scopes.
Overlapping scopes allows each server to assign any address from the same pool. However, the DHCP standard doesn't specify any way for servers to communicate with each other when they assign an address, so if both servers were told they could assign addresses from the same address pool, this could result in both servers trying to assign a particular address to two different devices.
As a result, if you are using two DHCP servers (as is often recommended for redundancy reasons), the administrator generally gives them different, non-overlapping scope assignments. Alternately, the same scope is given to each server, with each server told to exclude from use the addresses the other server is assigning.
For example, suppose we have two DHCP servers: A (the main server) and B (the backup). We want to assign most of the addresses to A and a few as backup to B. We could give both A and B the scope 22.214.171.124 through 126.96.36.199. Wed exclude 188.8.131.52 through 184.108.40.206 from both. Then we'd exclude from server A the range 220.127.116.11 through 18.104.22.168, and exclude from server B the range 111.14.20 through 22.214.171.124. Figure 261 shows how this would work. The main advantage of this method is that if one server goes down, the administrator can quickly remove the exclusion and let the remaining server access all addresses. Also, if one server runs out of addresses while the other has plenty, the allocations can be easily shifted.
There are many other issues related to address management, which start to get into the guts of DHCP server implementation. For example, as was the case with BOOTP, we may need to use relay agents when the DHCP server is responsible for addresses on a subnet different from its own. There are also special DHCP features that affect how addresses are managed. For example, the DHCP conflict detection feature can actually allow two servers to have overlapping scopes, despite what we said above. The section on DHCP implementation and features gets into these issues in more detail.
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.