Chapter 8 Planning for DHCP Service (Task)

You can use DHCP services in a network you are creating or in a network that exists. If you are setting up a network, see Chapter 3, Planning Your TCP/IP Network (Task) before you attempt to set up DHCP services. If the network exists, continue in this chapter.

This chapter describes what you need to do before you set up DHCP service on your network. The information is intended for use with DHCP Manager, although you can also use the command-line utility dhcpconfig to set up DHCP service.

This chapter contains the following information:

• Preparing Your Network for DHCP Service (Task Map)

• Making Decisions for DHCP Server Configuration (Task Map)

• Making Decisions for IP Address Management (Task Map)

• Planning for Multiple DHCP Servers

• Planning for Remote Network Configuration

• Selecting the Tool for Configuring DHCP

Preparing Your Network for DHCP Service (Task Map)

Before you set up your network to use DHCP, you must first collect information and make decisions about how you will configure the server(s). Use the following task map to identify the tasks for preparing your network for DHCP.

Task	Description	Instructions
Map your network topology	Determine what services are available on the network and where they are located.	Mapping Your Network Topology
Determine the number of DHCP servers you need	Use the expected number of DHCP clients as a basis for determining the number of DHCP servers you need.	Determining the Number of DHCP Servers
Update system files and netmasks table	Reflect the network topology accurately.	Updating System Files and Netmask Tables

Mapping Your Network Topology

If you have not already done so, you should map the physical structure or layout of your network. Indicate the location of routers and clients, and the location of servers that provide network services. This map of your network topology can help you determine which server to use for DHCP services, and what configuration information the DHCP server can provide to clients.

See “Planning Your TCP/IP Network” in System Administration Guide, Volume 3 for more information about planning your network.

The DHCP configuration process can look up some network information from the server's system and network files. Updating System Files and Netmask Tables discusses these files. However, you might want to give clients other service information, which you must enter into the server's macros. As you examine your network topology, record the IP addresses of any servers you want your clients to know about. The following are some examples of network services you may have on your network that the DHCP configuration does not discover:

• Time server

• Log server

• Print server

• Install server

• Boot server

• Swap server

• X Window font server

• TFTP server

Network Topology to Avoid

DHCP does not work well in network environments where more than one IP network shares the same network hardware media, either through the use of multiple network hardware interfaces or multiple logical interfaces. When multiple IP networks run across the same physical LAN, a DHCP client's request arrives on all network hardware interfaces. This makes the client appear to be attached to all of the IP networks simultaneously.

DHCP must be able to determine the address of a client's network in order to assign an appropriate IP address to the client. If more than one network is present on the hardware media, the server cannot determine the client's network and cannot assign an IP address.

You can use DHCP on one of the networks, but not more than one. If this does not suit your needs, you must reconfigure the networks. Suggestions for reconfiguration include:

• Use variable length subnet masks (VLSM) to make better use of the IP address space you have, so you do not need to run multiple LANs on the same physical network. See RFC-1519 for more information on VLSM and Classless Inter-Domain Routing (CDIR).

• Configure the ports on your switches to assign devices to different physical LANs. This preserves the mapping of one LAN to one IP network required for Solaris DHCP. See the documentation for the switch for information about port configuration.

Determining the Number of DHCP Servers

The data store option you choose has a direct effect on the number of servers you must have to support your DHCP clients. The following table shows the maximum number of DHCP/BOOTP clients that can be supported by one DHCP server for each data store.

Table 8–1 Estimated Maximum Number of Clients

Data Store	Maximum Number of Clients
Text files	10,000
NIS+	40,000
Binary files	100,000

This maximum number is a general guideline, not an absolute number. A DHCP server's client capacity depends greatly on the number of transactions it must process per second. Lease times and usage patterns have a large effect on the number of clients that a server can support. For example, if leases are set to 12 hours and users turn their systems off at night and on at the same time the next morning, the server must handle transaction peaks each morning as many clients request leases simultaneously. The DHCP server can support fewer clients in such an environment compared to an environment with longer leases, or an environment that consists of constantly connected devices such as cable modems.

The section Choosing the Data Store compares data store options.

Updating System Files and Netmask Tables

During the configuration process, DHCP Manager or the dhcpconfig utility scans various system files on your server for information it can use to configure the server.

You must be sure the information in the system files is current before you run DHCP Manager or dhcpconfig to configure your server. If you notice errors after you configure the server, use DHCP Manager or dhtadm to modify the macros on the server.

The following table lists some of the information gathered during DHCP server configuration, and the sources for the information. Be sure this information is set correctly on the server before you configure DHCP on it. If you make changes to the system files after you configure the server, you should reconfigure the service to pick up the changes.

Table 8–2 Information for DHCP Configuration

Information	Source	Comments
Time zone	System date, time zone settings	The date and time zone are initially set during the Solaris installation. You can change the date by using the date command and change the time zone by editing the /etc/TIMEZONE file, which sets the TZ variable.
DNS parameters	/etc/resolv.conf	The DHCP server uses the /etc/resolv.conf file to look up DNS parameters such as DNS domain name and DNS server addresses. See System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for more information about resolv.conf.
NIS or NIS+ parameters	System domain name, nsswitch.conf, NIS, NIS+	The DHCP server uses the domainname command to obtain the domain name of the server system, and the nsswitch.conf file to determine where to look for domain-based information. If the server system is a NIS or NIS+ client, the DHCP server queries NIS or NIS+ services to get NIS/NIS+ server IP addresses.
Default router	System routing tables, user prompt	The DHCP server searches the network routing tables to find the default router for clients attached to the local network. For clients not on the same network, the DHCP server must prompt the administrator for the information.
Subnet mask	Network interface, netmasks table	The DHCP server looks to its own network interfaces to determine the netmask and broadcast address for local clients. If the request had been forwarded by a relay agent, the server looks up the subnet mask in the netmasks table on the relay agent's network.
Broadcast address	Network interface, netmasks table	For the local network, the DHCP server obtains the broadcast address by querying the network interface. For remote networks, the server uses the BOOTP relay agent's IP address and the remote network's netmask to calculate the broadcast address for the network.

Making Decisions for DHCP Server Configuration (Task Map)

This section discusses some of the decisions to make before you configure the first DHCP server on your network. Use this task map to identify the decisions you must make.

Task	Description	For Instructions
Select a server for DHCP	Determine if a server meets the system requirements to run the DHCP service.	Selecting a Server for DHCP
Choose a data store	Compare the data store choices to determine the best for your site.	Choosing the Data Store
Set a lease policy	Learn about IP address leases to help you determine appropriate leasing for your site.	Setting a Lease Policy
Select router address or router discovery	Determine whether DHCP clients use a specific router or router discovery	Determining Routers for DHCP Clients

Selecting a Server for DHCP

With your network topology in mind, you can use the following guidelines to select a host on which to set up a DHCP server.

The server must:

• Run the Solaris 2.6, Solaris 7, or Solaris 8 operating environment. You must install the Solaris 8 7/01 operating environment or a later version if you need to support a large number of clients.

• Be accessible to all the networks that have clients that will use DHCP, either directly on the network or through a BOOTP relay agent.

• Be configured to use routing.

• Have a correctly configured netmasks table that reflects your network topology.

Choosing the Data Store

You can choose to store the DHCP data in text files, binary files, or the NIS+ directory service. The following table summarizes the features of each type of data store, and recommends the environment to which each is best suited.

Table 8–3 Comparison of Data Stores

Data Store Type	Performance	Maintenance	Sharing	Recommended Environment
Binary files	High performance, high capacity.	Low-maintenance, no database servers required. Contents must be viewed with DHCP Manager or dhtadm and pntadm. Regular file backups suggested.	Containers cannot be shared among DHCP servers.	Midsize to large environments with many networks with thousands of clients per network. Useful for small to medium ISPs.
NIS+	Moderate performance and capacity, dependent upon NIS+ service's performance and capacity	DHCP server system must be configured as a NIS+ client. Requires NIS+ service maintenance. Contents must be viewed with DHCP Manager or dhtadm and pntadm. Regular backups with nisbackup suggested.	DHCP data is distributed in NIS+, multiple servers can access the same containers.	Small to midsize environments with up to 5000 clients per network.
Text files	Moderate performance, low capacity.	Low-maintanence, no database servers required. ASCII format is readable without DHCP Manager, dhtadm, or pntadm. Regular file backups suggested.	Containers can be shared among DHCP servers if DHCP data is stored on one file system that is exported though an NFS mount point.	Small environments with a few hundred to a thousand clients per network, less than 10,000 total clients.

Traditional NIS (as opposed to NIS+) is not offered as a data store option because it does not support fast incremental updates. If your network uses NIS, you should use text files or binary files for your data store.

Setting a Lease Policy

A lease specifies the amount of time the DHCP server grants permission to a DHCP client to use a particular IP address. During the initial server configuration, you must specify a site-wide lease policy to indicate the lease time and whether clients can renew their leases. The server uses the information you supply to set option values in the default macros it creates during configuration. You can set different lease policies for specific clients or type of clients, by setting options in configuration macros you create.

The lease time is specified as a number of hours, days, or weeks for which the lease is valid. When a client is assigned an IP address (or renegotiates a lease on an IP address it is already assigned), the lease expiration date and time is calculated by adding the number of hours in the lease time to the timestamp on the client's DHCP acknowledgment. For example, if the timestamp of the DHCP acknowledgment is September 16, 2001 9:15 A.M., and the lease time is 24 hours, the lease expiration time is September 17, 2001 9:15 A.M. The lease expiration time is stored in the client's DHCP network record, viewable in DHCP Manager or with pntadm.

The lease time value should be relatively small, so that expired addresses are reclaimed quickly, but large enough so that if your DHCP service becomes unavailable, the clients continue to function until the system(s) that run the DHCP service can be repaired. A rule of thumb is to specify a time that is two times the predicted down time of a server. For example, if it generally takes four hours to obtain and replace a defective part and reboot the server, you should specify a lease time of eight hours.

The lease negotiation option determines whether or not a client can renegotiate its lease with the server before the lease expires. If lease negotiation is allowed, the client tracks the time that remains in its lease, and when half the lease time is used, the client requests the DHCP server to extend its lease to the original lease time. It is useful to disable lease negotiation in environments where there are more systems than IP addresses, so the time limit is enforced on the use of IP addresses. If there are enough IP addresses, you should enable lease negotiation so you do not force a client to take down its network interface and obtain a new lease, which can interrupt the client's TCP connections (such as NFS and telnet sessions). You can enable lease negotiation site-wide during the server configuration, and for particular clients or types of clients through the use of the LeaseNeg option in configuration macros.

---

Note –

Systems that provide services on the network should retain their IP addresses, and should not be subject to short-term leases. You can use DHCP with such systems if you assign them reserved (manual) IP addresses, rather than IP addresses with permanent leases. This enables you to detect when the system's IP address is no longer in use.

---

Determining Routers for DHCP Clients

Clients use routers for any network communication beyond their local network, and they must know the IP addresses of these routers in order to use them.

When you configure a DHCP server, you must provide the IP address of a router the clients can use or, if you use DHCP Manager, you can specify that clients should find routers themselves with the router discovery protocol.

If clients on your network support router discovery, you should use router discovery protocol, even if there is only one router. Discovery enables a client to adapt easily to router changes in the network. For example, if a router fails and is replaced by one with a new address, clients can discover the new address automatically without having to obtain a new network configuration to get the new router address.

Making Decisions for IP Address Management (Task Map)

As part of the DHCP service setup, you determine several aspects of the IP addresses that the server is to manage. If your network needs more than one DHCP server, you must decide how to divide responsibility for the addresses so you can assign some to each server. The following task map can help you make IP address management decisions.

Task	Description	Information
Specify what addresses the server should manage	Determine how many addresses you want the DHCP server to manage, and what those addresses are.	Number and Ranges of IP Addresses
Decide if server should automatically generate host names for clients	Learn about client host name generation and decide whether to use it.	Client Host Name Generation
Determine what configuration macro to assign to clients	Learn about client configuration macros so you can select an appropriate macro for clients.	Default Client Configuration Macros
Determine lease types to use	Learn about lease types to help you determine what type is best for your DHCP clients	Dynamic and Permanent Lease Type

Number and Ranges of IP Addresses

During the initial server configuration, DHCP Manager allows you to add one block, or range, of IP addresses under DHCP management by specifying the total number of addresses and the first address in the block. DHCP Manager adds a list of contiguous addresses from this information. If you have several blocks of noncontiguous addresses, you can add the others by running DHCP Manager's Address Wizard again, after the initial configuration.

Before you configure your IP addresses, know how many addresses are in the initial block of addresses you want to add and the IP address of the first address in the range.

Client Host Name Generation

The dynamic nature of DHCP means that an IP address is not permanently associated with the host name of the system that is using it. The DHCP management tools can generate a client name to associate with each IP address if you select this option. The client names consist of a prefix, or root name, plus a dash and a number assigned by the server. For example, if the root name is charlie, the client names will be charlie-1, charlie-2, charlie-3, and so on.

By default, generated client names begin with the name of the DHCP server that manages them. This is useful in environments that have more than one DHCP server because you can quickly see in the DHCP network tables which clients any given DHCP server manages. However, you can change the root name to any name you choose.

Before you configure your IP addresses, decide if you want the management tools to generate client names, and if so, what root name to use for the names.

The generated client names can be mapped to IP addresses in /etc/inet/hosts, DNS, or NIS+ if you specify this at configuration. See Client Host Name Registration for more information.

Default Client Configuration Macros

In Solaris DHCP, a macro is a collection of network configuration options and their assigned values. The DHCP server uses macros to determine what network configuration information to send to a DHCP client.

When you configure the DHCP server, the management tools gather information from system files and directly from you through prompts or command-line options you specify. With this information, the management tools create the following macros:

• Network address macro, named to match the IP address of the client network. The macro contains information needed by any client that is part of the network, such as subnet mask, network broadcast address, default router or router discovery token, and NIS/NIS+ domain and server if the server uses NIS/NIS+. Other options applicable to your network might be included.

• Locale macro, named Locale. The macro contains the offset (in seconds) from Universal Time to specify the time zone.

• Server macro, named to match the server's host name. The macro contains information about the lease policy, time server, DNS domain, and DNS server, and possibly other information that the configuration program was able to obtain from system files. This macro includes the Locale macro.

The network address macro is automatically processed for all clients located on that network. The locale macro is included in the server macro, so it is processed when the server macro is processed.

When you configure IP addresses for the first network, you must select a client configuration macro to be used for all DHCP clients using the addresses you are configuring. By default, the server macro is selected because it is contains information needed by all clients that use this server. Clients receive the options contained in the network address macro before those in the server macro. See Order of Macro Processing for more information about the order in which macros are processed.

Dynamic and Permanent Lease Type

The lease type determines if the lease policy applies to the addresses you are configuring. During initial server configuration, DHCP Manager allows you to select either dynamic or permanent leases for the addresses you are adding. If you configure with the dhcpconfig command, leases are dynamic.

When an address has a dynamic lease, the DHCP server can manage the address by allocating it to a client, extending the lease time, detecting when it is no longer in use, and reclaiming it. When an address has a permanent lease, the DHCP server can only allocate it to a client, after which the client owns the address until the client explicitly releases it. When the address is released, the server can assign it to another client. The address is not subject to the lease policy as long as it is configured with a permanent lease type.

When you configure a range of IP addresses, the lease type you select applies to all the addresses in the range. To get the most benefit from DHCP, you should use dynamic leases for most of the addresses. You can later modify individual addresses to make them permanent if necessary, but the total number of permanent leases should be kept to a minimum.

Reserved Addresses and Lease Type

Addresses can be reserved by manually assigning them to particular clients. A reserved address can have a permanent or dynamic lease associated with it. When a reserved address is assigned a permanent lease:

• The address can be allocated only to the client that is bound to the address

• The DHCP server cannot allocate the address to another client

• The address cannot be reclaimed by the DHCP server

If a reserved address is assigned a dynamic lease, the address can be allocated only to the client that is bound to the address, but the client must track lease time and negotiate for a lease extension as if the address were not reserved. This allows you to track when the client is using the address by looking at the network table.

You cannot create reserved addresses for all the IP addresses during the initial configuration because they are intended to be used sparingly for individual addresses.

Planning for Multiple DHCP Servers

If you want to configure more than one DHCP server to manage your IP addresses, consider the following guidelines:

• Divide the pool of IP addresses so that each server is responsible for a range of addresses and there is no overlap of responsibility.

• Choose NIS+ as your data store, if available. If not, choose text files and specify a shared directory for the absolute path to the data store. The binary files data store cannot be shared.

• Configure each server separately so that address ownership is allocated correctly and that server-based macros can be automatically created.

• Set up the servers to scan the options and macros in the dhcptab table at specified intervals so they each are using the latest information. You can do this by using DHCP Manager to schedule automatic reading of dhcptab as described in Customizing DHCP Service Performance Options.

• Be sure all clients can access all DHCP servers so that the servers can support one another. If a client has a valid IP address lease, and is either trying to verify its configuration or extend the lease, but the server that owns the client's address is not reachable, another server can respond to the client after the client has attempted to contact the primary server for 20 seconds. If a client requests a specific address, and the server that owns the address is not available, one of the other servers handles the request. The client receives a different address from the one requested.

Planning for Remote Network Configuration

After the initial configuration, you can place IP addresses in remote networks under DHCP management. However, because the system files are not local to the server, DHCP Manager and dhcpconfig cannot look up information to provide default values, so you must provide the information. Before you attempt to configure a remote network, be sure you know the following information:

• Remote network's IP address.

• Subnet mask of the remote network – This can be obtained from the netmasks table in the name service. If the network uses local files, look in /etc/netmasks on a system in the network. If the network uses NIS+, use the command niscat netmasks.org_dir. If the network uses NIS, use the command ypcat -k netmasks.byaddr. Make sure the netmasks table contains all the topology information for all the subnets you want to manage.

• Network type – Do the clients connect to the network through a local area network (LAN) connection or point-to-point protocol (PPP)?

• Routing – Can the clients use router discovery? If not, you must determine the IP address of a router they can use.

• NIS domain and NIS servers, if applicable.

• NIS+ domain and NIS+ servers, if applicable.

See Adding DHCP Networks for the procedure for adding DHCP networks.

Selecting the Tool for Configuring DHCP

After you have gathered information and made decisions as outlined in the previous sections, you are ready to configure a DHCP server. You can use the graphical DHCP Manager or the command-line utility dhcpconfig to configure a server. DHCP Manager lets you select options and enter data that is then used to create the dhcptab and network tables used by the DHCP server. The dhcpconfig utility requires you to use command-line options to specify data.

DHCP Manager Features

DHCP Manager, a Java-based graphical tool, provides a DHCP Configuration Wizard, which starts automatically the first time you run DHCP Manager on a system that is not configured as a DHCP server. The DHCP Configuration Wizard provides a series of dialog boxes that prompt you for the essential information required to configure a server: data store format, lease policy, DNS/NIS/NIS+ servers and domains, and router addresses. Some of the information is obtained by the wizard from system files, and you only need to confirm that the information is correct, or correct it if necessary.

When you progress through the dialog boxes and approve the information, and the DHCP server daemon starts on the server system, you are prompted to start the Add Addresses Wizard to configure IP addresses for the network. Only the server's network is configured for DHCP initially, and other server options are given default values. You can run DHCP Manager again after the initial configuration is complete to add networks and modify other server options.

dhcpconfig Features

The dhcpconfig utility supports a list of options that allow you to configure and unconfigure a DHCP server, as well as convert to a new data store and import/export data to and from other DHCP servers. When you use the dhcpconfig utility to configure a DHCP server, it obtains information from the system files discussed in Updating System Files and Netmask Tables. You cannot view and confirm the information it obtains from system files as you can with DHCP Manager, so it is important that the system files be updated before you run dhcpconfig. You can also use command-line options to override the values dhcpconfig would obtain by default from system files. The dhcpconfig command can be used in scripts. Please see the dhcpconfig man page for more information.

Comparison of DHCP Manager and dhcpconfig

The following table summarizes the differences between the two server configuration tools.

Table 8–4 Comparison of DHCP Manager and the dhcpconfig Command

Feature	DHCP Manager	dhcpconfig With Options
Network information gathered from system.	Allows you to view the information gathered from system files, and change it if needed.	You can specify the network information with command-line options.
Configuration experience for user.	Speeds the configuration process by omitting prompts for nonessential server options by using default values for them. Allows you to change nonessential options after initial configuration.	Fastest configuration process, but user may need to specify values for many options.

The next chapter includes procedures you can use to configure your server with both DHCP Manager and the dhcpconfig utility.