Chapter 6 Diagnostics, Monitoring, and Troubleshooting 157
Note – If you lose access to the console, but have a local display and physical access
to the server, you may gain access to the ok prompt using default NVRAM
parameters. For more information, see “How to Use Default NVRAM Parameters”
on page 175.
Note – If console output is redirected to the RSC console, you can also log in to an
RSC account on the server by using the RSC graphical user interface, or start a
command-line interface session by dialing in to the RSC modem or by using
telnet. Using RSC has the advantage of allowing access to the server console and
other RSC features even when the server operating system is not running. See the
Sun Remote System Control (RSC) User’s Guide for complete information about RSC.
About Diagnostic Tools
Both firmware-based and software-based diagnostic tools help you identify and
isolate hardware problems.
Two firmware tools are available that can run only before the Solaris Operating
Environment takes control. These tools are:
■ Power-on self-test (POST) diagnostics
■ OpenBoot Diagnostics
POST diagnostics can run as part of the power-on sequence. You can run OpenBoot
Diagnostics interactively from the ok prompt. You can run both of these tools locally,
and you can also run them remotely by using Sun Remote System Control (RSC) to
connect to the system console. However, RSC is not available until the server
operating environment software and RSC client and server software have been
installed and configured.
Two software tools are available that run directly from the Solaris Operating
Environment prompt. These software tools are:
■ Sun Validation Test Suite (SunVTS) software
■ Sun Management Center software
You can run both of these tools locally, and if the server operating environment is
running, you can also use the rlogin command to connect to the server remotely
and then use SunVTS or Sun Management Center software.
To Next Page
