DHCP has become such an important element of efficient network design that network administrators want to ensure proper DHCP deployment. Basic considerations of DHCP deployment include:
Determining the number of DHCP servers to use.
Determining and configuring scopes.
Reserving IP addresses.
Using BOOTP tables.
Determining the Number of DHCP Servers to Use
One active DHCP server and one backup DHCP server can support a large number of clients, depending on hardware configurations and other issues. However, when deciding on the number of DHCP servers required, consider the location of routers on the network and whether each subnet requires a DHCP server. In addition, be sure to account for slower WAN links or dial-up links between segments utilizing the DHCP service. Network administrators typically deploy a DHCP server on both sides of these links to serve clients locally.
A network can have practical size constraints based on the size of a broadcast IP address class, such as the 254-node limit of class C networks. In addition, server configuration issues, such as disk capacity and CPU speed, can affect performance.
Defining and Configuring Scopes
Administrators create an administrative grouping of computers called a scope for each physical subnet. Administrators plan scopes based on the needs of specific groups of users, with appropriate lease durations defined for the related scopes. A scope has the following properties:
A range of possible IP addresses from which to include or exclude addresses used in DHCP service lease offerings.
A unique subnet mask to determine the subnet related to a given IP address.
A scope name assigned when the scope is created.
Lease duration values to be assigned to DHCP clients that receive dynamically allocated IP addresses.
A DHCP scope consists of a pool of IP addresses on a subnet, such as 10.223.223.1 through 10.223.223.200, which the DHCP server can lease to DHCP clients. Each physical network can have only one DHCP scope or a superscope with one or more ranges of IP addresses.
Larger networks might require the following configuration steps to assign several address ranges within a single scope or subnet for DHCP service:
Define the scope by using the entire range of consecutive IP addresses that make up the local IP subnet.
Set exclusion ranges, which define the IP addresses within the scope that the DHCP server does not lease. For example, to exclude the first 10 addresses in the previous example scope, create an exclusion for 10.223.223.1 through 10.223.223.10. Doing so specifies that no DHCP clients ever receive these addresses for leased configuration.
Select additional exclusion ranges to further exclude any IP addresses that are not to be leased to DHCP clients. Exclusions should include all devices that cannot use DHCP, such as printers.
Create reservations by reserving some IP addresses for permanent lease assignment to specified computers or devices on a network. Reservations should be made only for devices that use DHCP and have a specialized function on the network, such as special server computers (servers used for DHCP, WINS, or DNS) and routers.
Adjust the duration of leases. Note that the default lease duration of eight days might not require adjustment.
After defining and configuring a scope as outlined above, you must activate the scope before dynamic service begins for DHCP-enabled clients. After you do this, the server can begin processing IP address lease requests and offering leases to DHCP-enabled clients on the network.
Superscopes add extra flexibility to complex DHCP service configurations by:
Supporting DHCP clients on a single physical network segment that has multiple logical IP subnets.
Supporting remote DHCP clients located on the far side of BOOTP/DHCP relay agents.
Superscopes offer greater flexibility when:
Adding more computers than originally planned.
Renumbering the network.
Two DHCP servers manage separate logical subnets on the same physical subnet.
Table 4 shows two DHCP servers that can be reached on the same physical subnet and configured with a single scope.
If DHCP-Server A manages a different scope of addresses than DHCP-Server B, and neither has any information about addresses managed by the other, a problem arises if a client previously registered with Server A, for example, releases its name during a shutdown and later reconnects to the network after restarting. The client tries to renew its previously leased IP address.
If DHCP-Server B receives a DHCPRequest message from the client to renew use of an address before Server A does, Server B, being unaware of that IP address, causes it to reject the request and send a DHCPNACK message to the client. The client must then renegotiate a DHCP lease by broadcasting a DHCPDiscover message on the local subnet. Server B can send a DHCPOffer message, offering the client an address. The client can accept the address by returning a DHCPRequest message for that address to Server B for approval. When Server B approves the address assignment, it returns a DHCPACK message to the client.
Several DHCP service problems can occur within this example:
Nothing prevents a client from having its attempt to renew a previous address rejected each time it connects to the network.
The server might, when the client rejects and re-requests an address lease, offer an address that places the client on a subnet requiring an alternate configuration.
These problems can be averted by using the following steps to implement superscopes on both DHCP servers, a solution which enables more predictable and effective address management:
Create a new scope on a server that contains the respective scope information for the other. For example, on DHCP-Server A, create a new scope with the range of 220.127.116.11 through 18.104.22.168. Also create an exclusion range for the new scope for all scope addresses (22.214.171.124 through 126.96.36.199).
Repeat the previous step for the other DHCP server. For example, on DHCP-Server B, create a new scope with the range of 188.8.131.52 through 184.108.40.206, as well as an exclusion range for this new scope for all scope addresses (220.127.116.11 through 18.104.22.168).
By configuring superscopes as described, both DHCP-Server A and DHCP-Server B recognize IP addresses assigned by the other. This procedure prevents either server from negatively acknowledging attempts by DHCP clients to renew their same IP address or to obtain an address from the same logical range of addresses—in other words, a different address within the same logical subnet.