Setting up a BOOTP server

Your BOOTP server should typically be the same machine as your installation server. To set up a BOOTP server, perform the following procedure:

1. Log in as a privileged user on the BOOTP server, and edit the file /etc/inet/bootptab.

2. Create a parameter value template entry for any configuration information that will be common to all client hosts on the network serviced by this BOOTP server.

   Give the entry a dummy host name beginning with one dot ``.'', such as .default. Specify the common parameter values using the keyword tags described on the bootptab(4tcp) manual page. Some typical parameters you can set in your template entry include a global subnet mask (using the sm tag) and a domain name server list (using the ds tag).

   An example parameter template entry might look like this:

   .default: \
           :sm=255.255.255.0: \
           :ds=pine,stone:
   

3. Create a generic subnet entry for each subnet serviced by this BOOTP server.

   Give each entry a dummy host name that begins with two dots ``..''. Specify the information that is common to all hosts on each subnet as parameter values. At minimum, each subnet entry must define a subnet IP address using the ip tag, and gateway address list using the gw tag. Also make sure you include a table continuation tag (tc) in each subnet entry. The tc specification ensures that the subnet entry references the network-wide parameters defined in your parameter template entry, as shown here:

   ..net133: \
           :tc=.default: \
           :ip=137.2.133.0: \
           :gw=137.2.133.1:
   ..net134: \
           :tc=.default: \
           :ip=137.2.134.0: \
           :gw=137.2.134.1:
   

4. Create entries for clients on the subnets. These are examples:

   curly:tc=.net133:ht=ether:ha=00608cf2cc46:ip=137.2.133.2:
   moe:tc=.net134:ht=ether:ha=00608cf2cc57:ip=137.2.134.2:
   

   If a host client requires configuration information other than that defined in the subnet entries, create an entry specifically for it such as the one shown here:

   larry:tc=.default:ht=ether:ha=00608cf2ca35:ip=137.2.107.27:gw=137.2.134.1:
   

5. The bootpd daemon is started by the Internet services daemon, inetd, when required. To enable BOOTP, search for the following line in /etc/inetd.conf:

   #bootps dgram udp wait root /usr/sbin/in.bootpd in.bootpd
   

   Uncomment the line by removing the leading ``#'' character.

   ---

   NOTE: If you also want to configure the server as a DHCP server, you must run the BOOTP server in slave mode. See ``Making DHCP work with BOOTP'' for more information.

   ---

6. Some devices, such as network printers that use BOOTP to obtain their network parameters, may also need to be able to download other configuration files or programs using TFTP. When required, the tftpd daemon is started by inetd. To enable TFTP, search for the following line in /etc/inetd.conf:

   #tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot
   

   Uncomment the line by removing the leading ``#'' character. This example assumes that the files to be downloaded are stored in the /tftpboot directory hierarchy on the server.

7. Force inetd to re-read /etc/inetd.conf by sending it a SIGHUP signal:
   
   kill -HUP `cat /etc/saf/inetd/_pid`

   or by stopping and restarting it:
   
   sacadm -k -p inetd
   sacadm -s -p inetd

   inetd will now be able to start bootpd and tftpd when the server receives a BOOTP request from a client.