The Dynamic Host Configuration Protocol (DHCP) is an excellent technique for managing changes in the network configuration parameters (such as IP address, network mask, default gateway, etc.) of Internet connected devices. DHCP uses a server containing a database of parameters that key off the network interface card (NIC) address of the connected device. A DHCP client program running on the device requests these parameters which are delivered by the DHCP server based on the requesting device's NIC address.

In order to migrate devices to the central DHCP service offered by EITS, departments are encouraged to follow the procedures listed below:

1. If departmental domain network liaisons (DNLs) do not have an accurate list of NIC & IP addresses (the minimum set of information needed by DHCP servers), they need to examine the list of devices seen on the network through the DHCP Web Page. Click "List my IP addresses by range" and click the building network in which you are interested.



2. Although these lists are generally fairly accurate, discrepancies with lists kept by DNLs have been noted in the past. If DNLs wish to verify the e-mailed lists with their own lists of NIC & IP addresses or they wish to verify them by visiting each networked device, they are encouraged to do so. DNLs are encouraged to put NIC addresses of ALL devices for which they have information into the database, including devices which do not currently do IP (such as Appletalk and IPX printers). Often in network troubleshooting the only identifier you have for a device is the NIC address, and having as complete a record as possible will help track down problem devices. These devices should be indicated by placing their NIC addresses in the appropriate field and then placing the characters N/A in place of the other fields, or leaving the other fields blank (as in the case of a device with no IP address). This information is here for the DNL to use, so the more complete it is the better.



3. Once these lists have been verified and undesirable entries have been removed, DNLs need to e-mail the lists as text attachments to dhcptf@listserv.uga.edu and include their UGA MyIDs (currently ARCHES userids) in the body of the message. DNLs will be notified when the lists have been imported into the DHCP server database. (Note: Individual machines can also be added, deleted or changed through the DHCP Web Page by DNLs, or DHCP updaters they authorize. These changes take effect approximately five minutes after they have been entered into the system. Access to the Web page requires UGA MyID and password credentials.)



4. After the DHCP database has been updated, one can start configuring devices to use DHCP. Printing the list of registered machines and using it as a checklist will help to systematically keep track of those devices that have successfully been converted to use DHCP. DNLs can display (and print) lists of their DHCP database entries by going to the DHCP Web Page, entering their UGA MyID and password, and clicking "List all of my devices" or "List my IP addresses by range". (Note: NIC addresses will be referred to as Mac addresses in the lists.)



5. DNLs should coordinate with the people doing the conversions (be they DNLs, departmental technical support staff, or the individual computer users) to make sure the records are accurate. Making sure one knows which devices are going to be on DHCP and which will have to be configured manually is essential for a smooth transition when the network attributes change on "cut-over day". The actual conversion procedure depends on the operating system running on the device. Web documentation for most of the common desktop operating systems can assist in the conversion process. If the individual attempting to convert a device to use DHCP is unsuccessful, they are encouraged to contact the EITS Help Desk via theWeb (http://www.uga.edu/~ucns/mail-forms/ct.html), e-mail (helpdesk@uga.edu), or phone (706-542-3106) to obtain assistance.