Sun Microsystems Sun Fire V440 Diagnostics And Troubleshooting Manual page 179

2. If there are no responding user sessions, record the state of the system LEDs.
The system LEDs might indicate a hardware failure in the system. You can use the
ALOM system controller to check the state of the system LEDs. Refer to the
Sun Fire V440 Server Administration Guide for more information about system LEDs.
3. Attempt to bring the system to the ok prompt.
For instructions, see "How to Get to the ok Prompt" on page 176.
If the system can get to the ok prompt, then the system hang can be classified as a
soft hang. Otherwise, the system hang can be classified as a hard hang. See
"Responding to System Hang States" on page 123 for more information.
4. If the preceding step failed to bring the system to the ok prompt, execute an
externally initiated reset (XIR).
Executing an XIR resets the system and preserves the state of the system before it
resets, so that indications and messages about transient errors might be saved.
An XIR is the equivalent of issuing a direct hardware reset. For further information
about XIR, see "Externally Initiated Reset (XIR)" on page 173.
5. If an XIR brings the system to the ok prompt, do the following.
a. Issue the printenv command.
This command displays the settings of the OpenBoot configuration variables.
b. Set the auto-boot? variable to true, the diag-switch? variable to true, the
diag-level variable to max, and the post-trigger and obdiag-trigger
variables to all-resets.
c. Issue the sync command to obtain a core dump file.
Core dump files provide invaluable information to your support provider to aid
in diagnosing any system problems. For further information about core dump
files, see "About the Core Dump Process" on page 113 and "Managing System
Crash Information" in the Solaris System Administration Guide, which is part of the
Solaris System Administrator Collection.
The system reboots automatically provided that the OpenBoot configuration
auto-boot? variable is set to true (default value).
Note – Steps 3, 4, and 5 occur automatically when the hardware watchdog
mechanism is enabled.
6. If an XIR failed to bring the system to the ok prompt, follow these steps:
a. Turn the system control keyswitch to the Diagnostics position.
This forces the system to run POST and OpenBoot Diagnostics tests during
system startup.
Chapter 7 Troubleshooting Hardware Problems 161