Filter
Top Products
Sun Fire 880 Server Product Notes 11
b. Determine if a console login session can be established through a ttya
connection.
If a working console connection can be established, the problem may not be a true
hang but instead a network related problem. For suspected network problems,
attempt to ping, rlogin, or telnet to another system that is on the same
sub-network, hub, or router that the system is on. If NFS services are served by
the affected system, determine if NFS activity is present on other systems.
2. If there are no responding login sessions, record the state of the system LEDs.
The system LEDs may indicate a hardware failure in the system. Refer to your
Sun Fire 880 Server Owner’s Guide for more information on system LEDs.
3. Attempt to bring the system to the ok prompt by issuing the Stop-A command
from your keyboard.
The Stop-A command attempts to bring a system with a standard or USB keyboard
to the ok prompt. For more information about system keyboards, see “About
OpenBoot Emergency Procedures” in the Sun Fire 880 Server Owner’s Guide.
a. If the system responds to the Stop-A command, issue the printenv command
to display the OpenBoot configuration variables.
For more information about OpenBoot configuration variables, see “About POST
Diagnostics” in the Sun Fire 880 Server Service Manual.
b. Set the diag-switch variable to true and the diag-level variable to max.
4. Issue the sync command to obtain a crash (core) dump file.
Saved 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 “Managing System Crash Information” in the Solaris System
Administration Guide.
The system will reboot automatically after issuing the sync command, provided
that the OpenBoot configuration variable is set to autoboot (the default value).
5. If you were not able to bring the system to the ok prompt, place the security
keyswitch to the Diagnostics position.
This forces the system to run POST and OpenBoot diagnostics during system
startup.
a. Press the system Power button for five seconds.
This causes an immediate hardware shutdown.
b. Wait at least 30 seconds; then power on the system by pressing the system
Power button.