 |
» |
|
|
|
To manually configure the BOOTP server daemon, bootpd, you need to add entries to the files /etc/services and /etc/inetd.conf. When you use SAM to do the configuration, entries
are made to the appropriate files automatically. The following sections
explain the manual method for configuring and verifying bootpd. | | | |  | NOTE: You must be superuser to configure the BOOTP server. | | | | |
Procedure for Configuring bootpd | |
Configuring bootpd sets up your local system to act as a server of
boot information for remote clients. Make sure that the BOOTP server and client protocols are added
to /etc/services: bootps 67/udp # Bootstrap protocol server
bootpc 68/udp # Bootstrap protocol client |
Uncomment the following entry in /etc/inetd.conf: bootps dgram udp wait root /usr/lbin/bootpd bootpd |
Reconfigure /usr/sbin/inetd:
You are now ready to add client or relay information to the
configuration file /etc/bootptab. This step is discussed in the section “Adding Client or Relay Information”. If you wish to verify your bootpd installation, continue to the next section. | | | | | NOTE: SAM does not add relay information to the configuration
file. You must manually configure relay information on a BOOTP server. | | | | |
Verify Your bootpd Installation | |
The verification step only ensures that bootpd is started by inetd. To test whether you have correctly configured bootpd to handle boot requests, perform the following
steps: On the host where you configured bootpd, use bootpquery to send a boot request to the server. (Type man 1M bootpquery for more information.) For example, if you configured bootpd on a system named myhost, enter: /usr/sbin/bootpquery 001122334455 -s myhost |
A bootrequest is sent to the server, requesting a bootreply
for the client with hardware address 001122334455. The BOOTP server
will not respond to this request, so you will see the following
message: bootpquery:Bootp servers not responding! |
To see if the BOOTP server was started, on myhost enter the command: You should see a bootpd entry. If your system is configured to use syslogd, bootpd logs informative messages to the daemon facility.
(Type man 1M syslogd for more information.) In the default configuration,
where syslogd sends daemon information messages to /var/adm/syslog/syslog.log, you should see messages similar to the following: Dec 13 13:32:22 myhost bootpd[13381]: reading "/etc/bootptab"
Dec 13 13:32:22 myhost bootpd[13381]: read 0 entries from "/etc/bootptab"
Dec 13 13:32:22 myhost bootpd[13381]: hardware address not found: 001122334455 |
These messages tell you that bootpd was able to read the configuration file /etc/bootptab and that it correctly rejected the test bootrequest
that you sent with bootpquery.
Having verified that bootpd is configured to start from inetd, you should add to the configuration file any
BOOTP clients that the system is to serve, or any BOOTP clients
that are to be relayed to another server. The next section, “Adding Client or Relay Information”, describes how to add client information or
client relay information and how to verify that the BOOTP server
will respond to the client. |
