280R Guide
280R Guide
Owner’s Guide
This product or document is distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or
document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party
software, including font technology, is copyrighted and licensed from Sun suppliers.
Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in
the U.S. and other countries, exclusively licensed through X/Open Company, Ltd.
Sun, Sun Microsystems, the Sun logo, AnswerBook2, docs.sun.com, Sun Fire, Sun Enterprise Volume Manager, Sun StorEdge, Sun StorEdge
LibMON, Java, Jiro, OpenBoot, OpenWindows, Solaris Management Console, Solaris Resource Manager, Solstice DiskSuite, Solstice
AdminSuite, Solstice AutoClient, Solstice Backup, and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems,
Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC
International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun
Microsystems, Inc.
The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges
the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun
holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN
LOOK GUIs and otherwise comply with Sun’s written license agreements.
Federal Acquisitions: Commercial Software—Government Users Subject to Standard License Terms and Conditions.
DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,
INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
Copyright 2001 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, CA 94303-4900 Etats-Unis. Tous droits réservés.
Ce produit ou document est distribué avec des licences qui en restreignent l’utilisation, la copie, la distribution, et la décompilation. Aucune
partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sans l’autorisation préalable et
écrite de Sun et de ses bailleurs de licence, s’il y en a. Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de
caractères, est protégé par un copyright et licencié par des fournisseurs de Sun.
Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l’Université de Californie. UNIX est une marque
déposée aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd.
Sun, Sun Microsystems, le logo Sun, AnswerBook2, docs.sun.com, Sun Fire, Sun Enterprise Volume Manager, Sun StorEdge, Sun StorEdge
LibMON, Java, Jiro, OpenBoot, OpenWindows, Solaris Management Console, Solaris Resource Manager, Solstice DiskSuite, Solstice
AdminSuite, Solstice AutoClient, Solstice Backup, et Solaris sont des marques de fabrique ou des marques déposées, ou marques de service, de
Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays. Toutes les marques SPARC sont utilisées sous licence et sont des marques de
fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d’autres pays. Les produits portant les marques SPARC
sont basés sur une architecture développée par Sun Microsystems, Inc.
L’interface d’utilisation graphique OPEN LOOK et Sun™ a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun
reconnaît les efforts de pionniers de Xerox pour la recherche et le développement du concept des interfaces d’utilisation visuelle ou graphique
pour l’industrie de l’informatique. Sun détient une licence non exclusive de Xerox sur l’interface d’utilisation graphique Xerox, cette licence
couvrant également les licenciés de Sun qui mettent en place l’interface d’utilisation graphique OPEN LOOK et qui en outre se conforment aux
licences écrites de Sun.
LA DOCUMENTATION EST FOURNIE “EN L’ETAT” ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES
OU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT
TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L’APTITUDE A UNE UTILISATION PARTICULIERE OU A
L’ABSENCE DE CONTREFAÇON.
Please
Recycle
Regulatory Compliance Statements
Your Sun product is marked to indicate its compliance class:
• Federal Communications Commission (FCC) — USA
• Industry Canada Equipment Standard for Digital Equipment (ICES-003) — Canada
• Voluntary Control Council for Interference (VCCI) — Japan
• Bureau of Standards Metrology and Inspection (BSMI) — Taiwan
Please read the appropriate section that corresponds to the marking on your Sun product before attempting to install the
product.
iii
ICES-003 Class A Notice - Avis NMB-003, Classe A
This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.
EMC
European Union
This equipment complies with the following requirements of the EMC Directive 89/336/EEC:
EN55022:1998/CISPR22:1997 Class A
EN550024:1998 EN61000-4-2 4 kV (Direct), 8 kV (Air)
EN61000-4-3 3 V/m
EN61000-4-4 1.0 kV AC Power Lines, 0.5 kV Signal DC & Power Lines
EN61000-4-5 1 kV AC Line-Line & Outdoor Signal Lines
2 kV AC Line-Gnd, 0.5 kV DC Power Lines
EN61000-4-6 3V
EN61000-4-8 1 A/m
EN61000-4-11 Pass
EN61000-3-2:1995 w/Amendments 1,2 Pass
EN61000-3-3:1995 Pass
Safety
This equipment complies with the following requirements of the Low Voltage Directive 73/23/EEC:
EC Type Examination Certificates:
EN60950:1992, 2nd Edition, Amendments 1,2,3,4,11 TUV Rheinland Certificate No.
IEC 950:1991, 2nd Edition, Amendments 1,2,3,4
Evaluated to all CB Countries CB Scheme Certificate No.
FDA DHHS Accession Number (Monitors Only)
Supplementary Information
This product was tested and complies with all the requirements for the CE Mark.
vii
viii Sun Fire 280R Server Owner’s Guide • January 2001
Safety Agency Compliance Depending on the type of power switch your device has,
one of the following symbols may be used:
Statements
Off - Removes AC power from the system.
Read this section before beginning any procedure. The
following text provides safety precautions to follow when
installing a Sun Microsystems product.
ix
SELV Compliance Lithium Battery
Safety status of I/O connections comply to SELV
requirements. Caution – On Sun CPU boards, there is a
lithium battery molded into the real-time
Power Cord Connection clock, SGS No. MK48T59Y, MK48TXXB-XX,
MK48T18-XXXPCZ, M48T59W-XXXPCZ, or
MK48T08. Batteries are not customer
Caution – Sun products are designed to work replaceable parts. They may explode if
with single-phase power systems having a mishandled. Do not dispose of the battery in
grounded neutral conductor. To reduce the fire. Do not disassemble it or attempt to
risk of electric shock, do not plug Sun recharge it.
products into any other type of power system.
Contact your facilities manager or a qualified
electrician if you are not sure what type of Battery Pack
power is supplied to your building.
Caution – The power switch of this product Caution – Do not operate Sun products
functions as a standby type device only. The without the top cover in place. Failure to take
power cord serves as the primary disconnect this precaution may result in personal injury
device for the system. Be sure to plug the and system damage.
power cord into a grounded power outlet that
is nearby the system and is readily accessible.
Do not connect the power cord when the
power supply has been removed from the
system chassis.
Precauciones de seguridad
Couvercle Para su protección observe las siguientes medidas de
Pour ajouter des cartes, de la mémoire, ou des unités de seguridad cuando manipule su equipo:
stockage internes, vous devrez démonter le couvercle de
■ Siga todas los avisos e instrucciones marcados en el
l’unité système Sun. Ne pas oublier de remettre ce couvercle
equipo.
en place avant de mettre le système sous tension.
■ Asegúrese de que el voltaje y la frecuencia de la red
eléctrica concuerdan con las descritas en las etiquetas
Attention: – il est dangereux de faire de especificaciones eléctricas del equipo.
fonctionner un produit Sun sans le couvercle ■ No introduzca nunca objetos de ningún tipo a través
en place. Si l’on néglige cette précaution, on de los orificios del equipo. Pueden haber voltajes
encourt des risques de blessures corporelles et peligrosos. Los objetos extraños conductores de la
de dégâts matériels. electricidad pueden producir cortocircuitos que
provoquen un incendio, descargas eléctricas o daños
en el equipo.
Conformité aux certifications Laser
Les produits Sun qui font appel aux technologies lasers sont Símbolos
conformes aux normes de la classe 1 en la matière. En este libro aparecen los siguientes símbolos:
ADVARSEL – Litiumbatteri —
Eksplosjonsfare.Ved utskifting benyttes kun
batteri som anbefalt av apparatfabrikanten.
Brukt batteri returneres apparatleverandøren.
Sverige
Danmark
ADVARSEL! – Litiumbatteri —
Eksplosionsfare ved fejlagtig håndtering.
Udskiftning må kun ske med batteri af samme
fabrikat og type. Levér det brugte batteri
tilbage til leverandøren.
Suomi
Preface xxiii
1. System Overview 1
About the Sun Fire 280R Server Hardware 1
About Front and Back Panel Features 5
About the Sun Fire 280R Server Software 11
2. System Setup 13
About the Parts Shipped to You 14
How to Install the Sun Fire 280R Server 15
About System Rackmounting 21
How to Install the System Into the Rack 23
How to Remove the System From the Rack 30
About Communicating With the System 33
How to Attach an Alphanumeric (ASCII) Terminal 34
How to Configure a Local Graphics Console 36
xix
How to Power On the System 40
How to Power On the System With
Full Diagnostics Enabled 43
How to Install the System Software 46
How to Select the Boot Device 48
How to Configure the Standard Ethernet Interface 51
How to Configure the Remote System Control (RSC) Ethernet Interface 53
How to Add an Ethernet Interface 54
How to Connect a Twisted-Pair Ethernet (TPE) Cable 57
How to Boot the System Using the Standard Ethernet Interface 59
How to Power Off the System 61
3. System Administration 63
About System Reliability, Availability, and Serviceability Features 64
About Managing the System 71
About Storage Management Tools 76
About Personal Computer Connectivity 78
Contents xxi
6. Diagnostics, Monitoring, and Troubleshooting 157
About Communicating With the System 159
About Diagnostic Tools 160
About Using Diagnostic Tools to Monitor, Diagnose, and Exercise the
System 162
How to Monitor the System 175
How to Isolate Failed Components 178
How to Exercise the System 198
Reference for the Fibre Channel-Arbitrated Loop (FC-AL) Port Connector 214
The Sun Fire 280R Server Owner’s Guide answers your questions about setting up and
running the Sun Fire 280R server. Features and options, setup and installation,
system management, hardware and software configuration, network administration
information, using internal storage devices, and diagnostics and troubleshooting
topics for the Sun Fire 280R server are covered in this manual.
With the exception of internal disk drives in the Sun Fire 280R server, all component
part installation or replacement is to be performed by a qualified service provider.
This manual presents information in a modular format designed to answer the type
of questions that you might ask while installing, configuring, and using the Sun Fire
280R server. Look at the module headings and you’ll find the cue words that direct
you to the categories of questions and answers, such as:
■ How to . . . How do I do something?
■ About . . . Is there more information about this topic?
■ Reference for . . . Where can I find reference material for something?
You determine how much or how little of the information you need to read.
Using the table of contents, the information or task list on the first page of each
chapter, and the index, you can quickly find a specific topic or task. The information
modules are brief; however, they are interrelated and refer you to other modules that
you may want or need to read. For instance, if you’re installing a disk drive and
you’re already familiar with the task, you could go to “How to Install a Disk Drive”
and follow the installation procedure. But if you need more background information
before performing the task, you should first read “About Disk Drives.”
xxiii
How This Book Is Organized
Chapter 1 describes the system’s hardware and software features. Descriptions of the
hardware front and back panel features, the system’s devices, and status indicators
and controls are included. Software features are summarized and listed.
Chapter 2 describes how to attach the cables needed to get the Sun Fire 280R server
hardware up and running. For information about rackmounting the server, consult
the Sun Fire 280R Server Setup and Rackmounting Guide that accompanied your
system. For the operating system software, the chapter explains what you need to do
and points you to the appropriate software manuals for additional information.
Chapter 3 focuses on the software in the server and its improved reliability,
availability, and serviceability features and system administrative information.
Chapter 5 provides what you need to know, and need to do, to install, remove, or
replace an internal disk drive. In addition, basic information about how to use the
system’s internal storage devices such as the hard disk drive, the DVD-ROM
drive(s), and tape devices is also covered.
Chapter 6 introduces the diagnostic tools available for the system and explains how
to use these tools. It also introduces the suite of software tools and how to use them
to monitor your system, isolate problems, and troubleshoot the system. The tools
should help you determine what component of the system (if any) needs to be
replaced.
Preface xxv
Shell Prompts
Shell Prompt
C shell machine_name%
C shell superuser machine_name#
Bourne shell and Korn shell $
Bourne shell and Korn shell superuser #
Related Documentation
The following documents contain topics that relate to the information in the
Sun Fire 280R Server Owner’s Guide.
Application Title
Server rackmounting and setup Sun Fire 280R Server Setup and Rackmounting Guide
Installation and removal of parts Sun Fire 280R Server Service Manual
by qualified service providers
Late-breaking product news and Sun Fire 280R Server Product Notes
information
System diagnostics SunVTS User’s Guide
SunVTS Test Reference
SunVTS Test Reference Manual
SunVTS Toolkit Test Developer’s Guide
SunVTS Quick Reference Card
OpenBoot Command Reference Manual
OpenBoot Quick Reference
OpenBoot Supplement for PCI
System management Sun Management Center Software Documentation Set
Sun Management Center Software User’s Guide
Sun Management Center Software Release Notes
Sun Management Center Supplement for Workgroup Servers
Sun Management Center Developer Environment Release
Notes
http://docs.sun.com
For a list of documents and how to order them, visit the Sun Documentation Center
on Fatbrain.com at:
http://www.fatbrain.com/documentation/sun
Preface xxvii
Sun Welcomes Your Comments
We are interested in improving our documentation and welcome your comments
and suggestions. You can email your comments to us at:
Please include the part number (806-4806) of your document in the subject line of
your email.
System Overview
This chapter introduces you to the Sun Fire 280R server and explains some of its
hardware and software features. The following information is covered in this
chapter:
■ “About the Sun Fire 280R Server Hardware” on page 1
■ “About Front and Back Panel Features” on page 5
■ “About the Sun Fire 280R Server Software” on page 11
Processing power is provided by one or two UltraSPARC III CPU modules, each
with up to 8 Mbytes of local high-speed external cache memory. The system bus
synchronizes automatically to the clock rate of the installed CPUs, and operates at a
clock rate that is a ratio of the speeds between CPU modules and the bus. For more
information about CPU modules, see “About Central Processing Unit
(CPU) Modules” on page 83.
1
memory I/O performance, the system transfers 64 bytes of data into or from
memory on each memory transfer. For more information about system memory, see
“About System Memory” on page 80.
There are four industry-standard Universal Serial Bus (USB) 12-Mbps ports on the
back panel. The system supports a Sun Type 6 USB keyboard and a Sun USB mouse;
each device uses a separate port. Industry-standard USB hubs are also supported.
For more information, see “About the Universal Serial Bus (USB) Ports” on page 102.
A standard Remote System Control (RSC) card is installed in every system. The RSC
card supports internal host environmental monitoring; host power-on and power-off
from the firmware level; remote or local automatic notification via email or pager for
hardware and software failures; and viewing of server boot logs and run-time logs.
Multiple simultaneous remote access connections to the RSC card on each host are
configurable over modem and serial ports, or over the card’s 10-Mbps standard
You can attach up to four external tape devices to the standard 68-pin 40-Mbyte per
second UltraSCSI port. Additional external tape devices are supported with
appropriate PCI host adapter cards.
You can easily connect the Sun Fire 280R server to either a 10-Mbps or a 100-Mbps
Ethernet by means of an auto-sensing Ethernet interface provided on the system’s
main logic board. You can establish Ethernet interfaces or connections to other
networks, such as Fiber Distributed Data Interface (FDDI), Asynchronous Transfer
Mode (ATM), or to token ring by installing the appropriate PCI interface cards. For
more information, see “About Peripheral Component Interconnect (PCI) Buses” on
page 84.
The system console device can be a standard ASCII character terminal, a local
windowing subsystem, or it can also be redirected to display over a supported
telnet connection using the RSC card. You can connect an ASCII terminal to one of
the system’s two serial ports, while a local windowing subsystem in a graphics
console requires installation of a PCI frame buffer card, monitor, keyboard, and
mouse. (Sun’s Universal Port Architecture (UPA) graphics is not supported in the
Sun Fire 280R server.) You can also administer the server from a remote system
connected to the server over an Ethernet network connection, or you can use an
Ethernet connection via the RSC and a redirected system console. See “About
Communicating With the System” on page 33.
Full power is provided by one 560-watt power supply with its dual internal fans.
System configurations with two power supplies provide both redundancy and full
hot-swap capability. For more information about the power supplies, see “About
Power Supplies” on page 95.
The system is housed in a standard Electronic Industries Association 310 (EIA 310)
specification-compliant rackmountable enclosure measuring 6.95 inches high, 17.25
inches wide, and 27.25 inches deep (17.6 cm x 43.8 cm x 69.2 cm). The system has a
The Sun Fire 280R server is shipped with a rackmounting kit for installation into a
standard EIA 310-compliant 29-inch to 32-inch (73.6-cm to 81.3-cm) deep and 19-inch
(48.26-cm) wide rack, with at least four rack units (7.0 inches, 17.78 cm) of vertical
mounting space available per server, and sufficient load-bearing capacity.
Sun Fire 280R system reliability, availability, and serviceability (RAS) are enhanced
by features that include:
■ Error correction and parity checking for improved data integrity
■ Easily accessible LED status indicators
■ Hot-pluggable internal disk drives with status indicators and easy front access
■ External support for RAID 0, 1, 0 + 1, and 5 implementations
■ System environmental monitoring and control
■ Power system monitoring and fault notification
■ Power supply redundancy
■ Hot-swappable power supplies with easy front panel access
■ Automatic system recovery
■ Improved system diagnostics software
■ Enhanced system availability software
■ Remote System Control card access to remotely boot, monitor, and control servers
■ Easy front or top access to all internal replaceable components
For additional hardware details, see “About System Reliability, Availability, and
Serviceability Features” on page 64, and for software details, see “About the Sun Fire
280R Server Software” on page 11 and “About Managing the System” on page 71.
When the key in the front panel keyswitch is in the Locked position, the front doors
are also locked preventing access to the disk drives and power supplies. Before you
close the doors, make sure that the key is in the Power-On/Off position and that you
overlap the front doors correctly as you close them. After closing the doors, to lock
them insert and turn the key to the Locked position; then remove the key.
Note – This same key also controls the system cover lock on the top of the system
(see “Reference for Physical Specifications” on page 218). If you lose the key, contact
your Sun sales representative about replacing the key.
Power-On/Off DVD-ROM or
position optional tape drive
Locked
position Status panel
Keyswitch control
For more information about status panel controls and indicators, see “Status and
Control Panel Features” on page 8.
Opening the system’s front doors provides access to the system’s hot-pluggable
internal disk drives. Releasing the power supply retainers affords qualified service
personnel access to the hot-swappable power supplies. The illustration below shows
the additional accessible features when the system front doors are open.
Internal drive 0
(default) Internal disk Power supply DVD-ROM or
Internal drive 1 drive LEDs retainers optional tape drive
(option)
Systems may be configured with one or two power supplies, and one or two disk
drives either of which is accessible when the system front doors are open. Each
power supply has an LED that displays the AC power, DC power, and fault status of
the supply. Only qualified service providers should access the power supplies. See
“Power Supply Failure” on page 195 for operational details of the LEDs.
Each disk drive has an LED indicating when lit steadily that the drive is present, and
if the LED is blinking that there is activity on the disk. For additional information
see “About Power Supplies” on page 95.
A ground screw hole 0.157 inch in diameter and 0.236 inch deep (4 mm x 6 mm) is
located in the lower-right corner of the back panel. Contact your Sun sales
representative if you need a grounding strap.
Diagnostics position
Locked position
This setting does not allow the RSC card to restart the
server. However, the RSC card can still report its data to
the software using the system’s standby power.
When you first power on the system, both the system indicator LEDs are lit. The
general fault indicator lights steadily for two seconds and is then toggled off. After
that, the LEDs operate as described in the following table.
For more information about these management features, see Chapter 3. For more
information about the Solaris 8 Operating Environment support for testing and
diagnostics, see Chapter 6.
The OpenBoot firmware on the Sun Fire 280R server supports the following tools:
■ Power-on self-test (POST)
■ OpenBoot Diagnostics
■ Access to the ok prompt for the RSC hardware and software, and system console
redirection
The operating environment tools complement the firmware tools and provide a
comprehensive set of diagnostic tools for the hardware. For more information about
the RSC card, see “About the Remote System Control (RSC) Card and Ports” on
page 107. For more information about how the RSC card extends the server’s
software, see “About the Remote System Control (RSC) Software” on page 110.
System Setup
This chapter, used with the Sun Fire 280R Server Setup and Rackmounting Guide,
describes how to rackmount a server and attach all cords and cables needed to get
the Sun Fire 280R server up and running. Where software is involved, this chapter
explains some of what you need to do, and then points you to the appropriate
software manuals for the rest of the information.
13
About the Parts Shipped to You
Your system is “configured-to-order,” which means that most internal options that
you ordered are pre-installed at the factory. However, if you ordered options that are
not factory-installed, these will be shipped to you separately.
You will receive a rackmounting kit (standard) or kits (ordered separately) to install
your system(s) into a rackmounting cabinet. See the Sun Fire 280R Server Setup and
Rackmounting Guide for a list of parts in the rackmounting kit. You may also have
separately ordered one or more rackmounting cabinets with accompanying
documentation (ordered separately). Verify that you have received everything you
ordered.
In addition, you should have received the media and documentation for all
appropriate system software (ordered separately). Verify that you have received
everything you ordered.
Note – Inspect all shipping cartons for evidence of physical damage. If a shipping
carton is damaged, request that the carrier's agent be present when the carton is
opened. Keep all contents and packing material for the agent's inspection.
Once you have answered these questions, you are ready to begin the installation
procedure.
What to Do
1. Verify that you have received all the parts of your system.
See “About the Parts Shipped to You” on page 14.
Note – Any additional options, other than the disk drives, should be installed by a
qualified service provider.
4. Ensure that the system’s front panel keyswitch is in the Off position.
See “Status and Control Panel Features” on page 8.
5. Once the system is installed into the rack, connect the AC power cord to the
power inlet labeled (1) at the back of the system.
6. Attach a strain relief (if necessary) and connect the other end of the cord to a
grounded AC power outlet.
To prevent accidental or inadvertent removal of an AC power cord from its inlet, use
the strain relief. The strain relief is a plastic tie-wrap and pedestal that is installed
into the back panel of the system. Use these reliefs to manage the power cords after
you have installed the cords into the AC inlets in the server.
Note – Each outlet must connect the system to a 15A circuit for North America and
Japan, and to a 10A circuit for Europe. See your local electrical codes.
Note – If your server includes a second power supply, connect the second AC
power cord to the left inlet labeled (2). You may connect the second power supply to
the same AC circuit as the first supply. However, for increased system redundancy
connect each power supply to a separate circuit.
Tab
Note – The RSC card Ethernet and modem interfaces are available only after you
have installed the operating system software and the RSC software. Consult the
Sun Remote System Control (RSC) User’s Guide for more details about configuring
these interfaces.
13. Load the Sun Fire 280R server hardware online documentation.
See the installation instructions that accompany the CD-ROM disc in the Sun Fire
280R documentation set.
Shipped with your system is the Sun Fire 280R Server Setup and Rackmounting Guide,
which describes how to rackmount your server. Use the guide for rackmounting
instructions.
Rackmounting Guidelines
■ Install the slide assemblies for the first server in the lowest possible rack position.
■ For stability, install the remaining servers from the lowest system upward into the
rack, as shown in the next figure.
■ To mount the server in an EIA standard rack, allow four RUs per system to obtain
the highest density in the rack. Use the supplied Rack Buddy rackmounting
template to locate the correct holes for server placement in the rack.
Use the Rack Buddy to determine at what height in the rack you will install the
server slide assemblies (and other subsequent server slide assemblies).
For example, a Sun cabinet might have 36 configurable vertical RUs and could
support up to nine servers. To maximize server density in a 72-inch (182.8-cm) rack,
install the slide assembly brackets starting for the lowest enclosure at rail hole 9 (in
a rack configured with a power sequencer in holes 1 to 6), and add subsequent
brackets starting at rail holes 21, 33, 45, 57, 69, 81, 93, and 105. The following figure
illustrates such a configuration.
Holes
9, 10
or 11
Holes 33, 34, or 35 Third
First
Holes 9, 10, or 11
Power sequencer
Note – For the latest configuration information about mixing different systems or
peripherals in standard EIA 310-compliant racks, and for information about Sun’s
rackmounting cabinets, consult the Rackmount Placement Matrix located at the URL
http://docs.sun.com. At the site, click on Storage and Peripherals, find
Rackmount Placement Matrix among the AnswerBook2 collection titles, and click on
the link to display the book.
Caution – A ground screw hole is located in the lower right corner of the chassis
back panel. For more information about rackmounting peripherals and grounding
them, see the documentation accompanying the peripheral.
Caution – The chassis is heavy. Two persons are required to place the system into
the rack slide assembly in the following procedure.
Caution – Unless the rack is bolted to the floor, you must extend the cabinet’s anti-
tip legs and adjust their stabilizing feet to the floor. Level and secure the cabinet to
provide a safe working environment.
■ Identify a person to assist you, and a cart to help move the system(s).
■ Discuss each task step and verify that your helper can safely lift and carry 34 lb
(17 kg), which is approximately half the weight of a fully-equipped system.
■ Open and remove the rack enclosure front door.
Caution – Ensure that each ball-bearing slide is secured at the front of each inner
slide assembly before inserting the system into the slide assemblies. Also verify that
the inner slides are as far back as they can travel into the rack.
Dimple
Ball-bearing
runner
3. Align the crimped ends of the innermost glides on the server with the slide
bracket assemblies in the rack enclosure.
4. Holding the server level, slide it evenly into the rack enclosure until the
innermost glides stop in the slides.
The innermost glides are factory installed on the sides of the server enclosure.
Innermost glide
Tip – Slide the server in and out slowly and carefully to ensure that the slide
assemblies and the innermost glides are working correctly.
a. Make sure that the slide assemblies are level front-to-back and left-to-right.
b. Tighten the eight 10-32 screws that secure the slide assemblies to the vertical
rack rails.
Tigh
fron
Decorative panel
Retaining screws
What Next
To power on the system, see:
■ “How to Power On the System” on page 40
Caution – Unless the rack is bolted to the floor, you must extend the cabinet’s anti-
tip legs and adjust their stabilizing feet to the floor. Level and secure the cabinet to
provide a safe working environment.
Caution – The chassis is heavy. Two persons are required to remove the system
from the rack enclosure in the following steps.
Caution – Both persons must know where the server is to be placed, once it is
removed from the rack. The chassis is heavy. Two persons are required to remove the
system from the rack enclosure in the following steps.
4. Simultaneously press in on both flat spring catches to release them, and then slide
the system out of the glides.
Each person presses one spring catch and helps slide the system free of the outer
glide, supporting the weight of the system with both hands as the system slides free
of the rack.
6. Slide the empty rack slides back into their protective outer glides.
What Next
For information about placing the system into the rack glides, see:
■ “How to Install the System Into the Rack” on page 23
You may only use the RSC connections (modem or network) after installing the
operating environment software and the RSC software. You can then access RSC
software from a workstation running the Solaris, Windows 95, Windows 98, or
Windows NT operating environment and Sun’s RSC Java application, or from an
ASCII terminal or device running ASCII terminal emulation software. See “About
the Remote System Control (RSC) Card and Ports” on page 107 for more
information.
Alternatively, you can configure a local graphics console or create a tip connection
from another Sun system, see:
■ “About Communicating With the System” on page 33
What to Do
1. Connect the terminal’s data cable to the serial port A connector on the back panel.
What Next
You can now issue system commands from the terminal keyboard and view system
messages. Continue with your installation or diagnostic procedure as needed.
Alternatively, you can attach an alphanumeric (ASCII) terminal to the system’s serial
ports or create a tip connection from another Sun system, see:
■ “About Communicating With the System” on page 33
2. Attach the monitor video cable to the graphic card’s video port.
Tighten the thumbscrews to secure the connection.
What Next
You can now issue system commands from the keyboard and view system messages.
Continue with your installation or diagnostic procedure as needed.
If an ASCII terminal or local graphics console is not already connected to the system,
you need to install one before continuing the startup procedure. For information,
see:
■ “How to Attach an Alphanumeric (ASCII) Terminal” on page 34
■ “How to Configure a Local Graphics Console” on page 36
Note – If you have just installed an internal or external storage device other than an
FC-AL drive or a USB device, or any new part that plugs in to the main logic board,
only restart the system to bring it to the operating environment level after
performing a reconfiguration boot.
The operating system cannot recognize newly added devices or parts until you have
performed a reconfiguration boot. The new boot will add any new devices to the
factory-configured device tree. For more information, see “How to Initiate a
Reconfiguration Boot” on page 136.
What to Do
Caution – Never move the system when system power is on. Movement can cause
catastrophic disk drive failure. Always power off the system before moving it. For
more information, see “How to Power Off the System” on page 61.
Caution – Before you power on the system, make sure that the top cover is properly
installed. See the Sun Fire 280R Server Service Manual for more information.
Note – The system may take anywhere from 30 seconds to several minutes before
video is displayed on the system console or the ok prompt appears on an attached
terminal. This time depends on the level of power-on self-test (POST) diagnostics
being performed.
Power-On/Off position
Power button
Locked position
6. Remove the key from the keyswitch, and keep it in a secure place.
If a local graphics console or ASCII terminal is not already connected to the system,
you need to install one before continuing the startup procedure. For information,
see:
■ “How to Attach an Alphanumeric (ASCII) Terminal” on page 34
■ “How to Configure a Local Graphics Console” on page 36
Note – If you have just installed an internal or external storage device other than an
FC-AL drive or a USB device, or any new part that plugs in to the main logic board,
only restart the system to bring it to the operating environment level after
performing a reconfiguration boot.
The operating system cannot recognize newly added devices or parts until you have
performed a reconfiguration boot. The new boot will add any new devices to the
factory-configured device tree. For more information, see “How to Initiate a
Reconfiguration Boot” on page 136.
For more complete interpretation of the diagnostic output from this procedure,
consult “About Diagnostic Tools” on page 160.
What to Do
Caution – Never move the system when system power is on. Movement can cause
catastrophic disk drive failure. Always power off the system before moving it. For
more information, see “How to Power Off the System” on page 61.
Caution – Before you power on the system, make sure that the top cover is properly
installed. See the Sun Fire 280R Server Service Manual for more information.
Power button
Diagnostics position
Note – The system may take anywhere from 30 seconds to several minutes before
video is displayed on the system monitor or the ok prompt appears on an attached
terminal. This time depends on the level of power-on self-test (POST) diagnostics
being performed.
Locked position
6. Remove the key from the keyswitch, and keep it in a secure place.
Note – If you have just installed an internal or external storage device other than an
FC-AL drive or a USB device, or any new part that plugs in to the main logic board,
only restart the system to bring it to the operating environment level after
performing a reconfiguration boot.
The operating system cannot recognize newly added devices or parts until you have
performed a reconfiguration boot. The new boot will add any new devices to the
factory-configured device tree. For more information see “How to Initiate a
Reconfiguration Boot” on page 136.
The method that you will use to boot your system depends on how you will
configure the system.
Tip – For a quick summary of your installation options, consult the Start Here:
Installation Instructions for Solaris 8 that accompanies your software.
The Solaris Interactive Installation Program will prompt you interactively for answers,
and at the end of the process you will be prompted to insert the second Solaris
release CD, and then CDs from the Solaris media kit.
If you want to boot across a network interface, then you must also perform the
following tasks:
■ Configure the Ethernet port; see “How to Configure the Standard Ethernet
Interface” on page 51
■ Attach the Ethernet port to a network; see “How to Connect a Twisted-Pair
Ethernet (TPE) Cable” on page 57
The device that is used to boot the system is determined by the setting of an
OpenBoot firmware configuration parameter called boot-device. The default
order of settings of this parameter is disk net. Because of this setting, the firmware
first attempts to boot from the system hard drive, and if that fails, then from the
main logic board Ethernet interface.
The following procedure assumes that you are familiar with the OpenBoot firmware
and that you know how to enter the OpenBoot environment. For more information
about the OpenBoot firmware, see the OpenBoot 4.x Command Reference Manual in the
Solaris System Administrator AnswerBook collection for your specific Solaris release.
Note – After you have installed the Remote System Control (RSC) software, you can
also access the ok prompt using RSC from a remote server.
Note – You can also specify the name of the program to be booted as well as the
way the boot program operates. For more information, see the OpenBoot 3.x
Command Reference Manual in the Solaris System Administrator AnswerBook collection
for your specific Solaris release.
If you want to select a network interface other than the system board Ethernet
interface as the default boot device, you can determine the full path name of each
interface, by typing:
ok show-devs
The show-devs command lists all the installed system devices, including any PCI
network interface(s). The output displays the full path name of each PCI device. An
example of a PCI path name is shown below:
/pci@8,700000/ebus@5/serial@1,400000
ok reset-all
Note – You can also power cycle the system using the front panel keyswitch and
Power button. See “How to Power On the System” on page 40 for more information.
What Next
For more information about using the OpenBoot firmware, see the OpenBoot 3.x
Command Reference Manual in the Solaris System Administrator AnswerBook collection
for your specific Solaris release.
Note – You can configure only one Ethernet interface during installation of the
operating environment. To configure additional interfaces, see “How to Add an
Ethernet Interface” on page 54.
What to Do
1. Assign a host name to the system.
The host name must be unique within the network. It can be made up of characters
and numbers. Do not use a dot in the host name. Do not begin the name with a
number or a special character.
Note – This system conforms to the Ethernet 100BASE-T IEEE 802.3u Ethernet
Standard, which states that the Ethernet 10BASE-T link integrity test function should
always be enabled on both the host system and the Ethernet hub. If you have
problems verifying connection between this system and your hub, verify that the
Ethernet hub also has the link test function enabled. See “Network Communications
Failure” on page 187 and refer to the manual provided with your hub for more
information about the link integrity test function.
What Next
After completing this procedure, the Ethernet hardware interface is ready for
operation. However, in order for other network devices to communicate with the
system, your network administrator must enter the system’s IP address and host
name into the namespace on the network name server. For information about setting
up a network name service, consult the Solaris System Administrator AnswerBook for
your specific Solaris release.
The eri Fast Ethernet device driver for the system’s standard Ethernet interface is
automatically installed with the Solaris release. For information about operating
characteristics and configuration parameters for the eri driver, see Platform Notes:
The eri Fast Ethernet Device Driver. This document is available on the Solaris on Sun
Hardware AnswerBook, which is provided on the Solaris Supplement CD for the
Solaris release you are running.
Note – You can configure only one Ethernet interface during installation of the
operating system. You cannot configure the RSC Ethernet port until the RSC
software has been installed. To configure additional interfaces, see “How to Add an
Ethernet Interface” on page 54.
What to Do
You cannot use the RSC TPE port until you or your system administrator has
installed the RSC software and configured the TPE port.
● Consult the Sun Remote System Control (RSC) User’s Guide for instructions about
how to configure and use the RSC TPE Ethernet port.
■ Install any additional PCI Ethernet interface cards that you wish to configure; see
the Sun Fire 280R Server Service Manual for installation instructions
■ Attach a cable to the new Ethernet port and to the network; see “How to Connect
a Twisted-Pair Ethernet (TPE) Cable” on page 57
What to Do
1. Assign a network host name to the interface.
The host name must be unique within the network. It can be made up of characters
and numbers. Do not use a dot in the host name. Do not begin the name with a
number or a special character.
Usually an interface host name is based on the machine host name. For example, if
the machine is assigned the host name zardoz, then the additional Ethernet
interface could be named zardoz-1. The machine’s host name is assigned when the
operating system software is installed. For more information, see the installation
instructions accompanying the Solaris software.
2. Determine the Internet Protocol (IP) address (and netmask if necessary) for the
interface.
Your network administrator must assign an IP address. Each interface on a network
must have a unique IP address and netmask (if necessary).
zardoz # su
Password:
Note – The documentation accompanying the Ethernet interface should identify its
type. For more advanced information about configuring the eri software driver,
consult Platform Notes: The eri FastEthernet Device Driver. Alternatively, you can enter
the show-devs command from the ok prompt to obtain a list of all installed devices.
The host name also has an associated IP address that you enter in the /etc/hosts
file. See Step 6.
5. Type the host name, assigned in Step 1, into the /etc/hostname file for the new
interface.
Following is an example of the /etc/hostname files required for a machine called
zardoz, which has two Ethernet interfaces—the standard on-board Ethernet
interface (eri0) and a second interface provided by a PCI Ethernet adapter card
(eri1). The host name will be zardoz to a network connected to the standard eri0
interface, and zardoz-1 to a network connected to the eri1 interface.
zardoz # reboot -- -r
This command rebuilds the device trees so that the system will recognize the newly
installed PCI Ethernet adapter card.
What Next
After completing this procedure, the Ethernet interface is ready for operation.
However, in order for other network devices to communicate with the system
through this interface, the interface information (its IP address and host name) must
be entered into the namespace on the network name server. For information about
setting up a network name service, consult the Solaris System Administrator
AnswerBook for your specific Solaris release.
If you are installing an additional Ethernet interface, you must perform the
following tasks:
■ Install the system hardware and software; complete the prerequisite network-
related preparations at the beginning of the section “How to Install the Sun Fire
280R Server” on page 15
■ Install a PCI Ethernet interface card; see the Sun Fire 280R Server Service Manual
What to Do
1. Locate the RJ-45 connector for the appropriate Ethernet interface.
Note – Select the correct TPE connector for the interface you are installing. The
system comes with one system TPE connector on the back panel, and one TPE
connector on the back panel of the RSC card. Your system may also include one or
more TPE connectors provided via PCI Ethernet interface cards.
3. Plug in the other end of the cable to the TPE outlet port in the wall or the floor.
Caution – Ensure that you plug this connector into the TPE RJ-45 port and not any
phone RJ-45 port. You can damage your TPE equipment if you use the incorrect port.
You should hear the connector tab snap into place.
See your network administrator if you need more information about how to connect
to your network, and to which port in the wall.
What Next
If you are installing your system, complete the installation procedure. Return to:
■ “How to Install the Sun Fire 280R Server” on page 15
If you are installing additional interfaces to the system, then you need to configure
those interfaces; see:
■ “How to Add an Ethernet Interface” on page 54
Note – To boot the system over an Ethernet network, it is necessary that there be a
bootable image for Sun4u architecture somewhere on the network on a boot server.
For details, see the installation instructions accompanying your Solaris software.
What to Do
● At the ok prompt, type either of the two following commands:
a. To load the operating system into the server’s volatile memory, type:
ok boot net
b. To install the operating system onto the server’s internal system disk, type:
Note – The boot net - install command assumes a network boot server is set up
with appropriate properties defined to allow auto-installation of the operating
environment on the internal system disk.
Both commands boot the system, and the system console displays the system
prompt.
What Next
If you want to use the main logic board Ethernet interface as the default boot device,
you must change the value of certain OpenBoot parameters. For more information,
see the OpenBoot Command Reference Manual in the Solaris System Administrator
AnswerBook for your specific Solaris release.
Caution – Before turning off system power, halt the operating system as described
below. Failure to halt the operating system properly can result in loss of disk drive
data and will sever network connections.
What to Do
1. Notify users that the system will be powered down.
2. Back up the system files and data, if necessary.
3. Halt the operating system using the appropriate commands.
Refer to the Solaris Handbook for Sun Peripherals that corresponds to your
operating system.
4. Wait for the system halt messages and the ok prompt.
Caution – If the system hangs, hold the Power button down for four seconds while
the keyswitch is in either the Power-On/Off or the Diagnostics position, or turn the
keyswitch to the Off position. Either of these actions will cause an immediate
hardware power off, and you will risk the loss of disk drive data and will sever
network connections. For information about these keyswitch positions, see
“Keyswitch Settings” on page 9 and “System LED Indicators” on page 10 for more
information about restoring the console.
Off position
Note – Standby current (5 V DC) is still present in the system. To remove all current
from the system, remove both AC cables from their back panel receptacles.
6. Remove the key from the keyswitch, and keep it in a secure place.
System Administration
This chapter is an overview of the Sun Fire 280R server’s enhanced reliability,
availability, and serviceability (RAS) features. It also covers administrative
information and tools associated with system management, system monitoring,
system diagnostics, device troubleshooting, storage management, and personal
computer connectivity. Also included is an overview of supported redundant arrays
of independent disks (RAID) storage options and of storage monitoring tools.
63
About System Reliability, Availability,
and Serviceability Features
Reliability, availability, and serviceability (commonly known as RAS) are three
design goals contributing to continuous operation and minimizing system
downtime. Reliability refers to a system’s ability to operate continuously without
failures and to maintain data integrity. System availability refers to the percentage of
time that a system remains accessible and usable. Serviceability relates to the time it
takes to restore a system to service following a system failure. Together, reliability,
availability, and serviceability features provide for near continuous system
operation.
To deliver high levels of reliability, availability, and serviceability, the system offers
the following features:
■ Error correction and parity checking for improved data integrity
■ Easily accessible LED status indicators
■ Hot-pluggable disk drives with status indicators and easy front access
■ External support for RAID 0, 1, 0 + 1, and 5 implementations
■ System environmental monitoring and control
■ Power supply redundancy
■ Hot-swappable power supplies
■ Automatic system recovery (ASR)
■ Improved system diagnostics software
■ Enhanced system availability software
■ Alternate pathing (alternate I/O network and disk paths)
■ Sun Cluster software support
■ Remote System Control (RSC) hardware and software
In addition to providing ECC protection for data, the system offers parity protection
on all system address buses. Parity protection is also used on the Peripheral
Component Interconnect (PCI), Extended PCI, Fibre Channel-Arbitrated Loop (FC-
AL), and Small Computer System Interconnect (SCSI)) buses, and in the UltraSPARC
CPU’s internal and external cache. In addition there is internal error detection and
reporting on all system application specific integrated circuits (ASICs).
The system status LEDs are described in the section “System LED Indicators” on
page 10.
The same hot-plug technology is also supported via PCI FC-AL, or UltraSCSI
adapter cards using external storage. With both internal and external technologies
installed, hot-plug technology significantly increases the system’s serviceability and
availability, by providing the ability to:
■ Replace disk drives without service disruption
■ Increase storage capacity dynamically to handle larger work loads and improve
system performance
For more information about hot-pluggable disk drives, see “About Internal Disk
Drives” on page 91 and “About Disk Array Configurations and Concepts” on
page 87.
Monitoring and control capabilities reside at the operating system level as well as in
the system’s on-board flash PROM firmware and in the Remote System Control
(RSC) firmware. In addition, you can monitor the system remotely using the RSC
card. This ensures that monitoring capabilities are operational both locally and
remotely (if configured), even if the system has halted or is unable to boot. For more
information about RSC software, see “Using the Sun Remote System Control (RSC)
Card” on page 74.
Temperature Controls
Temperature sensors (thermistors) are located on the system’s Remote System
Control (RSC) card and on the CPU modules, and allow monitoring of each CPU
module and the system ambient temperature.
In the case of a power supply, a warning is not generated until its shutdown
temperature is reached and the power supply (if there is redundancy) or the system
is shut down, and a system fault is displayed on the system front panel LED. An
error message is logged in the /var/adm/messages file that the supply has failed.
All error and warning messages are displayed on the system console (if one is
attached) or they are redirected to the RSC console and are logged in the
/var/adm/messages file. Front panel fault LEDs remain lit after an automatic
system shutdown to aid in problem diagnosis.
System Fans
The monitoring subsystem is also designed to detect and respond to fan failures. The
system includes one fan tray assembly comprising three fans that normally run at
full speed. A single or multiple fan failure in the fan tray assembly causes the
monitoring subsystem to generate an error message, and lights the amber system
LED.
Power Supplies
The power panel is monitored in a similar fashion. The monitoring subsystem
periodically polls a power supply status register to verify power supply status. If the
panel detects a problem with a power supply, an error message is displayed on the
console (if one is attached) and the message is logged in the /var/adm/messages
file. The LEDs located on the power supply itself will indicate a failure or out-of-
spec voltage condition, and if two power supplies are installed, will indicate which
supply is the source of the fault.
Automatic self-test features enable the system to detect failed hardware components.
During the power-on self-test (POST) sequence, if a faulty hardware component is
detected, the boot sequence halts at the ok prompt. A full suite of diagnostic
software is provided to diagnose such failures (see the following section for a
summary of these software tools, and Chapter 6 for information about using these
diagnostic tools).
Control over the system’s ASR firmware functionality is provided by the OpenBoot
PROM commands. These are described in the current version of the document
OpenBoot Command Reference Manual.
POST and OpenBoot Diagnostics are firmware-resident diagnostics that can run even
if the server is unable to boot the operating system. Application-level diagnostics,
such as SunVTS and Sun Management Center, offer additional troubleshooting
capabilities once the operating environment is running. The RSC software offers
monitoring and remote notification while the operating environment software is
running, and in addition provides access to the ok firmware prompt if the operating
environment is not running.
POST diagnostics provide a quick but thorough check of the most basic hardware
functions of the system. For more information about POST, see “How to Isolate
Failures Using Power-On Self-Test (POST)” on page 179, “About Isolating Failed
Components” on page 165, and “Isolating Failed Components” on page 72.
At the operating environment level, you have access to SunVTS diagnostics. Like
OpenBoot Diagnostics, SunVTS provides a comprehensive test of the system,
including its external interfaces. SunVTS also allows you to run tests remotely over a
network connection, for example using RSC. You can only use SunVTS software if
the operating system is running. For more information about SunVTS, see “About
Exercising the System Using SunVTS Software” on page 173, and “How to Check
Whether SunVTS Software Is Installed” on page 198.
Remote System Control (RSC) hardware and software combine to extend all the
diagnostic and OpenBoot firmware control from your local server to any remote
system from which you wish to connect to the local server. In addition, you can use
monitoring software such as Sun Management Center to monitor the system
remotely. RSC software supplies the following features:
■ Remote system monitoring and error reporting, including output from POST and
OpenBoot Diagnostics
■ Remote server reboot, power-on, and power-off on demand
■ Ability to monitor the CPU temperature and fan sensors without being near the
managed server, even when the server is offline
■ Ability to run diagnostic tests from a remote console
■ Remote event notification of server problems
■ A detailed log of RSC events
■ Remote console functions on both the modem and Ethernet ports
For more information about RSC hardware, see “Using the Sun Remote System
Control (RSC) Card” on page 74.
Sun Cluster 3.0 software provides higher levels of availability than are possible with
a single server by connecting together a cluster of servers. The software enables
automatic recovery from any single hardware or software failure within the cluster
by automatically restarting a failed application or by migrating the application and
its resources to a backup server. For more information, see “About Sun Clustering
Software” on page 117.
The new tool set, described in the following sections, facilitates system management:
■ “Managing and Monitoring System Performance” on page 71
■ “Isolating Failed Components” on page 72
■ “Diagnosing Intermittent Problems” on page 72
■ “Using the Sun Remote System Control (RSC) Card” on page 74
■ “About Storage Management Tools” on page 76
■ “About Personal Computer Connectivity” on page 78
You can run POST even if the system is unable to boot. For more information about
POST, see “How to Isolate Failures Using Power-On Self-Test (POST)” on page 179.
OpenBoot Diagnostics software focuses on system I/O and peripheral devices. Like
POST, you can run these diagnostics even if the system is unable to boot. For more
information about OpenBoot Diagnostics, see “About OpenBoot Diagnostics Tests”
on page 168 and “How to Isolate Failures Using OpenBoot Diagnostics” on page 181.
Which method or tool you use to diagnose system problems depends on the nature
of those problems:
■ If your machine is not able to boot its operating environment software, you need
to run POST and OpenBoot Diagnostics tests at the firmware level.
■ If your machine is “healthy” enough to start up and load the operating
environment software, you can use the Sun Validation Test Suite (SunVTS)
software to diagnose system problems, or the Sun Management Center software
to monitor the system from the operating environment level.
Problem Analysis
no System yes
boots
?
Firmware Solaris OE
Run POST
yes Fault no
LED lit
?
Run SunVTS
no yes
POST
failure
?
Run Sun
Run OpenBoot Management
Diagnostics Center
Replace part
no yes yes no
Diagnostic Hardware
failure Disk?
?
Software or Software
disk problem problem
yes
Start Solaris
monitoring software
With the RSC card in the Sun Fire 280R server, the Sun Management Center and all
other supported Solaris 8 software can now monitor multiple Sun servers and
systems, devices, and network resources from a single system. The RSC hardware
and software extend the server’s available RAS features to the network. You can
install the RSC software from the Solaris Supplement CD.
From a remote host command-line interface (CLI), you can log in to the card (using
telnet or the modem line) and execute commands that remotely control the host
server. The next figure shows how the RSC card and its software in the local server
extend the available monitoring, control, diagnostic, and remote notification
features, making them available to a system manager working on a remote system.
In addition, RSC provides both a graphical user interface (GUI) as well as its own
CLI. The RSC GUI is available to users of:
■ Solaris 8 Operating Environment and later compatible software
■ Windows 95 operating environment
■ Windows 98 operating environment
■ Windows NT Workstation operating environment
For a more complete list of features in the RSC software, see “About the Remote
System Control (RSC) Software” on page 110. For additional information about RSC
software, see http://www.sun.com/servers/rsc.html.
For more information about the RSC hardware, see “About the Remote System
Control (RSC) Card and Ports” on page 107.
no System yes
boots
?
Run POST
yes Fault no
LED lit
?
Run SunVTS
no yes
POST
failure
?
Run Sun
Run OpenBoot Management
Diagnostics Center
Replace part
no yes yes no
Diagnostic Hardware
failure Disk?
?
Software or Software
disk problem problem
yes
Start Solaris
monitoring software
Local Server
For more information contact your Sun sales representative. More storage software
information can be found at:
■ http://www.sun.com/storage/software/mgmtconsole.html
■ http://www.sun.com/storage/software/index.html
For more information about Solaris PC NetLink, see the Solaris PC NetLink
Administration Guide and the Solaris PC NetLink Installation Guide.
This chapter describes the hardware and software configuration of the Sun Fire 280R
system. Topics covered in this chapter include:
■ “About System Memory” on page 80
■ “About Central Processing Unit (CPU) Modules” on page 83
■ “About Peripheral Component Interconnect (PCI) Buses” on page 84
■ “About Network Interface Options” on page 86
■ “About Disk Array Configurations and Concepts” on page 87
■ “About Internal Disk Drives” on page 91
■ “About Power Supplies” on page 95
■ “About the Serial Ports” on page 97
■ “About the Small Computer System Interface (SCSI) Port” on page 98
■ “About the Parallel Port” on page 101
■ “About the Universal Serial Bus (USB) Ports” on page 102
■ “About the Standard Ethernet Port” on page 103
■ “About the Fibre Channel-Arbitrated Loop (FC-AL) and Port” on page 104
■ “About the Remote System Control (RSC) Card and Ports” on page 107
■ “About the Main Logic Board Jumpers” on page 112
■ “About Changing Serial Port Settings” on page 113
■ “About Flash Permanent Read Only Memory (PROM) Jumpers” on page 114
■ “About the Remote System Control (RSC) Card and Ports” on page 107
■ “About the Remote System Control (RSC) Software” on page 110
■ “About Multipathing Software” on page 115
■ “About Sun Clustering Software” on page 117
79
About System Memory
The system’s main logic board provides eight slots for high-capacity dual in-line
memory modules (DIMMs), divided into two groups of four DIMMs each that may
be subdivided again into four logical banks. For the DIMM bank organization and
numbering scheme, see the table on next page, or see “DIMM Failure” on page 196.
Memory modules are delicate. Ensure that you take appropriate precautions to
avoid damaging them through electrostatic discharge. The memory modules must
be replaced or installed by a qualified service provider. For information about
removing and installing DIMMs, see the Sun Fire 280R Server Service Manual.
Configuration Rules
The following memory configuration rules apply to your system:
■ At least one memory group consisting of 4 slots (slots J0101, J0203, J0305, and
J0407; or slots J0100, J0202, J0304, and J0406) must be filled for the system to boot.
■ All DIMMs in a group must be of the same type.
Note – DIMM capacities can differ from one group to the next—for example, four
128-Mbyte DIMMs installed in group 0 and four 256-Mbyte DIMMs installed
in group 1 is permissible, but performance may be impacted.
Caution – DIMMs are made of electronic components that are extremely sensitive
to static electricity. Static from your clothes or work environment can destroy the
modules. Do not remove any DIMM from its antistatic packaging until you are ready
to install it on the system board. Handle the modules only by their edges. Do not
touch the components or any metal parts. Always wear a grounding strap when you
handle the modules.
Main memory on the Sun Fire 280R server supports interleaving across all eight slots
on 64-byte boundaries, and the memory system can support from one to four logical
banks. The processing stride at 64 bytes produces no interleaving, at 128 bytes it
produces two-way interleaving, and at 256 bytes it produces four-way interleaving.
The Sun Fire 280R system is limited to four-way interleaving. The group addresses
are listed in the following table.
1 J0407 1
0 J0406 0
1 J0305 1
0 J0304 0
1 J0203 3
0 J0202 2
1 J0101 3
0 J0100 2
1 Logical banks are created on the DIMM.
For interleaving purposes, all banks are treated identically regardless of their
physical location. Two successive accesses to distinct logical banks located in the
same group of DIMMs are processed the same as accesses to logical banks that are in
separate groups of DIMMs.
The next figure illustrates the possible system interleaving configurations. In only
one configuration is it possible to interleave by four. Both groups must be populated
with DIMMs of the same size supporting four banks.
Group 0 Group 1
Group 0 Group 1
Group 0 Group 1
Group 0 Group 1
Group 0 Group 1
Group 0 Group 1
The system’s main logic board provides slots for two UltraSPARC III CPU modules.
Each processor module includes one CPU chip with integrated cache memory for
data and instructions, as well as up to 8 Mbytes of external static random access
memory (SRAM) cache memory.
The CPU modules communicate with the system’s main memory and I/O
subsystem via the system’s high-speed data bus. The system CPU modules are
automatically synchronized with the system bus that runs at clock speeds up to 150
MHz providing maximum data throughput of 1.2 Gbytes per second.
A qualified service provider must remove and replace CPU modules in your system.
For information about installing and removing CPU modules, see the Sun Fire 280R
Server Service Manual.
Configuration Rules
The following rules apply for your system:
■ You can install one or two UltraSPARC III CPU modules into the server.
■ Insert the first CPU module into CPU slot 0 (J0501 and J0601).
■ Install two CPU modules into CPU slot 0 (J0501 and J0601) and into
CPU slot 1 (J0701 and J0801).
■ If you install more than one CPU module, the modules must operate at identical
clock speeds and they must have the same size cache memory. This generally
means the CPU modules must have the same part number.
For information about the CPU slot locations on the main logic board, see the Sun
Fire 280R Server Service Manual.
PCI cards are available in a variety of configurations. Not all cards will fit or operate
in all PCI slots, so it is important to know the specifications of your PCI cards and
the types of cards supported by each PCI slot in the system.
Some PCI cards are as short as 6.875 inches (17.46 cm) in length (called “short”
cards), while the maximum length of PCI cards is 12.28 inches (31.19 cm, called
“long” cards). Each slot in the system can accommodate either a long or a short card.
Older PCI cards communicate over 32-bit PCI buses, while many newer cards
communicate over wider 64-bit buses. All four of the PCI slots accept either 32-bit or
64-bit wide cards.
Older PCI cards operate at 5 VDC, while newer cards are designed to operate on
3.3 VDC. Cards that require 5 volts will not operate in 3.3-volt slots, and 3.3-volt
cards will not operate in 5-volt slots. “Universal” PCI cards are designed to operate
on either 3.3 volts or 5 volts, so these cards can be inserted into either type of slot.
The system provides three slots for 5-volt cards and one slot for a 3.3-volt card.
All four PCI slots accept universal cards.
Most PCI cards operate at clock speeds of 33 MHz, while some newer cards operate
at 66 MHz. All four PCI slots can accept 33-MHz cards. 66-MHz cards are restricted
to the slot labeled PCI 1.
Clock
Back Panel Board PCI Slot Width (bits)/ Rates DC Voltage/
Slot Label Address Bus Card Type (bits) (MHz) Card Type
For the board addresses of the PCI slots on the main logic board, see the Sun Fire
280R Server Service Manual.
Configuration Rules
The following rules apply for your system:
■ All slots support PCI universal cards.
■ All slots support PCI long or short cards.
■ Each slot can supply up to 15 watts of power.
■ The total power used for all four slots must not exceed 60 watts.
You can install PCI cards into any compatible PCI slots. Slots need not be filled in
any particular order. In most cases, the system’s I/O performance will be unaffected
by placement of PCI cards in the slots. Heavily loaded systems, however, will
deliver better overall performance by installing high-throughput interface cards on
separate buses. Examples of high-throughput interfaces are dual-channel UltraSCSI
host adapters and ATM-622 interfaces.
You can also improve overall system availability by installing redundant storage or
network interfaces on separate PCI buses.
To operate standard Ethernet network protocols, the system’s main logic board
provides an auto-sensing, switchable 10BASE-T/100BASE-TX Ethernet interface
conforming to the IEEE 802.3u Ethernet standard. The interface configures itself
automatically for either 10-Mbps or 100-Mbps operation, depending on network
characteristics.
A back panel RJ-45 connector, for connecting a twisted-pair Ethernet (TPE) cable,
provides access to the built-in Ethernet interface.
For instructions on configuring the main logic board Ethernet interface, see “How to
Configure the Standard Ethernet Interface” on page 51. For information about
operating characteristics and configuration parameters for the eri FastEthernet
device driver, see Platform Notes: The eri FastEthernet Device Driver. This document is
available on Solaris on Sun Hardware AnswerBook, which is provided on the Solaris
Supplement CD for the Solaris release you are running.
The RSC card’s back panel connectors provide a built-in administrative network
interface via Ethernet (up to 10 Mbps) or over a modem supporting connections. The
ports provide access to the RSC card via:
■ The RJ-45 connector for a TPE cable supporting a 10BASE-T Ethernet interface
conforming to the IEEE 802.3u Ethernet standard
■ The RJ-11 phone jack connector for connecting to a standard telephone modem
cable
For instructions on configuring the RSC card Ethernet interface, see “How to
Configure the Remote System Control (RSC) Ethernet Interface” on page 53.
Additional network interfaces are available through PCI cards, which provide
connection to Ethernet, token ring, fiber distributed data interface (FDDI), and other
network types. For more information, see “About Peripheral Component
Interconnect (PCI) Buses” on page 84, “How to Add an Ethernet Interface” on
page 54, and the documentation supplied with the PCI network interface card.
The Sun Solstice DiskSuite and VERITAS software is designed for use with the Sun
Fire 280R server’s internal and external disk drives. The software supports a variety
of configurations called disk arrays, which improve storage performance, capacity,
and availability.
Note – Sun Solstice DiskSuite and other software must be ordered separately.
The VERITAS software also supports disk arrays and disk redundancy. For more
information, see “About Multipathing Software” on page 115.
This section describes some of the most popular and useful of the disk
configurations using two or more disk drives, including:
■ Disk concatenation
■ Disk mirroring (RAID 1)
■ Disk striping (RAID 0)
■ Disk striping with parity (RAID 5)
■ Hot spares
■ Hot plug
For instance, you can combine the two disks c1t2d0s2 and c1t3d0s2 into the
metadevice /dev/md/rdsk/d0.
The Sun Fire 280R server’s internal disks support RAID 1 and RAID 0. More
complicated configurations, including RAID 0+1 and RAID 5, are supported by
additional disks and external disk arrays with one or more PCI host adapter cards.
Using this method, the concatenated disks are filled with data sequentially, with the
second disk being written to when no space remains on the first, the third when no
room remains on the second, and so on.
Whenever the operating system needs to write to the mirrored metadevice, both
disks are updated. The disks are maintained at all times with exactly the same
information. When the operating system needs to read from the mirrored
metadevice, it reads from whichever disk is more readily accessible at the moment.
The scheme is sometimes called RAID 1, where RAID stands for redundant arrays of
independent disks.
RAID 1 offers the highest level of data protection, but storage costs are high, since all
data is stored twice.
System performance using RAID 0 will be better than using RAID 1 or 5, but the
possibility of data loss is greater because there is no way to retrieve or reconstruct
data stored on a failed drive.
System performance using RAID 5 will fall between that of RAID 0 and RAID 1, but
the system is fully protected from data loss.
Hot Spares
In a hot-spares arrangement, one or more disk drives are installed in the system but
are unused during normal operation. Should one of the active drives fail, disk write
operations are automatically redirected to a hot-spare disk and the failed disk drive
is retired from operation.
For more information about hot-pluggable disk drives, see “About Internal Disk
Drives” on page 91.
The drives are supported by the up to 106-Mbyte per second FC-AL interface on the
system’s main logic board. Both drives plug in to the two-disk backplane, which
mounts to the system’s chassis.
The following figure shows the system’s two internal disk drives. Disk drives are
numbered 0 and 1, with the 0 drive being the default system disk.
Internal drive 0
(default)
Internal drive 1
(option)
Internal disk
drive LEDs
The Solstice DiskSuite software supplied with the Solaris server media kit lets you
use internal disk drives in two RAID configurations: RAID 0 (striping), RAID 1
(mirroring). You can also configure data drives as hot-spares. For more information
on all supported RAID configurations, see “About Disk Array Configurations
and Concepts” on page 87.
The hot-plug feature of the system’s internal disk drives allows the removal and
installation of one of the drives (if two drives are configured) while the system is
operational. This capability significantly reduces system down-time associated with
disk drive replacement.
For information about implementing RAID configurations, see “About Disk Array
Configurations and Concepts” on page 87. For information about implementing
FC-AL configurations, see “About the Fibre Channel-Arbitrated Loop (FC-AL) and
Port” on page 104.
You can use the following table to associate internal disk slot numbers with the
logical and physical device names for each internal FC-AL disk drive.
For more information about FC-AL device names see “Internal Fibre Channel-
Arbitrated Loop (FC-AL) Physical Disk Drive Name(s) Are Variable” on page 105.
The system can accommodate one or two power supplies. Each power supply
provides up to 560 watts of DC power. All system configurations can operate with
only one power supply installed.
Power supplies are modular units, designed for fast, easy installation or removal,
even while the system is fully operational. Supplies are installed in bays at the front
of the system, as shown in the following figure.
DC status (green)
Fault (amber)
You can use a second supply to provide redundancy, allowing the system to
continue operating should one of the power supplies fail. If your server includes a
second power supply, connect the second AC power cord to the left inlet (labeled 2
Three LED indicators on the front of the power supply display AC and DC status,
and fault conditions. For additional details, see “Power Supply Failure” on page 195.
Note – Sun Fire 280R power supplies shut down automatically in response to
certain over-temperature and power fault conditions. To recover from an automatic
shutdown, you must disconnect the AC power cord, wait roughly 10 seconds, and
then reconnect the power cord.
In synchronous mode, each port operates at any rate from 50 Kbaud to 256 Kbaud
when the clock is generated internally. When the clock is generated from an external
source, synchronous communication occurs at rates up to 384 Kbaud.
In asynchronous mode, either port supports baud rates of 50, 75, 110, 200, 300, 600,
1200, 1800, 2400, 4800, 9600, 19200, 38400, 57600, 76800, 115200, 153600, 230400,
307200, and 460800 baud.
Both serial ports can be configured to provide EIA-423 or EIA-232D signal levels.
Signal levels are controlled by software. The default setting is EIA-423. For more
information about changing the serial port configuration, see “About Changing
Serial Port Settings” on page 113.
See “Reference for the Serial Port A and B Connectors” on page 204 for the connector
diagram, back panel icon, and pin assignments.
The external SCSI bus will support up to four external SCSI tape devices if the bus is
used exclusively for tape devices. When other types of SCSI devices are present on
the bus, a maximum of two SCSI tape devices are supported on the external SCSI
bus. Additional external tape devices can be supported by installing appropriate PCI
host adapter cards.
Target Devices
Up to 12 Sun-compensated devices can operate on the external SCSI bus at 20
Mbytes per second. For UltraSCSI performance of 40 Mbytes per second, no more
than seven devices may be connected. Target addresses for the external SCSI bus
(also known as SCSI IDs) are available in a range of 0 through 15. Target address 7 is
reserved for the SCSI host adapter located on the main logic board. All devices on
the bus must have unique target addresses.
The addresses for the internal Digital Video Disc-Read Only Memory (DVD)
drive (6) and tape drive (4 or 5) are determined by jumpers located on the drives. If
the DVD and tape drives have been factory-installed, they are configured with the
correct addresses for the system. Internal disk drives use 0 and 1.
You must include the Sun Fire 280R server internal bus length of .2226 feet
(.067 meter) in your bus length calculations.
For fast/wide performance on the external SCSI bus, the maximum SCSI bus length
for daisy-chained SCSI devices is 19.7 feet (6 meters), including the Sun Fire 280R
server internal bus length of .2226 feet (.067 meter).
Caution – Do not connect 68-pin devices after 50-pin devices; SCSI bus errors
will occur.
Autoterminating
System Non-Sun device Sun device
Sun device
68 - 68 68 - 68 68 - 68
Autoterminating
System Sun device 50-pin device
Sun device
T
Terminator
68 - 68 68 - 68 68 -50
Adapter cable
Multi-initiator Support
The SCSI implementation of the system includes multi-initiator support: any
external host adapter on the bus can drive Termpower. This means that if the system
should lose power, the devices on the SCSI bus (except those powered by the
system) can continue to operate.
The parallel port operates at a 2-Mbyte per second data transfer rate and supports
the enhanced parallel port (EPP) protocol modes as well as standard Centronics,
Nibble, and Byte modes.
See “Reference for the Parallel Port Connector” on page 212 for the connector
diagram, back panel icon, and pin assignments.
Connectivity is provided by the four standard four-pin USB connectors on the back
panel of the system. The Sun Type 6 USB keyboard (a Sun Type 5 keyboard with a
USB interface), and a Sun USB mouse are supported for direct system I/O and
require one 4-pin USB connector each.
The USB ports, connectors J3001 and J3002, operate at a 12-Mbps data transfer rate.
See “Reference for the Universal Serial Bus (USB) Connectors” on page 215 for the
connector diagram, back panel icon, and pin assignments.
One preconfigured RJ-45 back panel connector, for connecting a Category-5 twisted-
pair Ethernet (TPE) cable, provides access to the Ethernet interface.
For instructions on configuring the main logic board Ethernet interface, see “How to
Configure the Standard Ethernet Interface” on page 51.
For the connector diagram, back panel icon, and pin assignments, see “Reference for
the Twisted-Pair Ethernet (TPE) Connector” on page 206.
For information about operating characteristics and configuration parameters for the
eri Fast Ethernet device driver, see Platform Notes: The eri FastEthernet Device Driver.
This document is available on the Solaris on Sun Hardware AnswerBook, which is
provided on the Solaris Supplement CD for the Solaris release you are running.
FC-AL devices employ a serial interface, which transfers multiple standard protocols
such as Small Computer System Interface (SCSI) and Asynchronous Transfer Mode
(ATM). By supporting these standard protocols, FC-AL preserves your investment in
existing legacy systems, firmware, applications, and software.
The Sun Fire 280R system supports a single FC-AL loop. The internal FC-AL disk
controller application specific integrated circuit (ASIC)—the QLogic 2200A—is the
interface between the 64-bit 66-MHz PCI bus and the rest of the FC-AL loop, and
serves as the loop controller. The FC-AL disk controller ASIC also supports fabric
switches, and thus both additional public and private loops are configurable using
the external port. PCI adapter cards can also be on the same loop as the QLogic
2200A controller ASIC.
The FC-AL host controller ASIC provides a 64-bit, 66-MHz Extended PCI (EPCI )
interface and the disk drives are connected to the loop through a hub. Access to the
loop for the disk drives is through the FC-AL backplane. Access to the loop via the
external port for mass storage is through the copper High-Speed Serial Data
Connector (HSSDC) on the back panel. No Gigabit Interface Converter (GBIC)
adapter is supported.
On the FC-AL controller, internal signal detect circuitry on the hub automatically
detects any signal coming from the external connector, which then enables the
external port. Lack of an external signal causes the external connection to be
disconnected from the loop. The individual ports can also be bypassed manually via
a software probe and programming a General Programming I/O (GPIO) register in
the FC-AL controller.
The host controller implements the FC protocol through a microcoded engine. The
memory for the firmware is external and is implemented with synchronous
128-Kbyte static random access memory (SRAM). For the connector diagrams, back
panel icon, and pin assignments, see “Reference for the Fibre Channel-Arbitrated
Loop (FC-AL) Port Connector” on page 214.
Device names are currently assigned to devices depending on the order they are
probed. Commands that return device names poll installed devices in this order:
on-board SCSI devices, SCSI PCI slot cards (if present), on-board internal FC-AL
devices, and last PCI FC-AL cards (if present).
Because of this, the first controller (controller 0, or zero) is always the CD-
ROM/DVD-ROM drive. Other device names vary depending where they fall in the
order of polling and on the number and type of device installed in the system. The
following examples in the table show the resulting device names in two cases.
1st Case: 4 SCSI PCI cards are installed in the four PCI slots
Controller 0 CDROM/DVD drive /pci@8,700000/scsi@6
Controller 1 EXTERNAL SCSI PORT /pci@8,700000/scsi@6,1
Controller 2 PCI SCSI CARD /pci@8,600000/scsi@1
Controller 3 PCI SCSI CARD /pci@8,700000/scsi@1
Controller 4 PCI SCSI CARD /pci@8,700000/scsi@2
Controller 5 PCI SCSI CARD /pci@8,700000/scsi@3
Controller 6 FCAL INTERNAL DISK(s) /pci@8,600000/SUNW,qlc@4
2nd Case: 2 SCSI PCI cards and 2 FC-AL PCI cards are installed in the PCI slots
Controller 0 CDROM/DVD drive /pci@8,700000/scsi@6
Controller 1 EXTERNAL SCSI PORT /pci@8,700000/scsi@6,1
Controller 2 PCI SCSI CARD /pci@8,600000/scsi@1
Controller 3 PCI SCSI CARD /pci@8,700000/scsi@1
Controller 4 FCAL INTERNAL DISK(s) /pci@8,600000/SUNW,qlc@4
Controller 5 PCI FCAL CARD /pci@8,700000/SUNW,qlc@2
Controller 6 PCI FCAL CARD /pci@8,700000/SUNW,qlc@3
Both of the above cases assume that devices are attached to each controller.
Initial Support
Sun Fire 280R system’s FC-AL external port supports the following products:
■ Sun StorEdge Multipack-FC
■ Sun StorEdge T3 Arrays
The adapter card supports all current Sun Storage FC-AL options, including A5000
series and StorEdge Multipacks.
For more information about setting up and configuring Sun disk arrays, see the Sun
StorEdge StorTools User’s Guide and the Sun StorEdge Component Manager User’s Guide.
For more information about setting up and configuring T3 arrays, see the Sun
StorEdge T3 Administrator’s Guide.
Caution – The hardware card is installed in every system in the RSC slot. Never
move the RSC card to another system slot, as it is not a PCI-compatible card.
The card, installed in every system in the RSC slot, features on-board devices that
can monitor and trigger alerts, for example, about host system resets or power
supply failures, or other host system changes. An on-board RSC thermistor supplies
ambient temperature data about the host system to the firmware and to the installed
software.
The RSC card also supports redirection of its host’s console to the RSC connection,
and thus provides remote system administration for geographically distributed or
physically inaccessible systems. For information about redirecting the system
console, see “How to Redirect the Host Console to RSC” on page 111.
Console access also provides secure access to the host system firmware and permits
remote system diagnosis, system reconfiguration, and remote system rebooting from
the ok prompt in the host firmware.
Therefore, the RSC hardware and RSC software continue to be effective when the
server operating system goes offline. Even in the absence of the operating
environment software, RSC can send notification of hardware failures or other
events that may be occurring on your server.
All RSC connection ports can be used simultaneously. The modem supports regular
asynchronous serial protocol, and can also support the Point-to-Point Protocol (PPP).
When running PPP, a standard internet TCP/IP 10-Mbps protocol stack is available
over the modem interface.
RSC Jumpers
The following table describes the RSC flash PROM jumper addresses, functions, and
settings. Default jumper settings are marked with an asterisk.
Note – Never change RSC card address J0502 default jumper setting, as the RSC
card will not boot.
RSC Monitoring
The RSC card contributes significantly to improvements in environmental
monitoring. The Sun Fire 280R system RSC monitors the following devices or events:
■ Power supplies
■ System keyswitch
■ System fans
■ CPU module(s) temperature(s)
■ System ambient temperature
In addition the four front panel keyswitch positions are monitored; see “Status and
Control Panel Features” on page 8.
RSC software requirements are documented in the Sun Remote System Control (RSC)
User’s Guide.
RSC complements existing Sun monitoring and diagnostics tools such as Sun
Management Center, SunVTS, the kadb kernel debugger, OpenBoot PROM, and
OpenBoot Diagnostics. Sun Management Center software operation remains
unchanged, and it continues to be the main tool for observing system operation
behavior and performance while the server operating system is up and running.
Note – To use the RSC command shell, a client must be an ASCII character terminal
or have ASCII character terminal emulation software installed.
For instructions about how to configure the RSC hardware for the RSC software, and
about installing and using the RSC software, see the Sun Remote System Control (RSC)
User’s Guide.
ok diag-console rsc
These commands take effect after the next server reset. At any time, you can use the
following commands to remove RSC as the default console:
ok diag-console ttya
Jumpers are marked on the main logic board with jumper addresses. For example,
the serial port jumper is marked J2103. Jumper pins are located immediately adjacent
to the jumper address. Pin 1 is marked with an asterisk (*) in one of the positions
shown below.
J X X X X Jumper address
Pins
* *
* *
Note – The default setting at serial ports A and B is RS-423 mode. To change the
serial port to RS-232 mode proceed as follows.
To set the ports back to RS-423 mode, substitute rs423 for rs232 in the above
commands.
ok reset-all
Note – Setting only one of the ttya or ttyb rs232/rs423 mode variables causes
both ports to be set to that mode.
For pin assignments, back panel icons, and connector diagram, see “Reference for
the Serial Port A and B Connectors” on page 204.
One jumper on the main logic board controls flash PROM operation. The table below
describes its function.
Default
Shunt on Shunt on Shunt Signal
Jumper Pins 1 + 2 Selects Pins 2 + 3 Selects on Pins Controlled
Note – The jumper setting on J2104 must remain on its factory-supplied setting
(shunt on pins 1 and 2).
For information about how jumpers are marked on the main logic board with
jumper addresses, see “About the Main Logic Board Jumpers” on page 112.
For more information about flash PROM programming, see the Sun Fire 280R Server
Service Manual.
For the Sun Fire 280R system, two different types of multipathing software are
available:
■ Solaris IP Network Multipathing – Provides multipathing and load-balancing
capabilities for IP network interfaces
■ VERITAS Volume Manager – Includes a feature called Dynamic
Multipathing (DMP) for disk storage arrays
For additional information about VERITAS Volume Manager and its Dynamic
Multipathing feature, see “About Sun Clustering Software” on page 117 and refer to
the documentation provided with VERITAS Volume Manager software.
Sun Cluster 3.0 software connects a group of servers into a cluster system to avoid a
loss of service by managing failures on a larger scale than on a single server. Sun
Cluster software allows multiple Sun servers to be interconnected in a cluster
configuration. A cluster is a group of nodes that are interconnected to work as a
single, highly available and scalable system. A node is a single instance of Solaris
software – it may be a standalone server or a domain within a standalone server.
Sun Cluster software enables automatic recovery from any single hardware or
software failure within the cluster by automatically restarting a failed application, or
by migrating the application and its resources to a backup server. Sun Cluster
software provides:
■ Hardware and software failure detection
■ System administration
■ System failover and automatic restart of data services in the event of a failure
■ A set of high availability (HA) data services
■ Application programming interface (API) software to create other HA data
services by integrating them within the Sun Cluster framework
The Sun Cluster system uses Solstice DiskSuite or VERITAS Volume Manager
(VxVM) software to administer multihost disks arrays that are accessible from
multiple Sun Cluster servers. The volume management software provides disk
mirroring, concatenation, striping, and hot sparing. VxVM also provides RAID 5
capability. For more information about RAID, see “About Disk Array Configurations
and Concepts” on page 87.
For more information about Sun Cluster software, see the Sun Cluster Software
Planning and Installation Guide, the Sun Cluster Hardware Service Manual, and the Sun
Cluster System Administration Guide.
This chapter describes the internal storage devices in your system, and how to use
them when the operating environment is running. With the exception of internal
disk drives in the Sun Fire 280R server, all other component or part installation or
replacement must be performed by a qualified service provider. The chapter covers
what you need to know, and need to do, to install, remove, or replace the internal
disk drives.
119
How to Avoid Electrostatic Discharge
Use the following procedure to prevent static damage whenever you are accessing
the system internal drives.
What to Do
Caution – Printed circuit boards and hard disk drives contain electronic
components that are extremely sensitive to static electricity. Ordinary amounts of
static from your clothes or the work environment can destroy components.
Do not touch the components themselves or any metal parts without taking proper
antistatic precautions.
1. Disconnect the AC power cord from the wall power outlet only if you will be
handling the power distribution board.
The AC power cord provides a discharge path for static electricity, so you generally
want to leave it plugged in during installation and repair procedures. The only time
you should unplug the cord is when you service the power distribution board.
4. Detach both ends of the strap after you have completed the installation or service
procedure.
What to Do
1. Halt the operating system and turn off the system power.
See “How to Power Off the System” on page 61.
3. Identify the disk drive to be removed and note the bay in which it is installed.
The lower bay is the default system disk location.
5. Holding the disk drive by the handle, slide it out of the drive bay.
Note – When you reinstall the drive (or a replacement drive), be sure to install it
into the same drive bay as the one from which it was just removed.
What Next
To install a disk drive, complete this task:
■ “How to Install a Disk Drive” on page 125
You must follow antistatic precautions when handling a disk drive. Complete
this task:
■ “How to Avoid Electrostatic Discharge” on page 120
What to Do
1. Halt the operating system and turn off system power.
See “How to Power Off the System” on page 61.
Note – If you are replacing a drive that you removed previously, be sure to install
the drive in the same drive bay from which it was removed.
5. Holding the drive by its handle, fit the drive into the drive bay guide rails.
6. Slide the drive into the bay until it barely contacts the backplane.
8. Press the handle toward the drive until the latch closes, securing the drive
in place.
11. Restart the system and return the keyswitch to the Locked position.
For more information, see “How to Power On the System” on page 40.
What Next
When you restart the system, be sure to run power-on self-test (POST) and
OpenBoot Diagnostics tests to verify that the system functions correctly with the
new parts you have just installed. You do not have to perform a reconfiguration boot
with FC-AL drives. For additional information, see:
■ “How to Isolate Failures Using Power-On Self-Test (POST)” on page 179
■ “How to Isolate Failures Using OpenBoot Diagnostics” on page 181
When you remove a drive using the hot-plug operation, you need to stop the drive
and take it offline to remove the logical software links to the drive, and to re-
configure the file systems so that they now ignore the removed drive. You may also
have to reconfigure your application software to operate without the removed drive.
Use the luxadm and the devfsadm software tools to remove the Sun Fire 280R
server’s internal disk drive(s) using the hot-plug operation. The following procedure
describes the general steps involved, but your specific device names may be
different.
Caution – Do not hot-plug drives without the correct preparations. The system
supports hot-plugging disk drives, but there are software procedures that you must
perform before you remove or install any drive.
Note – If you have not configured the system with two boot disks, you cannot hot-
plug a single boot disk. You can only hot-plug the boot disk if you have configured
a two-disk mirror of the boot disk for hot-plugging. If the system is configured with
a boot disk and a data disk, you may hot-plug the data disk, not the boot disk.
■ Obtain the logical device name(s) for the device(s) you plan to remove. See “Hot-
Plug Device Information” on page 93 for more information.
■ Select the disk and stop any activity or applications accessing the drive.
You must follow antistatic precautions when handling a disk drive. Complete
this task:
■ “How to Avoid Electrostatic Discharge” on page 120
What to Do
1. Become superuser or the root user.
% su
Password: <root_password>
#
The picld daemon notifies the system that the disk has been removed, and (in this
example) that no other FC-AL devices were found.
The system responds with all the logical links present in the directory.
# devfsadm -C
Note – The default devfsadm operation is to attempt to load every driver in the
system and attach these drivers to all possible device instances. devfsadm then
creates device special files in /devices and logical links in /dev. The devfsadm
-C option cleans up the /dev directory and removes any dangling logical links to
the device link names.
# ls /dev/rdsk/c1t1d*
No match
The output confirms that the cleanup command has removed all dangling links, and
the operating environment can proceed to use the remaining devices.
What Next
If you need to install a drive using a hot-plug operation, see:
■ “How to Install a Disk Drive Using the Hot-Plug Operation” on page 132
Use the luxadm and the devfsadm software tools to hot-plug the Sun Fire 280R
server’s internal disk drive(s). The following procedure describes the general steps
involved, but your specific device names may be different.
Caution – Do not hot-plug drives without the correct preparations. The system
supports hot-plugging disk drives, but there are software procedures that you must
perform before you remove or install any drive.
Note – If you have not configured the system with two boot disks, you cannot hot-
plug a single boot disk. You can only hot-plug the boot disk if you have configured
a two-disk mirror of the boot disk for hot-plugging. If the system is configured with
a boot disk and a data disk, you may hot-plug the data disk, not the boot disk.
What to Do
1. Become superuser or the root user.
% su
Password: <root_password>
#
# ls /dev/rdsk/c1t1d*
No match
The output confirms there are no links present for the inserted drive.
# devfsadm -C
Note – The default devfsadm operation is to attempt to load every driver in the
system and attach the drivers to all possible device instances. devfsadm then
creates device special files in /devices and logical links in /dev. The -C option
also removes any dangling links.
The system responds with the logical links present in the directory.
# format
Searching for disks... done
8. Repeat Step 2 through Step 7 for every drive you are hot-plugging.
For more information, refer to the luxadm documentation in the Solaris on Sun
Hardware AnswerBook. This AnswerBook documentation is provided on the Solaris
Supplement CD for the Solaris release you are running.
If you need to remove a disk drive using the hot-plug operation, see:
■ “How to Remove a Disk Drive Using the Hot-Plug Operation” on page 128
Caution – Before you power on the system, make sure that the system cover and
doors are properly installed.
What to Do
1. Turn on power to any peripherals and external storage devices.
Read the documentation supplied with the device for specific instructions.
3. Turn the front panel keyswitch to the Power-On/Off position and press the Power
button once.
See “Status and Control Panel Features” on page 8.
To run power-on self-test (POST) and OpenBoot Diagnostics tests to verify that the
system functions correctly with the new part(s) you have just installed, see “How to
Power On the System With Full Diagnostics Enabled” on page 43, or see “About
Diagnostic Levels” on page 167.
Note – The system may take anywhere from 30 seconds to two minutes before the
system banner appears. This time depends on the level of POST diagnostics being
performed.
ok boot -r
This command rebuilds the device trees for the system, incorporating any newly
installed options. After a device has been added to a device tree, it can be recognized
by the system. After the system has successfully completed the reconfiguration boot,
the system prompt is displayed.
Caution – Never move the system when system power is on. Movement can cause
catastrophic disk drive failure. Always power off the system before moving it.
What Next
The system’s front panel LED indicators provide power-on status information.
For more information about the system LEDs, see:
■ “System LED Indicators” on page 10
What to Do
1. Push the Eject button on the drive to release the drive tray.
Note – You should warn users before abruptly halting processes. The command
fuser -u /cdrom/cdrom0 helps you identify who’s accessing the DVD drive.
Refer to the Solaris System Administrator’s Guide for more information about the
fuser command.
If the server is set up without a local console, you need to set up a console on it in
order to issue software commands; see:
■ “About Communicating With the System” on page 33
What to Do
1. Kill processes accessing the DVD drive, if necessary.
The disc will not eject while the drive is in use. To kill any processes accessing the
DVD drive, become superuser and type the following:
% su
Password:
# fuser -k /cdrom/cdrom0
% eject cdrom0
The drive ejects the DVD drive tray and you can remove the disc.
What Next
You can also eject a DVD or CD from the drive using one of these methods:
■ Manually; see “How to Eject a Digital Video Disc (DVD) Manually” on page 143
■ Using an emergency procedure; see “How to Eject a Digital Video Disc (DVD) in
an Emergency” on page 145
Note – Warn users before abruptly halting processes. The command fuser -u
/cdrom/cdrom0 helps you identify who’s accessing the ROM drive. Refer to the
Solaris System Administrator’s Guide for more information about the fuser command.
What to Do
1. Kill processes accessing the DVD drive, if necessary.
The front panel Eject button will not eject a disc while the disc is in use. To kill any
processes accessing the DVD or CD, become superuser and type the following:
% su
Password:
# fuser -k /cdrom/cdrom0
What Next
You can also eject a DVD or CD by using one of these methods:
■ With software commands; see “How to Eject a Digital Video Disc (DVD) With
Software Commands” on page 141
■ Using an emergency procedure; see “How to Eject a Digital Video Disc (DVD) in
an Emergency” on page 145
What to Do
Caution – If this procedure is used while a disc is mounted, you can degrade or
destroy data in your system.
What Next
You can also eject a DVD or CD by using one of these methods:
■ With software commands; see “How to Eject a Digital Video Disc (DVD) With
Software Commands” on page 141
■ Manually; see “How to Eject a Digital Video Disc (DVD) Manually” on page 143
Note – If the drive cannot read a disc, you may have a dusty or dirty disc.
What to Do
1. Clean the disc with compressed air.
Compressed air can remove most accumulations of dust and large dirt particles. If
you have access to the drive’s read-head, verify it is dust free also.
2. If spraying with compressed air fails to remove the dirt on a disc, wipe the disc
using a soft, clean, lint-free, dry cloth.
■ Wipe the data areas of the disc (on both sides if necessary) radially from the center
to the outside.
■ Do not wipe in a circular motion.
■ Wipe only the affected areas of the disc.
Incorrect Incorrect
What Next
To insert the disc into the drive, see:
■ “How to Insert a Digital Video Disc (DVD) Into the Drive” on page 138.
Thermal Conditioning
To ensure proper thermal conditioning, keep the tape cartridge at the same
temperature as the drive for 24 hours. This applies to cartridges for any of the tape
drives offered for your system.
What to Do
1. Verify that the tape cartridge write-protect switch is set correctly.
If the lock window is open, the tape is write-protected.
Write-protect switch
What Next
To remove a tape cartridge from the drive, see:
■ “How to Remove a Tape Cartridge” on page 152
Note – The information in this section applies to a DDS-4 tape drive. If you have a
different type of tape drive installed, see the specifications shipped with the drive
for information.
What to Do
1. Check that there is no drive activity.
The green activity LED should be unlit. A flashing LED indicates drive activity.
Caution – Do not eject the tape cartridge when the drive is active, or you may incur
data loss or equipment damage.
What to Do
For information about software commands needed to read and write data with your
tape drive, refer to the Solaris Handbook for Sun Peripherals or the Solaris User’s Guide.
1. Clean the drive after the first four hours of use with a new tape.
2. After that, clean the tape drive after every 25 hours of use to maintain reliable
operation.
3. Clean the drive twice as often if you use it in a dusty environment or operate
it infrequently.
Do not use any cartridge other than a DDS-approved cleaning tape cartridge to clean
your tape drive.
The Sun Fire 280R server and its accompanying software contain many tools and
features that help you:
■ Monitor the status of a functioning system
■ Isolate problems when there is a failure of a field-replaceable component
■ Exercise the system to disclose an intermittent or incipient problem
157
For background information about diagnostics and monitoring tools and features,
read the following section, “About Diagnostic Tools” on page 160, or turn to a
specific topic.
■ “About Monitoring the System” on page 162
■ “About Monitoring the System Using Sun Remote System Control (RSC)” on
page 162
■ “About Monitoring the System Using Sun Management Center Software” on
page 165
■ “About Isolating Failed Components” on page 165
■ “About Isolating Failures Using Sun Remote System Control (RSC)” on
page 165
■ “About Isolating Failures Using Power-On Self-Test (POST)” on page 166
■ “About Isolating Failures Using OpenBoot Diagnostics” on page 166
■ “About OpenBoot Diagnostics Tests” on page 168
■ “About Exercising the System” on page 173
■ “About Exercising the System Using SunVTS Software” on page 173
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 (ASCII) Terminal” on page 34.
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 36 for detailed instructions.
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 178.
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.
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.
OpenBoot Diagnostics tests focus on system I/O and peripheral devices. Like POST,
you can run OpenBoot Diagnostics even if the system is unable to boot. For more
information about OpenBoot Diagnostics, see “About Isolating Failures Using
OpenBoot Diagnostics” on page 166 and “How to Isolate Failures Using OpenBoot
Diagnostics” on page 181.
Which method or tool you use to diagnose system problems depends on the nature
of those problems. If your machine cannot load the operating environment software,
use POST and OpenBoot Diagnostics to isolate failed components. If your machine
starts up and loads the operating environment software, use SunVTS software and
Sun Management Center software to monitor or exercise the system.
The following chart provides an overview of which tools to use to diagnose hardware
problems locally.
no System yes
boots
?
Firmware OS Software
Run POST
yes Fault no
LED lit
?
Run SunVTS
no yes
POST
failure
?
Run Sun
Run OpenBoot Management
Diagnostics Center
Replace part
no yes yes no
Diagnostic Disk
failure failure?
?
Software or Software
disk problem problem
These monitoring tools let you specify system criteria that bear watching. For
instance, you might want to set a threshold for system temperature and be notified if
that threshold is exceeded. Warnings can be reported by visual indicators in the
software’s interface. Additionally, you could set RSC to send an email or pager alert
whenever a problem occurs.
You can access RSC either from a workstation running the Solaris, Windows 95,
Windows 98, or Windows NT operating environment and Sun’s RSC Java
application, or from an ASCII terminal or device running ASCII terminal emulation
software.
The RSC card runs independently, and uses standby power from the server.
Therefore, RSC firmware and software continue to be effective when the server
operating system goes offline, and can send notification of hardware failures or other
RSC lets you monitor the following on your Sun Fire 280R server.
Disk drives Whether each slot has a drive present, and whether it reports
OK status
Fan tray Whether the fan tray reports OK status
CPU modules Whether each bay has a CPU module present, and its
temperature including temperature warning and failure status
Power supplies Whether each bay has a power supply present, and whether it
reports OK status
System temperature System ambient temperature as measured at the RSC card,
including temperature warning and failure status
See the Sun Remote System Control (RSC) User’s Guide for complete information about
RSC.
Before you can start using RSC, you must install and configure its software on the
server and client systems. Instructions for doing this are given in the Sun Remote
System Control (RSC) User’s Guide. You also have to make any needed physical
The following chart provides an overview of connections enabled after RSC has been
installed and configured.
no System yes
boots
?
Run POST
yes Fault no
LED lit
?
Run SunVTS
no yes
POST
failure
?
Run Sun
Run OpenBoot Management
Diagnostics Center
Replace part
no yes yes no
Diagnostic Disk
failure failure?
?
Local Server
Software or Software
disk problem problem
Sun Management Center lets you monitor boards, tapes, power supplies, and disks
as well as operating system parameters like load, resource usage, and disk space.
You can create alarm thresholds and be notified when these are exceeded.
The system must be up and running if you want to use Sun Management Center,
since this tool runs on top of the Solaris Operating Environment. For instructions,
see “How to Monitor the System Using Sun Management Center Software” on
page 177. For detailed information about the product, see the Sun Management Center
Software User’s Guide.
RSC also gives you access to output from power-on self-test (POST) and OpenBoot
Diagnostics. RSC displays an alert to users logged in to an RSC account on the
server, and can also send alert messages by email or pager.
{0} 0 Return
{0} 1 Run all Tests in this Menu
{0} 2 Change Test Control Flags
{0} 3 * Reset Menu
{0} 4 * CPU Tests
{0} 5 * Ecache Tests
{0} 6 * Memory Tests
{0} 7 * Schizo Tests
{0} 8 * RIO Tests
{0} 9 * Estar Test (UP only)
{0} a * ECC Tests
{0} b * MP Tests
{0} c * BIST
{0} d * System Frequency and CPU Ratio
{0} e * I2C/Fan/Temperature/Smart card
{0} f * Run POST
{0} 10 * Return to OBP
{0}Selection:
For instructions on how to set the level of diagnostic testing, see “How to Set the
Diagnostics Level” on page 186. Note that if the diag-level setting is menus,
OpenBoot Diagnostics uses the setting min or max, depending on the test performed.
You can also use RSC to temporarily set the boot mode for a reboot that occurs
within 10 minutes. Using RSC to set the boot mode is similar to using L1-N key
combinations on non-USB Sun keyboards (the Sun Fire 280R server uses a USB
keyboard). See the Sun Remote System Control (RSC) User’s Guide for information
about the bootmode and rscadm bootmode commands.
When you use the obdiag command at the ok prompt, OpenBoot Diagnostics
displays a menu of available tests. The menu is dynamic, and test numbers are not
fixed. Following is an example of the menu.
______________________________________________________________________________
| o b d i a g |
|_________________________ _________________________ ________________________|
| | | |
| 1 SUNW,qlc@4 | 2 bbc@1,0 | 3 ebus@5 |
| 4 flashprom@0,0 | 5 gpio@1,300600 | 6 i2c@1,2e |
| 7 i2c@1,30 | 8 network@5,1 | 9 parallel@1,300278 |
| 10 pmc@1,300700 | 11 rsc-control@1,3062f8 | 12 rtc@1,300070 |
| 13 scsi@6 | 14 scsi@6,1 | 15 serial@1,400000 |
| 16 usb@5,3 | | |
|_________________________|_________________________|________________________|
| Commands: test test-all except help what printenvs setenv versions exit |
|____________________________________________________________________________|
You can also run OpenBoot Diagnostics commands from the ok prompt for any
device by invoking its self-test method. If a device has no self-test method, the
message No selftest method for device name is displayed. To run the
self-test method for a device, type the OpenBoot PROM test command at the ok
prompt, followed by the device alias or device path name. For example:
ok test net
Testing network
ok
Test Function
bbc Tests the registers in the boot bus controller, and then verifies that at
least one processor has boot bus access.
ebus Accesses the Ebus through the RIO port and then tests DMA
controller functionality.
flashprom Performs a checksum and read/write test on the flash PROM
containing the main logic board boot code.
gpio Tests the registers of the general purpose input/output subsystem.
i2c@1,2e Tests SEEPROM devices.
i2c@1,30 Tests SEEPROM devices and I2C port expanders. Also performs
various read and write tests on the I2C temperature controller devices.
network Tests the registers of the RIO Ethernet controller.
parallel Tests the parallel port using both supported parallel port modes:
ECPP and extended parallel mode.
pmc Tests the registers of the power management controller.
rsc-control Calls RSC POST and verifies loopback functionality through the RSC
console.
rtc Tests the registers of the realtime clock, then ensures that interrupts
are firing correctly.
SUNW,qlc Tests the registers of the Fibre Channel-Arbitrated Loop (FC-AL)
subsystem.
scsi Tests the SCSI disk controller registers and verifies DMA functionality.
serial Tests the ttya and ttyb serial lines, and then performs an internal
loopback test on each.
usb Tests the registers on each RIO Universal Serial Bus.
Note – Use of the OpenBoot PROM configuration variable test-args can affect
the behavior of OpenBoot Diagnostics. The test-args variable is empty by default.
Use the help command for more information on test-args.
The following example shows typical output from the OpenBoot Diagnostics
test-all command.
obdiag> test-all
Hit the spacebar to interrupt testing
Testing /pci@8,700000/ebus@5/bbc@1,0 .................. passed
Testing /pci@8,700000/ebus@5 .......................... passed
Testing /pci@8,700000/ebus@5/flashprom@0,0 ............ passed
Testing /pci@8,700000/ebus@5/gpio@1,300600 ............ passed
Testing /pci@8,700000/ebus@5/i2c@1,2e ................. passed
Testing /pci@8,700000/ebus@5/i2c@1,30 ................. passed
Testing /pci@8,700000/network@5,1 ..................... passed
Testing /pci@8,700000/ebus@5/parallel@1,300278 ........ passed
Testing /pci@8,700000/ebus@5/pmc@1,300700 ..............passed
Testing /pci@8,700000/ebus@5/rtc@1,300070 ..............passed
Testing /pci@8,600000/qlc@4 ........................... passed
Testing /pci@8,700000/scsi@6 .......................... passed
Testing /pci@8,700000/scsi@6,1 ........................ passed
Testing /pci@8,700000/ebus@5/serial@1,400000 .......... passed
Testing /pci@8,700000/usb@5,3 ......................... passed
Hit any key to return to the main menu
obdiag> test 4
Hit the spacebar to interrupt testing
Testing /pci@8,700000/ebus@5/flashprom@0,0
{0} ok watch-clock
Watching the ‘seconds’ register of the real time clock chip.
It should be ‘ticking’ once a second.
Type any key to stop.
4
{0} ok watch-net
gme register test --- succeeded.
Internal loopback test -- succeeded.
Transceiver check -- Using Onboard Transceiver - Link Up. up
{0} ok watch-net-all
/pci@8,700000/network@5,1
gme register test --- succeeded.
Internal loopback test -- succeeded.
Link is -- Using Onboard Transceiver - Link Up Up.
Sun provides a standard tool for exercising its desktop and server systems: the Sun
Validation Test Suite (SunVTS).
The system must be up and running if you want to use SunVTS, since this tool runs
on top of the Solaris Operating Environment.
For instructions on running SunVTS software to exercise your Sun Fire 280R server,
see “How to Exercise the System Using SunVTS Software” on page 199. For more
information about the product, see:
■ SunVTS User’s Guide (806-6515-10) — Describes SunVTS features as well as how
to start and control the various user interfaces.
■ SunVTS Test Reference Manual (806-6516-10) — Describes each SunVTS test,
option, and command-line argument.
■ SunVTS Quick Reference Card (806-6519-10) — Gives an overview of the main
features of the graphical user interface (GUI).
These documents are available on the Solaris Supplement CD-ROM and on the Web
at http://docs.sun.com
This manual describes the hardware aspects of setting up and using these
monitoring tools. For more information, see “Managing and Monitoring System
Performance” on page 71. For complete documentation of RSC and Sun
Management Center software, refer to the User’s Guides for these products.
% /opt/rsc/bin/rsc
If you are using a client running the Windows 95, Windows 98, or Windows NT
operating environment, follow these steps to start the RSC GUI:
If you have created a shortcut to Remote System Control, you can also double-click
on the Remote System Control icon on your desktop.
When the login screen appears, it prompts you to enter an RSC device name or
Internet address, your RSC username, and your password.
Note – It is important that you enter the name or Internet address of the RSC
device, not the name or Internet address of the server.
To monitor or control more than one server, start a separate GUI session for each.
Sun Management Center software is supported on the Sun Fire 280R server. To
download the current Sun Management Center software packages, and to obtain
information about the software documentation, go to the Web site
www.sun.com/software/sunmanagementcenter.
● For instructions about installing and using Sun Management Center software, see
the Sun Management Center Software User’s Guide.
What to Do
To reset the NVRAM parameters to a known recovery mode, perform the following
steps:
2. Watch the wrench LED for rapid flashing during the boot process.
The amber wrench LED flashes for approximately three seconds.
3. While the wrench LED is flashing, press the Power button twice in quick
succession.
The following output appears after the system boots to the ok prompt.
Note – The Stop-D (Stop-Shift-d) and the Stop-F (Stop-Shift-f) keyboard sequences
are not supported on systems with USB keyboards.
For information about the various keyswitch positions, see “Status and Control
Panel Features” on page 8.
You must also verify baud rates between a system and a monitor or a system and a
terminal when using a tip connection. See:
■ “How to Verify the Baud Rate” on page 185
After RSC software is installed, you can redirect the system console output from the
server serial port A to RSC and view the POST and diagnostic error messages using
an RSC account. After this redirection, the local system console is not available. For
more information about redirecting a console after the RSC software is installed, see:
■ “How to Redirect the Host Console to RSC” on page 111
You can choose to run an abbreviated POST with concise error and status reporting
or run an extensive POST with more detailed messages. For more information, see:
■ “How to Set the Diagnostics Level” on page 186
What to Do
Ensure that the front panel keyswitch is in the Power-On/Off position. For
descriptions of the keyswitch settings, see “Keyswitch Settings” on page 9.
You can initialize POST one of two ways:
■ By setting the diag-switch? to true and the diag-level to max, min, or
menus, followed by power cycling the system unit
■ You turn the keyswitch to the Diagnostics setting and press the Power button.
To set the diag-switch? to true and power cycle the system unit:
1. When the ok prompt is displayed, type the following command:
2. After a few seconds, press the Power button on the system once.
The keyswitch must be set to the Power-On/Off position.
While POST is running, you can observe its progress and any error indications in the
system console. You can view these results on an ASCII terminal, on a graphics
console, or through a tip connection. In addition, if the RSC has been installed, you
can view them on a remote system over either a telnet or modem connection.
POST status and error conditions are indicated by the general fault LED on the
system front panel. The LED blinks slowly to indicate that POST is running. It
remains lit if POST detects a fault.
If POST detects an error condition that prevents the system from booting, it will halt
operation and display the ok prompt. The last message displayed by POST prior to
the ok prompt indicates which part you need to replace.
What to Do
1. Press the Break key on your alphanumeric terminal’s keyboard, or enter the
Stop-a sequence on a Sun keyboard.
The ok prompt is displayed.
ok reset-all
ok obdiag
The OpenBoot Diagnostics menu appears. This menu displays a numbered list of all
available tests.
Note – Use of the OpenBoot PROM configuration variable test-args can affect
the behavior of OpenBoot Diagnostics. The test-args variable is empty by default.
Use the help command for more information on test-args.
If any problems are found by the test, OpenBoot Diagnostics displays an error report
on the console. The first line of the error report describes the possible problem. The
optional summary line displays the associated memory address and values.
What Next
Replace any field-replacable unit (FRU) that the OpenBoot Diagnostics test
determines is defective.
1. Connect the Sun server ttyb serial port to your UltraSPARC system ttya serial
port using a serial connection cable. Use a 3-wire Null Modem Cable, and connect
wires 3-2, 2-3, and 7-7.
Refer to your system installation manual for specifications on null modem cables.
2. At the Sun server, add the following lines to the /etc/remote file.
If you are running a version of the Solaris Operating Environment previous to 2.0,
type:
hardwire:\
:dv=/dev/ttyb:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:
If you are running version 2.0 or later of the Solaris Operating Environment, type:
hardwire:\
:dv=/dev/term/b:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:
The Shell Tool window is now a tip window directed to the Sun server ttyb port.
Note – Use a Shell Tool, not a Command Tool; some tip commands may not work
properly in a Command Tool window.
4. At your UltraSPARC system, enter the Forth Monitor so that the ok prompt is
displayed.
Note – If you do not have a video monitor attached to your UltraSPARC system,
connect the UltraSPARC system ttya serial port to the Sun server ttyb serial port
and turn on the power to your UltraSPARC system. Wait for a few seconds, and
press Stop-a to interrupt the power-on sequence and start the Forth Monitor. Unless
the system is completely inoperable, the Forth Monitor is enabled, and you can
continue with the next step in this procedure.
5. If you need to redirect the standard input and output to the ttya serial port, type:
ok ttya io
Note – Do not type Stop-a from a Sun server being used as a tip window to your
UltraSPARC system. Doing so will abort the operating system on the server. (If you
accidentally type Stop-a, you can recover by immediately typing go at the ok
prompt.) Typing ~# in the tip window is equivalent to pressing Stop-a at the
UltraSPARC system.
7. When you are finished using the tip window, end your tip session and exit the
window.
2. Type eeprom.
ttyb-mode = 9600,8,n,1
ttya-mode = 9600,8,n,1
Note – Ensure that the settings are consistent with TTY-type terminal or system
monitor settings.
The status field for ttyb (or the serial port you are using) must be set to off in
/etc/ttytab. Be sure to execute kill -HUP 1 (see init(8)) as root if you have
to change this entry.
Sometimes, a program will have changed the protection of /dev/ttyb (or the serial
port you are using) so that it is no longer accessible. Make sure that /dev/ttyb has
the mode set to crw-rw-rw-.
■ The serial line is in tandem mode.
If the tip connection is in tandem mode, the operating system sometimes sends
XON (^S) characters (particularly when programs in other windows are generating
lots of output). The XON characters are detected by the Forth word key?, and can
cause confusion. The solution is to turn off tandem mode with the ~s !tandem
tip command.
■ The .cshrc file generates text.
The tip connection opens a sub-shell to run cat, thus causing text to be attached to
the beginning of your loaded file. If you use dl and see any unexpected output,
check your .cshrc file.
where value is off, min, max, or menus, as described in “About Diagnostic Levels”
on page 167.
ok reset-all
Symptom
The system is unable to communicate over the network.
Action
Your system conforms to the Ethernet 10BASE-T/100BASE-TX standard, which
states that the Ethernet 10BASE-T link integrity test function should always be
enabled on both the host system and the Ethernet hub. The system cannot
communicate with a network if this function is not set identically for both the
system and the network hub (either enabled for both or disabled for both). This
problem applies only to 10BASE-T network hubs, where the Ethernet link integrity
test is optional. This is not a problem for 100BASE-TX networks, where the test is
enabled by default. Refer to the documentation provided with your Ethernet hub for
more information about the link integrity test function.
ok test net
2. If you connect the system to a network and the network does not respond, use the
OpenBoot PROM command watch-net-all to display conditions for all
network connections, type:
ok watch-net-all
For most PCI Ethernet cards, the link integrity test function can be enabled or
disabled with a hardware jumper on the PCI card, which you must set manually.
(See the documentation supplied with the card.) For the standard TPE main logic
board port, the link test is enabled or disabled through software, as shown on the
next page.
Note – Some hub designs permanently enable (or disable) the link integrity test
through a hardware jumper. In this case, refer to the hub installation or user manual
for details of how the test is implemented.
ok watch-net-all
/pci@8,700000/network@5,1
gme register test --- succeeded.
Internal loopback test -- succeeded.
Link is -- Using Onboard Transceiver - Link Up.
up
Using Onboard Transceiver - Link Up.
Looking for Ethernet Packets.
’.’ is a Good Packet. ’X’ is a Bad Packet.
Type any key to stop.
................................................................
................
....
ok
To enable or disable the link integrity test for the standard Ethernet interface, or for
a PCI-based Ethernet interface, you must first know the device name of the desired
Ethernet interface. To list the device name use either solution described below.
2. Type:
Use this method when the system is already at the OpenBoot prompt:
1. Shut down the operating system and take the system to the ok prompt.
ok nvedit
0: probe-all install-console banner
1: apply disable-link-pulse device-name
(Repeat this step for other device names as needed.)
(Press CONTROL-C to exit nvedit.)
ok nvstore
ok setenv use-nvramrc? true
Power-On Failure
Symptom
The system attempts to power on but does not boot or initialize the terminal or
monitor.
If the POST output contains an error message, then POST has failed. The most
probable cause for this type of failure is the main logic board. However, before
replacing the main logic board you should run the OpenBoot Diagnostics test-all
command by typing:
ok test-all
4. If the test-all command shows any defective components, remove them from
the main logic board and run POST again.
Replace any failed components that are not optional. Be sure to leave DIMMs in
Bank 0.
5. If POST still fails after you have removed or replaced all failed components, then
replace the main logic board.
Symptom
No video at the system monitor.
Action
1. Check that the power cord is connected to the monitor and to the wall outlet.
2. Verify with a volt-ohm meter that the wall outlet is supplying AC power.
4. If the cables and their connections are okay, then troubleshoot the monitor and
the graphics card.
ok test screen
Symptom
A disk drive read, write, or parity error is reported by the operating system or a
software application.
Action
● Replace the drive indicated by the failure message.
Symptom
Disk drive fails to boot or is not responding to commands.
Action
1. At the system ok prompt, type:
ok reset-all
ok probe-scsi
If the device responds and a message is displayed, the system FC-AL controller has
successfully probed the internal drive. This indicates that the main logic board is
operating correctly.
ok test /SUNW,qlc
3. Take one of the following actions depending on what the probe-scsi command
reports:
a. If one drive does not respond to the FC-AL controller probe but the others do,
replace the unresponsive drive.
b. If only one internal disk drive is configured with the system and the
probe-scsi test fails to show the device in the message, replace the drive.
4. If the problem is still evident after replacing the drive, replace the main logic
board.
5. If replacing both the disk drive and the main logic board does not correct the
problem, replace the associated FC-AL data cable and FC-AL backplane.
Note – You can also use the probe-scsi command to look for failures on the
FC-AL loop. An Unable to initialize error message indicates a problem on the
loop. Proceed by disconnecting all the loop devices and then probe the loop again.
If the loop is present, then swap drives in and out first, then cables, and finally loop-
device backplanes to isolate the problem.
Symptom
A disk drive fails to boot or is not responding to commands.
Action
To check whether the main logic board FC-AL controller is defective, first test the
drive response to the probe-scsi command and then run OpenBoot Diagnostics.
ok probe-scsi
If a message is displayed for each installed disk, the system FC-AL controllers have
successfully probed the devices. This indicates that the main logic board is working
correctly.
ok test /SUNW,qlc
3. Take one of the following actions depending on what the probe-scsi command
reports:
a. If one drive does not respond to the FC-AL controller probe but the others do,
replace the unresponsive drive.
b. If only one internal disk drive is configured with the system and the
probe-scsi test fails to show the device in the message, replace the drive.
4. If the problem is still evident after replacing the drive, replace the main logic
board.
5. If replacing both the disk drive and the main logic board does not correct the
problem, replace the associated FC-AL data cable and FC-AL backplane.
Symptom
A DVD/CD-ROM drive or externally connected SCSI drive read error or parity error
is reported by the operating system or a software application.
Action
1. Run the test command, type:
ok test scsi
Action
Test the response of the drive(s) to the probe-scsi-all command as follows:
ok reset-all
ok probe-scsi-all
ok test scsi
If the system has more than one SCSI disk, you must specify an address.
a. If the problem is still evident after replacing the DVD/CD-ROM drive, replace
the main logic board.
b. If replacing both the disk drive and the main logic board does not correct the
problem, replace the associated UltraSCSI data cable and UltraSCSI backplane.
Note – You can also use the probe-scsi-all command to look for failures on the
external UltraSCSI loop.
Symptom
An external SCSI drive fails to boot or is not responding to commands.
Action
To check whether the main logic board SCSI controllers are defective, first test the
external drive response to the probe-scsi-all command. Then run OpenBoot
Diagnostics by entering test scsi at the ok prompt. You can use the OpenBoot
PROM printenv command to display the OpenBoot PROM configuration variables
stored in the system NVRAM. The display includes the current values for these
variables as well as the default values. See “The printenv Command” on page 171
for more information.
ok probe-scsi-all
If a message is displayed for each installed disk, the system SCSI controllers have
successfully probed the devices. This indicates that the main logic board is working
correctly.
ok test scsi
4. If the problem remains after replacing the drive, contact your qualified service
provider to replace the associated SCSI cable and backplane.
DIMM Failure
SunVTS and POST diagnostics can report memory errors encountered during
program execution. Memory error messages typically indicate the DIMM location
number (“J” or “U” number) of the failing module. To replace a DIMM, contact a
qualified service provider.
Use the following diagram to identify the location of a failing memory module from
its J (or U) number:
Memory group 0
J0407
J0406
J0305
J0304
J0203
System Front
J0202
J0101
J0100
To check whether SunVTS software is installed, you must access your system from a
remote machine logged in to the server, connect an alphanumeric terminal or
graphics console to the server, or establish a tip connection to another Sun system.
For more information, see:
■ “How to Attach an Alphanumeric (ASCII) Terminal” on page 34
■ “How to Configure a Local Graphics Console” on page 36
■ “How to Set Up a tip Connection” on page 183
What to Do
1. Type the following:
% pkginfo -l SUNWvts
What Next
For more information, refer to the appropriate Solaris documentation, as well as the
pkgadd reference manual (man) page.
What to Do
You can run SunVTS locally or remotely. The following procedure assumes you will
test your Sun Fire 280R server by running a SunVTS session from a remote machine
using the SunVTS graphical interface. For information about SunVTS interfaces and
options, see the SunVTS User’s Guide.
1. Use the xhost command to give the remote server access to your system.
On the machine from which you will be running the SunVTS graphical interface,
type:
# /usr/openwin/bin/xhost + remote_hostname
Substitute the name of the Sun Fire 280R server for remote_hostname.
# cd /opt/SUNWvts/bin
# ./sunvts -display local_hostname:0
Substitute the name of the workstation you are using for local_hostname. Note that
/opt/SUNWvts/bin is the default directory for SunVTS binaries. If you have
installed SunVTS software in a different directory, use the appropriate path instead.
5. Fine-tune your testing session by selecting only the tests you want to run.
Click to select and deselect tests. (A check mark in the box means the item is
selected.) Some tests useful to run on a Sun Fire 280R server are listed below.
cdtest, Tests the DVD/CD-ROM drive by reading the disc and verifying
dvdtest the DVD/CD table of contents (TOC), if it exists
cputest Tests the CPU
disktest Verifies local disk drives
env5test, Tests power supply, fan tray, LEDs
i2ctest
fputest Checks the floating-point unit
fstest Tests the integrity of the software’s file systems
m64test Tests the PCI graphics board
mptest Verifies multiprocessor features (for systems with more than
one processor)
nettest Checks all the hardware associated with networking (for example,
Ethernet, token ring, quad Ethernet, fiber optic, 100-Mbit per second
Ethernet devices)
pmem Tests the physical memory (read only)
rsctest Tests the RSC card
sptest Tests the system’s on-board serial ports
tapetest Tests the various Sun tape devices
usbkbtest Tests the keyboard
vmem Tests virtual memory (a combination of the swap partition and the
physical memory)
This appendix describes the Sun Fire 280R server main logic board connector signals
and pin assignments that are accessible from the back panel.
203
Reference for the Serial Port A and B
Connectors
The serial port A and B connectors (J2001) are DB-25 type connectors located on the
main logic board back panel. Both serial ports conform to RS-423/RS-232
specifications.
13 1
Serial port A 25 14
13 1
Serial port B
25 14
1 NC Not connected
9 NC Not connected
10 NC Not connected
11 NC Not connected
12 NC Not connected
13 NC Not connected
14 NC Not connected
16 NC Not connected
18 NC Not connected
19 NC Not connected
21 NC Not connected
22 NC Not connected
23 NC Not connected
25 NC Not connected
1 8
34 1
68 35
1 Gnd Ground
2 Gnd Ground
3 NC Not connected
4 Gnd Ground
5 Gnd Ground
6 Gnd Ground
7 Gnd Ground
8 Gnd Ground
9 Gnd Ground
10 Gnd Ground
11 Gnd Ground
12 Gnd Ground
13 Gnd Ground
14 Gnd Ground
15 Gnd Ground
16 Gnd Ground
17 TERMPOWER Termpower
18 TERMPOWER Termpower
19 NC Not connected
20 Gnd Ground
21 Gnd Ground
22 Gnd Ground
23 Gnd Ground
24 Gnd Ground
25 Gnd Ground
26 Gnd Ground
27 Gnd Ground
28 Gnd Ground
29 Gnd Ground
30 Gnd Ground
31 Gnd Ground
32 Gnd Ground
33 Gnd Ground
34 Gnd Ground
35 SCSI_B_DAT<12> Data 12
36 SCSI_B_DAT<13>_ Data 13
37 SCSI_B_DAT<14>_ Data 14
38 SCSI_B_DAT<15>_ Data 15
39 SCSI_B_PAR<l> Parity 1
40 SCSI_B_DAT<0>_ Data 0
41 SCSI_B_DAT<1>_ Data 1
42 SCSI_B_DAT<2>_ Data 2
43 SCSI_B_DAT<3>_ Data 3
44 SCSI_B_DAT<4> Data 4
45 SCSI_B_DAT<5> Data 5
46 SCSI_B_DAT<6> Data 6
47 SCSI_B_DAT<7> Data 7
48 SCSI_B_PAR<0> Parity 0
49 Gnd Ground
50 NC Not connected
53 NC Not connected
54 Gnd Ground
55 SCSI_B_ATN_L Attention
56 Gnd Ground
57 SCSI_B-BSY_L Busy
58 SCSI_B_ACK_L Acknowledge
59 SCSI_B_RESET_L Reset
60 SCSI_B_MSG_L Message
61 SCSI_B_SEL_L Select
62 SCSI_B-CD_L Command
63 SCSI_B_REQ_L Request
64 SCSI_B_IO_L In/out
65 SCSI_B_DAT<8> Data 8
66 SCSI_B_DAT<9> Data 9
67 SCSI_B_DAT<10> Data 10
68 SCSI_B_DAT<11> Data 11
13 1
25 14
11 PAR_BUSY_CONN Busy
18 Gnd Ground
19 Gnd Ground
20 Gnd Ground
21 Gnd Ground
22 Gnd Ground
23 Gnd Ground
24 Gnd Ground
25 Gnd Ground
1 T_CM_FC_TX_EX_P TX +
2 GND Ground
3 T_CM_FC_TX_EX_N TX -
4, 5 NC Not connected
6 FC_RX_EX_N RX +
7 GND Ground
8 FC_RX_EX_P RX -
A C
1 2 3 4 1 2 3 4
B D
1 2 3 4 1 2 3 4
System Specifications
This appendix provides the following product specifications for the Sun Fire 280R
server:
■ “Reference for Physical Specifications” on page 218
■ “Reference for Electrical Specifications” on page 219
■ “Reference for Environmental Specifications” on page 220
217
Reference for Physical Specifications
Specification U.S.A. Metric
The system key fits into the system cover lock on the top of the system.
System key
Parameter Value
Input
Nominal Frequencies 50 Hz or 60 Hz
Nominal Voltages 100, 120, 220, or 240 VAC
Maximum Current AC RMS 9.2 A @ 100 VAC, 4.2 A @ 220 VAC
AC Operating Range 90 to 264 Vrms, 47 to 63 Hz
Outputs
Parameter Value
Operating
Temperature 5˚C to 40˚C (41˚F to 104˚F)—IEC 60068-2-1, 60068-2-2
Humidity 20% to 80% RH (noncondensing), 27 ˚C max wet
bulb—IEC 60068-2-56
Altitude 0 to 3000 meters (0 to 10,000 feet)—IEC 60068-2-13
Vibration 0.0002 G2/Hz, flat from 5–500 Hz (0.31 GRMS); z-axis
only—IEC 60068-2-64
Shock 3 G peak, 11 milliseconds half-sine pulse—IEC 60068-2-27
Declared Acoustics 6.9 Bel
Non-Operating
A boot
AC (alternating current) recovery from failure to boot, 178
power cord safe boot mode, 178
attaching strain relief, 17 boot device, how to select, 48
connecting, 16 boot sequence, server, 73
removing strain relief, 18 boot-device configuration parameter, 48
when to disconnect, 120 booting
power inlet (default), 7 after installing new hardware, 136
power inlets 1 and 2, 7 firmware, OpenBoot, 48
alphanumeric terminal, 33 over main logic board Ethernet, 59
attaching, 34 boxes shipped to you, 14
baud verification, 185
settings for, 34
antistatic
foot strap, 120 C
mat, 120 cables
wrist strap, 120, 121 keyboard, 38
array, disk, 87 mouse, 39
ASCII (American Standard Information twisted-pair Ethernet (TPE), 57
Interchange) terminal, See alphanumeric CD/DVD (compact disc/digital video disc)
terminal cleaning, 147
ASR (automatic system recovery), 68 drive troubleshooting, 193
ATM (asynchronous transfer mode), See network ejecting in an emergency, 145
ejecting manually, 143
inserting into drive, 138
when drive cannot read, 147
B Centronics compatibility, 3, 101
back panel features, 7 chassis ground screw, 7
baud rate, 35, 97 compact disc, See CD/DVD, 138
baud rate, verifying, 185 concatenation of disks, 88
configuration, See hardware configuration
Index 221
connector specifications, 201 to 213 disk configuration
connectors array, 87
pin assignments concatenation, 88
keyboard/mouse, 213 guidelines, 91 to 93
pin configuration hot spares, 89, 92
FC-AL port connector, 212 hot-plug, 65, 90, 92
keyboard/mouse, 213 mirroring, 87, 92
parallel port, 210 RAID 0, 89, 92
serial ports, 202 RAID 1, 88, 92
TPE port, 204 RAID 5, 89
UltraSCSI connector, 206 striping, 89, 92
USB connectors, 213 disk drive, 2
console caution, 40, 43, 137
enabling RSC as, 111 configuration guidelines, 91 to 93
recovering a lost console, 178 hot-plug, 65, 92
redirecting to RSC, 111 installing
removing RSC as default, 111 hot-plug operation, 132 to 135
console, system, 19, 33 non hot-plug operation, 125 to 127
locating drive bays, 6, 91, 94
cover lock, 216
removing
CPU (central processing unit) module, 1
hot-plug operation, 128 to 131
UltraSPARC III configuration guidelines, 83
non hot-plug operation, 122 to 124
creating metadevices, 87 troubleshooting, 191
disk drive names, controller numbers, 105
disk, LEDs (light-emitting diode), 6
D documentation, related, xxvi
damage, preventing door lock, 5
electrostatic, 120 drivers, 2
to tape cartridges, 149 DVD (digital video disc), See CD/DVD
device names DVD/CD-ROM or SCSI disk drive
bus probe order, 105 troubleshooting, 193
internal disk drive, 105 DVD-ROM (digital video disc-read only memory)
logical, 93 drive, 3, 6
physical name, 105 dimensions, 3
device trees, rebuilding, 137 location, 6
diagnostic use of software, 73
diagnostics, 178 to 196
available tools, 160
overview of (flowchart), 161, 164 E
diag-switch? configuration parameter, 179 ECC (error correcting code), 4, 64
dimensions, See specifications eeprom command, 189
DIMMs (dual in-line memory modules) EIA (electronic industries association), 3
capacities, 1 EIA-232D serial communications, 97, 113
See also memory modules (DIMMs) EIA-423 serial communications, 97, 113
disc, compact, See CD/DVD eject cd command, 141, 142, 143
ejecting a compact disc, 141 to 144
Index 222 Sun Fire 280R Server Owner’s Guide • January 2001
electrostatic damage, preventing, 120 pin and signal specifications, 212
emergency eject (of a compact disc), 146 controller, 104
environmental monitoring subsystem, 66 device names, 105
error messages, 67 disk drive
failure, 191
EPP (enhanced parallel port) protocol, 101
troubleshooting, 191
error correcting code (ECC), 64
external connector, 2
error messages features and description, 104
correctable ECC error, 65 interface, 104
fan-related, 67 serial data connector, 2
log file, 67 speed, 2
memory-related, 195 support, 106
POST diagnostics, 180, 181, 197
FDDI (fiber distributed data interface), See network
power-related, 67
flash PROM
temperature-related, 67
jumpers, 114
/etc/hostname file, 55
programming, 114
/etc/hosts file, 56
foot strap, antistatic, 120
Ethernet, 2, 3, 103
frame buffer card, 33
adding an interface, 54
front panel features, 5
as default boot device, 60
booting over main logic board interface, 59 fuser command, 141, 143
characteristics, 103
configuring interface, 19, 51, 53, 103
link integrity test, 52, 187 to 189
G
twisted-pair cable, attaching, 57
using multiple interfaces, 52, 54 general fault indicator, See status LEDs
external storage, 2, 3 ground screw, 7
ground screw size, 7
F
failure H
DIMM, 196 hardware configuration
disk drive, 191 CPU modules, 83
DVD/CD-ROM drive, 193 disk drives, 91 to 93
memory module, 196 Ethernet, 103
network, 187 flash PROM jumpers, 114
power supply, 195 main logic board jumpers, 112 to 114
power-on, 189 memory, 80
SCSI controller, 192, 195 PCI cards, 84 to 85
SCSI disk drive, 193 power supplies, 95
to boot, 178 SCSI port, 98 to 100
video output, 190 serial port jumpers, 113
fan tray assembly, 67 serial ports, 97
fans See fan tray assembly, 66 height, See specifications, of system
FC-AL (Fibre Channel-Arbitrated Loop) host name, 51, 54
configuration, 105 hot spares, See disk configuration
connector, 2, 104
Index 223
hot swap, See power supply L
hot-plug, See disk configuration LEDs (light-emitting diode), See status LEDs
link integrity test, 52, 187, 189
lock, 5
I lock, cover, 216
I2C bus, 66 lock, doors, 5
installing a server, 15 to 19 logical device names, 93
internal disk drive lost console, 178
device names, 105
FC-AL names, 105
names, physical, 105 M
internal disk drive bays, locating, 6, 94
main logic board
Internet Protocol Network MultiPathing CPU module, 83
software, 71 DIMM slots, 196
IP (Internet Protocol) address, 51, 54 jumpers, 112 to 114
memory bank locations, 196
managing the server, 71
J mat, antistatic, 120
jumpers, 112 to 114 memory modules (DIMMs)
flash PROM jumpers, 114 bank locations, 196
serial port jumpers, 113 configuration guidelines, 80
damage, preventing
electrostatic, 80
error reporting, 196
K handling, 80
key, lock the cover, 216 interleaving, 81
interleaving banks, 81
key, replacing, 5
location "U" or "J" number, 196
keyboard connector
metadevice, 87
location, 7
mirroring, disk, 87, 92
keyboard sequences
Stop-a, 182, 184 modem line, attaching to serial port, 33
Stop-a equivalent in a tip window, 184 monitor, attaching, 36
Stop-D, 179 mouse, attaching, 39
Stop-F, unsupported, 179 moving the system, caution, 40, 43
Stop-N functionality, 178
keyboard, attaching, 38
keyboard/mouse
connector
N
pin assignments, 213 network
pin configuration, 213 ATM (Asynchronous Transfer Mode), 3
keyswitch configuring interface, 19
location, 8 FDDI (Fiber Distributed Data Interface), 3, 86
power-on mode, 41, 44 name server, 56
settings, 9 primary interface, 52
standby mode, 62 token ring, 3, 86
troubleshooting, 187
Index 224 Sun Fire 280R Server Owner’s Guide • January 2001
types, 19 POST (power-on self-test), 72
nvedit command, 189 POST diagnostics
nvstore command, 189 error reporting, 181
how to use, 179
overview, 166
power
O LED indicator, 10
OpenBoot Diagnostics software, 72 turning off, 61
OpenBoot firmware, 48 turning on, 40, 44
version, 11 power cord, AC, when to disconnect, 120
OpenBoot PROM variables power supply, 6
boot-device, 48 configuration guidelines, 95
diag-switch?, 179 default, 6
operating system software display, 6
installing, 19 fault monitoring, 67
loading over a network, 59 hot swap capability, 3, 68, 96
options, installing, 16 LEDs, 95
output capacity, 95
redundancy, 3, 68, 95
troubleshooting, 195
P power-on self-test, See POST diagnostics
parallel port, 3 pre-POST preparation, verifying baud rate, 185
characteristics, 101 probe-scsi command, 192, 195
location, 7 probe-scsi-all command, 194
pin and signal specifications, 210
parity, 4, 35, 65, 89
parts, shipped to you, 14
PCI (Peripheral Component Interconnect) R
buses, 2, 84 to 85 RAID (redundant arrays of independent disks), See
configuration guidelines, 84 to 85 disk configuration
parity protection, 65 reconfiguration boot, 136
slot characteristics, 85 recovery of console, 178
card reliability, availability, and serviceability, 64 to 70
configuration guidelines, 84 to 85
reset command, 50
device name, 49
frame buffer card, 36 RSC (Remote System Control)
slot characteristics, 85 access from the PC, 74
slot locations, 7, 85 card, 107
tape drive, 3 described, 74
types, 2 features, 70, 74, 107
host adapters, 2 firmware, 12
jumpers, 108
PCI (Peripheral Component Interconnect) See PCI
monitoring, 108
card, PCI buses
ports, 107
pkgadd utility, 198 software, 12, 110
pkginfo command, 197 software features, 110
Index 225
S status and control panel, 8
safe boot mode, console recovery, 178 location, 8
SCSI (Small Computer Systems Interconnect) status LEDs, 65
bus length, 98 behavior during POST, 181
cabling guidelines, 99 environmental fault indicators, 67
configuration guidelines, 98 to 100 location, 8
connector location, 7 meaning, 10
controller, troubleshooting, 192, 195 Stop-a keyboard combination, 137
multi-initiator support, 100 storage software information, 77
parity protection, 65 striping of disks, 89, 92
target IDs, 98 Sun Cluster software, 71
termination, 99 Sun Management Center software, 161, 177, 178
serial ports, 3 Sun StorEdge Component Manager
configuring, 113 array enclosure monitor software, 76
jumpers, 113
Sun StorEdge LibMON
location, 7
tape library monitoring software, 76
pin and signal specification, 202
Sun StorEdge Management Console
server boot event sequence, 73
storage management software, 76
server installation, 15 to 19
SunVTS (Validation Test Suite) software
server management, 71 checking if installed, 197
server media kit, contents of, 20 how to use, 72
server software, 11 system configuration, See hardware configuration
shipping (what you should receive), 14 system console, 19
show-devs command, 49 system features, 1 to 4
shutdown, 61 back panel, 7
software drivers, 2 front panel, 5
software, server, 11 system ground screw, 7
Solaris system I/O (input/output), 2
operating environment version, 11 system key, replacing, 5
software features, 11 system management, 71
tools, 11 system software, 11
Solaris Bandwith Manager software, 71 system specifications, 215 to 218
Solaris Management Center software, 71 connectors, 201 to 213
Solaris Management Console software, 72 depth, 216
Solaris PC NetLink software, 78 electrical, 217
Solaris Remote System Control software, 71 environmental, 218
Solaris Resource Manager software, 71 non-operating, 218
operating, 218
Solstice DiskSuite software, 66, 87, 92
height, 216
backup, 76
physical, 216
domain management, 76
weight, 216
site management, 76
storage management software, 76
specifications, See system specifications
Index 226 Sun Fire 280R Server Owner’s Guide • January 2001
T USB (Universal Serial Bus)
tape cartridge buses, 2
ejecting, 152 keyboard, 2
handling, 149 mouse, 2
inserting into drive, 150 ports, 2
magnetic fields and, 149 USB (Universal Serial Bus) port, pin and signal
storing, 149 specifications, 213
sunlight and, 149 using software tools, 73
write-protecting, 150
tape drive, 3
cleaning, 154
controlling with software commands, 154
V
location, 6 verifying baud rate, 185
temperature sensors, 66 VERITAS
terminal, alphanumeric, 33, 34 File System (VxFS) software, 76
Volume Manager disk storage software, 77
terminal, baud verification, 185
VERITAS software, 87
thermistors, 66
video out failure, 190
tip connection, 33, 180, 197
token ring, See network
TPE (twisted-pair Ethernet) port
attaching twisted-pair cable, 57 W
location, 7 watch-net-all command, 188
pin and signal specification, 204 weight, See specifications
troubleshooting, 178 to 196 Windows operating environment, 176
disk drive, 191, 193
wrist strap, antistatic, 120, 121
DVD/CD drive, 191
DVD/CD-ROM drive, 193 write-protecting, a tape cartridge, 150
FC-AL disk drive failure, 191
memory, 195
network, 187
power supply, 195
SCSI controller, 192, 195
video output, 190
U
UltraSCSI (Ultra Small Computer System Interface)
port
pin and signal specification, 206
UltraSCSI disk drive, See disk drive
UltraSPARC III CPU, See CPU module
universal PCI card, 84
Index 227
Index 228 Sun Fire 280R Server Owner’s Guide • January 2001