Sun Microsystems SunSwift SPARCserver 1000, Руководство по обслуживанию

Страница: 75 / 218

Troubleshooting Flow Diagrams 3-11
3
Figure 3-11 Branch E: Checking the Neta
E
E.4
Yes
No
Yes
Bad boot file
No ethernet found
E.3
E.2
E.1
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.
If the system is standalone,
the two main indicators of net
problems are:
1. Ethernet jammed
2. No carrier
3. Link test setting wrong
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).
Is the system
set up to boot over
the net?
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.
Does the boot
succeed?
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.
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.
Checking the Network