
Troubleshooting Network Boot Problems
A-5
BOOTP Server Not Sending BOOTP Responses
If the BOOTP server is receiving BOOTP requests but failing to respond to them,
do the following:
1. Follow the instructions in the section “Displaying the BOOTP Server’s IP
Routes” later in this appendix.
2. Follow the instructions in the section “Debugging the BOOTP Server”
later in this appendix.
3. Make sure that the /etc/inetd.conf file contains no more than one bootps
entry.
If there is more than one entry, comment out the invalid entry. The valid entry
should be
bootps dgram udp wait root /etc/bootpd bootpd
4. Make sure that the tftp dgram entry in the /etc/inetd.conf file is correct
for your system.
Refer to “Setting Up a TFTP Server” in Chapter 2.
5. Refer to “Verifying the BOOTP Server Setup” later in this appendix.
ASN Fails to Perform Directed Netboot
If the ASN fails to perform Directed Netboot, do the following:
1. Make sure that the interface that connects the ASN to the TFTP file
server is configured with an IP address.
2. Make sure that all necessary files are, in fact, residing on the TFTP file
server.
Contact your local Bay Networks Technical Response Center if you perform the
instructions in these sections and cannot find and correct the problem.
ASN Netboots, But Fails to Load Applications
If the ASN Netboots a software image successfully, but displays an error message
indicating that it cannot load specific applications, it is failing to retrieve files
from the TFTP server that provided the software image. These files are necessary
to perform functions such as running the protocols specified in the configuration
file or displaying the log.
Komentarze do niniejszej Instrukcji