HP-UX IP Address and Client Management Administrator's Guide HP-UX 11i v2, HP-UX 11i v3

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 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 indicates errors in the configuration file entry for the client.
Action:
For details on the error message, see “Error Logging” (page 114). 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 110)),
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 (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.
112 Configuring the BOOTP and TFTP Servers