HP-UX HB v13.00 Ch-06 - Ignite-UX

HP-UX Handbook – Rev 13.00 Page 18 (of 58)
Chapter 06 Ignite-UX
October 29, 2013
 Check /etc/inetd.conf for “bootps” and “tftp” entries being uncommented. The
"tftp" line must contain /opt/ignite and /var/opt/ignite paths.
 Was inetd restarted or given an option to re-read the configuration files (inetd -c),
after they were edited? Is the inetd process running?
 Check for entries in /var/adm/inetd.sec that may cause inetd to deny service to
certain clients.
 Check /var/adm/syslog/syslog.log whether inetd was restarted, and that no
error messages are found. Check for messages from “bootpd” and “tftpd”
Check bootpd
 Check the /etc/bootptab entry. The MAC address should match the client MAC
address. Use "dhcptools -v" to validate the format of the /etc/bootptab file.
 Check for entries in /etc/dhcpdeny to insure that bootpd is not set up to deny
service for particular clients.
 Check /var/adm/syslog/syslog.log for a message from bootpd that indicates it
was started when a bootpd packet was received.
 Run ps –ef | grep bootpd and if an existing process is found, kill -9 the pid
then try the lanboot again.
 If packets were not received, use a tool such as tcpdump to check for network
packets. Verify that bootp packets are being seen by the system.
 Find out if there are other systems on the network that may also be replying to the
booting client system.
 If the system booting is on a different subnet to the bootp server ensure that any
router in between allows the forwarding of bootp requests (this is router specific on
how it would be configured).
Check tftpd
 Check the tftp line in /etc/inetd.conf to make certain /opt/ignite and
/var/opt/ignite directories are listed.
 Check the tftpd connection manually by using the "tftp" command, for example:
$ tftp <server-name>
tftp> get /opt/ignite/boot/nbp.efi /tmp/nbp.efi