Diagnosing Problems

When LED codes (Table 9-1, Table 9-2, Table 9-3) indicate a hardware problem, several types of software programs are available to supply information about the problem.

Error Messages

Error messages and other system messages are saved in the /var/adm/messages file.

SunVTS

The latest version of SunVTS(TM) (online validation test suite) has several modes of testing, including low-impact testing, which can run with minimum affect on customer applications.

The SunVTS can also be used to stress-test Sun hardware, either in or out of the Solaris operating environment. By running multiple and multithreaded diagnostic hardware tests, the SunVTS software verifies the system configuration and functionality of most hardware controllers and devices.

SunVTS tests many board and system functions, as well as interfaces for Fibre Channel, SCSI, and SBus interfaces. SunVTS accepts user-written scripts for automated testing.

Refer to the SunVTS User's Guide for starting and operating instructions.

prtdiag(1M)

You can use the prtdiag command to display:

• System configuration, including information about clock frequencies, CPUs, memory, and I/O card types.

• Diagnostic information

• Failed field replaceable units (FRUs)

Refer to the prtdiag man page for instructions.

History Log Option

To isolate an intermittent failure, it may be helpful to maintain a prtdiag history log. Use the prtdiag command with the -l (log) option to send output to a log file in the /var/adm directory.

Running prtdiag

To run prtdiag, type:

% /usr/platform/sun4u/sbin/prtdiag

POST and OpenBoot

POST and OpenBoot work together in the system to test and manage system hardware.

POST resides in the OpenBoot PROM on each CPU/Memory+ board, I/O+ board, and Disk board. When the system is turned on, or if a system reset is issued, POST detects and tests buses, power supplies, boards, CPUs, SIMMs, and many board functions. POST controls the status LEDs on the system front panel and all boards. POST displays diagnostic and error messages on a console terminal, if available.

Only POST can configure the system hardware, and only POST can enable hot-pluggable boards. If a new unit (board or modular power supply) is added to the card cage after the system has booted, the new unit will not work until the system is rebooted, at which time POST reconfigures the system, using the units that are found in the system at that time.

POST does not test drives or internal parts of SBus cards. To test these devices, run OBP diagnostics manually after the system has booted. Refer to the OpenBoot Command Reference manual for instructions.

OpenBoot provides basic environmental monitoring, including detection of overheating conditions and out-of-tolerance voltages. For example, if an overheated board is found, OpenBoot issues a warning message. If the temperature passes the danger level, POST will put the overheated board(s) in low power mode.

OpenBoot also provides a set of commands and diagnostics at the ok prompt. For example, you can use OpenBoot to set NVRAM variables that reserve a board or a set of SIMMs for hot-sparing.

The following OpenBoot commands may be useful for diagnosing problems:

show-devs Command

Use the show-devs command to list the devices that are included in the system configuration.

printenv Command

Use the printenv command to display the system configuration variables stored in the system NVRAM. The display includes the current values for these variables, as well as the default values.

If the system cannot communicate with a 10BASE-T network, the Ethernet link test setting for the port may be incompatible with the setting at the network hub. See "Failure of Network Communications" for further details.

probe-scsi Command

The probe-scsi command locates and tests SCSI devices attached to the system. probe-scsi is run from the OpenBoot prompt.

When it is not practical to halt the system, you can use SunVTS as an alternate method of testing the SCSI interfaces.

Reference Documents for POST/OpenBoot

For more information, refer to:

• OpenBoot 3.x Command Reference, part number 802-3242

• Writing FCode 3.x Programs, part number 802-3230

Solstice SyMON

The Solstice(TM) SyMON(TM) program monitors system functioning and features a graphical user interface (GUI) to continuously display system status. Solstice SyMON is intended to complement system management tools such as SunVTS.

Solstice SyMON is accessible through an SNMP interface from network tools such as Solstice(TM) SunNet Manager(TM).

Refer to the Solstice SyMON User's Guide, part number 802-5355, for starting and operating instructions.