1. Manuals
  2. Brands
  3. Digital Equipment Manuals
  4. Server
  5. DEC 10000
  6. Service manual

Digital Equipment DEC 10000 Service Manual

Axp system
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
DEC 10000 AXP System
VAX 10000
System Service Manual
Order Number EK–1002A–SV.001
This manual tells how to add or replace CPU and memory modules in a
DEC 10000 AXP or VAX 10000 system.
digital equipment corporation
maynard, massachusetts

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the DEC 10000 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Digital Equipment DEC 10000

Summary of Contents for Digital Equipment DEC 10000

  • Page 1 DEC 10000 AXP System VAX 10000 System Service Manual Order Number EK–1002A–SV.001 This manual tells how to add or replace CPU and memory modules in a DEC 10000 AXP or VAX 10000 system. digital equipment corporation maynard, massachusetts...
  • Page 2 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.

  • Page 3: Table Of Contents

    FEPROM Recovery—Hardware Requirements ....2-14 FEPROM Recovery—Software Requirements and Setup . 2-16 FEPROM Recovery—Procedure .......... 2-18 Chapter 3 Updating Firmware Booting LFU on a DEC 10000 System ........3-2 Booting LFU on a VAX 10000 System ........3-4 Show ..................3-6 List ..................3-8...
  • Page 4 Module Barcode ..............1-7 Removing a Module from the LSB Card Cage ...... 1-8 Inserting a Module in the LSB Card Cage ......1-10 Sample Hardware Requirements for Remote FEPROM Recovery ................2-14 Tables DEC 10000/VAX 10000 Documentation ......... ix...
  • Page 5 Related Documents ..............xi Field-Replaceable Units............1-6 EEPROM Environment Variables ........2-2...

  • Page 7: Preface

    Preface Intended Audience This manual is written for Digital customer service engineers and self- maintenance customers servicing DEC 10000 AXP or VAX 10000 systems. This manual is a follow-on to Basic Troubleshooting and Advanced Trou- bleshooting. Document Structure This manual uses a structured documentation design. Topics are organ- ized into small sections for efficient on-line and printed reference.

  • Page 8: Conventions Used In This Document

    Conventions Used in This Document Terminology. Unless specified otherwise, the use of "system" refers to either a DEC 10000 AXP or VAX 10000 system. The DEC 10000 AXP sys- tems use the Alpha AXP architecture. References in text use DEC 10000 to refer to DEC 10000 AXP systems.
  • Page 9 Table 1 DEC 10000/VAX 10000 Documentation Title Order Number Installation Kit EK–1000B–DK EK–1000B–SP Site Preparation Guide EK–100EB–IN Installation Guide EK–1001B–DK Hardware User Information Kit EK–1000B–OP Operations Manual EK–1000B–TS Basic Troubleshooting EK–1002A–DK Service Information Kit—VAX 10000 EK–1000A–SV Platform Service Manual EK–1002A–SV System Service Manual EK–1000A–PG...
  • Page 10 Table 1 DEC 10000/VAX 10000 Documentation (Continued) Title Order Number Reference Manuals EK–70C0B–TM Console Reference Manual EK–KA7AA–TM KA7AA CPU Technical Manual EK–KN7AA–TM KN7AA CPU Technical Manual EK–MS7AA–TM MS7AA Memory Technical Manual EK–70I0A–TM I/O System Technical Manual EK–7000A–TM Platform Technical Manual Upgrade Manuals EK–KA7AA–IN...
  • Page 11 Table 2 Related Documents Title Order Number General Site Preparation EK–CSEPG–MA Site Environmental Preparation Guide System I/O Options EK–BA350–CG BA350 Modular Storage Shelf Subsystem Configuration Guide EK–BA350–UG BA350 Modular Storage Shelf Subsystem User’s Guide EK–350LA–UG BA350-LA Modular Storage Shelf User’s Guide EK–CIXCD–UG CIXCD Interface User Guide EK–DEMFA–IP...
  • Page 12 Table 2 Related Documents (Continued) Title Order Number Operating System Manuals EY–L520E–DP Alpha Architecture Reference Manual AA–PJU7A–TE DEC OSF/1 Guide to System Administration AA–PQYAA–TK DECnet for OpenVMS Network Management Utilities AA–PS2DA–TE Guide to Installing DEC OSF/1 AA–PQYSA–TE OpenVMS Alpha Version 1.0 Upgrade and Installation Manual AA–PRAHA–TE VMS Upgrade and Installation Supplement:...

  • Page 13: Chapter 1 Adding Or Replacing Cpus And Memories

    Chapter 1 Adding or Replacing CPUs and Memories This chapter provides information on how to remove and install processor and memory modules in DEC 10000 and VAX 10000 systems. Sections in- clude: • What Is Required • LSB Configuration Rules •...

  • Page 14: What Is Required

    1.1 What Is Required Adding or replacing processor or memory modules is a simple op- eration. Afterward you must verify that the new modules are rec- ognized in the system. You may need to set system parameters. Figure 1-1 LSB Card Cage Slots System Cabinet...
  • Page 15 Processor and memory modules reside in the LSB card cage, a centerplane card cage in the system cabinet with nine slots for modules. The LSB card cage always contains an IOP module, a clock module, and at least one proc- essor and one memory module (see Figure 1-1).

  • Page 16: Lsb Configuration Rules

    1.2 LSB Configuration Rules The first CPU module is node 0, and the first memory module is at node 7. The LSB bus requires that an IOP module be at node 8. See Figure 1-2. Figure 1-2 LSB Configuration Rules Front Rear Power Filter...

  • Page 17: Sample Configuration-2 Processors, 4 Memories

    The LSB card cage (see Figure1-2) has nine slots. Slot numbers are equivalent to node numbers. Four slots are at the front of the cabinet (nodes 0 through 3, right to left), and five slots are at the rear (nodes 4 through 8, right to left).

  • Page 18: Identifying The Kernel Frus

    1.3 Identifying the Kernel FRUs Table 1-1 lists the field-replaceable units (FRUs) for DEC 10000 and VAX 10000 systems that are discussed in this book. Table 1-1 Field-Replaceable Units Option No. Part No. Description E2040-AB DEC 10000 CPU module KN7AA-AB...

  • Page 19: Module Barcode

    Each memory or processor board is enclosed in the module case, protect- ing the module electronics from static discharge. A barcode label gives in- formation about the module, including the module part number, revision level, and the module serial number (see Figure 1-4). Figure 1-4 Module Barcode E2043-AA...

  • Page 20: Removing A Module From The Lsb Card Cage

    1.4 Removing a Module from the LSB Card Cage Use the following procedure to remove a module from the LSB card cage for replacement or reconfiguration. Figure 1-5 Removing a Module from the LSB Card Cage BXB-0090B-92 1-8 Adding or Replacing CPUs and Memories...
  • Page 21 Perform an orderly shutdown of the system. Turn the keyswitch on the front control panel to the Disable position and wait for the control panel yellow Fault LED to stop flashing. When the Fault LED stops flashing, power has been removed from the LSB backplane and you may safely proceed.

  • Page 22: Inserting A Module In The Lsb Card Cage

    1.5 Inserting a Module in the LSB Card Cage Use the following procedure when replacing or adding a module in the system card cage during maintenance or upgrade. Figure 1-6 Inserting a Module in the LSB Card Cage BXB-0091A-92 1-10 Adding or Replacing CPUs and Memories...
  • Page 23 Follow Steps 1 through 6 in Section 1.4 and then: If you are adding a module, remove the filler module from the slot where you will install the new module. Hold the filler module firmly on the vertical piece closest to you and gently pull it out toward you. Place it aside for return.

  • Page 24: Verifying The System

    1.6 Verifying the System Power up the system and check that all processor and memory modules appear in the self-test display. Example 1-1 Self-Test Display NODE # C0 XMI + C1 XMI + . A1 A0 . .128 128 . 256Mb Firmware Rev = SROM Rev =...
  • Page 25 Power up the system by turning the keyswitch from Disable to either the Enable or Restart position. Power sequencing begins and the system runs self-test. Check the self-test display to make sure that the system recog- nizes the newly installed modules. Example 1-1 shows the self-test display of a system in which one processor and one memory module were added.

  • Page 27: Chapter 2 Servicing The Cpu

    Chapter 2 Servicing the CPU This chapter describes how to service a CPU in a DEC 10000 or a VAX 10000 system should it break or should new CPUs be added to a system. Some CPU firmware problems are covered in this chapter; others are cov- ered in Chapter 3.

  • Page 28: System Parameters

    Off or On Resets system and displays self-test results boot_reset during booting. Default is off for VAX 10000 and on for DEC 10000. The default device or device list from which bootdef_dev booting is attempted when no device name is specified by the boot command.
  • Page 29 Table 2-1 shows the permanent environment variables stored in EEPROM. Some of these variables must be set when either adding a CPU or replac- ing a broken one. You may view these variables by typing show * at the console prompt. Volatile environment variables are initialized by a system reset;...
  • Page 30 Applies only when using the test com- mand. dump_dev Null Device to which dump file is written if system crashes (DEC 10000 only). enable_audit If set to on, enables the generation of audit trail messages used to track boot to determine location of boot failure.
  • Page 31 Another important environment variable, not shown in Table 2-1, because it is not a default variable but may be defined by the customer, is a nick- name. Should the customer want to have a default boot path for a cluster and a different local one, a nickname variable may be used for that pur- pose.

  • Page 32: How To Replace The Only Processor

    2.2 How to Replace the Only Processor When replacing the only processor in a system, you must store the system ID and customized boot paths. If the customer changed console environment variables from the default values, you will want to set them as the customer wishes. Example 2-1 Replacing a Single Processor >>>...
  • Page 33 After you have removed and replaced the defective module, following the instructions in Chapter 1, take the following steps: Power up the system. Self-test is run and you need to decide whether the new CPU module is functioning properly. If it is not, try reseating the new CPU and/or refer to the Advanced Troubleshooting manual;...

  • Page 34: How To Replace The Boot Processor

    2.3 How to Replace the Boot Processor In cases where the boot processor in a multiprocessing system is the CPU that is in need of repair, you need to manipulate which CPU receives data from the console terminal. Example 2-2 Replacing the Boot Processor NODE # C0 XMI + C1 XMI +...
  • Page 35 There are at least two factors to consider when replacing a primary CPU: The desire to retain the system environment. The possibility that the new CPU is at a higher or lower firmware re- vision than other CPUs in the system. shows the mismatch mes- sage should the firmware differ between CPUs.

  • Page 36: How To Add A New Processor Or Replace A Secondary Processor

    2.4 How to Add a New Processor or Replace a Secondary Processor Add a new secondary in the slot to the left of the boot processor or other secondary processors. Example 2-3 Adding or Replacing a Secondary Processor NODE # C0 XMI + C1 XMI + .
  • Page 37 There are at least two factors to consider when adding or replacing a CPU: The desire to retain the system environment. The possibility that the new CPU is at a higher firmware revision than other CPUs in the system. shows the mismatch message should the firmware differ between CPUs.

  • Page 38: Build Eeprom Command

    2.5 Build EEPROM Command Should the EEPROM become corrupted, you can use the build eeprom command to recover. The build eeprom command is the proper response to the console error messages shown in Example 2-4. If the build eeprom command fails, return the module for re- pair.
  • Page 39 Most of the module unified 2-5-2.4 part number can also be found on the barcode. The first number is 80, the second for the DEC 10000 is E2040 and for the VAX 10000 is E2045, the third is a two-letter mod- ule variant, like AA, and the fourth is the hardware revision.

  • Page 40: Feprom Recovery-Hardware Requirements

    ROM forces a prompt, AXP- or VAX- 7000/10000-FRRC>, on the console terminal. Figure 2-1 Sample Hardware Requirements for Remote FEPROM Recovery InfoServer Source VAX Ethernet DEMNA DMB32 10000 System RRD42 (DEC 10000 only) RS232 Cable Console Port BXB-0005H-92 2-14 Servicing the CPU...
  • Page 41 • The AXP/VAX 10000 Console CD-ROM, with the console/diagnostic code on it. The file name for the console/diagnostic code is AXP7000_10000_CONSOLE_IMAGE.GROM for the DEC 10000 sys- tem and VAX7000_10000_CONSOLE_IMAGE.GROM for the VAX 10000 system. The serial line receive program in the serial ROM of the CPU is called FRRC (FEPROM recovery code).

  • Page 42: Feprom Recovery-Software Requirements And Setup

    2.7 FEPROM Recovery—Software Requirements and Setup On the source system you need to "bind" the RRD42 or InfoServer to a virtual disk container, mount it, and set the terminal speed to that of the target console. Example 2-5 Setting Up the Source System $ set term/speed=9600/perm txa3: # Set DMB32 port to # 9600 baud.
  • Page 43 Example 2-5 illustrates the steps needed to prepare Kermit with Open- VMS VAX. What you do is: First make sure that you have the hardware necessary to perform the task. Make sure you have the correct CD-ROM for the damaged system. Set the terminal speed on the source system to 9600.

  • Page 44: Feprom Recovery-Procedure

    2.8 FEPROM Recovery—Procedure After Kermit has been set up and you are ready to downline load the file, AXP or VAX7000_10000_CONSOLE_IMAGE.GROM, connect to the target system, prepare it to receive the file and then load it. The final steps are to copy the file into the FEPROMs and boot the system.
  • Page 45 Example 2-6 illustrates a VAX 10000 recovery. Follow the same steps for the DEC 10000, using a AXP7000_10000_console_image.grom file. At the Kermit prompt, connect to the target system. Here are two ex-...

  • Page 47: Chapter 3 Updating Firmware

    Both the LFU program and the firmware microcode images it writes are supplied on a CD-ROM. You start LFU on DEC 10000 systems by booting the RRD42. On VAX 10000 systems you start LFU by booting the Info- Server on your Ethernet.

  • Page 48: Booting Lfu On A Dec 10000 System

    3.1 Booting LFU on a DEC 10000 System LFU is supplied on the DEC 7000/10000 AXP Console CD- ROM (Part Number AG-PQW3*-RE, where * is the letter 10000 that denotes the disk revision). Make sure this CD-ROM is mounted in the RRD42 in-cabinet CD drive. Boot LFU from the CD-ROM.
  • Page 49 Use the show device command to find the name of the RRD42 CD drive. Enter the boot command to boot from the RRD42. The RRD42 has a device name of dka100. LFU starts, displays a summary of its commands, and issues its prompt (Function?).

  • Page 50: Booting Lfu On A Vax 10000 System

    3.2 Booting LFU on a VAX 10000 System LFU is supplied on the VAX 7000/10000 Console CD-ROM (Part Number AG-PQW1*-RE, where * is the letter that de- 10000 notes the disk revision). Make sure this CD-ROM is mounted in one of the system’s InfoServers. Boot the In- itial System Load (ISL) program, and select the service cor- responding to the console CD-ROM.
  • Page 51 Copyright Digital Equipment Corporation 1992 All Rights Reserved. Loadable Environment Rev: V1.0-1625 Jul 12 1992 10:50:56 ***** Loadable Firmware Update Utility ***** Version 2.1 16-jun-1992 ------------------------------------------------------------------- Function Description ------------------------------------------------------------------- Display Displays the system’s configuration table. Exit Return to loadable offline operating environment.

  • Page 52: Show

    3.3 Show The show command shows the current revision of firmware and hardware for every module in the system that contains microcode. In the display, each module that needs to be updated is indicated by a plus sign (+) following the device mnemonic. Example 3-3 Show Command Function? show Device Mnemonic(s)? ?
  • Page 53 If you type just the command show without a device mnemonic, LFU prompts for the device mnemonic. All the commands that require de- vice mnemonics will prompt. If you enter ? (or help) for the device, a table displays the syntax for specifying devices.

  • Page 54: List

    3.4 List The list command displays the inventory of update firmware on the CD-ROM. Only the devices listed at your terminal are sup- ported for firmware updates. Example 3-4 List Command Function? l Loadable Firmware Update Utility Version 2.1 Name Mnemonic Update Firmware Update Hardware...
  • Page 55 The list command shows the revisions of firmware corresponding to the revisions of hardware for each device. (There may be several hardware revisions for a particular device, but only one firmware re- vision corresponds to any hardware revision.) Comparing the output of the list and show commands helps you understand which devices should receive firmware updates.

  • Page 56: Update

    3.5 Update The update command writes new firmware from the CD-ROM to the module. Then LFU automatically verifies the update by read- ing the new firmware image from the module back into memory and comparing it with the CD-ROM image. Example 3-5 Update Command Function? update kn7aa0 cixcd0...
  • Page 57 Continue? [Y/(N)] y WARNING: updates may take several minutes to complete for each device. DO NOT ABORT! demna0 Updating to 6.6... Reading Device... Verifying 6.6... PASSED. Function? update demna* Update all demna? [Y/(N)] n Function? This command specifically requests firmware updates for the CPU and CIXCD modules.

  • Page 58: Exit

    3.6 Exit The exit command terminates the LFU program, causes system in- itialization and self-test, and returns to the system console prompt. Example 3-6 Exit Command Function? show Device Mnemonic(s)? exit Function? exit Initializing... NODE # C0 XMI + C1 XMI + .
  • Page 59 From within the "Device Mnemonic(s)?" prompt, exit returns to the Function prompt. At the Function prompt, exit causes the system to be initialized. The console prompt appears. Updating Firmware 3-13...

  • Page 60: Display And Verify Commands

    3.7 Display and Verify Commands Display and verify commands are used in special situations. Display shows the physical configuration. Verify repeats the veri- fication process performed by the update command. Example 3-7 Display and Verify Commands Function? disp Name Type Mnemonic FW Rev HW Rev...
  • Page 61 Display shows the system physical configuration. Display is equivalent to issuing the console command show configuration. Because it shows the LSB slot for each module, display can help you identify unknown devices. Verify reads the firmware from the module into memory and com- pares it with the update firmware on the CD-ROM.

  • Page 62: How To Update Corrupted Firmware

    3.8 How to Update Corrupted Firmware If LFU identifies a device as unknown, the firmware on the mod- ule is corrupted. The update command allows you to specify the correct device type so that new firmware can be written to the module.
  • Page 63 unknown0 Updating to 70.0... Reading Device... Verifying 70.0... PASSED. Function? exit Initializing... NODE # [self-test map appears] . A0 .256 256Mb Firmware Rev = V1.0-1625 SROM Rev = V1.0-0 SYS SN = GAO1234567 >>> sho config Name Type Mnemonic KN7AA (8001) 0000 kn7aa0...

  • Page 64: How To Modify Device Attributes

    3.9 How to Modify Device Attributes The modify command can change parameters stored in EEPROM on the following devices: KZMSA (DEC 10000 system), KFMSA (VAX 10000), DEC LANcontroller 400 (DEMNA), and CIXCD. The attributes are specific to each device. Example 3-9 Modify Command...
  • Page 65 Enter new value (HEX) or <CR> to keep present value: Secondary Lock Retries? [(0020)] Enter new value (HEX) or <CR> to keep present value: Modify DSSI Timeouts? [Y/(N)]n Modify DSSI Retries? [Y/(N)]n Modify XMI Timeouts? [Y/(N)]n Finished display/modify parameters? [(Y)/N]y Function? m demna0 demna0 Remote Boot:...
  • Page 66 The CIXCD has only one parameter: the hardware revision. You would need to modify the value only if the EEPROM had become cor- rupted. When you modify the KFMSA, LFU first displays all the parameters for both ports. You select which port to modify. LFU prompts for parameters by category.

  • Page 67: Appendix A Kermit Parameters

    Appendix A Kermit Parameters To transmit a file using Kermit, the following parameters must be set: Kermit-32> show all VMS Kermit-32 version 3.3.111 Block check type One character checksum Debugging Delay 5 (sec) Server sends NAKs every 75 seconds while waiting for a command Escape character 035 (octal)
  • Page 68 End of line character 015 (octal) Quoting character 043 (octal) 8-bit quoting character 046 (octal) Start of packet 001 (octal) Transmit parameters Delay 0.0 (sec) Echo Repeat quoting character 176 (octal) Kermit Parameters...
  • Page 69 Index software requirements, 2-16 FEPROM recovery code, 2-15 Attributes, setting device, 3-18, Field-replaceable units, 1-6 3-19 Firmware corrupted, 3-16 updating, 3-1 Booting Firmware revision of CPU, 2-9 DSSI VAXcluster, 3-2 FRU part numbers, 1-6 LFU, 3-2, 3-4 Build eeprom command, 2-12 InfoServer 2-15, 3-1, 3-4 Initialize command, 2-13 Configuration rules, LSB, 1-4...
  • Page 70 Replace boot processor, 2-8 only processor, 2-6 secondary processor, 2-10 RRD42, 2-15, 3-1, 3-3 Self-test display, 1-12 Set CPU command, 2-9 Set eeprom serial command, 2-6 Show command, LFU, 3-6 Show device command, 2-7 System parameters, how to set, 2-2 Update command, 2-9 Update command, LFU, 3-10 Verification, 1-12, 2-2...

Table of Contents