Installing and Administering Internet Services

Chapter 5 193

Conﬁguring TFTP and BOOTP Servers

Troubleshooting BOOTP and TFTP Servers

Notice Log Level

There may be cases where bootpd receives a bootrequest but does not

send a bootreply. The reason is given in one of the following messages

and logged at the notice log level:

• hardware address not found: hardware_address

bootpd could not ﬁnd a conﬁguration entry for the client with the

indicated hardware_address. If bootpd should know about the client

that is booting, ensure that you have correctly speciﬁed the client’s

hardware address in the conﬁguration ﬁle.

• IP address not found: ip_address

bootpd could not ﬁnd a conﬁguration entry for the client with the

indicated ip_address. If bootpd should know about the client that is

booting, ensure that you have correctly speciﬁed the client’s IP

address in the appropriate conﬁguration ﬁle entry.

• requested file not found: ﬁlename

The client requested the boot ﬁle ﬁlename, but bootpd could not

locate it. Ensure that the boot ﬁle the client is requesting is located in

the tftp directory on the server system.

• cannot route reply to ip_address

The IP address to which bootpd must send the bootreply is for a

client or gateway that is not on a directly connected network. Ensure

that you have speciﬁed a valid IP address for the client or gateway.

Error Log Level

The following errors indicate problems with the conﬁguration ﬁle. They

are logged at the error log level. If you see any of these messages, you

should correct the indicated conﬁguration entry in /etc/bootptab and

try to reboot the BOOTP client:

• bad bootp server address for host hostname

A value speciﬁed for the bp tag is invalid. Values can be individual IP

addresses separated by a space, and/or one or more network

broadcast addresses.

• bad hardware mask value for host hostname