Simple Network Debugging
If network boot is used on a local subnet and the
•Verify the client is on the same subnet as the
•Investigate instl_bootd errors in /var/adm/syslog/syslog.log.
•In the /var/adm/inetd.sec file, ensure the service instl_boots exists, and that the IP address 0.0.0.0 is allowed. (Normally, all addresses are allowed via 0.0.0.0.) The entry should look like:
instl_boots allow 0.0.0.0
•If /etc/services comes from NIS, make sure the NIS server has instl_boot* entries.
Logging to syslog.log
The bootpd and tftpd daemons have the ability to log requests and responses. The /etc/ inetd.conf file may be modified to enable logging. The bootpd
#tftp dgram udp wait root /usr/lbin/tftpd tftpd \
#bootps dgram udp wait root /usr/lbin/bootpd bootpd
The daemons log to the
NOTE: Logging should normally be disabled since it can consume a significant amount of disk space.
If the boot configuration includes multiple boot servers (for bootp relay, for example) it is often useful to enable logging on all servers.
Using bootpquery
To save time when configuring an
To use bootpquery, add the ba option to the appropriate entries in the /etc/bootptab file. Without this option, bootpd will send responses only to the client system making the boot request. The ba option requests the response be broadcast on the subnet, so any system is able to see the response, including the system where you are using bootpquery. For more information, see bootpquery(1M).
NOTE: The ba option should be removed once testing is completed.
The bootpquery output includes valuable debug information:
#bootpquery 0011855F549E
Received BOOTREPLY from hpignite.xyzco.com (10.1.1.11)
Hardware Address: | 00:11:85:5f:54:9e |
Hardware Type: | Ethernet |
IP Address: | 10.1.1.110 |
Boot file: | /opt/ignite/boot/nbp.efi |
RFC 1048 Vendor Information: | |
Subnet Mask: | 255.255.255.0 |
Gateway: | 10.1.1.1 |
Bootfile Size: | 24576 512 byte blocks |
28 Making Configuration Decisions for Ignite Servers