DHCP Server General Implementation and Management Issues
(Page 3 of 3)
Server Placement, Setup and Maintenance
Once you know how many servers you want, you have to determine on which part of the network you want to place them. If you have many physical networks, you may also need to use DHCP relaying to allow all clients to reach a server. Of course, the structure of the network may affect the number of servers you use, so many of these decisions are interrelated.
You must make policy decisions related to all the DHCP operating parameters we have seen earlier. The two biggies are deciding on the size and structure of the address pool, and making lease policy decisions such as lease length and the settings for the T1 and T2 timers. You also must decide what clients will be dynamically allocated addresses and how manually-configured clients will be handled.
Finally, it's essential for the administrator to remember that an organization's DHCP server is a database server and must be treated accordingly. Like any database server, it must be maintained and managed carefully. Administrative policies must be put into place to ensure the security and efficient operation of the server. Also, unlike certain other types of database systems, the DHCP database is not automatically replicated; the server database should therefore be routinely backed up, and using RAID storage is also a good idea.
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.