HP-UX IP Address and Client Management Administrator's Guide (October 2009)

To view the information that bootpd places in the bootreply, enable a broadcast bootreply by
adding the ba tag to the client’s /etc/bootptab entry. Use the bootpquery command to
emulate the client’s bootrequest:
bootpquery client_link_address -s servername
bootpquery prints the reply it receives from the server, which allows you to examine the
information supplied to the client. Remove the ba tag from the configuration entry after you
have verified that the bootreply is correct.
Following are the symptoms, causes, and actions for bootpd problems.
Symptom:
The server’s system log file /var/adm/syslog/syslog.log does not contain any log messages
from /usr/lbin/bootpd indicating that the server has started.
A ps -ef listing does not show a running /usr/lbin/bootpd daemon.
Cause:
The server may not be started or it may not be receiving the client’s bootrequest.
Action:
□ Make sure that the /etc/inetd.conf file is configured correctly as specified in the earlier
sections.
□ Ensure that you have reconfigured inetd with the command inetd -c.
□ Check inetd’s logging in the /var/adm/syslog/syslog.log file to ensure that inetd
is configured to start bootpd.
□ Verify that the server starts using the bootpquery command.
□ Check whether the client is on the same network as the BOOTP server. If the client is not on
the same network, ensure that intervening BOOTP servers are configured to relay bootrequest
broadcasts.
Symptom:
The system log file /var/adm/syslog/syslog.log contains one of the following messages:
hardware address not found: hardware_address
IP address not found: ip_address
Cause:
bootpd does not have an entry in /etc/bootptab for this client’s hardware address or IP
address.
Action:
□ Check the system log for any indication of syntax errors for the client’s configuration entry.
Correct the entry in the /etc/bootptab file and reboot the BOOTP client.
□ Ensure that the hardware address that you specified for the ha tag matches the hardware
address that /usr/lbin/bootpd is unable to find. Correct the tag and reboot the BOOTP
client.
□ Ensure the hardware type tag ht has the correct value for the client. For example, if you
have specified ether but the client is reporting ieee in its bootrequest, bootpd rejects the
request. Correct the tag and reboot the BOOTP client.
Symptom:
The system log file /var/adm/syslog/syslog.log contains the following message:
requested file not found: filename
Troubleshooting BOOTP and TFTP Servers 113