Alpha 1000 Betriebsanweisung

Stöbern Sie online oder laden Sie Betriebsanweisung nach Netzteile Alpha 1000 herunter. Alpha 1000 User`s guide Benutzerhandbuch

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 200
  • Inhaltsverzeichnis
  • FEHLERBEHEBUNG
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen

Inhaltsverzeichnis

Seite 1 - Service Guide

AlphaServer 1000AService GuideOrder Number: EK–ALPSV–SV. A01Digital Equipment CorporationMaynard, Massachusetts

Seite 3 - Contents

Table 5–4 (Cont.) Environment Variables Set During System ConfigurationVariable Attributes Functiontga_sync_green NV Sets the location of the SYNC sign

Seite 4 - 4 Error Log Analysis

the system by entering theinitcommand or pressing the Reset button.5.2 System Bus OptionsThe system bus interconnects the CPU and memory modules. Figu

Seite 5

5.2.1 CPU Daughter BoardAlphaServer 1000A systems use a CPU daughter board. The daughter boardprovides:• The DECchip 21064 or 21064A processor• 2 mega

Seite 6 - Examples

Table 5–5 provides the memory requirements and recommendations for eachoperating system.Table 5–5 Operating System Memory RequirementsOperating System

Seite 7

• Two serial ports with full modem control and the parallel port• The keyboard and mouse interface• CIRRUS VGA controller• The speaker interface• PCI-

Seite 8

5.5 ISA Bus OptionsThe ISA (Industry Standard Architecture) bus is an industry-standard, 16-bit I/Obus. The EISA bus is a superset of the well-establi

Seite 9

5.6 EISA Configuration UtilityWhenever you add or move EISA options or some ISA options in the system, youwill need to run a utility called the EISA Co

Seite 10

• If you are configuring an EISA bus that contains both ISA and EISAoptions, refer to Table 5–7.4. Locate the correct ECU diskette for your operating s

Seite 11 - Intended Audience

The system displays ‘‘loading ARC firmware.’’ When the firmware hasfinished loading, the ECU program is booted.3. Complete the ECU procedure according to

Seite 12 - Related Documentation

5.6.3 Configuring EISA OptionsEISA boards are recognized and configured automatically. Study Table 5–6 for asummary of steps to configure an EISA bus tha

Seite 13

PrefaceThis guide describes the procedures and tests used to service AlphaServer 1000Asystems. AlphaServer 1000A systems use a deskside ‘‘wide-tower’’

Seite 14

5.6.4 Configuring ISA OptionsISA boards are configured manually, whereas EISA boards are configured throughthe ECU software. Study Table 5–7 for a summar

Seite 15 - Troubleshooting Strategy

Table 5–7 (Cont.) Summary of Procedure for Configuring EISA Bus with ISAOptionsStep ExplanationReturn to the SRMconsole (Digital UNIX andOpenVMS system

Seite 16 - 1.1.1 Problem Categories

5.7.1 PCI-to-PCI BridgeAlphaServer 1000A systems have a PCI-to-PCI bridge (DECchip 21050) on themotherboard.• Physical PCI slots 11, 12, and 13 (prima

Seite 17

When configuring the StorageWorks shelf, note the following:• Narrow SCSI (8-bit) devices can be used in the wide StorageWorks shelf, aslong as the dev

Seite 18

5.8.3 SCSI Bus ConfigurationsTable 5–8 provides descriptions of the SCSI configurations available using single,dual, and triple controllers, as well as

Seite 19

Figure 5–7 Single Controller ConfigurationJ10J1J12J2J11J16J14J13J15J17J3MA00900W3W2W112-45490-0117-04021-0117-04233-01Bus ID 4Bus ID 5012345612-41667-0

Seite 20

Figure 5–8 Dual Controller Configuration with Split StorageWorks BackplaneJ10J1J12J2J11J16J14J13J15J17J3MA00950W3W2W112-45490-0117-04233-01Bus ID 4Bus

Seite 21

Figure 5–9 Triple Controller Configuration with Split StorageWorks BackplaneJ10J1J12J2J11J16J14J13J15J17J3MA00902W3W2W117-04022-0117-04233-01Bus ID 4Bu

Seite 22 - 1–8 Troubleshooting Strategy

5.9 Power Supply ConfigurationsAlphaServer 1000A systems offer added reliability with redundant power options,as well as UPS options.The power supplies

Seite 23 - 1.3 Information Services

Figure 5–10 Power Supply Configurations400 Watts DC or Less400 Watts DC or LessUPSMA00335SingleRedundantUPSThe H7290-AA power supply kit is used to ord

Seite 24 - 1–10 Troubleshooting Strategy

ConventionsThe following conventions are used in this guide:Convention MeaningReturnA key name enclosed in a box indicates that you press that key.Ctr

Seite 25 - Troubleshooting Strategy 1–11

Figure 5–11 Power Supply Cable ConnectionsSignal/Misc. Harness (15-Pin)(20-Pin)+ 5V Harness(24-Pin)+ 3.3V Harness+ 5V Harness(24-Pin)(20-Pin)+ 3.3V Ha

Seite 26

5.10 Console Port ConfigurationsPower-up information is typically displayed on the system’s console terminal. Theconsole terminal may be either a graph

Seite 27

serial Sets the power-up output to be displayed on the device that is connectedto the COM1 port at the rear of the system.Example:P00>>> set

Seite 28

5.10.3 set tga_sync_greenThe tga_sync_green environment variable sets the location of the SYNC signalgenerated by the ZLXp-E PCI graphics accelerator

Seite 29

5.10.5 Using a VGA Controller Other than the Standard On-BoardVGAWhen the system is configured to use a PCI- or EISA-based VGA controllerinstead of the

Seite 30

6AlphaServer 1000A FRU Removal andReplacementThis chapter describes the field-replaceable unit (FRU) removal and replacementprocedures for AlphaServer

Seite 31 - FAIL B:0 S:2

Table 6–1 AlphaServer 1000A FRUsPart # Description SectionCables17-03970-02 Floppy drive cable (34-pin) Figure 6–517-03971-01 OCP module cable (10-pin

Seite 32

Table 6–1 (Cont.) AlphaServer 1000A FRUsPart # Description SectionFans70-31350-01 92 mm fan Section 6.2.470-31351-01 120 mm fan Section 6.2.4Internal

Seite 33

Table 6–1 (Cont.) AlphaServer 1000A FRUsPart # Description SectionOther Modules and Components70-31348-01 Interlock switch Section 6.2.854-23499-01 Sy

Seite 34

Figure 6–1 FRUs, Front RightInterlockSwitchInterlock/ServerManagement CableTape DriveOCP ModuleOCP CableCDROM DriveDrivesFloppy DriveFloppy DriveCable

Seite 35 - 2.3 Power-Up Screen

• DECevent Analysis and Notification Utility for OpenVMS Alpha, User andReference Guide, AA-Q73LC-TE• DECevent Analysis and Notification Utility for Dig

Seite 36

Figure 6–2 FRUs, Rear LeftUpper FanSpeakerLower FanMemoryMA00930SCSI CablesPower CordMotherboardCPU Daughter BoardNVRAM Chip (E14)NVRAM Toy Clock Chip

Seite 37 - 2.3.1 Console Event Log

6.2 Removal and ReplacementThis section describes the procedures for removing and replacing FRUs forAlphaServer 1000 systems, which use the deskside ‘

Seite 38

Figure 6–4 Removing Top Cover and Side PanelsTop CoverRelease LatchMA009146–8 AlphaServer 1000A FRU Removal and Replacement

Seite 39

6.2.1 CablesThis section shows the routing for each cable in the system.Figure 6–5 Floppy Drive Cable (34-Pin)17-03970-02MA01420AlphaServer 1000A FRU

Seite 40

Figure 6–6 OCP Module Cable (10-Pin)17-03971-01MA01421Figure 6–7 Power CordMA003386–10 AlphaServer 1000A FRU Removal and Replacement

Seite 41 - 2.5 Storage Device LEDs

Table 6–2 lists the country-specific power cables.Table 6–2 Power Cord Order NumbersCountry Power Cord BN Number Digital NumberU.S., Japan, Canada BN09

Seite 42 - Activity LED

6.2.2 Power Supply DC Cable AssemblySTEP 1: REMOVE THE CABLE CHANNEL GUIDE.STEP 2: REMOVE THE POWER SUPPLY DC CABLE ASSEMBLY.The power supply DC cable

Seite 43

Figure 6–10 Power Supply DC Cable AssemblySignal/Misc. Harness (15-Pin)(20-Pin)+ 5V Harness(24-Pin)+ 3.3V Harness+ 5V Harness(24-Pin)(20-Pin)+ 3.3V Ha

Seite 44

Figure 6–11 Power Supply Storage Harness (12-Pin)Storage Harness(12-Pin)J12J13MA0142270-31346-016–14 AlphaServer 1000A FRU Removal and Replacement

Seite 45

Figure 6–12 Interlock/Server Management Cable (2-pin)MA00932J254AlphaServer 1000A FRU Removal and Replacement 6–15

Seite 47 - 2.8 Fail-Safe Loader

Figure 6–13 Internal StorageWorks Jumper Cable (68-Pin)J10J1J12J2J11J16J14J13J15J17J3MA01427W3W2W112-45490-0117-04021-0117-04233-0112-41667-0517-04022

Seite 48

Figure 6–14 Wide-SCSI (Controller to StorageWorks Shelf) Cable (68-Pin)J10J1J12J2J11J16J14J13J15J17J3MA01428W3W2W112-45490-0117-04022-0217-04233-0112-

Seite 49

J11 connector of the StorageWorks backplane. In Figure 6–15, just the17-04022-02 variant is used in a single bus configuration.Figure 6–15 Wide-SCSI (C

Seite 50 - 2.9 Power-Up Sequence

Figure 6–16 Wide-SCSI (J10 to Bulkhead Connector) Cable (68-Pin)J10J1J12J2J11J16J14J13J15J17J3MA01430W3W2W112-45490-0117-04022-0217-04233-0112-41667-0

Seite 51 - 2.10.1 Serial ROM Diagnostics

Figure 6–17 SCSI (Embedded 8-bit) Removable-Media Cable (50-Pin)J10J1J12J2J11J16J14J13J15J17J3MA01431W3W2W112-45490-0117-04022-0217-04233-0112-41667-0

Seite 52

6.2.3 CPU Daughter BoardFigure 6–18 Removing CPU Daughter BoardMA00312CrossbarRetainingScrewCPU CardHandleClipsWarning: CPU and memory modules have pa

Seite 53

6.2.4 FansSTEP 1: REMOVE THE CPU DAUGHTER BOARD AND ANY OTHER OPTIONSBLOCKING ACCESS TO THE FAN SCREWS.See Figure 6–18 for removing the CPU daughter b

Seite 54

6.2.5 StorageWorks DriveNoteIf the StorageWorks drives are plugged into an SWXCR-xx controller,you can ‘‘hot swap’’ drives; that is, you can add or re

Seite 55 - Running System Diagnostics

6.2.6 Internal StorageWorks BackplaneSTEP 1: REMOVE POWER SUPPLIES.Figure 6–21 Removing Power SupplyCurrent SharingHarness (3-Pin)Signal/Misc. Harness

Seite 56 - 3.2 Command Summary

STEP 2: REMOVE INTERNAL STORAGEWORKS BACKPLANE.Figure 6–22 Removing Internal StorageWorks BackplaneMA00934AlphaServer 1000A FRU Removal and Replacemen

Seite 57 - 3.3 Command Reference

1Troubleshooting StrategyThis chapter describes the troubleshooting strategy for AlphaServer 1000Asystems.• Section 1.1 provides questions to consider

Seite 58 - 3.3.1 test

6.2.7 Memory ModulesThe positions of the failing single-inline memory modules (SIMMs) are reportedby SROM power-up scripts (Section 2.2).Note• Bank 0

Seite 59

Warning: Memory and CPU modules have parts that operate at hightemperatures. Wait 2 minutes after power is removed before handlingthese modules.Cautio

Seite 60

NoteSIMMs can only be removed and installed in successive order. Forexample; to remove a SIMM at bank 0, SIMM 1, SIMMs 0 and 1 forbanks 3, 2, and 1 mu

Seite 61 - 3.3.2 cat el and more el

NoteWhen installing SIMMs, make sure that the SIMMs are fully seated. Thetwo latches on each SIMM connector should lock around the edges of theSIMMs.A

Seite 62 - 3.3.3 memory

6.2.8 Interlock SwitchFigure 6–26 Removing the Interlock Safety SwitchMA009356–30 AlphaServer 1000A FRU Removal and Replacement

Seite 63

6.2.9 MotherboardSTEP 1: RECORD THE POSITION OF EISA AND PCI OPTIONS.STEP 2: REMOVE EISA AND PCI OPTIONS.STEP 3: REMOVE CPU DAUGHTER BOARD.Figure 6–27

Seite 64 - 3.3.4 netew

Figure 6–28 Removing CPU Daughter BoardMA00312CrossbarRetainingScrewCPU CardHandleClipsWarning: CPU and memory modules have parts that operate at high

Seite 65 - Testing an Ethernet Port:

Figure 6–29 Removing MotherboardMA0143212AlphaServer 1000A FRU Removal and Replacement 6–33

Seite 66 - 3.3.5 network

STEP 5: MOVE THE NVRAM CHIP (E14) AND NVRAM TOY CHIP (E78) TO THENEW MOTHERBOARD.Move the socketed NVRAM chip (position E14) and NVRAM TOY chip (E78)

Seite 67

Figure 6–30 Motherboard LayoutMemory ModuleConnectors (20)CPU ModuleConnectorPower ConnectorsDiskette DriveConnectorUpper FanConnectorLower Fan Connec

Seite 68 - 3.3.6 net -s

1.1.1 Problem CategoriesSystem problems can be classified into the following five categories. Using thesecategories, you can quickly determine a startin

Seite 69 - 3.3.7 net -ic

6.2.10 NVRAM Chip (E14) and NVRAM TOY Clock Chip (E78)See Figure 6–30 for the motherboard layout.NoteThe NVRAM TOY clock chip contains the os_type env

Seite 70 - 3.3.8 kill and kill_diags

Figure 6–32 Removing Front PanelRemoveScrewsRemoveHidden ScrewsMA00307AlphaServer 1000A FRU Removal and Replacement 6–37

Seite 71 - 3.3.9 show_status

Figure 6–33 Removing the OCP ModuleMA01423Black/Red(To InterlockSwitch)Green/Yellow(To Motherboard)J2546–38 AlphaServer 1000A FRU Removal and Replacem

Seite 72 - 3.5 DEC VET

6.2.12 Power SupplySTEP 1: DISCONNECT POWER SUPPLY CABLES.STEP 2: REMOVE POWER SUPPLY.Figure 6–34 Removing Power SupplyCurrent SharingHarness (3-Pin)S

Seite 73 - Error Log Analysis

6.2.13 SpeakerFigure 6–35 Removing SpeakerMA014246–40 AlphaServer 1000A FRU Removal and Replacement

Seite 74

6.2.14 Removable MediaFigure 6–36 Removing a CD–ROM DriveMA00324AlphaServer 1000A FRU Removal and Replacement 6–41

Seite 75 - Error Log Analysis 4–3

Figure 6–37 Removing a Tape DriveMA003256–42 AlphaServer 1000A FRU Removal and Replacement

Seite 76 - 4–4 Error Log Analysis

Figure 6–38 Removing a Floppy DriveMA00326AlphaServer 1000A FRU Removal and Replacement 6–43

Seite 78 - 4–6 Error Log Analysis

ADefault Jumper SettingsThis appendix provides the location and default setting for all jumpers inAlphaServer 1000A systems:• Section A.1 provides loc

Seite 79 - System Configuration and Setup

Table 1–1 Diagnostic Flow for Power ProblemsSymptom ActionSystem does not power on.• Check the power source and power cord.• Check that the system’s t

Seite 80 - 5.1.1 System Firmware

A.1 Motherboard JumpersFigure A–1 shows the location and default settings for jumpers located on themotherboard.Figure A–1 Motherboard Jumpers (Defaul

Seite 81 - >>>

Jumper Name Description Default SettingJ16 Large Fan Allows the large fan to bedisabled to accommodate thealternative enclosures.This jumper is notins

Seite 82 - >>> init

A.2 CPU Daughter Board (J3 and J4) Supported SettingsFigure A–2 shows the supported AlphaServer 1000A 4/266 settings for the J3 andJ4 jumpers on the C

Seite 83

Figure A–3 AlphaServer 1000A 4/233 CPU Daughter Board (Jumpers J3 andJ4)MA00791J3J4Supported settings:• J4 Jumper:OffOnOffOffOn• J3 Jumper:OffDefault

Seite 84

A.3 CPU Daughter Board (J1 Jumper)Figure A–4 shows the default setting for the J1 jumper on the CPU daughterboard. For information on SROM tests and t

Seite 85

Glossary10Base-T Ethernet networkIEEE standard 802.3-compliant Ethernet products used for local distribution ofdata. These networking products charact

Seite 86

backup cacheA second, very fast cache memory that is closely coupled with the processor.bandwidthThe rate of data transfer in a bus or I/O channel. Th

Seite 87 - Digital UNIX and OpenVMS

bystanderA system bus node (CPU or memory) that is not addressed by a current systembus commander.byteA group of eight contiguous bits starting on an

Seite 88

clusterA group of networked computers that communicate over a common interface.The systems in the cluster share resources, and software programs work

Seite 89 - Example:

data cacheA high-speed cache memory reserved for the storage of data. Abbreviated asD-cache.DEC VETDigital DEC Verifier and Exerciser Tool. A multipurp

Seite 90

Table 1–2 Diagnostic Flow for Problems Getting to Console ModeSymptom ActionPower-up screen is not displayed. Interpret the error beep codes at power-

Seite 91

ECCError correction code. Code and algorithms used by logic to facilitate errordetection and correction.EEPROMElectrically erasable programmable read-

Seite 92

FIBFlexible interconnect bridge. A converter that allows the expansion of the systemenclosure to other DSSI devices and systems.field-replaceable unitA

Seite 93

instruction cacheA high-speed cache memory reserved for the storage of instructions. Abbreviatedas I-cache.interrupt request lines (IRQs)Bus signals t

Seite 94 - Key to variable attributes:

MAUMedium attachment unit. On an Ethernet LAN, a device that converts theencoded data signals from various cabling media (for example, fiber optic, coa

Seite 95

NVRAMNonvolatile random-access memory. Memory that retains its information in theabsence of power.OCPOperator control panel.open systemA system that i

Seite 96

portabilityThe degree to which a software application can be easily moved from onecomputing environment to another.portingAdapting a given body of cod

Seite 97

reliabilityThe probability a device or system will not fail to perform its intended functionsduring a specified time.responderIn any particular bus tra

Seite 98

SRMUser interface to console firmware for operating systems that expect firmwarecompliance with the Alpha System Reference Manual (SRM).storage arrayA g

Seite 99

test-directed diagnostics (TDDs)An approach to diagnosing computer system problems whereby error data loggedby diagnostic programs resident in read-on

Seite 100 - Whenever you use the

write backA cache management technique in which data from a write operation to cache iswritten into main memory only when the data in cache must be ov

Seite 101 - 5.2 System Bus Options

Table 1–3 Diagnostic Flow for Problems Reported by the Console ProgramSymptom ActionPower-up tests do not complete. Interpret the error beep codes at

Seite 103 - 5.3 Motherboard

IndexAA: environment variable, 5–7AC power-up sequence, 2–24Acceptance testing, 3–18arc command, 5–4ARC interface, 5–3switching to SRM from, 5–4AUTOLO

Seite 104 - 5.4 EISA Bus Options

Console event log, 2–11Console firmwarediagnostics, 2–26Digital UNIX, 5–3OpenVMS, 5–3Windows NT, 5–3Console interfacesswitching between, 5–4Console out

Seite 105 - 5.5 ISA Bus Options

Environment variables set during systemconfiguration, 5–16Errorhandling, 1–7logging, 1–7Error formattersDECevent, 4–5Error log translationDigital UNIX,

Seite 106 - 5.6 EISA Configuration Utility

Logsevent, 1–7Loopback tests, 1–8COM2 and parallel ports, 3–4command summary, 3–3MMachine check/interrupts, 4–2processor, 4–2processor corrected, 4–2s

Seite 107 - 5.6.2 How to Start the ECU

RRAIDdiagnostic flow, 2–14RAID problems, 2–14Removable mediastorage problems, 2–12ROM-based diagnostics (RBDs), 1–7diagnostic-related commands, 3–3perf

Seite 108

Troubleshooting (cont’d)EISA problems, 2–18error report formatter, 1–7errors reported by operating system,1–7interpreting error beep codes, 2–2mass st

Seite 109 - 5.6.3 Configuring EISA Options

How to Order Additional DocumentationTechnical SupportIf you need help deciding which documentation best meets your needs, call 800-DIGITAL(800-344-48

Seite 111 - 5.7 PCI Bus Options

Reader’s Comments AlphaServer 1000AService GuideEK–ALPSV–SV. A01Your comments and suggestions help us improve the quality of our publications.Thank yo

Seite 112 - 5.8 SCSI Buses

First Printing, March 1996Digital Equipment Corporation makes no representations that the use of its products in themanner described in this publicati

Seite 113 - 5.8.2 External SCSI Expansion

Table 1–4 Diagnostic Flow for Boot ProblemsSymptom ActionSystem cannot find boot device. Check the system configuration for the correct deviceparameters

Seite 114 - 5.8.3 SCSI Bus Configurations

Do Not Tear – Fold Here and TapeTMBUSINESS REPLY MAILFIRST CLASS PERMIT NO. 33 MAYNARD MASS.POSTAGE WILL BE PAID BY ADDRESSEENo PostageNecessaryIf Mai

Seite 115

Table 1–5 Diagnostic Flow for Errors Reported by the Operating SystemSymptom ActionSystem is hung or has crashed. Examine the crash dump file.Refer to

Seite 116

RECOMMENDED USE: ROM-based diagnostics are the primary means oftesting the console environment and diagnosing the CPU, memory, Ethernet,I/O buses, and

Seite 117

Crash DumpsFor fatal errors, such as fatal bugchecks, Digital UNIX and OpenVMSoperating systems will save the contents of memory to a crash dump file.R

Seite 118

ECU RevisionsThe EISA Configuration Utility (ECU) is used for configuring EISA options onAlphaServer systems. Systems are shipped with an ECU kit, which

Seite 119

You can obtain information about hardware configurations for theAlphaServer 1000A from the Digital Systems and Options Catalog. Thecatalog is regularly

Seite 121 - 5.10.1 set console

2Power-Up Diagnostics and DisplayThis chapter provides information on how to interpret error beep codes andthe power-up display on the console screen.

Seite 122 - 5.10.2 set tt_allow_login

2.1 Interpreting Error Beep CodesIf errors are detected at power-up, audible beep codes are emitted from thesystem. For example, if the SROM code coul

Seite 123 - 5.10.3 set tga_sync_green

Table 2–1 (Cont.) Interpreting Error Beep CodesBeepCode Problem Corrective Action1-3-3 No usable memory detected.1. Verify that the memory modulesare

Seite 124

ContentsPreface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi1 Troubleshooting Strategy1.1 Troubl

Seite 125 - Replacement

Table 2–1 (Cont.) Interpreting Error Beep CodesBeepCode Problem Corrective Action3-3-1 Generic system failure. Possible problemsources include the TOY

Seite 126

Table 2–2 SROM Memory Tests, CPU Jumper J1Bank# Test Description Test Results3 Cache Test: Testsbackup cache.Test status displays on OCP:...done.If t

Seite 127

Table 2–2 (Cont.) SROM Memory Tests, CPU Jumper J1Bank# Test Description Test Results6 Memory Test,Cache Enabled:Tests memory withbackup and datacache

Seite 128

Table 2–2 (Cont.) SROM Memory Tests, CPU Jumper J1Bank# Test Description Test Results4 Backup Cache Test:Tests backup cachealternatively withdata cach

Seite 129 - Figure 6–1 FRUs, Front Right

Figure 2–1 Jumper J1 on the CPU Daughter BoardMA00926J176543210Bank Jumper Setting0 Standard boot setting (AlphaServer 1000 systems)1 Standard boot se

Seite 130 - Figure 6–2 FRUs, Rear Left

Figure 2–2 AlphaServer 1000A Memory LayoutBank 3Bank 2Bank 1Bank 0ECC BanksMA00327SIMM 3SIMM 2SIMM 1SIMM 0ECC SIMM for Bank 2ECC SIMM for Bank 0ECC SI

Seite 131 - 6.2 Removal and Replacement

Table 2–3 Console Power-Up Countdown Description and Field ReplaceableUnits (FRUs)CountdownNumber Description Likely FRUff Console initialization star

Seite 132 - Release Latch

Windows NT SystemsThe Windows NT operating system is supported by the ARC firmware (seeSection 5.1.1). Systems using Windows NT power up to the ARC boo

Seite 133 - 6.2.1 Cables

2.4 Mass Storage Problems Indicated at Power-UpMass storage failures at power-up are usually indicated by read fail messages.Other problems are indica

Seite 134 - Figure 6–7 Power Cord

Table 2–4 (Cont.) Mass Storage ProblemsProblem Symptom Corrective ActionMissing or loosecables. Drives notproperly seated onStorageWorks shelfActivity

Seite 135

3 Running System Diagnostics3.1 Running ROM-Based Diagnostics . . . . . . . . . . . . . . . . . . . 3–13.2 Command Summary . . . . . . . . . . . . . .

Seite 136

Table 2–4 (Cont.) Mass Storage ProblemsProblem Symptom Corrective ActionSCSI storage controllerfailureProblems persist aftereliminating the problemsou

Seite 137 - Assembly

Table 2–5 (Cont.) Troubleshooting RAID ProblemsSymptom ActionCannot access disks connected tothe RAID subsystem on WindowsNT systems.On Windows NT sys

Seite 138 - 70-31346-01

Figure 2–3 StorageWorks Disk Drive LEDs (SCSI)ActivityFaultMA00927Figure 2–4 Floppy Drive Activity LEDMA00330Activity LED2–16 Power-Up Diagnostics and

Seite 139

Figure 2–5 CD–ROM Drive Activity LEDActivity LEDMA00333Power-Up Diagnostics and Display 2–17

Seite 140 - Backplane

2.6 EISA Bus Problems Indicated at Power-UpEISA bus failures at power-up are usually indicated by the following messagesdisplayed during power-up:EISA

Seite 141

2.6.1 Additional EISA Troubleshooting TipsThe following tips can aid in isolating EISA bus problems.• Peripheral device controllers need to be seated

Seite 142

2.7 PCI Bus Problems Indicated at Power-UpPCI bus failures at power-up are usually indicated by the inability of the systemto see the device. Table 2–

Seite 143

ftp://ftp.digital.com/pub/DEC/Alpha/systems/http://www.service.digital.com/alpha/server/2.8 Fail-Safe LoaderThe fail-safe loader (FSL) is a redundant

Seite 144

2.8.2 Activating the Fail-Safe LoaderTo activate the FSL:1. Install the jumper at bank 7 of the J1 jumper on the CPU daughter board(Figure 2–6). The j

Seite 145 - 6.2.3 CPU Daughter Board

Figure 2–6 Jumper J1 on the CPU Daughter BoardMA00926J176543210Bank Jumper Setting0 Standard boot setting (AlphaServer 1000 systems)1 Standard boot se

Seite 146 - 6.2.4 Fans

5.2.2 Memory Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–245.3 Motherboard . . . . . . . . . . . . . . . . . . . . . . . . . .

Seite 147 - 6.2.5 StorageWorks Drive

2.9 Power-Up SequenceDuring the AlphaServer 1000A power-up sequence, the power supplies arestabilized and the system is initialized and tested through

Seite 148 - 3.5 mm (2)

2.9.2 DC Power-Up SequenceDC power is applied to the system with the DC On/Off button on the operatorcontrol panel.A summary of the DC power-up sequen

Seite 149

3. Test the system bus to PCI bus bridge and system bus to EISA bus bridge. Ifthe PCI bridge fails or EISA bridge fails, an audible error beep code (3

Seite 150 - 6.2.7 Memory Modules

4. Run exercisers on the drives currently seen by the system.NoteThis step does not ensure that all disks in the system will be tested orthat any devi

Seite 152

3Running System DiagnosticsThis chapter provides information on how to run system diagnostics.• Section 3.1 describes how to run ROM-based diagnostics

Seite 153

3.2 Command SummaryTable 3–1 provides a summary of the diagnostic and related commands.Table 3–1 Summary of Diagnostic and Related CommandsCommand Fun

Seite 154 - 6.2.8 Interlock Switch

Table 3–1 (Cont.) Summary of Diagnostic and Related CommandsCommand Function ReferenceLoopback Testingtest lb Conducts loopback tests for COM2 and the

Seite 155 - 6.2.9 Motherboard

3.3.1 testThetestcommand runs firmware diagnostics for the entire core system. Thetests are run concurrently in the background. Fatal errors are report

Seite 156

Thetestscript tests devices in the following order:1. Console loopback tests if lb argument is specified: COM2 serial port andparallel port.2. Network

Seite 157

6.2.14 Removable Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–41A Default Jumper SettingsA.1 Motherboard Jumpers . . . . . . . .

Seite 158

Testing the memoryTesting parallel portTesting the SCSI DisksNon-destructive Test of the Floppy started dka400.4.0.6.0 has no mediapresent or is disab

Seite 159 - ECC Banks

3.3.2 cat el and more elThecat elandmore elcommands display the current contents of the consoleevent log. Status and error messages (if problems occur

Seite 160 - 6.2.11 OCP Module

3.3.3 memoryThememorycommand tests memory by running a memory exerciser each time thecommand is entered. The exercisers are run in the background and

Seite 161

The following is an example with a memory compare error indicating bad SIMMs.>>> memory>>> memory>>> memory*** Hard Error -

Seite 162

3.3.4 netewThenetewcommand is used to run MOP loopback tests for any EISA- or PCI-based ew* (DECchip 21040, TULIP) Ethernet ports. The command can als

Seite 163 - 6.2.12 Power Supply

Testing an Ethernet Port:>>> netew>>> show_statusID Program Device Pass Hard/Soft Bytes Written Bytes Read-------- ------------ ----

Seite 164 - 6.2.13 Speaker

3.3.5 networkThenetworkcommand is used to run MOP loopback tests for any EISA- or PCI-based er* (DEC 4220, LANCE) Ethernet ports. The command can also

Seite 165 - 6.2.14 Removable Media

Testing an Ethernet Port:>>> network>>> show_statusID Program Device Pass Hard/Soft Bytes Written Bytes Read-------- ------------ --

Seite 166

3.3.6 net -sThenet -scommand displays the MOP counters for the specified Ethernet port.Synopsis:net -s ewa0Example:>>> net -s ewa0Status count

Seite 167

3.3.7 net -icThenet -iccommand initializes the MOP counters for the specified Ethernetport.Synopsis:net -ic ewa0Example:>>> net -ic ewa0>&g

Seite 168

6–2 FRUs, Rear Left . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–66–3 Opening Front Door . . . . . . . . . . . . . . . . . . . . . .

Seite 169 - Default Jumper Settings

3.3.8 kill and kill_diagsThekillandkill_diagscommands terminate diagnostics that are currentlyexecuting .NoteA serial loopback connector (12-27351-01)

Seite 170 - A–2 Default Jumper Settings

3.3.9 show_statusTheshow_statuscommand reports one line of information per executingdiagnostic. The information includes ID, diagnostic program, devic

Seite 171

3.4 Acceptance Testing and InitializationPerform the acceptance testing procedure listed below after installing a system orwhenever adding or replacin

Seite 172 - A–4 Default Jumper Settings

4Error Log AnalysisThis chapter provides information on how to interpret error logs reported by theoperating system.• Section 4.1 describes machine ch

Seite 173 - Default Jumper Settings A–5

Table 4–1 AlphaServer 1000 Fault Detection and CorrectionComponent Fault Detection/Correction CapabilityKN22A Processor ModuleDECchip 21064 and 21064A

Seite 174

Processor Machine Check (SCB: 670)Processor machine check errors are fatal system errors that result in a systemcrash. The error handling code for the

Seite 175 - Glossary

• Invalid page table lookup (scatter gather)• Memory cycle error• B-cache tag address parity error• B-cache tag control parity error• Non-existent mem

Seite 176 - Glossary–2

4.3 Event Record TranslationSystems running Digital UNIX and OpenVMS operating systems use theDECevent management utility to translate events into ASC

Seite 177 - Glossary–3

System faults can be isolated by examining translated system error logs orusing the DECevent Analysis and Notification Utility. Refer to the DECeventAn

Seite 178 - Glossary–4

5System Configuration and SetupThis chapter provides configuration and setup information for AlphaServer 1000Asystems and system options.• Section 5.1 d

Seite 179 - Glossary–5

6–35 Removing Speaker . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–406–36 Removing a CD–ROM Drive . . . . . . . . . . . . . . . . . . . .

Seite 180 - Glossary–6

5.1 Verifying System ConfigurationFigure 5–1 illustrates the system architecture for AlphaServer 1000A systems.Figure 5–1 System Architecture: AlphaSer

Seite 181 - Glossary–7

SRM Command Line InterfaceSystems running Digital UNIX or OpenVMS access the SRM firmware through acommand line interface (CLI). The CLI is a UNIX styl

Seite 182 - Glossary–8

5.1.2 Switching Between InterfacesFor a few procedures it is necessary to switch from one console interface to theother.• Thetestcommand is run from t

Seite 183 - Glossary–9

5.1.3.1 Display Hardware ConfigurationThe hardware configuration display provides the following information:• The first screen displays system informatio

Seite 184 - Glossary–10

Table 5–2 ARC Firmware Device NamesName Descriptionmulti(0)key(0)keyboard(0)multi(0)serial(0)multi(0)serial(1)The multi( ) devices are located on the

Seite 185 - Glossary–11

Example 5–1 (Cont.) Sample Hardware Configuration Displayeisa(0)video(0)monitor(0)multi(0)key(0)keyboard(0)eisa(0)disk(0)fdisk(0) (Removable)multi(0)se

Seite 186 - Glossary–12

Table 5–3 lists and explains the default ARC firmware environment variables.Table 5–3 ARC Firmware Environment VariablesVariable DescriptionA: The defa

Seite 187 - Glossary–13

5.1.4 Verifying Configuration: SRM Console Commands forDigital UNIX and OpenVMSThe following SRM console commands are used to verify system configuratio

Seite 188 - Glossary–14

Bus 0, Slots 11–13 correspond to physical PCI card cage slots on theprimary PCI bus:Slot 11 = PCI11Slot 12 = PCI12Slot 13 = PCI13In the case of storag

Seite 189 - Glossary–15

Synopsis:show configExample:>>> show configFirmwareSRM Console: X4.4-5365ARC Console: 4.43pPALcode: VMS PALcode X5.48-115, OSF PALcode X1.35-8

Seite 190

5–6 Summary of Procedure for Configuring EISA Bus(EISA Options Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 5–315–7 Summary of Procedure f

Seite 191

The followingshow configexample illustrates how PCI options that contain aPCI-to-PCI bridge are represented in the display. For each option that conta

Seite 192

Example:>>> show configFirmwareSRM Console: X4.4-5365ARC Console: 4.43pPALcode: VMS PALcode X5.48-115, OSF PALcode X1.35-84Serial Rom: X2.1Pr

Seite 193

5.1.4.2 show deviceTheshow devicecommand displays the devices and controllers in the system.The device name convention is shown in Figure 5–2.Figure 5

Seite 194

Example:>>> show devicedka400.4.0.6.0 DKA400 RRD43 2893dva0.0.0.0.1 DVA0era0.0.0.2.1 ERA0 08-00-2B-BC-93-7Apka0.7.0.6.0 PKA0 SCSI Bus ID 7>

Seite 195

show envarArguments:envar The name of the environment variable to be modified.value The value that is assigned to the environment variable. This may be

Seite 196

Table 5–4 (Cont.) Environment Variables Set During System ConfigurationVariable Attributes Functionbootdef_dev NV The device or device list from which

Seite 197 - Electronic Orders

Table 5–4 (Cont.) Environment Variables Set During System ConfigurationVariable Attributes Functionbus_probe_algorithmNV Specifies a bus probe algorithm

Seite 198

Table 5–4 (Cont.) Environment Variables Set During System ConfigurationVariable Attributes Functioner*0_protocols,ew*0_protocolsNV Determines which net

Seite 199

Table 5–4 (Cont.) Environment Variables Set During System ConfigurationVariable Attributes Functionpci_parity NV Disable or enable parity checking on t

Seite 200 - BUSINESS REPLY MAIL

Table 5–4 (Cont.) Environment Variables Set During System ConfigurationVariable Attributes Functionpk*0_host_id NV Sets the controller host bus node ID

Kommentare zu diesen Handbüchern

Keine Kommentare