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

Helpful Configuration Changes
To ease troubleshooting, configure your system as follows:
• Ensure that syslogd is configured to log daemon information messages to the file
/var/adm/syslog/syslog.log. To check this configuration, make sure that
/etc/syslog.conf includes one of the following entries:
*.info /var/adm/syslog/syslog.log
or
daemon.info /var/adm/syslog/syslog.log
• Configure bootpd to start with debug logging set to level 2. This logging level causes
bootpd to log useful debugging messages about how bootpd replies to BOOTP clients.
Follow these steps to set the debug log level:
1. Add the -d 2 option to the bootpd line in the /etc/inetd.conf file as follows:
bootps dgram udp wait root /usr/lbin/bootpd
bootpd -d 2
2. Reconfigure inetd with the following command:
/usr/sbin/inetd
-c
3. Kill any bootpd daemon that is still running on your system. For example:
$ /usr/bin/ps -e /usr/bin/grep bootpd
root 20413 3006 0 10:51:09 ? 0:00 bootpd
$ /usr/bin/kill 20413
Common bootpd Problems
This section discusses certain common bootpd problems and possible remedies.
To view the information that bootpd places in the bootreply, enable a broadcast bootreply by
adding the ba tag to the client’s /etc/bootptab entry. Use the bootpquery command to
emulate the client’s bootrequest:
bootpquery client_link_address -s servername
bootpquery prints the reply it receives from the server, which allows you to examine the
information supplied to the client. Remove the ba tag from the configuration entry after you
have verified that the bootreply is correct.
Following are the symptoms, causes, and actions for bootpd problems.
Symptom:
The server’s system log file /var/adm/syslog/syslog.log does not contain any log messages
from /usr/lbin/bootpd indicating that the server has started.
A ps -ef listing does not show a running /usr/lbin/bootpd daemon.
Cause:
The server may not be started or it may not be receiving the client’s bootrequest.
Action:
□ Make sure that the /etc/inetd.conf file is configured correctly as specified in the earlier
sections.
□ Ensure that you have reconfigured inetd with the command inetd -c.
□ Check inetd’s logging in the /var/adm/syslog/syslog.log file to ensure that inetd
is configured to start bootpd.
110 Configuring the BOOTP and TFTP Servers