Sun Fire™ V490 Server Administration Guide Sun Microsystems, Inc. www.sun.com Part No. 817-3951-10 August 2004, Revision A Submit comments about this document at: http://www.sun.
Copyright 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
Contents Preface Part I xxv Installation 1. Sun Fire V490 Server Installation About the Parts Shipped to You 1 1 How to Install the Sun Fire V490 Server Part II 2 Background 2.
Automatic System Recovery MPxIO 21 21 Sun Remote System Control Software 22 Hardware Watchdog Mechanism and XIR Dual-Loop Enabled FC-AL Subsystem 23 Support for RAID Storage Configurations Error Correction and Parity Checking 3.
Configuration Rules 43 About the HSSDC FC-AL Port 43 About the FC-AL Host Adapters Configuration Rules 44 About the Internal Disk Drives Configuration Rule 4.
About Manually Configuring Devices Deconfiguring Devices vs. Slots 59 59 Deconfiguring All System Processors Device Paths 60 Reference for Device Identifiers 5.
About Monitoring the System 101 Monitoring the System Using Remote System Control Software Monitoring the System Using Sun Management Center About Exercising the System 103 105 Exercising the System Using SunVTS Software 106 Exercising the System Using Hardware Diagnostic Suite Reference for OpenBoot Diagnostics Test Descriptions 109 Reference for Decoding I2C Diagnostic Test Messages 111 Reference for Terms in Diagnostic Output Part III 102 108 114 Instructions 7.
. Configuring Network Interfaces and the Boot Device How to Configure the Primary Network Interface 144 How to Configure Additional Network Interfaces 146 How to Select the Boot Device 9.
11. Monitoring the System 185 How to Monitor the System Using Sun Management Center Software 186 How to Monitor the System Using the System Controller and RSC Software How to Use Solaris System Information Commands How to Use OpenBoot Information Commands 12.
B. System Specifications 217 Physical Specifications 217 Electrical Specifications 218 Environmental Specifications 219 Agency Compliance Specifications 220 Clearance and Service Access Specifications C.
Figures FIGURE 2-1 Sun Fire V490 Server Front Panel Features 12 FIGURE 2-2 Four-Position System Control Switch in Locked Position FIGURE 2-3 Sun Fire V490 Server Back Panel Features FIGURE 2-4 Back Panel External Ports 18 FIGURE 3-1 Memory Module Groups A0, A1, B0, B1 FIGURE 3-2 PCI Slots 32 FIGURE 3-3 Sun System Controller (SC) Card FIGURE 3-4 SC Card Ports 35 FIGURE 3-5 Jumper Identification Guide FIGURE 3-6 Hardware Jumpers on PCI Riser Board 37 FIGURE 3-7 Power Supply Locations 38
xii Sun Fire V490 Server Administration Guide • August 2004
Tables TABLE 2-1 System LEDs 14 TABLE 2-2 Fan Tray LEDs TABLE 2-3 Hard Disk Drive LEDs TABLE 2-4 System Control Switch Settings 16 TABLE 2-5 Ethernet LEDs TABLE 2-6 Power Supply LEDs TABLE 3-1 Association Between Processors and DIMM Groups 30 TABLE 3-2 PCI Bus Characteristics, Associated Bridge Chips, Centerplane Devices, and PCI Slots 32 TABLE 3-3 PCI Riser Board Jumper Functions 37 TABLE 3-4 FC-AL Features and Advantages 42 TABLE 4-1 Ethernet Port LEDs TABLE 5-1 System Administrati
TABLE 6-8 What Sun Management Center Software Monitors 103 TABLE 6-9 FRU Coverage of System Exercising Tools TABLE 6-10 OpenBoot Diagnostics Menu Tests TABLE 6-11 OpenBoot Diagnostics Test Menu Commands TABLE 6-12 Sun Fire V490 I2C Bus Devices TABLE 6-13 Abbreviations or Acronyms in Diagnostic Output TABLE 7-1 Ways of Accessing the ok Prompt TABLE 7-2 OpenBoot Configuration Variables That Affect the System Console TABLE 11-1 Using Solaris Information Display Commands 197 TABLE 11-2 Using
Declaration of Conformity Compliance Model Number: Product Family Name: 490 Sun Fire V490 EMC European Union This equipment complies with the following requirements of the EMC Directive 89/336/EEC: As Telecommunication Network Equipment (TNE) in both Telecom Centers and Other Than Telecom Centers per (as applicable): EN300-386 V.1.3.
xvi Sun Fire V490 Server Administration Guide • August 2004
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.
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. ICES-003 Class B Notice - Avis NMB-003, Classe B This Class B digital apparatus complies with Canadian ICES-003. Cet appareil numérique de la classe B est conforme à la norme NMB-003 du Canada.
BSMI Class A Notice The following statement is applicable to products shipped to Taiwan and marked as Class A on the product compliance label.
xx Sun Fire V490 Server Administration Guide • August 2004
Preface The Sun Fire V490 Server Administration Guide is intended to be used by experienced system administrators. It includes general descriptive information about the Sun Fire™ V490 server and detailed instructions for installing, configuring, and administering the server and for diagnosing problems with the server.
Each part of the book is divided into chapters. Part One Chapter 1 describes and provides instructions for Sun Fire V490 server installation. Part Two Chapter 2 presents an illustrated overview of the server and a description of the server’s reliability, availability, and serviceability (RAS) features. Chapter 3 describes and illustrates major system hardware. Chapter 4 describes the network interfaces and system firmware, including OpenBoot™ environmental monitoring.
Using UNIX Commands This document might not contain information on basic UNIX® commands and procedures such as shutting down the system, booting the system, and configuring devices. Refer to the following for this information: ■ Documentation that you received with your system ■ Solaris Operating System documentation, which is at http://docs.sun.com Typographic Conventions Typeface* Meaning Examples AaBbCc123 The names of commands, files, and directories; on-screen computer output Edit your.
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 xxiv Application Title Part Number / Location Site Planning Site Planning Guide for Entry-Level Servers, Version 1.
Application Title Part Number / Location Firmware configuration OpenBoot PROM Enhancements for Diagnostic Operation 817-6957-10 Documentation CD OpenBoot 4.x Command Reference Manual 816-1177-10 http://docs.sun.com Sun Fire V490 Server Product Notes 817-4193-10 Documentation CD Sun Remote System Control (RSC) 2.2.
Contacting Sun Technical Support If you have technical questions about this product that are not answered in this document, go to: http://www.sun.com/service/contacting Sun Welcomes Your Comments Sun is interested in improving its documentation and welcomes your comments and suggestions. You can submit your comments by going to: http://www.sun.
PART I Installation This one-chapter part of the Sun Fire V490 Server Administration Guide provides instructions for installing your server. For illustrated background information about the hardware and software components of the Sun Fire V490 server, see the chapters in Part Two – Background. For detailed instructions on how to configure and administer the server, and how to perform various diagnostic routines to resolve problems with the server, see the chapters in Part Three – Instructions.
CHAPTER 1 Sun Fire V490 Server Installation This chapter provides both an overview of, and instructions for, the hardware and software tasks you need to accomplish to get the Sun Fire™ V490 server up and running. This chapter explains some of what you need to do, and points you to the appropriate section in this guide, or to other manuals for more information.
Unpacking instructions are printed on the outside of the shipping carton. How to Install the Sun Fire V490 Server Each step in this procedure refers you to a particular document or to a section of this guide for instructions. Complete each step in the order listed. The best way to begin your installation of a Sun Fire V490 server is by completing the rackmounting and setup procedures in the Sun Fire V490 Server Setup and Rackmounting Guide. This guide is shipped with your server in the ship kit box.
You need to provide specific networking information about the server when you install the Solaris™ Operating System (Solaris OS). For background information about network support, see “About the Network Interfaces” on page 47. ■ How do you want to use and configure the machine’s internal disks? For background information about the internal disks, see “About the Internal Disk Drives” on page 45.
Note – To set up a serial connection using a Sun workstation or an ASCII terminal, insert the RJ-45 serial cable into the DB-25 adapter (Sun part number 530-2889-03) supplied in the ship kit. Plug in the adapter to the DB-25 serial connector on the terminal or the Sun workstation. If you are using a network terminal server (NTS), refer to “Serial Port Connector” on page 210 to determine whether you need to use the adapter. 4. Install any optional components shipped with your system.
6. Turn on power to your server. See “How to Power On the System” on page 122. For information about the LED status indicators that appear during power-on, see “LED Status Indicators” on page 13. 7. Install and boot the Solaris OS software. See the installation instructions provided with your Solaris software. You should also consult the Solaris on Sun Hardware Platform Guide for your particular operating system which contains platform-specific information about software installation. 8.
6 Sun Fire V490 Server Administration Guide • August 2004
PART II Background The five chapters within this part of the Sun Fire V490 Server Administration Guide explain and illustrate in detail the various components of the server’s hardware, software, and firmware. Use the chapters as a guided tour through the panels, cables, cards, switches, and so forth that make up your server.
CHAPTER 2 System Overview This chapter introduces you to the Sun Fire V490 server and describes some of its features.
■ 16 Mbytes of local static random access memory (SRAM) external cache memory per processor ■ Slots for up to 16 dual inline memory modules (DIMMs)—eight per processor A fully configured Sun Fire V490 system includes a total of four UltraSPARC IV processors residing on two CPU/Memory boards. For more information, see “About the CPU/Memory Boards” on page 27. System main memory is provided by up to 32 DIMMs, which operate at a 75-MHz clock frequency. The system supports 512-Mbyte and 1-Gbyte DIMMs.
The system provides two on-board Ethernet host PCI adapters, which support several modes of operations at 10, 100, and 1000 megabits per second (Mbps). Additional Ethernet interfaces or connections to other network types can be provided by installing the appropriate PCI interface cards. Multiple network interfaces can be combined with multipathing software to provide hardware redundancy and failover capability.
System reliability, availability, and serviceability (RAS) are enhanced by features that include hot-pluggable disk drives and redundant, hot-swappable power supplies. A full list of RAS features is in the section, “About Reliability, Availability, and Serviceability Features” on page 19. Locating Front Panel Features The illustration below shows the system features that you can access from the front panel.
gain access to the disk drives, power supplies, and Fan Tray 0. If the media door is locked and the power supply access panel is in place, you will not be able to gain access to the power supplies, disk drives, and Fan Tray 0—even if the PCI access panel is unlocked. Note – The same key operates the security lock, the system control switch (see “System Control Switch” on page 15), and the top panel lock for the PCI and CPU access panels.
Listed from left to right, the system LEDs operate as described in the following table. TABLE 2-1 System LEDs Name Description Locator This white LED is lit by the Sun Management Center, RSC software, or by the Solaris command to locate a system. Fault This amber LED lights when the system hardware or software has detected a system fault. Power/OK This green LED lights when the main power (48 VDC) is on. The following table describes the fan tray LEDs.
Power Button The system Power button is recessed to prevent accidentally turning the system on or off. The ability of the Power button to turn the system on or off is controlled by the system control switch. See the section, “System Control Switch” on page 15. If the operating system is running, pressing and releasing the Power button initiates a graceful software system shutdown. Pressing and holding in the Power button for five seconds causes an immediate hardware shutdown.
The following table describes the function of each system control switch setting. TABLE 2-4 Position System Control Switch Settings Icon Description Normal This setting enables the system Power button to power the system on or off. If the operating system is running, pressing and releasing the Power button initiates a graceful software system shutdown. Pressing and holding the Power button in for five seconds causes an immediate hardware power off.
Locator LED Power/OK LED Fault LED SC card USB ports (see Figure 2-4) PCI card slots SC ports: Serial AC input for Power Supply 0 Ethernet AC input for Power Supply 1 FIGURE 2-3 Power Supply 1 status LEDs Power Supply 0 status LEDs Serial port FC-AL port Ethernet ports (The ports above not visible in this illustration; see Figure 2-4.) Sun Fire V490 Server Back Panel Features Main system LEDs—Locator, Fault, and Power/OK—are repeated on the back panel.
TABLE 2-6 lists and describes the power supply LEDs on the system’s back panel. TABLE 2-6 Power Supply LEDs Name Description OK-to-Remove This blue LED lights when it is safe to remove the power supply from the system. Fault This amber LED lights when the power supply’s internal microcontroller detects a fault in the monitored power supply. Note that the system Fault LED on the front panel will also be lit when this occurs.
About Reliability, Availability, and Serviceability Features Reliability, availability, and serviceability (RAS) are aspects of a system’s design that affect its ability to operate continuously and to minimize the time necessary to service the system. 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.
Power Supply Redundancy The system features two hot-swappable power supplies, either of which is capable of handling the system’s entire load. Thus, the system provides N+1 redundancy, allowing the system to continue operating should one of the power supplies or its AC power source fail. For more information about power supplies, redundancy, and configuration rules, see “About the Power Supplies” on page 38.
The power subsystem is monitored in a similar fashion. Polling the power supply status registers periodically, the monitoring subsystem indicates the status of each supply’s DC outputs. If a power supply problem is detected, an error message is displayed on the system console and logged in the /var/adm/messages file. Additionally, LEDs located on each power supply are illuminated to indicate failures.
■ ■ ■ ■ ■ Host-level multipathing (there is no multipathing support for boot devices) Physical host controller interface (pHCI) support Sun StorEdge T3 and Sun StorEdge A5x00 support Load balancing Coexistence with Alternate Pathing (AP) and Dynamic Multipathing (DMP) For further details about MPxIO, see “Multiplexed I/O (MPxIO)” on page 66. Also consult your Solaris documentation.
Hardware Watchdog Mechanism and XIR To detect and respond to system hang conditions, the Sun Fire V490 system features a hardware watchdog mechanism—a hardware timer that is continually reset as long as the operating system is running. In the event of a system hang, the operating system is no longer able to reset the timer. The timer will then expire and cause an automatic externally initiated reset (XIR), eliminating the need for operator intervention.
Support for RAID Storage Configurations By attaching one or more external storage devices to the Sun Fire V490 server, you can use a software RAID application, such as Sun StorEdge™, to configure system disk storage in a variety of different RAID levels. Configuration options include RAID 0 (striping), RAID 1 (mirroring), RAID 0+1 (striping plus mirroring), RAID 1+0 (mirroring plus striping), and RAID 5 (striping with interleaved parity).
CHAPTER 3 Hardware Configuration This chapter provides hardware configuration information for the Sun Fire V490 server.
About Hot-Pluggable and HotSwappable Components In a Sun Fire V490 system, the FC-AL disk drives are hot-pluggable components and the power supplies are hot-swappable. (No other component of the system is either hot-pluggable or hot-swappable.) Hot-pluggable components are those that you can install or remove while the system is running, without affecting the rest of the system’s capabilities.
Disk Drives Sun Fire V490 internal disk drives are hot-pluggable. However, certain software preparations are required prior to removing or installing a drive. To perform Sun Fire V490 disk drive hot-plug operations, you use the Solaris luxadm utility. The luxadm utility is a command-line tool for managing intelligent storage arrays such as Sun StorEdge A5x00 series disk arrays or Sun Fire V490 internal storage arrays. For more information about luxadm, see the luxadm man page.
VIS provides high levels of multimedia performance, including real-time video compression and decompression and two streams of MPEG-2 decompression at full broadcast quality with no additional hardware support. The Sun Fire V490 server employs a shared-memory multiprocessor architecture with all processors sharing the same physical address space. The system processors, main memory, and I/O subsystem communicate via a high-speed system interconnect bus, operating at a clock rate of 150 MHz.
FIGURE 3-1 Memory Module Groups A0, A1, B0, B1 You must physically remove a CPU/Memory board from the system before you can install or remove DIMMs. The DIMMs must be added four-at-a-time within the same DIMM group, and each group used must have four identical DIMMs installed—that is, all four DIMMs in the group must be from the same manufacturing vendor and must have the same capacity (for example, four 512-Mbyte DIMMs or four 1-Gbyte DIMMs).
Memory Interleaving You can maximize the system’s memory bandwidth by taking advantage of its memory interleaving capabilities. Sun Fire V490 systems support two-way, four-way, and eight-way memory interleaving. In most cases, higher interleaving factors result in greater system performance. However, actual performance results may vary depending on the system application.
TABLE 3-1 Association Between Processors and DIMM Groups (Continued) CPU Number CPU/Memory Slot Associated Local DIMM Groups CPU 1 Slot B B0, B1 CPU 2 Slot A A0, A1 CPU 3 Slot B B0, B1 Configuration Rules ■ DIMMs must be added four-at-a-time within the same group of DIMM slots; every fourth slot belongs to the same DIMM group.
Note – PCI cards in a Sun Fire V490 system are not hot-pluggable. TABLE 3-2 PCI Bus Characteristics, Associated Bridge Chips, Centerplane Devices, and PCI Slots PCI Bridge PCI Bus 0 PCI A 0 Clock Rate (MHz)/ Bandwidth (bits)/ Voltage (V) Integrated Devices PCI Slots 66 MHz 64 bits 3.3V None Full-length slots 0 and 1 PCI B 33 MHz 64 bits 5V IDE controller (interface to the DVD-ROM drive) Full-length slot 2, short slots 3, 4, 5 1 PCI C 66 MHz 64 bits 3.
Configuration Rules ■ Three slots (0, 1, 2) accept short or long PCI cards, while the other three (3, 4, 5) support only short cards; that is, cards less than 7.5 inches (~19 cm) long. ■ 33-MHz slots accept 5V PCI cards; 66-MHz slots are keyed as 3.3V only cards. ■ All slots accept either 32-bit or 64-bit PCI cards. ■ All slots comply with PCI Local Bus Specification Revision 2.1. ■ Each slot can supply up to 25 watts of power. The total power used for all six slots must not exceed 90 watts.
FIGURE 3-3 Sun System Controller (SC) Card The SC card features serial and Ethernet interfaces that provide simultaneous access to the Sun Fire V490 server for multiple RSC software users. RSC software users are provided secure access to the system’s Solaris and OpenBoot console functions and have full control over power-on self-test (POST) and OpenBoot Diagnostics. The SC card runs independently of the host server, and operates off of 5V standby power from the system’s power supplies.
SC Serial port SC Ethernet port FIGURE 3-4 SC Card Ports Both SC connection ports can be used simultaneously or individually disabled. Note – You must install the Solaris OS and the Sun Remote System Control software prior to setting up an SC console. For more information, see “How to Monitor the System Using the System Controller and RSC Software” on page 190. Once you install the operating system and the RSC software, you can then configure the system to use the SC as the system console.
About Hardware Jumpers Three jumpers are located on the Sun Fire V490 system’s PCI riser board. Note that jumpers are set at the factory to ensure best system performance. Be aware that moving any jumper shunt from its default location can render the system unstable or unusable. All jumpers are marked with identification numbers. For example, the jumpers on the system PCI riser board are marked J1102, J1103, and J1104. Jumper pins are located immediately adjacent to the identification number.
J1103 J1104 J1102 Hardware Jumpers on PCI Riser Board FIGURE 3-6 The functions of the PCI riser board jumpers are shown in TABLE 3-3.
■ J1103 – Labeled “Hi-Lo” on the PCI riser board, this jumper is reserved for future use. ■ J1104 – Labeled “WREN” on the PCI riser board, this jumper controls write permissions for the system Boot PROM. In the default position with the shunt covering pins 1 and 2, the system Boot PROM is write-enabled. Moving the shunt to the other position prevents updating the PROM. About the Power Supplies A central power distribution board (PDB) delivers DC power to all internal system components.
The power supplies provide 48-volt and 5-volt standby outputs to the system. The 48-volt output powers point-of-load DC/DC converters that provide 1.5V, 1.8V, 2.5V, 3.3V, 5V, and 12V to the system components. Output current is shared equally between both supplies via active current-sharing circuitry. Power supplies in a redundant configuration feature a hot-swap capability. You can remove and replace a faulty power supply without shutting down the operating system or turning off the system power.
Caution – Fans on a Sun Fire V490 system are not hot-pluggable. Do not attempt to access any internal components unless you are a qualified service technician. Detailed service instructions can be found in the Sun Fire V490 Server Parts Installation and Removal Guide, which is included on the Sun Fire V490 Documentation CD. Caution – A complete set of two working fan trays must be present in the system at all times. After removing a fan tray, you must install a replacement fan tray.
■ ■ Fan speed in revolutions per minute (RPM) (monitored) Fan Fault LEDs (controlled) Configuration Rule ■ The minimum system configuration requires a complete set of two working fan trays—Fan Tray 0 for the CPUs and Fan Tray 1 for the FC-AL drives and PCI cards. Note – Do not attempt to access any internal components unless you are a qualified service technician.
FC-AL devices employ a high-performance serial interface, which supports multiple standard protocols such as Small Computer Systems Interface (SCSI) and Asynchronous Transfer Mode (ATM). By supporting these standard protocols, FCAL preserves any investment in legacy systems, firmware, applications, and software. The unique features of FC-AL provide many advantages over other data transfer technologies.
About the FC-AL Backplane All Sun Fire V490 servers include a single FC-AL backplane with connections for two internal hard disks, both of which are hot-pluggable. The FC-AL backplane accepts two, low-profile (1.0-inch, 2.54-cm), dual-ported FC-AL disk drives. Each disk drive is connected to the backplane via a standard 40pin single connector attachment (SCA) interface.
About the HSSDC FC-AL Port The Sun Fire V490 system back panel includes an FC-AL port with a high-speed serial data connector (HSSDC). Note – At this time, no Sun storage products are supported utilizing the HSSDC connector. About the FC-AL Host Adapters The Sun Fire V490 server uses an intelligent Fibre Channel processor as its on-board FC-AL controller. Integrated into the system centerplane, the processor resides on PCI Bus C and supports a 64-bit, 66-MHz PCI interface.
About the Internal Disk Drives The Sun Fire V490 system includes two internal, low-profile (1.0-inch, 2.54-cm) FC-AL disk drives, attached to a backplane. (The system also includes an external FC-AL port; see the section, “About the HSSDC FC-AL Port” on page 44.) Internal disks are available in storage capacities of 73 or 146 Gbytes, with a rotation speed of 10,000 RPM.
The port is accessible by connecting an RJ-45 serial cable to the back panel serial port connector. For your convenience, a serial port adapter (part number 530-2889-03) is included in your Sun Fire V490 server ship kit. This adapter enables you to use a standard RJ-45 serial cable to connect directly from the serial connector on the back panel to a Sun workstation, or to any other terminal that is equipped with a DB-25 serial connector.
CHAPTER 4 Network Interfaces and System Firmware This chapter describes the networking options of the system and provides background information about the system’s firmware.
Two back panel ports with RJ-45 connectors provide access to the on-board Ethernet interfaces. Each interface is configured with a unique media access control (MAC) address. Each connector features two LEDs, as described in TABLE 4-1. TABLE 4-1 Ethernet Port LEDs Name Description Activity This amber LED lights when data is either being transmitted or received by the particular port. Link Up This green LED lights when a link is established at the particular port with its link partner.
To help maximize system availability, make sure that any redundant network interfaces reside on separate PCI buses, supported by separate PCI bridges. For additional details, see “About the PCI Cards and Buses” on page 31. About the ok Prompt A Sun Fire V490 system with Solaris OS software is capable of operating at different run levels. A synopsis of run levels follows; for a full description, see the Solaris system administration documentation.
What You Should Know About Accessing the ok Prompt It is important to understand that when you access the ok prompt from a functioning Sun Fire V490 system, you are suspending the Solaris OS software and placing the system under firmware control. Any processes that were running under the Solaris OS software are also suspended, and the state of such processes may not be recoverable. The firmware-based tests and commands you run from the ok prompt have the potential to affect the state of the system.
Gracefully halting the system prevents data loss, allows you to warn users beforehand, and causes minimal disruption. You can usually perform a graceful halt, provided Solaris OS software is running and the hardware has not experienced serious failure.
An online version of the manual is included with the Solaris Software Supplement CD that ships with Solaris software. It is also is available at the following web site under Solaris on Sun Hardware: http://docs.sun.com About OpenBoot Environmental Monitoring Environmental monitoring and control capabilities for Sun Fire V490 systems reside at both the operating system level and the OpenBoot firmware level.
Note – Using the Stop-A keyboard command to enter the OpenBoot environment during power-on or reset will immediately disable the OpenBoot environmental monitor. If you want the OpenBoot PROM environmental monitor enabled, you must reenable it prior to rebooting the system. If you enter the OpenBoot environment through any other means—by halting the operating system, by powercycling the system, or as a result of a system panic—the OpenBoot environmental monitor will remain enabled.
You can obtain environmental status at any time, regardless of whether OpenBoot environmental monitoring is enabled or disabled. The .env status command simply reports the current environmental status information; it does not take action if anything is abnormal or out of range. For an example of .env command output, see “How to Obtain OpenBoot Environmental Status Information” on page 155.
Stop-F Functionality The Stop-F functionality is not available in systems with USB keyboards. However, the RSC bootmode forth command provides similar functionality. For more information, see the Sun Remote System Control (RSC) 2.2 User’s Guide, which is included on the Sun Fire V490 Documentation CD. Stop-N Functionality The Stop-N sequence is a method of bypassing problems typically encountered on systems with misconfigured OpenBoot configuration variables.
■ ■ ■ ■ FC-AL subsystem Ethernet interface USB interface Serial interface In the event of such a hardware failure, firmware-based diagnostic tests isolate the problem and mark the device (using the 1275 Client Interface, via the device tree) as either failed or disabled. The OpenBoot firmware then deconfigures the failed device and reboots the operating system. This all occurs automatically, as long as the Sun Fire V490 system is capable of functioning without the failed component.
Error Handling Summary Error handling during the power-on sequence falls into one of three cases summarized in the following table. Scenario System Behavior Notes No errors are detected. The system attempts to boot if auto-boot? is true. By default, auto-boot? and auto-boot-onerror? are both true. Nonfatal errors are detected. The system attempts to boot if auto-boot? and auto-boot-onerror? are both true.
Reset Scenarios The system control switch position and three OpenBoot configuration variables, service-mode?, diag-switch?, and diag-trigger, control whether and how the system runs firmware diagnostics in response to system reset events. When you set the system control switch to the Diagnostics position, the system is in service mode and runs tests at Sun-specified levels, disabling auto-booting and ignoring the settings of OpenBoot configuration variables.
Normal Mode and Service Mode Information You will find a full description of normal and service modes, as well as detailed information about the OpenBoot configuration variables that affect ASR behavior, in OpenBoot PROM Enhancements for Diagnostic Operation, which is available on the Sun Fire V490 Documentation CD.
Device Paths When manually deconfiguring and reconfiguring devices, you might need to determine the full physical paths to those devices. You can do this by typing: ok show-devs The show-devs command lists the system devices and displays the full path name of each device.
Reference for Device Identifiers Refer to the following table when manually specifying which devices to deconfigure and reconfigure.
62 Sun Fire V490 Server Administration Guide • August 2004
CHAPTER 5 System Administration Software This chapter provides an introduction to system administration software tools supported on the Sun Fire V490 system.
The following table provides a summary of each tool with a pointer to additional information. TABLE 5-1 System Administration Tool Summary For More Information Tool Description Multipathing software Multipathing software is used to define and control alternate (redundant) physical paths to I/O devices. If the active path to a device becomes unavailable, the software can automatically switch to an alternate path to maintain availability. See “About Multipathing Software” on page 64.
■ Multiplexed I/O (MPxIO) is a new architecture fully integrated within the Solaris OS (beginning with Solaris 8) that enables I/O devices to be accessed through multiple host controller interfaces from a single instance of the I/O device. For More Information For information about setting up redundant hardware interfaces for storage devices or networks, see “About Redundant Network Interfaces” on page 48.
■ Performance analysis tools, which enable you to monitor I/O performance and isolate bottlenecks ■ A graphical user interface (GUI), which simplifies storage management ■ Support for online resizing, which enables volumes and their file systems to grow and shrink online ■ Online reconfiguration facilities, which let you change to a different RAID configuration or modify characteristics of an existing configuration Multiplexed I/O (MPxIO) A newer alternative to dynamic multipathing (DMP) that is als
Disk Concatenation Disk concatenation is a method for increasing logical volume size beyond the capacity of one disk drive by creating one large volume from two or more smaller drives. This lets you create arbitrarily large partitions. 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.
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 disk drive. RAID 5: Disk Striping With Parity RAID 5 is an implementation of disk striping in which parity information is included with each disk write.
About Sun Cluster Software Sun™ Cluster software lets you connect up to eight Sun servers 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 running on a standalone server or on a domain within a standalone server. With Sun Cluster software, you can add or remove nodes while online, and mix and match servers to meet your specific needs.
During initial installation of the Sun Fire V490 system and the Solaris OS software, you must use the built-in serial port (ttya) to access the system console. After installation, you can configure the system console to use different input and output devices. See TABLE 5-2 for a summary.
Instructions for attaching and configuring hardware to access the system console are given in Chapter 7. The following subsections, “Default System Console Configuration” on page 71 and “Alternative System Console Configuration” on page 71, provide background information and references to instructions appropriate for the particular device you choose to access the system console.
Note – Power-on self-test (POST) diagnostics cannot display status and error messages to a local graphics terminal. If you configure a local graphics terminal as the system console, POST messages will be redirected to the serial port (ttya), but other system console messages will appear on the graphics terminal. Using the System Controller as the System Console Once the system controller (SC) is set up and its software configured, you can use the SC and RSC software as the system console.
CHAPTER 6 Diagnostic Tools The Sun Fire V490 server and its accompanying software contain many tools and features that help you: ■ ■ ■ Isolate problems when there is a failure of a field-replaceable component Monitor the status of a functioning system Exercise the system to disclose an intermittent or incipient problem This chapter introduces the tools that let you accomplish these goals, and helps you to understand how the various tools fit together.
The diagnostic tool spectrum also ranges from standalone software packages, to firmware-based power-on self-tests (POST), to hardware LEDs that tell you when the power supplies are operating. Some diagnostic tools enable you to examine many computers from a single console, others do not. Some diagnostic tools stress the system by running tests in parallel, while other tools run sequential tests, enabling the machine to continue its normal functions.
TABLE 6-1 Summary of Diagnostic Tools (Continued) Diagnostic Tool Type What It Does Accessibility and Availability Remote Capability SC card and RSC software Hardware and software Monitors environmental conditions, performs basic fault isolation, and provides remote console access Can function on standby power and without operating system Designed for remote access Sun Management Center Software Monitors both hardware environmental conditions and software performance of multiple machines.
CPU / Memory Boards Processor Processor Processor Processor Memory Memory Memory Memory Boot Bus Boot Bus Data Switch Data Switch Centerplane Board 5-Way Data Switch Fan I/O Bridge (reserved) I/O Bridge EBus Boot PROM I/O Bridge Power Supply EBus Boot Bus Controller TTYA Other I/O Power Supply Disk Controller Ethernet Controller PCI Riser Board DVD Controller PCI Slots Ethernet Controller USB Controller IDPROM HSSDC, USB, & Ethernet I/O FIGURE 6-1 Fan EBus SC I2C Bus Simplifi
Another complicating factor is that different installations have different diagnostic requirements. You may be administering a single computer or a whole data center full of equipment racks. Alternatively, your systems may be deployed remotely— perhaps in areas that are physically inaccessible.
It is important to understand that almost all of the firmware-based diagnostics can be disabled so as to minimize the amount of time it takes the server to start up. In the following discussion, assume that the system is configured to run its firmwarebased tests. Prologue: System Controller Boot As soon as you plug in the Sun Fire V490 server to an electrical outlet, and before you turn on power to the server, the system controller (SC) inside the server begins its self-diagnostic and boot cycle.
POST 8 Kbytes Boot PROM IDPROM 2 Mbytes variables OpenBoot firmware FIGURE 6-2 Boot PROM and IDPROM The extent of these power-on self-tests, and whether they are performed at all, is controlled by configuration variables stored in a separate firmware memory device called the IDPROM. These OpenBoot configuration variables are discussed in “Controlling POST Diagnostics” on page 82.
What POST Diagnostics Do Each POST diagnostic is a low-level test designed to pinpoint faults in a specific hardware component. For example, individual memory tests called address bitwalk and data bitwalk ensure that binary 0s and 1s can be written on each address and data line. During such a test, the POST may display output similar to this: 1:0>Data Bitwalk on Slave 3 1:0> Test Bank 0.
Here is an excerpt of POST output showing another error message.
The dashed lines in FIGURE 6-3 represent boundaries between FRUs. Suppose a POST diagnostic is running in the processor in the left part of the diagram. This diagnostic attempts to initiate a built-in self-test in a PCI device located in the right side of the diagram. If this built-in self-test fails, there could be a fault in the PCI controller, or, less likely, in one of the data paths or components leading to that PCI controller. The POST diagnostic can tell you only that the test failed, but not why.
TABLE 6-2 OpenBoot Configuration Variable OpenBoot Configuration Variables (Continued) Description and Keywords diag-out-console Redirects diagnostic and console messages to the system controller. Default is false. • true—Display diagnostic messages via the SC console. • false—Display diagnostic messages via the serial port ttya or a graphics terminal. diag-script Determines which devices are tested by OpenBoot Diagnostics. Default is normal. • none—No devices are tested.
TABLE 6-2 OpenBoot Configuration Variable OpenBoot Configuration Variables (Continued) Description and Keywords diag-trigger Specifies the class of reset event that causes diagnostic tests to run. This variable can accept single keywords as well as combinations of the first three keywords separated by spaces. For details, see “How to View and Set OpenBoot Configuration Variables” on page 180. Default is power-on-reset and error-reset.
Stage Two: OpenBoot Diagnostics Tests Once POST diagnostics have finished running, POST reports back to the OpenBoot firmware the status of each test it has run. Control then reverts back to the OpenBoot firmware code. OpenBoot firmware code compiles a hierarchical “census” of all devices in the system. This census is called a device tree. Though different for every system configuration, the device tree generally includes both built-in system components and optional PCI bus devices.
In addition, the OpenBoot Diagnostics tests use a special variable called test-args that enables you to customize how the tests operate. By default, test-args is set to contain an empty string. However, you can set test-args to one or more of the reserved keywords, each of which has a different effect on OpenBoot Diagnostics tests. TABLE 6-3 lists the available keywords.
o b d i a g 1 SUNW,qlc@2 2 bbc@1,0 3 ebus@1 4 flashprom@0,0 5 i2c@1,2e 6 i2c@1,30 7 ide@6 8 network@1 9 network@2 10 pmc@1,300700 11 rsc-control@1,3062f8 13 serial@1,400000 14 usb@1,3 12 rtc@1,300070 Commands: test test-all except help what setenv set-default exit diag-passes=1 diag-level=off test-args=subtests FIGURE 6-4 OpenBoot Diagnostics Interactive Test Menu Interactive OpenBoot Diagnostics Commands You run individual OpenBoot Diagnostics tests from the obdiag> prompt by typing: obdiag
Note – Knowing how to construct an appropriate hardware device path requires precise knowledge of the hardware architecture of the Sun Fire V490 system. To customize an individual test, you can use test-args as follows: ok test /usb@1,3:test-args={verbose,debug} This affects only the current test without changing the value of the test-args OpenBoot configuration variable.
Testing /pci@9,700000/ebus@1/rsc-control@1,3062f8 ERROR : DEVICE : SUBTEST : CALLERS : MACHINE : SERIAL# : DATE : CONTR0LS: SC card is not present in system, or SC card is broken. /pci@9,700000/ebus@1/rsc-control@1,3062f8 selftest main Sun Fire V490 705459 11/28/2001 14:46:21 GMT diag-level=min test-args=media,verbose,subtests Error: /pci@9,700000/ebus@1/rsc-control@1,3062f8 selftest failed, return code = 1 Selftest at /pci@9,700000/ebus@1/rsc-control@1,3062f8 (errors=1) ......
Other OpenBoot Commands Beyond the formal firmware-based diagnostic tools, there are a few commands you can invoke from the ok prompt. These OpenBoot commands display information that can help you assess the condition of a Sun Fire V490 server. These include the following commands: ■ ■ ■ ■ ■ .env command printenv command probe-scsi and probe-scsi-all commands probe-ide command show-devs command This section describes the information these commands give you.
The probe-scsi command communicates with all SCSI and FC-AL devices connected to on-board SCSI and FC-AL controllers. The probe-scsi-all command additionally accesses devices connected to any host adapters installed in PCI slots. For any SCSI or FC-AL device that is connected and active, the probe-scsi and probe-scsi-all commands display its loop ID, host adapter, logical unit number, unique World Wide Name (WWN), and a device description that includes type and manufacturer.
probe-ide Command The probe-ide command communicates with all Integrated Drive Electronics (IDE) devices connected to the IDE bus. This is the internal system bus for media devices such as the DVD drive. Caution – If you used the halt command or the Stop-A key sequence to reach the ok prompt, then issuing the probe-ide command can hang the system. The following is sample output from the probe-ide command.
Stage Three: The Operating System If a system passes OpenBoot Diagnostics tests, it normally attempts to boot its multiuser operating system. For most Sun systems, this means the Solaris OS. Once the server is running in multiuser mode, you have recourse to software-based diagnostic tools, like SunVTS and Sun Management Center. These tools can help you with more advanced monitoring, exercising, and fault isolating capabilities.
prtconf Command The prtconf command displays the Solaris device tree. This tree includes all the devices probed by OpenBoot firmware, as well as additional devices, like individual disks, that only the operating system software “knows” about. The output of prtconf also includes the total amount of system memory. CODE EXAMPLE 6-7 shows an excerpt of prtconf output (edited to save space).
The display format used by the prtdiag command can vary depending on what version of the Solaris OS is running on your system. Following is an excerpt of some of the output produced by prtdiag on a healthy Sun Fire V490 system running Solaris 8, Update 7. System Configuration: Sun Microsystems System clock frequency: 150 MHz Memory size: 4096 Megabytes sun4u Sun Fire V490 ========================= CPUs =============================================== Brd --A A CPU --0 2 Run MHz --900 900 E$ MB ---8.
In addition to that information, prtdiag with the verbose option (-v) also reports on front panel status, disk status, fan status, power supplies, hardware revisions, and system temperatures. System Temperatures (Celsius): ------------------------------Device Temperature Status --------------------------------------CPU0 59 OK CPU2 64 OK DBP0 22 OK CODE EXAMPLE 6-9 prtdiag Verbose Output In the event of an overtemperature condition, prtdiag reports an error in the Status column.
The prtfru command can display this hierarchical list, as well as data contained in the serial electrically-erasable programmable read-only memory (SEEPROM) devices located on many FRUs. CODE EXAMPLE 6-12 shows an excerpt of a hierarchical list of FRUs generated by the prtfru command with the -l option.
■ ■ ■ Power distribution board Power supplies System controller card psrinfo Command The psrinfo command displays the date and time each processor came online. With the verbose (-v) option, the command displays additional information about the processors, including their clock speed. The following is sample output from the psrinfo command with the -v option. Status of processor 0 as of: 04/11/03 12:03:45 Processor has been on-line since 04/11/03 10:53:03.
When used with the -p option, this command displays installed patches. CODE EXAMPLE 6-16 shows a partial sample output from the showrev command with the -p option.
About Isolating Faults in the System Each of the tools available for fault isolation discloses faults in different field– replaceable units (FRUs). The row headings along the left of TABLE 6-5 list the FRUs in a Sun Fire V490 system. The available diagnostic tools are shown in column headings across the top. A check mark (✔) in this table indicates that a fault in a particular FRU can be isolated by a particular diagnostic.
In addition to the FRUs listed in TABLE 6-5, there are several minor replaceable system components—mostly cables—that cannot directly be isolated by any system diagnostic. For the most part, you determine when these components are faulty by eliminating other possibilities. These FRUs are listed in TABLE 6-6.
Monitoring the System Using Remote System Control Software Sun Remote System Controller (RSC) software, working in conjunction with the system controller (SC) card, enables you to monitor and control your server over a serial port or a network. RSC software provides both graphical and command-line interfaces for remotely administering geographically distributed or physically inaccessible machines.
For instructions on using RSC software to monitor a Sun Fire V490 system, see “How to Monitor the System Using the System Controller and RSC Software” on page 190. Monitoring the System Using Sun Management Center Sun Management Center software provides enterprise-wide monitoring of Sun servers and workstations, including their subsystems, components, and peripheral devices.
The server component maintains a large database of status information for a wide range of Sun platforms. This database is updated frequently, and includes information about 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 monitor components present the collected data to you in a standard format.
Who Should Use Sun Management Center? Sun Management Center software is geared primarily toward system administrators who have large data centers to monitor or other installations that have many computer platforms to monitor. If you administer a more modest installation, you need to weigh Sun Management Center software’s benefits against the requirement of maintaining a significant database (typically over 700 Mbytes) of system status information.
TABLE 6-9 FRU Coverage of System Exercising Tools SunVTS Hardware Diagnostic Suite CPU/Memory Boards ✔ ✔ IDPROM ✔ DIMMs ✔ ✔ DVD Drive ✔ ✔ FC-AL Disk Drive ✔ ✔ Centerplane ✔ ✔ SC Card ✔ PCI Riser ✔ FC-AL Disk Backplane ✔ ✔ Exercising the System Using SunVTS Software SunVTS software validation test suite performs system and subsystem stress testing. You can view and control a SunVTS session over a network.
■ Exclusive mode – SunVTS software exercises only the specific subsystems you choose. Selected tests are run one at a time. A few tests are only available in this mode, including: l1dcachetest, l2cachetest, l2sramtest, mpconstest, mptest, qlctest, ramtest, ssptest, and systest. ■ Online mode – SunVTS software exercises only the specific subsystems you choose. Selected tests are run one at a time until one complete system pass is achieved.
SunVTS Software and Security During SunVTS software installation, you must choose between Basic or Sun Enterprise Authentication Mechanism (SEAM) security. Basic security uses a local security file in the SunVTS installation directory to limit the users, groups, and hosts permitted to use SunVTS software. SEAM security is based on Kerberos—the standard network authentication protocol—and provides secure user authentication, data integrity, and privacy for transactions over networks.
Requirements for Using Hardware Diagnostic Suite Since it is a part of Sun Management Center, you can only run Hardware Diagnostic Suite if you have set up your data center to run Sun Management Center. This means you have to dedicate a master server to run the Sun Management Center server software that supports Sun Management Center software’s database of platform status information. In addition, you must install and set up Sun Management Center agent software on the systems to be monitored.
TABLE 6-10 OpenBoot Diagnostics Menu Tests (Continued) Test Name What It Does FRU(s) Tested ide@6 Tests the on-board IDE controller and IDE bus subsystem that controls the DVD drive PCI riser board, DVD drive network@1 Tests the on-board Ethernet logic, running internal loopback tests.
TABLE 6-11 OpenBoot Diagnostics Test Menu Commands (Continued) Command Description except #,# Tests all devices in the OpenBoot Diagnostics test menu except those identified by the specified menu entry numbers versions Displays the version, last modified date, and manufacturer of each self-test in the OpenBoot Diagnostics test menu and library what #,# Displays selected properties of the devices identified by menu entry numbers.
TABLE 6-12 112 Sun Fire V490 I2C Bus Devices (Continued) Address Associated FRU fru@1,a0 processor 1, DIMM 0 fru@1,a2 processor 1, DIMM 1 fru@1,a4 processor 1, DIMM 2 fru@1,a6 processor 1, DIMM 3 fru@1,a8 processor 1, DIMM 4 fru@1,aa processor 1, DIMM 5 fru@1,ac processor 1, DIMM 6 fru@1,ae processor 1, DIMM 7 fru@2,a0 processor 2, DIMM 0 fru@2,a2 processor 2, DIMM 1 fru@2,a4 processor 2, DIMM 2 fru@2,a6 processor 2, DIMM 3 fru@2,a8 processor 2, DIMM 4 fru@2,aa processor 2, D
TABLE 6-12 Sun Fire V490 I2C Bus Devices (Continued) Address Associated FRU What the Device Does fru@4,aa PCI riser Provides PCI riser board configuration information fru@5,10 Centerplane Provides communication and control for I2C subsystem fru@5,14 RSC card Provides communication and control for the RSC card temperature@5,30 CPU/Mem board A Monitors processor 0 temperature temperature@5,32 CPU/Mem board B Monitors processor 1 temperature temperature@5,34 CPU/Mem board A Monitors proce
Reference for Terms in Diagnostic Output The status and error messages displayed by POST diagnostics and OpenBoot Diagnostics tests occasionally include acronyms or abbreviations for hardware subcomponents. TABLE 6-13 is included to assist you in decoding this terminology and associating the terms with specific FRUs, where appropriate.
TABLE 6-13 Abbreviations or Acronyms in Diagnostic Output (Continued) Term Description Associated FRU(s) NVRAM IDPROM IDPROM, located on PCI riser board OBP Refers to OpenBoot firmware N/A PDB Power Distribution Board Power distribution board PMC Power Management Controller PCI riser board POST Power-On Self-Test N/A RIO Multifunction integrated circuit bridging the PCI bus with EBus and USB PCI riser board RTC Real-Time Clock PCI riser board RX Receive – Communication protocol C
116 Sun Fire V490 Server Administration Guide • August 2004
PART III Instructions The six chapters within this part of the Sun Fire V490 Server Administration Guide use illustrated instructions on how to set up various components within your system, configure your system, and diagnose problems. Instructions within this guide are primarily to be used by experienced system administrators who are familiar with the Solaris OS and its commands.
CHAPTER 7 Configuring Console Access This chapter includes instructions on how to configure and access the system console from different physical devices.
How to Avoid Electrostatic Discharge Qualified service technicians should use the following procedure to prevent static damage whenever they access any of the internal components of the system. Caution – Do not attempt to access any internal components unless you are a qualified service technician. Detailed service instructions can be found in the Sun Fire V490 Server Parts Installation and Removal Guide, which is included on the Sun Fire V490 Documentation CD.
2. Use an antistatic mat or similar surface. When performing any installation or service procedure, place static-sensitive parts, such as boards, cards, and disk drives, on an antistatic surface.
What Next To power on the system, complete this task: ■ “How to Power On the System” on page 122 How to Power On the System Before You Begin Do not use this power-on procedure if you have just added any new internal option or external storage device, or if you have removed a storage device without replacing it. To power on the system under those circumstances, you must initiate a reconfiguration boot. For those instructions, see “How to Initiate a Reconfiguration Boot” on page 138.
Media door 4. Insert the system key into the system control switch and turn the system control switch to the Normal position. See “System Control Switch” on page 15 for information about each system control switch setting. Normal position Power button 5. Press the Power button that is below the system control switch to power on the system.
6. Turn the system control switch to the Locked position. This prevents anyone from accidentally powering off the system. Locked position 7. Remove the system key from the system control switch and keep it in a secure place.
How to Power Off the System Before You Begin Applications running on the Solaris OS can be adversely affected by a poorly executed system shutdown. Make sure that you have gracefully shut down any applications before powering off the system. You can also use Solaris commands, the OpenBoot firmware power-off command, or RSC software to power off the system. For details, see: ■ ■ “How to Get to the ok Prompt” on page 126 Sun Remote System Controller (RSC) User’s Guide What to Do 1.
Caution – Be sure to turn the system control switch to the Forced Off position before handling any internal components. Otherwise, it is possible for an operator at a system controller (SC) console to restart the system while you are working inside it. The Forced Off position is the only system control switch position that prevents an SC console from restarting the system. 7. Remove the system key from the system control switch and keep it in a secure place.
If at all possible, back up system data before starting this procedure. Also halt all applications and warn users of the impending loss of service. For information about the appropriate backup and shutdown procedures, see Solaris system administration documentation. What to Do 1. Decide which method you need to use to reach the ok prompt. See “About the ok Prompt” on page 49 for details. 2. Refer to TABLE 7-1 for instructions.
■ Install the server in the rack, following instructions in the Sun Fire V490 Server Setup and Rackmounting Guide. What to Do 1. Locate the RJ-45 twisted-pair Ethernet (TPE) connector for the appropriate Ethernet interface—the top connector or the bottom connector. See “Locating Back Panel Features” on page 16. For a PCI Ethernet adapter card, see the documentation supplied with the card. 2. Connect a Category-5 unshielded twisted-pair (UTP) cable to the appropriate RJ-45 connector.
How to Access the System Console via tip Connection Before You Begin The following procedure assumes you are connecting to the serial port (ttya) of the Sun Fire V490 system using a tip connection from serial port B (ttyb) of another Sun server, and that the other Sun server has its own local graphics terminal. What to Do 1. Decide whether you need to reset OpenBoot configuration variables on the Sun Fire V490 system.
Note – There are many other OpenBoot configuration variables, and although these do not affect which hardware device is used as the system console, some of them affect what diagnostic tests the system runs and what messages the system console displays. For details, see “Controlling POST Diagnostics” on page 82. 3. Connect the RJ-45 serial cable and adapter. The cable and adapter connect the Sun server’s ttyb serial port to the Sun Fire V490 system’s built-in ttya serial port.
How to Modify the /etc/remote File You may need to perform this procedure to access the system console via a tip connection from a Sun server running an older version of the Solaris OS software. You may also need to perform this procedure if the /etc/remote file on the Sun server has been altered and no longer contains an appropriate hardwire entry.
■ If the number displayed by the uname -r command is less than 5.0: Check the /etc/remote file and add the entry shown in CODE EXAMPLE 7-2, if it does not already exist. hardwire:\ :dv=/dev/ttyb:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D: CODE EXAMPLE 7-2 Entry for hardwire in /etc/remote (Older System Software) Note – If you intend to use the Sun server’s serial port A rather than serial port B, edit this entry by replacing /dev/ttyb with /dev/ttya. What Next The /etc/remote file is now properly configured.
2. Type: # eeprom ttya-mode 3. Look for the following output: ttya-mode = 9600,8,n,1,- This line indicates that the Sun Fire V490 server’s serial port is configured for: ■ ■ ■ ■ ■ 9600 baud 8 bits No parity 1 stop bit No handshake protocol What Next For more information about serial port settings, see the eeprom man page.
For detailed information about system console options, see “About Communicating With the System” on page 69. What to Do 1. Attach one end of the serial cable to the alphanumeric terminal’s serial port. Use an RJ-45 null modem serial cable or an RJ-45 serial cable and null modem adapter. Plug this into the terminal’s serial port connector. 2. Attach the opposite end of the serial cable to the Sun Fire V490 system. Plug the cable into the system’s built-in serial port (ttya) connector. 3.
Note – There are many other OpenBoot configuration variables, and although these do not affect which hardware device is used as the system console, some of them affect what diagnostic tests the system runs and what messages the system console displays. For details, see “Controlling POST Diagnostics” on page 82. 7.
To install a local graphics terminal, you must have: ■ A supported PCI-based graphics frame buffer card and software driver ■ ■ An 8-Bit Color Graphics PCI adapter frame buffer card (Sun part number X3660A is currently supported) An 8/24-Bit Color Graphics PCI adapter frame buffer card (Sun part number X3768A is currently supported) ■ A monitor with appropriate resolution ■ A Sun-compatible USB keyboard (Sun USB Type–6 keyboard) ■ A Sun-compatible USB mouse (Sun USB mouse) and mouse pad (if necessa
5. Connect the mouse USB cable to any USB port on the back panel. 6. Set OpenBoot configuration variables appropriately.
Note – There are many other OpenBoot configuration variables, and although these do not affect which hardware device is used as the system console, some of them affect what diagnostic tests the system runs and what messages the system console displays. For details, see “Controlling POST Diagnostics” on page 82. 7.
Before You Begin Caution – Before you power on the system, make sure that the system doors and all panels are properly installed. To issue software commands, you need to set up a system ASCII terminal, a local graphics terminal, or a tip connection to the Sun Fire V490 system.
a. Wait until the system has completed initializing memory. During initialization, you see the message: Initializing memory b. Watch carefully, as you will need to act quickly. Once the process is complete, the Initializing memory message is erased and the system displays a line similar to: Boot device: disk2 File and args: c. At this point, abort the boot process as promptly as possible. To do this, use one of the following methods: ■ ■ ■ Hold down the Stop (or L1) key and press A on your keyboard.
Reference for System Console OpenBoot Variable Settings Certain OpenBoot configuration variables control from where system console input is taken and to where its output is directed. The table below shows how to set these variables in order to use ttya, the system controller, or a local graphics terminal as the system console.
142 Sun Fire V490 Server Administration Guide • August 2004
CHAPTER 8 Configuring Network Interfaces and the Boot Device This chapter provides information and instructions that are required to plan and to configure the supported network interfaces.
How to Configure the Primary Network Interface Before You Begin You must perform this task: ■ Complete the installation steps in Chapter 1. For background information, see: ■ “About the Network Interfaces” on page 47 If you are using a PCI network interface card, see the documentation supplied with the card. What to Do 1. Choose a network port, using the following table as a guide.
4. Determine the unique Internet Protocol (IP) address of the network interface and make a note of it. You need to furnish the address in a later step. An IP address must be assigned by the network administrator. Each network device or interface must have a unique IP address. 5. Resume the installation of the system. Return to Chapter 1.
Note – The Sun Fire V490 system conforms to the Ethernet 10/100BASE-T 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 establishing a connection between this system and your hub, verify that the Ethernet hub also has the link test function enabled. Consult the manual provided with your hub for more information about the link integrity test function.
What to Do 1. Choose a network host name for each new interface. The host name must be unique within the network. It can consist only of alphanumeric characters and the dash (-). Do not use a dot in the host name. Do not begin the name with a number or a special character. The name must not be longer than 30 characters. Usually an interface host name is based on the machine host name. For example, if the machine is assigned the host name sunrise, the added network interface could be named sunrise-1.
5. Edit the /etc/hostname file(s) created in Step 4 to add the host name(s) determined in Step 1. Following is an example of the /etc/hostname files required for a system called sunrise, which has two on-board Sun GigaSwift Ethernet interfaces (ce0 and ce1) and a PCI Ethernet adapter card (ce2). A network connected to the on-board ce0 and ce1 interfaces will know the system as sunrise and sunrise-1, while networks connected to the PCI-based ce2 interface will know the system as sunrise-2.
What Next After completing this procedure, any new network interfaces are ready for operation. However, in order for other network devices to communicate with the system through the new interface, the IP address and host name for each new interface must be entered into the namespace on the network name server.
Specifically, you must set up a system console and power on the system. See: ■ “How to Set Up an Alphanumeric Terminal as the System Console” on page 133 ■ “How to Configure a Local Graphics Terminal as the System Console” on page 135 ■ “How to Power On the System” on page 122 If you want to boot from a network, you must also connect the network interface to the network and configure the network interfaces.
If you want to specify a network interface other than an on-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 the system devices and displays the full path name of each PCI device. What Next For more information about using the OpenBoot firmware, see: ■ OpenBoot 4.x Command Reference Manual, included with the Solaris Software Supplement CD that ships with Solaris software.
152 Sun Fire V490 Server Administration Guide • August 2004
CHAPTER 9 Configuring System Firmware This chapter describes OpenBoot firmware commands and configuration variables available for configuring the following aspects of Sun Fire V490 system behavior: ■ ■ OpenBoot environmental monitoring Automatic system recovery (ASR) In addition, this chapter provides information about keyboard commands and alternative methods for performing OpenBoot emergency procedures.
How to Enable OpenBoot Environmental Monitoring Before You Begin For background information about the OpenBoot environmental monitor, see: ■ “About OpenBoot Environmental Monitoring” on page 52 What to Do ● To enable OpenBoot environmental monitoring, type env-on at the ok prompt.
What to Do ● To disable OpenBoot environmental monitoring, type env-off at the ok prompt: ok env-off Environmental monitor is OFF ok How to Obtain OpenBoot Environmental Status Information Before You Begin For background information about environmental status information, see: ■ “OpenBoot Environmental Status Information” on page 53 What to Do ● To obtain OpenBoot environmental status information, type .env at the ok prompt: ok .
How to Enable the Watchdog Mechanism and Its Options Before You Begin For background information about the hardware watchdog mechanism and related externally initiated reset (XIR) functionality, see: ■ “Hardware Watchdog Mechanism and XIR” on page 23 What to Do 1. Edit the /etc/system file to include the following entry. set watchdog_enable = 1 2. Choose the desired system recovery behavior. The hardware watchdog mechanism can automatically reboot the system in case the system hangs.
3. Restart the system to effect the changes. Type: # reboot What Next If you choose to have the system generate an automated crash dump file, then, in the event the operating system hangs, that file appears in the /var/crash/ directory, under a subdirectory named after your system. For more information, see the documentation accompanying your Solaris software release. How to Enable ASR The automatic system recovery (ASR) feature is activated by default.
The system permanently stores the parameter changes and boots automatically if the OpenBoot variable auto-boot? is set to true (its default value). What Next To disable ASR, complete this task: ■ “How to Disable ASR” on page 158 How to Disable ASR After you disable the automatic system recovery (ASR) feature, it is not activated again until you enable it at the system ok prompt. What to Do 1. At the system ok prompt, type: ok setenv auto-boot-on-error? false 2.
What to Do 1. At the system ok prompt, type: ok .asr In the .asr command output, any devices marked disabled have been manually deconfigured using the asr-disable command. The .asr command also lists devices that have failed firmware diagnostics and have been automatically deconfigured by the OpenBoot ASR feature. 2. Display components that have failed POST diagnostics. Type: ok show-post-results 3. Display components that have failed OpenBoot diagnostics tests.
What to Do 1. Establish a system controller session. For instructions, see the Sun Remote System Controller (RSC) User’s Guide, which is included on the Sun Fire V490 Documentation CD. 2. At the system ok prompt, type: ok setenv diag-out-console true ok setenv input-device rsc-console ok setenv output-device rsc-console 3.
How to Restore the Local System Console Perform this procedure if your system is configured to use the system controller (SC) as the system console and you need to redirect the system console to a local graphics terminal, alphanumeric terminal, or an established tip connection. For more information about RSC software, see: ■ ■ “About the System Controller (SC) Card” on page 33 Sun Remote System Controller (RSC) User’s Guide What to Do 1. Set the input and output device. Do one of the following.
What Next You can now issue commands and view system messages on the local console. How to Deconfigure a Device Manually Before You Begin To support the ability to boot even when nonessential components fail, the OpenBoot firmware provides the asr-disable command, which lets you manually deconfigure system devices. This command “marks” a specified device as disabled, by creating an appropriate “status” property in the corresponding device tree node.
2. To effect the changes immediately, type: ok reset-all Note – To immediately effect the changes, you can also power cycle the system using the front panel Power button How to Reconfigure a Device Manually Before You Begin You can use the OpenBoot asr-enable command to reconfigure any device that you previously deconfigured with asr-disable. For background information, see ■ “About Manually Configuring Devices” on page 59 What to Do 1.
Note – To reconfigure a processor, you must power cycle the system. The reset-all command will not suffice to bring the processor back online. How to Implement Stop-N Functionality Before You Begin This procedure implements Stop-N functionality on Sun Fire V490 systems, temporarily resetting OpenBoot configuration variables to their default settings. This procedure is most useful if you have not configured your Sun Fire V490 system to run diagnostic tests.
3. Press the front panel Power button twice, with no more than a short, one-second delay in between presses. A screen similar to the following is displayed to indicate that you have temporarily reset OpenBoot configuration variables to their default values: Setting NVRAM parameters to default values. Probing I/O buses Sun Fire V490, No Keyboard Copyright 1998-2004 Sun Microsystems, Inc. All rights reserved. OpenBoot x.x, xxxx MB memory installed, Serial #xxxxxxxx.
To correct such problems, you must either manually change individual OpenBoot configuration variables using the setenv command, or else type set-defaults to permanently restore the default settings for all OpenBoot configuration variables.
CHAPTER 10 Isolating Failed Parts The most important use of diagnostic tools is to isolate a failed hardware component so that a qualified service technician can quickly remove and replace it. Because servers are complex machines with many failure modes, there is no single diagnostic tool that can isolate all hardware faults under all conditions. However, Sun provides a variety of tools that can help you discern what component needs replacing.
Note – Many of the procedures in this chapter assume that you are familiar with the OpenBoot firmware and that you know how to enter the OpenBoot environment. For background information, see “About the ok Prompt” on page 49. For instructions, see “How to Get to the ok Prompt” on page 126. Caution – Do not attempt to access any internal components unless you are a qualified service technician.
■ As root, type: # /usr/sbin/locator -n ■ At the SC command-line interface, type: rsc> setlocator on ■ From the RSC software’s main GUI screen, click the representation of the Locator LED. See the illustration under Step 5 in “How to Monitor the System Using the System Controller and RSC Software. With each click, the LED will change state from off to on, or vice versa. 2. Turn the Locator LED off.
How to Put the Server in Service Mode Before You Begin In normal mode, firmware-based diagnostic tests can be configured (and even disabled) to expedite the server’s startup process. If you have set OpenBoot configuration variables to bypass diagnostic tests, you can always reset those variables to their default values to run tests. Alternatively, putting the server into service mode according to the following procedure ensures that POST and OpenBoot Diagnostics tests do run during startup.
What Next Should you want to restore the system to normal mode in order to control the depth of diagnostic coverage, the tests run, and the verbosity of the output, see: ■ “How to Put the Server in Normal Mode” on page 171. How to Put the Server in Normal Mode Before You Begin If you have set the server to run in service mode, you can follow this procedure to return the system to normal mode. Putting the system in normal mode allows you control over diagnostic testing.
What Next For detailed descriptions of service and normal modes, see: ■ OpenBoot PROM Enhancements for Diagnostic Operation This document is included on the Sun Fire V490 Documentation CD. How to Isolate Faults Using LEDs While not a deep, formal diagnostic tool, LEDs located on the chassis and on selected system components can serve as front-line indicators of a limited set of hardware failures. Before You Begin You can view LED status by direct inspection of the system’s front or back panels.
What to Do 1. Check the system LEDs. There is a group of three LEDs located near the top left corner of the front panel and duplicated on the back panel. Their status can tell you the following. LED Indicates Action Locator (left) A system administrator can turn this on to flag a system that needs attention. Identify the system. Fault (middle) If lit, hardware or software has detected a problem with the system. Check other LEDs or run diagnostics to determine the problem source.
4. Check the disk drive LEDs. There are two sets of three LEDs, one for each disk drive. These are located behind the media door, just to the left of each disk drive. Their status can tell you the following. LED Indicates Action OK-to-Remove (top) If lit, disk can safely be removed. Remove disk as needed. Fault (middle) If lit, there is a problem with the disk. Perform software commands to take the disk offline. See the Sun Fire V490 Server Parts Installation and Removal Guide.
How to Isolate Faults Using POST Diagnostics This section explains how to run power-on self-test (POST) diagnostics to isolate faults in a Sun Fire V490 server. For background information about POST diagnostics and the boot process, see Chapter 6. Before You Begin You must ensure that the system is configured to run diagnostic tests.
3. Start POST diagnostics. Type: ok post The system runs the POST diagnostics and displays status and error messages via either the local serial terminal (ttya) or the redirected (system controller) system console. 4. Examine the POST output. Each POST error message includes a “best guess” as to which field-replaceable unit (FRU) was the source of failure. In some cases, there may be more than one possible source, and these are listed in order of decreasing likelihood.
How to Isolate Faults Using Interactive OpenBoot Diagnostics Tests Before You Begin Because OpenBoot Diagnostics tests require access to some of the same hardware resources used by the operating system, they cannot be operated reliably after an operating system halt or Stop-A key sequence. You need to reset the system before running OpenBoot Diagnostics tests, and then reset the system again after testing. Instructions for doing this follow. This procedure assumes you have established a system console.
5. Type the appropriate command and numbers for the tests you want to run. For example, to run all available OpenBoot Diagnostics tests, type: obdiag> test-all To run a particular test, type: obdiag> test # where # represents the number of the desired test. For a list of OpenBoot Diagnostics test commands, see “Interactive OpenBoot Diagnostics Commands” on page 87. The numbered menu of tests is shown in FIGURE 6-4. 6. When you are done running OpenBoot Diagnostics tests, exit the test menu.
How to View Diagnostic Test Results After the Fact Summaries of the results from the most recent power-on self-test (POST) and OpenBoot Diagnostics tests are saved across power cycles. Before You Begin You must set up a system console. See: ■ “About Communicating With the System” on page 69 Then halt the server to reach the ok prompt.
How to View and Set OpenBoot Configuration Variables Switches and diagnostic configuration variables stored by the system firmware determine how and when power-on self-test (POST) diagnostics and OpenBoot Diagnostics tests are performed. This section explains how to access and modify OpenBoot configuration variables. For a list of important OpenBoot configuration variables, see TABLE 6-2. Before You Begin Halt the server to reach the ok prompt.
● To set OpenBoot configuration variables that accept multiple keywords, separate keywords with a space: ok setenv post-trigger power-on-reset error-reset post-trigger = power-on-reset error-reset Note – The test-args variable operates differently from other OpenBoot configuration variables. It requires a single argument consisting of a commaseparated list of keywords. For details, see “Controlling OpenBoot Diagnostics Tests” on page 85.
Fault LED lit ? yes no Replace part System boots ? no yes Consider running system exerciser Run POST no POST failure ? Replace part Run OBDiag no OBDiag failure ? yes yes yes Software or disk problem FIGURE 10-1 Check disks Disk failure ? no Software problem Choosing a Tool to Isolate Hardware Faults 4. Do you intend to run the tests remotely? Both Sun Management Center and RSC software enable you to run tests from a remote computer.
5. Will the tool test the suspected source(s) of the problem? Perhaps you already have some idea of what the problem is. If so, you want to use a diagnostic tool capable of testing the suspected problem sources. ■ TABLE 6-5 tells you which replaceable hardware parts can be isolated by each fault isolating tool. ■ TABLE 6-9 tells you which replaceable hardware parts are covered by each system exercising tool. 6.
184 Sun Fire V490 Server Administration Guide • August 2004
CHAPTER 11 Monitoring the System When something goes wrong with the system, diagnostic tools can help you determine what caused the problem. Indeed, this is the principal use of most diagnostic tools. However, this approach is inherently reactive. It means waiting until a component fails outright. Some diagnostic tools allow you to be more proactive by monitoring the system while it is still “healthy.
Note – Many of the procedures in this chapter assume that you are familiar with the OpenBoot firmware and that you know how to enter the OpenBoot environment. For background information, see “About the ok Prompt” on page 49. For instructions, see “How to Get to the ok Prompt” on page 126. How to Monitor the System Using Sun Management Center Software Sun Management Center software is a flexible product with many features and options.
Note – Sun Management Center software provides both standalone and browserbased console interfaces. This procedure assumes you are using the standalone Java technology-based console. The web-browser console interface, which differs somewhat in design and capabilities, is covered in the Sun Management Center User’s Guide. What to Do 1. On your Sun Fire V490 system, install Sun Management Center agent software. For instructions, see the Sun Management Center Supplement for Workgroup Servers. 2.
Photo-realistic view (front) Highlighted component (disk drive) Information about disk drive b. Select “Logical View: system” from the Views pull-down menu. The logical view lets you browse a hierarchy of system components, arranged as a tree of nested folders. Logical view V490 Selected component As you highlight a hardware component, status and manufacturing information about that component appears in a property table to the right.
7. Monitor the Sun Fire V490 system using Config-Reader module data property tables. To access this information: a. Click the Browser tab. b. Click the Hardware icon in the hierarchy view. Browser tab Hardware icon Config-Reader icon Data property table icons c. Click the Config-Reader icon in the hierarchy view. Under the Config-Reader icon you can find data property table icons for many hardware components. d. Click a data property table icon to see status information for that hardware component.
What Next There is much more to Sun Management Center software than what is detailed in this manual. In particular, you may be interested in setting alarms and administering security. These topics and many others are covered in the Sun Management Center User’s Guide, as well as the other documents accompanying the Sun Management Center software.
What to Do 1. As root on the Sun Fire V490 server, run the RSC configuration script. Type: # /usr/platform/‘uname -i‘/rsc/rsc-config The configuration script runs, prompting you to choose options and to provide information. 2. Follow the configuration script prompts. For the purposes of this procedure, you can accept most of the default values. However, you need to pay attention to specific prompts as described below. a.
f. Near the end of the script, you need to provide an RSC password: Setting User Password Now ... Password: Re-enter Password: The RSC firmware on the Sun Fire V490 system is configured. Perform the following steps on the monitoring system. 3. From the monitoring Sun computer or PC, start the RSC GUI. Do one of the following.
4. Reply to the prompts given at the login screen. The main screen of the GUI appears. 5. Note the main screen’s features. The left side of the main screen provides help text and navigation controls. The right side shows a representation of the Sun Fire V490 server’s front panel and system control switch.
a. Turn the Sun Fire V490 server’s power off (or on). Click the Power button on the front panel representation. A dialog box appears asking you to confirm the action. Proceeding will actually turn system power off (or on). Power button b. Examine status tables for the Sun Fire V490 server’s disks and fans. Click the appropriate LEDs. A table appears giving you the status of the components in question. Fan tray LEDs Fan tray status table c. Turn the Sun Fire V490 server’s Locator LED on and off.
7. Check system temperatures and other environmental data. To do this: a. Find the navigation panel at the left side of the RSC GUI. b. Click the Show Environmental Status item under Server Status and Control. The Environmental Status window appears. Check marks By default, the Temperatures tab is selected and temperature data from specific chassis locations are graphed. The green check marks on each tab let you see at a glance that no problems are found with these subsystems.
c. Click the other Environmental Status window tabs to see additional data. 8. Access the Sun Fire V490 server’s system console from RSC software. To do this: a. Find the navigation panel at the left side of the RSC GUI. b. Click the Open Console item under Server Status and Control. A Console window appears. c. From the Console window, press the Return key to reach the system console output.
If you want to change RSC configuration, run the configuration script again as shown in Step 1 of this procedure. For information about RSC configuration, user accounts, and alerts, see: ■ Sun Remote System Controller (RSC) User’s Guide This document is included on the Sun Fire V490 Documentation CD. How to Use Solaris System Information Commands This section explains how to run Solaris system information commands on a Sun Fire V490 server.
TABLE 11-1 Using Solaris Information Display Commands (Continued) Command What It Displays What to Type Notes prtfru FRU hierarchy and SEEPROM memory contents /usr/sbin/prtfru Use the -l option to display hierarchy. Use the -c option to display SEEPROM data. psrinfo Date and time each processor came online; processor clock speed /usr/sbin/psrinfo Use the -v option to obtain clock speed and other data.
3. Type the appropriate command at a console prompt. See TABLE 11-2. TABLE 11-2 Using OpenBoot Information Commands Command to Type What It Displays .
200 Sun Fire V490 Server Administration Guide • August 2004
CHAPTER 12 Exercising the System Sometimes a server exhibits a problem that cannot be isolated definitively to a particular hardware or software component. In such cases, it may be useful to run a diagnostic utility that stresses the system by continuously running a comprehensive battery of tests.
How to Exercise the System Using SunVTS Software Before You Begin The Solaris operating system must be running. You also need to make sure that SunVTS validation test software is installed on your system. See: ■ “How to Check Whether SunVTS Software Is Installed” on page 206 SunVTS software requires that you use one of two security schemes, and these must be properly configured in order for you to perform this procedure.
What to Do 1. Log in as superuser to a system with a graphics display. The display system should be one with a frame buffer and monitor capable of displaying bitmapped graphics such as those produced by the SunVTS GUI. 2. Enable remote display. On the display system, type: # /usr/openwin/bin/xhost + test-system where test-system is the name of the Sun Fire V490 server being tested. 3. Remotely log in to the Sun Fire V490 server as superuser. Use a command such as rlogin or telnet. 4. Start SunVTS software.
Log button Start and Stop buttons Test selection area Mode selection area Test messages area 5. Expand the test lists to see the individual tests. The interface’s test selection area lists tests in categories, such as “Network,” as shown below. To expand a category, click the + icon to the left of the category name.
6. (Optional) Select the tests you want to run. Certain tests are enabled by default, and you can choose to accept these. Alternatively, you can enable and disable individual tests or blocks of tests by clicking the checkbox next to the test name or test category name. Tests are enabled when checked, and disabled when not checked. TABLE 12-1 lists tests that are especially useful to run on a Sun Fire V490 server.
8. Start testing. Click the Start button, located at the top left of the SunVTS window, to begin running the tests you enabled. Status and error messages appear in the Test Messages area located across the bottom of the window. You can stop testing at any time by clicking the Stop button. What Next During testing, SunVTS software logs all status and error messages. To view these, click the Log button or select Log Files from the Reports menu.
■ “About Communicating With the System” on page 69 What to Do 1. Check for the presence of SunVTS packages. Type: % pkginfo -l SUNWvts SUNWvtsx SUNWvtsmn ■ If SunVTS software is loaded, information about the packages is displayed. ■ If SunVTS software is not loaded, you see an error message for each missing package. ERROR: information for "SUNWvts" was not found ERROR: information for "SUNWvtsx" was not found ... The pertinent packages are as follows.
SunVTS 5.1 software requires additional packages that may not be installed with Solaris 8 software. To find out, type the following: % pkginfo -l SUNWlxml SUNWlxmlx SUNWzlib SUNWzlibx This tests for the presence of the following packages. Package Description SUNXlxml XML library (32-bit) SUNWlxmlx XML library (64-bit) SUNWzlib Zip compression library (32-bit) SUNWzlibx Zip compression library (64-bit) Notes Required by SunVTS 5.1 Needed by XML libraries 3.
APPENDIX A Connector Pinouts This appendix gives you reference information about the system’s back panel ports and pin assignments.
Serial Port Connector The serial port connector is an RJ-45 connector that can be accessed from the back panel.
USB Connector Two Universal Serial Bus (USB) connectors are located on the centerplane and can be accessed from the back panel.
Twisted-Pair Ethernet Connector The twisted-pair Ethernet (TPE) connector is an RJ-45 connector located on the system centerplane and can be accessed from the back panel. The Ethernet interface operates at 10 Mbps, 100 Mbps, and 1000 Mbps.
SC Ethernet Connector The System Controller (SC) Ethernet connector is an RJ-45 connector located on the SC card and can be accessed from the back panel.
SC Serial Connector The System Controller (SC) serial connector is an RJ-45 connector located on the SC card and can be accessed from the back panel.
FC-AL Port HSSDC Connector The Fibre Channel-Arbitrated Loop port high-speed serial data connector is located on the centerplane and can be accessed from the back panel.
216 Sun Fire V490 Server Administration Guide • August 2004
APPENDIX B System Specifications This appendix provides the following specifications for the Sun Fire V490 Server server: ■ ■ ■ ■ ■ “Physical Specifications” on page 217 “Electrical Specifications” on page 218 “Environmental Specifications” on page 219 “Agency Compliance Specifications” on page 220 “Clearance and Service Access Specifications” on page 220 Physical Specifications The dimensions and weight of the system are as follows. Measurement U.S Metric Height 8.75 in 222 mm Width 17.
Electrical Specifications The following table provides the electrical specifications for the system. Note – All electrical specifications apply to a fully configured system.
Environmental Specifications The operating and non-operating environmental specifications for the system are as follows. Parameter Value Operating Temperature 5˚ C to 35˚C (41˚F to 95˚F)—IEC 60068-2-1&2 Humidity 20% to 80% RH noncondensing; 27˚C (81˚F) wet bulb— IEC 60068-2-3&56 Altitude 0 to 3000 meters (0 to 10,000 feet)—IEC 60068-2-13 Vibration .
Agency Compliance Specifications The system complies with the following specifications. Category Relevant Standards Safety UL 60950, CB Scheme IEC 60950, CSA C22.2 No.
APPENDIX C Safety Precautions Read this section before beginning any procedure. The following text provides safety precautions to follow when installing a Sun Microsystems product. Safety Precautions For your protection, observe the following safety precautions when setting up your equipment: ■ ■ ■ Follow all cautions and instructions marked on the equipment. Ensure that the voltage and frequency of your power source match the voltage and frequency inscribed on the equipment’s electrical rating label.
Depending on the type of power switch your device has, one of the following symbols may be used: On – Applies AC power to the system. Off - Removes AC power from the system. Standby – The On/Standby switch is in the standby position. Modifications to Equipment Do not make mechanical or electrical modifications to the equipment. Sun Microsystems is not responsible for regulatory compliance of a modified Sun product.
Power Cord Connection Caution – Sun products are designed to work with single-phase power systems having a grounded neutral conductor. To reduce the risk of electric shock, do not plug Sun products into any other type of power system. Contact your facilities manager or a qualified electrician if you are not sure what type of power is supplied to your building. Caution – Not all power cords have the same current ratings.
The following caution applies only to devices with a Standby power switch: Caution – The power switch of this product functions as a standby type device only. The power cord serves as the primary disconnect device for the system. Be sure to plug the 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.
Laser Compliance Notice Sun products that use laser technology comply with Class 1 laser requirements. Class 1 Laser Product Luokan 1 Laserlaite Klasse 1 Laser Apparat Laser KLasse 1 CD-ROM Caution – Use of controls, adjustments, or the performance of procedures other than those specified herein may result in hazardous radiation exposure.
Einhaltung sicherheitsbehördlicher Vorschriften Auf dieser Seite werden Sicherheitsrichtlinien beschrieben, die bei der Installation von Sun-Produkten zu beachten sind. Sicherheitsvorkehrungen Treffen Sie zu Ihrem eigenen Schutz die folgenden Sicherheitsvorkehrungen, wenn Sie Ihr Gerät installieren: ■ ■ ■ Beachten Sie alle auf den Geräten angebrachten Warnhinweise und Anweisungen.
Aufstellung von Sun-Geräten Achtung – Um den zuverlässigen Betrieb Ihres Sun-Geräts zu gewährleisten und es vor Überhitzung zu schützen, dürfen die Öffnungen im Gerät nicht blockiert oder verdeckt werden. Sun-Produkte sollten niemals in der Nähe von Heizkörpern oder Heizluftklappen aufgestellt werden. Achtung – Der arbeitsplatzbezogene Schalldruckpegel nach DIN 45 635 Teil 1000 beträgt 70Db(A) oder weniger.
Die folgende Warnung gilt nur für Geräte mit Wartezustand-Netzschalter: Achtung – Der Ein/Aus-Schalter dieses Geräts schaltet nur auf Wartezustand (StandBy-Modus). Um die Stromzufuhr zum Gerät vollständig zu unterbrechen, müssen Sie das Netzkabel von der Steckdose abziehen. Schließen Sie den Stecker des Netzkabels an eine in der Nähe befindliche, frei zugängliche, geerdete Netzsteckdose an. Schließen Sie das Netzkabel nicht an, wenn das Netzteil aus der Systemeinheit entfernt wurde.
Einhaltung der Richtlinien für Laser Sun-Produkte, die mit Laser-Technologie arbeiten, entsprechen den Anforderungen der Laser Klasse 1. Class 1 Laser Product Luokan 1 Laserlaite Klasse 1 Laser Apparat Laser KLasse 1 CD-ROM Warnung – Die Verwendung von anderen Steuerungen und Einstellungen oder die Durchfhrung von Prozeduren, die von den hier beschriebenen abweichen, knnen gefhrliche Strahlungen zur Folge haben.
Attention: – présence de tensions dangereuses. Pour éviter les risques d’électrocution et de danger pour la santé physique, veuillez suivre les instructions. Un des symboles suivants sera peut-être utilisé en fonction du type d'interrupteur de votre système: MARCHE – Votre système est sous tension (courant alternatif). ARRET - Votre système est hors tension (courant alternatif). VEILLEUSE – L'interrupteur Marche/Veilleuse est en position « Veilleuse ».
Connexion du cordon d’alimentation Attention: – les produits Sun sont conçus pour fonctionner avec des alimentations monophasées munies d’un conducteur neutre mis à la terre. Pour écarter les risques d’électrocution, ne pas brancher de produit Sun dans un autre type d’alimentation secteur. En cas de doute quant au type d’alimentation électrique du local, veuillez vous adresser au directeur de l’exploitation ou à un électricien qualifié.
Batterie au lithium Attention: – sur les cartes CPU Sun, une batterie au lithium (référence MK48T59Y, MK48TXXB-XX, MK48T18-XXXPCZ, M48T59W-XXXPCZ, ou MK48T08.) a été moulée dans l’horloge temps réel SGS. Les batteries ne sont pas des pièces remplaçables par le client. Elles risquent d’exploser en cas de mauvais traitement. Ne pas jeter la batterie au feu. Ne pas la démonter ni tenter de la recharger.
Normativas de seguridad El siguiente texto incluye las medidas de seguridad que se deben seguir cuando se instale algún producto de Sun Microsystems. Precauciones de seguridad Para su protección observe las siguientes medidas de seguridad cuando manipule su equipo: ■ ■ ■ Siga todas los avisos e instrucciones marcados en el equipo. Asegúrese de que el voltaje y la frecuencia de la red eléctrica concuerdan con las descritas en las etiquetas de especificaciones eléctricas del equipo.
Modificaciones en el equipo No realice modificaciones de tipo mecánico o eléctrico en el equipo. Sun Microsystems no se hace responsable del cumplimiento de las normativas de seguridad en los equipos Sun modificados. Ubicación de un producto Sun Precaución – Para asegurar la fiabilidad de funcionamiento de su producto Sun y para protegerlo de sobrecalentamien-tos no deben obstruirse o taparse las rejillas del equipo. Los productos Sun nunca deben situarse cerca de radiadores o de fuentes de calor.
Precaución – Para eliminar completamente la alimentación de esta unidad, desconecte todos los cables de alimentación. La siguiente advertencia se aplica solamente a equipos con un interruptor de encendido que tenga una posición "En espera": Precaución – El interruptor de encendido de este producto funciona exclusivamente como un dispositivo de puesta en espera. El enchufe de la fuente de alimentación está diseñado para ser el elemento primario de desconexión del equipo.
Aviso de cumplimiento con requisitos de láser Los productos Sun que utilizan la tecnología de láser cumplen con los requisitos de láser de Clase 1. Class 1 Laser Product Luokan 1 Laserlaite Klasse 1 Laser Apparat Laser KLasse 1 CD-ROM Precaución – El manejo de los controles, los ajustes o la ejecución de procedimientos distintos a los aquí especificados pueden exponer al usuario a radiaciones peligrosas.
GOST-R Certification Mark Nordic Lithium Battery Cautions Norge ADVARSEL – Litiumbatteri — Eksplosjonsfare.Ved utskifting benyttes kun batteri som anbefalt av apparatfabrikanten. Brukt batteri returneres apparatleverandøren. Sverige VARNING – Explosionsfara vid felaktigt batteribyte. Använd samma batterityp eller en ekvivalent typ som rekommenderas av apparattillverkaren. Kassera använt batteri enligt fabrikantens instruktion. Danmark ADVARSEL! – Litiumbatteri — Eksplosionsfare ved fejlagtig håndtering.
238 Sun Fire V490 Server Administration Guide • August 2004
Index A AC Present LED (power supply), 173 accounts RSC, 191 Activity LED disk drive, 174 Ethernet, 174 address bitwalk (POST diagnostic), 80 of I2C devices (table), 111 agency compliance specifications, 220 agents, Sun Management Center, 103 alphanumeric terminal attaching, 133 baud verification, 132 setting up as system console, 133 settings for, 133 .
redirecting to SC, 161 removing SC as default, 161 console, system, 3 CPU displaying information about, 98 master, 78, 80 CPU/Memory board, 9, 27 currents, displaying system, 90 D data bitwalk (POST diagnostic), 80 data bus, Sun Fire V480, 75 data crossbar switch (CDX), 75 illustration of, 76 location of, 114 DC Present LED (power supply), 173 device paths, hardware, 87, 88, 92 device tree defined, 85, 103 Solaris, displaying, 94 device trees, rebuilding, 140 diag-level configuration variable, 82 diag-leve
with SunVTS, 106, 202 externally initiated reset (XIR), 51, 127 described, 23 manual command, 23 F fan displaying speed of, 90 Fan Tray 0 isolating faults in cable, 101 Fan Tray 0 LED described, 14 Fan Tray 1 LED described, 14 fan tray assembly, 39 configuration rule, 41 illustration, 40 LEDs, 14 fan tray LED, 173 fans See also fan tray assembly monitoring and control, 20 fault isolation, 100 FRU coverage (table), 100 procedures for, 167 using system LEDs, 172 Fault LED described, 13, 14 disk drive, 174 po
host adapter (probe-scsi), 91 hot spares, See disk configuration HP Openview, See third-party monitoring tools I I2C bus, 20 I2C device addresses (table), 111 IDE bus, 92 IDPROM function of, 79 IEEE 1275-compatible built-in self-test, 85 informal diagnostic tools, 73, 93 informal diagnostic tools, See also LEDs, system, 172 init command (Solaris), 50, 127 input-device configuration variable, 84, 165 installing a server, 2, 5 Integrated Drive Electronics, See IDE bus intermittent problem, 79, 105, 108 inter
M manual hardware reset, 127 manual system reset, 51 master CPU, 78, 80 memory interleaving, 30 mirroring, disk, 24, 66 monitor, attaching, 136 monitoring the system with RSC, 190 moving the system, precautions, 122 MPxIO (multiplexed I/O) features, 21 N network name server, 149 primary interface, 145 types, 4 O OBDIAG, See OpenBoot Diagnostics tests ok prompt risks in using, 50 ways to access, 50, 126 OK-to-Remove LED disk drive, 174 power supply, 173 OpenBoot commands dangers of, 50 .
pkgadd utility, 208 pkginfo command, 207, 208 POST, 74 controlling, 82 criteria for passing, 79 defined, 78 error messages, interpreting, 80 how to run, 175 persistent problems and, 79 purpose of, 79 post-trigger configuration variable, 84 power specifications, 218 turning off, 125 turning on, 122 Power button, 15 power distribution board isolating faults in, 101 power supplies LEDs, 17 LEDs, described, 18 power supply fault monitoring, 21 output capacity, 218 redundancy, 20 Power/OK LED, 173 described, 14
shipping (what you should receive), 1 show-devs command, 60, 151 show-devs command (OpenBoot), 92 showrev command (Solaris), 98 shutdown, 125 shutdown command (Solaris), 50, 127 software revision, displaying with showrev, 98 Solaris commands fsck, 51 halt, 50, 127 init, 50, 127 prtconf, 94 prtdiag, 94 prtfru, 97 psrinfo, 98 showrev, 98 shutdown, 50, 127 sync, 51 uadmin, 50, 127 specifications, 217, 220 agency compliance, 220 clearance, 220 electrical, 218 environmental, 219 physical, 217 service access, 220
Tivoli Enterprise Console, See third-party monitoring tools tree, device, 103 defined, 85 U uadmin command (Solaris), 50, 127 Universal Serial Bus (USB) ports about, 46 connecting to, 46 V /var/adm/messages file, 93 /var/crash directory, 157 verifying baud rate, 132 voltages, displaying system, 90 W warnings and cautions, 221, 237 watchdog, hardware described, 23 World Wide Name (probe-scsi), 91 X XIR (externally initiated reset), 51, 127 described, 23 manual command, 23 246 Sun Fire V490 Server Admin
