Installing and Administering Internet Services

188 Chapter 5
Configuring TFTP and BOOTP Servers
Troubleshooting BOOTP and TFTP Servers
❏ Ensure the IP address you have chosen for the client is a valid IP
address for the server’s 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 means there are errors in the configuration
file entry for the client.
Action: See “Error Logging” on page 191 for an explanation of the error
message. Correct the appropriate field for the entry in /etc/bootptab
and reboot the BOOTP client. Use bootpquery to send a bootrequest to
/usr/lbin/bootpd for the client whose entry you have corrected.
Check the system log /var/adm/syslog/syslog.log to see if the
server replies. At debug level 2 (see “Helpful Configuration Changes” on
page 185), bootpd logs the following sequence of messages when it
responds to a bootrequest:
request from hardware address link_address
found ip_address hostname
vendor magic field is magic_cookie
sending RFC1048-style reply
Symptom: The client does not receive configuration information for the tags that
pertain to RFC 1048 vendor information:
bs = boot_file_size
ds = domain_nameserver_addresses
gw = gateway_addresses
hn = hostname
lg = log_server_addresses
sm = subnet_mask