Troubleshooting
D.8
Overview to Troubleshooting Internet Loading Problems
Following the software installation, you should attempt to initialize all units so that they load the
new release of software. If you are using a UNIX host for a load server, and the loading process
fails, the most likely reasons are:
1. BOOTP or RARP is not properly configured or are not running at the UNIX load host.
2. TFTP is not properly configured or is not running at the UNIX load host.
3. There is a problem with UNIX file protections or ownership for either the load image or the
parameter file.
The fastest way to identify the cause of the loading failure is to initialize a unit which has a
terminal connected to a serial port, wait until it passes self-test diagnostics, and then
repeatedly press the RETURN key in order to observe the messages that are displayed during
the loading sequence. You can then isolate the loading problem by observing how far the unit
gets in the loading process. The following is a description of the messages you will see during
the loading process, and a description of the problem you may have encountered. Sections D.9
through D.12 describe how to resolve the specific problems you may encounter.
a . After you initialize the unit, and it completes self-test diagnostics, press the RETURN key,
once every few seconds. You will observe a message similar to the following one:
Terminal Server, Type 76, Rev x.xx.x
Ethernet address 08-00-87-xx-xx-xx Port 1
Initializing...
This message appears for approximately 10 seconds.
b. Next observe a message similar to the following one:
Terminal Server, Type 76, Rev x.xx.x
Ethernet address 08-00-87-xx-xx-xx Port 1
Requesting network load service
The last line changed. This message lasts for approximately 20 to 80 seconds (20 seconds for
each load/dump configuration you have enabled; the message stops when a service offer is
received).
c . Next observe a message similar to the following one:
Terminal Server, Type 76, Rev x.xx.x
Ethernet address 08-00-87-xx-xx-xx Port 1
Evaluating service offers
If you don't observe this message, after the 80 second period (mentioned in step b) has elapsed,
the most likely reason for loading failure is that BOOTP or RARP is not properly configured
for loading the unit or it is not running at the UNIX host. Refer to section D.9 or D.10 to
troubleshoot this problem.
0021
D-95
