Sun Microsystems Fire V890 Diagnostic Manual
  1. Manuals
  2. Brands
  3. Sun Microsystems Manuals
  4. Server
  5. Sun Fire V890
  6. Diagnostic manual

Sun Microsystems Fire V890 Diagnostic Manual

Hide thumbs Also See for Fire V890:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Service Manual, Owner's Manual
Sun Fire
V890 Server
™
Diagnostics Guide
Sun Microsystems, Inc.
www.sun.com
Part No. 817-5950-11
October 2004, Revision 01
Submit comments about this document at:
http://www.sun.com/hwdocs/feedback

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Fire V890 and is the answer not in the manual?

Questions and answers

Related Manuals for Sun Microsystems Fire V890

Summary of Contents for Sun Microsystems Fire V890

  • Page 1 Sun Fire V890 Server ™ Diagnostics Guide Sun Microsystems, Inc. www.sun.com Part No. 817-5950-11 October 2004, Revision 01 Submit comments about this document at: http://www.sun.com/hwdocs/feedback...
  • Page 2 Copyright 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, Californie 95054, Etats-Unis. Tous droits réservés. Sun Microsystems, Inc. a les droits de propriété intellectuels relatants à la technologie qui est décrit dans ce document. En particulier, et sans la limitation, ces droits de propriété...

  • Page 3: Table Of Contents

    Contents Preface vii Diagnostic Tools 1 About Diagnostic Tools 2 About POST Diagnostics 4 OpenBoot Configuration Variables for POST 5 Running POST Diagnostics 8 How to Run POST Diagnostics 9 Before You Begin 10 Initiating POST Diagnostics 10 Displaying POST Diagnostic Results 11 Sample POST Diagnostic Output 12 Sample POST Error Messages 14 Sample Summary of POST Results 16...
  • Page 4 About Sun Remote System Control Software 44 RSC Capabilities 44 RSC User Interfaces 45 For More Information 45 Troubleshooting Strategies 47 About Troubleshooting Your System 48 Error Indications 49 Software Commands 51 About Diagnosing Specific Problems 72 Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 5 Network Communication Failure 72 Power-On Failure 75 Video Output Failure 76 RSC Console Failure 76 FC-AL Loop or Disk Drive Failure 78 DVD-ROM Drive Failure 81 Power Supply Failure 82 DIMM Failure 83 Environmental Failures 84 Index 89 Contents...
  • Page 6 Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 7: Preface

    Preface The Sun Fire V890 Server Diagnostics Guide is intended for experienced system administrators. It includes descriptive information about the Sun Fire™ V890 server and its diagnostic tools, and specific information about diagnosing and troubleshooting problems with the server. Before You Read This Book This book assumes that you are familiar with computer and network concepts and terms, and have advanced familiarity with the Solaris™...

  • Page 8: Typographic Conventions

    You must be superuser to do this. with real names or values. To delete a file, type rm filename. * The settings on your browser might differ from these settings. viii Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 9: Related Documentation

    Platform Notes: The eri FastEthernet Device Driver Platform Notes: The Sun Gigabit Ethernet Device Driver Platform Notes: Using luxadm Software Sun Fire V890 Server Dynamic Reconfiguration User’s Guide OpenBoot 4.x Command Reference Manual OpenBoot 4.x Quick Reference OpenBoot PROM Enhancements for Diagnostic Operation Remote System Sun Remote System Control (RSC) 2.2.2 User’s Guide...

  • Page 10: Contacting Sun Technical Support

    You can submit your comments by going to: http://www.sun.com/hwdocs/feedback Please include the title and part number of your document with your feedback: Sun Fire V890 Server Diagnostics Guide, part number 817-5950-11 x Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 11: Diagnostic Tools

    C H A P T E R Diagnostic Tools This chapter covers the diagnostic tools that are available for the Sun Fire V890 server and provides instructions on how to use these tools. The following tasks are covered in this chapter: “Running POST Diagnostics”...

  • Page 12: About Diagnostic Tools

    Remote System Control (RSC) software is a server management tool that provides remote system administration for geographically distributed or physically inaccessible systems. For more information about RSC, see “About Sun Remote System Control Software” on page Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 13 Which method or tool you use to diagnose system problems depends on the nature of those problems: If your system is unable to boot its operating system software, you need to run ■ POST and OpenBoot Diagnostics tests. If your system is “healthy” enough to start up and load its operating system ■...

  • Page 14: About Post Diagnostics

    To view detailed diagnostic and error messages from RSC POST, you must attach an ASCII terminal directly to the RSC serial port before running RSC POST. For more information about RSC POST, see the Sun Remote System Control (RSC) User’s Guide. Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 15: Openboot Configuration Variables For Post

    OpenBoot Configuration Variables for POST The following table lists and describes the OpenBoot configuration variables that enable you to control the operation of POST. Note – Both POST and OpenBoot Diagnostics use the settings of the configuration variables diag-level, diag-switch?, and diag-trigger. Changing the values of these variables will affect both POST and OpenBoot Diagnostics operation.
  • Page 16 OpenBoot (reset-all or boot) or from Solaris (reboot, shutdown, or init). Any kind of reset. all-resets To display the current and default values of all OpenBoot configuration variables, use the printenv command without specifying a variable. Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 17 The following is sample output from the printenv command. ok printenv Variable Name Value Default Value test-args diag-passes local-mac-address? true false scsi-initiator-id oem-logo No default oem-logo? false false oem-banner No default oem-banner? false false ansi-terminal? true true screen-#columns screen-#rows ttyb-rts-dtr-off false false ttyb-ignore-cd...

  • Page 18: Running Post Diagnostics

    POST does not run unless the keyswitch is set to the Diagnostics position or service-mode? is set to true. For maximum test coverage, set diag-level variable to max prior to starting POST diagnostics. Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 19: How To Run Post Diagnostics

    You can also configure POST to run automatically after specific types of reset events by setting the values of the OpenBoot configuration variables diag-switch? and diag-trigger, as shown in the following table. Note that diag-level must be set to any valid value other than none. For more information, see “OpenBoot Configuration Variables for POST”...

  • Page 20: Before You Begin

    RSC software before starting POST. For information about using the RSC software, see the Sun Remote System Control (RSC) User’s Guide. For information about setting up an alphanumeric terminal or establishing a tip connection, see the Sun Fire V890 Server Owner’s Guide.

  • Page 21: Displaying Post Diagnostic Results

    Displaying POST Diagnostic Results As POST runs, it displays diagnostic status messages locally on an attached terminal, through a tip connection, or on an RSC console (if POST output has been redirected to the RSC console). By default, POST output displays locally on an attached terminal or through a tip connection.

  • Page 22: Sample Post Diagnostic Output

    1>INFO: Setting Trip Temp of CPU 1 and 3 to 110C 1>INFO: Setting Trip Temp of CPU 5 and 7 to 110C 1>WED FEB 21 6:14:00 GMT 1 1>INFO: Disabling Cheetah-Err Circuitry ... Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 23 1>Setup DMMU Miss Handler 1>Probe and Setup Memory 1>INFO: 256MB Bank 0 1>INFO:No memory detected in Bank 1 1>INFO:No memory detected in Bank 2 1>INFO:No memory detected in Bank 3 1>Data Bitwalk on Master 1> Test Bank 0. 1>Address Bitwalk on Master 1>INFO: Addr walk mem test on CPU 1 Bank 0: 00000010.00000000 to 00000010.10000000.

  • Page 24: Sample Post Error Messages

    Address: 00000030.001b0038 Expected: 00000000.00100000 Observed: 00000000.00000000 1>END_ERROR 1>ERROR: TEST = Data Bitwalk on Slave 3 1>H/W under test = CPU3 Memory 1>MSG = *** Test Failed!! *** 1>END_ERROR Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 25 As shown in the preceding error message, POST reports memory errors by indicating the location (“J” number) of the failing DIMM. Use the following diagram to identify the location of a failing DIMM according to J number. J 8 0 J 8 2 J 3 2 J 3 0...

  • Page 26: Sample Summary Of Post Results

    With diag-level set to off, no tests are run, and POST indicates a passed status for all devices. ok setenv diag-level off ok reset-all Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 27: About Openboot Diagnostics

    About OpenBoot Diagnostics OpenBoot Diagnostics code resides in the OpenBoot PROM on the system I/O board. OpenBoot Diagnostics can detect and isolate errors in the following system components: Motherboard and I/O board ■ Disk drives and FC-AL disk backplanes ■ Any PCI card that contains an on-board self-test ■...

  • Page 28: Openboot Configuration Variables For Openboot Diagnostics

    OpenBoot Diagnostics tests that are run from the OpenBoot Diagnostics menu. The maximum value for diag-passes is >1,000,000. Note: The variable diag-passes has no effect outside the OpenBoot Diagnostics Menu. See “OpenBoot ok Prompt Commands” on page Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 29 Variable Setting or Keyword Description Default Determines which OpenBoot Diagnostics tests diag-script normal are run automatically after the reset event specified by the variable diag-trigger. Tests all the devices shipped with a base system. normal Executes all available self-tests, including tests on plug-in cards.
  • Page 30 (This keyword has no effect on status messages of tests run from the ok prompt.) Displays name of each subtest that is called. subtests Displays detailed messages of progression of all verbose tests. Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 31 Variable Setting or Keyword Description Default Displays backtrace of N callers when an error callers=N occurs. • callers=0 displays backtrace of all callers on error. Continues executing the test until N errors are errors=N encountered. • errors=0 displays all error reports without terminating testing.

  • Page 32: Openboot Ok Prompt Commands

    OpenBoot Diagnostics, you must set the OpenBoot configuration variable auto-boot? to false and reset the system. For the detailed procedure, see “Initiating OpenBoot Diagnostics” on page Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 33: Test Command

    test Command The test command enables you to test an individual device. At the ok prompt, type test and the full path name or device alias of the device, as shown in the following example: ok test /pci@9,700000/ebus@1/flashprom@0,0 Chapter 1 Diagnostic Tools...
  • Page 34 /pci@9,700000/ebus@1/i2c@1,500030/nvram@0,a0 i2c3 /pci@9,700000/ebus@1/i2c@1,500030 i2c2 /pci@9,700000/ebus@1/i2c@1,50002e bbc1 /pci@9,700000/ebus@1/bbc@1,500000 i2c1 /pci@9,700000/ebus@1/i2c@1,30 i2c0 /pci@9,700000/ebus@1/i2c@1,2e bbc0 /pci@9,700000/ebus@1/bbc@1,0 rsc-console /pci@9,700000/ebus@1/rsc-console@1,3083f8 rsc-control /pci@9,700000/ebus@1/rsc-control@1,3062f8 ttyb /pci@9,700000/ebus@1/serial@1,400000:b ttya /pci@9,700000/ebus@1/serial@1,400000:a pci9b /pci@9,700000 pci9a /pci@9,600000 pci8b /pci@8,700000 pci8a /pci@8,600000 ebus /pci@9,700000/ebus@1 Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 35 You can use test-args keywords with the test command to fine-tune the execution of the test. See “OpenBoot Configuration Variables for OpenBoot Diagnostics” on page 18 for more information about the test-args options. The following is an example of using the test-args keywords loopback and verbose with the test command: ok test /pci@9,700000/network@1:test-args={loopback,verbose} test-all Command...

  • Page 36: Openboot Diagnostics Menu

    “OpenBoot Diagnostics Test Descriptions” on page 27. For a description of the interactive commands that allow you to run OpenBoot Diagnostics from the obdiag> prompt, see “OpenBoot Diagnostics Menu Commands” on page Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 37: Openboot Diagnostics Menu Commands

    OpenBoot Diagnostics Menu Commands The following table describes the interactive OpenBoot Diagnostics menu commands that are available at the obdiag> prompt. Command Description Exits the OpenBoot Diagnostics menu and returns to the ok prompt. exit Displays a brief description of each OpenBoot Diagnostics menu command and help OpenBoot configuration variable.
  • Page 38 To run hot-plug tests, the test-args hotplugcontroller@0,e2 keyword hotplug must be specified. hotplugcontroller@0,e6 Warning: After the hot-plug test, hotplugcontroller@0,e8 the PCI cards in the slots tested are hotplugcontroller@0,ec not usable until you reset the system. Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 39 Device Description of Device Self-Test Special Considerations Tests the devices (temperature i2c@1,2e sensors, fans, power supplies, i2c@1,30 system fault LEDs, thermal fault i2c@1,50002e LEDs, and front panel keyswitch) i2c@1,500030 monitored by the I environmental monitoring bus. Tests the on-board IDE controller You must specify the variable ide@1 and IDE bus subsystem for internal...
  • Page 40 The Sun part number for the serial loopback connector is 501-4205-01. Tests the writable registers of the usb@1,3 USB open host controller. Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 41: Running Openboot Diagnostics

    Additional testing may be performed if your configuration includes an optional device that has an on-board self-test that supports the OpenBoot standard. Such optional devices include PCI interface cards that support parallel communication lines, audio devices, or any other device that is IEEE 1275 compatible and provides a method named “selftest.”...
  • Page 42 – Executes all available self-tests, including tests on plug-in cards. ■ none – No diagnostic self-tests are run. ■ “OpenBoot Configuration Variables for OpenBoot Diagnostics” on page 18 information about the settings for diag-script. Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 43: How To Run Openboot Diagnostics

    The following sample output shows the results of OpenBoot Diagnostics tests when the variable diag-level is set to max, diag-script is set to normal, and no test-args keywords are specified. Running diagnostics script obdiag/normal Testing /pci@8,600000/network@1 Testing /pci@8,600000/SUNW,qlc@2 Testing /pci@9,700000/ebus@1/i2c@1,2e Testing /pci@9,700000/ebus@1/i2c@1,30 Testing /pci@9,700000/ebus@1/i2c@1,50002e Testing /pci@9,700000/ebus@1/i2c@1,500030...

  • Page 44: Before You Begin

    If OpenBoot Diagnostics will be running automatically after a power-on or reset ■ event, you can: Connect an alphanumeric terminal. See the Sun Fire V890 Server Owner’s Guide ■ for instructions. (You cannot view diagnostics messages at a graphics console when OpenBoot Diagnostics is running automatically.)

  • Page 45: Initiating Openboot Diagnostics

    Initiating OpenBoot Diagnostics You should run OpenBoot Diagnostics tests interactively only after a power-on or system reset. You cannot run OpenBoot Diagnostics reliably after halting the operating system or aborting the operating system with the Stop-A keyboard command (or an equivalent abort key sequence). Therefore, in order to access the ok prompt and run OpenBoot Diagnostics, you must set the OpenBoot configuration variable auto-boot? to false and reset the system.

  • Page 46: Displaying Openboot Diagnostics Results

    1. Type the following commands at the system ok prompt: ok diag-console rsc ok setenv input-device rsc-console ok setenv output-device rsc-console 2. To cause the changes to take effect, power cycle the system, or type: ok reset-all Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 47: Sample Openboot Diagnostics Error Messages

    If you redirect OpenBoot Diagnostics output to an RSC console, the output will not display on the system console. To redirect OpenBoot Diagnostics output to the local system console or to a tip connection, issue the diag-console command as shown in the following example: ok diag-console ttya ok reset-all...

  • Page 48: About Sunvts Software

    SunVTS software provides the following user interfaces: Command-line interface ■ TTY interface ■ Graphical user interface (GUI) that runs within a windowed desktop environment ■ You can run SunVTS software from any one of its interfaces. Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 49: For More Information

    For More Information The following documents provide information about SunVTS software. They are available on the Supplement CD for your specific Solaris release and on the web at http://docs.sun.com. SunVTS User’s Guide ■ This document describes the SunVTS environment, including how to start and control the various user interfaces.

  • Page 50: How To Check Whether Sunvts Software Is Installed

    Before You Begin This procedure assumes that the Solaris operating environment is running on the Sun Fire V890 server, and that you have access to the Solaris command line. For more information, see the Sun Fire V890 Server Owner’s Guide What to Do 1.

  • Page 51: What Next

    2. (Solaris 8 Operating System only) Check for additional needed software. This applies only if you intend to install and run SunVTS 5.1 software (or later compatible versions) under the Solaris 8 Operating System. SunVTS 5.1 software requires additional packages that may not be installed with Solaris 8 software.

  • Page 52: How To Run Sunvts Software

    SunVTS graphical interface. For information about the SunVTS interfaces and options, see the SunVTS User’s Guide. 1. Use the xhost command to give the Sun Fire V890 server access to the remote display.
  • Page 53 On the Test Selection panel, click to select and deselect tests. (A check mark in the box indicates the item is selected.) The following table lists and describes useful tests to run on the Sun Fire V890 server. SunVTS Test...

  • Page 54: Sunvts Results

    SunVTS Results If SunVTS tests indicate an impaired or defective part, see the replacement procedures in the Sun Fire V890 Server Service Manual. 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. This opens a log window from which you can choose to view the following logs: Information —...

  • Page 55: About Sun Management Center Software

    About Sun Management Center Software Sun Management Center software is a convenient, single solution for managing multiple Sun systems, devices, and network resources. With its intuitive graphical interface based on Java software, Sun Management Center offers powerful management capabilities that allow you to do the following: Manage and monitor your server remotely from any location in the network ■...

  • Page 56: About Sun Remote System Control Software

    View a graphical representation of the server’s front panel, including keyswitch ■ position and LED states Receive notification of server problems via email or pager, even in the event of a ■ power failure Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 57: Rsc User Interfaces

    Perform remote server reboot, power-on, and power-off functions on demand ■ Access a detailed log of RSC events, command history, and detected errors ■ RSC complements existing Sun monitoring and diagnostic tools such as Sun Management Center, SunVTS, POST, and OpenBoot Diagnostics. RSC User Interfaces RSC offers the following user interfaces: A graphical user interface (GUI) that runs as a Java client application on...
  • Page 58 Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 59: Troubleshooting Strategies

    C H A P T E R Troubleshooting Strategies This chapter provides information about error indications and software commands to help you determine which component you need to replace. It contains the following sections: “About Troubleshooting Your System” on page 48 ■...

  • Page 60: About Troubleshooting Your System

    Software disk problem problem About Troubleshooting Your System The system provides the following features to help you identify and isolate hardware problems: Error indications ■ Software commands ■ Diagnostic tools ■ Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 61: Error Indications

    Usually, a front panel LED is not the only indication of a problem. Error messages and other LEDs within the enclosure can help to isolate the problem further. For additional information about the front panel LEDs, see the Sun Fire V890 Server Owner’s Guide.

  • Page 62: Error Messages

    ■ Disk drive LEDs ■ For detailed information about these LEDs, see the Sun Fire V890 Server Owner’s Guide. Since all front panel and power supply LEDs are powered by the system’s 5-volt standby power source, fault LEDs remain illuminated for any fault condition that results in a system shutdown.

  • Page 63: Software Commands

    Software Commands Several Solaris and OpenBoot firmware commands are available for diagnosing system problems. For more information about Solaris commands, see the appropriate man pages. For additional information about OpenBoot commands, see the OpenBoot 4.x Command Reference Manual. An online version of the manual is included with the OpenBoot Collection AnswerBook that ships with Solaris software.
  • Page 64 1, 17 1200 16.0 US-IV 2, 18 1200 16.0 US-IV 3, 19 1200 16.0 US-IV 4, 20 1200 16.0 US-IV 5, 21 1200 16.0 US-IV 6, 22 1200 16.0 US-IV 7, 23 1200 16.0 US-IV Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 65 ========================= Memory Configuration =============================== Logical Logical Logical Bank Bank Bank DIMM Interleave Interleaved size Status Size Factor with ---- ---- ------ ----------- ------ ---------- ----------- 1024MB no_status 512MB 8-way 1024MB no_status 512MB 8-way 1024MB no_status 512MB 8-way 1024MB no_status 512MB 8-way 1024MB no_status...
  • Page 66 The prtdiag command with the -v option produces all of the output of the prtdiag command (shown in the preceding example) in addition to environmental information, current keyswitch position, LED indications, and other information. Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 67 The following is an example of the additional output produced by the -v option. ========================= Environmental Status ========================= System Temperatures (Celsius): ------------------------------- Device Temperature Status --------------------------------------- CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 DBP0 ================================= Front Status Panel: ------------------- Keyswitch position: NORMAL System LED Status: GEN FAULT...
  • Page 68 ------- ---- GOOD GOOD GOOD ========================= HW Revisions ======================================= System PROM revisions: ---------------------- OBP 4.15.1 2004/06/02 16:06 IO ASIC revisions: ------------------ Port Model Status Version -------- ---- ------ ------- Schizo Schizo Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 69 To run prtconf, type: % /usr/sbin/prtconf The following is partial sample output. % /usr/sbin/prtconf System Configuration: Sun Microsystems sun4u Memory size: 3072 Megabytes System Peripherals (Software Nodes): SUNW,Sun-Fire-V890 packages (driver not attached) SUNW,builtin-drivers (driver not attached)
  • Page 70 (driver not attached) memory-controller, instance #5 cmp (driver not attached) cpu (driver not attached) cpu (driver not attached) memory-controller, instance #6 cmp (driver not attached) cpu (driver not attached) cpu (driver not attached) Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 71 pci, instance #0 scsi, instance #0 disk (driver not attached) tape (driver not attached) sd, instance #0 (driver not attached) sd, instance #1 (driver not attached) sd, instance #2 (driver not attached) TSI,gfxp (driver not attached) pci, instance #1 network (driver not attached) SUNW,qlc, instance #0 fp (driver not attached) disk (driver not attached)
  • Page 72 /ManR/Sun_Part_No: 5015142 /ManR/Sun_Serial_No: 000069 /ManR/Vendor_Name: NO JEDEC CODE FOR THIS VENDOR /ManR/Initial_HW_Dash_Level: 03 /ManR/Initial_HW_Rev_Level: 01 /ManR/Fru_Shortname: /Dak_IOBoardR /Dak_IOBoardR/PROM_Format_Version: 1 /Dak_IOBoardR/Ambient_Temp_Array: 9223372036854775806 /Dak_IOBoardR/Min_Power_Rating (4 iterations) /Dak_IOBoardR/Min_Power_Rating[0]: 11 /Dak_IOBoardR/Min_Power_Rating[1]: 22 /Dak_IOBoardR/Min_Power_Rating[2]: 33 /Dak_IOBoardR/Min_Power_Rating[3]: 44 Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 73 /Dak_IOBoardR/Max_Power_Rating (4 iterations) /Dak_IOBoardR/Max_Power_Rating[0]: 22 /Dak_IOBoardR/Max_Power_Rating[1]: 33 /Dak_IOBoardR/Max_Power_Rating[2]: 44 /Dak_IOBoardR/Max_Power_Rating[3]: 55 /frutree/chassis/rsc-board (container) SEGMENT: SD /frutree/chassis/fcal-backplane-slot?Label=0 /frutree/chassis/fcal-backplane-slot?Label=0/fcal-backplane (container) /frutree/chassis/fcal-backplane-slot?Label=1 /frutree/chassis/fcal-backplane-slot?Label=1/fcal-backplane (container) /frutree/chassis/power-dist-board (container) /frutree/chassis/power-dist-board/power-supply-slot?Label=0 /frutree/chassis/power-dist-board/power-supply-slot?Label=0/power-supply (container) /frutree/chassis/power-dist-board/power-supply-slot?Label=1 /frutree/chassis/power-dist-board/power-supply-slot?Label=1/power-supply (container) /frutree/chassis/power-dist-board/power-supply-slot?Label=2 /frutree/chassis/power-dist-board/power-supply-slot?Label=2/power-supply (container) /frutree/chassis/system-board (container) /frutree/chassis/system-board/cpu-mem-slot?Label=A /frutree/chassis/system-board/cpu-mem-slot?Label=B /frutree/chassis/system-board/cpu-mem-slot?Label=B/cpu-mem-module (container) SEGMENT: SD /ManR /ManR/UNIX_Timestamp32: Mon Jun 12 14:31:06 EDT 2000 /ManR/Fru_Description: ASSY,CPU,DUAL,DAK...
  • Page 74 24C64_A4_1 (i2c, 43000006a0) 24C64_A6_1 (i2c, 43000006a5) 24C64_A8_1 (i2c, 43000006aa) 24C64_AA_1 (i2c, 43000006af) 24C64_AC_1 (i2c, 43000006b4) 24C64_AE_1 (i2c, 43000006b9) 24C64_A0_3 (i2c, 43000006e6) 24C64_A2_3 (i2c, 43000006eb) 24C64_A4_3 (i2c, 43000006f0) 24C64_A6_3 (i2c, 43000006f5) 24C64_A8_3 (i2c, 43000006fa) Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 75 CPU_4_6_MOD_SLOT (picl, 430000027e) CPU_5_7_MOD_SLOT (picl, 4300000283) CPU_0_2_MOD_PR_SENSOR (gpio, 43000002cc) CPU_1_3_MOD_PR_SENSOR (gpio, 43000002d3) CPU_4_6_MOD_PR_SENSOR (gpio, 43000002da) CPU_5_7_MOD_PR_SENSOR (gpio, 43000002e1) DAR8_DIE_TEMPERATURE_SENSOR (temperature-sensor, 430000034c) DCS8_DIE_TEMPERATURE_SENSOR (temperature-sensor, 4300000356) 24C64_A8_4 (i2c, 4300000718) SSC050_80_5 (i2c, 4300000786) HPC3130_EC_5 (i2c, 43000007fe) 24C64_A0_11 (i2c, 43000008bc) IO_BOARD (picl, 430000000f) FAN_BLAST_OFF_SWITCH (switch, 430000003c) CPU_PFAN_PR_SENSOR (gpio, 43000000bb) CPU_SFAN_PR_SENSOR (gpio, 43000000c2) IO_PFAN_PR_SENSOR (gpio, 43000000c9)
  • Page 76 Status of processor 2 as of: 04/11/01 12:03:45 Processor has been on-line since 04/11/01 10:53:05. The sparcv9 processor operates at 750 MHz, and has a sparcv9 floating point processor. Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 77 If you are working from the ok prompt, you can use the OpenBoot show-devs command to list the devices in the system configuration. The following is sample show-devs output for a Sun Fire V890 server configured with a full complement of CPU/Memory boards, DIMMs, power supplies, and FC-AL disk backplanes. The ™...
  • Page 78 FRU SEEPROM – CPU5 DIMM J3200 /pci@9,700000/ebus@1/i2c@1,50002e/fru@1,a8 FRU SEEPROM – CPU5 DIMM J3000 /pci@9,700000/ebus@1/i2c@1,50002e/fru@1,a6 FRU SEEPROM – CPU5 DIMM J3101 /pci@9,700000/ebus@1/i2c@1,50002e/fru@1,a4 FRU SEEPROM – CPU5 DIMM J2901 /pci@9,700000/ebus@1/i2c@1,50002e/fru@1,a2 FRU SEEPROM – CPU5 DIMM J3100 Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 79 /pci@9,700000/ebus@1/i2c@1,30/hotplug-controller@0,ecHot plug controller, CPU/Memory slots /pci@9,700000/ebus@1/i2c@1,30/hotplug-controller@0,e8Hot plug controller, PCI slots 5-8 /pci@9,700000/ebus@1/i2c@1,30/hotplug-controller@0,e6Hot plug controller, PCI slots 2-8 /pci@9,700000/ebus@1/i2c@1,30/hotplug-controller@0,e2Hot plug controller, PCI slots 0-1 /pci@9,700000/ebus@1/i2c@1,30/rscrtc@0,d0 system controller card real time clock /pci@9,700000/ebus@1/i2c@1,30/fru@0,ae FRU SEEPROM – power distribution board /pci@9,700000/ebus@1/i2c@1,30/fru@0,ac FRU SEEPROM – expansion backplane /pci@9,700000/ebus@1/i2c@1,30/fru@0,a8 FRU SEEPROM –...
  • Page 80 FRU SEEPROM – CPU0 DIMM J2901 /pci@9,700000/ebus@1/i2c@1,2e/fru@0,a2 FRU SEEPROM – CPU0 DIMM J3100 /pci@9,700000/ebus@1/i2c@1,2e/fru@0,a0 FRU SEEPROM – CPU0 DIMM J2900 /pci@8,600000/SUNW,qlc@2 On-board FC-AL controller /pci@8,600000/network@1 On-board Gigabit Ethernet interface /pci@8,600000/SUNW,qlc@2/fp@0,0 /pci@8,600000/SUNW,qlc@2/fp@0,0/disk /packages/disk-label Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 81 /pci@8,700000/ide@1 /pci@8,700000/ide@1/cdrom /pci@8,700000/ide@1/disk /openprom/client-services /packages/kbd-translator /packages/dropins /packages/SUNW,debug /packages/obp-tftp /packages/terminal-emulator /packages/disk-label /packages/deblocker /packages/SUNW,builtin-drivers Chapter 2 Troubleshooting Strategies...
  • Page 82 40 deg. C, Die = 61 deg. C Motherboard: Ambient = 29 deg. C I/O Board: Ambient = 22 deg. C Disk Backplane 0: Ambient = 21 deg. C Environmental monitor is ON Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 83 OpenBoot printenv Command Use the OpenBoot printenv command to display the OpenBoot configuration variables. The display includes the current values for these variables as well as the default values. Chapter 2 Troubleshooting Strategies...
  • Page 84 No default security-#badlogins No default verbosity debug normal fcode-debug? false false diag-out-console false false diag-trigger none error-reset power-on-res ... service-mode? false false diag-script none normal diag-level diag-switch? false false error-reset-recovery sync sync Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 85 OpenBoot probe-scsi and probe-scsi-all Commands To diagnose problems with the SCSI or FC-AL devices, you can use the OpenBoot probe-scsi and probe-scsi-all commands. Both commands require that you get to the ok prompt after a reset. Note – When it is not practical to halt the system, you can use SunVTS software as an alternative method of testing the SCSI and FC-AL interfaces.

  • Page 86: Network Communication Failure

    Ethernet 10BASE-T link integrity test function should always be enabled on both the host system and the Ethernet hub. If you have trouble establishing a connection between the Sun Fire V890 server and your Ethernet hub, verify that the Ethernet hub also has the link test function enabled.
  • Page 87 If you connect the system to a network and the network does not respond, use the OpenBoot PROM command watch-net-all to display conditions for all network connections: ok watch-net-all For most PCI Ethernet cards, the link integrity test function can be enabled or disabled with a hardware jumper on the PCI card, which you must set manually.
  • Page 88 1: apply disable-link-pulse device-name (Repeat this step for other device names as needed.) (Press CONTROL-C to exit nvedit.) ok nvstore ok setenv use-nvramrc? true 2. Reboot the system to make the changes effective. Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 89: Power-On Failure

    Check the POST output using a locally attached terminal, tip connection, or RSC console. If you see no front panel LED activity, a power supply may be defective. See the Sun Fire V890 Server Owner’s Guide for information about power supply LED indications.

  • Page 90: Video Output Failure

    The most likely cause of this problem is a faulty system controller card. To recover from this problem and gain access to the system from a local system console, follow these steps: 1. Press the system Power button briefly to initiate a graceful software shutdown. Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 91 2. Make sure that the system is connected to a local console device. Install a local console if necessary. See the Sun Fire V890 Server Owner’s Guide for instructions. 3. Press and release the Power button and wait until the System Fault LED on the front panel begins to blink.

  • Page 92: Fc-Al Loop Or Disk Drive Failure

    Run OpenBoot Diagnostics tests for the mass storage subsystem. 1. At the ok prompt, type: ok setenv auto-boot? false ok setenv diag-level max ok setenv diag-switch true ok setenv test-args verbose,subtests 2. Power off the system. Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 93 3. Verify that all cables attached to the FC-AL disk backplanes are properly connected. 4. Power on the system and observe the POST status messages. If POST reports a problem, replace the component indicated by the failure message and repeat POST diagnostics until the problem is resolved. 5.
  • Page 94 AL_PA Expansion Backplane AL_PA Disk 0 Disk 6 Disk 1 Disk 7 Disk 2 Disk 8 Disk 3 Disk 9 Disk 4 Disk 10 Disk 5 Disk 11 SSC-100 SES processor Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 95: Dvd-Rom Drive Failure

    Other types of failures during the on-board controller test usually indicate a problem with the motherboard or the motherboard FC-AL cable. When testing the PCI controller, these types of failure messages point to the PCI card or the FC-AL cable between the card and the base backplane.

  • Page 96: Power Supply Failure

    In addition, the AC Status and DC Status LEDs at the rear of each power supply indicate any problem with the AC input and DC output, respectively. See the Sun Fire V890 Server Owner’s Guide for more information about the LEDs. Action ●...

  • Page 97: Dimm Failure

    DIMM Failure Symptom SunVTS and POST diagnostics can report memory errors encountered during program execution. Memory error messages typically indicate the location number (“J” number) of the failing DIMM. Action 1. Use the following diagram to identify the location of a failing DIMM from its J number.

  • Page 98: Environmental Failures

    2. After you identify the defective DIMM, replace it according to the removal and installation instructions in the Sun Fire V890 Server Service Manual. Environmental Failures The Sun Fire V890 server features an environmental monitoring subsystem designed to protect against: Extreme temperatures ■...
  • Page 99 Fault LEDs on the status and control panel are also lit. LEDs located on the back of each power supply indicate the source and nature of the fault. Note – The Sun Fire V890 server power supplies have their own built-in overtemperature protection circuits that will automatically shut down the supplies in response to certain overtemperature and power fault conditions.
  • Page 100 “CRITICAL: HIGH TEMPERATURE...” Warning and the shut down message. Note: Output from the prtpicl command shows the high-temperature warning threshold for each component. See the prtpicl man page for information. Sun Fire V890 Server Diagnostics Guide • October 2004...
  • Page 101 Message Type Description Warning Indicates that the temperature measured at WARNING: LOW TEMPERATURE DETECTED Temp,Temperature-Sensor Temperature-Sensor has fallen below the warning threshold. If the temperature continues to fall and goes below the critical threshold, the system issues the “CRITICAL: LOW TEMPERATURE...” warning and the shutdown message.
  • Page 102 The message “Disk Error cleared” appears when the disk fault is cleared. Disk Error Cleared Advisory Indicates keyswitch position has changed and Keyswitch position changed to Position gives the current position. Sun Fire V890 Server Diagnostics Guide • October 2004...

  • Page 103: Index

    Index configuring interface 44 device names 73 airflow, monitoring 85 link integrity test 72–74 configuration parameters, See OpenBoot PROM failure variables disk drive 78 DVD-ROM drive 81 FC-AL loop 78 diagnostics memory module 83 See also POST diagnostics, OpenBoot network 72 Diagnostics, SunVTS power supply 82 available tools 2...
  • Page 104 44 user interfaces 45 reset command 78 show-devs command 73 status LEDs about 49 environmental fault indicators 85 SunMC 2 SunVTS about 2 checking if installed 39 how to use 40 Sun Fire V890 Server Diagnostics Guide • October 2004...

Table of Contents