Chapter 10 Administering DHCP (Task)

This chapter describes tasks you might find useful when you administer the Solaris DHCP service. The chapter includes tasks for the server, BOOTP relay agent, and client. Each task includes a procedure to help you perform the task in DHCP Manager and a procedure for the equivalent task with DHCP command-line utilities. DHCP command-line utilities are more fully documented in man pages.

You should have already completed the initial configuration of your DHCP service and initial network before you use this chapter. Chapter 9, Configuring DHCP Service (Task) discusses DHCP configuration.

The chapter contains the following information:

• DHCP Manager

• Setting Up User Access to DHCP Commands

• Starting and Stopping the DHCP Service

• Modifying DHCP Service Options (Task Map)

• Adding, Modifying, and Removing DHCP Networks (Task Map)

• Supporting BOOTP Clients with DHCP Service (Task Map)

• Working With IP Addresses in the DHCP Service (Task Map)

• Working With DHCP Macros (Task Map)

• Working With DHCP Options (Task Map)

• Supporting Solaris Network Installation with the DHCP Service (Task Map)

• Supporting Remote Boot and Diskless Boot Clients (Task Map)

• Setting Up DHCP Clients as NIS+ Clients

• Converting to a New Data Store

• Moving Configuration Data Between DHCP Servers (Task Map)

DHCP Manager

DHCP Manager is a graphical interface you can use to perform administration tasks on the DHCP service.

The DHCP Manager Window

The DHCP Manager window's appearance differs, depending on whether the server on which it is running was configured as a DHCP server or a BOOTP relay agent.

When the server is configured as a DHCP server, DHCP Manager uses a tab-based window, in which you select a tab for the type of information you want to work with. DHCP Manager features the following tabs:

• Addresses – Lists all networks and IP addresses placed under DHCP management. From the Addresses tab, you can add or delete networks and add or delete IP addresses individually or in blocks. You can also modify the properties of individual networks or IP addresses or make the same property modifications for a block of addresses simultaneously. When you start DHCP Manager, it opens on the Addresses tab.

• Macros – Lists all macros available in the DHCP configuration database (dhcptab) and the options contained within them. From the Macros tab, you can create or delete macros, and modify them by adding options and providing values for the options.

• Options – Lists all options that have been defined for this DHCP server. Options listed on this tab are not the standard ones defined in the DHCP protocol. The options are extensions to the standard options, and have a class of Extended, Vendor, or Site. Standard options cannot be changed in any way so they are not listed here.

The following figure shows the DHCP Manager window as it appears when you start it on a DHCP server.

Figure 10–1 DHCP Manager on a DHCP Server System

When the server is configured as a BOOTP relay agent, the DHCP Manager window does not show these tabs because the BOOTP relay agent does not need any of this information. You can only modify the BOOTP relay agent's properties and stop/start the DHCP daemon with DHCP Manager. The following figure shows the DHCP Manager window as it appears when you start it on a system configured as a BOOTP relay agent.

Figure 10–2 DHCP Manager on a BOOTP Relay Agent System

DHCP Manager Menus

DHCP Manager menus include:

• File – Exit DHCP Manager

• Edit – Perform management tasks upon networks, addresses, macros, and options

• View – Change the look of the tab currently selected

• Service – Manage the DHCP daemon and data store.

• Help – Open your web browser and display help for DHCP Manager

When DHCP Manager runs on a BOOTP relay agent, the Edit and View menus are disabled.

All DHCP service management activities are accomplished through the Edit and Service menus. You use the commands in the Edit menu to create, delete, and modify networks, addresses, macros, and options, depending on which tab is selected. When the Addresses tab is selected, the Edit menu also lists wizards, which are sets of dialogs that make it easy to create networks and multiple IP addresses. The Service menu lists commands that enable you to manage the DHCP daemon. You can start/stop, enable/disable, modify the server configuration, and unconfigure the server. The Service menu also lists commands that enable you to convert the data store and export and import data on the server.

Starting and Stopping DHCP Manager

You must run DHCP Manager on a DHCP server system as superuser, but you can display it remotely on another UNIX system using the X Window remote display feature.

How to Start and Stop DHCP Manager

1. (Optional) Become superuser on the DHCP server system.

2. If you are logged in to the DHCP server system remotely, you can display DHCP Manager on your local system as follows.

   1. Type the following on the local system:

      # xhost +server-name

   2. Type the following on the remote DHCP server system:

      # DISPLAY=local-hostname;export DISPLAY

3. Type the following command:

   # /usr/sadm/admin/bin/dhcpmgr &

   The DHCP Manager window opens, displaying the Addresses tab if the server is configured as a DHCP server, or no tabs if the server is configured as a BOOTP relay agent.

4. To stop the DHCP Manager, choose Exit from the File menu.

   The DHCP Manager window closes.

Setting Up User Access to DHCP Commands

To allow users other than root to execute dhcpconfig, dhtadm, and pntadm commands without first becoming superuser, you must set up role-based access control (RBAC) for those commands. RBAC enables you to more precisely define which users can perform which tasks on the system. See rbac(5), exec_attr(4), and user_attr(4) man pages for more information.

The following procedure explains how to assign a user the DHCP Management profile, which enables the user to execute the DHCP commands.

How to Grant Users Access to DHCP Commands

1. Become superuser on the DHCP server system.

2. Edit the file /etc/user_attr to add an entry of the following form for each user you want to be able to manage the DHCP service:

   username::::type=normal;profiles=DHCP Management

   For example, for user ram, add the following entry:

   ram::::type=normal;profiles=DHCP Management

Starting and Stopping the DHCP Service

The starting and stopping of the DHCP service encompasses several degrees of action you can take to affect the operation of the DHCP daemon. You must understand what it means to start/stop, enable/disable, and configure/unconfigure the DHCP service in order to select the correct procedure to obtain the result you want. The terms are explained below.

• Start, stop, and restart commands affect the daemon only at the current session. For example, if you stop the DHCP service, the daemon terminates but restarts when you reboot the system. DHCP data tables are not affected when you stop the service.

• Enable and disable commands affect the daemon for current and future sessions. If you disable the DHCP service, the currently running daemon terminates and does not start when you reboot the server. You must enable the DHCP daemon for the automatic start at system boot to occur. DHCP data tables are not affected. You can disable and enable the DHCP service only from DHCP Manager.

• Unconfigure command shuts down the daemon, prevents the daemon from starting on system reboot, and enables you to remove the DHCP data tables. Unconfiguration is described in Chapter 9, Configuring DHCP Service (Task).

If a server has multiple network interfaces and you do not want to provide DHCP services on all the networks, see Specifying Network Interfaces to Monitor for DHCP Service.

This section provides the procedures to help you start and stop the DHCP service, and enable and disable it.

How to Start and Stop the DHCP Service (DHCP Manager)

1. Become superuser on the DHCP server system.

2. Start DHCP Manager.

   See How to Start and Stop DHCP Manager for the procedure.

3. Select one of the following operations:

   1. Choose Start from the Service menu to start the DHCP service.

   2. Choose Stop from the Service menu to stop the DHCP service.

      The DHCP daemon stops until it is manually started again, or the system reboots.

   3. Choose Restart from the Service menu to stop the DHCP service and immediately restart it.

How to Start and Stop the DHCP Service (Command Line)

1. Become superuser on the server system.

2. Choose one of the following operations:

   1. To start the DHCP service, type the following command:

      # /etc/init.d/dhcp start

      The DHCP daemon starts, using the configuration parameters set in /etc/inet/dhcpsvc.conf.

   2. To stop the DHCP service, type the following command:

      # /etc/init.d/dhcp stop

      The DHCP daemon stops until it is manually started again, or the system reboots.

How to Enable and Disable the DHCP Service (DHCP Manager)

1. Start DHCP Manager.

2. Choose one of the following operations:

   1. Choose Enable from the Service menu to start the DHCP service immediately and configure it for automatic startup when the system boots.

   2. Choose Disable from the Service menu to stop the DHCP service immediately and prevent it from starting automatically when the system boots.

Modifying DHCP Service Options (Task Map)

You can change values for some additional features of the DHCP service, some of which were not offered during the initial configuration with DHCP Manager. If you configured your server with dhcpconfig, the server is using default values for these options. You can use the Modify Service Options dialog box in DHCP Manager or specify options on the in.dhcpd command to change service options.

The following task map shows the tasks related to service options and the procedures to use:

The following figure shows DHCP Manager's Modify Service Options dialog box.

Figure 10–3 Modify Service Options Dialog Box

Changing DHCP Logging Options

The DHCP service can log DHCP service messages and DHCP transactions to syslog. See thesyslogd(1M) andsyslog.conf(4) man pages for more information about syslog.

DHCP service messages logged to syslog include:

• Error messages, which notify the administrator of conditions that prevent the DHCP service from fulfilling a request by a client or by the administrator.

• Warnings and notices, which notify the administrator of conditions that are abnormal, but do not prevent the DHCP service from fulfilling a request.

You can increase the amount of information reported by using the verbose option for the DHCP daemon. Verbose message output can help you troubleshoot DHCP problems. See How to Generate Verbose DHCP Log Messages (DHCP Manager).

Another useful troubleshooting technique is transaction logging. Transactions provide information about every interchange between a DHCP server or BOOTP relay and clients. DHCP transactions include:

• ASSIGN – IP address assignment

• ACK – Server acknowledges that client accepts the offered IP address, and sends configuration parameters

• EXTEND – Lease extension

• RELEASE – IP address release

• DECLINE – Client is declining address assignment

• INFORM – Client is requesting network configuration parameters but not an IP address

• NAK – Server does not acknowledge a client's request to use a previously used IP address

• ICMP_ECHO – Server detects potential IP address is already in use by another host.

BOOTP relay transactions include:

• RELAY-CLNT – Message being relayed from the DHCP client to a DHCP server

• RELAY–SRVR – Message being relayed from the DHCP server to the DHCP client

Transaction logging is disabled by default. When enabled, transaction logging uses the local0 syslog facility by default. DHCP transaction messages are generated with a syslog severity level of notice, so by default, transactions are logged to the file where other notices are logged. However, because they use a local facility, the transaction messages can be logged separately from other notices if you edit the syslog.conf file to specify a separate log file.

You can disable or enable transaction logging, and specify a different syslog facility, from 0 through 7, as explained in How to Enable and Disable DHCP Transaction Logging (DHCP Manager). If you edit the server system's syslog.conf file, you can also instruct syslogd to store the DHCP transaction messages in a separate file, as explained in How to Log DHCP Transactions to a Separate syslog File.

How to Generate Verbose DHCP Log Messages (DHCP Manager)

1. Choose Modify from the Service menu.

2. Select Verbose Log Messages.

3. Select Restart Server if it is not already selected.

4. Click OK.

   The daemon runs in verbose mode for this session and each subsequent session until you reset this option. Verbose mode can reduce daemon efficiency because of the time taken to display messages.

How to Generate Verbose DHCP Log Messages (Command Line)

1. Become superuser on the DHCP server system.

2. Type the following commands to stop the DHCP daemon and restart it in verbose mode:

   # /etc/init.d/dhcp stop # /usr/lib/inet/in.dhcpd -v options

   where options are any other options you normally use to start the daemon.

   The daemon runs in verbose mode for this session only.

   Verbose mode can reduce daemon efficiency because of the time taken to display messages.

How to Enable and Disable DHCP Transaction Logging (DHCP Manager)

This procedure enables/disables transaction logging for all subsequent DHCP server sessions.

1. Choose Modify from the Service menu.

2. Select Log Transactions to Syslog Facility.

   To disable transaction logging, deselect this option.

3. (Optional) Select a local facility from 0 to 7 to use for logging transactions.

   By default, DHCP transactions are logged to the location where system notices are logged, which depends on how syslogd is configured. If you want the DHCP transactions to be logged to a file separate from other system notices, see How to Log DHCP Transactions to a Separate syslog File.

   Message files can quickly become very large when transaction logging is enabled.

4. Select Restart Server if it is not already selected.

5. Click OK.

   The daemon will log transactions to the selected syslog facility for this session and each subsequent session until you disable it in this dialog box.

How to Enable and Disable DHCP Transaction Logging for Current Session (Command Line)

1. Become superuser on the DHCP server system.

2. Type the following commands to enable logging for the current session:

   # /etc/init.d/dhcp stop # /usr/lib/inet/in.dhcpd -l syslog-local-facility

   where syslog-local-facility is a number from 0 through 7. If you omit this option, 0 is used by default. See How to Enable and Disable DHCP Transaction Logging (DHCP Manager).

   ---

   Note –

   To disable transaction logging, omit the -l option when starting in.dhcpd.

   ---

   By default, DHCP transactions are logged to the location where system notices are logged, which depends on how syslogd is configured. If you want the DHCP transactions to be logged to a file separate from other system notices, see How to Log DHCP Transactions to a Separate syslog File.

   Message files can quickly become very large when transaction logging is enabled.

How to Log DHCP Transactions to a Separate syslog File

1. Become superuser on the DHCP server system.

2. Edit the /etc/syslog.conf file on the server system and add a line of the following format:

   localn.notice path-to-logfile

   where n is the syslog facility number you specified for transaction logging, and path-to-logfile is the complete path to the file to use for logging transactions.

   For example, you might add the following line:

   local0.notice /var/log/dhcpsrvc

   See the syslog.conf(4) man page for more information about the syslog.conf file.

Enabling Dynamic DNS Updates by DHCP Server

If a host name is mapped to the IP address leased to a DHCP client and the DHCP server has been configured to supply host names, the DHCP server will inform the client of the name it has been assigned. Alternatively, the DHCP server may be configured so that DHCP clients may supply their own host names and the DHCP server will attempt DNS updates on their behalf.

DNS provides basic name-to-address and address-to-name services for the Internet. Once a DNS update is made, other systems may refer to the DHCP client system by name.

You can enable the DHCP service to update the DNS service with the host names of DHCP clients that supply their own host names. When a system's name is registered with DNS, the system is visible outside its domain. In order for the DNS update feature to work, the DNS server, DHCP server, and DHCP client must all be set up correctly, and the requested name must not be in use by another system in the domain.

The DHCP server's DNS update feature works if all the following are true:

• DNS server supports RFC 2136.

• DNS software that is BIND-based, whether on the DHCP server system or the DNS server system, must be v8.2.2, patch level 5 or newer.

• DNS server is configured to accept dynamic DNS updates from the DHCP server.

• DHCP server is configured to make dynamic DNS updates.

• DNS support is configured for the DHCP client's network on the DHCP server.

• DHCP client is configured to supply a requested host name in its DHCP request message.

• Requested host name corresponds to a DHCP-owned address or has no corresponding address.

How to Enable Dynamic DNS Updating for DHCP Clients

Be aware that dynamic DNS updates are by nature a security risk.

By default, the Solaris DNS daemon (in.named) does not allow dynamic updates. Authorization for dynamic DNS updates is granted if the requesting host's IP address is assigned to the allow-update keyword in the appropriate zones of the named.conf configuration file on the DNS server system. No other security is provided. You must carefully weigh the convenience of this facility for users against the security risk created when you enable dynamic DNS updates.

1. At the DNS server, edit the /etc/named.conf file as root.

2. Find the zone section for the appropriate domain and add the DHCP server's IP addresses to the allow-update keyword.

   For example, if the DHCP server resides at addresses 10.0.0.1 and 10.0.0.2, a named.conf file for the dhcp.domain.com zone would be modified as follows:

   zone "dhcp.domain.com" in { type master; file "db.dhcp"; allow-update { 10.0.0.1; 10.0.0.2; }; }; zone "10.IN-ADDR.ARPA" in { type master; file "db.10"; allow-update { 10.0.0.1; 10.0.0.2; }; };

   Note that allow-update for both zones must be enabled to allow the DHCP server to update both A and PTR records on the DNS server.

3. On the DHCP server, start DHCP Manager.

4. Choose Modify from the Service menu.

   The Modify Service Options dialog box opens.

5. Select Update DNS Host Information Upon Client Request.

6. Specify the number of seconds to wait for a response from the DNS server before timing out, then click OK.

   The default value should be adequate. If you have timeout problems, you can increase the value later.

7. Click the Macros tab and ensure that the correct DNS domain is specified.

   The DNSdmain option must be passed with the correct domain name to any client that expects dynamic DNS update support. By default, DNSdmain is specified in the server macro, which is used as the configuration macro bound to each IP address.

8. Set up the DHCP client to specify its host name when requesting DHCP service.

   If you use the Solaris DHCP client, see How to Enable a Solaris Client to Request Specific Host Name. If your client is not a Solaris DHCP client, see the documentation for your DHCP client for information about how to do this.

How to Enable a Solaris Client to Request Specific Host Name

1. On the client system, edit the /etc/default/dhcpagent file as root.

2. Find the keyword REQUEST_HOSTNAME in the /etc/default/dhcpagent file and modify it as follows:

   REQUEST_HOSTNAME=yes

   If there is a comment sign (#) in front of the keyword, remove the #. If the keyword is not present, insert it.

3. Edit the /etc/hostname.interface file on the client system and add the following line:

   inet hostname
   

   where hostname is the name you want the client to use.

4. As root, type the following commands to have the client perform a full DHCP negotiation upon rebooting:

   # pkill dhcpagent # rm /etc/dhcp/interface.dhc # reboot

   The DHCP server makes sure that the host name is not in use by another system on the network before the server assigns it to the client. Depending how it is configured, the DHCP server may update name services with the client's host name.

Customizing DHCP Service Performance Options

You can change options that affect the performance of the DHCP service. These options are described in the following table.

The following procedures describe how to change these options.

How to Customize DHCP Server Performance Options (DHCP Manager)

1. Choose Modify from the Service menu.

2. To change the number of BOOTP relay agents a request can pass through, specify a different Maximum Number of Relay Agent Hops.

3. To have the DHCP server verify that an IP address is not in use before it offers the address to a client, select Detect Duplicate IP Addresses.

4. To have the DHCP server read dhcptab at specified intervals, select Reload dhcptab Every n Minutes, and type the number of minutes for the interval.

5. To change the length of time the server holds an IP address open after it makes an offer, type the number of seconds in the field Cache Offers for n Seconds.

6. Select Restart Server if it is not already selected.

7. Click OK.

How to Customize DHCP Server Performance Options (Command Line)

If you change options with this procedure, the changed options affect only the current server session. If the DHCP server system reboots, the DHCP server starts with the settings specified during server configuration. If you want settings to apply to all future sessions, you must make changes using DHCP Manager.

1. Become superuser on the DHCP server system.

2. Type the following command:

   # /etc/init.d/dhcp stop # /usr/lib/inet/in.dhcpd options

   where options are any of the following:
   -h relay-hops	Specifies the maximum number of relay agent hops that can occur before the daemon drops the DHCP/BOOTP datagram.
   -n	Disables automatic duplicate IP address detection. This is not recommended.
   -t dhcptab_rescan_interval	Specifies the interval in minutes that the DHCP server should use to schedule the automatic rereading of the dhcptab information.
   -o seconds	Specifies the number of seconds the DHCP server should cache the offers it has extended to discovering DHCP clients. The default setting is 10 seconds.

   For example, the following command sets the hop count to 2, disables duplicate IP address detection, sets the rescan interval to 30 minutes, and sets the offer time to 20 seconds.

   # /usr/lib/inet/in.dhcp -h 2 -n -t 30 -o 20

Adding, Modifying, and Removing DHCP Networks (Task Map)

When you configure a DHCP server, you must also configure at least one network in order to use the DHCP service. You can add more networks at any time.

The following task map lists tasks you may need to perform when working with DHCP networks and the procedures used to carry them out.

Specifying Network Interfaces to Monitor for DHCP Service

By default, both dhcpconfig and DHCP Manager's Configuration Wizard configure the DHCP server to monitor all the server system's network interfaces. If you add a new network interface to the server system, the DHCP server automatically monitors the new interface when you boot the system. You can then add any networks that will be monitored through the network interface.

However, DHCP Manager also allows you to specify which network interfaces the DHCP service should monitor and which it should ignore. You might want to ignore an interface if you do not want to offer DHCP service on that network.

If you specify that any interface should be ignored, and then install a new interface, the DHCP server ignores the new interface unless you add it to the server's list of monitored interfaces. You can specify interfaces with DHCP Manager.

This section includes a procedure that enables you to specify which network interfaces DHCP should monitor, and which to ignore. The procedure uses the Interfaces tab of the DHCP Manager's Modify Service Options dialog box, which is shown in the following figure.

Figure 10–4 Interfaces Tab of Modify Service Options Dialog Box

How to Specify Network Interfaces for DHCP Monitoring (DHCP Manager)

1. Choose Modify from the Service menu.

   The Modify Service Options dialog box is displayed.

2. Select the Interfaces tab.

3. Select the appropriate network interface and click the arrow buttons to move the interface to the Monitored Interfaces list or the Ignored Interfaces list.

   For example, to ignore an interface, select it in the Monitored Interfaces list and click the right arrow button to move the interface in the Ignored Interfaces list.

4. Make sure Restart Server is selected and click OK.

Adding DHCP Networks

When you use DHCP Manager to configure the server, the first network (usually the local one on the server system's primary interface) is also configured at the same time. If you want to configure additional networks, use the DHCP Network Wizard in DHCP Manager.

If you use dhcpconfig -D to configure the server, you must manually configure all networks that will be served by the DHCP service. See How to Add a DHCP Network (dhcpconfig) for more information.

The following figure shows the initial dialog box for the DHCP Network Wizard in DHCP Manager.

Figure 10–5 DHCP Manager's Network Wizard

When you configure a new network, DHCP Manager creates the following components:

• Network table in the data store. The new network is shown in the network list on the Addresses tab of DHCP Manager.

• Network macro that contains information needed by clients that reside on this network. The network macro's name matches the IP address of the network. The network macro is added to the dhcptab in the data store.

How to Add a DHCP Network (DHCP Manager)

1. Click the Addresses tab in DHCP Manager.

   Any networks already configured for DHCP service are listed.

2. Choose Network Wizard from the Edit menu.

3. Select options or type requested information based on the decisions you made during the planning phase.

   Planning is described in Planning for Remote Network Configuration.

   If you have difficulty with the wizard, click Help in the wizard window to open your web browser and display help for the DHCP Network Wizard.

4. Click Finish to complete the network configuration when you have finished entering the requested information.

   The Network Wizard creates a network macro whose name matches the IP address of the network. If you click the Macros tab in the DHCP Manager window and select the network macro, you can confirm that the information you provided in the wizard has been inserted as values for options contained in the macro.

   The Network Wizard creates an empty network table, which is listed in the left pane of the window. You must add addresses for the network before the network's IP addresses can be managed under DHCP. See Adding Addresses to the DHCP Service for more information.

How to Add a DHCP Network (dhcpconfig)

1. Become superuser or a user assigned to the DHCP Management profile .

2. Type the following command on the DHCP server system:

   # /usr/sbin/dhcpconfig -N network_address

   where network_address is the IP address of the network you want to add to the DHCP service. See the dhcpconfig man page for suboptions you can use with the -N option.

   If you do not use suboptions, dhcpconfig uses network files to obtain information it needs about the network.

3. Add IP addresses for the network so clients on the network can obtain addresses.

   See Adding Addresses to the DHCP Service.

Modifying DHCP Network Configuration

After you add a network to the DHCP service, you can modify the configuration information you originally supplied by modifying the network macro used to pass information to the clients on the network.

The following figure shows the Macros tab of the DHCP Manager.

Figure 10–6 DHCP Manager's Macros Tab

How to Modify Configuration of a DHCP Network (DHCP Manager)

1. Select the Macros tab.

   All macros defined for this DHCP server are listed in the left pane.

2. Select the network macro whose name matches the network whose configuration you want to change.

   The network macro name is the network IP address.

3. Choose Properties from the Edit menu.

   The Macro Properties dialog box displays a table of the options included in the macro.

4. Select the option you want to modify.

   The option name and value are displayed in text fields near the top of the dialog box.

5. Type the new value for the option and click Modify.

   You can also add options here by clicking Select in the dialog box. See Modifying DHCP Macros for more general information about modifying macros.

6. Select Notify DHCP Server of Change and click OK.

   The change is made to the dhcptab and the DHCP server is signaled to reread the dhcptab and put the changes into effect.

How to Modify Configuration of a DHCP Network (dhtadm)

1. Determine which macro includes information for all clients of the network.

   The network macro's name matches the network IP address.

   If you don't know which macro includes this information, you can display the dhcptab database to list all macros by using the command dhtadm -P.

2. Type a command of the following format to change the value of the option you want to change:

   # dhtadm -M -m macro-name -e 'symbol=value'

   For example, to change the 10.25.62.0 macro's lease time to 57600 seconds and NIS domain to sem.example.com, type the following commands:

   # dhtadm -M -m 10.25.62.0 -e 'LeaseTim=57600'

   # dhtadm -M -m 10.25.62.0 -e 'NISdmain=sem.example.com'

3. Type the following command as root to make the DHCP daemon reread dhcptab:

   # pkill -HUP in.dhcpd

Removing DHCP Networks

DHCP Manager enables you to remove multiple networks at once. You have the option to automatically remove the hosts table entries associated with the DHCP-managed IP addresses on those networks as well. The following figure shows DHCP Manager's Delete Networks dialog box.

Figure 10–7 Delete Networks Dialog Box

The pntadm command requires you to delete each IP address entry from a network before you delete that network. You can delete only one network at a time.

How to Remove a DHCP Network (DHCP Manager)

1. Select the Addresses tab.

2. Choose Delete Networks from the Edit menu.

   The Delete Networks dialog box opens.

3. In the Keep Networks list, select the networks you want to delete.

   Press the Control key while you click with the mouse to select multiple networks, or press the Shift key while you click to select a range of networks.

4. Click the right arrow button to move the selected networks to the Delete Networks list.

5. If you want to remove the host table entries for the DHCP–managed addresses on this network, select Delete Host Table Entries.

   Note that this does not delete the host registrations at the DNS server for these addresses. It affects only the local name service.

6. Click OK.

How to Remove a DHCP Network (pntadm)

Note that this procedure deletes the addresses on the network before removing the network. This ensures that the host names are removed from the hosts file or database.

1. On the server system, become superuser or a user assigned to the DHCP Management profile.

2. Type a command following this format to remove an IP address and its host name from the name service:

   # pntadm -D -y IP-address

   For example, to remove address 10.25.52.1, type the following command:

   # pntadm -D -y 10.25.52.1

   The -y option specifies to delete the host name.

3. Repeat the pntadm -D -y command for each address in the network.

   You might want to create a script to do this if you are deleting many addresses.

4. After all addresses are deleted, type the following command to delete the network from the DHCP service.

   # pntadm -R network-IP-address

   For example, to remove network 10.25.52.0, type the following command:

   # pntadm -R 10.25.52.0

   See the pntadm man page for more information about using pntadm.

Supporting BOOTP Clients with DHCP Service (Task Map)

To support BOOTP clients on your DHCP server, you must set up your DHCP server to be BOOTP compatible. You can register BOOTP clients in the DHCP server's network table or reserve a number of IP addresses for allocation to BOOTP clients, depending how you set up BOOTP compatibility.

BOOTP addresses are permanently assigned, whether or not you explicitly assign them a permanent lease.

The following task map lists tasks you may need to perform to support BOOTP clients and the procedures used to carry them out.

How to Set Up Support of Any BOOTP Client (DHCP Manager)

1. Select Modify from the Service menu.

   The Modify Service Options dialog box opens.

2. In the BOOTP Compatibility section of the dialog box, select Automatic.

3. Select Restart Server, if it is not already selected.

4. Click OK.

5. Select the Addresses tab in DHCP Manager.

6. Select addresses that you want to reserve for BOOTP clients.

   Select a range of addresses by clicking the first address, pressing the Shift key, and clicking the last address.

   Select multiple non-concurrent addresses by pressing the Control key while clicking each address.

7. Select Properties from the Edit menu.

   The Modify Multiple Addresses dialog box opens.

8. In the BOOTP section, select Assign All Addresses Only to BOOTP Clients.

   All other options should be set to Keep Current Settings.

9. Click OK.

   Any BOOTP client can now obtain an address from this DHCP server.

How to Set Up Support of Registered BOOTP Clients (DHCP Manager)

1. Select Modify from the Service menu.

   The Modify Service Options dialog box opens.

2. In the BOOTP Compatibility section of the dialog box, select Manual.

3. Select Restart Server if it is not already selected.

4. Click OK.

5. Select the Addresses tab in DHCP Manager.

6. Select an address you want to assign to a particular BOOTP client.

7. Choose Properties from the Edit menu.

   The Address Properties dialog box opens.

8. Select the Lease tab.

9. In the Client ID field, type the client's identifier.

   For a BOOTP client that runs the Solaris operating environment on an Ethernet network, the client ID is a string derived from the client's hexadecimal Ethernet address, preceded by the Address Resolution Protocol (ARP) type for Ethernet (01). For example, a BOOTP client having the Ethernet address 8:0:20:94:12:1e would use the client ID 0108002094121E.

   ---

   Tip –

   As superuser on a Solaris client system, type the following command to obtain the Ethernet address for the interface:

   ifconfig -a

   ---

10. Select Reserved to reserve the IP address for this client.

11. Select Assign Only to BOOTP Clients.

12. Click OK.

    In the Addresses tab, BOOTP is displayed in the Status field, and the client ID you entered is listed in the Client ID field.

Working With IP Addresses in the DHCP Service (Task Map)

You can use DHCP Manager or the pntadm command to add IP addresses, modify their properties, and remove them from the DHCP service. Before you work with IP addresses, you should refer to Table 10–2 to become familiar with IP address properties. The table provides information for users of DHCP Manager and pntadm.

This section does not include procedures for using the pntadm command. However Table 10–2 includes examples of using pntadm to specify IP address properties while adding and modifying IP addresses. Also refer to the pntadm man page for more information about pntadm.

The following task map lists tasks you must perform to add, modify, remove IP addresses and the procedures used to carry them out.

The following table lists and describes the properties of IP addresses.

Adding Addresses to the DHCP Service

Before you add addresses, you must add the network that owns them to the DHCP service. See Adding DHCP Networks for information about adding networks.

You can add addresses with DHCP Manager or pntadm.

On networks that are already managed by the DHCP service, you can add addresses in several ways with DHCP Manager:

• Add a single IP address – Place one new IP address under DHCP management.

• Duplicate an existing IP address – Copy the properties of an existing IP address managed by DHCP, and supply a new IP address and client name.

• Add a range of multiple IP addresses – Use the Address Wizard to place a series of IP addresses under DHCP management.

The following figure shows the Create Address dialog box. The Duplicate Address dialog box is identical to the Create Address dialog box, except that the text fields display the values for an existing address.

Figure 10–8 Create Address Dialog Box

The following figure shows the first dialog of the Address Wizard, used to add a range of IP addresses.

Figure 10–9 Address Wizard

How to Add a Single IP Address (DHCP Manager)

1. Select the Addresses tab.

2. Select the network where the new IP address is to be added.

3. Choose Create from the Edit menu.

   The Create Address dialog box opens.

4. Select or type values for the address settings on the Address and Lease tabs.

   See Table 10–2 for information about the settings.

5. Click OK.

How to Duplicate an Existing IP Address (DHCP Manager)

1. Select the Addresses tab.

2. Select the network where the new IP address is located.

3. Select the address whose properties you want to duplicate.

4. Choose Duplicate from the Edit menu.

5. Change the IP address and client name for the address.

   Most other options should remain the same, but you can change them if necessary.

6. Click OK.

How to Add Multiple Addresses (DHCP Manager)

1. Select the Addresses tab.

2. Select the network where the new IP addresses are to be added.

3. Choose Address Wizard from the Edit menu.

   The Address Wizard prompts you to provide values for the IP address properties. See Table 10–2 for more information about the properties. Making Decisions for IP Address Management (Task Map) includes more extensive information.

4. Click the right arrow button as you finish entering information in each screen, and click Finish on the last screen.

   The Addresses tab is updated with the new addresses.

How to Add Addresses (pntadm)

1. Become superuser or a user assigned to the DHCP Management profile.

2. Type a command of the following format:

   # pntadm -A ip-address options network-address

   Refer to the pntadm man page for a list of options you can use with pntadm -A. In addition, Table 10–2 shows some sample pntadm commands that specify options.

   ---

   Note –

   You can write a script to add multiple addresses with pntadm. See Example 12–1 for an example.

   ---

Modifying IP Addresses in the DHCP Service

After you add IP addresses to the DHCP service, you can modify any of the properties described in Table 10–2 by using DHCP Manager or the pntadm -M command. See the pntadm man page for more information about pntadm -M.

The following figure shows the Address Properties dialog box that you use to modify IP address properties.

Figure 10–10 Address Properties Dialog Box

The following figure shows the Modify Multiple Addresses dialog box that you use to modify multiple IP addresses.

Figure 10–11 Modify Multiple Addresses Dialog Box

How to Modify IP Address Properties (DHCP Manager)

1. Select the Addresses tab.

2. Select the IP address's network.

3. Select one or more IP addresses you want to modify.

   If you want to modify more than one address, press the Control key while you click with the mouse to select multiple addresses. You can also press the Shift key while you click to select a block of addresses.

4. Choose Properties from the Edit menu.

   The Modify Addresses dialog box or the Modify Multiple Address dialog box opens.

5. Change the appropriate properties.

   Click the Help button or refer to Table 10–2 for information about the properties.

6. Click OK.

How to Modify IP Address Properties (pntadm)

1. Become superuser or a user assigned to the DHCP Management profile.

2. Enter a command of the following format:

   # pntadm -M ip-address options network-address

   Many options can be used with the pntadm command, which are documented in the pntadm man page.

   Table 10–2 shows some sample pntadm commands that specify options.

Removing Addresses From DHCP Service

At times you might want the DHCP service to stop managing a particular address or group of addresses. The method you use to remove an address from DHCP depends on whether you want the change to be temporary or permanent.

• To temporarily prevent the use of addresses, you can mark them unusable in the Address Properties dialog box as described in Marking IP Addresses Unusable by the DHCP Service.

• To permanently prevent the use of addresses by DHCP clients, delete the addresses from the DHCP network tables, as described in Deleting IP Addresses from DHCP Service.

Marking IP Addresses Unusable by the DHCP Service

You can use the pntadm -M command with the -f UNUSABLE option to mark addresses unusable.

In DHCP Manager, you use the Address Properties dialog box, shown in Figure 10–10, to mark individual addresses, and the Modify Multiple Addresses dialog box, show in Figure 10–11, to mark multiple addresses, as described in the following procedure.

How to Mark Addresses Unusable (DHCP Manager)

1. Select the Addresses tab.

2. Select the IP address's network.

3. Select one or more IP addresses you want to mark unusable.

   If you want to mark more than one address unusable, press the Control key while you click with the mouse to select multiple addresses. You can also press the Shift key while you click to select a block of addresses.

4. Choose Properties from the Edit menu.

   The Modify Addresses dialog box or the Modify Multiple Address dialog box opens.

5. If you are modifying one address, select the Lease tab.

6. Select Address is Unusable.

   If you are editing multiple addresses, select Mark All Addresses Unusable.

7. Click OK.

How to Mark Addresses Unusable (pntadm)

1. Become superuser or a user assigned to the DHCP Management profile.

2. Enter a command of the following format:

   # pntadm -M ip-address -f UNUSABLE network-address

   For example, to mark address 10.64.3.3 as unusable, type:

   pntadm -M 10.64.3.3 -f UNUSABLE 10.64.3.0

Deleting IP Addresses from DHCP Service

You should delete IP addresses from the DHCP service database if you no longer want the address to be managed by DHCP. You can use the pntadm -D command or DHCP Manager's Delete Address dialog box.

The following figure shows the Delete Address dialog box.

Figure 10–12 Delete Address Dialog Box

How to Delete IP Addresses from DHCP Service (DHCP Manager)

1. Select the Addresses tab.

2. Select the IP address's network.

3. Select one or more IP addresses you want to delete.

   If you want to delete more than one address, press the Control key while you click with the mouse to select multiple addresses. You can also press the Shift key while you click to select a block of addresses.

4. Choose Delete from the Edit menu.

   The Delete Address dialog box lists the address you selected so you can confirm the deletion.

5. If you want to delete the host names from the hosts table, select Delete From Hosts Table.

   If the host names were generated by DHCP Manager, you might want to delete the names from the hosts table.

6. Click OK.

How to Delete IP Addresses from DHCP Service (pntadm)

1. Become superuser or a user assigned to the DHCP Management profile.

2. Type a command of the following format:

   # pntadm -D ip-address

   If you include the -y option, the host name is deleted from the name service in which it is maintained.

Setting Up DHCP Clients for a Consistent IP Address

The Solaris DHCP service attempts to provide the same IP address to a client that has previously obtained an address through DHCP. However, it is not always possible when a dynamic lease is used.

Routers, NIS/NIS+, DNS servers, and other hosts critical to the network should not use DHCP because they should not rely on the network to obtain their IP addresses. Clients such as print or file servers should have consistent IP addresses as well, but can be set up to receive their network configurations through DHCP.

You can set up a client to receive the same IP address each time it requests its configuration if you reserve, or manually assign, the client's ID to the address you want it to use. You can set up the reserved address to use a dynamic lease to make it easy to track the use of the address, or a permanent lease if you do not need to track address use. However, you might not want to use permanent leases because once a client obtains a permanent lease, it does not contact the server again and cannot obtain updated configuration information unless it releases the IP address and restarts the DHCP lease negotiation. A diskless client is an example of a client that should use a reserved address with a dynamic lease.

You can use the pntadm -M command or DHCP Manager's Address Properties dialog box.

The following figure shows the Lease tab of the Address Properties dialog box used to modify the lease.

Figure 10–13 Address Properties Lease Tab

How to Assign a Consistent IP Address to a DHCP Client (DHCP Manager)

1. Determine the client ID for the client you want to have a permanent IP address.

   See the entry for client ID in Table 10–2 for information about how to determine the client ID.

2. Select the Addresses tab in DHCP Manager.

3. Select the appropriate network.

4. Double-click the IP address you want to the client to use.

   The Address Properties window opens.

5. Select the Lease tab.

6. In the Client ID field, type the client ID you determined from the client's hardware address.

   See the Client ID entry in Table 10–2 for more information.

7. Select the Reserved option to prevent the IP address from being reclaimed by the server.

8. In the Lease Policy area of the window, select Dynamic or Permanent assignment.

   Select Dynamic if you want the client to negotiate to renew leases, and thus be able to track when the address is used. Because you selected Reserved, the address cannot be reclaimed even when it uses a dynamic lease. You do not need to enter an expiration date for this lease. The DHCP server calculates the expiration date based on the lease time.

   If you select Permanent, you cannot track the use of the IP address unless you enable transaction logging.

How to Assign a Consistent IP Address to a DHCP Client (pntadm)

1. Become superuser or a user assigned to the DHCP Management profile.

2. Type a command of the following format:

   # pntadm -M ip-address -i client-id -f MANUAL+BOOTP network-address

   Refer to the Client ID entry in Table 10–2 for more information about how to determine client identifiers.

Working With DHCP Macros (Task Map)

DHCP macros are containers of DHCP options. The Solaris DHCP service uses macros to gather together options that should be passed to clients. DHCP Manager and dhcpconfig create a number of macros automatically when you configure the server. See About Macros for background information about macros, and Chapter 9, Configuring DHCP Service (Task) for information about macros created by default.

You might find that when changes occur on your network, you need to make changes to the configuration information passed to clients. To do this, you need to work with DHCP macros. You can view, create, modify, duplicate, and delete DHCP macros.

When you work with macros, you must know about DHCP standard options, which are described in the dhcp_inittab man page.

The following task map lists tasks to help you view, create, modify, and delete DHCP macros.

The following figure shows the Macros tab in the DHCP Manager window.

Figure 10–14 DHCP Manager's Macros Tab

How to View Macros Defined on a DHCP Server (DHCP Manager)

1. Select the Macros tab.

   The Macros area on the left side of the window displays, in alphabetical order, all macros defined on the server. Macros preceded by a folder icon include references to other macros, while macros preceded by a document icon do not reference other macros.

2. To open a macro folder, click the open/close widget to the left of the folder icon.

   The macros included in the selected macro are listed.

3. To view the contents of a macro, click the macro name and look at the area on the right side of the window.

   Options and their assigned values are displayed.

How to View Macros Defined on a DHCP Server (dhtadm)

1. Become superuser or a user assigned to the DHCP Management profile.

2. Type the following command:

   # dhtadm -P

   This command prints to standard output the formatted contents of the dhcptab, including all macros and symbols defined on the server.

Modifying DHCP Macros

You might need to modify macros when some aspect of your network changes and one or more clients need to know about the change. For example, you might add a router or a NIS server, create a new subnet, or decide to change the lease policy.

When you modify a macro, you must know the name of the DHCP option that corresponds to the parameter you want to change, add, or delete. The standard DHCP options are listed in the DHCP Manager help and in the dhcp_inittab man page.

You can use the dhtadm -M -m command or DHCP Manager to modify macros. See the dhtadm man page for more information about dhtadm.

The following figure shows DHCP Manager's Macro Properties dialog box.

Figure 10–15 Macro Properties Dialog Box

How to Change Values for Options in a DHCP Macro (DHCP Manager)

1. Select the Macros tab.

2. Select the macro you want to change.

3. Choose Properties from the Edit menu.

   The Macro Properties dialog box opens.

4. In the table of Options, select the option you want to change.

   The option's name and value are displayed in the Option Name and Option Value fields.

5. In the Option Value field, select the old value and type the new value for the option.

6. Click Modify.

   The new value is displayed in the options table.

7. Select Notify DHCP Server of Change.

   This selection tells the DHCP server to reread the dhcptab to put the change into effect immediately after you click OK.

8. Click OK.

How to Change Values for Options in a DHCP Macro (dhtadm)

1. Become superuser or a user assigned to the DHCP Management profile.

2. Type a command of the following format:

   # dhtadm -M -m macroname -e 'option=value:option=value'

   For example, to change the lease time and the Universal Time Offset in macro bluenote, type the following command:

   # dhtadm -M -m bluenote -e 'LeaseTim=43200:UTCOffst=28800'

How to Add Options to a DHCP Macro (DHCP Manager)

1. Select the Macros tab.

2. Select the macro you want to change.

3. Choose Properties from the Edit menu.

   The Macro Properties dialog box opens.

4. In the Option Name field, specify the name of an option by using one of the following methods:

   1. Click the Select button next to the Option Name field and select the option you want to add to the macro.

      The Select Option dialog box displays an alphabetized list of names of Standard category options and descriptions. If you want to add an option that is not in the Standard category, use the Category list to select the category you want.

      See About Macros for more information about macro categories.

   2. Type Include if you want to include a reference to an existing macro in the new macro.

5. Type the value for the option in the Option Value field.

   If you typed Include as the option name, you must specify the name of an existing macro in the Option Value field.

6. Click Add.

   The option is added to the bottom of the list of options displayed for this macro. If you want to change the option's position in the list, select the option and click the arrow keys next to the list to move the option up or down.

7. Select Notify DHCP Server of Change.

   This selection tells the DHCP server to reread the dhcptab to put the change into effect immediately after you click OK.

8. Click OK.

How to Add Options to a DHCP Macro (dhtadm)

1. Become superuser or a user assigned to the DHCP Management profile.

2. Type a command of the following format:

   # dhtadm -M -m macroname -e 'option=value'

   For example, to add the ability to negotiate leases, in macro bluenote, type the following command:

   # dhtadm -M -m bluenote -e 'LeaseNeg=_NULL_VALUE'

   Note that if an option does not require a value, you must use _NULL_VALUE as the value for the option.

How to Delete Options from a DHCP Macro (DHCP Manager)

1. Select the Macros tab.

2. Select the macro you want to change.

3. Choose Properties from the Edit menu.

   The Macro Properties dialog box opens.

4. Select the option you want to remove from the macro.

5. Click Delete.

   The option is removed from the list of options for this macro.

6. Select Notify DHCP Server of Change.

   This selection tells the DHCP server to reread the dhcptab to put the change into effect immediately after you click OK.

7. Click OK.

How to Delete Options from a DHCP Macro (dhtadm)

1. Become superuser or a user assigned to the DHCP Management profile.

2. Type a command of the following format:

   # dhtadm -M -m macroname -e 'option='

   For example, to remove the ability to negotiate leases in macro bluenote, type the following command:

   # dhtadm -M -m bluenote -e 'LeaseNeg='

   If an option is specified with no value, it is removed from the macro.

Creating DHCP Macros

You may want to add new macros to your DHCP service to support clients with specific needs. You can use the dhtadm -A -m command or DHCP Manager's Create Macro dialog box to add macros. See the dhtadm man page for more information about the dhtadm command.

The following figure shows DHCP Manager's Create Macro dialog box.

Figure 10–16 Create Macro Dialog Box

How to Create a DHCP Macro (DHCP Manager)

1. Select the Macros tab.

2. Choose Create from the Edit menu.

   The Create Macro dialog box opens.

3. Type a unique name for the macro.

   The name can be up to 128 alphanumeric characters. If you use a name that matches a vendor class identifier, network address, or client ID, the macro will be processed automatically for appropriate clients. If you use a different name, the macro can only be processed if it is assigned to a specific IP address or included in another macro that is processed. See Macro Processing by the DHCP Server for more detailed information.

4. Click the Select button next to the Option Name field.

   The Select Option dialog box displays an alphabetized list of names of Standard category options and their descriptions.

5. If you want to add an option that is not in the Standard category, use the Category list to select the category you want.

   See About Options for more information about option categories.

6. Select the option you want to add to the macro and click OK.

   The Macro Properties dialog box displays the selected option in the Option Name field.

7. Type the value for the option in the Option Value field.

8. Click Add.

   The option is added to the bottom of the list of options displayed for this macro. If you want to change the option's position in the list, select the option and click the arrow keys next to the list to move the option up or down.

9. Repeat Step 6 through Step 8 for each option you want to add to the macro.

10. Select Notify DHCP Server of Change when you are finished adding options.

    This selection tells the DHCP server to reread the dhcptab to put the change into effect immediately after you click OK.

11. Click OK.

How to Create a DHCP Macro (dhtadm)

1. Become superuser or a user assigned to the DHCP Management profile.

2. Type a command of the following format:

   # dhtadm -A -m macroname -d ':option=value:option=value:option=value:'

   There is no limit to the number of option/value pairs included in the argument to -d. The argument must begin and end with colons, with colons separating each option/value pair.

   For example, to create macro bluenote, type the following command:

   # dhtadm -A -m bluenote -d \
   ':Router=10.63.6.121:LeaseNeg=_NULL_VALUE:'DNSserv=10.63.28.12:'
   

   Note that if an option does not require a value, you must use _NULL_VALUE as the value for the option.

Deleting DHCP Macros

You might want to delete a macro from the DHCP service. For example, if you delete a network from the DHCP service, you can also delete the associated network macro.

You can use the dhtadm -D -m command or DHCP Manager to delete macros.

How to Delete a DHCP Macro (DHCP Manager)

1. Select the Macros tab.

2. Select the macro you want to delete.

   The Delete Macro dialog box prompts you to confirm that you want to delete the specified macro.

3. Select Notify DHCP Server of Change.

4. Click OK.

How to Delete a DHCP Macro (dhtadm)

1. Become superuser or a user assigned to the DHCP Management profile.

2. Type a command of the following format:

   # dhtadm -D -m macroname

   For example, to delete macro bluenote, type the following command:

   # dhtadm -D -m bluenote

Working With DHCP Options (Task Map)

Options are keywords for network configuration parameters that the DHCP server can pass to clients. In the Solaris DHCP service, the only options that you can create, delete, or modify are those that are not specified as standard options in the Solaris DHCP service. For this reason, when you first set up your DHCP service, the Options tab in DHCP Manager is empty until you create options for your site.

If you create options on the DHCP server, you must also add information about the options on the DHCP client. For the Solaris DHCP client, you must edit the /etc/dhcp/inittab file to add entries for the new options. See the dhcp_inittab man page for more information about this file.

If you have DHCP clients that are not Solaris clients, refer to the documentation for those clients for information about adding new options or symbols. See About Options for more information about options in Solaris DHCP.

You can use either DHCP Manager or the dhtadm command to create, modify, or delete options.

Options are called symbols in the DHCP literature. The dhtadm command and man page also refer to options as symbols.

The following task map lists tasks you must perform to create, modify, and delete DHCP options and the procedures needed to carry them out.

Before you create options, you should be familiar with the option properties listed in the following table.

Creating DHCP Options

If you need to pass client information for which there is not already an existing option in the DHCP protocol, you can create an option. See the dhcp_inittab man page for a list of all the options that are defined in Solaris DHCP before you create your own.

You can use the dhtadm -A -s command or DHCP Manager's Create Option dialog box to create new options.

The following figure shows DHCP Manager's Create Option dialog box.

Figure 10–17 Create Option Dialog Box

How to Create DHCP Options (DHCP Manager)

1. Select the Options tab.

2. Choose Create from the Edit menu.

   The Create Options dialog box opens.

3. Type a short descriptive name for the new option.

   The name may contain up to 128 alphanumeric characters including spaces.

4. Type or select values for each setting in the dialog box.

   Refer to Table 10–3 for information about each setting.

5. Select Notify DHCP Server of Change if you are finished creating options.

6. Click OK.

   You can now add the option to macros and assign a value to the option to pass to clients.

How to Create DHCP Options (dhtadm)

1. Become superuser or a user assigned to the DHCP Management profile.

2. Type a command using the following format:

   # dhtadm -A -s option-name-d 'category,code,data-type,granularity,maximum'

   where

   option-name	is an alphanumeric string of 128 characters or less.
   category	is Site, Extend, or Vendor=list-of-classes, and list-of-classes is a space-separated list of vendor client classes to which the option applies. See Table 10–3 for information about how to determine the vendor client class.
   code	is a numeric value appropriate to the option category, as explained in Table 10–3.
   data-type	is a keyword that indicates the type of data passed with the option, as explained in Table 10–3.
   granularity	is a nonnegative number, as explained in Table 10–3.
   maximum	is a nonnegative number, as explained in as explained in Table 10–3.

   The following two commands are examples:

   # dhtadm -A -s NewOpt -d 'Site,130,UNUMBER8,1,1'
   

   # dhtadm -A -s NewServ -d 'Vendor=SUNW.Ultra-1 \ 
   SUNW.SPARCstation10,200,IP,1,1'
   

Modifying DHCP Options

If you have created options for your DHCP service, you can change the properties for an option by using either DHCP Manager or the dhtadm command.

You can use the dhtadm -M -s command or DHCP Manager's Option Properties dialog box to modify options.

Note that you should modify the Solaris DHCP client's option information to reflect the same modification you make to the DHCP service. See Modifying the Solaris DHCP Client's Option Information.

The following figure shows DHCP Manager's Option Properties dialog box.

Figure 10–18 Option Properties Dialog Box

How to Modify DHCP Option Properties (DHCP Manager)

1. Select the Options tab.

2. Select the option whose properties you want to change.

3. Choose Properties from the Edit menu.

   The Option Properties dialog box opens.

4. Edit the properties as needed.

   See Table 10–3 for information about the properties.

5. Select Notify Server of Change when you are finished with options.

6. Click OK.

How to Modify DHCP Option Properties (dhtadm)

1. Become superuser or a user assigned to the DHCP Management profile.

2. Type a command using the following format:

   # dhtadm -M -s option-name-d 'category,code,data-type,granularity,maximum'

   where

   option-name	is the option name whose definition you want to change.
   category	is Site, Extend, or Vendor=list-of-classes, and list-of-classes is a space-separated list of vendor client classes to which the option applies. For example, SUNW.Ultra5_10 SUNW.Ultra-1 SUNWi86pc.
   code	is a numeric value appropriate to the option category, as explained in Table 10–3.
   data-type	is a keyword that indicates the type of data passed with the option, as explained in Table 10–3.
   granularity	is a nonnegative number, as explained in Table 10–3.
   maximum	is a nonnegative number, as explained in as explained in Table 10–3.

   Note that you must specify all of the DHCP option properties with the -d switch, not just the properties you want to change.

   The following two commands are examples:

   # dhtadm -M -s NewOpt -d 'Site,135,UNUMBER8,1,1'
   # dhtadm -M -s NewServ -d 'Vendor=SUNW.Ultra-1 \
   SUNW.i86pc,200,IP,1,1'
   

Deleting DHCP Options

You cannot delete standard DHCP options, but if you have defined options for your DHCP service, you can delete them by using DHCP Manager or the dhtadm command.

How to Delete DHCP Options (DHCP Manager)

1. Select the Options tab.

2. Choose Delete from the Edit menu.

   The Delete Options dialog box opens.

3. Confirm the deletion by clicking OK.

How to Delete DHCP Options (dhtadm)

1. Become superuser or a user assigned to the DHCP Management profile.

2. Type a command using the following format:

   # dhtadm -D -s option-name

Modifying the Solaris DHCP Client's Option Information

If you add a new DHCP option to your DHCP server, you must add a complementary entry to each DHCP client's option information. If you have a DHCP client that is not a Solaris DHCP client, refer to that client's documentation for information about adding options or symbols.

On a Solaris DHCP client, you must edit the /etc/dhcp/inittab file and add an entry for each option that you add to the DHCP server. If you later modify the option on the server, you must also modify the entry in the client's /etc/dhcp/inittab file.

Refer to the dhcp_inittab man page for detailed information about the syntax of the /etc/dhcp/inittab file.

If you added DHCP options to the dhcptags file in a previous release of Solaris DHCP, you must add the options to the /etc/dhcp/inittab file. See DHCP Option Information for more information.

Supporting Solaris Network Installation with the DHCP Service (Task Map)

You can use DHCP to install the Solaris operating environment on certain client systems on your network. Only Sun Enterprise Ultra systems and Intel systems that meet the hardware requirements for running the Solaris operating environment can use this feature.

For information about supporting diskless clients, see Supporting Remote Boot and Diskless Boot Clients (Task Map).

The following task map shows the high-level tasks that must be performed to enable clients to obtain installation parameters using DHCP.

Creating DHCP Options and Macros for Solaris Installation Parameters

When you add clients with the add_install_client -d script on the install server, the script reports DHCP configuration information to standard output. This information can be used when you create the options and macros needed to pass network installation information to clients.

To support clients that require Solaris installation from the network, you must create Vendor category options to pass information that is needed to correctly install the Solaris operating environment. The following table shows the options you must create and the properties needed to create them.

When you have created the options, you can create macros that include those options. The following table lists suggested macros you can create to support Solaris installation for clients.

You can create these options and macros by using the dhtadm command or DHCP Manager. If you use dhtadm, it is better to create the options and macros by writing a script that uses the dhtadm command repeatedly.

The following section, Writing a Script That Uses dhtadm to Create Options and Macros, shows a sample script that uses the dhtadm command. If you prefer to use DHCP Manager, see Using DHCP Manager to Create Install Options and Macros.

Writing a Script That Uses dhtadm to Create Options and Macros

You can create a Korn shell script by adapting the example in Example 10–1 to create all the options listed in Table 10–4 and some useful macros. Be sure to change all IP addresses and values contained in quotes to the correct IP addresses, server names, and paths for your network. You should also edit the Vendor= key to indicate the class of clients you have. Use the information reported by add_install_client -d to obtain the data needed to adapt the script.

Example 10–1 Sample Script to Support Network Installation

# Load the Solaris vendor specific options. We'll start out supporting 
# the Ultra-1, Ultra-30, and i86 platforms. Changing -A to -M would replace
# the current values, rather than add them.
dhtadm -A -s SrootOpt -d 'Vendor=SUNW.Ultra-1 SUNW.Ultra-30 SUNW.i86pc,1,ASCII,1,0'
dhtadm -A -s SrootIP4 -d 'Vendor=SUNW.Ultra-1 SUNW.Ultra-30 SUNW.i86pc,2,IP,1,1'
dhtadm -A -s SrootNM -d 'Vendor=SUNW.Ultra-1 SUNW.Ultra-30 SUNW.i86pc,3,ASCII,1,0'
dhtadm -A -s SrootPTH -d 'Vendor=SUNW.Ultra-1 SUNW.Ultra-30 SUNW.i86pc,4,ASCII,1,0'
dhtadm -A -s SswapIP4 -d 'Vendor=SUNW.Ultra-1 SUNW.Ultra-30 SUNW.i86pc,5,IP,1,0'
dhtadm -A -s SswapPTH -d 'Vendor=SUNW.Ultra-1 SUNW.Ultra-30 SUNW.i86pc,6,ASCII,1,0'
dhtadm -A -s SbootFIL -d 'Vendor=SUNW.Ultra-1 SUNW.Ultra-30 SUNW.i86pc,7,ASCII,1,0'
dhtadm -A -s Stz -d 'Vendor=SUNW.Ultra-1 SUNW.Ultra-30 SUNW.i86pc,8,ASCII,1,0'
dhtadm -A -s SbootRS -d 'Vendor=SUNW.Ultra-1 SUNW.Ultra-30 SUNW.i86pc,9,NUMBER,2,1'
dhtadm -A -s SinstIP4 -d 'Vendor=SUNW.Ultra-1 SUNW.Ultra-30 SUNW.i86pc,10,IP,1,1'
dhtadm -A -s SinstNM -d 'Vendor=SUNW.Ultra-1 SUNW.Ultra-30 SUNW.i86pc,11,ASCII,1,0'
dhtadm -A -s SinstPTH -d 'Vendor=SUNW.Ultra-1 SUNW.Ultra-30 SUNW.i86pc,12,ASCII,1,0'
dhtadm -A -s SsysidCF -d 'Vendor=SUNW.Ultra-1 SUNW.Ultra-30 SUNW.i86pc,13,ASCII,1,0'
dhtadm -A -s SjumpsCF -d 'Vendor=SUNW.Ultra-1 SUNW.Ultra-30 SUNW.i86pc,14,ASCII,1,0'
dhtadm -A -s Sterm -d 'Vendor=SUNW.Ultra-1 SUNW.Ultra-30 SUNW.i86pc,15,ASCII,1,0'
# Load some useful Macro definitions
# Define all Solaris-generic options under this macro named Solaris.
dhtadm -A -m Solaris -d ':SrootIP4=10.21.0.2:SrootNM="blue2":SinstIP4=10.21.0.2:\
SinstNM="red5":Sterm="xterm":'
# Define all sparc-platform specific options under this macro named sparc.
dhtadm -A -m sparc -d ':SrootPTH="/export/sparc/root":SinstPTH="/export/sparc/install":'
# Define all sun4u architecture-specific options under this macro named sun4u. (Includes
# Solaris and sparc macros.)
dhtadm -A -m sun4u -d ':Include=Solaris:Include=sparc:'
# Solaris on IA32-platform-specific parameters are under this macro named i86pc.
dhtadm -A -m i86pc -d \
':Include=Solaris:SrootPTH="/export/i86pc/root":SinstPTH="/export/i86pc/install"\
:SbootFIL="/platform/i86pc/kernel/unix":'
# Solaris on IA32 machines are identified by the "SUNW.i86pc" class. All
# clients identifying themselves as members of this class will see these
# parameters in the macro called SUNW.i86pc, which includes the i86pc macro.
dhtadm -A -m SUNW.i86pc -d ':Include=i86pc:'
# Ultra-1 platforms identify themselves as part of the "SUNW.Ultra-1" class.
# By default, we boot these machines in 32bit mode. All clients identifying
# themselves as members of this class will see these parameters.
dhtadm -A -m SUNW.Ultra-1 -d ':SbootFIL="/platform/sun4u/kernel/unix":Include=sun4u:'
# Ultra-30 platforms identify themselves as part of the "SUNW.Ultra-30" class.
# By default, we will boot these machines in 64bit mode. All clients
# identifying themselves as members of this class will see these parameters.
dhtadm -A -m SUNW.Ultra-30 -d ':SbootFIL="/platform/sun4u/kernel/sparcv9/unix":\
Include=sun4u:'
# Add our boot server IP to each of the network macros for our topology served by our
# DHCP server. Our boot server happens to be the same machine running our DHCP server.
dhtadm -M -m 10.20.64.64 -e BootSrvA=10.21.0.2
dhtadm -M -m 10.20.64.0 -e BootSrvA=10.21.0.2
dhtadm -M -m 10.20.64.128 -e BootSrvA=10.21.0.2
dhtadm -M -m 10.21.0.0 -e BootSrvA=10.21.0.2
dhtadm -M -m 10.22.0.0	-e BootSrvA=10.21.0.2
# Make sure we return host names to our clients.
dhtadm -M -m DHCP-servername -e Hostname=_NULL_VALUE_
# The client with this MAC address is a diskless client. Override the root settings
# which at the network scope setup for Install with our client's root directory.
dhtadm -A -m 0800201AC25E -d \
':SrootIP4=10.23.128.2:SrootNM="orange-svr-2":SrootPTH="/export/root/10.23.128.12":'

As superuser, execute dhtadm in batch mode and specify the name of the script to add the options and macros to your dhcptab. For example, if your script is named netinstalloptions, type the command:

dhtadm -B netinstalloptions

When you have done this, clients that have vendor client classes that are listed in the Vendor= string can use DHCP to obtain the parameters they need for Solaris installation over the network.

Using DHCP Manager to Create Install Options and Macros

You can create the options listed in Table 10–4 and the macros listed in Table 10–5 with DHCP Manager.

See Figure 10–17 and Figure 10–16 for illustrations of the dialog boxes you use to create options and macros.

How to Create Options to Support Solaris Installation (DHCP Manager)

1. Select the Options tab in DHCP Manager.

2. Choose Create from the Edit menu.

   The Create Option dialog box opens.

3. Type the option name for the first option and type values appropriate for that option.

   Use Table 10–4 to look up the option names and values for options you must create. Notice that the vendor client classes are only suggested values. You should create classes to indicate the actual client types that need to obtain Solaris installation parameters from the DHCP service. See Table 10–3 for information about how to determine a client's vendor client class.

4. Click OK when you have entered all the values.

5. In the Options tab, select the option you just created.

6. Select Duplicate from the Edit menu.

   The Duplicate Option dialog box opens.

7. Type the name of another option and modify other values appropriately.

   The values for code, data type, granularity, and maximum are most likely to need modification. See Table 10–4 for the values.

8. Repeat Step 5 through Step 7 until you have created all the options.

   You can now create macros to pass the options to network installation clients, as explained in the following procedure.

   ---

   Note –

   You do not need to add these options to a Solaris client's /etc/dhcp/inittab file because they are already included in that file.

   ---

How to Create Macros to Support Solaris Installation (DHCP Manager)

1. Select the Macros tab in DHCP Manager.

2. Choose Create from the Edit menu.

   The Create Macro dialog box opens.

3. Type the name of a macro.

   See Table 10–5 for macro names you might use.

4. Click the Select button.

   The Select Option dialog box opens.

5. Select Vendor in the Category list.

   The Vendor options you created are listed.

6. Select an option you want to add to the macro and click OK.

7. Type a value for the option.

   See Table 10–4 for the option's data type and refer to the information reported by add_install_client -d.

8. Repeat Step 6 through Step 7 for each option you want to include.

   To include another macro, type Include as the option name and type the macro name as the option value.

9. Click OK when the macro is complete.

Supporting Remote Boot and Diskless Boot Clients (Task Map)

The Solaris DHCP service can support Solaris client systems that mount their operating system files remotely from another machine, called the OS server. Such clients are often called diskless clients. They can be thought of as persistent remote boot clients in that each time they boot, they must obtain the name and IP address of the server that hosts their operating system files, and then boot remotely from those files.

Each diskless client has its own root partition on the OS server, which is shared to the client host name. This means that the DHCP server must always return the same IP address to the client, and that address must remain mapped to the same host name in the name service (such as DNS). To accomplish this, each diskless client must be assigned a consistent IP address.

In addition to the IP address and host name, the DHCP server can supply a diskless client with all the information needed to locate its operating system files on the OS server. However, you must create options and macros that can be used to pass the information in a DHCP message packet.

The following task map lists the tasks required to support diskless clients or any other persistent remote boot clients, and includes links to procedures to help you carry them out.

Setting Up DHCP Clients as NIS+ Clients

You can use the NIS+ name service on Solaris systems that are DHCP clients, but to do so requires you to partially circumvent one of the security-enhancing features of NIS+ - the creation of DES credentials. When you set up a NIS+ client that is not using DHCP, you add unique DES credentials for the new NIS+ client system to the cred table on the NIS+ server. There are several ways to accomplish this, such as using the nisclient script or the nisaddcred command.

For DHCP clients, you cannot use these methods because they depend on a static host name to create and store the credentials. If you want to use NIS+ and DHCP, you must create identical credentials to be used for all the host names of DHCP clients. In this way, no matter what IP address (and associated host name) a DHCP client receives, it can use the same DES credentials.

Before you do this, remember that NIS+ was designed with security in mind, and this procedure weakens that security because it allows random DHCP clients to receive NIS+ credentials.

The following procedure shows you how to create identical credentials for all DHCP host names. This procedure is only valid if you know the host names that DHCP clients will use, such as when the host names are generated by the DHCP server.

How to Set Up Solaris DHCP Clients as NIS+ Clients

A DHCP client workstation that is to be a NIS+ client must use credentials copied from another NIS+ client workstation in the NIS+ domain. This procedure only produces credentials for the workstation, which apply only to the superuser logged in to the workstation. Other users logged in to the DHCP client workstation must have their own unique credentials in the NIS+ server, created according to the procedure in the System Administration Guide: Naming and Directory Services (FNS and NIS+).

1. Type the following command on the NIS+ server to write the cred table entry for the NIS+ client to a temporary file.

   # nisgrep nisplus-client-name cred.org_dir > /tmp/file

2. View the contents of the temporary file so you can copy the credentials and use them to create credentials for DHCP clients.

   You must copy the public key and private key, which are long strings of numbers and letters separated by colons.

3. Type the following commands to add credentials for a DHCP client. Copy the public and private key information from the temporary file.

   # nistbladm -a cname=" dhcp-client-name@nisplus-domain" auth_type=DES \ auth_name="unix.dhcp-client-name@nisplus-domain" \ public_data=copied-public-data \ private_data=copied-private-data

4. Type the following commands on each DHCP client system to remote copy NIS+ client files to the DHCP client system.

   # rcp nisplus-client-name:/var/nis/NIS_COLD_START /var/nis # rcp nisplus-client-name:/etc/.rootkey /etc # rcp nisplus-client-name:/etc/defaultdomain /etc

   If you get a “permission denied” message, the systems may not be set up to allow remote copying. You can copy the files as a regular user to an intermediate location and then copy them to the proper location as root on the DHCP client systems.

5. Type the following command on the DHCP client system to use the correct name service switch file for NIS+:

   # cp /etc/nsswitch.nisplus /etc/nsswitch.conf

6. Reboot the DHCP client system.

   The DHCP client system should now be able to use NIS+ services.

Example – Setting up a Solaris DHCP Client as an NIS+ Client

The following example assumes that you have one workstation, nisei, which is a NIS+ client in the NIS+ domain dev.example.net, and one DHCP client, dhow, that you want to be a NIS+ client.

(first log in as root on the NIS+ server)
# nisgrep nisei cred.org_dir > /tmp/nisei-cred
# cat /tmp/nisei-cred
nisei.dev.example.net.:DES:unix.nisei@dev.example.net:46199279911a84045b8e0
c76822179138173a20edbd8eab4:90f2e2bb6ffe7e3547346dda624ec4c7f0fe1d5f37e21cff63830
c05bc1c724b
# nistbladm -a cname="dhow@dev.example.net." \
auth_type=DES auth_name="unix.dhow@dev.example.net" \
public_data=46199279911a84045b8e0c76822179138173a20edbd8eab4 \
private_data=90f2e2bb6ffe7e3547346dda624ec4c7f0fe1d5f37e21cff63830\
c05bc1c724b
# rlogin dhow
(log in as root on dhow)
# rcp nisei:/var/nis/NIS_COLD_START /var/nis
# rcp nisei:/etc/.rootkey /etc
# rcp nisei:/etc/defaultdomain /etc
# cp /etc/nsswitch.nisplus /etc/nsswitch.conf
# reboot

The DHCP client system dhow should now be able to use NIS+ services.

Adding Credentials With a Script

If you want to set up a large number of DHCP clients as NIS+ clients, you can write a script to quickly add the entries to the cred table. The following sample shows how this might be done.

Example 10–2 Sample Script for Adding Credentials for DHCP Clients

#! /usr/bin/ksh  
# 
# Copyright (c) by Sun Microsystems, Inc. All rights reserved. 
# 
# Sample script for cloning a credential. Hosts file is already populated  
# with entries of the form dhcp-[0-9][0-9][0-9]. The entry we're cloning 
# is dhcp-001. 
#  
#  
PUBLIC_DATA=6e72878d8dc095a8b5aea951733d6ea91b4ec59e136bd3b3 
PRIVATE_DATA=3a86729b685e2b2320cd7e26d4f1519ee070a60620a93e48a8682c5031058df4
HOST="dhcp-" 
DOMAIN="mydomain.example.com"  
 
for 
i in 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019
do         
     print - ${HOST}${i}         
     #nistbladm -r [cname="${HOST}${i}.${DOMAIN}."]cred.org_dir         
     nistbladm -a cname="${HOST}${i}.${DOMAIN}." \
         auth_type=DES auth_name="unix.${HOST}${i}@${DOMAIN}" \
         public_data=${PUBLIC_DATA} private_data=${PRIVATE_DTA} cred.org_Dir
done  
 
exit 0 

Converting to a New Data Store

Solaris DHCP provides a utility to convert the DHCP configuration data from one data store to another. You may need to convert to a new data store if, for example, your number of DHCP clients increases to the point that you need higher performance or higher capacity from the DHCP service, or if you want to share the DHCP server duties among multiple servers. See Choosing the Data Store for a comparison of the relative benefits and drawbacks of each type of data store.

If you upgraded from a Solaris release older than the Solaris 8 7/01 release on the DHCP server system, the first time you run any Solaris DHCP management tool after Solaris installation, you are prompted to convert your DHCP data tables to the new data store. The conversion is required because the format of the data stored in both files and NIS+ changed in the Solaris 8 7/01 release. If you do not convert to the new data store, the DHCP server continues to read the old data tables to extend leases for existing clients. You cannot register new DHCP clients or use management tools with the old data tables.

The conversion utility is also useful for sites converting from a Sun-provided data store to a third-party data store. The conversion utility looks up entries in the existing data store and adds new entries that contain the same data to the new data store. Data store access is implemented in separate modules for each data store, which enables the conversion utility to convert DHCP data from any data store format to any other data store format, provided each data store has a module. See Solaris DHCP Service Developer's Guide for more information about how to write a module to support a third-party data store.

The data store conversion can be accomplished with DHCP Manager through the Data Store Conversion wizard, or with the dhcpconfig -C command.

The initial dialog box of the Data Store Conversion wizard is shown in the following figure.

Figure 10–19 Data Store Conversion Wizard Dialog Box

Before the conversion begins, you must specify whether to save the old data store's tables (dhcptab and network tables) . The conversion utility then stops the DHCP server, converts the data store, and restarts the server when the conversion has completed successfully. If you did not specify to save the old tables, the utility deletes them after it determines the conversion is successful. The process of converting can be time-consuming, so the conversion runs in the background with a meter to inform you of its progress.

How to Convert the DHCP Data Store (DHCP Manager)

1. Choose Convert Data Store from the Service menu.

   The Data Store Conversion wizard opens.

2. Answer the wizard's prompts.

   If you have trouble providing the requested information, click Help to view detailed information about each dialog box.

How to Convert the DHCP Data Store (dhcpconfig -C)

1. Become superuser or a user assigned to the DHCP Management profile.

2. Type a command of the following format:

   # /usr/sbin/dhcpconfig -C -r resource -p path

   where resource is the data store (such as SUNWbinfiles) and path is the path to the data (such as /var/dhcp).

   Note that if you want to keep the original data (in the old data store) after the conversion, specify the -k option.

Moving Configuration Data Between DHCP Servers (Task Map)

The DHCP Manager and dhcpconfig utilities enable you to move some or all the DHCP configuration data from one Solaris DHCP server to another. You can move entire networks and all the addresses, macros, and options associated with it, or select specific IP addresses, macros, and options to move. You can also copy useful macros or options without removing them from the first server when you specify to keep the data on the server.

You might want to move data if you are going to do any of the following tasks:

• Add a server to share DHCP duties

• Replace the DHCP server's system

• Change the path for the data store (while still using the same data store)

The following task map identifies the procedures you must perform when you move DHCP configuration data.

In DHCP Manager, you use the Export Data wizard and Import Data wizard to move the data from one server to the other, and modify macros in the Macros tab. The following figures show the initial dialog boxes for the wizards.

Figure 10–20 Export Data Wizard Dialog Box

Figure 10–21 Import Data Wizard Dialog Box

How to Export Data From a DHCP Server (DHCP Manager)

1. Become superuser on the server from which you want to move or copy data.

2. Choose Export Data on the Service menu.

   The Export Data wizard opens as shown in Figure 10–20.

3. Answer the wizard's prompts.

   If you have difficulty, click Help for detailed information about the prompts.

4. Move the export file to a file system that is accessible to the DHCP server to which you want to move the data.

   Import the data as described in How to Import Data On a DHCP Server (DHCP Manager).

How to Import Data On a DHCP Server (DHCP Manager)

1. Become superuser on the server to which you want to move data that you previously exported from a DHCP server.

2. In DHCP Manager, choose Import Data from the Service menu.

   The Import Data Wizard opens, as shown in Figure 10–21.

3. Answer the wizard's prompts.

   If you have difficulty, click Help for detailed information about the prompts.

How to Modify Imported DHCP Data (DHCP Manager)

1. Become superuser on the server to which you imported data.

2. Examine imported data for network–specific information that needs modification.

   For example, if you moved networks, you must open the Addresses tab and change the owning server of addresses in the imported networks. You might also need to open the Macros tab to specify the correct domain names for NIS, NIS+ or DNS in the macros that specify them.

3. Open the Addresses tab and select a network that you imported.

4. To select all the addresses, click the first address, press and hold the Shift key, and click the last address.

5. From the Edit menu, choose Properties.

   The Modify Multiple Addresses dialog box opens.

6. At the Managing Server prompt, select the new server's name.

7. At the Configuration Macro prompt, select the macro that should be used for all clients on this network.

8. Click OK.

9. Open the Macros tab.

10. Use the Find facility at the bottom of the window to locate the options that are likely to need modified values.

    DNSdmain, DNSserv, NISservs, NIS+serv, and NISdmain are examples of options that might need modification on the new server.

11. When you locate an option that needs to be changed, select the macro name and choose Properties from the Edit menu and change its value.

How to Export Data From a DHCP Server (dhcpconfig -X)

1. Become superuser on the server from which you want to move or copy data.

2. Type a command of the following format:

   # /usr/sbin/dhcpconfig -X filename -a network-addresses -m macros -o options

   where filename is the full path name you want to use to store the compressed exported data. You can use the keyword ALL with the command options to export all the networks, macros, or options. For example:

   # /usr/sbin/dhcpconfig -X dhcp1065_data -a ALL -m ALL -o ALL
   

   Alternatively, you can specify particular network addresses, macros, and configuration options in comma-separated lists. For example:

   # /usr/sbin/dhcpconfig -X dhcp1065_data -a 10.63.0.0,10.62.0.0 \
   -m 10.63.0.0,10.62.0.0,SUNW.Ultra-5_10 -o Sterm
   

   See the dhcpconfig man page for more information about the dhcpconfig command.

3. Move the file that contains the exported data to a location that is accessible to the server to which you want to move the data.

   Import the data as described in How to Import Data on a DHCP Server (dhcpconfig -I).

How to Import Data on a DHCP Server (dhcpconfig -I)

1. Become superuser on the server to which you want to import the data.

2. Type a command of the following format:

   # /usr/sbin/dhcpconfig -I filename

   where filename is the name of the file that contains the data exported from the first server.

   Be sure to modify the imported data as described in How to Modify Imported DHCP Data (pntadm, dhtadm)

How to Modify Imported DHCP Data (pntadm, dhtadm)

1. Become superuser on the server to which you imported data.

2. Examine the network tables for data that needs to be modified.

   If you moved networks, use pntadm -P network_address to print out the network tables for the networks you moved.

3. Use the pntadm command to modify IP address information.

   You might need to change the owning server and the configuration macro used for imported addresses. For example, to change the owning server (10.60.3.4) and macro (dhcpsrv-1060) for address 10.63.0.2, you would use the following command:

   pntadm -M 10.63.0.2 -s 10.60.3.4 -m dhcpsrv-1060 10.60.0.0

   If you have a large number of addresses, you should create a script file that contains commands to modify each address, and then execute the script with the pntadm -B command, which runs pntadm in batch mode. See the pntadm man page.

4. Examine the dhcptab macros for options with values that need modification.

   Use dhtadm -P to print the entire dhcptab, and use grep or some other tool to search for particular options or values that you might want to change.

5. Use the dhtadm -M command to modify options in macros if necessary.

   For example, you might need to modify some macros to specify the correct domain names and servers for NIS, NIS+ or DNS. For example, the following command changes the values of DNSdmain and DNSserv in the macro mymacro:

   dhtadm -M -m mymacro -e 'DNSserv=dnssrv2:DNSdmain=example.net'