HP-UX IP Address and Client Management Administrator's Guide HP-UX 11i v2, HP-UX 11i v3

□ 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
Cause:
The client specified filename as the boot file in its bootrequest, but bootpd could not find the
file in the tftp directory.
Action:
□ Make sure that you have configured tftpd with the entry in /etc/passwd for the user
tftp.
□ Ensure that the requested file is present in the tftp directory, which is usually the
/home/tftpdir directory or in the directory specified with the tftpd command. If not,
place the file in the /home/tftpdir directory and reboot the BOOTP client. If the requested
file exists in the directory, be sure it is readable by the user tftp. (See “Common tftpd
Problems” (page 113).)
Symptom:
The system log /var/adm/syslog/syslog.log contains the following message:
cannot route reply to client's_IP_address
Cause:
The server cannot directly reach the IP address specified for the client.
Troubleshooting BOOTP and TFTP Servers 111