OkiLAN 6200e Plus User’s Guide
TCP/IP
130
UNIX BOOTP
If you are running UNIX, try the following methods with
the BOOTP server (check the documentation for your
particular UNIX flavor).
•
Verify that the BOOTP server has reread the “/etc/
bootptab” file when the new entry was added. If the
BOOTP server was running when you added the
new entries, the server might not have reread the
new bootptab file. Try sending the SIGHUP signal
to the running BOOTP server. For example,
kill -
HUP <process id of bootpd>
tells it to reread “/etc/
bootptab”. Most BOOTP servers support this
option. Check your local BOOTP documentation. If
this does not work, restart the BOOTP server (kill
and restart the process).
•
Some BOOTP servers write their internal bootptab
tables to a file when they receive a SIGUSR1 sig-
nal. You can check this file to verify that the hard-
ware and IP address are correct. You can use the
kill command to send signals. For example,
kill -
USR1 <process id of bootpd>
. Check your docu-
mentation for more information.
•
Check the system’s syslog file. Some BOOTP
servers write error messages into the syslog file.
Example:
Sep 6 14:38:43 bootpd[17565]:
hardware address not found:
004068175042
This message appears when the BOOTP server
receives a request from a device not in its internal
bootptab tables.
