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

• vendor magic field is magic_cookie
sending CMU-style reply
sending RFC1048-style reply
Displays the vendor magic cookie in the client’s bootrequest and the corresponding vendor
magic cookie used in the bootreply. These messages are logged at debug level 2.
• bootptab mtime is time
bootpd uses the indicated modification time to determine if the configuration file has been
modified and whether the configuration file needs a reread. This message is logged at debug
level 3.
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 find a configuration entry for the client with the indicated
hardware_address. If bootpd must be aware of the client that is booting, ensure that
you have correctly specified the client’s hardware address in the configuration file.
• IP address not found: ip_address
bootpd could not find a configuration entry for the client with the indicated ip_address.
If bootpd must be aware of the client that is booting, ensure that you have correctly specified
the client’s IP address in the appropriate configuration file entry.
• requested file not found: filename
bootpd could not locate the boot file requested by the client. Ensure that the boot file is
located in the tftp directory on the server system.
• cannot route reply to ip_address
The IP address of the client or gateway to which bootpd sends the bootreply does not exist
on a directly connected network. Ensure that you specify a valid IP address for the client or
gateway.
Error Log Level
When you find any of these error messages, you must correct the indicated configuration entry
in the /etc/bootptab file and reboot the BOOTP client. The following errors are logged at the
error log level:
• bad bootp server address for host hostname
A value specified for the bp tag is invalid. Values can be individual IP addresses separated
by a space, and an optional one or more network broadcast addresses.
• bad hardware mask value for host hostname
The formatting for the hardware address mask tag hm is incorrect in the configuration file
entry for hostname. Correct the configuration entry and reboot the BOOTP client. The
subnet mask must be specified in hexadecimal notation.
• bad hardware type for host hostname
The value specified for the ht tag is an unsupported hardware type. For a list of the supported
hardware types, type man 1M bootpd at the HP-UX prompt.
• bad hostname: hostname
The name given in the hostname field is an invalid host name. Correct the host name and
reboot the BOOTP client. A valid host name must begin with a letter followed by any number
of letters, digits, periods, or hyphens.
118 Configuring the BOOTP and TFTP Servers