Sun Microsystems SPARCserver 1000 Service Manual page 75

Checking the Network
E
A network problem may be caused by either the physical medium or the application
software. Check the network response as the system is initializing or booting over the net.
If this is a stand-alone system, see if there is interference from the network.
Connection OK.
Type go at the? prompt to
run it. The display should
read:
Loading [filename of bootfile]
Displays hexadecimal
number of bytes loaded.
Displays kernel messages.
System cannot load boot file. If file is missing or
corrupted, the system hangs, and no message is
displayed. If the wrong file is booted, display reads:
The file just loaded does not appear to be executable.
E.1
Is the system
set up to boot over
the net?
Yes
The system will attempt to boot over the net. It will list the
boot device, primarily the onboard ethernet.
Verify that the network cable is connected to the correct
SBus card (on the master board).
Yes
Does the boot
succeed?
Bad boot file
E.2
Figure 3-11 Branch E: Checking the Neta
Troubleshooting Flow Diagrams
If the system is standalone,
the two main indicators of net
problems are:
No
1. Ethernet jammed
2. No carrier
3. Link test setting wrong
E.4
No ethernet found
Connection not found or timed out. The
display reads:
Lost carrier (transceiver cable problem?)
ARP/RARP send failed.
Check ethernet cable and transceiver.
Check Link Integrity Test settings; SBus
card and transceiver settings must match.
If RARP times out, the configuration of the
boot server may be wrong.
E.3
3
3-11