AlphaServer 1000AService GuideOrder Number: EK–ALPSV–SV. A01Digital Equipment CorporationMaynard, Massachusetts
Table 5–4 (Cont.) Environment Variables Set During System ConfigurationVariable Attributes Functiontga_sync_green NV Sets the location of the SYNC sign
the system by entering theinitcommand or pressing the Reset button.5.2 System Bus OptionsThe system bus interconnects the CPU and memory modules. Figu
5.2.1 CPU Daughter BoardAlphaServer 1000A systems use a CPU daughter board. The daughter boardprovides:• The DECchip 21064 or 21064A processor• 2 mega
Table 5–5 provides the memory requirements and recommendations for eachoperating system.Table 5–5 Operating System Memory RequirementsOperating System
• Two serial ports with full modem control and the parallel port• The keyboard and mouse interface• CIRRUS VGA controller• The speaker interface• PCI-
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
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
• 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
The system displays ‘‘loading ARC firmware.’’ When the firmware hasfinished loading, the ECU program is booted.3. Complete the ECU procedure according to
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
PrefaceThis guide describes the procedures and tests used to service AlphaServer 1000Asystems. AlphaServer 1000A systems use a deskside ‘‘wide-tower’’
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
Table 5–7 (Cont.) Summary of Procedure for Configuring EISA Bus with ISAOptionsStep ExplanationReturn to the SRMconsole (Digital UNIX andOpenVMS system
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
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
5.8.3 SCSI Bus ConfigurationsTable 5–8 provides descriptions of the SCSI configurations available using single,dual, and triple controllers, as well as
Figure 5–7 Single Controller ConfigurationJ10J1J12J2J11J16J14J13J15J17J3MA00900W3W2W112-45490-0117-04021-0117-04233-01Bus ID 4Bus ID 5012345612-41667-0
Figure 5–8 Dual Controller Configuration with Split StorageWorks BackplaneJ10J1J12J2J11J16J14J13J15J17J3MA00950W3W2W112-45490-0117-04233-01Bus ID 4Bus
Figure 5–9 Triple Controller Configuration with Split StorageWorks BackplaneJ10J1J12J2J11J16J14J13J15J17J3MA00902W3W2W117-04022-0117-04233-01Bus ID 4Bu
5.9 Power Supply ConfigurationsAlphaServer 1000A systems offer added reliability with redundant power options,as well as UPS options.The power supplies
Figure 5–10 Power Supply Configurations400 Watts DC or Less400 Watts DC or LessUPSMA00335SingleRedundantUPSThe H7290-AA power supply kit is used to ord
ConventionsThe following conventions are used in this guide:Convention MeaningReturnA key name enclosed in a box indicates that you press that key.Ctr
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
5.10 Console Port ConfigurationsPower-up information is typically displayed on the system’s console terminal. Theconsole terminal may be either a graph
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
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
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
6AlphaServer 1000A FRU Removal andReplacementThis chapter describes the field-replaceable unit (FRU) removal and replacementprocedures for AlphaServer
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
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
Table 6–1 (Cont.) AlphaServer 1000A FRUsPart # Description SectionOther Modules and Components70-31348-01 Interlock switch Section 6.2.854-23499-01 Sy
Figure 6–1 FRUs, Front RightInterlockSwitchInterlock/ServerManagement CableTape DriveOCP ModuleOCP CableCDROM DriveDrivesFloppy DriveFloppy DriveCable
• DECevent Analysis and Notification Utility for OpenVMS Alpha, User andReference Guide, AA-Q73LC-TE• DECevent Analysis and Notification Utility for Dig
Figure 6–2 FRUs, Rear LeftUpper FanSpeakerLower FanMemoryMA00930SCSI CablesPower CordMotherboardCPU Daughter BoardNVRAM Chip (E14)NVRAM Toy Clock Chip
6.2 Removal and ReplacementThis section describes the procedures for removing and replacing FRUs forAlphaServer 1000 systems, which use the deskside ‘
Figure 6–4 Removing Top Cover and Side PanelsTop CoverRelease LatchMA009146–8 AlphaServer 1000A FRU Removal and Replacement
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
Figure 6–6 OCP Module Cable (10-Pin)17-03971-01MA01421Figure 6–7 Power CordMA003386–10 AlphaServer 1000A FRU Removal and Replacement
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
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
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
Figure 6–11 Power Supply Storage Harness (12-Pin)Storage Harness(12-Pin)J12J13MA0142270-31346-016–14 AlphaServer 1000A FRU Removal and Replacement
Figure 6–12 Interlock/Server Management Cable (2-pin)MA00932J254AlphaServer 1000A FRU Removal and Replacement 6–15
Figure 6–13 Internal StorageWorks Jumper Cable (68-Pin)J10J1J12J2J11J16J14J13J15J17J3MA01427W3W2W112-45490-0117-04021-0117-04233-0112-41667-0517-04022
Figure 6–14 Wide-SCSI (Controller to StorageWorks Shelf) Cable (68-Pin)J10J1J12J2J11J16J14J13J15J17J3MA01428W3W2W112-45490-0117-04022-0217-04233-0112-
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
Figure 6–16 Wide-SCSI (J10 to Bulkhead Connector) Cable (68-Pin)J10J1J12J2J11J16J14J13J15J17J3MA01430W3W2W112-45490-0117-04022-0217-04233-0112-41667-0
Figure 6–17 SCSI (Embedded 8-bit) Removable-Media Cable (50-Pin)J10J1J12J2J11J16J14J13J15J17J3MA01431W3W2W112-45490-0117-04022-0217-04233-0112-41667-0
6.2.3 CPU Daughter BoardFigure 6–18 Removing CPU Daughter BoardMA00312CrossbarRetainingScrewCPU CardHandleClipsWarning: CPU and memory modules have pa
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
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
6.2.6 Internal StorageWorks BackplaneSTEP 1: REMOVE POWER SUPPLIES.Figure 6–21 Removing Power SupplyCurrent SharingHarness (3-Pin)Signal/Misc. Harness
STEP 2: REMOVE INTERNAL STORAGEWORKS BACKPLANE.Figure 6–22 Removing Internal StorageWorks BackplaneMA00934AlphaServer 1000A FRU Removal and Replacemen
1Troubleshooting StrategyThis chapter describes the troubleshooting strategy for AlphaServer 1000Asystems.• Section 1.1 provides questions to consider
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
Warning: Memory and CPU modules have parts that operate at hightemperatures. Wait 2 minutes after power is removed before handlingthese modules.Cautio
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
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
6.2.8 Interlock SwitchFigure 6–26 Removing the Interlock Safety SwitchMA009356–30 AlphaServer 1000A FRU Removal and Replacement
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
Figure 6–28 Removing CPU Daughter BoardMA00312CrossbarRetainingScrewCPU CardHandleClipsWarning: CPU and memory modules have parts that operate at high
Figure 6–29 Removing MotherboardMA0143212AlphaServer 1000A FRU Removal and Replacement 6–33
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)
Figure 6–30 Motherboard LayoutMemory ModuleConnectors (20)CPU ModuleConnectorPower ConnectorsDiskette DriveConnectorUpper FanConnectorLower Fan Connec
1.1.1 Problem CategoriesSystem problems can be classified into the following five categories. Using thesecategories, you can quickly determine a startin
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
Figure 6–32 Removing Front PanelRemoveScrewsRemoveHidden ScrewsMA00307AlphaServer 1000A FRU Removal and Replacement 6–37
Figure 6–33 Removing the OCP ModuleMA01423Black/Red(To InterlockSwitch)Green/Yellow(To Motherboard)J2546–38 AlphaServer 1000A FRU Removal and Replacem
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
6.2.13 SpeakerFigure 6–35 Removing SpeakerMA014246–40 AlphaServer 1000A FRU Removal and Replacement
6.2.14 Removable MediaFigure 6–36 Removing a CD–ROM DriveMA00324AlphaServer 1000A FRU Removal and Replacement 6–41
Figure 6–37 Removing a Tape DriveMA003256–42 AlphaServer 1000A FRU Removal and Replacement
Figure 6–38 Removing a Floppy DriveMA00326AlphaServer 1000A FRU Removal and Replacement 6–43
ADefault Jumper SettingsThis appendix provides the location and default setting for all jumpers inAlphaServer 1000A systems:• Section A.1 provides loc
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
A.1 Motherboard JumpersFigure A–1 shows the location and default settings for jumpers located on themotherboard.Figure A–1 Motherboard Jumpers (Defaul
Jumper Name Description Default SettingJ16 Large Fan Allows the large fan to bedisabled to accommodate thealternative enclosures.This jumper is notins
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
Figure A–3 AlphaServer 1000A 4/233 CPU Daughter Board (Jumpers J3 andJ4)MA00791J3J4Supported settings:• J4 Jumper:OffOnOffOffOn• J3 Jumper:OffDefault
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
Glossary10Base-T Ethernet networkIEEE standard 802.3-compliant Ethernet products used for local distribution ofdata. These networking products charact
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
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
clusterA group of networked computers that communicate over a common interface.The systems in the cluster share resources, and software programs work
data cacheA high-speed cache memory reserved for the storage of data. Abbreviated asD-cache.DEC VETDigital DEC Verifier and Exerciser Tool. A multipurp
Table 1–2 Diagnostic Flow for Problems Getting to Console ModeSymptom ActionPower-up screen is not displayed. Interpret the error beep codes at power-
ECCError correction code. Code and algorithms used by logic to facilitate errordetection and correction.EEPROMElectrically erasable programmable read-
FIBFlexible interconnect bridge. A converter that allows the expansion of the systemenclosure to other DSSI devices and systems.field-replaceable unitA
instruction cacheA high-speed cache memory reserved for the storage of instructions. Abbreviatedas I-cache.interrupt request lines (IRQs)Bus signals t
MAUMedium attachment unit. On an Ethernet LAN, a device that converts theencoded data signals from various cabling media (for example, fiber optic, coa
NVRAMNonvolatile random-access memory. Memory that retains its information in theabsence of power.OCPOperator control panel.open systemA system that i
portabilityThe degree to which a software application can be easily moved from onecomputing environment to another.portingAdapting a given body of cod
reliabilityThe probability a device or system will not fail to perform its intended functionsduring a specified time.responderIn any particular bus tra
SRMUser interface to console firmware for operating systems that expect firmwarecompliance with the Alpha System Reference Manual (SRM).storage arrayA g
test-directed diagnostics (TDDs)An approach to diagnosing computer system problems whereby error data loggedby diagnostic programs resident in read-on
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
Table 1–3 Diagnostic Flow for Problems Reported by the Console ProgramSymptom ActionPower-up tests do not complete. Interpret the error beep codes at
IndexAA: environment variable, 5–7AC power-up sequence, 2–24Acceptance testing, 3–18arc command, 5–4ARC interface, 5–3switching to SRM from, 5–4AUTOLO
Console event log, 2–11Console firmwarediagnostics, 2–26Digital UNIX, 5–3OpenVMS, 5–3Windows NT, 5–3Console interfacesswitching between, 5–4Console out
Environment variables set during systemconfiguration, 5–16Errorhandling, 1–7logging, 1–7Error formattersDECevent, 4–5Error log translationDigital UNIX,
Logsevent, 1–7Loopback tests, 1–8COM2 and parallel ports, 3–4command summary, 3–3MMachine check/interrupts, 4–2processor, 4–2processor corrected, 4–2s
RRAIDdiagnostic flow, 2–14RAID problems, 2–14Removable mediastorage problems, 2–12ROM-based diagnostics (RBDs), 1–7diagnostic-related commands, 3–3perf
Troubleshooting (cont’d)EISA problems, 2–18error report formatter, 1–7errors reported by operating system,1–7interpreting error beep codes, 2–2mass st
How to Order Additional DocumentationTechnical SupportIf you need help deciding which documentation best meets your needs, call 800-DIGITAL(800-344-48
Reader’s Comments AlphaServer 1000AService GuideEK–ALPSV–SV. A01Your comments and suggestions help us improve the quality of our publications.Thank yo
First Printing, March 1996Digital Equipment Corporation makes no representations that the use of its products in themanner described in this publicati
Table 1–4 Diagnostic Flow for Boot ProblemsSymptom ActionSystem cannot find boot device. Check the system configuration for the correct deviceparameters
Do Not Tear – Fold Here and TapeTMBUSINESS REPLY MAILFIRST CLASS PERMIT NO. 33 MAYNARD MASS.POSTAGE WILL BE PAID BY ADDRESSEENo PostageNecessaryIf Mai
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
RECOMMENDED USE: ROM-based diagnostics are the primary means oftesting the console environment and diagnosing the CPU, memory, Ethernet,I/O buses, and
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
ECU RevisionsThe EISA Configuration Utility (ECU) is used for configuring EISA options onAlphaServer systems. Systems are shipped with an ECU kit, which
You can obtain information about hardware configurations for theAlphaServer 1000A from the Digital Systems and Options Catalog. Thecatalog is regularly
2Power-Up Diagnostics and DisplayThis chapter provides information on how to interpret error beep codes andthe power-up display on the console screen.
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
Table 2–1 (Cont.) Interpreting Error Beep CodesBeepCode Problem Corrective Action1-3-3 No usable memory detected.1. Verify that the memory modulesare
ContentsPreface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi1 Troubleshooting Strategy1.1 Troubl
Table 2–1 (Cont.) Interpreting Error Beep CodesBeepCode Problem Corrective Action3-3-1 Generic system failure. Possible problemsources include the TOY
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
Table 2–2 (Cont.) SROM Memory Tests, CPU Jumper J1Bank# Test Description Test Results6 Memory Test,Cache Enabled:Tests memory withbackup and datacache
Table 2–2 (Cont.) SROM Memory Tests, CPU Jumper J1Bank# Test Description Test Results4 Backup Cache Test:Tests backup cachealternatively withdata cach
Figure 2–1 Jumper J1 on the CPU Daughter BoardMA00926J176543210Bank Jumper Setting0 Standard boot setting (AlphaServer 1000 systems)1 Standard boot se
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
Table 2–3 Console Power-Up Countdown Description and Field ReplaceableUnits (FRUs)CountdownNumber Description Likely FRUff Console initialization star
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
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
Table 2–4 (Cont.) Mass Storage ProblemsProblem Symptom Corrective ActionMissing or loosecables. Drives notproperly seated onStorageWorks shelfActivity
3 Running System Diagnostics3.1 Running ROM-Based Diagnostics . . . . . . . . . . . . . . . . . . . 3–13.2 Command Summary . . . . . . . . . . . . . .
Table 2–4 (Cont.) Mass Storage ProblemsProblem Symptom Corrective ActionSCSI storage controllerfailureProblems persist aftereliminating the problemsou
Table 2–5 (Cont.) Troubleshooting RAID ProblemsSymptom ActionCannot access disks connected tothe RAID subsystem on WindowsNT systems.On Windows NT sys
Figure 2–3 StorageWorks Disk Drive LEDs (SCSI)ActivityFaultMA00927Figure 2–4 Floppy Drive Activity LEDMA00330Activity LED2–16 Power-Up Diagnostics and
Figure 2–5 CD–ROM Drive Activity LEDActivity LEDMA00333Power-Up Diagnostics and Display 2–17
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
2.6.1 Additional EISA Troubleshooting TipsThe following tips can aid in isolating EISA bus problems.• Peripheral device controllers need to be seated
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–
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
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
Figure 2–6 Jumper J1 on the CPU Daughter BoardMA00926J176543210Bank Jumper Setting0 Standard boot setting (AlphaServer 1000 systems)1 Standard boot se
5.2.2 Memory Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–245.3 Motherboard . . . . . . . . . . . . . . . . . . . . . . . . . .
2.9 Power-Up SequenceDuring the AlphaServer 1000A power-up sequence, the power supplies arestabilized and the system is initialized and tested through
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
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
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
3Running System DiagnosticsThis chapter provides information on how to run system diagnostics.• Section 3.1 describes how to run ROM-based diagnostics
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
Table 3–1 (Cont.) Summary of Diagnostic and Related CommandsCommand Function ReferenceLoopback Testingtest lb Conducts loopback tests for COM2 and the
3.3.1 testThetestcommand runs firmware diagnostics for the entire core system. Thetests are run concurrently in the background. Fatal errors are report
Thetestscript tests devices in the following order:1. Console loopback tests if lb argument is specified: COM2 serial port andparallel port.2. Network
6.2.14 Removable Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–41A Default Jumper SettingsA.1 Motherboard Jumpers . . . . . . . .
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
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
3.3.3 memoryThememorycommand tests memory by running a memory exerciser each time thecommand is entered. The exercisers are run in the background and
The following is an example with a memory compare error indicating bad SIMMs.>>> memory>>> memory>>> memory*** Hard Error -
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
Testing an Ethernet Port:>>> netew>>> show_statusID Program Device Pass Hard/Soft Bytes Written Bytes Read-------- ------------ ----
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
Testing an Ethernet Port:>>> network>>> show_statusID Program Device Pass Hard/Soft Bytes Written Bytes Read-------- ------------ --
3.3.6 net -sThenet -scommand displays the MOP counters for the specified Ethernet port.Synopsis:net -s ewa0Example:>>> net -s ewa0Status count
3.3.7 net -icThenet -iccommand initializes the MOP counters for the specified Ethernetport.Synopsis:net -ic ewa0Example:>>> net -ic ewa0>&g
6–2 FRUs, Rear Left . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–66–3 Opening Front Door . . . . . . . . . . . . . . . . . . . . . .
3.3.8 kill and kill_diagsThekillandkill_diagscommands terminate diagnostics that are currentlyexecuting .NoteA serial loopback connector (12-27351-01)
3.3.9 show_statusTheshow_statuscommand reports one line of information per executingdiagnostic. The information includes ID, diagnostic program, devic
3.4 Acceptance Testing and InitializationPerform the acceptance testing procedure listed below after installing a system orwhenever adding or replacin
4Error Log AnalysisThis chapter provides information on how to interpret error logs reported by theoperating system.• Section 4.1 describes machine ch
Table 4–1 AlphaServer 1000 Fault Detection and CorrectionComponent Fault Detection/Correction CapabilityKN22A Processor ModuleDECchip 21064 and 21064A
Processor Machine Check (SCB: 670)Processor machine check errors are fatal system errors that result in a systemcrash. The error handling code for the
• Invalid page table lookup (scatter gather)• Memory cycle error• B-cache tag address parity error• B-cache tag control parity error• Non-existent mem
4.3 Event Record TranslationSystems running Digital UNIX and OpenVMS operating systems use theDECevent management utility to translate events into ASC
System faults can be isolated by examining translated system error logs orusing the DECevent Analysis and Notification Utility. Refer to the DECeventAn
5System Configuration and SetupThis chapter provides configuration and setup information for AlphaServer 1000Asystems and system options.• Section 5.1 d
6–35 Removing Speaker . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–406–36 Removing a CD–ROM Drive . . . . . . . . . . . . . . . . . . . .
5.1 Verifying System ConfigurationFigure 5–1 illustrates the system architecture for AlphaServer 1000A systems.Figure 5–1 System Architecture: AlphaSer
SRM Command Line InterfaceSystems running Digital UNIX or OpenVMS access the SRM firmware through acommand line interface (CLI). The CLI is a UNIX styl
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
5.1.3.1 Display Hardware ConfigurationThe hardware configuration display provides the following information:• The first screen displays system informatio
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
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
Table 5–3 lists and explains the default ARC firmware environment variables.Table 5–3 ARC Firmware Environment VariablesVariable DescriptionA: The defa
5.1.4 Verifying Configuration: SRM Console Commands forDigital UNIX and OpenVMSThe following SRM console commands are used to verify system configuratio
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
Synopsis:show configExample:>>> show configFirmwareSRM Console: X4.4-5365ARC Console: 4.43pPALcode: VMS PALcode X5.48-115, OSF PALcode X1.35-8
5–6 Summary of Procedure for Configuring EISA Bus(EISA Options Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 5–315–7 Summary of Procedure f
The followingshow configexample illustrates how PCI options that contain aPCI-to-PCI bridge are represented in the display. For each option that conta
Example:>>> show configFirmwareSRM Console: X4.4-5365ARC Console: 4.43pPALcode: VMS PALcode X5.48-115, OSF PALcode X1.35-84Serial Rom: X2.1Pr
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
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>
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
Table 5–4 (Cont.) Environment Variables Set During System ConfigurationVariable Attributes Functionbootdef_dev NV The device or device list from which
Table 5–4 (Cont.) Environment Variables Set During System ConfigurationVariable Attributes Functionbus_probe_algorithmNV Specifies a bus probe algorithm
Table 5–4 (Cont.) Environment Variables Set During System ConfigurationVariable Attributes Functioner*0_protocols,ew*0_protocolsNV Determines which net
Table 5–4 (Cont.) Environment Variables Set During System ConfigurationVariable Attributes Functionpci_parity NV Disable or enable parity checking on t
Table 5–4 (Cont.) Environment Variables Set During System ConfigurationVariable Attributes Functionpk*0_host_id NV Sets the controller host bus node ID
Komentarze do niniejszej Instrukcji