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

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 115).)
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.
Action:
Ensure you have specified the correct IP address for the client in the /etc/bootptab file.
Correct the entry and reboot the BOOTP client.
If the server must reply directly to the client, it must reside on the same network or subnet
as the client. If the client resides on another network, ensure that intervening servers are
configured to relay the bootrequests.
Ensure that the IP address you have chosen for the client is a valid IP address for the servers
network.
Symptom:
The system log contains one or more of the following error messages:
duplicate hardware address: link_address
bad host name: hostname
syntax error in entry for host hostname
unknown symbol in entry for host hostname
bad IP address for host hostname
bad subnet mask for host hostname
bad time offset for host hostname
bad vendor magic cookie for host hostname
bad reply broadcast address for host hostname
Cause:
Any of these error messages indicates errors in the configuration file entry for the client.
Action:
For details on the error message, see “Error Logging” (page 117). Correct the appropriate field
for the entry in the /etc/bootptab file and reboot the BOOTP client. Then, use bootpquery
to send a bootrequest to the client. Verify the system log file /var/adm/syslog/syslog.log
to check if the server replies. At debug level 2 (see “Helpful Configuration Changes” (page 112)),
bootpd logs the following sequence of messages when it responds to a bootrequest:
request from hardware address link_address
found ip_address hostname
114 Configuring the BOOTP and TFTP Servers