Digital PDFs

EK-422AA-MG-001

August 1990

118 pages

Original

1.0MB

Document:	DECsystem 5100 Maintenance Guide
Order Number:	EK-422AA-MG
Revision:	001
Pages:	118
Original Filename:

OCR Text

DECsystem 5100
Maintenance Guide
EK-422AA-MG.001

August 1990
This guide describes how to troubleshoot, adjust, and repair DECsystem 5100 systems
to field replaceable unit (FRU) level.

Revision/Update Information:

digital equipment corporation
maynard, massachusetts

This is a new guide.

August 1990
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 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 responsibility is assumed for the use or reliability of software on equipment that is
not supplied by Digital Equipment Corporation or its affiliated companies.
© Digital Equipment Corporation 1990.
All Rights Reserved.
Printed in Ireland.
The postpaid Reader’s Comments forms at the end of this document request your
critical evaluation to assist in preparing future documentation.

The following are trademarks of Digital Equipment Corporation:
DEC
DEC/CMS
DEC/MMS
DECnet
DECsystem–10
DECSYSTEM–20
DECUS
DECwriter

DIBOL
EduSystem
IAS
MASSBUS
PDP
PDT
RSTS
RSX

UNIBUS
VAX
VAXcluster
VMS
VT

UNIX is a registered trademark of American Telephone and Telegraph Company.

This equipment 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. Operation of this
equipment in a residential area may cause interference in which case the user at his
own expense will be required to take whatever measures may be required to correct
the interference.

This document was prepared using VAX DOCUMENT, Version 1.2.

Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 General Maintenance
1.1
1.1.1
1.1.2
1.1.3
1.1.4
1.2
1.3
1.4
1.5
1.5.1
1.5.2
1.6
1.6.1
1.7
1.7.1
1.7.2
1.7.3
1.8
1.8.1

System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Internal Storage Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
External Storage Expansion Boxes . . . . . . . . . . . . . . . . . . . . .
Optional Communications Module . . . . . . . . . . . . . . . . . . . . . .
Maintenance Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing Visual Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Shutting Down the Operating System Software . . . . . . . . . . . . . . .
Running the Power-Up Self-Test . . . . . . . . . . . . . . . . . . . . . . . . . .
Unsuccessful Power-Up Self-Test . . . . . . . . . . . . . . . . . . . . . . .
Interpreting Power-Up Self-Test Results . . . . . . . . . . . . . . . . .
Monitoring the Status LED Display . . . . . . . . . . . . . . . . . . . . . . . .
Interpreting the Status LED Display . . . . . . . . . . . . . . . . . . . .
Using the System in Console Mode . . . . . . . . . . . . . . . . . . . . . . . .
System Security and Operator Privileges . . . . . . . . . . . . . . . . .
Console Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Command Conventions . . . . . . . . . . . . . . . . . . . . . . . .
Booting the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Boot Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–1
1–1
1–2
1–2
1–2
1–2
1–3
1–5
1–6
1–8
1–9
1–12
1–12
1–14
1–14
1–16
1–17
1–18
1–19

iii

2 Extended Self-Test Diagnostics
2.1
2.2
2.3
2.4
2.4.1
2.4.2
2.4.3
2.5
2.5.1
2.6
2.6.1
2.6.2
2.6.3
2.6.4
2.6.5
2.6.6
2.6.7
2.6.8
2.6.9
2.6.10
2.6.11
2.6.12
2.6.13
2.6.14
2.6.15
2.6.16
2.6.17
2.6.18
2.6.19
2.6.20
2.6.21
2.6.22
2.6.23
2.6.24
2.6.25
2.6.26
2.6.27
2.6.28
2.6.29
2.6.30
2.7

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ULTRIX Diagnostic Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting a Console Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preparing for Console Extended Self-Tests . . . . . . . . . . . . . . . . . . .
Viewing Test Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Test Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminating Connectors for Diagnostic Tests . . . . . . . . . . . . . .
Running Console Extended Self-Tests . . . . . . . . . . . . . . . . . . . . . .
Error Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Test Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exception Test (t 0x1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FPU Test (test 0x2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Write Buffer Test (test 0x3) . . . . . . . . . . . . . . . . . . . . . . . . . . .
RTC Test (test 0x4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DZ Test (test 0x5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCSI Test (test 0x6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LANCE Test (test 0x7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EEPROM Test (test 0x8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TLB Test (test 0x10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Cache Segment Test (test 0x15) . . . . . . . . . . . . . . . . . . . .
Data Cache Tag Mats Test (test 0x16) . . . . . . . . . . . . . . . . . . .
Data Cache Tag Parity Mats Test (test 0x17) . . . . . . . . . . . . . .
Data Cache Data Parity Mats Test (test 0x18) . . . . . . . . . . . . .
Data Cache Valid Bit Test (test 0x19) . . . . . . . . . . . . . . . . . . .
Data Cache Tag Shorts Test (test 0x1a) . . . . . . . . . . . . . . . . . .
Data Cache Reload Test (test 0x21) . . . . . . . . . . . . . . . . . . . . .
Data Cache I-Stream Test (test 0x23) . . . . . . . . . . . . . . . . . . .
Instruction Cache Segment Test (test 0x1b) . . . . . . . . . . . . . . .
Instruction Cache Tag Mats Test (test 0x1c) . . . . . . . . . . . . . .
Instruction Cache Tag Parity Mats Test (test 0x1d) . . . . . . . . .
Instruction Cache Data Parity Mats Test (test 0x1e) . . . . . . . .
Instruction Cache Valid Bit Test (test 0x1f) . . . . . . . . . . . . . . .
Instruction Cache Tag Shorts Test (test 0x20) . . . . . . . . . . . . .
Instruction Cache Reload Test (test 0x22) . . . . . . . . . . . . . . . .
Instruction Cache I-Stream Test (test 0x24) . . . . . . . . . . . . . . .
Bitmap Placing Test (test 0x30) . . . . . . . . . . . . . . . . . . . . . . . .
Memory Address Test (test 0x31) . . . . . . . . . . . . . . . . . . . . . . .
Memory Data Test (test 0x32) . . . . . . . . . . . . . . . . . . . . . . . . .
Moving Inversions Test (test 0x33) . . . . . . . . . . . . . . . . . . . . . .
Memory Data Shorts Test (test 0x33) . . . . . . . . . . . . . . . . . . . .
Power Supply Troubleshooting Procedures . . . . . . . . . . . . . . . . . . .

2–1
2–1
2–1
2–2
2–2
2–4
2–4
2–4
2–5
2–6
2–7
2–8
2–8
2–8
2–8
2–9
2–10
2–10
2–10
2–10
2–11
2–11
2–11
2–11
2–12
2–12
2–12
2–12
2–13
2–13
2–13
2–13
2–14
2–14
2–14
2–14
2–15
2–15
2–16
2–16
2–16

3 FRU Removal and Replacement
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
3.11
3.12
3.13
3.14
3.14.1
3.14.2

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Unit Cover Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Upper Drive Mounting Panel Removal . . . . . . . . . . . . . . . . . . . . .
DHT80 Asynchronous Module Removal . . . . . . . . . . . . . . . . . . . . .
Lower Drive Mounting Panel Removal . . . . . . . . . . . . . . . . . . . . . .
RZ23 Disk Drive Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RZ24 Disk Drive Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TZ30 Tape Drive Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TZK10 Tape Drive Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RX23 Diskette Drive and FDI Board Removal . . . . . . . . . . . . . . . .
MS44 Memory Module Removal . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Module Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Supply Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DHT80 Asynchronous Module . . . . . . . . . . . . . . . . . . . . . . . . .
MS44 Memory Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–1
3–3
3–3
3–5
3–8
3–10
3–13
3–15
3–16
3–17
3–21
3–22
3–24
3–25
3–25
3–28

A Console Commands
A.1
A.2
A.3
A.4
A.5
A.6
A.7
A.8
A.9
A.10
A.11
A.12
A.13
A.14
A.15
A.16
A.17
A.18

Boot Command (boot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Command (conf) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Continue Command (continue) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deposit Command (d) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disable Command (disable) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dump Command (dump) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examine Command (e) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enable Command (enable) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fill Command (fill) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Go Command (go) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Help Command (help) (?) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Init Command (init) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Password Command (passwd) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Print Environment Command (printenv) . . . . . . . . . . . . . . . . . . . .
Set Environment Command (setenv) . . . . . . . . . . . . . . . . . . . . . . .
SCSI Command (scsi) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Test Command (test) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unset Environment Command (unsetenv) . . . . . . . . . . . . . . . . . . .

A–1
A–2
A–4
A–4
A–4
A–5
A–6
A–6
A–6
A–7
A–7
A–8
A–8
A–9
A–12
A–12
A–13
A–13

B System Specifications
C Recommended Spares List
D Status LED Display
E Parameters Returned by Diagnostic Tests
Index
Examples
1–1
1–2
1–3
1–4
2–1
A–1
A–2
A–3
A–4
A–5

Successful Power-Up Self-Test Display . . . . . . . . . . . . . . . . . . . . . .
Console Banner and Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unsuccessful Power-Up Self-Test Example . . . . . . . . . . . . . . . . . . .
Console Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Error Report Summary Example . . . . . . . . . . . . . . . . . . . . . . . . . .
Brief System Configuration Display . . . . . . . . . . . . . . . . . . . . . . . .
Full System Configuration Display . . . . . . . . . . . . . . . . . . . . . . . .
Console Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Environment Variable Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCSI Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–7
1–7
1–8
1–16
2–5
A–3
A–3
A–8
A–10
A–12

Connectors, Switches, and Indicators . . . . . . . . . . . . . . . . . . . . . . .
Location of On/Off Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Location of Halt/Reset Button . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Location of Status LED Display . . . . . . . . . . . . . . . . . . . . . . . . . . .
Location of Security Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Test Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Flowchart for Troubleshooting the Power Supply . . . . . . . . . . . . . .
Power Connector Pin Voltages on the System Module . . . . . . . . . .
Drive Power Connector Pin Voltages . . . . . . . . . . . . . . . . . . . . . . .

1–4
1–6
1–10
1–12
1–15
2–2
2–3
2–17
2–18
2–19

Figures
1–1
1–2
1–3
1–4
1–5
2–1
2–2
2–3
2–4
2–5

3–1
3–2
3–3
3–4
3–5
3–6
3–7
3–8
3–9
3–10
3–11
3–12
3–13
3–14
3–15
3–16
3–17
3–18
3–19
3–20
3–21
3–22
3–23
3–24
3–25

FRU Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cover Screw Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Drive Mounting Panel Power and Signal Cabling . . . . . . . . . . . . .
Releasing the Upper Drive Mounting Panel . . . . . . . . . . . . . . . . . .
Second Modem Cable Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DHT80 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DHT80 Asynchronous Module Removal . . . . . . . . . . . . . . . . . . . . .
Cover Plate Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Releasing the Lower Drive Mounting Panel . . . . . . . . . . . . . . . . . .
Separating the RZ23 HDA from the Module/Frame Assembly . . . .
RZ23 SCSI ID Jumper Wire Locations . . . . . . . . . . . . . . . . . . . . . .
RZ24 SCSI ID Jumper Wire Locations . . . . . . . . . . . . . . . . . . . . . .
TZ30 SCSI Switch Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TZK10 SCSI Switch Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RX23 Mounting Bracket Screws . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing the FDI Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FDI Board SCSI Switch Locations . . . . . . . . . . . . . . . . . . . . . . . . .
RX23 Select Switch Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MS44 Memory Module Removal . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Module Screw Locations . . . . . . . . . . . . . . . . . . . . . . . . . .
Location of the Ethernet Address Chip on the System Module . . .
Power Supply Screw Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Accessing the Asynchronous Connector on the System Module . . .
DHT80 Asynchronous Module Installation . . . . . . . . . . . . . . . . . . .
Memory Bank Connector Identification . . . . . . . . . . . . . . . . . . . . .

3–2
3–3
3–4
3–5
3–6
3–7
3–8
3–9
3–10
3–11
3–12
3–14
3–15
3–17
3–18
3–19
3–20
3–21
3–22
3–23
3–24
3–25
3–26
3–27
3–30

Visual Check Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Shutdown Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Memory Size Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interpreting Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LED Power-Up Self-Test Display Codes . . . . . . . . . . . . . . . . . . . . .
System Security Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Mode Control Characters . . . . . . . . . . . . . . . . . . . . . . . . .
Test Mode Terminators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Extended Self-Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serial Port Numbers and ULTRIX Mnemonics . . . . . . . . . . . . . . .
System Module Power Connector Voltages . . . . . . . . . . . . . . . . . . .

1–5
1–5
1–7
1–10
1–13
1–15
1–18
2–4
2–6
2–9
2–18

Tables
1–1
1–2
1–3
1–4
1–5
1–6
1–7
2–1
2–2
2–3
2–4

vii

2–5
3–1
3–2
3–3
3–4
3–5
3–6
3–7
A–1
B–1
B–2
B–3
B–4
B–5
B–6
B–7
B–8
C–1
C–2
D–1
E–1
E–2
E–3
E–4
E–5
E–6
E–7
E–8
E–9

viii

Drive Power Connector Voltages . . . . . . . . . . . . . . . . . . . . . . . . . .
FRU Section References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RZ23 SCSI ID Jumper Wire Combinations . . . . . . . . . . . . . . . . . .
RZ24 SCSI ID Jumper Wire Combinations . . . . . . . . . . . . . . . . . .
TZ30 SCSI ID Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TZK10 SCSI ID Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . .
RX23 SCSI ID Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . .
Possible Memory Configurations . . . . . . . . . . . . . . . . . . . . . . . . . .
Default Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Unit Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Storage Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Operating Conditions and Nonoperating Conditions . . . . .
TZ30 Tape Drive Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . .
TZK10 Tape Drive Specifications . . . . . . . . . . . . . . . . . . . . . . . . . .
RZ23 and RZ24 Hard Disk Drive Specifications . . . . . . . . . . . . . . .
RX23 Diskette Drive Specifications . . . . . . . . . . . . . . . . . . . . . . . .
DECsystem 5100 FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Miscellaneous Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Status LED Display Interpretation . . . . . . . . . . . . . . . . . . . . . . . .
Exception Test (t 0x1) Parameters . . . . . . . . . . . . . . . . . . . . . . . . .
Write Buffer Test (t 0x3) Parameters . . . . . . . . . . . . . . . . . . . . . . .
Real Time Clock Test (t 0x4) Parameters . . . . . . . . . . . . . . . . . . . .
DZ Test (t 0x5) Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCSI Test (t 0x6) Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EEPROM Test (t 0x8) Parameters . . . . . . . . . . . . . . . . . . . . . . . . .
Data Cache Test (t 0x15, t 0x16, t 0x17, t 0x18, t 0x19, t 0x1a)
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Instruction Cache Test (t 0x1b, t 0x1c, t 0x1d, t 0x1e, t 0x1f, t
0x20) Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Memory Test (t 0x30, t 0x31, t 0x32, t 0x33, t 0x34) Parameters . .

2–19
3–1
3–12
3–14
3–16
3–17
3–20
3–29
A–10
B–1
B–2
B–2
B–2
B–3
B–3
B–4
B–5
C–1
C–2
D–1
E–1
E–1
E–2
E–2
E–2
E–3
E–3
E–3
E–4

Preface
Purpose of This Guide
This document describes how to isolate hardware failures that occur during
operation of the DECsystem 5100. It contains procedures for running
diagnostic self-tests and replacing field replaceable units (FRUs).

Who Should Read This Guide
This guide is intended for Digital Field Service personnel who provide support
and maintenance for the DECsystem 5100 hardware, or customers who have a
self-maintenance agreement with Digital.
Readers of this guide should have experience of replacing hardware
components.

Document Structure
This guide contains the following chapters and appendixes:
Section

Title

Description

Chapter 1

General Maintenance

This chapter describes how to shut
down the operating system, run and
interpret the power-up self-test, use
the console menu, and reboot the
system.

Chapter 2

Extended Self-Tests

This chapter explains how to run
and interpret the DECsystem 5100
extended self-tests.

Chapter 3

FRU Removal and
Replacement

This chapter contains instructions on
replacing FRUs that diagnostic tests
have indicated are faulty.

Appendix A

Console Commands

This appendix describes the console
commands that you can enter when
the system is in console mode.

Appendix B

System Specifications

This appendix lists the system
specifications.

Appendix C

Recommended Spares List

This appendix lists the recommended
spare parts for the DECsystem 5100.

Appendix D

Status LED Display

This appendix describes how to
interpret the status LED display on
the back of the system unit.

Appendix E

Parameters Returned by
Diagnostic Tests

This appendix describes the
significance of the parameters that
certain diagnostic tests use.

Associated Documents
The following documents provide additional hardware information about the
DECsystem 5100:
DECsystem 5100 Installation Guide, EK-420AA-IN.001
DECsystem 5100 Operator’s Guide, EK-421AA-OG.001
DECsystem 5100 Illustrated Parts Breakdown, EK-5100X-IP.001

Conventions
The following conventions are used in this document.
Convention

Description

MONOSPACE

Text displayed on the screen is shown in monospaced type.

[]

In command syntax descriptions, brackets [ ] indicate optional
elements.

In command syntax descriptions, a vertical line separates similar
options, one of which you can choose.

bold

User input is shown in bold type.

italic type

Italic type emphasizes important information, indicates variables,
and references titles of other manuals.

Note

A note contains information of special importance to the reader.

Caution

A caution contains information to prevent damage to the equipment.

Warning

A warning contains information to prevent personal injury.

1
General Maintenance
1.1 System Overview
The DECsystem 5100 is a multiuser ULTRIX desktop system based on Reduced
Instruction Set Computer (RISC) technology. The system supports VT series
terminals.
Some DECsystem 5100 systems are supplied with factory installed software
(FIS), which means that the ULTRIX operating system is preloaded onto the
system disk at the factory. For other DECsystem 5100 systems, the owner
must install the operating system software.

1.1.1 System Module
The system module provides most of the functionality of the system. It
provides external connections for the following:
Three DEC423 compatible asynchronous lines (MMJ connectors)
One RS232 modem port
Ethernet connection—ThinWire or Standard Ethernet, but not both.
The system module also provides eight connectors for MS44 memory modules.
These eight connectors are arranged in four banks. To fill a bank of memory,
you must install two MS44 memory modules. There are two different types of
MS44 memory modules as follows:
MS44-AA—4MB
MS44-CA—16MB
The minimum memory possible in the system is 8MB. You can add memory in
8MB (MS44-BA) and 32MB (MS44-DA) increments to a maximum of 128MB.

General Maintenance 1–1

A switch on the system module and a password in nonvolatile memory provide
a security system that allows only privileged users (those who know the
password) to access the full range of console commands.
On the system module, there is also a status LED display. This provides
system status and diagnostic test status information.
The system module supports a programmable halt/reset button. In console
mode, the switch is reset, pressing it invokes the power-up diagnostic tests.
You can program the switch to halt the operating system and enter console
mode.

1.1.2 Internal Storage Devices
The DECsystem 5100 can house mass storage devices internally. The devices
are mounted on two drive mounting panels in the system unit. A DECsystem
5100 may contain any of the following devices internally:
RZ23 disk drive
RZ24 disk drive
TZ30 tape drive
TZK10 tape drive
RX23 diskette drive

1.1.3 External Storage Expansion Boxes
DECsystem 5100 systems also have a small system computer interface (SCSI)
connector that allows you to connect external mass storage expansion boxes.
The maximum number of expansion boxes that you can connect is two.

1.1.4 Optional Communications Module
The DECsystem 5100 supports the DHT80 asynchronous option. It provides
external connections for the following:
Seven DEC423 compatible asynchronous lines (MMJ connectors)
One RS232 modem connector

1.2 Maintenance Overview
The remainder of this chapter describes the following general maintenance
procedures:
Visually checking the equipment
Shutting down the operating system software
Running the power-up self-tests

1–2 General Maintenance

Interpreting the power-up self-tests
Monitoring the status LED display
Interpreting the status LED display
Using the console menu
Booting the operating system software after running diagnostics

1.3 Performing Visual Checks
Examine all external connections, cables, power cords, and monitor the
operation of the system. Figure 1–1 shows the locations of the various
connectors, switches and indicators on the system unit. Table 1–1 describes
common problems that you may encounter with your system.

General Maintenance 1–3

Figure 1–1

Connectors, Switches, and Indicators

Power On/Off Switch
Power Connector
Ethernet SCSI Port
Modem Port
(Optional)
MMJ Ports 4 to 10
(Optional)
Halt/Reset Button
Net Select
Indicators
Standard Ethernet
Port
Ethernet Switch
ThinWire Ethernet Port
MMJ Port 1
MMJ Port 2
MMJ Port 3
Modem Port
Diagnostic LEDs

RE_EN05173A_90

1–4 General Maintenance

Table 1–1

Visual Check Problems

Problem

Cause

Action

The power indicator
LED is off and the fans
are off.

Power cord is not connected
properly.

Make sure that there is
power at the power outlet.
Reconnect the power cord.

The power supply assembly is
not functioning.

Replace the power supply
(see Chapter 3).

Power supply assembly is not
functioning.

Check internal power
cabling and connections.
Replace the power supply
(see Chapter 3).

The fans start up but
the LED is off.

1.4 Shutting Down the Operating System Software
Before you can run diagnostic self-tests, you must shutdown the operating
system software. If the operating system software is not running, go to
Section 1.5.
Before shutting down the operating system, obtain permission from the system
manager. To shut down the operating system software, log in to the ULTRIX
field account or an account that has superuser privileges. Table 1–2 shows
the commands that you can enter at the system prompt (#) to shut down your
system.
Table 1–2

Shutdown Commands

Command

Result

/etc/shutdown -h now

This command starts the operating system software
shutdown procedure immediately, without issuing
warning messages.

/etc/shutdown -h hhmm

This command shuts down the operating system software
at a specified time. In this table, hh indicates hours, mm
indicates minutes. The system sends warning messages
to all users on the Local Area Network (LAN) indicating
shutdown time.
(continued on next page)

General Maintenance 1–5

Table 1–2 (Cont.)

Shutdown Commands

Command

Result

/etc/shutdown -h +n

This command shuts down the operating system software
after a specified number of minutes. In this table,
n indicates the number of minutes after which the
operating system software shuts down. The system
sends warning messages to all users on the LAN at an
increasing frequency.

1.5 Running the Power-Up Self-Test
The power-up self-test checks each component, subsystem, and connection. The
DECsystem 5100 automatically runs the power-up self-test when you turn on
the system.
To turn on the system, push the on/off switch on the system unit to the on ( | )
position. Figure 1–2 shows the location of the system unit on/off switch.
Figure 1–2

Location of On/Off Switch

Power On/Off Switch

RE_EN05169A_90

The system begins to build a power-up self-test display on the console
terminal. Example 1–1 shows the power-up self-test display when it completes
successfully.

1–6 General Maintenance

Example 1–1

Successful Power-Up Self-Test Display

26..25..24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..

The numbers in the power-up self-test display represent tests or a group of
tests on specific system functions.
If the power-up self-test completes successfully, the system displays the console
banner and prompt (see Example 1–2).
Example 1–2

Console Banner and Prompt

KN230 Vx.x
08-00-2b-55-55-55
0x1000000
Bad mem: 0x1400
>>

1
2
3
4
5

The version of the system module console program. The character V
indicates the version type of the system firmware. The digits x.x indicate
the release number.

The Ethernet address of the system.

The size of memory in hexadecimal format. Table 1–3 shows the possible
values for the various memory configurations.

Table 1–3

Memory Size Indication

Hexadecimal Value

Memory Size

0x800000

8MB

0x1000000

16MB

0x1800000

24MB

0x2000000

32MB

0x2800000

40MB

0x3000000

48MB
(continued on next page)

General Maintenance 1–7

Table 1–3 (Cont.)

Memory Size Indication

Hexadecimal Value

Memory Size

0x3800000

56MB

0x4000000

64MB

0x4800000

72MB

0x5000000

80MB

0x6000000

96MB

0x6800000

104MB

0x8000000

128MB

A message to indicate that some bad memory exists but you can use the
system.

The console prompt. This prompt may also be S> if security is enabled and
a valid password exists (see Section 1.7.1).

1.5.1 Unsuccessful Power-Up Self-Test
If during the power-up self-test, one of the individual tests fails, the system
halts and displays an error report summary. Example 1–3 shows a typical
error report summary resulting from the failure of test group 21. An error
report summary contains five lines of diagnostic information. See Section 2.5.1
for more information on error reports.
Example 1–3

Unsuccessful Power-Up Self-Test Example

26..25..24..23..22..21.. 1
?1f 03 ff 0001 2
P1= 00000000 P2= 00000000 P3= 00000000 P4= 00000000 P5= 00000000 2
P6= 00000000 P7= 00000000 P8= 00000000 P9= 00000000 P10=00000000 2
gp= 17bcbcfc sp= a000f7b0 fp=bfc00480 sr= 00000000 2
2
epc=bfc20a70 badvaddr=00060000 cause=3000000
20..19..18..17..16..15..14..13..12..11..10..9.. 3
8..7..6..5..4..3..
>> 4
1

Power-up self-test in progress

Five line error report summary on the failing test, test 1f (see Section 2.5.1)

Power-up self-test continuing after error

1–8 General Maintenance

Console prompt, optionally S>, if security is enabled and a valid password
exists (see Section 1.7.1).

Note the number of the test that failed. It is the number after the ? in the
error report summary (test 1f in Example 1–3).
If the power-up self-test display is not displayed on the console terminal, you
can use the status LED display to determine the probable cause of the problem
(see Section 1.6).

1.5.2 Interpreting Power-Up Self-Test Results
This section describes how to interpret the power-up self-test results.
If an error occurs during power-up self-test, proceed as follows:
1

Make sure that all external cables and power cords are properly connected.

Make sure that the Ethernet cable is properly connected.

Note If your system is connected to a network and you want to run tests in
manufacturing mode (see Section 2.4.2), you have to disconnect the
Ethernet connection. Install either the ThinWire Ethernet T-connector
and terminators, or the Standard Ethernet loopback connector, depending
on the type of Ethernet you are using. Also, to run tests in manufacturing
mode, you have to install loopback connectors on the serial ports.
If you locate and correct an external problem, you can run the power-up
self-test again, using one of the following methods:
Press the halt/reset button at the back of the system unit (see Figure 1–3).
Enter the following command at the console prompt:
>> test 0x0

General Maintenance 1–9

Figure 1–3

Location of Halt/Reset Button

Halt/Reset Button
RE_EN05172A_90

If you cannot locate an external problem, compare the code of the test that
failed during the power-up self-test with the codes in Table 1–4, and take the
action suggested.
Table 1–4
Test Group

Interpreting Test Results
Test Group Name

Most Likely Failing Component

Exception Test

System Module

FPU Test

System Module

Write Buffer Test

System Module

Data Cache Tests

System Module

Instruction Cache Tests

System Module

TLB Test

System Module

Data Cache Tests

System Module

Instruction Cache Tests

System Module

Data Cache Test

System Module

Instruction Cache Test

System Module

Memory Bitmap Placing Test

MS44 Memory Modules 1 or
System Module

Memory Address Test

MS44 Memory Module 1

See the test description in Chapter 2 for instructions on how to identify which MS44 memory
module is faulty.

(continued on next page)

1–10 General Maintenance

Table 1–4 (Cont.)
Test Group

Interpreting Test Results

Test Group Name

Most Likely Failing Component

Memory Data Test

MS44 Memory Module 1

Memory Moving Inversions
Test

MS44 Memory Module 1

Memory Data Shorts Test

MS44 Memory Module 1

RTC Tests

System Module

DZ Tests

System Module or
DHT80 Asynchronous Module2

SCSI Tests

System Module

LANCE Tests

System Module

EEPROM Tests

System Module

1
See the test description in Chapter 2 for instructions on how to identify which MS44 memory
module is faulty.
2

Depends on which serial line fails. See the test description in Chapter 2 to identify which serial
lines belong to which module.

General Maintenance 1–11

1.6 Monitoring the Status LED Display
If the console terminal does not show the power-up self-test display, you
can use the status LED display to determine the cause of the problem and
determine if the system is able to run diagnostic tests.
The status LED display contains eight LEDs. Appendix D describes the
functions of all the LEDs in the status LED display. This section describes
the five LEDs that provide power-up and extended self-test information.
Figure 1–4 shows the location of the status LED display on the back of the
system unit.
Figure 1–4

Location of Status LED Display

Status LED Display
RE_EN05170A_90

During the power-up self-test, or when running extended self-test diagnostics
(see Chapter 2), LEDs 7, 6, 5, 4, and 2 on the status LED display show a binary
code. If the system detects an error, it halts and displays a code indicating the
number of the test that failed.

1.6.1 Interpreting the Status LED Display
Compare the code that you noted on LEDs 7, 6, 5, 4, and 2 on the status LED
display during the power-up self-test with the list of codes in Table 1–5 to get
an indication of the system component that failed.

1–12 General Maintenance

Table 1–5

LED Power-Up Self-Test Display Codes

LED Display1
2
7654

Decimal
Value

1111

Initial state at power-up, no code has
executed

1110

Entered ROM, some instructions have
executed

1101

Stack tested and set

1100

NXM taken

1011

Security initialization

1010

DZ initialization

1001

Exception test

1000

FPU test

0111

Write buffer test

Hexadecimal Component
Value
Tested

0101

Data cache tag test

0110

Instruction cache tag test

0100

TLB test

0011

Data cache test

0010

Instruction cache test

0001

Data cache i-stream test

0000

Instruction cache i-stream test

1111

Memory bitmap placing test

1110

Memory address test

1101

Memory data test

1100

Memory moving inversions test

1011

Memory data shorts test

1010

RTC test

1001

DZ test

1000

SCSI test

0111

LANCE test

0110

EEPROM test

0101

Option card test

1 = LED is on, 0 = LED is off

(continued on next page)

General Maintenance 1–13

Table 1–5 (Cont.)

LED Power-Up Self-Test Display Codes

LED Display1
2
7654

Decimal
Value

0100

Reserved

0011

Console I/O mode

Hexadecimal Component
Value
Tested

0010

Primary bootstrap

0001

Secondary bootstrap

0000

Operating system running

1 = LED is on, 0 = LED is off

1.7 Using the System in Console Mode
You can enter commands at the console prompt (>>) to view and control the
operation of the system. There are specific commands that allow you to set
operator preferences and run diagnostic tests.

1.7.1 System Security and Operator Privileges
A switch on the system module (see Figure 1–5) and a password in nonvolatile
memory control the security of the system. The DECsystem 5100 is either
secure or insecure. The operator has a privileged or unprivileged status.

1–14 General Maintenance

Figure 1–5

Location of Security Switch

Security Switch

RE_EN05193A_90

When you set the security switch on the system module to the insecure (down)
position, the password is set to zero and the system is insecure.
To make the system secure, set the security switch on the system module to the
secure (up) position. You can then use the passwd command with the -s option
to set a password and make the system secure (see Section A.13). When you
make the system secure, the next time you turn on your system, the prompt
S> is displayed. You must now enter the new password to access the full set of
console commands.
Table 1–6 summarizes the console commands that you can enter when the
system is secure or insecure and you have a privileged or unprivileged status.
Table 1–6

System Security Conditions

Operator
Status

Console Commands Allowed
Secure System (switch up)
Insecure System (switch down)

Privileged

All console commands (>>)

Unprivileged

Only the boot and passwd
commands without options or
arguments (S>)

Not applicable

Use the passwd command to enter and exit privileged mode, and to set and
clear the password stored in nonvolatile memory (see Section A.13).

General Maintenance 1–15

1.7.2 Console Menu
The console menu lists the commands you can use in console mode, that is,
when the system displays the console prompt (>>). To display the console
menu, enter one of the following commands at the console prompt and press
Return:
>> ?

or,
>> help

The system displays the console menu (see Example 1–4).
Example 1–4

Console Menu

>> ?
CMD:
boot [-f FILE] [-(s|m)] [-n] [ARG...]
conf [-(b|f|m)]
continue
d [-(b|h|w)] ADDR VAL
disable DEV
dump [-(b|h|w)] [-(o|d|u|x|c|B)] RNG
e [-(b|h|w)] ADDR
enable DEV
fill [-(b|h|w)] [-v VAL] RNG
go [PC]
help [CMD]
init
passwd [-(c|s|u)]
printenv [EVAR...]
scsi
setenv EVAR STR
test [-v] [-f] [-r[REPS]] [-s] TNUM [param1 param2 param3 ...]
unsetenv EVAR
? [CMD]
RNG:
ADDR#CNT
ADDR:ADDR
>>

Appendix A describes the console commands in detail.

1–16 General Maintenance

1.7.3 Console Command Conventions
The following command conventions apply when you are entering console
commands:
The commands you enter at the console prompt are case sensitive. The
system recognizes uppercase and lowercase letters as completely different
input.
To enter any console command, enter the command exactly as it is
displayed on the console menu, add the appropriate arguments (if
necessary), and press Return.
To enter numeric values, use the following conventions:
Decimal - enter a string of decimal digits (for example, 123).
Octal - enter a string of octal digits with a leading zero (for example,
0177).
Hexadecimal - enter a string of hexadecimal digits preceded by 0x (for
example, 0x3ff).
Binary - enter a string of binary digits preceded by 0b (for example,
0b1001).
In console mode, certain ASCII control characters have a special significance.
Table 1–7 describes the significance of these control characters.

General Maintenance 1–17

Table 1–7

Console Mode Control Characters

Character

Significance

Ends a command line. The system enters command characters
into a buffer until a carriage-return is received.

Delete

Deletes the previously typed character. If the console terminal is
set as hardcopy (environment variable term set to hardcopy), the
system echoes the deleted text enclosed by backslashes.

Ctrl/C

Causes the console program to abort the processing of a command.

Ctrl/O

Causes the console program to discard output until you enter the
next Ctrl/O character, or until it receives the next console prompt
or error message. Ctrl/C also cancels Ctrl/O.

Ctrl/Q

Resumes console output that the control character Ctrl/S suspends.

Ctrl/R

Causes the current command line to display, omitting any deleted
characters.

Ctrl/S

Suspends the current command line that the console program
displays, omitting any deleted characters.

Ctrl/U

Discards all characters that the console program accumulates for
the current command line.

Ctrl/V

Suppresses any special meaning that the next character of the
console command line has.

1.8 Booting the Operating System
Booting is the process of loading and transferring control to an operating
system. The DECsystem 5100 supports the bootstrapping of the ULTRIX
operating system.
In the DECsystem 5100, the operating system boots in one of the following
circumstances:
You set the environment variable bootmode to the value a, and you press
the halt/reset button
You set the environment variable bootmode to a value other than a, and
you enter the boot command at the console prompt (see Section A.1).
The operating system software initiates a boot operation.
See Section A.14 for more information about the environment variable
bootmode.

1–18 General Maintenance

1.8.1 Boot Devices
You can boot the DECsystem 5100 from one of three different device types as
follows:
Hard disk drive
Tape drive
Ethernet
The boot command specifies the boot device and the boot file (see Section A.1).

General Maintenance 1–19

2
Extended Self-Test Diagnostics
2.1 Introduction
This chapter describes how to run and interpret the DECsystem 5100 extended
self-test diagnostics. You can use the extended self-test diagnostics to diagnose
component and subsystem malfunctions in the system unit.

2.2 ULTRIX Diagnostic Tools
If the system you are testing is experiencing intermittent hardware errors,
examine the ULTRIX error logs before running extended self-tests. You can
use the ULTRIX tools, uerf and netstat, to trace some hardware errors. See
Section 8 in the ULTRIX documentation set for information about uerf, and
Section 1 for information about netstat.

2.3 Connecting a Console Terminal
You can enter console commands from the console terminal connected to MMJ
port 3 on the back of the system unit (see Figure 2–1).
To connect a terminal to this port, do the following:
1

Connect the cable from the terminal to the console port, MMJ port 3 (see
Figure 2–1).

On the terminal, set the power on/off switch to the on ( | ) position.

Extended Self-Test Diagnostics 2–1

On the terminal, set the communication parameters as follows:
Baud rate: 9600
No of bits: 8
Parity: none
No of stop bits: 1

Figure 2–1

Console Port

Console Port
(MMJ Port 3)

RE_EN05171A_90

2.4 Preparing for Console Extended Self-Tests
Before running the extended self-tests:
1

Display the test menu to find the correct commands (see Section 2.4.1).

Choose the appropriate test mode (see Section 2.4.2).

Install terminators or loopback connectors for the test mode you are using
(see Section 2.4.3).

2.4.1 Viewing Test Commands
To view the test menu, which lists all valid diagnostic test commands, enter
the following command at the console prompt:
>> test ?

2–2 Extended Self-Test Diagnostics

The system displays the test menu (see Figure 2–2).
Figure 2–2

Test Menu

>> test ?
Test#
Name
Parameters
---------------------------------------------------------------------0x1
Exception test
0x2
FPU test
0x3
Write Buffer test
0x4
RTC test
0x5
DZ test
[int/ext,line]
0x6
SCSI test
0x7
LANCE test
0x8
EEPROM test
0x10
TLB test
0x15
Data Cache Segment test
0x16
Data Cache Tag Mats test
0x17
Data Cache Tag Mats Parity test
0x18
Data Cache Data Parity Mats test
0x19
Data Cache Valid Bit test
0x1A
Data Cache Tag Shorts test
0x1B
Instruction Cache Segment test
0x1C
Instruction Cache Tag Mats test
0x1D
Instruction Cache Tag Mats Parity test
0x1E
Instruction Cache Data Parity Mats test
0x1F
Instruction Cache Valid Bit test
0x20
Instruction Cache Tag Shorts test
0x21
Data Cache Reload test
0x22
Instruction Cache Reload test
0x23
Data Cache Istream test
0x23
Instruction Cache Istream test
0x30
Bitmap Placing test
0x31
Memory Address test
[start_addr,end_addr,OFFset]
0x32
Memory Data test
0x33
Moving Inversions test
0x34
Memory Data Shorts test
Script# Name
---------------------------------------------------------------------0xA0
Memory tests
0xA1
Data Cache tests
0xA2
Instruction Cache tests
0xA3
Device (RTC,DZ,SII,LANCE) tests

Extended Self-Test Diagnostics 2–3

2.4.2 Test Modes
You can run the self-test diagnostics in two modes as follows:
User mode
Manufacturing mode
When you power up the system, it is in user mode. You can put the system in
manufacturing mode by entering the following command at the console prompt:
>> setmode mfg 1

Note When you run tests in manufacturing mode, you must install loopback
connectors on the serial ports.

2.4.3 Terminating Connectors for Diagnostic Tests
Depending on the mode in which you run the diagnostics, you must install
terminators or loopback connectors on DECsystem 5100 connectors. Table 2–1
describes which terminators and loopback connectors that you must install in
both user mode and manufacturing mode. Appendix C lists the terminator and
loopback connector part numbers. Figure 1–1 shows the ports and connectors
on the back of the system unit.
Table 2–1

Test Mode Terminators

Test Mode

Required Terminators/Loopback Connectors

User

None

Manufacturer/debug

A ThinWire Ethernet terminator, Standard Ethernet
loopback connector, or connection to Ethernet cable. (Make
sure the Ethernet button is in the correct position; set to the
in position for ThinWire Ethernet, set to the out position for
Standard Ethernet.)
Serial line loopback connectors for all MMJ ports and all
modem ports.

2.5 Running Console Extended Self-Tests
You can run all tests in either user or manufacturing mode. The examples
in this chapter show user mode test displays. Manufacturing tests are more
comprehensive and take longer to complete.
To run a console extended self-test, enter the test command and the test
number at the console prompt. For example, to run the FPU test, enter the
following command:

2–4 Extended Self-Test Diagnostics

>> test 0x2

Note You must enter the test number in hexadecimal format (see Section 1.7.3).
When the test completes without errors, the system displays the console
prompt (>>).
To get information about a test as it executes, you can add the -v (verbose)
option to the command line. You can also choose to repeat a test by adding the
-r (repeat) option to the command line. To exit a repeating test, press Ctrl/c.
See Section A.17 for more information on the test command.
Note When using Ctrl/c to halt a test, it may take some time for the test to halt.
To get a list of the tests you can run and their corresponding test numbers,
enter the following command:
>> test ?

The system displays the test menu (see Section 2.4.1).

2.5.1 Error Reports
If an error occurs during power-up or extended self-test, the system displays an
error report on the console terminal if possible. Example 2–1 shows a typical
error display resulting from a failed self-test.
Example 2–1

Error Report Summary Example

?1f 03 ff 0001 1
P1= 00000000 P2= 00000000 P3= 00000000 P4= 00000000 P5= 00000000 2
P6= 00000000 P7= 00000000 P8= 00000000 P9= 00000000 P10=00000000 2
gp= 17bcbcfb sp= a000f7b0 fp= bfc00480 sr= 00000000 3
3
epc=bfc20a70 badvaddr=00060000 cause=3000000c
1

Test summary contains four hexadecimal fields as follows:
?1f is the test number that failed.
03 is the number of the subtest that failed. You can use this number to
identify the location of the failure in the diagnostic listing.
ff is an error code. This code indicates a condition that the diagnostic
executive expects on test failure. The possible codes are as follows:
ff—Normal error, exit from diagnostic
fe—Unanticipated exception
fd—Interrupt in cleanup routine
fc—Interrupt in interrupt handler

Extended Self-Test Diagnostics 2–5

fb—Failure to meet script requirements
fa—No such diagnostic
ef—Unanticipated exception in executive
0001 is a count value. This is the number of previous errors that
occurred.
2

P1 to P10 are specific parameters used during the diagnostic test. The
values shown are the values of the parameters when the test failed.
Appendix E gives the significance of these registers for each of the
individual tests that use these parameters.

The following CPU registers gp, sp, fp, sr, epc, badvaddr, and cause. The
values shown are the values of the registers when the test failed.

2.6 Test Descriptions
Table 2–2 lists the test number, the name of the test and a reference to a
section that describes the test in this chapter.
Table 2–2

Console Extended Self-Tests

Test Command

Test Name

Section

test 0x1

Exception tests

2.6.1

test 0x2

FPU test

2.6.2

test 0x3

Write buffer test

2.6.3

test 0x4

RTC test

2.6.4

test 0x5

DZ test

2.6.5

test 0x6

SCSI test

2.6.6

test 0x7

LANCE test

2.6.7

test 0x8

EEPROM test

2.6.8

test 0x10

TLB test

2.6.9

Miscellaneous Tests

(continued on next page)

2–6 Extended Self-Test Diagnostics

Table 2–2 (Cont.)
Test Command

Console Extended Self-Tests
Test Name

Section

test 0x15

Data cache segment test

2.6.10

test 0x16

Data cache tag mats test

2.6.11

test 0x17

Data cache tag mats parity test

2.6.12

test 0x18

Data cache data parity mats test

2.6.13

test 0x19

Data cache valid bit test

2.6.14

test 0x1A

Data cache tag shorts test

2.6.15

test 0x21

Data cache reload test

2.6.16

test 0x23

Data cache I-stream test

2.6.17

test 0x1B

Instruction cache segment test

2.6.18

test 0x1C

Instruction cache tag mats test

2.6.19

test 0x1D

Instruction cache tag mats parity test

2.6.20

test 0x1E

Instruction cache data parity mats
test

2.6.21

test 0x1F

Instruction cache valid bit test

2.6.22

test 0x20

Instruction cache tag shorts test

2.6.23

test 0x22

Instruction cache reload test

2.6.24

test 0x24

Instruction cache I-stream test

2.6.25

test 0x30

Bitmap placing test

2.6.26

test 0x31

Memory address test

2.6.27

test 0x32

Memory data tests

2.6.28

test 0x33

Moving inversions test

2.6.29

test 0x34

Memory data shorts test

2.6.30

Data Cache Tests

Instruction Cache Tests

Memory Tests

2.6.1 Exception Test (t 0x1)
This test verifies that the processor can invoke, detect, and process all types of
program exceptions.
To run the Exception Test, enter the following command:
>> test 0x1

Extended Self-Test Diagnostics 2–7

If an error occurs, replace the system module (see Section 3.12). Table E–1
describes the significance of the parameters P1 and P2 in the error report.

2.6.2 FPU Test (test 0x2)
This test checks the operation of the Floating Point Unit (FPU). The test uses
the addition, subtraction, multiplication, and division instructions to test the
FPU and ensures that errors are detected as appropriate.
To run the FPU Test, enter the following command:
>> test 0x2

If an error occurs, replace the system module (see Section 3.12).

2.6.3 Write Buffer Test (test 0x3)
This test verifies that the CPU can write data through and read back data
through the LR3220 read-write buffer correctly.
To run the Write Buffer Test, enter the following command:
>> test 0x3

If an error occurs, replace the system module (see Section 3.12). Table E–2
describes the significance of the parameters P1 to P3 in the error report.

2.6.4 RTC Test (test 0x4)
This test checks the operation of the Real Time Clock (RTC), and the nonvolatile RAM associated with the RTC.
To run the RTC Test, enter the following command:
>> test 0x4

If an error occurs, replace the system module (see Section 3.12). Table E–3
describes the significance of the parameters P1 to P3 in the error report.

2.6.5 DZ Test (test 0x5)
This test checks the serial ports on the system module and on the DHT80
asynchronous module (if installed) to ensure that the serial ports transmit and
receive serial data correctly.
To run the DZ Test, enter the following command:
>> test 0x5

You can enter parameters at the command line. Enter the first parameter, 0
or 1, to specify internal loopback (0) or external loopback (1). If you specify
external loopback, you must install a loopback connector on the serial port
under test. Enter the second parameter, a number in the range 1 to 12, to
specify the serial port you want to test. These parameters are P1 and P2
respectively (see Table E–4).

2–8 Extended Self-Test Diagnostics

If an error occurs, you can determine from the error report which serial line on
which unit failed. Table E–4 describes the significance of the parameters P1 to
P6 in the error report. Table 2–3 shows the following:
the port names
the mnemonics that the ULTRIX operating system assigns to the ports
the modules to which the ports are associated.
Table 2–3

Serial Port Numbers and ULTRIX Mnemonics

Port Name

ULTRIX mnemonic

Module

MMJ 1

/dev/tty02

System Module

MMJ 2

/dev/tty00

System Module

MMJ 3

/dev/console

System Module

MODEM

/dev/tty01

System Module

MMJ 4

/dev/tty09

DHT80 Asynchronous Module

MMJ 5

/dev/tty08

DHT80 Asynchronous Module

MMJ 6

/dev/tty07

DHT80 Asynchronous Module

MMJ 7

/dev/tty010

DHT80 Asynchronous Module

MMJ 8

/dev/tty06

DHT80 Asynchronous Module

MMJ 9

/dev/tty04

DHT80 Asynchronous Module

MMJ 10

/dev/tty03

DHT80 Asynchronous Module

B2 MODEM

/dev/tty05

DHT80 Asynchronous Module

Note The ULTRIX mnemonics shown in Table 2–3 are the default assignments. You
may change these while the ULTRIX operating system is running. See your
ULTRIX documentation.

2.6.6 SCSI Test (test 0x6)
This test verifies that the SCSI controller chip functions correctly.
To run the SCSI Test, enter the following command:
>> test 0x6

If an error occurs, replace the system module (see Section 3.12). Table E–5
describes the significance of the parameters P1 to P3 in the error report.

Extended Self-Test Diagnostics 2–9

2.6.7 LANCE Test (test 0x7)
This test verifies the functionality of the LANCE Ethernet controller chip and
support hardware on the system module. This test checks the operation of the
LANCE CSRs (control status registers), packet generation, packet reception,
CRC (Cycle Redundancy Code) generation, bad CRC detection and interrupt
control.
To run the LANCE Test, enter the following command:
>> test 0x7

If an error occurs, replace the system module (see Section 3.12).

2.6.8 EEPROM Test (test 0x8)
This test verifies that the EEPROM on the system module contains the correct
information. The test calculates the checksum of the EEPROM and compares
it with a stored value.
To run the EEPROM Test, enter the following command:
>> test 0x8

If an error occurs, replace the system module (see Section 3.12). Table E–6
describes the significance of the parameters P1 and P2 in the error report.

2.6.9 TLB Test (test 0x10)
This test checks the Translation Lookaside Buffer (TLB). The test comprises
two subtests. The first subtest writes and verifies data patterns to all of the
TLB locations. The second subtest ensures that TLB locations respond to
probes when an address match is found.
To run the TLB Test, enter the following command:
>> test 0x10

If an error occurs, replace the system module (see Section 3.12).

2.6.10 Data Cache Segment Test (test 0x15)
This test verifies that the data cache RAMs correctly cache data when
addressed through unmapped cached memory. The test also verifies that
the data cache RAMs do not cache data when addressed through unmapped
uncached memory.
To run the Data Cache Segment Test, enter the following command:
>> test 0x15

If an error occurs, replace the system module (see Section 3.12). Table E–7
describes the significance of the parameters P1 to P3 in the error report.

2–10 Extended Self-Test Diagnostics

2.6.11 Data Cache Tag Mats Test (test 0x16)
This test checks the data cache tags for addressing faults, and verifies that
none of the bits are stuck at a certain level.
To run the Data Cache Tag Mats Test, enter the following command:
>> test 0x16

If an error occurs, replace the system module (see Section 3.12). Table E–7
describes the significance of the parameters P1 to P3 in the error report.

2.6.12 Data Cache Tag Parity Mats Test (test 0x17)
This test checks the data cache tag parity for addressing faults, and verifies
that none of the bits are stuck at a certain level.
To run the Data Cache Tag Parity Mats Test, enter the following command:
>> test 0x17

If an error occurs, replace the system module (see Section 3.12). Table E–7
describes the significance of the parameters P1 to P3 in the error report.

2.6.13 Data Cache Data Parity Mats Test (test 0x18)
This test checks the data cache data parity for addressing faults, and verifies
that none of the bits are stuck at a certain level.
To run the Data Cache Data Parity Mats Test, enter the following command:
>> test 0x18

If an error occurs, replace the system module (see Section 3.12). Table E–7
describes the significance of the parameters P1 to P3 in the error report.

2.6.14 Data Cache Valid Bit Test (test 0x19)
This test checks the data cache valid bit for addressing faults, and verifies that
none of the bits are stuck at a certain level.
To run the Data Cache Valid Bit Test, enter the following command:
>> test 0x19

If an error occurs, replace the system module (see Section 3.12). Table E–7
describes the significance of the parameters P1 to P3 in the error report.

Extended Self-Test Diagnostics 2–11

2.6.15 Data Cache Tag Shorts Test (test 0x1a)
This test checks the ability of the Data Cache RAM to modify all tag bits.
To run the Data Cache Tag Shorts Test, enter the following command:
>> test 0x1a

If an error occurs, replace the system module (see Section 3.12). Table E–7
describes the significance of the parameters P1 to P3 in the error report.

2.6.16 Data Cache Reload Test (test 0x21)
This test verifies the integrity of the data cache RAMs. It also verifies that
there are no parity problems generated in data transfers between the main
memory and the data cache RAMs.
To run the Data Cache Reload Test, enter the following command:
>> test 0x21

If an error occurs, replace the system module (see Section 3.12).

2.6.17 Data Cache I-Stream Test (test 0x23)
This test verifies that the CPU, data cache RAMs, and main memory can
operate at full speed when the caches are swapped. When the caches are
swapped, the data cache is used for the instruction stream, and the instruction
cache is used for the data stream.
To run the Data Cache I-Stream Test, enter the following command:
>> test 0x23

If an error occurs, replace the system module (see Section 3.12).

2.6.18 Instruction Cache Segment Test (test 0x1b)
This test verifies that the instruction cache RAMs correctly cache data when
addressed through unmapped cached memory, and do not cache data when
addressed through unmapped uncached memory.
To run the Instruction Cache Segment Test, enter the following command:
>> test 0x1b

If an error occurs, replace the system module (see Section 3.12). Table E–7
describes the significance of the parameters P1 to P3 in the error report.

2–12 Extended Self-Test Diagnostics

2.6.19 Instruction Cache Tag Mats Test (test 0x1c)
This test checks the instruction cache tags for addressing faults, and verifies
that none of the bits are stuck at a certain level.
To run the Instruction Cache Tag Mats Test, enter the following command:
>> test 0x1c

If an error occurs, replace the system module (see Section 3.12). Table E–8
describes the significance of the parameters P1 to P3 in the error report.

2.6.20 Instruction Cache Tag Parity Mats Test (test 0x1d)
This test checks the instruction cache tag parity for addressing faults, and
verifies that none of the bits are stuck at a certain level.
To run the Instruction Cache Tag Parity Mats Test, enter the following
command:
>> test 0x1d

If an error occurs, replace the system module (see Section 3.12). Table E–8
describes the significance of the parameters P1 to P3 in the error report.

2.6.21 Instruction Cache Data Parity Mats Test (test 0x1e)
This test checks the instruction cache data parity for addressing faults, and
verifies that none of the bits are stuck at a certain level.
To run the Instruction Cache Data Parity Mats Test, enter the following
command:
>> test 0x1e

If an error occurs, replace the system module (see Section 3.12). Table E–8
describes the significance of the parameters P1 to P3 in the error report.

2.6.22 Instruction Cache Valid Bit Test (test 0x1f)
This test checks the instruction cache valid bit for addressing faults, and
verifies that none of the bits are stuck at a certain level.
To run the Instruction Cache Valid Bit Test, enter the following command:
>> test 0x1f

If an error occurs, replace the system module (see Section 3.12). Table E–8
describes the significance of the parameters P1 to P3 in the error report.

Extended Self-Test Diagnostics 2–13

2.6.23 Instruction Cache Tag Shorts Test (test 0x20)
This test checks the ability of the Instruction Cache RAMs to modify all tag
bits.
To run the Instruction Cache Tag Shorts Test, enter the following command:
>> test 0x20

If an error occurs, replace the system module (see Section 3.12). Table E–8
describes the significance of the parameters P1 to P3 in the error report.

2.6.24 Instruction Cache Reload Test (test 0x22)
This test verifies the integrity of the instruction cache RAMs. It also verifies
that there are no parity problems generated in data transfers between the
main memory and the instruction cache RAMs.
To run the Instruction Cache Reload Test, enter the following command:
>> test 0x22

If an error occurs, replace the system module (see Section 3.12).

2.6.25 Instruction Cache I-Stream Test (test 0x24)
This test verifies that the CPU, instruction cache RAMs, and main memory
can operate at full speed when the instruction cache is used for the instruction
stream, and the data cache is used for the data stream.
To run the Instruction Cache I-Stream Test, enter the following command:
>> test 0x24

If an error occurs, replace the system module (see Section 3.12).

2.6.26 Bitmap Placing Test (test 0x30)
This test determines the size of the memory and sets up a bitmap in memory
for use during the memory tests. When this test is complete, the bitmap
identifies the following:
The parts of the memory that are available for use
The parts of the memory that are faulty
The parts of the memory that are used for the bitmap
Caution This test uses a destructive sizing routine. It destroys the contents of the
memory it sizes.
This test is always run, before other memory tests, to make sure that the
memory bitmap is present. Normally, the test is run only once.

2–14 Extended Self-Test Diagnostics

To run the Bitmap Placing Test, enter the following command:
>> test 0x30

Enter the following command to get a list of all the bad pages in memory.
>> test 0x30 0x1

If an error occurs, the system generates an error report. Table E–9 describes
the significance of the parameters P1 to P6 in the error report. When this test
fails, it indicates a serious hardware error. There is not enough good memory
available to store the bitmap used for testing the memory.

2.6.27 Memory Address Test (test 0x31)
This test verifies that the CPU can uniquely address each location in memory.
The test writes a unique pattern from the starting address to the ending
address, then reads back and checks that the data is the same as that
originally written. Because this is an addressing test and not a data check, the
test ignores single bit errors that it corrects.
To run the Memory Address Test, enter the following command:
>> test 0x31

If an error occurs, the system generates an error report. Table E–9 describes
the significance of the parameters P1 to P6 in the error report.
To determine which memory bank failed, enter the following command at the
console prompt:
>> conf -m

The system displays the bad memory pages in each memory bank. Figure 3–25
identifies the connectors of the memory modules in each memory bank.

2.6.28 Memory Data Test (test 0x32)
This test verifies that the MS44 memory modules can store data correctly.
To run the Memory Data Test, enter the following command:
>> test 0x32

The system displays the bad memory pages in each memory bank. Figure 3–25
identifies the connectors of the memory modules in each memory bank.

Extended Self-Test Diagnostics 2–15

2.6.29 Moving Inversions Test (test 0x33)
This test verifies that the system can store various data patterns in all of the
memory locations provided by the MS44 memory modules.
To run the Moving Inversions Test, enter the following command:
>> test 0x33

The system displays the bad memory pages in each memory bank. Figure 3–25
identifies the connectors of the memory modules in each memory bank.

2.6.30 Memory Data Shorts Test (test 0x33)
This test checks for shorts in all of the memory locations provided by the MS44
memory modules.
To run the Memory Data Shorts Test, enter the following command:
>> test 0x34

The system displays the bad memory pages in each memory bank. Figure 3–25
identifies the connectors of the memory modules in each memory bank.

2.7 Power Supply Troubleshooting Procedures
Figure 2–3 shows a flowchart that helps you to isolate a fault in the power
supply.

2–16 Extended Self-Test Diagnostics

Figure 2–3

Flowchart for Troubleshooting the Power Supply

Start

Is power
present at
outlet?

Call an electrician.

Y
Is power
cord plugged
in?

Plug in power cord.

Switch on power switch.

Is the
green LED on
the front of the
system box
on?

Replace power supply.

End

Check the voltages listed
in Tables 2-4 and 2-5.
MLO-002949

Figure 2–4 identifies the power connector pins on the system module.
Table 2–4 lists the voltages on the respective pins.

Extended Self-Test Diagnostics 2–17

Figure 2–4

Power Connector Pin Voltages on the System Module

RE_EN05191A_90

Table 2–4

System Module Power Connector Voltages

Pin Number

Voltage

Tolerance

- 12.1 Vdc

Ground

—

Ground

—

Ground

—

+ 5.1 Vdc

+ 3.5 to + 5.25 Vdc

—

+ 5.1 Vdc

5%
(continued on next page)

2–18 Extended Self-Test Diagnostics

Table 2–4 (Cont.)
Pin Number
9

System Module Power Connector Voltages
Voltage

Tolerance

+ 12.1 Vdc

+ 5.1 Vdc

Ground

—

Ground

—

- 9 Vdc

5%
2

- 9 Vdc return

—

Measurement made with negative lead connected to pin 14

Ground for the - 9 Vdc supply (an isolated supply)

Figure 2–5 identifies the drive power connector pins. Table 2–5 lists the
voltages on the respective pins.
Figure 2–5

Drive Power Connector Pin Voltages

Pin 4 (Red Cable)
Pin 3 (Black Cable)
Pin 2 (Black Cable)
Pin 1 (Orange Cable)

MLO-002968

Table 2–5

Drive Power Connector Voltages

Pin Number

Voltage

Tolerance

+ 12.1 Vdc

Ground

—

Ground

—

+ 5.1 Vdc

Extended Self-Test Diagnostics 2–19

3
FRU Removal and Replacement
3.1 Introduction
This chapter describes the procedures that you use to remove and replace the
field replaceable units (FRUs) in the DECsystem 5100. See Table 3–1 to find
the name of the faulty FRU, then go to the section listed opposite the FRU
entry. Follow the steps in the section to remove the FRU and reverse the
procedures to replace the FRU. Always test the replacement device for proper
operation.
Caution Wear an anti-electrostatic wrist strap and use an anti-electrostatic mat when
replacing FRUs.
Table 3–1

FRU Section References

FRU

Section

DHT80 asynchronous module

3.4

RZ23 disk drive

3.6

RZ24 disk drive

3.7

TZ30 tape drive

3.8

TZK10 tape drive

3.9

RX23 diskette drive

3.10

MS44 memory module

3.11

System module

3.12

Power supply

3.13

Figure 3–1 shows the locations of the FRUs.

FRU Removal and Replacement 3–1

Figure 3–1

FRU Locations

Upper Drive
Mounting Panel

RZ23 or RZ24
Disk Drives

DHT80
Asynchronous
Module
(Optional)
RZ24 Disk Drive
(Optionally,
RZ23 Disk Drive or
RX23 Diskette Drive or
TZK10 Tape Drive)
Lower Drive Mounting Panel
TZ30 Tape Drive
(Optionally,
RZ24 Disk Drive or
RZ23 Disk Drive or
RX23 Diskette Drive or
TZK10 Tape Drive)
Power Supply
System Module

MS44 Memory Module

RE_EN05174A_90

3–2 FRU Removal and Replacement

3.2 System Unit Cover Removal
Remove the system unit cover as follows:
1

Set the on/off switch on the system unit to the off (O) position.

Disconnect all the cables connected to the system unit.

Loosen the two cover screws on the back panel of the system unit (see
Figure 3–2).

Slide the cover forward, and up, off the system unit.

Figure 3–2

Cover Screw Locations

RE_EN05175A_90

3.3 Upper Drive Mounting Panel Removal
Depending on your system configuration, the upper drive mounting panel can
contain one, two, or three hard disk drives. These drives can be either RZ23 or
RZ24 disk drives.
Remove the upper drive mounting panel as follows:
1

Remove the system unit cover (see Section 3.2).

FRU Removal and Replacement 3–3

Caution It is important to note which cables connect to which drives. When
disconnecting cables, write the type of drive and its position on a piece of
tape and wrap the tape around the connector before you disconnect the
cable. This will help you to reinstalling the upper drive mounting panel.
2

Disconnect the power cables and the SCSI bus cable from the drives on the
upper drive mounting panel (see Figure 3–3).

Unscrew the four captive screws (see Figure 3–4).

Figure 3–3

Drive Mounting Panel Power and Signal Cabling

Adapter (TZ30 Only)

SCSI Connector
to System Module

External SCSI
Connector

Power Connectors
for RX23 FDI
Boards

RZ23 or
RZ24 or
RX23 or
TZK10

Power
Supply

TZ30 or
RZ23 or
RZ24 or
RX23 or
TZK10

Lower Drive
Mounting Panel

Upper Drive
Mounting Panel

RZ23 or
RZ24

Upper Drive Panel Power
Lower Drive Panel Power
Data
RE_EN05176A_90

3–4 FRU Removal and Replacement

Figure 3–4

Releasing the Upper Drive Mounting Panel

Captive Screws (2)

Upper Drive
Mounting Panel

Captive
Screws (2)
RE_EN05177A_90

Lift the upper drive mounting panel from the lower drive mounting panel
and gently set it aside.

3.4 DHT80 Asynchronous Module Removal
Depending on the configuration, the DECsystem 5100 you are servicing can
contain the optional DHT80 asynchronous module. If the system contains this
option, you can remove the module as follows:
1

Remove the system unit cover (see Section 3.2).

Disconnect the cable to the second modem port connector, if connected (see
Figure 3–5).

FRU Removal and Replacement 3–5

Remove the two universal connector screws, and then remove the second
modem cable from the system unit (see Figure 3–5).

Figure 3–5

Second Modem Cable Removal

Universal Connector Screws (2)

Second Modem
Cable (Optional)

RE_EN05178A_90

Disconnect the signal cable from the system module. Figure 3–6 shows the
location of the connector for the signal cable (from the system module).

3–6 FRU Removal and Replacement

Figure 3–6

DHT80 Connectors

Connector for
Signal Cable
from System
Module

Connector for
Second Modem
Cable

RE_EN05182A_90

Unscrew the three captive screws on the DHT80 asynchronous module (see
Figure 3–7).

Release the DHT80 asynchronous module from the five standoffs and
remove it from the system unit (see Figure 3–7).

FRU Removal and Replacement 3–7

Figure 3–7

DHT80 Asynchronous Module Removal

Captive Screws (3)

Standoffs (2)

Standoffs (3)
RE_EN05179A_90

3.5 Lower Drive Mounting Panel Removal
The lower drive mounting panel can contain devices in combinations that are
restricted by the following rules:
You can install the RZ23 disk drives, the TZK10 tape drive, and the RX23
diskette drive in either the left, or right compartments.
You can install the TZ30 tape drive in the right compartment only.
Remove the lower drive mounting panel as follows:
1

Remove the system unit cover (see Section 3.2).

Remove the upper drive mounting panel, if not already removed (see
Section 3.3).

3–8 FRU Removal and Replacement

Disconnect the SCSI cable and the power cable connected to the drives on
the lower drive mounting panel (see Figure 3–3).

Remove the two screws securing the cover plate to the lower drive
mounting panel (see Figure 3–8). Remove the two screws securing the
cover plate to the back panel of the system unit. Remove the plate cover.
Store the screws in a safe place.

Figure 3–8

Cover Plate Removal

Panhead Screws (2)

Cover Plate

Panhead Screws (2)

RE_EN05180A_90

Remove the DHT80 asynchronous module, if installed (see Section 3.4).

Unscrew the four captive screws and remove the three panhead screws (see
Figure 3–9). Store the panhead screws in a safe place.

Slide the panel forward (with the devices attached), then lift the panel from
the system unit, and gently set it aside.

FRU Removal and Replacement 3–9

Figure 3–9

Releasing the Lower Drive Mounting Panel

Captive Screws (2)

Lower Drive Mounting Panel
Panhead Screws
(3 Loosened)
RE_EN05181A_90

3.6 RZ23 Disk Drive Removal
Depending on the configuration, the system you are servicing can contain a
maximum of three RZ23 disk drives on the upper drive mounting panel, and a
maximum of two RZ23 disk drives on the lower drive mounting panel. On the
upper drive mounting panel, the disk drive on the right side (as viewed from
the front) is the system disk. All RZ23 disk drives connect to the SCSI bus.
The RZ23 disk drive comprises two major components: the head/disk assembly
(HDA), and the module/frame assembly (see Figure 3–10).
When replacing RZ23 disk drives, replace the module/frame assembly first. If
replacing the module/frame assembly does not correct the fault, replace the
complete disk drive.
Note The HDA is not a separate FRU.

3–10 FRU Removal and Replacement

The following procedure describes how to remove a drive from the system, and
how to remove and replace the module/frame assembly:
1

Remove the system unit cover (see Section 3.2).

Remove the drive mounting panel on which the faulty drive is mounted
(see Section 3.3, or Section 3.5).

Turn the drive mounting panel over, and while supporting the RZ23 disk
drive with one hand, remove the four screws from the drive.

Disconnect the drive interconnect cable and remove the two screws (see
Figure 3–10) with a 1/8 inch Allen wrench.

Figure 3–10

Separating the RZ23 HDA from the Module/Frame Assembly

TTB_X1236_88
MA-X1046-88

Caution RZ23 disk drives are fragile. Handle them with care.
5

Push the HDA back against the rubber stops. Then lift up the front of the
HDA and remove it from the frame.

Slide the HDA into the rubber stops on the new module/frame assembly.

Screw in the two new screws supplied.

Connect the drive interconnect cable on the new module/frame assembly to
the HDA.

FRU Removal and Replacement 3–11

Position the jumper wires on the new drive module to the same position
as the jumper wires on the drive module that you removed. Figure 3–11
shows the location of the jumper wires on the RZ23 disk drive.

Figure 3–11

RZ23 SCSI ID Jumper Wire Locations

Signal Connector

Connector to HDA Module

E1
E2
E3

SCSI ID Jumper Wires

Power Connector
MLO-002943

Table 3–2 shows the jumper wire combinations for the valid SCSI ID
numbers.
Table 3–2
Address ID on
SCSI Bus

RZ23 Jumper Wire Settings
E1
E2
E3

Out

7
1

RZ23 SCSI ID Jumper Wire Combinations

Reserved address ID for SCSI bus controller.

3–12 FRU Removal and Replacement

3.7 RZ24 Disk Drive Removal
Depending on the configuration, the system you are servicing can contain a
maximum of three RZ24 disk drives on the upper drive mounting panel, and a
maximum of two RZ24 disk drives on the lower drive mounting panel. On the
upper drive mounting panel, the disk drive on the right side (as viewed from
the front) is the system disk. All RZ24 disk drives connect to the SCSI bus.
The RZ24 disk drive comprises two major components; the head/disk assembly
(HDA), and the module/frame assembly. When replacing an RZ24 disk drive,
replace the module/frame assembly first. If replacing the module/frame
assembly does not correct the fault, replace the HDA.
Note The HDA and the module/frame assembly are two separate FRUs.
The following procedure describes how to remove a drive from the system:
1

Remove the system unit cover (see Section 3.2).

Remove the drive mounting panel on which the faulty drive is mounted
(see Section 3.3, or Section 3.5).

Turn the drive mounting panel over, and while supporting the RZ24 disk
drive with one hand, remove the four torx screws from the RZ24 disk drive
with a T10 torx screw driver.

Caution RZ24 disk drives are fragile. Handle them with care.
4

Position the jumper wires on the new drive module to the same position
as the jumper wires on the drive module that you removed. Figure 3–12
shows the location of the jumper wires on the RZ24 disk drive.

FRU Removal and Replacement 3–13

Figure 3–12

RZ24 SCSI ID Jumper Wire Locations

SCSI Connector

E1 E2 E3

SCSI ID Jumper Wires

Power Connector
RE_EN05183A_90

Table 3–3 shows the jumper wire combinations for the valid SCSI ID
numbers.
Table 3–3
Address ID on
SCSI Bus

RZ24 Jumper Wire Settings
E1
E2
E3

Out

7
1

RZ24 SCSI ID Jumper Wire Combinations

Reserved address ID for SCSI bus controller.

3–14 FRU Removal and Replacement

3.8 TZ30 Tape Drive Removal
The TZ30 tape drive is on the lower drive mounting panel. It is positioned on
the right-hand side (as viewed from the front).
Remove the TZ30 tape drive as follows:
1

Remove the system unit cover (see Section 3.2).

Remove the upper drive mounting panel (see Section 3.3).

Remove the DHT80 asynchronous module (see Section 3.4).

Remove the lower drive mounting panel (see Section 3.5).

Turn the lower drive mounting panel over, and while supporting the TZ30
with one hand, loosen two of the screws holding the drive to the mounting
panel, and remove the other two screws.

Slide the drive to one side and remove it from the mounting panel.

Set the switches on the right side of the new TZ30 to the setting of the
TZ30 that you removed. Figure 3–13 shows the location of the SCSI ID
switches on the TZ30 tape drive.

Note Ensure the rubber grommets stay in place.
Figure 3–13

TZ30 SCSI Switch Locations

4
3
2
1
ON
OFF
MA-X0799-88

MLO-003379

FRU Removal and Replacement 3–15

Table 3–4 shows the TZ30 SCSI ID switch settings for the valid SCSI ID
numbers.
Table 3–4
Address ID on
SCSI Bus

TZ30 Tape Drive Switch Settings
4
3
2

Off

7
1

TZ30 SCSI ID Switch Settings

Reserved address ID for SCSI bus controller.

3.9 TZK10 Tape Drive Removal
Depending on the system configuration, the lower drive mounting panel can
contain a TZK10 tape drive in the left or right compartment, or both.
Remove the TZK10 tape drive as follows:
1

Remove the system unit cover (see Section 3.2).

Remove the upper drive mounting panel (see Section 3.3).

Remove the DHT80 asynchronous module (see Section 3.4).

Remove the lower drive mounting panel (see Section 3.5).

Turn the lower drive mounting panel over, and while supporting the TZ30
with one hand, loosen four screws holding the drive to the mounting panel,
and remove the other four screws.

Slide the drive to one side and remove it from the mounting panel.

Set the switches on the right side of the new TZK10 to the settings of the
TZK10 that you removed. Figure 3–14 shows the locations of the SCSI ID
switches on the TZK10 tape drive.

3–16 FRU Removal and Replacement

Figure 3–14

TZK10 SCSI Switch Locations

Table 3–5 shows the TZK10 SCSI ID switch settings for the valid SCSI ID
numbers.
Table 3–5
Address ID on
SCSI Bus

TZK10 Tape Drive Switch Settings
4
3
2

TBS

7
1

TZK10 SCSI ID Switch Settings

Reserved address ID for SCSI bus controller.

3.10 RX23 Diskette Drive and FDI Board Removal
Depending on the system configuration, the lower drive mounting panel can
contain an RX23 diskette drive in the left or right compartment, or both.
Remove the RX23 diskette drive and floppy disk interface (FDI) board as
follows:
1

Remove the system unit cover (see Section 3.2).

Remove the upper drive mounting panel (see Section 3.3).

Disconnect the ribbon cable and the power cable from the connectors at the
back of the RX23 diskette drive.

FRU Removal and Replacement 3–17

Unscrew the four screws securing the RX23 mounting bracket to the drive
mounting panel, and lift out the RX23 with the bracket attached (see
Figure 3–15).

Figure 3–15

RX23 Mounting Bracket Screws

RX23 Mounting Bracket

MLO-003322

Remove the four screws securing the faulty RX23 diskette drive to the
mounting bracket.

Disconnect the SCSI cable and the power cable from the connectors on the
FDI board.

Release the FDI board from the six standoffs, then lift it off the drive
mounting panel (see Figure 3–16).

3–18 FRU Removal and Replacement

Figure 3–16

Removing the FDI Board

RX23 Diskette Drive
Mounting Bracket

Captive Screws (4)

RX23 FDI Board

Standoffs (6)

Holes for RX23
Mounting Bracket (4)
Lower Drive
Mounting Panel

Holes for
Standoffs (6)

Holes for RX23
Mounting Bracket (4)

ALTERNATIVE POSITIONING
RE_EN05184A_90

Set the switches on the new FDI board to the settings of the drive that you
removed. Figure 3–17 shows the location of the SCSI switches on the FDI
board.

FRU Removal and Replacement 3–19

Figure 3–17

FDI Board SCSI Switch Locations

1
2
3
OFF
ON

SCSI ID Switches
MLO-003273

Table 3–6 shows the setting of the switches on the RX23 FDI board for the
valid SCSI ID numbers.
Table 3–6
Address ID on
SCSI Bus

RX23 Switch Settings
1
2

Off

7
1

RX23 SCSI ID Switch Settings

Reserved address ID for SCSI bus controller.

Set the select switch on the new drive to the setting on the drive that you
removed. Figure 3–18 shows the location of the select switch.

3–20 FRU Removal and Replacement

Figure 3–18

RX23 Select Switch Position

MLO-003383

3.11 MS44 Memory Module Removal
Remove an MS44 memory module as follows:
1

Remove the system unit cover (see Section 3.2).

Remove the upper drive mounting panel (see Section 3.3).

Remove the DHT80 asynchronous module, if installed (see Section 3.4).

Remove the lower drive mounting panel (see Section 3.5).

Locate the faulty MS44 memory module.

Note Note the position of the faulty MS44 memory module on the system module.
You must install a replacement in this position.
6

Push the tabs on the MS44 memory module connector away from the
center, tilt the MS44 memory module forward, and lift it out of its
connector.

Caution The MS44 memory module connectors are keyed so that you cannot install
them with an incorrect orientation. Do not try to force the module into the
connector with an incorrect orientation.
FRU Removal and Replacement 3–21

Figure 3–19

MS44 Memory Module Removal

System Module
MS44 Memory Module

RE_EN05185A_90

3.12 System Module Removal
Remove the system module as follows:
1

Remove the system unit cover (see Section 3.2).

Remove the upper drive mounting panel (see Section 3.3).

Remove the DHT80 asynchronous module, if installed (see Section 3.4).

Remove the lower drive mounting panel (see Section 3.5).

Disconnect the power cable from the system module (see Figure 3–20).

Note The power cable connector has a release tab. You must press this tab to
disconnect the power cable from the system module.
6

Remove the 12 panhead screws from the system module (see Figure 3–20).

3–22 FRU Removal and Replacement

Figure 3–20

System Module Screw Locations

Panhead Screws (4)

Power Cable

Panhead Screws (2)

System Module

Panhead Screws (3)
Panhead Screws (3)

RE_EN05186A_90

Remove the system module by carefully lifting the module out of the system
unit.

Note When reinstalling the system module, first install the connector end through
the openings in the back of the unit. Push the module back to load the
connector ground tabs. All screw holes are then aligned.
Caution Be careful not to bend the pins on the Ethernet address chip.

FRU Removal and Replacement 3–23

Remove the Ethernet address chip from the system module that you
removed (see Figure 3–21). Note the position of pin 1 (notched) on the chip.
Install the Ethernet address chip on the new system module.

Figure 3–21

Location of the Ethernet Address Chip on the System Module

Ethernet ID ROM

RE_EN05187A_90

Make sure that the security switch on the system module is in the secure
(up) position. This allows you to enter a password to make the system
secure (see Section 1.7.1).

Note To clear the password, set the security switch to the insecure (down) position
while the system is on, and then set it to the secure (up) position.

3.13 Power Supply Removal
Remove the power supply as follows:
1

Remove the system unit cover (see Section 3.2).

Remove the upper drive mounting panel (see Section 3.3).

Remove the DHT80 asynchronous module (see Section 3.4).

Remove the lower drive mounting panel (see Section 3.5).

Disconnect the power cable from the system module.

Loosen the two captive screws and the two panhead screws (see
Figure 3–22).

Disconnect, from the faulty power supply, the two cables that supply power
to the storage devices.

3–24 FRU Removal and Replacement

Lift the faulty power supply out of the system unit.

Figure 3–22

Power Supply Screw Locations

Captive Screw

Power Supply

Panhead Screws (2)

Captive Screw

RE_EN05188A_90

3.14 Options
There are two system specific options available for the DECsystem 5100 as
follows:
DHT80 asynchronous module
MS44 memory module

3.14.1 DHT80 Asynchronous Module
The DHT80 asynchronous module provides seven DEC423 ports and one RS232
full modem port. Install the DHT80 asynchronous module as follows:
1

Remove the system unit cover (see Section 3.2).

Remove the upper drive mounting panel (see Section 3.3).

FRU Removal and Replacement 3–25

Remove the two screws securing the cover plate to the lower drive
mounting panel (see Figure 3–23). Remove the two screws securing
the cover plate to the back panel of the system unit. Remove the cover
plate. Store the screws in a safe place.

Figure 3–23

Accessing the Asynchronous Connector on the System
Module

Panhead Screws (2)

Cover Plate

Panhead Screws (2)

Standoffs (3)
RE_EN05190A_90

Install the DHT80 asynchronous module onto the five standoffs on the
lower drive mounting panel (see Figure 3–24).

Tighten the three captive screws on the asynchronous communications
module (see Figure 3–24).

3–26 FRU Removal and Replacement

Figure 3–24

DHT80 Asynchronous Module Installation

Universal
Connector
Screws (2)

Second Modem
Cable
Ribbon Cable

DST80
Asynchronous
Module
Captive Screw (1)
Modem Connector
Captive Screws (2)
RE_EN05189A_90

Connect one end of the ribbon cable (supplied with the option) to the
asynchronous connector on the system module. Lock the connector in place
with the connector clips.

Connect the other end of the ribbon cable to the DHT80 asynchronous
module (see Figure 3–23). Lock the connector in place with the connector
clips.

Install the cover plate, using the four screws retained in step 3.

Connect the second modem cable to the second modem connector on the
DHT80 asynchronous module (see Figure 3–24).

10 Align the other cable connector with the cut-out on the back panel of the
system unit. Secure the connector to the chassis with the two universal
connector screws (see Figure 3–24).

FRU Removal and Replacement 3–27

11 Reassemble the system.
12 Run the diagnostic tests (see Chapter 2) to make sure that the option is
operating correctly.

3.14.2 MS44 Memory Modules
The system module in the DECsystem 5100 contains eight connectors for MS44
memory modules. These connectors make up four memory banks. You must
install two MS44 memory modules to fill a memory bank. Each MS44 memory
option contains two MS44 memory modules as follows:
The MS44-BA memory option contains two 4MB memory modules
(MS44-AA).
The MS44-DA memory option contains two 16MB memory modules
(MS44-AC).
You can add memory to your system by installing one of these memory options
into one of the memory banks on the system module.
Note You can install both types of memory option on the system module, but you
cannot install a 4MB memory module, and a 16MB memory module, in the
same memory bank.
Note In systems with mixed memory module types, you must position the higher
density memory modules (MS44-DA) in the lowest possible memory banks.
Table 3–7 shows the possible memory configurations.

3–28 FRU Removal and Replacement

Table 3–7

Possible Memory Configurations
Memory Size
(MB)

Bank 0

Bank 1

Bank 2

Bank 3

MS44-BA

MS44-DA

MS44-BA

MS44-DA

MS44-BA

MS44-DA

MS44-BA

MS44-DA

MS44-BA

MS44-DA

MS44-BA

MS44-DA

MS44-BA

104

MS44-DA

128

Install an MS44 memory option as follows:
1

Remove the system unit cover (see Section 3.2).

Remove the upper drive mounting panel (see Section 3.3).

Remove the DHT80 asynchronous module, if installed (see Section 3.4).

Remove the lower drive mounting panel (see Section 3.5).

Identify the connectors of the memory bank into which you want to install
the memory modules (see Figure 3–25 and Table 3–7).

FRU Removal and Replacement 3–29

Figure 3–25

Memory Bank Connector Identification

J 29 (Bank 0)
J 28 (Bank 1)
J 27 (Bank 2)
J 26 (Bank 3)

J 30 (Bank 0)
J 31 (Bank 1)
J 32 (Bank 2)
J 33 (Bank 3)
RE_EN05192A_90

Insert the first MS44 memory module, with the side containing the bar
code label facing up, into the connector on the system module. Gently press
down on the module, until the tabs on the connector snap, locking the
module into position.

Caution The connectors are keyed so that you can install MS44 memory modules
with the correct orientation. Do not force the modules into the connectors
with an incorrect orientation.
7

Repeat the procedure in step 6 for the second MS44 memory module,
installing it into the other connector of the memory bank.

Reassemble the system unit.

Run the diagnostic tests (see Chapter 2) to make sure that the option is
operating correctly.

3–30 FRU Removal and Replacement

A
Console Commands
This appendix describes the console commands that you can enter when your
system is in console mode.
Note If the system is in security mode (that is, the console prompt is S>), you can
enter only two valid commands (without options or arguments). The two
commands are: boot and passwd.
Note The console commands are case sensitive. You must enter lowercase commands
on your console terminal in lowercase letters.

A.1 Boot Command (boot)
This command specifies a file from which the system loads the operating
system software. The format of this command is as follows:
boot [-f FILE] [-(m | s)] [-n] [args]
The -f option followed by the FILE parameter specifies the file you want
to use during a boot procedure. If you do not specify the -f option and a
FILE parameter, then the system uses the file specified by the environment
variable, bootpath. See Section A.14 for more information on the bootpath
variable.
The FILE parameter has the format:
dev(controller,unit,lbn)filename
dev - specifies the device from which you are booting the operating
system software. Typical device types are: hard disk (rz), tape (tz), and
network (mop).
controller - specifies the ID number of the controller.

Console Commands A–1

unit - specifies the unit number of the device from which you are
booting the operating system software.
lbn - specifies the logical block number that specifies the absolute block
number from the beginning of the disk.
filename - specifies the name of the operating system software file.
Note When you do not enter values for controller, unit, or lbn, the system uses
default values of zero.
The -m option specifies that the operating system software file boots in
multiuser mode.
The -s option specifies that the operating system software file boots in
singleuser mode.
Note When you do not specify the -m option or the -s option, the system uses the
default option, -m.
The -n option specifies that the file loads but does not run.
The parameter, args, represents data that you want to pass to the booting
operating system file.

A.2 Configuration Command (conf)
This command displays the system configuration. The format of this command
is:
conf [-(b | f | m)]
The -b option directs the system to display a brief system configuration.
Example A–1 shows an example of a brief system configuration display.

A–2 Console Commands

Example A–1

Brief System Configuration Display

>> conf -b
hardware: revision 1
firmware: revision 1
ethernet hardware address: 08-00-2b-12-7f-58
option board: Asynch Comm, 8 ports
memory: total size 16MBs
scsi peripherals
unit type
product
removable/fixed
0 disk
RZ56
(C) DEC
fixed
2 cdrom
RRD40
TM DEC
removable
3 tape
TZK50
removable
5 tape
TZ30
removable
7 host adapter

The -f option directs the system to display a full system configuration table.
Example A–2 shows an example of a full system configuration display.
Example A–2

Full System Configuration Display

>> conf -f
hardware: revision 1
firmware: revision 1
cpu: revision 2.32
fpu: revision 3.32
security switch: unsecure mode
password: clear
eeprom: valid
ethernet hardware address: 08-00-2b-12-7f-58
option board: Asynch Comm, 8 ports
memory: total size 16MBs
bank0
4MB SIMMs size: 8MBs
0 bad pages
bank1
4MB SIMMs size: 8MBs
0 bad pages
scsi peripherals
unit type
product
removable/fixed
0 disk
RZ56
(C) DEC
fixed
2 cdrom
RRD40
TM DEC
removable
3 tape
TZK50
removable
5 tape
TZ30
removable
7 host adapter

capacity
634 MBs
571 MBs

The -m option directs the system to display the bad memory pages in each
memory bank.

Console Commands A–3

A.3 Continue Command (continue)
This command causes the CPU to begin executing instructions from the
address currently stored in the program counter. The format of this command
is:
continue
Note You can use this command to return to the operating system from the console
mode. This works only if you have set the variable bootmode so that you enter
console mode by pressing the halt/reset button.

A.4 Deposit Command (d)
This command deposits a single byte, halfword or word value at the address
you specify. The format for this command is as follows:
d [-(b | h | w)] ADDR VAL
The -b option indicates a single byte.
The -h option indicates a halfword.
The -w option indicates a word.
Note If you do not specify any of these options, the system uses the default option,
-w.
The parameter ADDR represents a virtual address. For example, to
examine physical address location 0, enter an ADDR value of 0x80000000.
Note When you do not enter an address, the default address is the address
immediately before the last address accessed by the last e (examine), or d
(deposit) command.
The parameter VAL represents a specific numeric value.

A.5 Disable Command (disable)
This command removes a console device from the current list of enabled
console devices.
disable DEV
The parameter DEV is an ASCII string representing the console device you
want to disable. You can enter the following values:
tty(0)
tty(1)

A–4 Console Commands

tty(2)
tty(3)
If you do not enter a value for DEV, the system displays the current list of
enabled console devices.

A.6 Dump Command (dump)
This command shows a formatted display of the contents of memory. The
format of this command is as follows:
dump [-(B | c | d | o | u | x)] [-(b | h | w)] RNG
The -B option displays memory in binary format.
The -c option displays memory in ASCII format.
The -d option displays memory in decimal format.
The -o option displays memory in octal format.
The -u option displays memory in unsigned decimal format.
The -x option displays memory in hexadecimal format.
The -b option displays memory in bytes.
The -h option displays memory in halfwords.
The -w option displays memory in words.
Note When you do not specify any of the options -b, -h , or -w, the system uses the
default option, -w.
The parameter RNG indicates a range of memory contents that the system
displays. You can specify the memory range in three different ways:
ADDR - displays the contents of a single address location specified by the
parameter ADDR.
ADDR#CNT - displays the contents of a number of address locations. The
parameter ADDR specifies the address of the first location that the system
displays. The parameter CNT specifies the number of address locations
that the system displays after the starting address.
ADDR1:ADDR2 - displays the contents of the address locations between
the two addresses ADDR1 and ADDR2.

Console Commands A–5

A.7 Examine Command (e)
This command displays the byte, halfword, or word of the address you specify.
The format of this command is as follows:
e [-(b | h | w)] ADDR
The -b option indicates a single byte.
The -h option indicates a halfword.
The -w option indicates a word.
Note When you do not specify any of the options -b, -h, or -w, the system uses the
default option, -w.
The parameter ADDR represents a virtual address. For example, when
you want to examine the contents of physical address location 0, enter an
ADDR value of 0x80000000.

A.8 Enable Command (enable)
This command adds a console device to the current list of enabled console
devices.
enable DEV
The parameter DEV is an ASCII string representing the console device you
want to enable. You can enter the following values:
tty(0)
tty(1)
tty(2)
tty(3)
If you do not enter a value for DEV, the system displays the current list of
enabled console devices.

A.9 Fill Command (fill)
This command places the value that you specify in the range of memory
locations that you specify. When you do not specify a value, the system puts
zeros in the range of memory locations that you specify. The format of this
command is as follows:
fill [-(b | h | w)] [-v VAL] RNG
The -b option indicates a single byte.

A–6 Console Commands

The -h option indicates a halfword.
The -w option indicates a word.
The -v option specifies that you are putting the numeric value, represented
by the parameter VAL, into the memory locations that you specify.
The parameter RNG indicates the range of memory into which the system
places the value represented by the parameter VAL. You can specify the
memory range in three different ways:
ADDR - specifies a single address location.
ADDR#CNT - specifies a range of address locations. The parameter
ADDR specifies the first address location of the range. The parameter
CNT specifies the number of address locations in the range.
ADDR1:ADDR2 - specifies a range of address locations. The parameter
ADDR1 specifies the first address of the range. The parameter ADDR2
specifies the last address of the range.

A.10 Go Command (go)
This command transfers program control to the address you specify. The
format of this command is as follows:
go [PC]
The parameter PC is the entry point address to which you want to transfer
control.
When you do not specify an entry point address, the system uses the entry
point address of the program module that the system has most recently loaded.
If the system has not loaded a program module, it uses address 0 as the entry
point address.

A.11 Help Command (help) (?)
This command displays the correct format of the command you specify. The
format of this command is as follows:
help [CMD]
or,
? [CMD]

Console Commands A–7

The parameter CMD represents the command for which you want information.
When you do not specify a command, the system displays the complete console
menu. Example A–3 shows the console menu.
Example A–3

Console Menu

A.12 Init Command (init)
This command performs a full system initialization. The format of this
command is as follows:
init
The init command performs the same initialization procedure that is performed
when you turn on the system unit, or when you press the halt/reset button.
However, the system does not execute the power-up self-test.

A.13 Password Command (passwd)
This command allows you to:
enter privileged mode
set a new password
clear the currently stored password

A–8 Console Commands

exit privileged mode
Note If the system is in secure mode and you do not know the password, you must set
the security switch on the system module to the insecure (down) position while
the system is on. This action resets the password to zero. You can now enter a
new password and make the system secure, using the passwd command. See
Section 1.7.1 for more information on system security.
The format of the command is:
passwd [-(s | c | u)]
When you do not specify any of the options in the command, the system
prompts you for the system password. Enter the password.
Note The system does not display the password as you enter it.
When the password you enter matches the current system password, the
system assigns you a privileged status.
When the password you enter does not match the current system password,
the system assigns you an unprivileged status. Also, the system maintains a
record of the number of incorrect passwords entered.
The -s option allows you to set the system password. The system prompts
you for a password twice. When you enter the same password each time,
the system accepts the password you enter as the new system password.
On the next system power-up, the console prompt is S> and you must enter
the correct password.
The -c option allows you to clear the system password. This is equivalent
to disabling system security.
The -u option assigns you an unprivileged status.

A.14 Print Environment Command (printenv)
This command displays the current value of the specified environment variable.
The format of this command is as follows:
printenv [EVAR]
The parameter EVAR represents the variable, the value of which, you want
to display. When you do not specify a variable, the system displays a table
showing the values of all the environment variables. Example A–4 is a typical
environment variable table.

Console Commands A–9

Example A–4

Environment Variable Table

console=0
scsiid=7
systype=0x820c0101
baud0=9600
baud1=9600
baud2=9600
baud3=9600
bitmap=0xa07ff800
bitmaplen=0x200
iooption=0x1
bootpath=rz()vmunix
bootmode=a

The system puts the environment variables into classes according to the type
of memory in which they reside as follows:
volatile - the system stores variables in memory that is lost when you
switch the power off
nonvolatile - the system stores variables in memory that is not lost when
you switch the power off
initialized - the console program automatically initializes the memory that
stores the values of these variables.
Table A–1 describes the types of default environment variables.
Table A–1

Default Environment Variables

Variable

Type

Description

baud0

Nonvolatile

Baud rate of the tty(0) terminal line. The
allowed values are as follows: 75, 110, 134, 150,
300, 600, 1200, 2400, 4800, 9600 (default). The
system enables this terminal line at power-up.

baud1

Initialized

Baud rate of the tty(1) terminal line. The
allowed values are as follows: 75, 110, 134, 150,
300, 600, 1200, 2400, 4800, 9600 (default). The
system disables this terminal line at power-up.

baud2

Initialized

Baud rate of the tty(2) terminal line. The
allowed values are as follows: 75, 110, 134, 150,
300, 600, 1200, 2400, 4800, 9600 (default). The
system disables this terminal line at power-up.
(continued on next page)

A–10 Console Commands

Table A–1 (Cont.)

Default Environment Variables

Variable

Type

Description

baud3

Initialized

Baud rate of the tty(3) terminal line. The
allowed values are as follows: 75, 110, 134, 150,
300, 600, 1200, 2400, 4800, 9600 (default). The
system enables this terminal line at power-up.

bootpath

Nonvolatile

A string containing the complete boot path
specification. The boot path has two fields: the
boot device and the boot file (see Section A.1.)

bootmode

Nonvolatile

A one character control code that specifies the
action taken by the console program on power-up
or when you press the halt/reset button. The
allowed control characters are as follows:
a - automatically boots the system from
the device and file specified in the bootpath
variable
d - halts the system before running the
power-up diagnostics
h - enables the halt interrupt mechanism

bitmap

Initialized

The hexadecimal address of the memory bitmap
table. The memory bitmap table is a vector
of words. Each bit in each word corresponds
to a page in memory. If the bit is set to 1, the
memory page is good and available to the system.
If the bit is set to 0, the page is bad.

bitmaplen

Initialized

The length of the memory bitmap in bytes. Do
not change the value of this variable.

iooption

Nonvolatile

Specifies the type of Input/Output Option
present.

console

Nonvolatile

Always selects tty (0).

scsiid

Nonvolatile

Specifies the SCSI ID number assigned to the
SCSI bus adapter. The default value is 7.

systype

Initialized

Provides information identifying the CPU type,
the firmware revision level, and the hardware
revision level.

Console Commands A–11

A.15 Set Environment Command (setenv)
This command assigns a new value to the specified environment variable. The
format of this command is as follows:
setenv EVAR STR
The parameter EVAR is the variable that you want to set.
The parameter STR is the string value, to which you want to set the
variable.
Table A–1 provides descriptions of the default environment variables that
the system sets up. You can add your own environment variables but these
variables are stored in volatile memory. The environment variables table can
contain up to 16 variables, a total of 256 characters.

A.16 SCSI Command (scsi)
This command allows you to inquire, reset and test devices on the SCSI bus.
The format of this command is as follows:
scsi [? | a1] [a2] [a3]
Enter the command scsi ? and the system displays a summary of the scsi
commands that you can enter. Example A–5 shows the scsi command
summary that the system displays.
Example A–5

SCSI Command Summary

scsi

a1
rs
ri
st
du
cd
ct
cr
fm
iq
ms
ry
sn
sp
sr
su

unit
unit
unit
unit
unit
unit
unit
unit
unit
unit
unit

A–12 Console Commands

[r]
[r]
[r]

Reset the SCSI bus
Reset the sii
Dump the sii status registers
Dump all sii registers
Read/write test for SCSI hard drives
Read/write test for TZ30 tape drive
Read only self test for RRD40 ROM disk drive
Format <UNIT> using default parameters
Show inquiry response from <UNIT>
Show mode sense response from <UNIT>
Show ready status from <UNIT>
Show request sense response from <UNIT>
Stop <UNIT>
Start <UNIT>
Setup <UNIT>, wait for ready status

A.17 Test Command (test)
This command allows you to run the ROM based diagnostic test that you
specify by entering the test number. The format of this command is as follows:
test [?] [-v] [-(f | h)] [-r[REPS]] [-s] test_number [test_parameters]
The ? option displays a list of the tests and test scripts (groups of tests)
that the system can run.
The -v option activates the diagnostic report mode for the duration of test
execution.
The -f option forces the test to continue even if an error is detected. In
general, the default is to stop the test on error detection.
The -h option forces any diagnostic test or diagnostic script to halt as soon
as it encounters an error.
The -r option allows you to repeat a test or test script. The parameter
REPS defines the number of times the test repeats. If you do not specify
a value for REPS, the test repeats continuously. Press Ctrl/c to stop a
repeating test.
The -s option allows you to create and execute a script of tests. When you
specify this option, the system prompts you to enter each test number of
the script, one line at a time. End the script by pressing Return twice.
The parameter test_number is the number of the test that you want to run.
You must enter this number in hexadecimal format.
The parameter test_parameters are the parameters that you want to pass
to the test. See Appendix E for more information on test parameters.
Chapter 2 provides more information about the tests that you can perform.

A.18 Unset Environment Command (unsetenv)
This command removes the specified variable from the environment variables
table. The format of this command is as follows:
unsetenv EVAR
The parameter EVAR represents the variable that you want to remove. See
Table A–1 for a description of the environment variables that the system sets
up by default.
Note The unsetenv command has no effect on environment variables that are stored
in nonvolatile memory.

Console Commands A–13

B
System Specifications

Table B–1

System Specifications

Subject

Description

Processor

KN230 (20 MHz)

EPROM

256KB

EEPROM

32KB

Instruction Cache RAM

64KB

Data Cache RAM

64KB

DRAM memory

8MB, expandable to 32MB or 128MB

Hard disk

RZ23 (104MB) or RZ24 (209MB), 5 devices maximum 1

Tape drive

TZ30 or TZK10 1

Diskette drive

RX231

Terminals

Supports VT series terminals

Interfaces

1 SCSI port, 1 ThinWire Ethernet port2 , 1 standard Ethernet port2 ,
4 asynchronous lines provided by the system module (one
asynchronous line has full modem control)
8 asynchronous lines provided by the optional DHT80 asynchronous
module (one asynchronous line has full modem control)

Input voltage

Automatically adjusting AC input. Range: 100-120 VAC to 220-240
VAC

Depends on configuration

You cannot use both Ethernet types simultaneously

(continued on next page)

System Specifications B–1

Table B–1 (Cont.)

System Specifications

Subject

Description

Input current

Typically 3.2 A in a 110 VAC circuit; 1.9 A in a 220 VAC circuit

Power

Typically 230 W

Frequency

47 to 63 Hz

Table B–2

System Unit Metrics

Weight1

Height

Width

Depth

20.5 kg

14.99 cm

46.38 cm

40.00 cm

45 lb

5.90 in

18.26 in

15.75 in

Depends on configuration

Table B–3

System Storage Conditions

Temperature range

5°C to 50°C (41°F to 122°F )

Relative humidity

10% to 95% at 66°C (noncondensing)

Altitude

0 to 2400 m (0 to 8000 ft )

Maximum wet bulb temperature

32°C (90°F)

Minimum dew point

2°C (36°F)

Table B–4

System Operating Conditions and Nonoperating Conditions

Operating Conditions
Temperature range

10°C (50°F) to 32°C (90°F) with TZ30 tape drive;
otherwise 10°C (50°F) to 40°C (104°F)

Temperature change rate

11°C (20°F) degree per hour maximum

Relative humidity

10% to 90% noncondensing

Maximum wet bulb temperature

28°C (82°F)

Minimum dew point

2°C (36°F)

Altitude

2400 m (8000 ft) at 36°C (96°F)
(continued on next page)

B–2 System Specifications

Table B–4 (Cont.)

System Operating Conditions and Nonoperating Conditions

Nonoperating Conditions
Temperature range

–40°C (–40°F) to 66°C (151°F)

Relative humidity

10% to 95% at 66°C (151°F)

Altitude

4900 m (16,000 ft)

Maximum wet bulb temperature

28°C (82°F)

Minimum dew point

2°C (36°F)

Table B–5

TZ30 Tape Drive Specifications

Subject

Description

Mode of operation

Streaming

Media

12.77 mm (½ in) unformatted magnetic tape

Bit density

2624 b/cm (6667 b/in)

Number of tracks

Transfer rate (at host)

62.5KB/s

Tape speed

190 cm/s (75 in/s)

Track format

Multiple track, serpentine recording

Cartridge capacity

95MB, formatted (approximately)

Table B–6

TZK10 Tape Drive Specifications

Subject

Description

Mode of operation

Streaming

Media

DC6320 or Digital approved equivalent

Data density

16,000 bpi

Number of tracks

Transfer rate

200KB/s at average streaming mode
1.5MB/s at SCSI (maximum)

Tape speed

3.05 cm/s

Track format

Multiple track, serpentine recording

Bytes per block

1024

Blocks per frame

Cartridge capacity

325MB

System Specifications B–3

Table B–7

RZ23 and RZ24 Hard Disk Drive Specifications

Formatted Storage Capacity

RZ23

RZ24

Per drive

104MB

209MB

Per surface

13MB

26.2MB

Bytes per track

16,896

19,456

Bytes per block

512

Blocks per track

38 and 1 spare

Blocks per drive

204,864

409,792

Spare blocks per track

Spare tracks

Spare blocks per drive

6,208

10,944

Performance

RZ23

RZ24

Transfer rate to/from media

1.25MB/sec

1.5MB/sec

Transfer rate to/from buffer (asynchronous)

1.5MB/sec

3MB/sec

Transfer rate to/from buffer (synchronous)

1.5MB/sec

4MB/sec

Seek-time track to track

8 msec

5 msec

Seek-time average

25 msec

16 msec

Seek-time maximum (full stroke)

45 msec

Average latency

8.4 msec

Rotational speed

3575 RPM

35 msec

8.5 msec
0.1%

3497 RPM

Start time (maximum)

20 sec

Stop time (maximum)

20 sec

Interleave

1:1

Functional Specifications

RZ23

RZ24

Recording density (bpi)

23,441

31,800

Flux density (fci)

15,627

21,200

Track density (tpi)

1150

1700

Tracks/surface

776

1348

R/W heads

Disks

Time-to-process ECC (512 Bytes)

<100 msec

B–4 System Specifications

Table B–8

RX23 Diskette Drive Specifications

Subject

Description

Diskette size

9 cm (3.5 in)

Diskettes/diskette drive

Data capacity

1.4MB (RX23K)

Track density

135 TPI

Storage capacity (high density)

600KB

System Specifications B–5

C
Recommended Spares List

Table C–1

DECsystem 5100 FRUs

Part Number

Description

Quantity

TBS

DECsystem 5100 system module

54-20428-01

DHT80 asynchronous module

MS44-AA

4MB memory module

MS44-BA

8MB memory option

MS44-CA

16MB memory module

MS44-DA

32MB memory option

RZ23-E

104MB SCSI disk drive with logic module

29-27240-01

RZ23 module/frame assembly

30-29999-01

RZ23 104MB HDA

RZ24-E

209MB SCSI disk drive with logic module

TZ30-AX

TZ30 95MB/256MB tape drive

TZK10-TBS

TZK10 TBS?MB tape drive

RX23-E

RX23 diskette drive

H7822-00

Power supply

TBS

Cable from system module to asynchronous communications module

TBS

Second modem port cable

TBS

Internal SCSI cable

(continued on next page)

Recommended Spares List C–1

Table C–1 (Cont.)

DECsystem 5100 FRUs

Part Number

Description

Quantity

17-02219-01

Power cable for upper drive mounting panel devices

17-02225-01

Power cable for lower drive mounting panel devices

1 17-00083-43

System power cord (USA)

12-22196-01

Standard Ethernet loopback

12-25869-01

ThinWire Ethernet T-connector

12-26318-01

ThinWire Ethernet cable 50-ohm terminator

12-25083-01

MMJ loopback connector (H3103)

12-30552-01

50-pin SCSI terminator

17-00811-03

BC16E-25 DECconnect office cable (25 feet)

17-00811-04

BC16E-50 DECconnect office cable (50 feet)

1 For 120 VAC US/Canada/Japan orders only. All 240 VAC country specific power cords are a line

item on the order.

Table C–2

Miscellaneous Parts

Part Number

Description

Quantity

30-25145-05

RX23 blank media

12-23599-01

25-pin passive adapter (H8571-A)

C–2 Recommended Spares List

D
Status LED Display
This appendix describes the significance of the status LED display on the
back of the system unit. The status LED display comprises eight LEDs.
These LEDs provide system status information during power-up and extended
self-test diagnostics. Table D–1 describes the functions of the individual
LEDs.
Table D–1

Status LED Display Interpretation

LED Number †
3210 7654

Significance

1XXX XXXX

Indicates that the system cannot write to the EEPROM on
the system module

0XXX XXXX

Indicates that the system can write to the EEPROM on the
system module

XX1X XXXX

Indicates that there is a 32MB memory option in memory
bank 0

XX0X XXXX

Indicates that there is a 8MB memory option in memory
bank 0

X1XX XXXX ‡

Indicates that the maximum baud rate for the serial ports is
9600 baud

X0XX XXXX ‡

Indicates that the maximum baud rate for the serial ports is
19.2 kbaud or 38.4 kbaud

†1 indicates the LED is on, 0 indicates the LED is off, and X indicates a don’t care state.
‡Function of LED 2 during normal operation. LED 2 has a different significance during diagnostic
tests.

(continued on next page)

Status LED Display D–1

Table D–1 (Cont.)

Status LED Display Interpretation

LED Number †
3210 7654

Significance

XXX1 XXXX

Indicates that reset is enabled and halt disabled

XXX0 XXXX

Indicates that halt is enabled and reset disabled

X1XX 1111

Initial state at power-up, no code has executed

X1XX 1110

Entered ROM, some instructions have executed

X1XX 1101

Stack tested and set

X1XX 1100

NXM taken

X1XX 1011

Security initialization

X1XX 1010

DZ initialization

X1XX 1001

Exception tests

X1XX 1000

FPU test

X1XX 0111

Write buffer test

X1XX 0101

Data cache tag test

X1XX 0110

Instruction cache tag test

X1XX 0100

TLB test

X1XX 0011

Data cache test

X1XX 0010

Instruction cache test

X1XX 0001

Data cache i-stream test

X1XX 0000

Instruction cache i-stream test

X0XX 1111

Memory bitmap test

X0XX 1110

Memory address test

X0XX 1101

Memory data test

X0XX 1100

Memory moving inversion test

X0XX 1011

Memory data shorts test

X0XX 1010

RTC tests

X0XX 1001

DZ tests

X0XX 1000

SII tests

†1 indicates the LED is on, 0 indicates the LED is off, and X indicates a don’t care state.

(continued on next page)

D–2 Status LED Display

Table D–1 (Cont.)

Status LED Display Interpretation

LED Number †
3210 7654

Significance

X0XX 0111

LANCE tests

X0XX 0101

EEPROM test

X0XX 0110

Option card test

X0XX 0100

Reserved

X0XX 0011

Console I/O mode

X0XX 0010

Primary boot operation

X0XX 0001

Secondary boot operation

X0XX 0000

Operating system running

†1 indicates the LED is on, 0 indicates the LED is off, and X indicates a don’t care state.

Status LED Display D–3

E
Parameters Returned by Diagnostic Tests
Certain diagnostic tests use parameters. For each test that uses parameters, a
table in this appendix describes the significance of the parameters.
Note In the tables following, parameter values marked NA are not applicable.
Table E–1
No.

Name

Exception Test (t 0x1) Parameters
Min

Max

Default

Description

actual

The actual exception code taken

expected

The exception code that should have
been taken

Table E–2

Write Buffer Test (t 0x3) Parameters

No.

Name

Min

Max

Default

Description

actual

The data pattern read back from the
write buffer address location under test

expected

The data pattern written to the write
buffer address location under test

address

The write buffer address location under
test

Parameters Returned by Diagnostic Tests E–1

Table E–3

Real Time Clock Test (t 0x4) Parameters

No.

Name

Min

Max

Default

Description

actual

The data pattern read from the address
location under test

expected

The data pattern written to the address
location under test

address

The address location under test

Table E–4

DZ Test (t 0x5) Parameters

No.

Name

Min

Max

Default

Description

loopback

0 = Internal loopback mode,
1 = External loopback mode

line

Serial line number to test

iteration

999

Iteration count - specifies the number of
times the test executes

xmit

Data transmitted on a given line

rcvd

Data received on a given line

line

The line on which an error was detected

Table E–5

SCSI Test (t 0x6) Parameters

No.

Name

Min

Max

Default

Description

actual

The data pattern read from the SII chip
or buffer

expected

The data pattern the CPU expects to
read from the SII chip or buffer

address

The address of the location that failed to
store the data properly

E–2 Parameters Returned by Diagnostic Tests

Table E–6

EEPROM Test (t 0x8) Parameters

No.

Name

Min

Max

Default

Description

xsum_was

Calculated checksum of EEPROM

xsum_
should_
be

Checksum stored on the EEPROM

Table E–7

Data Cache Test (t 0x15, t 0x16, t 0x17, t 0x18, t 0x19, t 0x1a) Parameters

No.

Name

Min

Max

Default

Description

actual

The data pattern read back from the
data cache RAM address location under
test

expected

The data pattern written to the data
cache RAM address location under test

address

The data cache RAM address location
under test

Table E–8

Instruction Cache Test (t 0x1b, t 0x1c, t 0x1d, t 0x1e, t 0x1f, t 0x20)
Parameters

No.

Name

Min

Max

Default

Description

actual

The data pattern read back from the
instruction cache RAM address location
under test

expected

The data pattern written to the
instruction cache RAM address location
under test

address

The instruction cache RAM address
location under test

Parameters Returned by Diagnostic Tests E–3

Table E–9

Memory Test (t 0x30, t 0x31, t 0x32, t 0x33, t 0x34) Parameters

No.

Name

Min

Max

Default

Description

start_addr

0xA0000000

0xA8000000

0xA0010000

The first address of memory
to test

end_addr

0xA0000000

0xA8000000

0xA0010000

The last address of memory
to test

offset

0x1

0x10000000

0x4

Offset in longwords to next
address of memory to test

actual

The actual data read from
memory

expected

The data that the CPU
expected to read from
memory

address

The address of the failed
memory location

E–4 Parameters Returned by Diagnostic Tests

Index
A
Asynchronous lines test, 2–8

B
boot command, A–1
Boot command
See also operating system, 1–18
use of, 1–18
Boot device
specifying, A–1
types of, 1–18
bootmode variable
defined, A–11
bootpath variable
defined, A–11
use of, A–1

C
? command, A–7
Communications device
type of, 1–2
conf command, A–2
Console mode, 1–14
command conventions, 1–17
command descriptions, 1–17
control characters, 1–17
menu, 1–16
Console mode menu

Console mode menu (Cont.)
See ? command, 1–16
See help command, 1–16
Console program
version, 1–7
Console terminal
connecting, 2–1
setup, 2–1
continue command, A–4
Control characters
in console mode, 1–17

D
Data cache tests, 2–10 to 2–12
data parity test, 2–11
reload test, 2–12
segment test, 2–10
tag parity test, 2–11, 2–13
tag shorts test, 2–12
tag test, 2–11
valid bit test, 2–11
d command, A–4
DHT80 asynchronous module
removal of, 3–5
Diagnostics, 2–1
Dimensions
system unit, B–2
disable command, A–4
Disk drive

Index–1

Disk drive (Cont.)
types of, 1–2
Diskette drive
type of, 1–2
Drive mounting panel
power cabling, 3–4
signal cabling, 3–4
dump command, A–5
DZ test, 2–8

E
EEPROM test, 2–10
enable command, A–6
entry point address, A–7
Environment variables
default set, A–9
defined, A–9
types of, A–10
user defined, A–12
Error reports
interpretation of, 2–5
Error Report Summary
example of, 1–7
Errors
on status LED display, 1–12
Error severity level, 2–5
Ethernet
address, 1–7
Ethernet address chip
location of, 3–23
removal of, 3–23
Ethernet ID chip
location of, 3–23
removal of, 3–23
Ethernet tests
LANCE test, 2–10
examine command, A–6
Exception test, 2–7
Extended self-test, 2–4 to 2–16
data cache tests, 2–10 to 2–12
instruction cache tests, 2–12 to 2–14
list of, 2–6
memory tests, 2–14 to 2–16
Miscellaneous tests, 2–7 to 2–10

Index–2

Extended self-test (Cont.)
preparing for, 2–2
running, 2–4
Extended self-tests, 2–1

F
Factory installed software
See FIS, 1–1
Fans
troubleshooting, 1–5
FDI Board
removal of, 3–18
fill command, A–6
FIS
defined, 1–1
Floating point unit test, 2–8
FRU
list, 3–1
locations, 3–1
section references, 3–1
See field replaceable unit, 3–1

G
go command, A–7

H
Halt/Reset button
location, 1–10
Hardware specifications
RX23 diskette drive, B–5
RZ23 disk drive, B–4
RZ24 disk drive, B–4
system unit, B–1
TZ30 tape drive, B–3
TZK10 tape drive, B–3
HDA
See Head/disk assembly, 3–10
Head/disk assembly
removal of, 3–10
See HDA, 3–10
help command, A–7

I
init command, A–8
Instruction cache tests, 2–12 to 2–14
data parity test, 2–13
reload test, 2–14
segment test, 2–12
tag shorts test, 2–14
tag test, 2–13
valid bit test, 2–13

L
LANCE tests, 2–10
LED codes
interpreting, 1–12
LED definitions, D–1
Lower drive mounting panel
device combination options, 3–8
removal of, 3–8

Miscellaneous tests (Cont.)
translation lookaside buffer test,
2–10
write buffer test, 2–8
Miscellaneous Tests
LANCE tests, 2–10
MMJ port 3
connecting a terminal, 2–1
Mode
manufacturing, 2–4
user, 2–4
Module/frame assembly
removal of, 3–10
MS44 memory module
removal of, 3–21

N
Nonoperating conditions
system specifications, B–3

Memory
expansion, 1–1
indication of size, 1–7
size, 1–1
size indication, 1–7
type, 1–1
Memory tests, 2–14 to 2–16
address test, 2–15
data test, 2–15
memory data shorts test, 2–16
moving inversions test, 2–16
size and bitmap test, 2–14
Menu
console, 1–16
scsi, A–12
Miscellaneous tests
DZ test, 2–8
EEPROM test, 2–10
exception tests, 2–7
Floating point unit test, 2–8
Real time clock test, 2–8
SCSI tests, 2–9

Operating conditions
system specifications, B–2
Operating system
booting, 1–18
See boot command, 1–18
shutdown commands, 1–5
shutting down, 1–5
Operator privileges, 1–14
Options
system specific, 3–25

P
passwd command, A–8
Power supply
removal of, 3–24
troubleshooting, 2–16
Power-up self-test
defined, 1–6
errors, 1–10
interpreting results, 1–9, 1–10
running, 1–9
successful display, 1–7

Index–3

Power-up self-test (Cont.)
test 0, 1–9
unsuccessful display, 1–8
printenv command, A–9
Printer/console port
connecting a terminal, 2–1

R
Real time clock test, 2–8
Recommended Spares List, C–1
Reduced instruction set computer. See
RISC
RISC
defined, 1–1
RX23 diskette drive
hardware specifications, B–5
removal of, 3–17
RX23 diskette drive mounting bracket
removal of, 3–18
RX23 SCSI ID switches
location of, 3–19
setting, 3–19
RX23 select switch
location of, 3–20
setting, 3–20
RZ23 disk drive
drive interconnect cable, 3–11
hardware specifications, B–4
removal, 3–10
troubleshooting, 3–10
RZ23 SCSI ID jumpers
location of, 3–12
settings, 3–12
RZ24 disk drive
drive interconnect cable, 3–11, 3–13
removal, 3–13
RZ24 hard disk drive
hardware specifications, B–4
RZ24 SCSI ID jumpers
location of, 3–13
settings, 3–13

S
scsi command, A–12
SCSI tests, 2–9
Security
for system, 1–14
Security switch
location of, 3–24
setting, 3–24
use with passwd command, A–8
Self-test diagnostics
power-up, 1–12
Serial ports test, 2–8
setenv command, A–12
Spares list, C–1
Status LED display
described, 1–12
interpreting codes, 1–12
monitoring, 1–12
Storage Conditions
system unit, B–2
Storage devices
external, 1–2
internal, 1–2
System, turning on, 1–6
System configuration
display of, A–2
System module
function of, 1–1
removal of, 3–22
System on/off switch
location, 1–6
System specifications
nonoperating conditions, B–3
operating conditions, B–2
System unit
dimensions, B–2
hardware specifications, B–1
storage conditions, B–2
System Unit Cover
removal of, 3–3

T
Tape drive

Index–4

Tape drive (Cont.)
types of, 1–2
Terminators
for test modes, 2–4
Test 0
running power-up self-test, 1–9
test command, A–13
Test commands
viewing menu, 2–2
Test errors, 2–5
Test menu
viewing, 2–2
Test modes
selecting, 2–4
Test results
interpreting, 1–9
Translation lookaside buffer test, 2–10
Troubleshooting
fans, 1–5
power supply, 2–16
using power-up self-test results, 1–10
using status LED display, 1–12
using ULTRIX utilities, 2–1
visual checks, 1–3
TZ30 SCSI ID switches
location of, 3–15
setting, 3–15
TZ30 tape drive
hardware specifications, B–3
removal of, 3–15
TZK10 SCSI ID switches
location of, 3–16
setting, 3–16
TZK10 tape drive
hardware specifications, B–3
removal of, 3–16

V
Visual checks
performing, 1–3

W
Write buffer test, 2–8

U
ULTRIX troubleshooting utilities
netstat, 2–1
uerf, 2–1
unsetenv command, A–13
Upper drive mounting panel
removal of, 3–3

Index–5