Sun Microsystems SPARCcenter 2000 Service Manual page 74

3
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.
E.1
3-10
set up to boot over
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
Bad boot file
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.
Figure 3-10 Branch E: Checking the Net
SPARCcenter 2000/2000E Service Manual—June 1996
Is the system
No
the net?
Yes
No ethernet found
Does the boot
succeed?
E.2
If the system is stand-alone, the
two main indicators of net
problems are:
1. Ethernet jammed
2. No carrier
E.4
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.
The SBus card and transceiver
settings must match.
If RARP times out, the
configuration of the boot server
may be wrong.
E.3