156 Sun Fire 280R Server Service Manual • January 2001
■ “About Monitoring the System” on page 160
■ “About Monitoring the System Using Sun Remote System Control (RSC)” on
page 160
■ “About Monitoring the System Using Sun Management Center Software” on
page 163
■ “About Isolating Failed Components” on page 163
■ “About Isolating Failures Using Sun Remote System Control (RSC)” on
page 163
■ “About Isolating Failures Using Power-On Self-Test (POST)” on page 164
■ “About Isolating Failures Using OpenBoot Diagnostics” on page 164
■ “About OpenBoot Diagnostics Tests” on page 166
■ “About Exercising the System” on page 171
■ “About Exercising the System Using SunVTS Software” on page 171
In addition, this chapter contains information designed to help you troubleshoot
some common problems given their symptoms.
About Communicating With the System
To diagnose problems with your server, you need some way to enter system
commands and view output. There are three ways to do this.
1. If console output is not redirected to the RSC console, attach an ASCII character
terminal to serial port A.
You can attach a simple terminal or modem line to serial port A. For instructions,
see “How to Attach an Alphanumeric Terminal” on page 38.
2. Establish a tip connection from another Sun system.
The tip utility establishes a full-duplex terminal connection to a remote host.
Once the connection is established, a remote session using tip behaves like an
interactive session on a local terminal. For information about establishing a tip
connection, see “How to Set Up a tip Connection” on page 180.
3. Install a local graphics console on your server.
The server is shipped without a mouse, keyboard, monitor, or frame buffer for the
display of graphics. To install a local graphics console on a server, you must
install a graphics frame buffer into a PCI slot, and attach a mouse, monitor, and
keyboard to the appropriate back panel ports. See “How to Configure a Local
Graphics Console” on page 39 for detailed instructions.
To Next Page
