Volume II - Diagnostics

Self-Test Diagnostic

The CPU Self-Test runs in either the Normal or Diag mode. Set the CPU DIAG/NORM switch to DIAG to enable the Diag mode. Set the CPU Diag/Norm switch to NORM to enable the Normal mode. Some systems do not have this capability.

The jumper or NVRAM parameter changes required to set the Sun386i CPU board to Diag mode or to By-pass mode are described in the CPU Configuration Section. By-pass mode forces the CPU to skip most of the Self-Tests and go to the Prom Monitor.

In the Normal mode, the CPU runs through a basic set of tests and reports errors on the diagnostic LEDs. The meanings of the failure patterns of these LEDs are not always consistent between machine types. Refer to the appropriate Field Service Manual and the Troubleshooting Section of this Handbook for self-test LED error code information.

When the CPU is set to the Diag mode, the self-tests are more extensive than in the Normal mode and include a complete memory check. Connect an ASCII terminal to port A to display the self-test output when the system is in Diag mode. Use full duplex, 9600 baud, XON/XOFF, 8bits/1 stop bit, and no parity with a null modem type cable.

Extended Diagnostics

The diagnostics built into the EPROM on CPU boards are designed to verify a working boot path so that more comprehensive diagnostics can be loaded.

Enter "x" at the PROM Monitor prompt to display the Extended Diagnostics menu:

>x

The Extended Diagnostics menu displays the tests available. At the prompt select a test for execution. To return to the PROM Monitor, enter "q" to the Extended Diagnostics prompt.

EPROM space is limited. Some tests were removed from the 2.8 EPROM in November 1988 to make room for more boot and display device drivers.

With the 2.8 EPROM, boot path tests are no longer accessed through the Extended Diagnostics menu. They are executed directly from the PROM Monitor prompt using the command:

>b*device()

where device is the appropriate disk or tape device to be tested.

In the Sun-4c, the PROM Monitor has changed to the Open PROM Toolkit to take advantage of the FORTH programming language. Refer to the EPROM and NVRAM Information in the CPU section of Configurations for more information.

Sun386i Hardware Diagnostics

The Sun386i Hardware Diagnostics are a diagnostic tool for nontechnical Sun386i users.

The Hardware Diagnostics are an automated subset of the Diagnostic Executive. These tests are used to find a FRU level failure. The diagnostic prints an error indication, reports the probable subsystem that needs help, and returns control to the PROM Monitor if a problem is found.

To execute the Hardware Diagnostics, halt the system, install the Hardware Diagnostic diskette in the floppy drive, and cycle the power.

The Hardware Diagnostics compare the system configuration with the configuration information stored in NVRAM. If a conflict exists between the system configuration and the contents of NVRAM, answer the displayed questions. All the tests are then displayed with an indication of which tests will be executed.

Select the tests with the return key and toggle the Yes/No choice with the space key. When the last return is entered, verify the configuration. The tests then run to completion or until an error occurs.

Diagnostic Executive

The Diagnostic Executive (Exec) provides a single, unified diagnostic environment with one user interface. The diagnostic tests reside in individual programs that work through the Exec platform. The platform provides a consistent interface and multitasking capabilities. Some features are:

Multiple Consoles
The Exec can run from any control terminal. This may be a monitor, serial port, or a remote console.
Error Logging
The Exec provides the ability to capture error messages into a logfile. The logfile may reside on a local disk or on a server.
Script Execution
Command scripts can be used to drive the menus without further user input.
Remote Execution
The Exec has the ability to perform remote diagnostics over a modem connected to a Serial Port or over Ethernet.

Due to the complexity of the Exec, individual tests will not be discussed here. Refer to the Sun Diagnostic Executive User Manuals for additional information. Tables of Contents for the Exec are included in this section.

Loopback connectors are required for some tests. The loopback connectors are described at the end of this section.