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

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 (BOOTP
Vendor Information Extensions) vendor information:
bs = boot_file_size
ds = domain_nameserver_addresses
gw = gateway_addresses
hn = hostname
lg = log_server_addresses
sm = subnet_mask
to = time_offset
Tnnn = generic_information
Cause:
Many RFC 1048 options are specified for the client’s configuration entry in the /etc/bootptab
file. The BOOTP protocol allows only 64 bytes of vendor extension information. When such
extended information is included in the bootreply, bootpd must also add a 4-byte vendor magic
cookie to the bootreply, a 1-byte tag indicating the end of the vendor information, and a 1-byte
or 2-byte tag for each field (depending on the format of the field) along with the value of the tag
itself. The total size of the extended information for a client must not exceed 64 bytes.
Action:
Ensure that the configuration contains only the necessary information to boot the client. Verify
that the BOOTP client contains only the necessary tags and that the tags are supported by the
client.
For example, if the client supports only one name server address, you need not list three name
server addresses with the ds tag. If the client does not support configuring its host name with
the hn tag, you need not include the hn tag.
Common tftpd Problems
This section discusses the common tftpd problems and possible resolutions.
Symptom:
A file transfer ‘timed out’ message is displayed. inetd connection logging (enabled with the
inetd -l command) does not show any connection to the TFTP server.
Cause:
The TFTP server, tftpd, did not start.
Action:
□ Ensure that the /etc/inetd.conf file contains the appropriate tftp entry.
□ Ensure you have reconfigured inetd with the command inetd -c.
□ Ensure that the bootpd server is configured properly for tftp to transfer the boot file. For
information on configuring bootpd, see “Configuring the BOOTP Server” (page 103). Now,
try to transfer a file on a different node on the network, instead of the server node.
If the server still fails to start when the client attempts the file transfer, it may be a connectivity
problem. See Installing and Administering LAN/9000 Software or the BOOTP client manual
(for example HP 700/X documentation).
Troubleshooting BOOTP and TFTP Servers 115