digital equipment corporation maynard, massachusetts DEC 7000 AXP System VAX 7000 Basic Troubleshooting Order Number EK7000BTS.002 This manual is intended for the system operator and covers the basic trou­ bleshooting procedures for the DEC 7000 and VAX 7000 systems. First Printing, November 1992 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software, if any, described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No re­ sponsibility is assumed for the use or reliability of software or equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Copyright © 1992 by Digital Equipment Corporation. All Rights Reserved. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: Alpha AXP DECUS VAXBI AXP DWMVA VAXELN DEC OpenVMS VMScluster DECchip ULTRIX XMI DEC LANcontroller UNIBUS The AXP logo DECnet VAX OSF/1 is a registered trademark of the Open Software Foundation, Inc. FCC NOTICE: The equipment described in this manual generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such radio frequency interference when operated in a commercial environment. Operation of this equipment in a residential area may cause interference, in which case the user at his own expense may be required to take measures to correct the interference. iii Contents Preface ..................................................................................................... vii Chapter 1 System Troubleshooting 1.1 Troubleshooting During Power­Up ....................................... 1­2 1.2 Troubleshooting During Booting ........................................... 1­4 1.3 Troubleshooting a DSSI Plug­In Unit ................................... 1­6 1.4 Troubleshooting a SCSI Plug­In Unit ................................... 1­8 1.5 Troubleshooting an XMI Plug­In Unit ................................ 1­10 1.6 Troubleshooting a TF85 Tape Drive .................................. 1­12 1.7 Troubleshooting an RRD42 Compact Disk Drive ............... 1­14 1.8 Air Pressure Sensor and Temperature Sensors ................. 1­15 Chapter 2 Self­Test 2.1 Self­Test Overview ................................................................. 2­2 2.2 Testing Sequence ................................................................... 2­4 2.3 Sample Self­Test Display ....................................................... 2­6 2.4 Self­Test Lines NODE # and TYP ......................................... 2­8 2.5 Self­Test Lines ST and BPD ................................................ 2­10 2.6 Self­Test Lines C0, C1, C2, and C3 ..................................... 2­12 2.7 Self­Test Lines ILV and Mb ................................................ 2­14 2.8 Self­Test Identification Line ................................................ 2­16 Chapter 3 Getting System Information 3.1 Show Command ..................................................................... 3­2 3.1.1 Show Configuration ......................................................... 3­2 3.1.2 Show Network .................................................................. 3­4 3.1.3 Show Device ..................................................................... 3­6 3.2 Test Command ....................................................................... 3­8 iv 3.2.1 Testing the System ........................................................ 3­10 3.2.2 Testing a Subsystem ..................................................... 3­12 3.2.3 Testing a Module or a Device ........................................ 3­14 3.3 Error Reports ....................................................................... 3­16 Appendix A Power System Indicators A.1 AC Input Box .......................................................................... A­2 A.2 Control Panel .......................................................................... A­3 A.3 System Power Regulator ....................................................... A­4 A.4 XMI PIU Power Regulators ................................................... A­6 A.5 Cabinet Control Logic Module ............................................... A­8 Examples 1­1 Sample Self­Test Display, Failing DWLMA Adapter ........ 1­11 3­1 Sample System Hardware Configuration ............................. 3­2 3­2 Sample Output of Show Network Command ........................ 3­4 3­3 Sample Output of Show Device Command ........................... 3­6 3­4 Sample Test Commands ........................................................ 3­8 3­5 Sample Test Command, System Test ................................. 3­10 3­6 Sample Test Command, I/O Subsystem Test ..................... 3­12 3­7 Sample Test Command, I/O Adapter Test .......................... 3­14 3­8 Sample Test Command, Device Test ................................... 3­15 3­9 Sample Test Command, Memory Module Test .................. 3­15 3­10 Sample Summary Error Report .......................................... 3­16 3­11 Sample Full Error Report .................................................... 3­18 Figures 1­1 Power­Up Troubleshooting Flowchart .................................. 1­2 1­2 Power­Up Troubleshooting Steps .......................................... 1­3 1­3 Booting Troubleshooting Flowchart ...................................... 1­4 1­4 Troubleshooting Steps During Booting ................................. 1­5 1­5 DSSI Disk Control Panel ....................................................... 1­6 1­6 SCSI Indicator LEDs ............................................................. 1­8 1­7 Troubleshooting an XMI Plug­In Unit ................................ 1­10 1­8 TF85 Controls and Indicators ............................................. 1­12 1­9 RRD42 CD Drive Control Panel .......................................... 1­14 1­10 CCL Air Pressure Sensor ..................................................... 1­15 2­1 Determining Self­Test Results .............................................. 2­2 2­2 Testing Sequence ................................................................... 2­4 v 2­3 Self­Test Results .................................................................... 2­6 2­4 Self­Test Results: NODE # and TYP ..................................... 2­8 2­5 Self­Test Results: ST and BPD ........................................... 2­10 2­6 Self­Test Results: C0, C1, C2, and C3 ................................. 2­12 2­7 Self­Test Results: ILV and Mb ............................................ 2­14 2­8 Self­Test Results: Identification Line ................................ 2­16 A­1 AC Input Box .......................................................................... A­2 A­2 Control Panel .......................................................................... A­3 A­3 System Power Regulator ........................................................ A­4 A­4 XMI PIU Power Regulators ................................................... A­6 A­5 CCL Module LEDs ................................................................. A­8 Tables 1 DEC 7000/VAX 7000 Documentation ..................................... ix 2 Related Documents .................................................................. xi 1­1 Indicator Switches on DSSI Disk Control Panel .................. 1­7 1­2 DSSI Disk PIU Fault Diagnosis ............................................ 1­7 1­3 SCSI Disk Drive LEDs ........................................................... 1­9 1­4 SCSI Power Supply LEDs ...................................................... 1­9 1­5 TF85 Light Summary .......................................................... 1­13 1­6 RRD42 LED Summary ........................................................ 1­14 2­1 System Configuration for Figure 2­3 .................................... 2­7 2­2 I/O Subsystem Configuration for Figure 2­3 ........................ 2­7 3­1 Test Command Options ......................................................... 3­9 3­2 Test Command Environment Variables ............................... 3­9 A­1 System Power Regulator Light Summary ............................ A­5 A­2 XMI PIU Power Regulator Lights ......................................... A­7 vii Preface Intended Audience This manual is written for the system manager or system operator who has had training in system management tasks and is running a DEC 7000 or a VAX 7000 system. Document Structure This manual uses a structured documentation design. Topics are organ­ ized into small sections for efficient on­line and printed reference. Each topic begins with an abstract. You can quickly gain a comprehensive over­ view by reading only the abstracts. Next is an illustration or example, which also provides quick reference. Last in the structure are descriptive text and syntax definitions. This manual has three chapters and one appendix as follows: · Chapter 1, System Troubleshooting, tells you what to do if some­ thing goes wrong. · Chapter 2, Self­Test, explains how to interpret the self­test display. · Chapter 3, Getting System Information, explains how to identify the modules and devices in your system and how to test them. · Appendix A describes the indicators on the various power system components. viii Conventions Used in This Document Terminology. Unless specified otherwise, the use of "system" refers to either a DEC 7000 AXP or VAX 7000 system. The DEC 7000 AXP systems use the Alpha AXP architecture. References in text use DEC 7000 to refer to DEC 7000 AXP systems. When a discussion applies to only one system, an icon is used to highlight that system. Otherwise, the discussion applies to both systems. Thus, the abstract for a module that applies only to DEC 7000 systems would look like this: Book titles. In text, if a book is cited without a product name, that book is part of the hardware documentation. It is listed in Table 1 along with its order number. Icons. The icons shown below are used in illustrations for designating part placement in the system described. A shaded area in the icon shows the location of the component or part being discussed. Documentation Titles Table 1 lists the books in the DEC 7000 and VAX 7000 documentation set. Table 2 lists other documents that you may find useful. DEC 7000 This section shows a sample boot of OpenVMS Alpha AXP from the RRD42 CD drive for DEC 7000 systems. The first step is issuing the show device command to determine the location of the RRD42. ix Table 1 DEC 7000/VAX 7000 Documentation Title Order Number Installation Kit EK7000BDK Site Preparation Guide EK7000BSP Installation Guide EK700EBIN Hardware User Information Kit EK7001BDK Operations Manual EK7000BOP Basic Troubleshooting EK7000BTS Service Information Kit·VAX 7000 EK7002ADK Platform Service Manual EK7000ASV System Service Manual EK7002ASV Pocket Service Guide EK7000APG Advanced Troubleshooting EK7001ATS Service Information Kit·DEC 7000 EK7002BDK Platform Service Manual EK7000ASV System Service Manual EK7002BSV Pocket Service Guide EK7700APG Advanced Troubleshooting EK7701ATS x Table 1 DEC 7000/VAX 7000 Documentation (Continued) Title Order Number Reference Manuals Console Reference Manual EK70C0BTM KA7AA CPU Technical Manual EKKA7AATM KN7AA CPU Technical Manual EKKN7AATM MS7AA Memory Technical Manual EKMS7AATM I/O System Technical Manual EK70I0ATM Platform Technical Manual EK7000ATM Upgrade Manuals KA7AA CPU Installation Guide EKKA7AAIN KN7AA CPU Installation Guide EKKN7AAIN MS7AA Memory Installation Guide EKMS7AAIN KZMSA Adapter Installation Guide EKKXMSXIN DWLMA XMI PIU Installation Guide EKDWLMAIN DWMBB VAXBI PIU Installation Guide EKDWMBBIN H7237 Battery PIU Installation Guide EKH7237IN H7263 Power Regulator Installation Guide EKH7263IN BA654 DSSI Disk PIU Installation Guide EKBA654IN BA655 SCSI Disk and Tape PIU Installation Guide EKBA655IN Removable Media Installation Guide EKTFRRDIN xi Table 2 Related Documents Title Order Number General Site Preparation Site Environmental Preparation Guide EKCSEPGMA System I/O Options BA350 DECstor/me Modular Storage Shelf Subsystem Configuration Guide EKBA350CG BA350 DECstor/me Modular Storage Shelf Subsystem User's Guide EKBA350UG BA350­LA DECstor/me Modular Storage Shelf User's Guide EK350LAUG CIXCD Interface User Guide EKCIXCDUG DEC FDDIcontroller 400 Installation/Problem Solving EKDEMFAIP DEC LANcontroller 400 Installation Guide EKDEMNAIN DEC LANcontroller 400 Technical Manual EKDEMNATM DSSI VAXcluster Installation and Troubleshooting Manual EK410AAMG InfoServer 150 Installation and Owner's Guide EKINFSVOM KDM70 Controller User Guide EKKDM70UG KFMSA Module Installation and User Manual EKKFMSAIM KFMSA Module Service Guide EKKFMSASV RRD42 Disc Drive Owner's Manual EKRRD42OM RF Series Integrated Storage Element User Guide EKRF72DUG TF85 Cartridge Tape Subsystem Owner's Manual EKOTF85OM TLZ06 Cassette Tape Drive Owner's Manual EKTLZ06OM xii Table 2 Related Documents (Continued) Title Order Number Operating System Manuals Alpha Architecture Reference Manual EYL520EDP DEC OSF/1 Guide to System Administration AAPJU7ATE DECnet for OpenVMS Network Management Utilities AAPQYAATK Guide to Installing DEC OSF/1 AAPS2DATE OpenVMS Alpha Version 1.0 Upgrade and Installation Manual AAPQYSATE VMS Upgrade and Installation Supplement: VAX 7000600 and VAX 10000600 Series AAPRAHATE VMS Network Control Program Manual AALA50ATE VMSclusters and Networking HSC Installation Manual EKHSCMNIN SC008 Star Coupler User's Guide EKSC008UG VAX Volume Shadowing Manual AAPBTVATE Peripherals Installing and Using the VT420 Video Terminal EKVT420UG LA75 Companion Printer Installation and User Guide EKLA75XUG xiii xiv System Troubleshooting 1­1 Chapter 1 System Troubleshooting This chapter describes system problems and their symptoms during power­up, booting, and normal operation. Sections include: · Troubleshooting During Power­Up · Troubleshooting During Booting · Troubleshooting a DSSI Plug­In Unit · Troubleshooting a SCSI Plug­In Unit · Troubleshooting an XMI Plug­In Unit · Troubleshooting a TF85 Tape Drive · Troubleshooting an RRD42 Compact Disk Drive · Air Pressure Sensor and Temperature Sensors 1­2 System Troubleshooting 1.1 Troubleshooting During Power­Up Figure 1­1 shows the power­up sequence and steps to take if a problem occurs. Figure 1­1 Power­Up Troubleshooting Flowchart System Troubleshooting 1­3 Troubleshooting steps during power­up are described in Figure 1­2. Figure 1­2 Power­Up Troubleshooting Steps For more information: Operations Manual Console Reference Manual 1­4 System Troubleshooting 1.2 Troubleshooting During Booting When booting fails, you can check several parameters. Figure 1­3 shows the boot sequence. Figure 1­4 shows the steps to take if a problem occurs during booting. If you are unable to correct the problem, call your Digital customer service engineer. Figure 1­3 Booting Troubleshooting Flowchart System Troubleshooting 1­5 Figure 1­4 Troubleshooting Steps During Booting For more information: Operations Manual 1­6 System Troubleshooting 1.3 Troubleshooting a DSSI Plug­In Unit Check the disk control panel. The control panel has four indicator switches. Table 1­5 lists the functions of the indicator switches. Figure 1­5 DSSI Disk Control Panel System Troubleshooting 1­7 Table 1­1 Indicator Switches on DSSI Disk Control Panel The Fault indicator switch goes on for approximately 10 seconds during power­up, and then goes off. If the Fault indicator switch stays on, press the switch to diagnose the problem (see Table 1­2). Table 1­2 DSSI Disk PIU Fault Diagnosis Indicator Switch Pushbutton Position Light Function DC Pwr (Green) Out In On Off DC power present. DC power not present. Ready (Green) In Out On Off Integrated storage element is on­line. Integrated storage element is off­line. Wrt Prot (Yellow) In Out On Off Write­protect enabled. Write­protect disabled. Fault (Red) Momentary Switch On Off Fault condition. Normal operation. Fault Indicator Switch When Pressed... Meaning On Slow Flash Integrated storage element cali­ brations being performed. On Fast Flash Disk control panel failure. Call your Digital customer service en­ gineer. For more information: RF Series Integrated Storage Element User Guide 1­8 System Troubleshooting 1.4 Troubleshooting a SCSI Plug­In Unit SCSI indicator LEDs are located on each disk drive and power supply. Table 1­3 and Table 1­4 list the functions of the LEDs shown in Figure 1­6 . Figure 1­6 SCSI Indicator LEDs System Troubleshooting 1­9 Table 1­3 SCSI Disk Drive LEDs Table 1­4 SCSI Power Supply LEDs If the power supply LEDs indicate a problem, call your Digital customer service engineer. Indicator LED LED State Meaning Green Off Flashing On No activity Activity Activity Yellow Off Flashing On1 Normal Spin up/spin down Not used. 1This LED state is not supported on DEC 7000 systems. Indicator LED LED State Meaning Green (left) Off On Shelf fault Shelf OK Green (right) Off On Power fault Power OK 1­10 System Troubleshooting 1.5 Troubleshooting an XMI Plug­In Unit You can perform several checks if you suspect a problem with an XMI plug­in unit. See Figure 1­7. If you are unable to correct the problem, call your Digital customer service engineer. Figure 1­7 Troubleshooting an XMI Plug­In Unit System Troubleshooting 1­11 In Example 1­1 an initialize command is issued, causing a system reset and self­test. Self­test results indicate a failing DWLMA adapter. See Chapter 2 for more information on the self­test display. Example 1­1 Sample Self­Test Display, Failing DWLMA Adapter P00>>> initialize ! Resets the entire system. Initializing the system... F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE # A M . . . . . P P TYP o + . . . . . + + ST1 . . . . . . . E B BPD o + . . . . . + + ST2 . . . . . . . E B BPD + + . . . . . + + ST3 . . . . . . . E B BPD . . . . . . . . . . . . . . C0 XMI ­ . . . . . . . . . . . . . . C1 . . . . . . . . . . . . . . C2 . . . . . . . . . . . . . . C3 . A0 . . . . . . . ILV . 128 . . . . . . . 128Mb Firmware Rev = V1.0­1625 SROM Rev = V1.0­0 SYS SN = GAO1234567 P00>>> 1 In Example 1­1 the IOP module passes self­test, as indicated by the plus sign (+) at node 8 on self­test line ST3. 2 The DWLMA adapter fails self­test, as indicated by the minus sign (-) displayed on the C0 XMI line. When a DWLMA fails self­test, the failure is reported, and the results of the I/O adapter self­tests are not displayed. 1 2 For more information: Console Reference Manual 1­12 System Troubleshooting 1.6 Troubleshooting a TF85 Tape Drive Check the controls and indicators on the TF85 tape drive. Table 1­5 lists the functions of the controls and indicators shown in Fig­ ure 1­8. Figure 1­8 TF85 Controls and Indicators System Troubleshooting 1­13 Table 1­5 TF85 Light Summary Light State Condition Green (Operate Handle) On Off Blinking OK to operate handle. Do not operate handle. Defective cartridge. Pull the handle to the open position and remove cartridge. Try another cartridge. Yellow (Tape in Use) Steady Blinking Drive ready. Drive in use. Orange (Write Protected) On Off Tape write protected. Tape write enabled. Orange (Use Cleaning Tape) On Off Drive needs cleaning. No cleaning needed. All four lights Blinking Drive fault. Reset by press­ ing the unload button. For more information: TF85 Cartridge Tape Subsystem Owner's Manual 1­14 System Troubleshooting 1.7 Troubleshooting an RRD42 Compact Disk Drive Table 1­6 lists the functions of the green LED on the RRD42 com­ pact disk (CD) drive. Figure 1­9 RRD42 CD Drive Control Panel Table 1­6 RRD42 LED Summary LED State Condition Green (Activity) Off On No activity Data is being transferred For more information: RRD42 Disc Drive Owner's Manual System Troubleshooting 1­15 1.8 Air Pressure Sensor and Temperature Sensors An air pressure sensor is located on the cabinet control logic (CCL) module and is connected to the LSB card cage by a tube. If the sensor detects a pressure differential, then the system power regulators are disabled. Figure 1­10 CCL Air Pressure Sensor The air pressure sensor monitors the pressure differential across the up­ per cabinet. If the air pressure drops below normal, all system power regulators are disabled and the control panel Fault light will blink. CAUTION: Do not place any materials on top of the cabinet. Doing so may cause your system to shut down. The system also has temperature sensors located on the system power regulators, the disk converter module, the PIU power regulators, and the CCL module. Self­Test 2­1 Chapter 2 Self­Test This chapter discusses the testing that the system performs and the record displayed at power­up and at a system reset. The console self­test display allows you to identify both passing and failing modules in the system. This chapter includes the following sections: · Self­Test Overview · Testing Sequence · Sample Self­Test Display · Self­Test Lines NODE # and TYP · Self­Test Lines ST and BPD · Self­Test Lines C0, C1, C2, and C3 · Self­Test Lines ILV and Mb · Self­Test Identification Line NOTE: The description of self­test results applies to VAX 7000 systems and DEC 7000 systems. 2­2 Self­Test 2.1 Self­Test Overview The system provides a record of its testing in the self­test display. The control panel Fault light and the module self­test LEDs also indicate success or failure. Figure 2­1 Determining Self­Test Results Self­Test 2­3 Following power­up and system reset, the system performs testing. Self­ test results are indicated by the following: · Fault light on the control panel · Self­test LEDs on the modules · Self­test display The self­test display is discussed in detail in this chapter. During system self­test, the yellow Fault light on the control panel lights. If a module fails self­test, the Fault light remains lit. If all modules pass self­test, the Fault light goes off. Each CPU and memory module has a green LED that lights when the module passes self­test. These LEDs can be viewed through the module enclosure from the front and rear of the cabinet when the doors are open. If a module fails self­test, its green LED does not light. I/O modules have yellow LEDs that light when each module in the I/O card cage passes self­test. These LEDs can be seen through the PIU enclosure. 2­4 Self­Test 2.2 Testing Sequence The self­test display shows the results of system self­test. The pass (+) or fail (-) status of each module is indicated. Figure 2­2 Testing Sequence Self­Test 2­5 During the first round of testing each module runs its own self­test and the results are shown on the ST1 line. The boot processor is then determined (indicated by a B on the first BPD line). This processor then generates the results of testing to this point ( ). NOTE: If a processor fails self­test (ST1) in a multiprocessor system, there is no indication of its failure in the self­test display. The failing processor is logically disconnected from the backplane to prevent faulty system operation. The processor failure is indicated by the control panel Fault light remaining lit after power­up. Next, the processors run a second round of tests using the memory mod­ ules. In this testing the processor that had been designated as boot proces­ sor could fail (as shown in Figure 2­2), so the boot processor is again deter­ mined. Results are displayed on the ST2 line ( 2 ). Finally, the processors run a third round of tests, the multiprocessing tests. Once again the boot processor is determined. The status of the boot processor and secondary processors is then displayed on the third BPD line ( 3 ). Results of the I/O adapter self­test are displayed next. The results are shown in columns 1 through E, which stand for XMI node numbers. The boot processor next configures memory and displays the configuration. Note that it is the boot processor determined at ( 3) that displays the lines after the third BPD line. The final line before the console prompt contains the boot processor's ROM revision and system serial number. Each line of the self­test display is described in detail in the following sec­ tions of this chapter. 1 2­6 Self­Test 2.3 Sample Self­Test Display The primary processor reports the results of self­test. Results are displayed on the console terminal, as shown in Figure 2­3. Figure 2­3 Self­Test Results Self­Test 2­7 The self­test display reflects the system configuration listed in Table 2­1 and Table 2­2. Each numbered item in the example is explained in Section 2.4 through Section 2.8. These sections assume the same system configu­ ration. Table 2­1 System Configuration for Figure 2­3 Table 2­2 I/O Subsystem Configuration for Figure 2­3 Module LSB Node # Module Type KA7AA 0 Processor; fails ST2 testing. KA7AA 1 Processor; operating as boot processor fol­ lowing ST2 testing. MS7AA 7 Memory (128 Mbytes). IOP 8 I/O adapter leading to I/O buses. Module XMI Node # Module Type I/O Channel C0 DWLMA 8 I/O adapter; fails self­test, no devices report. I/O Channel C1 DWLMA 8 I/O adapter; passes self­test. DEMNA E Ethernet adapter; passes self­ test. KFMSA 3 Disk adapter; fails self­test. 2­8 Self­Test 2.4 Self­Test Lines NODE # and TYP The first two lines of the self­test printout provide the node num­ ber identification (NODE #) and the type of module (TYP). Figure 2­4 Self­Test Results: NODE # and TYP Self­Test 2­9 The system configuration being tested is discussed in Section 2.3. See Ta­ ble 2­1. 1 The NODE # line lists the node numbers on the LSB and XMI buses. The nodes on this line are numbered in hexadecimal. Nodes 0 through 3 reflect the right­to­left position of the LSB slots as you view the LSB from the front of the cabinet. Nodes 4 through 8 reflect the right­to­ left position of the LSB slots as you view the LSB from the rear of the cabinet. Note that LSB entries use nodes 0 through 8, while the XMI has en­ tries in nodes 1 through E. The LSB has 9 slots. The LSB slot num­ bers and node numbers are identical. Each XMI bus has 14 slots. The XMI slot and node numbers are iden­ tical. Node numbers are 1 through E on the XMI. 2 The TYP line in the printout indicates the type of module at each LSB node: · An adapter: the I/O port module (A) · A memory module (M) · A processor (P) A period (.) indicates that the slot is not populated or that the module is not reporting. 1 2­10 Self­Test 2.5 Self­Test Lines ST and BPD The next six lines of the self­test display provide test information on the processors (ST1, ST2, and ST3) and boot processor designa­ tion (BPD). Figure 2­5 Self­Test Results: ST and BPD Self­Test 2­11 3 The ST1 line shows the results of self­test. This information is taken from the self­test passed bit in the LCNR register of each module. The entries are: · + (pass) · o (does not apply) NOTE: If a processor fails self­test (ST1) in a multiprocessor system, there is no indication of its failure in the self­test display. The failing processor is logically disconnected from the backplane to prevent faulty system operation. The processor failure is in­ dicated by the control panel Fault light remaining lit after power­up. Since the I/O port module does not have a module­resident self­test, its entry for the ST1 line is always "o". 4 The BPD line indicates boot processor designation. When the system goes through self­test, the processor with the lowest ID number that passes self­test (ST1 line is +) becomes the boot processor, unless you intervene. The results on the BPD line indicate: · The boot processor (B) · Processors eligible to become the boot processor (E) · Processors ineligible to become the boot processor (D) This BPD line is printed three times. After the first determination of the boot processor, the processors go through two more rounds of test­ ing. Since it is possible for a processor to pass self­test (at line ST1) and fail ST2 or ST3 testing, the processors again determine the boot processor following each round of tests. In Figure 2­5 the processor at node 0 failed self­test, so the processor at node 1 was chosen boot processor. 5 During the second round of testing (ST2) all processors run additional CPU tests involving memory. In Figure 2­5 results printed on the ST2 line indicate that the processor at node 0 failed ST2 (-), while the proc­ essor at node 1 passed ST2 (+). 6 During the third round of testing (ST3) all processors run multiproces­ sor tests, and the status of each processor is once again reported on the BPD line. The primary CPU also tests the IOP module at this time. 2­12 Self­Test 2.6 Self­Test Lines C0, C1, C2, and C3 The I/O channel lines (C0, C1, C2, and C3) of the self­test display provide information on the node numbers and self­test status for modules in the XMI card cages, which are connected to the system bus through the IOP module and the DWLMA adapter. Figure 2­6 Self­Test Results: C0, C1, C2, and C3 Self­Test 2­13 The system configuration being tested is discussed in Section 2.3. See Ta­ ble 2­1. The I/O channel lines, C0 through C3, indicate the: · I/O channel that connects the XMI I/O bus to the system bus · DWLMA adapter self­test results · XMI adapters' self­test results 7 In Figure 2­6 the DWLMA adapter accessed through C0 failed (-) self­test (C0 XMI -). 8 The other DWLMA adapter was accessed through C1 and passed (+) self­test (C1 XMI +); however, one XMI adapter, node 3, failed its self­ test. I/O channels C2 ( 9 ) and C3 ( 10 ) are not used in this system configu­ ration. When a DWLMA adapter passes self­test, each node on that XMI is in­ dicated by symbols + and -, indicating the self­test status for that node number on the XMI. A period (.) indicates that that node number is not used. When a DWLMA adapter fails self­test, the failure is re­ ported, and the XMI adapter self­tests are not displayed. NOTE: The XMI clock module, always node 7, is not reported in the self­test display. The show configuration command gives additional information on XMI I/O subsystems and adapters (see Section 3­1). 2­14 Self­Test 2.7 Self­Test Lines ILV and Mb The ILV line details the interleaving of the memories, and the Mb line gives the Mbytes of each memory module and the total size of the system memory. Figure 2­7 Self­Test Results: ILV and Mb Self­Test 2­15 The system configuration being tested is discussed in Section 2.3. See Ta­ ble 2­1. 11 The ILV line contains a memory interleave value (ILV) for each mem­ ory. The default memory configuration algorithm attempts to maxi­ mize memory interleaving; arrays on a single memory module are in­ terleaved by default. In Figure 2­7, the memory module at node 7 is in a two­way system interleave indicated by the first interleave set A. In­ formation on memory interleaving can be obtained by entering a show memory command: >>> show memory Set Node Size Base Addr Intlv Position A 7 128M 00000000 2­Way 0 A system with four memory modules is shown in the following exam­ ple: F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE # . B0 A3 A1 A0 . . . . ILV . 64 64 64 128. . . . 320Mb In this example, there are two memory interleave sets designated by the letters A and B. Note that there is no A2 designator on the ILV line; the memory at node 4 provides on­board interleaving, and so sup­ plies both the A0 memory word and the A2 memory word (which is not reported on the ILV line). Also note that different size memory arrays can be interleaved into a single set by "stacking" the smaller arrays to interleave with their larger counterparts. 12 The line after the ILV line displays the size of each configured memory module in the system and gives the total size of system memory. In Figure 2­7 the total size is 128 Mbytes. For more information: MS7AA Memory Technical Manual Console Reference Manual 2­16 Self­Test 2.8 Self­Test Identification Line The last line of the self­test display gives the firmware revision numbers, the SROM revision numbers, and the serial number of the machine. Figure 2­8 Self­Test Results: Identification Line Self­Test 2­17 The system configuration being tested is discussed in Section 2.3. See Ta­ ble 2­1. 13 In Figure 2­8 the Firmware Rev information, reported by the primary processor, indicates the version of the console firmware. 14 The SROM Rev information indicates the primary processor's serial ROM version. The serial ROM contains the first level of console, diag­ nostic, and bootstrap code. This code initializes the CPU programma­ ble features and diagnoses any faults detected along the bootstrap path and bootstrapping code execution out to the main console program (the second level of console, diagnostic, and bootstrap code). 15 SYS SN gives the system serial number. The serial number of the sys­ tem is stored in the EEPROM of each processor and also appears on the cabinet. For more information: KA7AA CPU Technical Manual KN7AA CPU Technical Manual Getting System Information 3­1 Chapter 3 Getting System Information This chapter discusses how to get information on your hardware configura­ tion and how to test your system. For more information, see the Console Reference Manual or enter the help command at your console terminal. Sections include: · Show Command · Show Configuration · Show Network · Show Device · Test Command · Testing the System · Testing a Subsystem · Testing a Module or a Device · Error Reports 3­2 Getting System Information 3.1 Show Command To get system information, enter a show configuration, show net­ work, or show device command. The show command output iden­ tifies the subsystem, module, or device you may want to test. The following sections explain the show command output. 3.1.1 Show Configuration Enter a show configuration command to display the system hard­ ware configuration. Example 3­1 Sample System Hardware Configuration P00>>> show configuration 1 Name Type Rev Mnemonic 2 LSB 0+ KA7AA (8002) 0000 ka7aa0 1+ KA7AA (8002) 0000 ka7aa1 7+ MS7AA (4000) 0000 ms7aa0 8+ IOP (2000) 0001 iop0 C0 XMI xmi0 3 8+ DWLMA (102A) 0104 dwlma0 C+ KDM70 (0C22) 1E11 kdm700 E+ DEMNA (0C03) 0802 demna0 4 C1 XMI xmi1 3 2+ KFMSA (0810) A2A6 kfmsa0 8+ DWLMA (102A) 0104 dwlma1 A+ CIXCD (0C05) 4611 cixcd0 C+ KDM70 (0C22) 1E11 kdm701 E+ DEMNA (0C03) 0802 demna1 Getting System Information 3­3 1 In Example 3­1 the operator enters a show configuration command to show the system hardware configuration. 2 The mnemonic for each processor, memory module, I/O adapter, and I/O subsystem is displayed in this column. You use mnemonics to identify the subsystem, module, or device you wish to test. 3 This system has two XMI I/O subsystems; in the mnemonics column they are identified as xmi0 and xmi1. To test the xmi0 subsystem, you would issue the command test xmi0 (see Section 3.2.2). 4 To test an I/O adapter, such as the DEMNA adapter, you would enter the command test demna0 (see Section 3.2.3). For more information: Console Reference Manual 3­4 Getting System Information 3.1.2 Show Network Enter a show network command to display network devices. Example 3­2 Sample Output of Show Network Command >>> show network 1 polling for units on demna0 2 ,slot 1, xmi0... exa0.0.0.1.0: 08­00­2B­25­D5­96 3 polling for units on demna1 4 ,slot 2, xmi1... exb0.0.0.2.1: 08­00­2B­25­D5­BB 5 >>> Getting System Information 3­5 1 In Example 3­2 the operator enters a show network command to show the network adapters in the system. 2 The first DEMNA adapter is identified by the demna0 mnemonic. This DEMNA adapter is in slot 1 of the I/O card cage connected to I/O chan­ nel 0. 3 The unit number for demna0 is exa0.0.0.1.0. The hardware address is 08­00­2B­25­D5­96. 4 The second DEMNA adapter is demna1. This adapter is in slot 2 of the I/O card cage connected to I/O channel 1. 5 The unit number for demna1 is exb0.0.0.2.1. The hardware address is 08­00­2B­25­D5­BB. 3­6 Getting System Information 3.1.3 Show Device Enter a show device command to display system devices. Example 3­3 Sample Output of Show Device Command >>> show device 1 polling for units on cixcd0, slot 2, xmi0... 2 dua73.13.0.2.0 $200$DUA73 (HSC000) RA70 dua77.13.0.2.0 $200$DUA77 (HSC000) RA70 dua20.14.0.2.0 $100$DUA20 (HSC000) RA82 dua21.14.0.2.0 $100$DUA21 (HSC000) RA82 dua22.14.0.2.0 $100$DUA22 (HSC000) RA82 dua23.14.0.2.0 $100$DUA23 (HSC000) RA82 dua24.14.0.2.0 $100$DUA24 (HSC000) RA82 dua72.14.0.2.0 $100$DUA72 (HSC000) RA82 dua73.14.0.2.0 $100$DUA73 (HSC000) RA82 dua90.14.0.2.0 $100$DUA90 (HSC000) RA90 dua91.14.0.2.0 $100$DUA91 (HSC000) RA90 dua92.14.0.2.0 $100$DUA92 (HSC000) RA90 dua93.14.0.2.0 $100$DUA93 (HSC000) RA90 >>> 3 4 5 6 Getting System Information 3­7 1 In Example 3­3 the operator enters a show device command to show all disks and tapes supported by the system. 2 The first I/O adapter polled is the CIXCD with the mnemonic cixcd0. This CIXCD is located in slot 2 of the I/O card cage. The I/O channel number is 0. 3 Device information is displayed. Device mnemonics are listed in the first column. In this example, all devices are disks. 4 The name of each disk as presented by the HSC controller is displayed in the second column. 5 The third column lists the HSC controller for each disk. All disks are connected to the system through the HSC000 controller. 6 Device types are listed in the fourth column. 3­8 Getting System Information 3.2 Test Command You can use the test command to test the entire system, an I/O sub­ system, a module, a group of devices, or a specific device. Enter a show configuration command to see a list of the subsystems and devices that you may want to test. Examples of the test command are shown in the following sections. Example 3­4 Sample Test Commands 1. >>> test ­q ! Runs a system test. Since a test ! run time was not specified, the ! entire system will be tested ! provided that testing does not ! exceed 10 minutes. Status messages ! will not be displayed. 2. >>> test kdm700 ­t 90 ! Runs the KDM700 self­test and then ! tests all devices associated with ! the KDM700 I/O adapter. Test run ! time is 90 seconds. 3. >>> test ms7aa* ! Tests all memory modules in the ! system. 4. >>> test xmi0 ! Tests the XMI0 I/O subsystem. 5. >>> test dua80.0.0.2.1 ! Tests the disk unit 80 on ! controller A. The disk adapter is ! located in slot 2 of the xmi1 card ! cage. Getting System Information 3­9 All test command options are described in the Console Reference Manual. Two helpful ones are outlined in Table 3­1. Environment variables com­ monly used with test are listed in Table 3­2. Table 3­1 Test Command Options Table 3­2 Test Command Environment Variables Option Meaning ­t Specifies the test run time in seconds. For a system test the default run time is 600 seconds (10 minutes). The run time for a device test is dependent upon the number and type of devices selected for testing. The ­t option takes any value between 30 and 99999999. ­q Disables the status messages displayed by default as exerciser processes are started and stopped during test­ ing. Environment Variable Meaning d_report Specifies the type of error report displayed. Values are summary and full. Summary is the default value. d_harderr Specifies the action taken when a hard error occurs. Values are halt or continue. Halt is the default value. d_softerr Specifies the action taken when a soft error oc­ curs. Values are halt or continue. Continue is the default value. 3­10 Getting System Information 3.2.1 Testing the System To test the entire system, enter the test command. Example 3­5 Sample Test Command, System Test P00>>> test ­t 180 1 Configuring system... Testing system... Type Ctrl/C to abort Starting floating point exerciser on ka7aa0 (id #57) 2 Starting floating point exerciser on ka7aa1 (id #58) Starting memory exerciser, running on ka7aa0 (id #59) Starting memory exerciser, running on ka7aa1 (id #60) Starting multiprocessor exerciser on ka7aa* (id #61) Starting network exerciser on exa0.0.0.4.0 in external mode (id #62) Starting network exerciser on exb0.0.0.5.0 in external mode (id #63) Starting network exerciser on exc0.0.0.4.1 in external mode (id #64) Starting device exerciser on dua10.14.0.1.0 (id# 67) Test time has expired... 3 Stopping floating point exerciser on ka7aa0 (id #57) 4 Stopping floating point exerciser on ka7aa1 (id #58) Stopping memory exerciser (id #59) Stopping memory exerciser (id #60) Stopping multiprocessor exerciser on ka7aa* (id #61) Stopping network exerciser on exa0.0.0.4.0 (id #62) Stopping network exerciser on exb0.0.0.5.0 (id #63) Stopping network exerciser on exc0.0.0.4.1 (id #64) Stopping device exerciser on dua10.14.0.1.0 (id# 67) The following devices were not tested: 5 dua11.14.0.1.0 P00>>> 6 Getting System Information 3­11 In Example 3­5: 1 At the console prompt, the operator enters a test ­t 180 command. The option ­t specifies a system test run time of 180 seconds. 2 Status messages indicate the start of the console­based exercisers. 3 The exercisers run for 180 seconds; not enough time to test the entire system, so this status message is displayed. 4 All exercisers are stopped, as indicated by the status messages. 5 Untested devices are reported. 6 The console prompt returns. 3­12 Getting System Information 3.2.2 Testing a Subsystem To test a portion of the system, such as an I/O subsystem, enter the test command and the I/O subsystem mnemonic. I/O subsystem mnemonics are displayed when you enter a show configuration command. Example 3­6 Sample Test Command, I/O Subsystem Test >>> test xmi0 1 Configuring xmi0 subsystem... Testing xmi0 Type Ctrl/C to abort KA7AA0 running module tests on DWLMA0 DWLMA0 module tests passed 2 Initializing DEMNA0 Initializing CIXCD0 Initializing KDM700 Initializing DEMFA0 DEMNA0 self­test passed 3 CIXCD0 self­test passed KDM700 self­test passed DEMFA0 self­test passed Starting network exerciser on exa0.0.0.4.0 in internal mode (id #31) Starting network exerciser on fxa0.0.0.e.0 in external mode (id #33) Starting device exerciser on dua0.0.0.6.0 (id #34) Starting device exerciser on dub0.0.0.a.0 (id #35) Starting device exerciser on dua1.1.0.6.0 (id #36) Starting device exerciser on dub1.1.0.a.0 (id #37) Starting device exerciser on dua2.2.0.6.0 (id #38) Stopping network exerciser on exa0.0.0.4.0 (id #31) Stopping network exerciser on fxa0.0.0.e.0 (id #33) Stopping device exerciser on dua0.0.0.6.0 (id #34) Stopping device exerciser on dub0.0.0.a.0 (id #35) Stopping device exerciser on dua1.1.0.6.0 (id #36) Stopping device exerciser on dub1.1.0.a.0 (id #37) Stopping device exerciser on dua2.2.0.6.0 (id #38) >>> 5 4 Getting System Information 3­13 1 At the console prompt, the operator enters a test xmi0 command to test all adapters and I/O devices on the XMI0 I/O bus. 2 The status message indicates that the DWLMA adapter passes all tests. Next, the adapters in the XMI0 card cage are initialized. 3 All XMI0 adapters pass self­test. 4 The status messages report that all exercisers started and completed. 5 The console prompt returns. 3­14 Getting System Information 3.2.3 Testing a Module or a Device To test a processor, memory module, or an I/O adapter and its as­ sociated devices, enter the test command and the correct mne­ monic. Mnemonics are displayed when you enter a show configu­ ration or a show device command. Example 3­7 Sample Test Command, I/O Adapter Test >>> test demna0 Configuring demna0... Testing demna0 Type Ctrl/C to abort Initializing DEMNA0 2 DEMNA0 self­test passed Starting network exerciser on exa0.0.0.4.0 in internal mode (id #30) Stopping network exerciser on exa0.0.0.4.0 (id #30) >>> In Example 3­7: 1 At the console prompt, the operator enters test demna0. The device mnemonic, demna0, was identified by issuing a show configuration command. 2 The DEMNA0 adapter is initialized and passes self­test. 3 The status messages report that the network exercisers started and completed. 1 3 Getting System Information 3­15 Example 3­8 Sample Test Command, Device Test >>> test dua2.2.0.8.0 ­q 1 Testing dua2.2.0.8.0 2 Type Ctrl/C to abort Done testing... >>> In Example 3­8: Example 3­9 Sample Test Command, Memory Module Test >>> test ms7aa0 1 Testing ms7aa0 Type Ctrl/C to abort Starting memory exerciser, running on kn7aa0 (id #77) 2 Stopping memory exerciser on kn7aa0 (id #77) Done testing... >>> In Example 3­9: 1 Enter test dua2.2.0.8.0 ­q. Testing is executed on the single disk with the device mnemonic dua2.2.0.8.0. The ­q option is used to disable status messages. 2 Testing begins. 1 Enter test ms7aa0. 2 The ms7aa0 memory module is tested by the memory exerciser, a se­ ries of tests executed from the kn7aa0 processor. 3­16 Getting System Information 3.3 Error Reports In the event of an error, either a summary or a full error report is displayed at the console. Error reports are specified by setting the d_report environment variable. See Example 3­10 and Example 3­11. Example 3­10 Sample Summary Error Report >>> set d_report summary ! Command to set the type of error ! report to summary (default value). >>> test kdm700 ! Command to test the kdm700 adapter ! and its devices. Configuring kdm700... Testing kdm700 Type Ctrl/C to abort Initializing KDM700 KDM700 self­test passed Starting device exerciser on duc1.0.0.12.0 (id #20) Starting device exerciser on duc2.0.0.12.0 (id #21) Starting device exerciser on duc4.0.0.12.0 (id #22) Bad MSCP status (4|0) received Failed to send Read to duc4.0.0.12.0 *** Hard Error ­ Error #1 on FRU: duc4.0.0.12.0 Error in read of 2097152 bytes at location 07E00000 from duc4.0.0.12.0. ID Program Device Pass Hard/Soft Test Time ­­­­­­­­ ­­­­­­­­ ­­­­­­­­­­­­­­­ ­­­­­­­­ ­­­­­­­­­ ­­­­ ­­­­­­­­ 481 dsk_ex duc4.0.0.12.0 18 1 0 1 12:07:01 ***End of Error*** 1 2 3 4 5 6 7 8 9 10 Getting System Information 3­17 In Example 3­10: 1 Testing begins on each disk. 2 A hard error, error #1, is reported on FRU duc4.0.0.12.0, a disk associ­ ated with the kdm700 adapter. The three types of errors reported are hard, soft, and fatal. The error number, in this case error #1, corre­ sponds to the location of the actual error report call within the source code for the failing diagnostic. The FRU, or field­replaceable unit, is duc4.0.0.12.0. 3 The process identification number (ID) is 481. This is the process ID of the failing diagnostic. 4 The program running when the error occurred is dsk_ex, or, the disk exerciser. 5 The target device selected for testing at the time of the error. The de­ vice name in this field may or may not match the device mnemonic dis­ played in the FRU field ( 2 ). 6 The current pass count, 18, is the number of passes executed when the error was detected. 7 The current hard error count is 1. The hard and soft ( 8 ) error counts are the number of errors detected and reported by the failing diagnos­ tic since the testing started. 9 In this example, the failing test number is 1. 10 The time stamp shows when the error occurred. 3­18 Getting System Information Example 3­11 Sample Full Error Report >>> set d_report full ! Command to set the type of ! error report to full. >>> test demna0 ! Command to test the DEMNA ! adapter with the mnemonic ! demna0. Configuring demna0... Testing demna0 Type Ctrl/C to abort Initializing demna0 demna0 self­test passed Starting network exerciser on exa0.0.0.1.0 (id #183) ***Hard Error ­ Error #15 on FRU: exa0.0.0.1.0 External loopback error, no packet received ID Program Device Pass Hard/Soft Test Time ­­­­­­­­ ­­­­­­­­ ­­­­­­­­­­­­­­­ ­­­­­­­­ ­­­­­­­­­ ­­­­ ­­­­­­­­ 183 net_ex exa0.0.0.1.0 5 1 0 1 12:31:01 Address Expected Received 1 ­­­­­­­­ ­­­­­­­­ ­­­­­­­­ 00240000 AAAAAAAA AAAAAAAA 00240004 55555555 45554555 2 00240008 CCCCCCCC CCCCCCCC 0024000C 33333333 33333333 00240010 88888888 88888888 00240014 77777777 77777777 00240018 FFFFFFFF FFFFFFFF *** End of Error *** Getting System Information 3­19 NOTE: Except for the extended error information shown in Example 3­11, the information shown in a full and a summary error report is the same. See Example 3­10 for a description of the common error re­ port entries. In Example 3­11: 1 This full error report shows a list of addresses and the expected and received data values for each address. 2 The expected value at address 00240004 was 55555555. The received value was 45554555. Power System Indicators A­1 Appendix A Power System Indicators This appendix describes the lights and indicators on the power modules. Sections include: · AC Input Box · Control Panel · System Power Regulator · XMI PIU Power Regulators · Cabinet Control Logic Module A­2 Power System Indicators A.1 AC Input Box The AC input box with circuit breaker is located in the upper left rear of the cabinet (see Figure A­1). The AC input box accepts three­phase power; the three leftmost indicators on the circuit breaker show the state of each pole (one pole per phase). If an indicator is green, the pole is in the off po­ sition or tripped due to an overload. If an indicator is red, the pole is in the on position and is not tripped. The fourth rightmost indicator reflects the mechanical position of the cir­ cuit breaker. The indicator is red when the circuit breaker is in the on posi­ tion and green when the circuit breaker is in the off position. NOTE: The function of the poles and indicators differs on the 202V AC in­ put box. If one pole trips, all poles will trip, including the fourth pole. All indicators will be green in this condition. Figure A­1 AC Input Box Power System Indicators A­3 A.2 Control Panel The control panel has three indicator lights and one keyswitch (see Figure A­2). You turn the keyswitch to Enable to power up the system. The Fault light blinks slowly, goes on momentarily during self­test, and then goes off. The Key On and Run lights should remain on. If the Fault light does not go off, there is a hardware problem. Call your Digital customer service engineer. Figure A­2 Control Panel A­4 Power System Indicators A.3 System Power Regulator Power regulators are located in the upper right front of the cabinet. A sys­ tem can have one, two, or three power regulators. Each power regulator has a Run light and a Fault light. Figure A­3 System Power Regulator Power System Indicators A­5 Table A­1 lists the functions of the power regulator indicators shown in Figure A­3. Table A­1 System Power Regulator Light Summary Run Light (Green) Fault Light (Yellow) Condition Off Off No AC power Off On Fatal fault Fast flash Off AC power present and keyswitch in Disable position On Fast flash Nonfatal fault On Slow flash Battery discharge mode On Off Normal operation A­6 Power System Indicators A.4 XMI PIU Power Regulators An XMI plug­in unit (PIU) has two power regulators, regulator A and regulator B (see Figure A­4). You can see the power regulators through the PIU enclosure when the front cabinet door is open. Both regulators have indicator lights. Regulator B also has a reset switch and an en­ able/disable switch for Digital customer service use only. Figure A­4 XMI PIU Power Regulators Power System Indicators A­7 Table A­2 lists the functions of the indicators shown in Figure A­4. Table A­2 XMI PIU Power Regulator Lights Light Color State Meaning MOD OK Green On Regulator is working. Off Regulator is not working. OC Yellow On Overcurrent condition has been de­ tected. The light turns on and stays on even if the fault condition no longer exists. OT Yellow On Temperature condition has been de­ tected. The light turns on and stays on even if the fault condition no longer exists. OV Yellow On Overvoltage condition has been de­ tected. The light turns on and stays on even if the fault condition no longer exists. 48V Green On 48V is present. A­8 Power System Indicators A.5 Cabinet Control Logic Module The cabinet control logic (CCL) module is located in the upper rear of the cabinet, behind the control panel. The CCL module has four PIU LEDs. At power­up, a PIU LED goes on to indicate that power is present in the PIU power regulators. The CCL module also has its own power LED to in­ dicate that power is present on the module. You can see the CCL LEDs when the rear door is open (see Figure A­5). Figure A­5 CCL Module LEDs Index­1 Index A AC input box, A­2 circuit breaker, A­2 indicators, A­2 Air pressure sensor, 1­16 B Booting, 1­4 troubleshooting during, 1­4 C CCL module, A­8 PIU LEDs, A­8 power LED, A­8 Console commands show configuration, 3­2 show device, 3­6 show network, 3­4 test, 3­8 environment variables, 3­9 examples of, 3­8 options, 3­9 Control panel, A­3 indicator lights, A­3 keyswitch, A­3 D DSSI plug­in unit, 1­6 control panel, 1­6 fault indicator switch, 1­7 E Error reports, 3­16 full, 3­18 summary, 3­16 M Memory interleaving, 2­15 size, 2­15 P Power regulators, A­4 indicator lights, A­5 Power­up, 1­2 troubleshooting during, 1­2 R RRD42 compact disk drive, 1­14 S SCSI plug­in unit, 1­8 indicator LEDs, 1­8 Self­test, 2­2 DWLMA, 2­13 explanation of sample configuration, 2­7 firmware version, 2­16 line ILV, 2­14 Mb, 2­14 NODE#, 2­8 TYP, 2­8 lines BPD, 2­10 C0, C1, C2, and C3, 2­12 ST1, ST2, and ST3, 2­10 module types, 2­9 node numbers, 2­9 Index­2 order of testing, 2­5 overview, 2­2 sample, 2­6 SROM version, 2­16 system identification, 2­16 T Temperature sensors, 1­17 Testing a device, 3­14 a module, 3­14 a subsystem, 3­12 the system, 3­10 TF85 tape drive controls and indicators, 1­12 X XMI PIU power regulators, A­6 indicator lights, A­6 XMI plug­in unit, 1­10 troubleshooting a, 1­10