Digital PDFs

EK-A0372-MG-B01

March 1992

328 pages

Original

16MB

view download

OCR Version

12MB

view download

Document:	MicroVAX 3100, VAXserver 3100, InfoServer 100 and InfoServer 150/150 VXT Maintenance Guide
Order Number:	EK-A0372-MG
Revision:	B01
Pages:	328
Original Filename:

OCR Text

MicroVAX 3100, VAXserver 3100,
o
infoServer 100 and infoServer 150/150 VXT

Maintenance Guide
EK-A0372-MG. BO1

Revision/Update Information:

March 1992

This manual describes how to troublesheot,

adjust, and repair MicroVAX 3100, VAXserver
3100, and infoServer 100 systems to Field
Replaceable Unit level.
Revision/Update Information:

Thisis a

revised

document.

Digital Equipment Corporation

Maynard, Massachusetts

March 1992

The information in this document is subject to change without notice and should not
be construed as a commitment by Digital Equipment Corporation. Digital Equipment
Corporation assumes no responsibility for any errors that may appear in this document.
The software 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 sofiware on equipment that is not
supplied by Digital Equipment Corporation or its affiliated companies.
Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and
Computer Software clause at DFARS 262.227-7013.
Copyright ©®

Digital Equipment Corporation

March 1992

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

DIBOL
EduSystem
1AS
MASSBUS

DECwriter

RSX

DECsystem-10
DECSYSTEM-20
DECUS

PDP
PDT
RSTS

UNIBUS
VAX
VAXcluster
VMS
vT

FCC NOTICE: The equipment described in this manual generates, uses, and may emit
radio frequency energy. The equipment has been type tested and found to comply with
the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC
Rules, which are designed to provide reasonable protection against such radio frequency
interference when operated in a commercial environment. Operation of this equipment in
a residential area may cause interference; in which case, the user at his own expense may

be required to take measures to correct the interference.
The following are trademarks of Digital Equipment Corporation: CompacTape, DEC,
MicroVAX, ULTRIX, VAX, VAXserver, and the DIGITAL logo.
MS-DOS is a registered trademark of Microsoft Corporation.
NFS is a trademark of Sun Microsystems, Inc.

Personal Computer AT is a trademsark of International Busincss Machines Carporation.

PostScript is a registered trademark of Adobe Systems, Inc.
UNIX is a registered trademark of American Telephone and Telsgraph Company.
X Window System is a trademark oi the Massachusetts Institute of Technology.

This document was prepared using VAX DOCUMENT, Version 2.0.

Contents

About This Manual
1

xix

Testing

1.1

UsingConsoleMode.

. ................
... .. ... ...

1-1

1.1.1

Determining the Console Device . ... ...............

1-2

1.12

EnteringConsole Mode ...........................

1-3

1.1.3

Exiting Console Mode

... .........................

1-4

RunningPower-UpTests .................
... .......

1-5

121

CPUNameand ROMVersion ......................

1-5

1.2.2

Power-Up Test Sequence . ...........
... .. .........

1-6

1.2.3

Power-UpSummary............
... ... . ... ......

1-6

1.24

Checking the System Devices.

. . ... .................

1-7

1.2.5

Power-UpTestCodes . ..................
.. .. ....

1-7

RunningSelf‘Test.............
... ... ... .. .. .....

1-10

1.3.1

Seif-Test DiagnosticCommands . . . . .................

1-10

1.3.2

Self-Test with Loopback Connectors . . ............
....

1-11

133

SelfTestCodes................
...
...

1-13

Running System Exerciser Diagnostics .................

i-14

1.4.1

System Exerciser Diagnostic Commands ..............

1-16

142

System Exerciser Codes . .. ........................

1--17

1.43

Extended Summary Reporting . .. .. ... ...............

1-20

1.3

1.4

Troubleshooting

2.1

Troubleshooting Procedures . . ........................

2-1

NoScreenDisplay ..........
... .. ...

2-2

2.2.1

Troubleshooting Procedure for No Sereen Display .. ...
..

2-4

222

Additicnal Information on Nonoperating Systems . . . .. ..

2-5

2.3
2.3.1
24
2.4.1

TESTE — CLK — Time-of-YearClock
Additional CLK Information

.................

2-5

... ....................

2-5

TESTD — NVR — Nonvolatile RAM

..................

2-5

Additional NVR Information . ......................

2-6

iv.

Contents

TESTC — DZ — Serial Line Controller . ...............
25
Additional DZ Information.........................
2.5.1
... ...
TESTB—MEM-—Memory ...............
26

2.6.1
2.7
28
29
210

2-6
2-7
2-8

Additional MEM Information....................... 2-10
TEST A — MM — Memory Managemeax:............... 2-12
TEST9 -—FP —FloatingPoint ...................... 2-13
2-13
2-13

2.11

TEST8 —IT —Interval Timer ......................
TESTT7—SCSI-ABus ..........coiiiiiiiinnnennn.
TEST6 —~SCSI-B—SCSI-BBus ....................

2.12

General SCSI Bus Troubleshooting .. ..................

2-14

2121

Self-Test . .......

2.12.1.1
2.12.2

e e

2-15

Self-Test Codes Explained .......................

2-15

System Exerciser

2-14

........ ... ... ... i,

2-16

2.12.2.1

System Exerciser Codes Explained ................

2-17

2.12.3

Additional SCSI Bus Information ................
...

2-18

2,124

SCSI Bus Address ID Settings . . ................

2-21

2.124.1

Setting the SCSIIDontheTZ30............. .....

2-21

2.1242

Settingthe SCSI IDontheRZ23..................

2-22

2.1243

Setting the SCSIIDforthe RX23 .................

2-24

2.12.4.4

Settingthe SCSIIDonthe RRD40 .. ..............

2-25

2.1245

Settingthe SCSIIDontheRZ55..................

2-28

2.124.6

Setting the SCSI ID on the TK50Z-GA .............

2-29

2.13

Troubleshooting a Tape Drive (TEST6or7) .............

2-31

2.14

Troubleshooting an RZ23 Disk Drive (TEST6o0r7)........

231

2.15

Troubleshooting an RX23 Diskette Drive . . .........
....

2-32

2.17

(TEST 6) ..ottt
e et
e e e e e 2-33
TEST 5 — SYS — Interrupt Controller and Ethernet ID
ROM ..
e
e 2-34

2.16 Troubleshooting an RRD40 or an RRD42 Compact Disc Drive
2.17.1

Additional SYS Information .. ......................

2-34

2.18

TEST 4 — DSH32-B Asynchronous Subsystem (DSH32-A) ..

2-34

2.18.1

Additional DSH32-A Information

2.18.1.1

Self-Test Codes Explained .......................

2.18.1.2

System Exerciser Codes Explained

2.19

TEST 3 — DSH32-B Synchronous Subsystem (DSH32-S) ...

2-35

2-39

‘

Contents

2.19.1

Additional DSH32-S Information . . . .................

2-39

2.19.1.1

Self-Test Codes Explained .......................

2-40

2.19.12

System Exerciser Codes Explained

................

2-40

General DSH32-B Communications Module Troubleshooting.

2-42

2201

SelfTestErrors ...............
... ...,

2-42

2.20.2

System Exerciser Errors ..........................

243

2.20.2.1

DSH32-A System Exerciser . .....................

2-43

2.20.22

DSH32-S System Exerciser . .....................

2-43

2.20

221

...................

2-44

2.21.1

Additional NI Information .........................

2-45

2.22

Power Supply Troubleshooting Procedures. ..............

246

TEST 1 — NI —Ethernet Network

Utilities

3.1

Configuration Tablc (T50) . ........... ...,

3-2

3.1.1

DZ Explanation in ConfigurationTable ...............

3.1.2

MEM Explanation in Configuration Table . ............

3-5

3.1.3

SCSI Bus Explanation (SCSI-A and SCSI-B) in the
ConfigurationTable ............. .................

3-7

3.13.1

. ..................

3-8

DSH32-A Explanation in the Configuration Table . . . . . ..

3-9

3.2

Setting NVR Default Boot Device (T 51) ................

3-11

3.3

Setting NVR Default Boot Flags (T 62) .................

3-12

3.4

Setting the 'VR Default Recovery Action Flags (T 53) ... ..

3-16

3.5

Tape Cartridge Special Diagnostic Key for Field Service
System Exerciser (T'73) . .. .. ... ... ... .. .. .
..

3-18

Exerciser (T74) ...

Diskette Special Diagnostic Key for Field Service System
... .
... ... ... ... ... ... ...

3-19

SCSI Mass Storage Disk Data Eraser (T 75) .............

3-20

3.71

SCSI Disk Eraser Messages . . . . . ..................

3-21

3.8

Mass Storage Diskeite Formatter (T 76) . ..............,

3-22

3.14

3.6
3.7

3.8.1

3.9
3.10
3.11

SCSI Address ID Assignments.

Diskette Formatter Messages.

... ...................

3--23

Determining SCSI Address IDs for Drives in the System
(SHOWDEVICE) . . . ....... ... ... . i

3-24

Extended Summaries for the System Exerciser (SHOW
ESTAT) . ...
. ...

3-25

Determining the Revisien Levels in the System Module’s

ROM@SHOWVER) ... ... .. ... ... ... .. ... ... .....

3-27

Contents

The Mode! 10 System

Enclosure Description ...... ..... ... ... ... ... . ...
4.1
FRU Removal and Replacement. .. ... .................
4.2
System Box Cover Removal .. ......................
421
Drive Mounting Panel Removal . . ... ................
422

...
Disiribution Boara Kemovai.....................
423
RZ23DiskDriveRemoval .........................
424
TZ30TapeDrive Removal .........................
425
RX23 Diskette Drive and FDI Board Removal . .. .. ....
426
DSH32-B Communications Module Removal .. ... ... ..
427
...
Memory Module Removal . . ...................
428
...
System Module Removal ......................
429
4.2.10 BatteryPack Removal ............................
... ... ...
...
... .......
PowerSupply Removal ....
4211
e
Options . ...t
43
Internal Memory Options..........................
4.3.1
DSH32-B Communications Module Options . . .. .. .. ....
432
Optional Storage Device Positioning . ................
4.3.3
Changing the Maximum Baud Rate of the MMJ Ports and
4.4

the Modem Port . ........ ... ... i

The Model 20 System

4-1
4-3
44
4-5
4-7
49
4-12
4-13
4-16
4-17
4-19
4-21
4-22
4-23
4-23
4-23
4-23
4-24

... ........ ..
Enclosure Description . ................
FRU Removal and Replacement. ... ...................

5-1

System Box Cover Removal ..........
... ..........
Upper Drive Mounting Panel Removal ...............

5-5
5-6

Lower Drive Mounting Panel Removal. ...............

5-8

525

Distribution Board Removal . . . .. ...................
RZ23 Disk Drive Removal .........................

5-11
5-13

526

TZ30TapeDrive Removal .........................

5-16

527

5.28

RX23 Diskette Drive and FDI Board Removal .........
DSH32-B Communications Module Removal ...........

5-17
5-21

529

Memory Module Removal . . . ... ....................

5-21

5.2.10

System Module Removal ..........................

5-23

5.2.11

BatteryPack Removal .....................
... ...

5-25

5.2.12

Power Supply Removal

5.1

5.2
5.2.1
5.2.2
523
5.24

5-3

Contants

vii

Internal MemoryOptions. . ........
... ... ...,

5-28

5.4

DSH32-B Communications Module Option . .............

5-28

5.5

Changing the Maximum Baud Rate of the MMJ Ports and
the Modem Port ... ...........
... ... ... ...
...

5-28

Expansion Boxes

6.1

RZ55ExpansionBox ...............
... .. .. ... ......

6-1

6.1.1

Troubleshooting the RZ55 Disk Drive Expansion Box ....

6-4

6.1.2

RZ55 Expansion Box FRU Locations . ................

6-6

6.1.3

RZ55 Expansion Box FRU Removal and Replacement . ...

6-8

6.1.3.1

RZ55 Disk Drive Reinoval from Expansion Box . ......

6-7

6.1.3.2

RZ55 Expansion Box SCSI ID Switchboard

.........

6-15

6.1.3.3

RZ55 Expansion Box Power Supply Removal

........

6-17

6.1.3.4

Resistor Load Board Removal .. ..................

6-18

6.2

..................

6-19

6.2.1

RRD40 Compact Disc Expansion Box Troubleshooting. ...

6-20

6.22

RRD40 Expansion Box Removal and Replacement

......

6-22

TK50Z ExpansionBox ..............................

6-23

Troubleshooting the TK50Z Expansion Box ............

6-24

Troubleshooting Inside the TK50Z Expansion Box . . . ..

6-26

6.3.2

TK50Z Expansion Box FRU Locations . ...............

6-28

6.3.3

TK50Z Expansion Box FRU Removal and Replacement

6-28

6.33.1

TZK50 Controller Board Removal .................

6-29

6.3.3.2

TK50 Tape Drive Removal . . ... ..................

6-31

6.3.3.3

Power Supply Removal

........

6-35

6.3.3.4

SCSI ID Switcnboard Removal . . ... ...............

6--37

6.3.3.5

Resistor Load Board Removal .. ..................

6-37

6.3

RRD40 Compact Disc Expansion Box

6.3.1

6.3.1.1

... .............

Operating Information

7.1

Booting the MicroVAX 3100 and VAXserver 3100 .........

7-1

TheTZ30TapeDrive ... ..... ... ... ... ... . ... ..

7.2.1

Tape Cartridges . . ....... ...

7.2.2

TZ30 Controls and Indicators.

... . ... ...

...

. . . ...................

7-5

vii

Contents

TZ300peration ............cciiiiiiiiiiinnans
723
Inserting and Using the Tape Cartridge ............
7.23.1
7232
Removing a Tape Cartridge from the Drive ..........
..
..
.. ........
RX23 DisketteDrive .....
724
.. .o e
Diskettes .. ...
7.24.1
7.24.2
InsertingaDiskette . ...............
... ...
Removinga Diskette ...........................
7.24.3
7.3
The RRD40 Compact DiscDrive ......................
7.3.1
Front Panel of the RRD40 Exparsionbox .............
732
LoadingaDise............
..
i,
.
... . it
UnloadingaDisc ..............
733

7-7
7-8
7-10
7-11
7-12
7-13
7-14
7-15
7-15
7-15
7-16

734

Disc and Caddy Repair .......... e

7-18

7.3.5
736
737

Removing the Disc fromtheCaddy ..................
CleaningaDisc ..........
... ..o,
Replacingthe DiscintheCaddy ....................

7-19
7-20
7-20

7.4

TK50Z Tape ExpansionBox . .........................

7-21

74.1

InsertingaTapeCartridge. ........................

7-21

7.42

Summary of TK50Z Controls and Indicator Lights ... ...

7-23

743

RemovingaTapeCartridge ........................

7-24

InfoServer 100

8.1

8.1.1

Enclosure Description ... ...... ... ... . ..

...

8-1

InfoServer 100 System Box Back Panel . ..............

RRD40or RRD42CDDrives

........
... .............

8-5

8.3

FRU Removal and Replacement. ... ... ................

8-8

8.3.1

System Box Cover Removal .. . .....................

8-9

8.3.2

Upper Drive Mounting Panel Removal ...........
....

8-10

833

Removing the RRD40 Controller(s) (if present) .........

8-ii

8.34

Lower Drive Mounting Panel and CD Drive Removal ....

8-13

83.5

Remove the CD Drives from the Lower Drive Mounting
Panel .. ..
e

8-14

836

RRD42CDDriveRemoval .........................

§8-16

837

RZ23 Disk DriveRemoval .. .......................

8-16

838

System Module Removal ..........................

8-16

839

BatteryPackRemoval ......................
... ...

8-16

8.2.10

Power Supply Removal ...........................

8-16

Contents

Console Test Commands

Console Commands

B.1

Console CommandSyntax .......... .................

B-1

ConsoleCommands .............c..................

B-2

B21

BOOT........

B22

COMMENT ........ ... ... i

B-3

B23

CONTINUE.......... ...,

B-3

B25

DTE.....

B-5

B24

... ..

DEPOSIT........

B-2

... .. ... B-3

... ... .

B26

EXAMINE ...... ... ... ... ... . . .. .,

B-5

B27

FIND ...

B-6

B28

HALT.......

B29

HELP..

B.2.10

INITIALIZE.....

... ... .. ... .. . . . . .

B-7

B.2.11

REPEAT........

...

.. . i,

B-7

B213

SHOW ........ ... i

B-9

B.214

START .......... .. .

B-11

B215

TEST ... .. . .

B-11

B216

UNJAM ......... ...

B-11

B.217

Transfer XFER)...
... ......
....
... ......
. ......

B-12

... ..
... ...

B-6

. .

B-6

B212 SET ...... . B-7

SpecialKeys..........

...

.. ... .. .. .

Console Messages and Explanations

VMB Boot Error Status Codes

Power-Up and Self-Test Error Codes

. .,

B-13

E.1

Time-Of-Year Clock (CLK)

..........................

E-2

Nonvolatile RAM(NVR).............................

E-3

E.3

Serial Line Controller (DZ) ..........................

E-3

SystemMemory (MEM).............................

E-56

E.5

Memory Management MM)...............

E-6

..........

Contents

E.6

Floating Point (FP) . ...............
(. ... .. ...

E-6

E.7

Interval timer (IT) . ... ... ... .. ... ..

...

E-6

E.8

SCSI Bus Controller (SCSI-A and SCSI-B) ..............

E-7

E.9

Interrupt Controller and Ethernet ID ROM (SYS).........

E-14

E.10

DSH32-B Communications Module Asynchronous Subsystem

E.1ll
E.12

(DSH32-A) . ..ottt
e e
e E-15
DSH32-B Communications Madule Synchronous Lines

(DSHB2-8) ..ottt ittt

it e e E-17

Ethernet Circuits (NI) . ..........
.. .. ... ... ... ...... E-18

System Exerciser Error Codes

F.1

Serial Line Controller(DZ) ........ ..................

F-1

SystemMemory(MEM).............................

F-5

F.3

SCSI Bus Controller (SCSI-Aand SCSI-B) ..............

F-6

F.4

DSH32-B Asynchronous Subsystem (DSH32-A)...........

F-10

F.5

DSH32-B Synchronous Subsystem (DSH32-S) ............

F-13

EthernetNetwork (ND)..............................

F-18

Diagnostic LED Definitions

G.1

Additional LED Information .........................

Recommended Spares List

index

Figures
1-1

PortsandConnectors . .................
... 0vrunn..

1-3

1-2

Exarple of Power-Up Test and Power-Up Summary .. ... ..

1-6

1-3

Configuration Table (T 50)...........................

1-9

1-4

Example of Running Self-Test on an SCSI Bus ...........

1-11

1-5

Running the System Exerciser on Individual Devices . ... ..

1-15

1-6

System Exerciser Display Example ....................

1-18

1-7

Example of SCSI Extended Summary Report ............

1-21

2-1

Normal System Power-Up Flowchart . . .................

2-3

Contents

Running the System Exerciser on the Serial Line Controller
(D) .
e e

2-6

2-3

Example of the DZ Line in the Configuration Table........

2-7

Configuration Display MEM Information................

2-10

Configuration Display MEM Error Code Example 1

.. ... ..

2-11

2-6

Configuration Display MEM Error Code Example 2 ... .. ..

2-12

2-7

Self-Test Example on the SCSI-B Device ................

2-15

2-8

System Exerciser Example for SCSI-B Device ............

2-18

2-9

Example of the SHOW DEVICE Command ..............

2-20

2-10

TZ30 SCSI ID Switch Locations . . ... ..................

2-21

2-11

RZ23 SCSI ID Jumper Locations . . . ...................

2-23

2-12

FDI Board SCSI ID Switch Positions . . . ................

2-24

2-13

RX23 Select Switch Setting . .. .......................

2-25

2-14

RRD40 SCSI ID Switch Locations . . ...................

2-26

2-15

RZ55 Expansion Box SCSI ID Switch Locations ..........

2-28

2-16

TKS502Z-GA SCSI ID Switch Locations

2-30

2-17

Running the System Exerciser on the DSH32-A Subsystem

2-18

Configuration Display DSH32-A Information.

2-19

Configuration Display DSH32-A Error Code Example 2

....

2-36

2-20

Error Code Format for the DSH32-A Subsystem ..........

2-37

2-21

Running the System Exerciser on the DSH32-A Subsystem .

2-37

2-22

System Exerciser DSH32-A Information ................

2-38

2-23

System Exerciser DEH32-A Error Code Example. .. ... ....

2-38

2-24

Running the System Exerciser on the DSH32-S Subsystem. .

2-39

2-25

Configuration Display DSH32-S Information . . ... ... ... ..

240

2-26

Running the System Exerciser on the DSH32-S Subsystem..

2-40

2-27

System Exerciser DSH32-S Information

2-28

System Exerciser DSH32-S Example 1

2-29

System Exerciser DSH32-S Example 2

2-30

System Exerciser DSH32-S Status Code and Error Code
Example. . ... ... ... . . .

2-42

2-31

Flowchart for Troubleshooting the Power Supply..........

2-46

2-32

Power Connector Pin Voltages on the System Module . . . . ..

2-47

2-33

Drive Power Connector Pin Voltages. . . .................

248

3-1

Example of the Configuration Table

...................

3-3

3-2

Example of the DZ Line in the Configuration Table...
.. ...

2-2

. .................
.

2-35

. ...........

2-36

.................

241

Contents

3-6

Configuration Display MEM Error Code Example 1 .......

3-6

Configuration Display MEM Error Code Example 2 . ... ...

3-7

SCSI Bus Lines in the Configuration Table . . ............

3-8

Configuration Display DSH32-A Information. . . ..........

3-9

Error Code Format for the DSH32-A Subsystem ..........

3-10

Configuration Display DSH32-A Error Code Example 2 ....

3-10

3-10 Example of Changing the Default Boot Device............

3-11

Example of Changing the Default Boot Flag . ...... e

3-12

Determining the NVR Code for Three Boot Flags ... ......

3-13

Example of Changing the NVR Recovery Action Flags .. ...

3-17

3-14

Example of Creating the Special Key on a Tape Cartridge ..

3-18

3-15

Example of Creating the Special Key on a Diskette........

3-19

3-16

Example of Erasing DataonanRZ55 ..................

3-20

3-17

Example of an Error While Erasingan RZ55

............

3-20

3-18

Example of Formatting an RX23 Diskette ... ............

3-22

3-19

Example of the SHOW DEVICE Command ..............

3-24

3-20

Example of SCSI-B Extended Summary Report

..........

3-26

3-21

Example of the System Module’s ROM Code Revision Levels

3-27

TheSystem Box ... ...... ... ... .. .. i

4-2

FRU Locations . .. ......... ...

.. ...,

Cover Screw Locations . . ............
... ... ..........

4-5

Storage Device Positioning and Cabling. . ... ............

4-6

Unscrewing the Drive Mounting Panel ... ..............

4-7

Removing the Distribution Board. . . . ... ... ... .......

4-8

Distribution Board Connectors. . ... ...................

4-9

Removingthe HDA ..........
... ... ... .. ... .......

4-10

4-9

RZ23 SCSI ID Jumper Locations . . . ...................

4-11

¥
© LLEELL

Configuration Display MEM Information................

LLELILLE

xii

4-10 TZ30 Jumper Switch Location .........

..............

4-13

4-11

RX23 Mounting Bracket Screws. . . ....................

4-14

4-12

Removing the FDIBoard ... .......................

4~15

4-13

FDI Board SCSI Switch Locations . . . ...............

4-15

4-14

RX23 Select Switech Position

.........................

4-16

+~15

DSH32-B Communications Module Removal .. ......
...
.

4-17

4-16

Memory Module Removal . . ..........
... ...........

4-1

417

16Mb Merory Module

4-18

............
.. .. ... ... .. ....

Contents

xiii

4-18

System Module Screw Locations ................ ......

4-20

4-19

Location of Ethernet ID ROM on System Module .........

4-20

Battery Cable Location . ...........
... ...............

4-21

Power Supply Screw Locations

4-22

Location of Nodes on the System Module.

. . .............

4-25

AP
A (AR

... ....................

Model 20 System Box

..........
... .. ... ... .. .. ...

5-2

FRU Locations . .. ......... ... oo,

Cover Screw Locations . . . ...... ... ... ... ... .. .. ...

5-5

Drive Mounting Panel Power and Signal Cabling .........

5-7

Unscrewing the Upper Drive Mounting Panel

...........

5-8

Distribution Board Cabling . ........
. ... ... ..........

5-10

Unscrewing the Lower Drive Mounting Panel

...........

5-11

Removing the Distribution Board. . ... .................

5-12

5-9

Distribution Board Connectors.

5-12

o—-10

Removingthe HDA ... ... .. ...

.. ... ... .........

5-14

511

RZ23 SCSI ID Jumper Locations .. .. ..................

5-15

5-12

TZ30 Jumper Switch Location .. .. ....................

5-17

5-13

RX23 Mounting Bracket Screws. .. ....................

5-18

o-~14

Removingthe FDIBoard ... ..... ... ..

... ... .......

5-19

5-15

FDI Board SCSI Switch Locations . . . ..................

5-19

5-16

RX23 Select Switch Position

.........................

5-20

5-17

DSH32-B Communications Module Removal .. . ......
...

5-21

5-18

Memory Module Removal . . ... ........
... ............

5-22

5-19

16Mb Memory Module

.. ...... ... ... ... ... .. ... . ...

5-23

5-20

System Module Screw Locations ... ...... .............

5-24

5-21

Location of Ethernet ID ROM on System Module ... ... . ..

5-25

5-22

Battery Cable Location ...........
... ... .. .........

5-26

5-23

Power Supply Screw Locations

5-27

5-24

Location of Nodes on the System Module.

.....

5-29

6-1

RZ55 Expansion Box . .......................
......

6-2

RZ55 Expansion Box Connection ... ...... .............

6-3

6-2

Two Daisy Chained RZ55 Expansion Boxes . . ......
... ...

6-3

RZ55 Expansion Box FRU Locations

. .................

RZ55 Expansion Box Cover Screws .. ... ... ..........
..

6-8

RZ55 Expansion Box Shield Serews . . ... ...

6-9

6-7

. ... ..................

... ....................

... ......

RZ55 Expansion Box Drive Mounting Screws

... .. ... ...

xiv

Contents

6-8

RZ55 Expansion Box Drive Cables

6~9

RZ55 Mounting Bracket Screws

6-10 RZ55 Bezel Removal

6-11

....................

......................

. ...... ... ...... ..

Drive Module Removal . . . ...

... ... ... ...

... ... ... ... ..........

6-12 RZ55 Expansion Box SCSI ID Switchboard . . . ... .. .. .. ..
6-13

RZ55 Expansion Box SCSI 1D Switch Setting

............

6-14 RZ55 Expansion Box Power Supply Screws
6-15

RZ55 Expansion Box Resistor Load Board

6-16 RRD40 Compact Disc Expansion Box. . ... .....
6-17

........

RRD49 Expansion Box SCSI Address ID Setting

6-18 TK50Z ExpansionBox ...........
... ... ... ............
6-19 TKB5B0Z Expansnn Box Connection . . .. .................
6-20 TK50Z-CA SCSI Address ID Switch Settings

............

6-21

TK5H0Z Expansion Box FRU Locations

6-22

TK5H0Z Expansion Box Cover Screws

6-23

TZK50 Ccntroller Board Cables

6-24

TKbH0Z Expansion Box Shield Serews

6-25

TK50Z Expansion Box Drive Mounting Screws

6-26

Tape DriveCables . .............
... ..

6-27

TK50 Mounting Brackets Screws

6-28

TK50Z Expansion Box Power Supply Sc:ews

... ... ...

6-29

TK50Z Expansion Box Resistor Load Board Power Cables

. .

7-1

Example of the SHOW DEVICE Command .. ... .. . ... ..

7-2

Accessing the TZ30 Tape Drive ...
. .
..

7-3

TZ30 Tape Drive (Front View)

7-4

TK50 Tape Cartridge Door.

7-5

TZ30 Take-Up Leader Adjustment

Insertinga Tape Cartridge.

7-7

Removing a Tape Cartridge . ..... . ... ..

7-8

Accessing the R¥X23 Diskette Drive

7-9

Inserting a Diskette

7-10

Removing a Diskette . ... . ...

7-11

RRD40 Compact Disc Expansion Box

7-12

RRD40 Compact Disc Loading

7-13

DiscParts

7-14

Separating the Disc from the Caddy

...

.................

.. ...

... ... .........

.. ........ ...... ..

... ........
... ........

. . ...
. ..
... ... ....

.. ...

.. ...... ... .. .

.. ........

... ... .. .. .. .. ..

... ... ... ...

Contents

7-15

RemovingtheDisc ... ....... ...

... ...

.. ...

.. ....

7-20

7-16 Inserting and Loading a Tape in the TK50Z Expansion Box .

7-22

7-17 Unloading and Removing the TK50 Tape . . . .............

7--24

8-1

InfoServer 100 Front Panel ....... ... ...

.. ..........

8-2

InfuServer 100 Back Panel...........................

8-3

Power and Signal Cabling for -AX Models

8-6

Power and Signal Cabling for -BX and -CX Models

.......

8-7

CoverScrewlocations..............................

8-6

Unscrewing the Upper Drive Mounting Panel . . ... ... .. ..

8-10

8-7

Removing the RRD40 Controller Module(s) ..............

8-12

8-8

Removing the Lower Drive Mounting Panel

8 i4

8-9

Removing CD Drive from the Lower Drive Mounting Panel

D-1

VMBErrorDisplays

G-1

LEDULayout......

..............

..........
...
.

8-15

.....

D-1

... ... ... ... ... . . . .

....... ...

... .. ... ... ...

Tables
I-1

Prompts .. ...

1-2

Power-Up Symbols Defined ........ ..................

1-6

1-3

Power-Up and Self-Test Commands . . ..................

1-8

Self-TestCommands. ...............................

1-13

1-5

System Exerciser Test Modes . . .. .....................

1-14

1-6

System Exerciser Diagnostic Commands .. ...... e

1--15

2-1

Troubleshooting Procedures ... .......................

2-2

DZPortAssignments . . ................. ...,

2-8

2-3

MEM System Exerciser ErrorCodes .. .................

2-9

2-4

Hexadecima: Memory Codes .........................

2-10

2-5

Locating a Failed Memory Bank ......................

2-11

2-6

Self-Test Commands on the SCSIBuses ................

2-15

2-7

SCSI Devices Self-Test StatusCodes .. .................

2-16

2-8

SCSI Bus Address ID Assignments (both buses) ..........

2-19

2-9

TZ30 SCSI ID Switch Settings.

... ....................

2-22

2-10

RZ23 SCSI ID dumper Combinations . . . ... .............

2-23

2-11

RX23 SCSI ID Switch Settings

.....................
..

2-24

2-12

RRD40 SCSI ID Switch Settings .. ... ................

2-27

2-13

RZ55 SCSI ID Switch Settings . . .. ....................

2-29

2-14

TK50Z-GA SCSI ID Switch Settings ... ................

2-30

Contents

2-15

Ethernet Port Loopback Connectors. .. ... .............

2-45

2-16

System Module Power Connector Voltages . .. ............

241

2-17

Drive Power Connector Voltages . .....................

248

3-1

Utilities . .......... ... ...

3-1

LLELLLE

xvi

Hexadecimal Memory Codes . ........................

3-5

Locating a Failed Memory Bank ......................

3-6

MicroVAX 3100 Family SCSI Bus ID Assignments ... ... ..

3-9

Boot Device Names ................................

3-12

Boot Flags Usedby ULTRIX .........................

3-13

Boot Flags Usedby VMS . . ..........................

3-15

Default Recovery Flags ..........
... ...........
..

3-17

3-9

SCSI Data Eraser Messages .......
.. e

3-21

3-10 T 75 Error Codes for the SCSI Data Eraser

.............

3-11

Diskette Formatter Messages. . . . ... ..... ...

3-12

T 76 Error Codes for the Diskette Formatter.

4-1

... ..... .

3-23

. ... .. . . .. ..

3-23

FRU Section Listings . . .. ...........................

Model 10 Internal Storags Device Combinations .. ... ... ..

4-24

Jumper Settings for Serial Port Baud Rates .. ...........

4-24

FRU Section Listings . . ..............
... ..........
..

5-3

Lower Drive Mounting Panel Device Ccmbinations . . . . .. ..

5-8

Jumper Settings for Serial Por{ Baud Rates .. ......
...
.

5-29

Expansion Box Section Listing

. ......................

6-1

RZ55 Expeansion Box FRU Section Listings .. .. ..........

6-7

TK50Z Expansion Box FRU Section Listings

6-28

TZ30Controls ......... ... ... ...

3-21

............

. ... ... ...

... ...

7-5

TZ30Indicators . ............
... ...
......
... .. ....

7-6

Function of TK50Z Physical Controls.

. ..............
...

7-23

Functior of TK50Z Indicator Lights . . .. ................

7-23

InfoServer 100 Model Variations .. ....................

8-3

InfoServer 100 FRU Section Listing. . ......... .........

8-8

Diagnostic Test Commands ..........................

A-1

Utility Commands . ...
...
...
... .........
...
... ...

A-2

System Device Names . ........................
.....

B-2

INITTALIZE Command Register Values . . .. .............

B-7

Special Keys Used in Console Program Mode ............

B-13

Console Error Messages . . . .

Contents

-1

VMB Boot Error Status Codes . . . .............

E-1

Failing Test/Device Section References

E-2

xvii

.......

D-2

.................

E-1

Time-Of Year Clock (0000.XXXX) .....................

E-2

Nonvolatile RAM Error Ccaes (0000.XXXX). . ............

E-3

Sernial Line Controiler (0000.XXXX) . . .......
... ... ...

E-3

Serial Line Status Codes (0000WWWW) . ... ............

E-5

aystem Memory Error Codes (0000.XXXX) ..............

E-5

Memory Management Error Codes (0000.000X)...........

E-6

Floating Point Error Codes (0000.000X).................

E-6

Binary Mask of Selected Devices (WWXX.0000). . .........

E-17

E~-10 Binary Mask of Error Flags (0000.YY00) ................

E-8

E-11 SCSI Bus Controller’s Error Codes (0000.002Z) .. .........

E-8

E-12 Device Status Codes (DDMMSSTT) .. ..................

E-11

E-13 Interrupt Controller/Ethernet ID ROM Error Codes

(0000, XXX X ). .ot
e e

E-14

E-14 DSH32-A Error Codes (0000.YYYZ) . . ......
... ... .....

E-15

E-15 DSH32-A Field Service Mode Error Codes (0000.YYYZ) ....

E-16

E-16 DSH32-S Error Codes (XXXX.YYYO) .......
.. .........

E-17

E-17 Ethernet Circuits Error Codes (0000.YYYY) .............

E-18

... ...............

F-1

Status Code Format Significance ... ...................

F-2

F-3

Serial Line Assignments (0000.ABCD). .. ...............

F-2

Serial Line Console Codes (0L00.0000) .................

F-3

F-5

Each Serial Line's Status/Error Codes (0000.ABCD) . ..
.. ..

F-3

F-6

Fatal Device’s Error Codes (00FFABCD)................

F-7

System Memory Error Codes (XXXX.00YZ) ..............

F-5

F-8

Bus Controller Code Format Significance. .. .............

F-6

F-9

Drive Code Format Significance.

.. ...................
.

F-7

F-10 SCSI Bus Controller Error Codes (0U00.XYZ1) (0000.00S1) .

F-7

r-ii Last Command on the SCSI Bus Codes (0000.P001) . ... ...

F-9

F-12 Drive Status Codes (0000.0ROL). .. ....................

F-9

F-13 Exerciser Error Codes for the DSH32-A Subsystem........

F-10

F-14 Exerciser Error Codes for DSH32-S Subsystem .. ... ......

F-13

F-15 Ethernet Test Numbers (000X.0000) ...................

F-19

F-16 Ethernet Error Codes (000X.22ZZ)

....................

F-19

Diagnostic LEDs Definitions .........................

G-1

F-1

G-1

Failing Test/Device Section References

xviii

Contents

H-1

MicroVAX 3100 and VAXserver 3106 FRUs ... ...........

H-i

H-2

InfoServer 100 FRUs . . .........
.. ... ... .. ....... ...

H-3

DSH32 Communications Subsystem FRUs ..............

H-4

H+4

RZ55-Fx Disk Expansion Box FRUs (BA40B-AA) . ... ... ..

H—4

H-5

TK50Z-Gx Tape Expansion Box FRUs (BA40B-AA) ... ... ..

H-5

H-6

SZ12x-xx Storage Expansion Box FRUs . ................

H-5

H-7

RRD40-Fx Compact Disk Expansion Box FRUs . ..........

H-6

H-8

Miscellaneous Parts . . .............................

H-6

About This Manual
This guide describes how to troubleshoot, adjust, and repair the MicroVAX
3100 and the VAXserver 3100 Model 10 and Model 20, and the InfoServer
100 to Field Replaceable Unit (FRU) level. It covers all FRU options
presently available for these systems. The nameplate on the front of the
system box indicates the type of system you are working on. The model
number is on the back of the system box.

Organization
This guide has eight chapters and eight appendixes.
Chapter 1 contains testing procedures: power-up test, self-test, anc
system exerciser tests.

Chapter 2 contains troubleshooting procedures to help isolate the
problem to an FRU.

Chapter 3 contains a description of the utilities.
Chapter 4 describes the Model 10 system: a system overview, FRU
removal and replacement, and description of options.
Chapter 5 describes the Model 20 system: a system overview, FRU
removal and replacement, and description of options.

Chapter 6 describes the expansion boxes available for use with the
system: an enclosure overview, troubleshooting information, and FRU
removal and replacement procedures.

Chapter 7 contains operating information: booting and removable
media drives operating information.
Chapter 8 describes the InfoServer 100 systam: a system overview
and FRU removal and replacement procedures.
Appendix A lists the test commands.
Appendix B lists the console commands and definitions.
Anpendiv C ligte the console massages and definitions.
Appendix D lists the VMB boot error status codes and VMB
definitions.

Appendix £ lists the power-up and self-test error codes.

Xix

About This Manual

Appendix F lists the system exerciser error codes.

Appendix G lists the definitions of the LEDs on the back of the system

Appendix H gives the recommended spares list (RSL).

box.

intended Audience
This document is for DIGITAL Field Service personnel and selfmaintenance customers only.

Conventions
This document uses the following conventions:
Convention

CAUTION
NOTE
PN

Meaning
Cautions provide information to prevent damage to

equipment or software. Kead these carefully.

Indicates important information you should be

aware of.

Indicates a part number.
Boxed text within examples and system displays
identifies a key that should be pressed on the
keyboard.

>>>

Bold

{x:y)

Indicates a console prompt.
Bold print identifies user input when used in
examples and system displays.
Represents a bit field, a set of lines, or gignals,

ranging from x through y. For example, RO (7:4)
indicates bits 7 through 4 in general purose
register RO.

SHOW QUEUE

Command names in text are shown in uppercase.

CTRL/C

For sequences that use the CTRL key, hold down
CTRL and press the second key.

PV_SCS_FMTing...

System displays used as examples are shown in
monospace type .

Testing
This chapter describes how to tcst the MicroVAX 3100, the VAXserver
3100, and the InfoServer 100 systems. Testing procedures for these
systems are similar and any differences between them are specifically
identified in the text. The nameplate on the front of the system box
indicates the type of system you are working on.

All testing is done while in console mode and diagnostic tests are ROM-

based.

This chapter contains the following sections:

1.1

Using console mode

Running power-up tests

Running self-tests

Running system exerciser diagnostics

Using Conscle Mode

The svstem has two modes of operation: program mode and console
mode. Program mode is when the operating system (for example, VMS
or ULTRIX) is controlling the system. Console mode allows the user to
control the system from the console terminal. Console mode is contained
in ROM on the systeiz: module.
See Appendix B for a description of the console commands.

1-1

1-2

Testing

Testing is done while in console mode. The system returns the console
prompt (>>>) when it is in cons..e mode. Table 1-1 lists the prompts and
the mode of operation each prompi represents.
Table 1-1

Prompts

Prompt

Mode of operation

(>>>)

Console mcde. See Appendix B for a list of console commands.
$

Program mode (VMS operating system).
Program mode (ULTRIX operating system).

1.1.1

Program mode (ULTRIX operating system, privilegec mode).

Determining the Console Device

The console device, a VTI'xxx terminal, is connecte¢ to MMJ port 1.
Figure 1-1 shows the ports and connectors at the rear »f the Model
20 system. The Model 10 system is identical except for the port marked
reserved. Figure 4-1 shows the front and rear panelis of the the Model 10
system.

A terminal (VTxxx series) can be connected to MMJ Port 3 and made to
operate as the console terminal by setting BREAK ENABLE correctly.
The switch on the back of the system box must be in the up position at
power-on if the terminal connected to MMdJ Port 3 is to be recognized as
the console. Otherwise, the console is the terminal connected to MMJ
Port 1.

The terminal must be set at 9600 baud, with 8 bits, #nd no parity.

A terminal attached to MMJ Port 3 with BREAK ENABLED allows you
to halt the CPU and go directly to console mode by pressing the BREAK
key on the keyboard.

Testing

Flgure 1~1

Ports and Connectors
Powar On/Oft Switch
Powaer Connector
——

SCSI-B Port

\
\

Raserved

Synchronous Port
Hait Button

8-Asynchronous Port
Neot Selact indicators

Standard Etherne' et

Ethernet Switch

ThinWire Etharngt Port ————
.

MMJ Port 1

\— Diagnostic LEDs
Break Enable Switch

Modem Port

MMJ Port 2

MMJ Port 3

WLO- 002950

1.1.2 Entering Console Mode
Console mode is entered any time the CPU halts. A halt means that
control has passed from the operating system software to the console mode
program in ROM. The CPU can be halted automatically or manually.
When halted automatically (boot failure, major system error, or after
power-up testing), the console mode program checks the nonvolatile RAM
for user-defined instructions (restart, boot, or halt). The system then
executes the instructions. The CPU is halted manually by pressing the
Halt button on the back of the system box and the system enters console
mode immediately. Figure 1-1 shows the position of the Halt button.
Have the system manager shut down the operating system software, then
press the halt button to enter console mode.

1~4

Testing

NOTE
Press the BREAK key on the keyboard to enter conscle mode if
you are using a terminal attached to MMJ Port 3 with BREAK
ENABLED.

1.1.3 Exiting Console Mode
To exit console mode, type one of the following console commands (See
Appendix B):

BOOT—This command initializes the CPU and boots the operating
system software from the device specified. If no device is specified, the
system uses the default device in NVR. If no device is listed in NVR,
the system defaults to the Ethernet (ESAQ) as the boot device.
The BOOT command starts the system but does not run power-up
tests. If the svstem attempts to boot over the Ethernet (ESA0) and no
response is received, make sure the node with the operating system
software is operating normally and the software is loaded. Press the
halt button if you need to abort the Ethernet boot.

CONTINUE—This command instructs the CPU to continue the
operating system software at the address contained in the program
counter (PC). This command starts up the operating software where it
was halted provided no console TEST commands were run. Running
a TEST command alters the PC register and memory so that the
operating system software cannot be started correctly by entering

the CONTINUE command. Enter the BOOT command to start the
operating system software if a TEST command was entered.

START—This command starts the operating system software at a
specified address. If no address is given, the contents of the PC
register are used. However, running a TEST ¢ommand alters the PC
register and memory so that the operating system software cannot

be started correctly by entering the START command. If a TEST
command was entered, use the BOOT command to start the operating
system software.

Testing

1.2

1-5

Running Power-Up Tests

Power-up tests run each time the system power is turned on and, if the
tesis are successful, the system either boots the operating system or halts
in console mode when the tests have finished, depending on the default
recovery action. See Chapter 3, Setting the NVR Default Recovery Action
Flags.

Power-up testing consists of a sequence of tests executed for each device
installed in the system. The test number of each device is listed on the
power-up screen display as the device is tested. LEDs on the rear of the
system box indicate the status of the system as it is powered up. See
Appendix G for a definition of the LEDs, if you need them.
Figure 1-2 shows an example of the power-up display and the power-up
summary.

Figure 1-2

Example cf Power-Up Test and Power-Up Summary

¥A41-a v1.4@
F..E...D...C...B...A...9...8...7...6...5...4...3...2_
? E
??

0040

0000.0005%5

(Soft

error)

00CO0

{Hard

error)

.12..@

@ CPU name and ROM version
NOTE
The -A in the CPU name indicates that the system under test is
a MicroVAX 3100 system. The CPU name of the VAXserver 3100
is KA41-B or KA41-F; for the InfoSeirver 100, the CFPU name 18
-

@ Power-up test sequence
@® Power-up summary
1.2.1

CPU Name and ROM Version

The first line, @ in Figure 1-2, indicates the CPU name (KA41-A) and
the ROM version (V1.3 or higher).

1-6

Testing

1.2.2 Power-Up Test Sequence
In the power-up test sequence, @ in Figure 1-2, the test numbers (in
hexadecimal) are listed in descending order from the first test, F, to
the final test, 1. Each test number is followed by three periods (...)
or a symbol and two periods (?.. for example). Table 1-2 outlines the
significance of each syiboi.

Table 1-2

Power-Up Symbols Defined

Symbol

Definition
LDevice test>d successfully or it may have a soft error.

Device has a hard error.

Option devive not installed or device not tested.
.

Option device installed, but its ROM code has not been executed.

The underscores in line @ indicate that no option device is installeq;
therefore, no option tests are done.

An asterisk (*) may only appear in TESTS 7, 6, or 4 through 2 and
indicates that an optional device is installed, but its ROM is destroyed
and the optional device must be replaced. Only TESTMS 7, 6, or 4 through
2 can have an * after them.

In the power-up test sequence, hard errors (errors that indicate the device
must be replaced for proper operation) are indicated by a question mark

(?). Note that soft errors do not put a question mark after the failing test
number during the countdown sequence.

1.2.3 Power-Up Summary
The power-up summary, @ ir: Figure 1-2, lists any errers found during
the power-up test. Figure 1-2 shows the power-up screen display with a
hard error found in TEST 1 and a soft error found in TEST E.

Testing

1-7

The power-up summary consists of question mark or two question marks

(7?), a test number, the ID number of the failed device, and an 8-digit
code. In the power-up summary, two question marks indicate a hard error
and one question mark indicates a soft error or a status for that device.
For example, in the power-up summary, @, the first line shows a soft
The second line shows a hard error for TEST 1, a device ID of 00C0, and a
code of 0100.2004. The device tested by TEST 1 must be replaced, but the
device tested by TEST E only indicates a status code and does not have to
be replaced. When you are not sure whether a device needs replacing or
not, refer to the troubleshooting section for that device (See Chapter 2).
Usually, a question mark in the power-up suminary indicates a minor
problem and the system may be usable without replacing any FRUs. Two
question marks in the power-up summary indicates a hard error. This
indicates a serious problem that may affect normal operation and use of
some component in the system. The failing device must be replaced before
booting the operating system software. If your system boots automatically,
you must stop the booting process by pressing the Halt button and check
the status of all devices in the system,

1.2.4 Checking the System Devices
Enter TEST 50 to display the configuration table after the power-up tests.
Check all the devices in the system to make sure they are all listed (online). If, for instance, a disk drive is installed but its power connector
becomes unplugged, the tests would not show an error during testing. You
should be familiar with the good status ¢ndes for each device listed in the
configuration table and know when a drive’s status code shows it to be
off-line when it really should be on-line.
If the terminal screen remains blank for more than 5 minutes after the
power is switched on, there may be a problem with the terminal, the
terminal cable, or the system. Check the LEDs on the back of the system
box to determine if the system has failed. If the system is normal, check
the terminal and cable. See Appendix G for a definition of the LEDs, if
IS
you need them.

1.2.5 Power-Up Test Codes
The power-up test codes indicate hard (fatal) errors, soft errors, no errors,
or status information. Any errors found by power-up tests are listed in

the power-up tests summary. These errors as well as the status of all
devices installed in the system are then stored in the configuration table.
Enter TEST 50 to display the configuration table.

1-8

Testing

Table 1-3 lists the test numbers and the devices that are tested during
that particular test. Enter TEST 50 (T 50) to display the configuration
table. The configuration table allows you to look at the status of a
device. It lists every device in the system and also lists the results of
the power-up tests and self-test. It is updated each time a self-test is run.
Remember that the configuration table contains the results of the powerup tests and self-test and not the results of the system exerciser. See
Section 1.3, Running Self-Test and Section 1.4, Running System Exerciser
Diagnostics.

Table 1-3

Test

Power-Up and Self-Test Commands

Mnemonics

Device

Reserved

CLK

Time-of-year clock

NVR

Nonvolatile random access memory (RAM)

Serial line controller

MEM

Memory

Memory management unit

Floating point unit

Interval timer

SCSI-A

SCSI-A bus devices

Teé

SCSI-B

SCSI-B bus devices

SYS

Interrupt controller and Ethernet ID ROM

DSH32-A

DSH32-B communications module
asynchronous lines

DSH32-S

DSH32-B communications module
synchronous lines

Reserved

Ethernet circuits

Testing

1-9

Figure 1-3 shows an example of a configuration table.
Figure 1-3

>>> TRST

Configuration Table (T 50)

KA41~A V1.3

08-00-2B-03-79-1F

CLK

0000.0001

NVR

0000.0001

0000.4001
00004001

MEM

00000001

00000000

00000001

FFFFFFO05

FFFFFFO3

0004.0001
00400000

0000.0001

SCS5I-A

7711.0001 V1.0

FFFFFFO5 FFFFFF0S
SCSI-B

1C1C.0001

FFFFFFO5 FFFFFFOS

FFFFFF0S5

FFFFFE

V1.0

SYS

0000.0000

DSH3z-A

Q0FF.0000

V2.C

CSH32-S

0000.0001

V2.0

0000.0001

00000001

FFFFFF03

FFFFFFOS

>>>

Any code in the configuration table other than 0000.0001 on the MM, FP,
IT, or SYS devices indicates a hard error and the system module must be
replaced for proper operation of the system. The other devices such as
CLK, NVR, DZ, MEM, SCSI-A, SCSI-B, and NI may have a code other
than (0000.0001) and may still operate normally.

Any code in the configuration table other than 0000.0001 on the DSH32-S
device indicates a hard error and the DSH32-B communications module
or the distribution board must be replaced for proper operation of the
system. The DSH32-A device may have a code other than (0000.0001) and
may still operate normally.
Go to the device’s troubleshooting section to determine whether or not the
device’s code indicates a fault or a status for the device. See Chapter 2.

See Chapter 3 for more information on reading the configuration table.
See Appendix E for a complete list of the power-up error codes.

1-10

Testing

Since ¢ question mark could indicate status information, some common
power-up status messages are defined as follows:
*

Clock not set — ? E 0040 0000.0005

This message indicates that the system clock has not been set. The
clock cannot be set while in console mode; it is set in program mode.
Once the clock is set, this code will be cleared the next time the clock
circuits are tested.

Low battery — ? D 0050 0000.0005
This message indicates that the battery’s charge is low which may be
the case when a system is first installed. Run the system for about 17
hours to fully recharge the battery.

No Ethernet cable (ThinWire) — ?? 1 00C0 0000.7004
This message indicates that the ThinWire Ethernet connector on the
back of the system is not terminated or that the ThinWire Ethernet
cable 1s not terminated correctly.

No Ethernet cable (standard) — ?? 1 00C0 0011.700E
This message indicates that the standard Ethernet connector on the
back of the system is not terminated or that the standard Ethernet
cable is not terminated correctly.

No heartbeat on standard Ethernet — ?? 1 00C0 0100.0001

This message indicates that the standard Ethernet is selected and
terminated correctly, but the Ethernet network is not supplying che
necessary heartbeat signals to the system. This is normal if the
loopback connector is installed on the standard Ethernet connector.

1.3

Running Self-Test

Self-test allows you to test every device again after the power-up tests are
completed. Devices can be tested individually (except for drives), a few at
a time, or all of them sequentially just like power-up tests.

1.3.1

Self-Test DiegnosticC mmands

Enter TEST or just T, followed by a space and the test number of the
device you want tested to individually test a device (drives are tested all
together on their particular bus). All devices connected to the SCSI bus
are tested and the results are listed in the configuration table. Enter
TEST 50 to view the configuration table.

Testing

1-11

Table 1-3 lists each device and its corresponding test number. Figure 1-4
shows an example of running self-test on an SCSI bus.
Figure 1-4

>>> TEST

Example of Running Sel{-Test on an SCSI Bus

NOTE
Enter TEST 50 to see the results.
Enter TEST followed by the test number of the first device to be tested
and then the test number of the last device to be tested to test a group of
devices. For example, enter TEST C 4 to test all devices between C and
4. You cannot exclude any intermediate tests, every device beiween C and
4 is tested. Enter TEST F 1 to test all devices. Enter REPEAT TEST x,
where x is any device between F and 1, to run a test repeatedly without
reentering it. Enter CTRL/C to exit from this test.

1.3.2 Self-Test with Loopback Connectors
Customer mode self-test does not test the drivers on the serial lines (DZ)
because serial line loopbacks are not installed. The Serial Line Controller
(DZ) must be tested in Field Service mode. Enter TEST C with loopbacks
installed in the two unused MMJ connectors and a 25-pin loopback
installed in the modem port. Enter TEST 50 to check the results in the
configuration table.
If only one MMJ loopback is available, install it in one of the ports
and run the tests. An error code of 0000.0200 for the DZ indicates that
some ports do net have the loopback installed, but the test port tested
successfully. The diagnostic test recognizes that a terminal is connected
to MMJ port 1 and no hard errors are generated for that port.

Similarly, Customer mode self-test does not test the the external cabling
or the transmit drivers or receivers on the distribution board. The
transmit drivers, receivers, and the external cabling must be tested in
Field Service mode.

1-12

Testing

To test the DSH32-B communications module, the distribution board, and
the internal cabling, proceed as follows:
1.

Install the H3101 36-pin loopback in the asynchronous port on the
rear of the system unit (see Figure 1-1).

Install the H3199 50-pin loopback in the synchronous port on the rear
of the system unit (see Figure 1-1).

Enter TEST 3 to run self-test on the DSH32-S sub ystem.

Enter TEST 4 to run self-test on the DSH32-A subsystem.

If you wish to include the external cables in the tests, proceed &3 follows:

Connect the 50-pin connector of the synchronous cable to the
synchronous on the rear of the system unit (see Figure 1-1).

Connect the 25-pin loopback (H3248 for RS232) or the 37-pin loopback

Connect one end of the asynchronous cable to the asynchronous port
on the rear of the system unit (see Figure 1-1).

Conlnect the 36-pin loopback to the other end of the asynchronous
cable.

Enter TEST 3 to run self-test on both the DSH32-S subsystem and
synchronous cable.

Enter TEST 4 ¢5 run self-test on both the DSH32-A subaystem and
asynchronous cable.

(H3198 for RS422/RS423) to the other end of the synchronous cable.

To test the cable concentrator (H3104), remove the 36-pin terminator from
the 36-pin cable and connect the cable to the concentrator. Install one or
more MM.J loopbacks in the ports on the cable concentrator. Enter TEST
4 at the console prompt. Table 1-4 shows addi‘ional self-test commands
that provide further testing capability.

Testing

Table 1-4

1-13

Self-Test Commands

Command

Meaning

>>>T 4000000X!

Run self-test once in cusiomer mode, loop on error (LOE).

>>>T 8000000X*

Run self-test in customer mode, loop on test (LOT).
This command can be negated by typing CTRL/C.

>>>T C000000X’

Run self-test, loop on error (LOE), loop on test (LOT), in

customer mode.

1X=3 For synchronous subsystem (DSH32-S) or X=4 for asynchronous subsystem (DSH32-A)

NOTE
The ThinWire Ethernet port or the standard Ethernet port

(depending on which port the customer is using) on the back
of the sysiem box must be terminated correctly when running
diagnostics on the Ethernet circuits (TEST 1). Otherwise an error
code of 0000.7001 or greater is listed in the configuration table,

1.3.3 Self-Test Codes
If an error is detected during self-test, a question mark is put next to the
test number and a failure message (84 FAIL) is displayed. Enter TEST 50
to check the results in the configuration table after self-test is completed.
The configuration table lists every device in the system, the results of the
self-test and power-up tests, and displays the error codes. It is updated
each time self-test is run. Remember that the configuration table contains
the results of the self-test and power-up tests and not the results of the
system exerciser. See Section 1.4. Go to the device’s troubleshooting
section to determine whether or not the device’s code indicates a fault or a
status for the device. See Chapter 2.
See Chapter 3 for more information on reading the configuration table.
See Appendix E for a complete list of the self-test error codes.

1-14

Testing

1.4

Running System Exerciser Diagnostics

The system exerciser simulates a worst-case operating system situation

test for each device and checks how the device operates under these
conditions. This type of testing usually finds any interactive problems.

There are three modes of system exerciser; customer mode, manufacturing
mode and Field Service mode. Table 1-5 lists the test numbers
corresponding to each mode.
Table 1-5

System Exerciser Test Modes

Test No.

System Exerciser Mode

Customer mode

T 101

Field Service mode

T 102

Field Service mode

T 80000103

Manufacturing mode

T 80000106

Field Service mode

CAUTION
TEST 80000103 and TEST 80000106 overwrite customer data.

Table 1-6 describes these commands in detail.
The system exerciser exercises most of the devices. However, some devices
such as the memory management unit (MM) and the interval timer (IT)
are tested through the testing of other devices and are not displayed. Of
the devices the exerciser does exercise, it runs each one sequentially until
all have been run once, then it runs them concurrently.
To run the Field Service mode system exerciser, we recommend that the
console terminal be attached to MMJ Port 3 with BREAK ENABLED;
however, MMJ Port 1 can also be used. Install loopback connectors on
any unused MMJ ports, the modem port, and on the synchronous and
asynchronous ports of the DSH32-B communications module. Insert and

load the special-keyed! test diskette, compact disc, and tape cartridge (if
the system has these devices installed).

' This special key o1 the media prevents the exerciser from accidentally destroying
data on the custome: s diskette or tape cartridge. The compact disc is a read-only
device.

Testing

1-1§

Enter TEST 101, TEST 102, or TEST 80000106 to run the exerciser in
Field Service mode.
NOTE
A 12-15336-08 Modem Port Loopback Connector must be used to
enable operation of the service exerciser tests.

TEST 80000106 allows you to enter the test number of the individual
devices you want to run the exerciser on. Figure 1-5 shows an example of
running the system exerciser on the the DSH32-A subsystem.
Figure 1-5

>>»

‘TRS8T

?s>>

Running the System Exerciser on Individual Devices

80000106

NOTE
Entering 4 3 at the ?>>> prompt tests both the DSH32-A and

DSH32-S subsystems of the DSH32 option. Entering 3 will test
only the DSH32-S subsystem. Entering 4 will test only the DSH32A subsystem.
This procedure tests only as far as the loopbacks on the asynchrowious
port. To test the external cable, remove the H3101 36-pin loopback
connector from the asynchronous port and connect it to one end of the 36pin cable. Connect the other end of the 36-pin cable to the asynchronous
port on the rear of the system unit. Enter TEST 4 at the console prompt
>

To test the cable concentrator, remove the H3101 36-pin loopback from
the asynchronous port. Connect one end of the 36-pin cable to the
asynchronous port. Connect the other end of the 36-pin cable to the
cable concentrator. Install one or more MMJ loopbacks in the cable
concentrator. Enter TEST 4 at the console prompt >>>.
If the diskette or tape drive are not loaded with the special-keyed media,
the system exerciser does not do destructive writes to them and t{ests
them the same way as it does during the customer mode system exerciser.
If the compact disc drive is not loaded with the test disc (P/N 30-23507-

03), the drive does not perform any reads. If the test disc is not available,
any disc loaded allows the exerciser to perform reads but does not check
the error correction circuits (ECC). See Section 3.6 if you need information
on creating the special diagr.»stic keys on diskette. See Section 3.5 if you
need information on creating the special diagnostic keys on tape.

1-16

Testing

The test numbers and mnemonics used for the system exerciser are
the same as the test numbers and mnemonics used by self-test. See

1.4.1 System Exerciser Diagnostic Commands
Table 1-6 describes the system exerciser commands.

When running TEST 0 or TEST 101, the exerciser automatically stops
after all the devices have been tested simultaneously. Typically, it takes
about 5 minutes for the test on the slowest device to finish. When the test
is finished, the results and the halt message (06 HLT INST) are disglayed.

This halt message is normal for these two tests.

If TEST 102 or TEST 80000106 is entered, the exerciser continues testing
until you press CTRL/C.
Table 1-6
Test

System Exerclser Dlaghostic Commands
Description of Commands

Runs customer mode system exerciser. No loopback connectors
and no removable media are required. It exercises each device
once sequentially, then exercises them simultaneously, and
stops when the slowest device finishes (about 5 minutes).

T 101

Runs Field Service mode system exerciser. Loopbacks and
removable media are required. It exercises each device once
sequentially, then exercises them simultaneously, and stops
when the slowest device finishes (nbout 5 t0 8 minutes). Do not
stop the exerciser before it is finished.

Testing

Tabie 1-6 (Cont.)
Test
T 102

1-17

System Exerciser Diagnostic Commands

Description of Commands
Runs Fieid Service mode system exerciser. Loopbacks and

removable media are required. It exercises each device once
sequentially and then exercises them simultaneously until
you terminate the tests. Press CTRL/C to terminate the tests.
Once the test are terminated, an extended summary for some

of the tests can be displayed. Press RETURN to display the
extended summary. Continue pressing RETURN to display

more extended summaries. Press CTRL/C again to terminate
the extended summary and return control to the console prompt
(>>>). Note that the exerciser takes up to 30 seconds to stop
after you press CTRL/C. Do not stop the exerciser until every
device i8 exercised twice (second pass). Also, do not press the
halt button to stop the exerciser.

T 80000106

Individual device testing. Loopbacks and removable media
are required. Runs system exerciser diagnostics on individual
devices (TEST 6 and TEST 7 are considered individual devices
even though they test several drives). This test allows you to
test individual devices by entering the test number of the device
at a second prompt. This individual testing saves time since
you do not have to wait for all of the other devices to finish
testing.

T 80000103

Runs manufacturing mode system exerciser. Loopbacks and

removable media are required. It exercises each device once
sequentiaily and then exercises them simultaneously until
you terminate the tests. Preas CTRL/C to terminate the tests.
Once the test are terminated, an extended summary for some
of the tests can be displayed. Press RETURN to display the
extended summary. Continue pressing RETURN to display
more extended summaries. Press CTRL/C again to terminate
the extended summary and return control to the console prompt
(>>>). Note that the exerciser takes up to 30 zeconds to stop

after you press CTRL/C. Do not stop the exerciser until every
device is exercised twice (second pass). Also, do not press the
halt button to stop the exerciser.

1.4.2 System Exerciser Codes

The system exerciser displays the status of the devices on the screen as

the exerciser is running. Any errors found are displayed in the exerciser
display. When examining the exerciser display, one question mark in the
far left column indicates a soft error, two question marks indicate a hard
error, and the absence of question marks usually indicates success. There
o
may s
be Llonnn
dimes subvan
when there art no Guestion marhs, bui a drive may not be

1-18

Testing

listed in the display (for example, an unplugged power cable.. in these
instances, you need to he familiar with the codes of all devices so that
when you examine the display, you know if a specific drive or device is
listed and if the drive or device has a fault.

Figure 1-6 shows an example of the system exerciser display whi's
running the system exerciser in Field Service mode. Customer moae gives
the same display, but with a CU (customer mode) in place of the FS (Field
Service mode) on the top of the display.
Figure 1-6

System Exserciser Digplay Example

>>> YBEST

KA41-A

101

V1.3

rs @

0080

0000.0001

00:01:12

0010

'FM

0137.0001

OOA7

00:02:02

0090

SISI-A

6000.0001

0002

00:02:23

0002

00:02:56

3200.0001

OOAU

SCSI-B

6000.0001
2200.0001
3200.0001

4101.0471 @
7200.0001
4

B81F0

DSH32-A

OOFF.0001

00:03:15

0001.0000

00:03:26

0001.0001

0001.0001
0001.0001

0001.0001
3

B1IF1

DSH32-S

0000.0001
1

00CO

00
206

0.00:08:14
HLT
PC

INST
-~

O00OSA0F

0000.0001

® @

00:04:01

Testing

1-19

@ The CPU name (KA41-A), the ROM version (V1.3), the ROM status

(01 — if not 01, the ROM is corrupted and the system module must
be replaced), and the mode of the system exerciser (CU for customer
and FS for Field Service mode). The following lines of the display list
information on the devices that are exercised by the system exerciser.
Example of RRD40 erior code.

Status indicators (if any).

The test number (C,B,7,6,1). TESTS 7, 6, and 4 through 2 are option
modules and are listed in the display only if they are installed.
The device identifier (06080, 0010, and so on).
The mnemonic for each device (DZ, MEM, and so on).

The code (0000.0000) for that device. Note that the SCSI-A and
SCSI-B devices have additional codes for each drive that is installed.
The number of times the device was tested.
The progress count (available on some devices).

The time of the last pass the exerciser made on that device. The time
is in the following format; days hours:minutes:seconds.
A question mark in the far left column indicates a soft error, two
question marks indicate a hard error, and the absence of question marks
usually indicates success. If an error is indicated, go to the device's
troubleshooting section to determine whether or not the device must be
replaced for normal operation. See Chapter 2.

See Appendix F for a compiete list of the system exerciser error codes.

Some devices display the progress count which indicates the progression

of the test for that device. At the beginning of each test pass, the progress
count is again initialized to zero.

1-20

Testing

1.4.3 Extended Summary Reporting
Extended summaries are available only when running the system
exerciser in Field Service mode. They contain additional error information
on some of the devices run by the exerciser. Extended summaries are
available after the following tests:
¢

When running TEST 101, extended summaries are available when the
testing automatically stops after the second pass.

When running TI'ST 102, extended summaries are available when
you halt the tests. Press CTRL/C to halt the test when the second
pass is completed.

When running TEST 80000106, extended summaries are not
immediately available. Enter SHOW ESTAT at the console prompt
(>>>) to display the results of the tests once again.

When running TEST 101, press RETURN after the test has stopped
to display the first extended summary. Continue pressing RETURN to
display all of the extended summarie. until you return to the exerciser
display.

When running TEST 102, press CTRL/C to halt the system exerciser.
Press RETURN to display the extended summaries. Continue pressing
RETURN to display more extended summaries. Press CTRL/C return to
the console prompt (>>>).
When running TEST 80000106, extended summaries are not available.
Press the halt button after the second pass of the test has finished and
enter the SHOW ESTAT command at the console prompt (>>>) to display
the results of the test once again.
Figure 1-7 shows an example of the extended summary foi the SCSI-A
device and then an example for the SCSI-B device.

1-21

xample of SCSI Extended Summary Report

}

Testing

KA4l-A

V1.3

kkxkxnkx

SCSI-A

STM_SUMM

0 00:05:57

#*xxxix

adyx

rds

wts

%fs

xferr

sde

003

008

020

157

000

0 00:05:57

*akkxr

kxxkkkkxk

STM

TYPE ANYTHING

>>> [Fetorn]
kwkkkakkx

SCIT~B

STM_SUMM

adr

rds

wts

xfs

xferr

sde

004
005

008
008

000
004

073
023

000
000

a##xsxkss

STM_TYPE_ANYTHING

@ The SCSI address ID of a drive.
@ The number of reads performed on that drive.

@ The number of writes performed on that drive.

@ The number of data transfers performed on that drive.
@ The number of transfer errors on that drive.
Enter SHOW ESTAT to display the extended sumimaries once again after
exiting the system exerciser. SHOW ESTAT brings up extended summary
information from the last time you ran the Field Service system exerciser.

2
Troubieshooting
This chapter contains infermation on troubleshooting a MicroVAX 3100,
a VAXserver 3100, or an InfoServer 100 system. The nameplate on the

front of the sysiem box identifies the system type. All procedures in this
chapter apply to these systems unless specificelly listed in the section
titles or as described in the text. Also, all troublechooting procedures are
done while in console mode (operating system software halted).

2.1

Troubleshooting Procecures

siefer to Table 2—1 to locate the troubleshooting section for the faulty
device if you already know which device it is.
Run the diagnostics (self-test or system exerciser) if you think there is a
problem with the system but are not sure which, if any, device is faulty.
When you identify the faulty device, refer to Table 2-1 to locate the
troubleshooting section for that device. See Chapter 1 for a description of
the diagnostic procedures.

Troubleshooting

2-2

Table 2-1
Failing

Troubleshooting Procedures

Test

Device

Section

CLK

NVR

2.4

MEM

2.7

2.8

SCSI-A

2.10

6or7

RZ23 disk drive

2.14

6or7

RX23 diskette drive

2.16

TZ30 tape drive

2.13

SCSI-B

2.11

RZ55 expansion box

61.1

RRD40 expansion box

6.2.1

TKb50Z expansion box

6.3.1

SYS

2.17

DSH32-B communications module
asynchronous lines

2.18

DSH32-B communications module

2.19

synchronous lines

221

No screen display

2.2

No Screen Display

Figure 2-1 shows the normal sequence of events during power-up. Refer
to Section 2.2.1, Troubleshooting Procedure for No Screen Display, if
nothing is displayed on the console screen during power-up.

Troubleshooting

Figure 2-1

2-3

Nommal System Power-Up Flowchar

Swaich on the power

The green power light comes on. The LEDs on
the back of the system box count down
(in Hex). If not, see Section 2.22 Power Supply

Troubleshooting Procedures.

Within two minutas, the power-up diagnostic

countdown i1s displayed on the consold screen
if no, retur to Sectian 2 22 Power Supply
Troubieshoating Pracedures.

1
It nu tatal errors are detected during power-up
testing, the system displays the boot devices

recovery achon fiag

The System automatically boots from the

system disk or from the specitied default boot
device.

The system haits automancally

Prass the Halt button on the rear on the system

unit to return to console mode for tasting
purposes.

MLO-002962

2-4

Troubleshooting

2.2.1 Troubieshooting Precedure for No Screen Display
Each step in this troubleshooting procedure instructs you to disconnect
an FRU, power-up the system, and determine if the problem still exists.
Each step describes a different FRU to disconnect. You must disconnect
an FRU as described in each step until the system powers-up normally.
Once the system powers-up normally, the last FRU you disconnected is
the failing FRU. Replace the failing FRU and retest the system for any
further problems.
Follow these steps to locate the failing FRU:
1.

Check the terminal cable for a good connection on the terminal and
on the system box. Make sure the terminal is switched on. The LED
on the terminal shouid be lit when power is supplied. Check the
terminai set-up. It should be set to 9600 baud, 8 bits, and no parity
(Check the terminal documentation if you do not know how to change
the set-up). Turn up the brightness control until raster is observed. If
no raster appears on the screen, refer to the terminal troubleshooting
documentation.

Power down the system. Check the position of the Break Enable
switch on the back of the systera box. It should be in the down
positicn if a terminal connected to MMJ port 1 is used as the console
device. It should be in the up position if a terminal connected to MMJ
port 3 is i..22d as the console device. Confirm that the terminal has no
output when connected to either port. See Figure 1-1.
NOTE
The position of the switch is only read during power up.

Power down the system, remove both drive mounting panels
from the system unit, and disconnect and remove the DSH32-B
communications module (if installed).

Remove the memory module from the system module.

Power up the system with the memory module disconnected. If the
system has no screen display, the problem is not the memory module,
proceed to step 6. If the system has a screen display, replace the
memory module and retest the system.

Power down the system. Replace the system module and power up the
system again. If the system still has no screen display after replacing
the system module, replace the power supply.

Troublashooting

2-5

2.2.2 Additional Information on Nonoperating Systems
See Appendix E for a complete list of the power-up and self-test error
codes. See Appendix F for a complete list of the system exerciser error
codes.

2.3

TESTE — CLK — Time-of-Year Clock

The time-of-year (TOY) clock controls the system date and time. The date
and time cannot be set while the system is in console mode. Therefore,
the code for the TOY clock should always indicate a soft error (0000.0005 clock not set) when the system is first powered on after replacing a system
module or the battery or before the operating system software is installed.

Sc)f-test is used to troubleshoot the time-of-year clock circuits. The
system exerciser does not test the TOY clock circuits. Enter TEST E to
run self-test.
A code of 0000.0001 next to the (i
X mnemonic indicates no errors
detected with the clock circuits. Replace the system module if any other

code is listed (except 0000.0005 as previously described).

2.3.1

Additional CLK Information

The operating system (VMS or ULTRIX) sets the date and time. Refer to

the operating system documentation to set the time.
The TOY clock is located on the system module. Therefore, the system
module must be replaced whenever the clock shows an error other than
the clock not set error.
See Appendix E for a complete list of the power-up and self-test error
codes.

2.4

TEST D — NVR — Nonvoiatile RAM

The nonvolatile RAM (NVR) contains specific data that must not be lost
when the system is powered down. It stores boot device information, boot
flag information, the keyboard language, the time and date, the charge
status of the batlery, and other information. Since the battery charge
may be low before the initial installation of the system, the NVR may
show a soft error code of 0000.0005 indicating that the battery needs to be
r. harged.

Self-test is used to troubleshoot the NVR circuits. The system exerciser
does not test the NVR circuits. Enter TEST D to run self-test.

2-6 Troubleshooting

A code of 0000.0001 next to the NVR mnemonic indicates no errors
detected with the NVR circuits. Replace the system module if any other
code is listed (except 0000.0005 as previously described).

2.4.1

Additional NVR Information

The NVR circuits are located on the system module. Therefore, any error
code for the NVR, except the low battery charge code (0000.0005 - low
battery) indicates that the system module must be replaced. If the low
battery charge code does not clear within 1 hour of continuous operation,
check the battery cable connection. Then replace the battery and allow it
to charge for a 24-hour period.
See Appendix E for a complete list of the power-up and self-test error
codes.

2.5

TEST C — DZ — Serial Line Controller

The r.erial line controller (DZ) controls the four serial lines on the srstem

module. Table 2-2 lists the four serial lines and the port mnemonic for
VMS and ULTRIX operating systems.

Run self-test and the system exerciser to troubleshoot the DZ circuits.
Enter TEST C to run self-test. Then enter TEST 50 to see the results.
Enter TEST 80000106 and press RETURN, then enter C in response to
the ?>>> prompt to run the Field Service system exerciser on the serial
line controller only. Figure 2-2 shows an example of this command.

Figure 2-2

Running the System Exerciser on the Serial Line Controlier

(DZ)
>>> TEST

800J0106

?2>>> C

A code of 0000.0001 next to the DZ mnemonic indicates no errors detected
in the serial line controller circuits. Replace the system module if any
other code is listed.

Troubleshooting

2-7

2.5.1 Additional DZ Information
Install a 12-15336-08, 25-pin D-sub loopback connector on the modem port
and loopback connectors on MMJ ports 2 and 3 when running the tests
in Field Service mode. The diagnostic test recognizes that a terminal is
connected to MMJ port 1 and no hard errors are generated for that port.

If MMJ port 3 is used as the console port, by setting the Break Enable

switch to the up position before the system is powered on, the terminal
can be connected to MMJ port 3 and the loopback connectors installed on
ports 1 and 2.
The loopback connectors are not needed during customer mode testing
because the DZ uses internal loopback switches for transmission testing.
During Field Service mode testing, the serial line drivers are fully tested.
Characters are sent out to the four serial lines. They are verified as they
are looped back into the port's receiver. If a loopback connector is not
installed or the wrong character is received, an error code is listed in the
DZ code for that port.

The DZ circuite are on the system module. Therefore, if an error code
for the DZ other than 0000.0001 is indicated, replace the system module.
While in Field Service mode, check the loopbacks for proper installation
before replacing the system module.

See Appendix E for a complete list of the power-up and self-test error
codes. See Appendix F for a complete list of the system exerciser error
codes.
In the configuration table (TEST 50), the DZ contains six additional status
codes. See Figure 2-3. Any code other than the codes shown indicates a
failure on that line.
Figure 2-3

Example of the DZ Line in the Configuration Table

0000.0001

00000001

0000001

00000001

@ MMJ port 1 (DEC423)

@ MMJ port 2 (DEC423)

00000000 00000000

2-8

Troubleshooting

@ Modem (RS5232 Serial line port)
© MMJ port 3 (DEC423)

® Unused
® Unused
Tabie 2-2

0OZ Port Assignments

Port

VMS Mnemonic

ULTRIX Mnemonic

MMJ Port 1

TTAO

/dev/tty00

MMJ Port 2

TTA1

/dev/tty01

Modem

TTA2

/dev/tty02

MMJ Port 3

TTA3

/dev/tty03

2.6 TESTB— MEM — Memory
The memory diagnostics test all of the main memory in the system
including any memory option modules installed. Therefore, any error for
the memory must be deciphered to determine which moduie contains the
error. There may be more than one module containing the error.
Self-test and the system exerciser are used to troubleshoot the memory

circuits. Enter TEST B to run self-test. Then enter TEST 50 to see the

results or enter TEST 80000106 and press RETURN, then enter B in
response to the ?>>> prompt to run the Field Service system exerciser on
just the memory circuits (loopback are required, see Section 2.5.1).

Troubleshooting

2-9

A code of 00XX.0001 (self-test) next to the MEM mnemonic indicates no
errors detected with the memory circuits (the XX is the total amount of
memory instalied in the system (in hexadecimal)). If an error is detected,

see Section 2.6.1 to determine whether the system module or one of the
memory modules needs to be replaced.
A code of 0XXX.0001 (system exerciser) next to the MEM mnemonic
indicates no errors detected with the memory circuits (the XXX is the

number of pages of memory tested during the last pass of the exerciser (1
page = 512 bytes)). Table 2-3 lists the MEM system exerciser error codes
and lists which module needs to be replaced when an error is detected.
Table 2-3

MEM System Exerciser Error Codes

Error Codes

Definition

0XXX.0001

No error. XXX = number of pages tested.

0001.000F

Operating system error.

0002.000F

Operating system error.

0003.000F

Operating system error.

0004.000F

Operating sysi..m error.

0005.000F

Operating system error.

0006.000F

Operaang system error.

0007.000F

Operating system error.

0008.000F

Operating sysiem error.

0001.001F

Compare error on system module.

0002.001F

Compare error on an option r.iodule.

0001.002F

Parity error on system module.

0002.002F

Parity error on an option module.

2-10

Troubleshooting

2.6.1 Additional MEM Information
The Configuration display provides additional information about the
memory in the system. Figure 2-4 shows an example of the MEM
information in the configuration display.
Figure 2-4

MEM

Configuration Display MEM Information

0004.0020

00400000 00000003

@ The first four digits indicate the amount of memory available if no

errors are detected. The second four digits contain a status code for
the memory.

@ This code repeats the amount of memory in the system. Table 24
explains the codes.

@ This code contains the location of the failed memory. It is displayed
only if an error is detected.

Table 2-4

Hexadecimal Memory Codes

Codes

Mb of Memory

00400000

4Mb

00800000

8Mb

01000000

16Mb

01400000

20Mb

01800000

24Mb

01C00000

28Mb

02000000

32Mb

Troubleshooting

2-11

If the 8-digit error code, @, appears, there is an error in one or more of
the memory modules. A code other than 0 in any of the digits indicates
a faulty module. The module indicated by that digit depends on the
configuration as shown in Table 2-5.

Table 2-5

Locating a Falled Memory Bank

System module

{

4Mb module

]

12Mb module

16Mb mudule

Installed Memory

4Mb and 16Mb modules

12Mb and 16Mb

8-Digit Error Code for MEM

modules

S—Represents the system module
4—Represents the 4Mb memory r-odule
12-—Represents the 12Mb memory module

16—Represents the 15Mb memory module

Figure 2-5 shows a typical error code for MEM 1n the configuration

display.

Figure 2-5

Configuration Display MEM Error Code Example 1

MEM

0020.0020
02000000

10002000

2-12

Troubleshooting

In this example, digits 1 and 5 of the error code are not zero. The system
has 32Mb of memory, therefore the 12Mb and 16Mb memory modules are
installed. Table 2-5 indicates that when the 12Mb and 16Mb modules
are installed, digits 1 and 5 indicate errors on the 16Mb module and the
12Mb module respectively.

Figure 2-6 shows another MEM error code example.

Figure 2-6
MEM

Configuration Display MEM Error Code Example 2
0020.0020

01000000 00003003

In this example, digits 5 and 8 of the error code are not zero. The system
has 16Mb of memory, therefore the 12Mb memory module is installed.
Table 2-5 indicates that when only the 12Mb module is installed, digits
5 and 8 indicate errors cn the 12Mb module and the system module
respectively.

A code other than zero in digit 8 always indicates an error in the system
module memory.

See Appendix E for a complete list of the power-up and self-test error

codes. See Appendix F for a complete list of the system exerciser error
codes.

2.7 TEST A— MM — Memory Management
The memory management circuits control the allocation of physical and
virtual memory.

Self-test is used to troubleshoot the memory management circuits. The
system exerciser does not test the MM circuits directly. They are tested
when the system exerciser is run on the memory. Enter TEST A to run
self-test. Enter TEST 50 to see the results.

A code of 0000.0001 next to the MM mnemonic indicates no errors
detected with the memory management circuits. Replace the system
module if any other code is listed.

See Appendix E for a complete list of the power-up and seif-test error
codes.

Troubleshooting

2-13

2.8 TEST 9 — FP — Floating Point
The floating point (FP) controls the arithmetic operations done for the
CPU. Self-test is used to troubleshoot the floating point circuits. The
system exerciser does not test the FP circuits. Enter TEST 9 to run
self-test. Enter TEST 50 to see the results.

A code of 0000.0001 next to the FP mnemonic indicates no errors detected
with the floating point circuits. Replace the system module if any other
code is listed. See Appendix E for a complete list of the p ‘wer-up and
self-test error codes.

2.9

‘

TEST 8 —IT —interval Timer

The interval timer (IT) controls key timing operations in the system.
Self-test is used to troubleshoot the interval timer circuits. The system
exerciser does not test the IT circuits. Enter TEST 8 to run self-test.
Enter TEST 50 to see the results.
A code of 0000.0001 next to the IT mnemonic indicates no errors detected
with the interval timer circuits. Replace the system module if any other
code is listed. See Appendix E for a complete list of the power-up and
self-test error codes.

2.10 TEST7 — SCSI-A Bus
The SCSI-A bus is an internal device bus; no external devices can be

connected to this bus. It supports two devices only: the RZ23 system disk
and a bhack-up device, a TZ30 tape drive, an RZ23 disk drive or an RX23
diskette drive. The system disk uses small computer system interface
(SCSI) address ID 3; the TZ30, RX23, or RZ23 uses SCSI address ID 5.
In InfoServer 100 systems, the RZ23 system disk MUST be set to ID 1,
and the RRD40 or RRD42 on SCSI-A bus MUST be set to ID 2.
The procedures for troubleshooting devices on any SCSI bus are similar.
Look at the drives installed in the system unit and at any expansion boxes
connected and make sure their cables are connected correctly. Enter
SHOW DEVICE at the console prompt (>>>) to determine what drives
are installed on the SCSI bus you are troubleshooting. This command
lists all drives and devices operating in the system and lists which
drive is on which SCSI bus. See Section 2.12 for further information
on troubleshooting either the SCSI-A bus or the SCSI-B bus.

2-14

Troubleshooting

2.1

TEST 6 — SCSI-B — SCSI-B Bus

The SCSI-B bus is an internal and external device bus.
in Model 10 systems, one internal device and four external devices, or five
external devices can be connected to the bus. The internal device which
can be connected is the RZ23 disk drive.

In Model 20 systems, up to three internal devices and four external

devices can be connected to the bus. The internal devices which can be
connected include one RZ23 or one RX23 on the lower drive mounting
panel and two RZ23s on the upper drive mounting panel.
In InfoServer 100 systems, a second RRD40 or RRD42 may be connected
internally on the SCSI-B bus and is set to ID 5. Up to six additional SCSI
devices may be attached externally. If there is no internal device, seven
external SCSI devices may be attached. Note that the BC19J-1E SCSI
cable must be used as the external interconnect cable to ensure that bus
length restrictions are met.
NOTE
SCSI IDs of expansion boxes are determined by the SCSI ID
switch positions on the device. To simplify explanations, the SCSI
IDs mentioned in this chapter are the defauit values. They may
have been changed by the customer depending on the system
configuration.
External devices that can be connected include the RRD40 and RRD42
compact disc expansion boxes, the RZ55 and RZ56 hard disk drive

expansion boxes, the TK50Z tape drive expansion box, and other Digital
qualified SCSI devices. Any combination in which these devices are
connected is dependent on SCSI ID assignments.
If there are any other devices on the SCSI-B bus, be sure to note the type
of device and their SCSI addrer:es since they might be the cause of the
problem on the bus.

The procedures for troubleshooting devices on any SCSI bus are similar.
See Section 2.12 for further information on troubleshooting either the
SCSI-A bus or the SCSI-B bus.

2.12

General SCSIi Bus Troubleshooting

To troubleshoot an SCSI bus and its controller (SCSI-A or SCSI-B), run
self-test or the system exerciser.

Troubleshooting

2-1!

2.12.1 Self-Test
Run self-test to get a quick status of the SCSI buses and the drives on
those buses inclnding any devices connected to the SCSI port on the back
o” the system box.

CAUTION
An SCSI terminator must be connected to the SCSI port if no
external boxes are connected or to the last daisy-chained box
connected to the SCSI port.
Enter TEST 6 or TEST 7 depending on which SCSI bus you are
troubleshooting. Enter TEST 50 to see the results of self-test.
Table 2-6

Seif-Test Commands on the SCSI Buses

SCSI Bus

Test Number

SCSI-A

SCSI-B

2.12.1.1 Self-Test Codes Explained
Figure 2-7 shows an example of SCSI-B codes in the configuration table
(SCSI-A codes are similar). There is one line for the status of the SCSI

bus controller and one line that contains the status for all drives on that

SCSI bus. The status of the SCSI bus controller is next to the SCSI-B
mnemonic (first line 0000.XXXX) and each drive status is listed by SCSI
address order in the second line.
Figure 2-7

Self-Test Example on the SCSI-B Device

SCSI-B

1C1C.0001

V1.0

00000001

05000001

e 66
90

00000001

RZ23 or RX23 on lower drive mounting panel

00000001

RRD40 expansion box

RZ55 expansion box

RZ23 on upper drive mounting panel
RZ23 on upper drive mounting panel

01000001

FFFFFFO23

FFFF

2-16

Troubleshooting

@ TKS50Z expansion box
@ SCSI-B bus controller
@ Reserved for expansion
An easy way to determine if any errors are detected is by looking for the
question marks in the left column. If there are question marks, t* =n one
or more of the drives on the hus are faulty. To determine whick
- ice is
faulty, examine the status codes of the drives (second line). The address
IDs are numbered 0 through 7 from left to right. Table 2-7 lists the
normal status codes for each SCSI device available in the system. Any
code other than those previously listed indicates an ervor in the device at
that SCSI address ID.
Table 2-7

SCSI Devices Self-Test Status Codes

Status Code

SCSI Device

FFFFFF05

Device is off-line or not installed at this address.

FFFFFF03

SCSI bus controller.

FFFFFFFF

Device not tested - possible SCSI bus controller error.

00000001

RZ23 disk drive, RZ55 disk drive, or RX23 diskette drive.

01000001

TZ30 or TK50Z tape drive.

N5009001

RRD40 compact disc drive.

If a drive is configured for an address ID that indicates FFFFFF05, check
the drive's cabling and power source, then retest. If the code is still
FFFFFFO05 after retesting, replace the drive.

See Appendix E for a complete list of self-test error codes.

2.12.2 System Exerciser
Enter TEST 0 to start the system exerciser in customer mode. Enter
TEST 101 or TEST 102, at the console prompt, or enter TEST 80020106
and press RETURN, then enter 6 or 7 at the ?>>> prompt to start the
system exerciser in: Field Service mode. The customer mode system
exerciser does not perform reads or writes to the drives. The Field Service
mode system exerciser performs a complete read/write test on the tape
drive, diskette drive, and the disk drives (on reserved diagnostics blocks),
performs reads on the compact disc drive (if test disk is loaded), and also
performs data transfer tests on all drives. For Field Service mode to
run correctly, you must install the loopback on the serial line ports, load

Troubleshooting

2-17

the special-keyed tape cartridge! and diskette? into the tape drive and

diskette drive respectively, and load the RRD40 test disc before starting
the system exerciser. See Section 2.5.1 for more information on installing
the loopback connectors.

The first pass of the system exerciser on an SCSI bus tests the SCSI bus

controller and, if the SCSI bus controller is operating correctly, checks
the SCSI bus for the presence of any drives. It does not perform any
diagnostics or any data transfer tests on the drives during the first test
pass. If the SCSI bus controller is faulty, an error code is listed in the
display and the SCSI bus is not checked for the presence of any drives.
2.12.2.1 System Exerciser Codes Explained

Figure 2—8 shows the system exerciser display for SCSI-B (SCSI-A codes
are similar). There is one line for the status of the SCSI bus controller
and one line for each of the drives installed on the SCSI bus. The status
of the SCSI bus controller is next to the SCSI-B mnemonic (first line) and
the status of each drive is listed under the bus controller’s code (separate
line for each drive).

! TRST 73 writes a special key to a tape cartridge.
2 TEST 74 writes a special key to a diskette.

2-18

Troubleshooting

Figure 2-8

O00AO

System Exercigser Example for SCSI-B Device

SCSI-B

6000.0001

0000

00:03:18

0200.0001 @
1100.0001 @

2200.0001 @
3200.0001 @
4100.0001 @
5300.0001 @
RZ55 expansion box.

RX23 holding a write-protected diskette (1300.0001 if the diskette is

not write protected).

RZ23.

RZ23.
RRD40 expansion box.
TK50Z expansion box.
An easy way to determine if any errors are detected is by looking for the
question marks in the left column. If there are any question marks on

the SCSI bus controller’s status line, the SCSI bus controiler is probably
faulty and the error code identifies the problem. If there are any question
marks on a drive's status line, the problem could be in either the drive,

the SCSI bus cabling or terminator, or the SCSI bus controller. For
example, an error that is listed in the drive’s code may be a data transfer
error and does not isolate the problem tu the device itself; it may still be
in the SCSI bus controller.
See Appendix F for a complete list of the system exerciser error codes.

2.12.3 Additional SCSI Bus Information
The SCSI bus controller controls up to seven SCSI devices on the SCSI
bus. The SCSI-B bus can have internal and external devices connected.
The internal devices include the RZ23 disk drive, the TZ30 tape drive,
and the RX23 diskette drive. The external devices include the TK50Z
expansion box, the RZ55 disk expansion box, and the RRD40 compaci disc
expansion box.

Troubleshooting

2-19

All of the expansion boxes connect to che SCSI port on the back of the
system box using a daisy-chain cabling scheme. An SCSI terminator must
be installed on the connector of the last expansion box or installed on the
SCSI pori connector if expansion boxes are not used.
Each device on the SCSI bus, including the SCSI bus controller, has
its own address ID location. The SCSI bus controlier always holds the
address ID of 6 for all buses. Table 2-8 shows the address ID assignments
for both buses.
Table 2-8

SCSI Bus Address D Assignments (both buses)

1))

SCSI-A Bus

SCSI-B Bus

Unused

Reserved for expansion

SCSI-A bus controller

SCSI-B bus controller

TZ30, RX23, RZ23

TK50Z expansion box

Unused

RRD40 expansion box

RZ23 (system disk)

RZ23

Unused

RZ23

Unused

RZ55 expansion box

Unused

R223, RX23

NOTE
Model 10 systems do not contain as many internal storage devices

as Model 20 systems; however, both systems use the same SCSI ID
assignments, as listed in Table 2-8. InfoServer 100 systems have
different SCSI-A bus assignments. The system disk, RZ23E or
RZ23L, MUST be ID 1 and the internal RRD40 or RRD42 compact
disc drive on SCSI-A bus MUST be ID 2. InfoServer 100 systems
do not support the TZ30 or the RX23.

Enter SHOW DEVICE at the console prompt (>>>) to determine the SCS]
address ID of the devices on the SCSI-A or SCSI-B bus. This command
digplays all devices connected to the SCSI bus controllers. This display

lists the SCSI address ID of all devices on SCSI buses. Figure 2-9 gives
an example of this command.

Troubleshooting

2-20

Figure 2-9

Example of the SHOW DEVICE Command

>>> SHOW DEVICE

VMS/VMB

OLTRIX

ADDR

DEVTYP

NUMBYTES

RM/FX

DEVNAM

—

- -

- —-— -

ESA0

SE0

08-00-2B-03-79-1F
@

DKA300

RZ3

A/3/0/00

DISK

MKAS00

TZS5

A/5/0/00

TAPE

A/6

INITR

B/2/0/06

DISK

..HostID....

DKB200

DKB300
DKB400

RZ10
RZ11
RZ12

...HostID....

B/3/0/00
B/3/0/00
B/6

........

104

104
_

DISK
RODISK

104
593

MB
MB

e -

R223

FX
RM

R223
RRD40

INITR

>>>

@ ESAO — the Ethernet device and the Ethernet address of the system.

@ .. .HostID... — the SCSI bus conircller.
@ Device numbers for VAX/VMS operating systems.

@ Device numbers for ULTRIX operating systems.

@ Address.
@ Device type.

@ Number of megabytes.
@ Removable or fixed media.

@ Write protected.
@ Device name.
If the system does not contain a full configuration of drives internally,
additional expansion boxes can be connected to the SCSI-B port using one
of the unused SCSI address ID locaticns. Section 2.12.4 explains how to
set the proper SCSI addres< 1D for all devices.

Troubleshooting

2-21

2.12.4 SCSI Bus Address ID Settings
This section shows how each SCSI device’s address ID is determined and
set.

The jumpers and switches shown in the following figures are set to the
recommended SCSI address ID for each drive.

It is sometimes necessary to change the default setting. When two devices
with the same default address ID are installed on an SCSI bus, the
address ID of one of (he devices must be changed. This is because no
two devices on an SCSI bus can have the same address ID. The SCSI
Address ID) on the second device must be set to any one of the unused
valid address IDs (0 to 7) on that bus. Remember that both SCSI buses
operate independently as far as address IDs are concerned.
2.12.4.1 Setting the SCS! ID on the TZ30
Figure 2—-10 shows the location of the SCSI ID switches on the TZ30 tape
drive. Table 2-9 lists the switch settings corresponding to the possible
SCSI IDs.
Figure 2-10

T2Z30 SCSI ID Switch Locations

WA X0798 B8

MLO-003379

2-22

Troubleshooting

Table 2-9

TZ30 SCSI ID Swiich Settings

Address i} on

TZ30 Tape Drive Switch Settings

SCSI Bus

Off

off

Off

Ooff

Off

off

Off

'Reserved address ID for SCSI bus controller

2Recommended address ID for the TZ30 tape drive

2.12.4.2 Setting the SCSI 1D on the RZ23

Figure 2-11 shows the location of the SCSI ID switches on the RZ23 hard
disk drive. Table 2-10 lists the SCSI ID jumper combinations.

Troubleshooting

Figure 2-11

RZ23 SCSI ID Jumper Locations

Signat Connector

Connector to HOA Module

SCSI 1D Jumper Wires

g o T
Pows; Cranecior
MLO 002143

Table 2-10

RZ23 SCSI ID Jumper Combinations

Address ID on

RZ23 Jumper Settings

SCSI Bus

Out

'Reserved address 1D for SCSI bus controller.
2Recommended address IDs for the RZ23 drives on SCSI-A bus.
tRecommended address IDs for the RZ23 drives on SCSI-B bus.

2-23

2-24

Troubleshooting

2.12.4.3 Setting the SCSI ID for the RX23
The SCSI ID for the RX23 is set on the FDI board. Figure 2-12 shows the
location of the SCSI ID switches on the FDI board. Table 2-11 lists the
SCSI ID switch settings.
Figure 2-12

FDI Board SCSI ID Switch Positions

SCSI D Swiches
MLO 003273

Table 2-11

RX23 SCSI ID Switch Settings

Address ID on

RX23 Switch Settings

SCSI Bus

Off

off

Off

off

Off

1Reserved address ID for SCSI bus controller.
2Recommended address IDs for the RX23 drives on SCSI-A bus.
3Recommended address iDs for the RX23 drives on SCSI-B bus.

Troubieshooting

2-25

RX23 Diskette Drive Select Switch Seftings
Figure 2-13 shows the only valid switch setting for an RX23 diskette
drive. It should be set to the zaro position which is all the way towards
the back.
Figure 2-13

RX23 Select Switch Setting

MLO-003382
2.12.4.4 Setting the SCS! ID on the RRD40
Figure 2—14 shows the location of the SCSI ID switches on the RRD40
corapact disc drive expansion box. Table 2—-12 lists the switch settings
corresponding to the possible SCSI IDs.

2-26

Troubleshooting

Figure 2-14

RRD40 SCSi ID Switch Locations

SCS11D &

BEEEd
1

Lacation of SCS| Switchas

Baul Lock

Power Cord

Voltags Selactor

Troubleshooting

Table 2-12

RRD40 SCSI ID Switch Settings

Address ID on

RRD40 Expansion Box Switch Settings

SCSI Bus

Down

Not used

Down

Not used

Down

Not used

Down

Not used

Down

Not used

Down

Not used

'Reserved address ID for SCSI bus controller.

2Recommended address ID for the RRD40 compact disc drive.
.

tBecause switch 4 is unused, it can be in either position.

Not used

2-27

2-28

Troubleshooting

2.12.4.5 Setting the SCSI ID on the RZ55

Figure 2-15 shows the location of the SCSI ID switches on the RZ55 hard
disk drive expansion box. Table 2-13 lists the SCSI ID switch settings.
Figure 2-15

RZ55 Expansion Box SCSI ID Switch Locations

l oN

123

m
OPEN

wAN IS 0

MO 00322Y

Troubleshooting

Table 2-13

’

RZ55 SCSI ID Switch Settings

Address [ on

RZ55 Expansion Box Switch Settings

SCSI Bus

Down

2-29

Down

'Reserved address 1D for SCSI bus c... troller.

2Hecommended address 1D for the RZ55 expansion box.

2.12.4.6 Setting the SCSI ID on the TK502-GA

Figure 2-16 shows the location of the SCSI ID switches on the TK50ZGA type tape drive expansion box. Table 2-14 lists the SCSi ID switch
settings.

Troubleshooting

2-30

Figure 2-16

TKS0Z-GA SCSI ID Switch Locations

ro
L

123

)

OPEN

WA B9 N8
MLO 003320

Table 2-14

TKS50Z-GA SCS! ID Switch Settings

Address ID on

TK80Z-GA Expansion Box Switch Settings '

SCSI Bus

Down

The switch convention is the opposite to the RZ565 SCSI 1D switch convention.
2Reserved address ID for SCSI bus controller.

3Recommended address ID for the TK50Z-GA expansion box.

Troubleshooting

2-31

2.13 Troubleshooting a Tape Drive (TEST6 or 7)
This section describes how to troubleshoot a TZ30 tape drive in the system
box or th: TK50 tape drive in the TK50Z expansion box. This section
assumes you know how to read, decipher, and understand the SCSI bus
operation, its codes, and its address ID setiings. See Section 2.12 for
further information about the SCSI bus operation if you are not familiar
with this type of bus. Otherwise, the next two paragraphs explain the
self-test and the system exerciser results for the tape drive. Enter SHOW
DEVICE to check the SCSI address ID of the tape drive and to determine
which bus it is on.
Self-test results for the tape device should contain 01000001 in the
SCSI address ID 5 location. A ccde of FFFFFFO05 indicates that the
device is not installed, not powered up, or faulty. A code of FFFFFFFF
indicates that the device was not tested because of an SCSI bus controller
error. Any code other than those pre iously mentioned indicates an error
with the tape device, a cabling problem, or an error with the SCSI bus
controller. Run the internal self-test on the TK50Z expansion box if there
is a problem with the external tape device. See Section 6.3.1. Otherwise,
replace the internal TZ30 tape device and retest the system. Replace the
system module if replacing the TZ30 tape device did not fix the probiem.
When running the system exerciser in Field Service mode with the special
keyed tape cartridge installed, the code for the tape device shows that it
is not writable (5100.0001) during the first pass. However, the subsequent
passes should show that it is removable and writable (5300.0001) as long
as the cartridge has a valid special key on it and the SCSI bus contreller
is operating correcily. So you must wait for the system exerciser to
complete at least twc passes to see if the tape drive (address ID 5 in this
case) is operating correctly.

2.14

Troubleshooting an RZ23 Disk Drive (TEST &
or7)

This section describes how to troubleshoot an RZ23 disk drive. This

section assumes you know how to read, decipher, and understand
the SCSI bus operation, its codes, and its address ID settings. See
Section 2.12 for further information about the SCSI bus operation if you
are not familiar with this type of bus. Otherwise, the next two paragraphs
explain the self-test and the system exerciser results for the RZ23 disk
drive at SCSI ad4ress IDs 3 and 5 on SCSI-A bus and address IDs 1, 2, or
3 on SCSI-B bus. Enter SHOW DEVICE to check the SCSI address IDs of
the disk drives and to determine which bus they are on.

2-32

Troubleshooting

Self-test results for each disk drive should contain 00000001 in the SCSI
address locations occupied by the disk drives. A code of FFFFFF05
indicates that the device is not installed, not powered up, or faulty. A
code of FFFFFFFF indicates that the device was not tested because of
an SCSI bus controller error. Any code other than those previously listed
indicates an error with the disk drive at that address ID location, a
cabling problem, or an error with the SCSI bus controller.

When running the system exerciser in Field Service mode, the code for
the disk drive shows that it is writable an that no errors are present
(1200.0001, 2200.0001, 3200.0001, or 5200.)001 ). Any error code other
than those previously listed indicates an error is most likely on the disk,
but never rule out the possibility of an error on the SCSI bus controller
itself.

2.15

Troubleshooting an RX23 Diskette Drive

This section describes how to troubleshoot an RX23 diskette drive.

This section assumes you know how to read, decipher, and understand

the SCSI bus operation, its codes, and its address ID settings. See
Section 2.12 for further information about the SCSI bus operation if you
are not familiar with this type of bus. Otherwise, the next two paragraphs
explain the self-test and the system exerciser results for the RX23 disk
drive at SCSI address ID 5 on SCSI-A bus and address ID 0 on SCSI-B
bus. Enter SHOW DEVICE to check the SCSI address ID of the diskette
drives and to determine which bus they are on.
Self-test results for each diskette drive should contain 00000001 in the
SCSI address locations ‘ccupied by the disk drives. A code of FFFFFF05
indicates that the device is not installed, not powered up, or faulty. A code
of FFFFFFFF indicates that the device was not tested because of an SCSI
bus controller error.
When running the system exerciser in Field Service mode, a code of
1100.0001 for the disk drive shows that it is write protected, does not
contain the special diagnostic key, and that no errors are present. A

code of 1300.0001 for the disk drive shows that it is not write protected,
contains the special diagnostic key, and that no errors are present.
Any error code other than those previously listed indicates an error on
the special keyed diskette, the FDI board, or the diskette drive. If an
error code is displayed, replace the special keyed diskette and run the

tests again. If that fails to solve the problem, replace the FDI board. Run
the tests again. If the system still displays the error, replace the RX23
diskette drive.

Troubleshooting

2-33

Never rule out the possibility of an error on the SCSI bus controller itself.
If replacing the special keyed diskette, FDI board, or diskette drive failed
to solve the problem, replace the system module.

2.16

Troubieshooting an RRD40 or an RRD42
Compact Disc Drive (TEST 6)

This section describes how to troubleshoot an RRD40/42 compact disc
drive expansion box. This section assumes you know how to read,
decipher, and understand the SCSI bus operation, its codes, and its
address ID settings. See Section 2.12 for further information about
the SCSI bus operation if you are not familiar with this type of bus.
Otherwise, the next two paragraphs explain the self-test resuits and the
gystem exerciser results for the RRD40/42 compact disc drive at SCSI
address ID 4. Enter SHOW DEVICE to check the SCSI address ID of the
RRD40/42 drive.
Self-test results for the RRD40/42 drive should contain 05000001 in the
SCSI address ID 4 location. A code of FFFFFF05 in: .«cates that the device
is not installed or not powered up. A code of FFFFFFFF indicates that
the device was not tested because of a SCSI bus controller error. Any code
other than those previously listed indicates an error with the compact disc
drive, a cabling problem, or an error with the SCSI bus controller. The
RRD40/42 expansion box is one FRU (no replaceable FRUs inside the box)
and the whole box must be replaced if an error is detected. Be sure that
the SCSI bus terminator is connected to the last expansion box on the
daisy chain.
InfoServer 100 systems may have one or two internal RRD40 or RRD42
compact disk drives. The CD on the SCSI-A bus MUST be set to address
ID 2; the CD on the SCSI-B bus is set to ID 5.
When running the system exerciser in Field Service mode with the
RRD40/42 test disk instalied, the code for the disk drnive shows that it
is removable and that no errors are present (4100.0001). The test disk
contains known errors embedded to test the error correction code (ECC)
logic. However, any disk can be installed to perform read testing on the
RRD40/42. Any error code other than those previously listed indicates an
ervor is most likely on the compact disk or its controller module, but never
rule out the possibility of an error on the SCSI bus controller itself.

2-34

Troubleshooting

2.17 TEST 5 — §YS — Interrupt Controller and
Ethernet iD ROM
The interrupt controller manages the device interrupts in the system and
checks the Ethernet ID ROM for valid contents.
Self-test is used to troubleshoot the SYS circuits. The system exerciser
does not test the SYS circuits. Enter TEST 5 to run self-test. Enter TEST
50 to see the results.
A code of 0000.0001 next to the SYS mnemonic indicates nc <.rors
detected with the SYS circuits. Replace the system module if any other
code is listed (except 0000.0004 as descrived in the following section).

2.17.1 Additional SYS information
A code of 0000.0004 next to the SYS mnemonic indicates an error in the
Ethernet ID ROM. Since the ROM is not an FRU, you must replace the
system module.

CAUTION
If the Ethernet ID ROM has failed, do not put the old ROM on
the aew s ~tem r.odule. Instead, replace the system module and
notify the system manager of the new Ethernet ROM addiess.
See Appendix E for a complete list of the the power-up and self-test error
codes.

2.18 TEST 4 — DSH32-B Asynchronous Subsystem
(DSH32-A)
The DSH32-A subsystem controls the eight-asynchronous communication
port on the rear of the system unit. The DSH32-A subeystem
asynchronous line drivers are located on the distribution board and are

controlled from the DSH32-B communications module. The asynchronous
port on the rear of the system unit has eight data-only communication

lines to which terminals or other peripheral devices can be connected
through an asynchronous cable and an eight-MMJ port cable concentrator.

Self-test and the system exerciser are used to troubleshoot the DSH32-A
subsvstemn. Enter TEST 4 to run the self-test. Then enter TEST 50 to see
the results. Enter TEST 80000106 and and press RETURN, then enter 4
in response to the ?>>> prompt to run the Field Service system exerciser
on the DSH32-A subsystem only. Figure 2-17 shows an example running
the system exerciser on the DSH32-A subsystem.

Troubleshooting

Figure 2-17

2-35

Running the System Exerciser on the DSH32-A Subsystem

>>> TEST 80000106

> 4

A code of 00FF.0001 next to the DSH32-A mnemonic indicates no errors

detected in DSH32-A subsystem. Replace the DSH32-B communications
module or the distribution board if any other code is listed.

2.18.1 Additional DSH32-A information
Install a H3101 36-pin loopback on the eight-asynchronrous port when
running the tests in Field Service mode on the DSH32-B communications
module, distribution board, and internal cabling.

Install the loopback on the end of the agsynchronous cable when running
tests in Field Service mode on the cable.
Install the MMJ loopbacks in one or more of the MMJ ports on the
cable concentrator when running tests in Field Service mode on that
attachment.

The loopback connectors are not needed during customer mode testing
because the DSH32-A uses internal loopback switches for transmission
testing.

During Field Service mode testing, the asynchronous line drivers are fully
tested. Characters are sent out to the each asynchronous line. They are
verified as they are looped back into the port’s receiver. If a loopback
connector is not installed or the wrong character is received, an error code
is listed in the DSH32-A code for that port.
2.18.1.1 Self-Test Codes Explained

Enter TEST 4 to run the self-test on the DSH32-A subsystem. When the
test has completed, enter TEST 50 to view the configuration display.
Figure 2-18 shows an example of the DSH32-A information in the
configuration display.

2-36

Troubleshooting

Figure 2-18

DSH32~A

Configuration Display DSH32-A Information

00FF.0001 V2.0

@ The device identifier, in this case, the DSH32-A subsystem.
@ A bitmap, in hexadecimal, that indicates which of the asynchronous
lines are working. See Figure 2-20.

@ A device error code.

@ The revision level of the device.
Figure 2-19 shows a typical error code for DSH32-A in the configuration

display.

Figure 2-19

Configuration Display DSH32-A Error Code Example 2

DSH32-A

00B7.00A0 V2.0

To determine which asynchronous lines are working, convert B7 into
binary format, giving 10110111. Therefore asynchronous lines 7, 5, 4, 2, 1,
and 0 are operating normally, while lines 6 and 3 are faulty, as indicated
in Figure 2-20.

Troubleshooting

Figure 2-20

2-37

Error Code Format for the DSH32-A Subsystem

Fro g o
19

(000000011‘

1] 1

(o Lo ERROR
ol RESERVED -ofo———"
BIT MAP —————o
FELW

4232

HGHIGHITS

* 1 = LINE IS WORKING
0 = ERROR DETECTED ONLINE

suhmunien
st
i
Bt
15 14 1

1110 9

ooooooooo

fo————

5.4
3 2 1.0

ooo|0]01LOW1ems

3 DIGITHEXERROR
CODE -———ef FESERVED] *

* 1= SUCCESSFUL

0 = FATAL ERROR

MOTE: UNUSED BITS ARE ALWAYS 0

See Appendix E for a complete list of the power-up and self-test error
codes.
2.18.1.2 System Exerciser Codes Explained
Run the system exerciser on the DSH32-A subsystem only. Figure 2-21
shows the command to do this.
Figure 2-21

>>> TEST

Running theSvetem Exarclser on the DSH32-A Subsystem

80000106

2>>> 4
Figure 2-22 shows an example of the DSH32-A information in the system
exerciser display.

Troubleshooting

2-38

Figure 2-22

B1FO

System Exerciser DSH32-A Information

DSH32-A

00FF.0001 @
@ o0001.0001 @

0 00:04:54

8 0001.0001 8
0001.0001

0001.0001 @

Status code and error code for the DSH32-A subsystem.
Status for line 1.
Status for line 0.
Status for line 3.

Status for line 2.
Status for line 5.
Status for line 4.

Status for line 7.
Status for line 6.

The normal status code and error code for the DSH32-A subsystem is
00FF.0001. The normal status code for each line is 0001. Any other codes
displayed indicate an error.
Figure 2-23 shows a typical error code for DSH32-A in the system
exerciser display.

Figure 2-23

81FO

System Exerciser DSH32-A Error Code Exampie

DSH32-A

007F.0321

00:04:54

0001.0001

0001.0001
0001.0001
0321.0001

In this example, line 7 displays an error code because data was lost on
that line. The code 007F.0321, which indicates the overall status of the
DSH32-A subsystem, shows that line 7 was dropped by displaying 7F.

(Section 2.18.1.1 describes how to decipher this bitmap.) The code 0321

Troubleshooting

2-39

on the first line shows that the error was the last error detected. The
status code for each line holds the error code for that line's failure or
success.

See Appendix F for a complete list of the system exerciser error codes.

2.19

TEST 3 — DSH32-B Synchronous Subsystem
(DSH32-S)

The DSH32-S subsystem controls the synchronous communications port
on the rear of the system unit. The DSH32-S subsystem synchronous
line driver is located on the distribution board and is controlled from the
DSH32-B communications module.

Self-test and the system exerciser are used to troubleshoot the DSH32-S
subsystem. Enter TEST 3 to run the self-test. Then enter TEST 50 to
see the results. Enter TEST 80000106 and and press RETURN, then
enter 3 in response to the ?>>> prompt to raun the Field Service system
exerciser on the DSH32-S subsystem only. Figure 2-24 shows an example
of running the system exerciser on the DSH32-S subsystem.
Figure 2-24

>>> TEST

Running the System Exerciser on the DSH32-S Subsystem

80000106

>>> 3

A code of 0000.0001 next to the DSH32-S mnemonic indicates no errors
detected in DSH32-S subsystem. Replace the DSH32-B communications
module or the distribution board if any other code is listed.

2.19.1

Additional DSH32-S Information

Install a H3199 50-pin loopback on the synchronous port when running

the tests in Field Service mode on the DSH32-B communications module,
distribution board, and internal cabling.
Install the loopback on the end of the synchronous cable when running
tests in Field Service mode on that cable. Disconnect the cable from the
modem or host computer and install either the H3248 25-pin loopback or
the H3198 37-pin loopback on that end of the cable. The H3248 loopback
is used when a RS232 cable is connected to the system. The H3198
loopback is used when 2 RS422 or RS423 cable is connected to the system.

The loopback connectors are not needed during customer mode testing
because the DSH32-A uses internal loopback switches for transmission
testing.

2-40

Troubleshooting

= mode testing, the synchronous line driver is fully
During Field Ser
tested. Character. :. sent out to the synchronous line. They are verified
as they are looped bacs into the port’s receiver. If a loopback connector is
not installed or the wrong character is received, an error code is listed in
the DSH32-A code for that port.
2.19.1.1 Seif-Test Codes Explained

Enter TEST 3 to run the self-test on the DSH32-S subsystem. When the
test has completed, enter TEST 50 to view the configuration display.
Figure 2-25 shows an example of the DSH32-A information in the
configuration display.

Figure 2-25

DSH32-S

Configuration Display DSH32-S information

0000.0001

V2.0

@ The device identifier, in this case, the DSH32-S subsystem.
@ The four digits to the left of the period indicate the test number.
@ The four digits to the right of the period indicate the fault code.

@ The revision level of the device.
See Appendix E for a complete list of the power-up and self-test error
codes.
2.19.1.2 System Exerciser Codes Explained

Run the system exerciser on the DSH32-S subsystem only. Figure 2-26
shows the command to do this.
Figure 2-26

>>> TEST

Running the System Exerciser on the DSH32-S Subsystem

80000106

2>>> 3 [ReTurr]
Figure 2-27 shows an example of the DSH32-S information in the system
exerciser display.

Troubleshooting

Figure 2-27

81F1

2-41

System Exerciser DSH32-S Information

DSH32-S

0001.0000 @
0000.0001 @

0 00:04:54

@ A common module information line holding either the status code and
error code for the DSH32-S subsystem or the operating status of the
synchronous line.

@ Status for synchronous port 1.
If the first digit of the common module information line is 0, the operating
status of the synchronous line is displayed. The four digits to the left of
the period are a bitmap indicating which of the synchronous lines are
operating. The four digits to the right are a bitmap indicating those lines
that are not operating. Since the DSH32-B communications module in the
MicroVAX 3100 and VAXserver 3100 support only one synchronous line,
these bitmaps can either be 0001 or 0000. Figure 2-28 and Figure 2-29
show how the system can display these error codes.
Flgure 2-28

81F1

Figure 2-29

81F1

System Exerciser DSH32-S Example 1

DSH32-S

0001.0000 @

0 20:04:54

System Exerciser DSH32-S Example 2

DSH32-S

0000.0001 @

0 00:04:54

@ 1n this example the bitmap representing synchronous port 1 is to the
left of the period and therefore port 1 is operating normally.

@ In this example the bitmap representing synchronous port 1 is to the
right of the period and port 1 is faulty.

If the first digit of the common module information line is not zero, a
status code and error code for the DSH32-S subsystem is displayed. The
four digits to the left of the period indicate the status code. The four
digits to the right of the period indicate the error code.

Troubleshooting

2-42

Figure 2-30 shows a typical status code error code for DSH32-S in the
system exerciser display.
Figure 2-30

System Exerciser DSH32-S Status Code and Error Code
Example

?2?

81F1

DSH32-S

1100.7C1C

0 00:34:54

0000.0001

The second line of the display indicates the status of synchronous port 1.
A status code of 0000.0001 indicates that tte port is operating normally.
Any other code indicates an error on the synchronous port. As you can see
from the previous example, the synchronous port may display a normal
status code even though an error code is displayed for the DSH32-S
subsystem.

See Appendix F for a complete list of the system exerciser error codes.

2.20

General DSH32-B Communications Module
Troubleshooting

The procedures listed in this section describe how to correct errors
detected while running either the self-tests or the system exerciser on
the DSH32-A and DSH32-S subsystems.

2.20.1

Seli-Test Errors

Run the self-tests on both the DSH32-A and DSH32-S subsystems in Field
Service mode. Enter TEST 50 to display the results. Any seli-test error
code other than 00FF.0001 indicav°s a fault in the DSH32-A subsystem.
An error code other than 0003 0001 indicates a fault in the DSH32-8
subsystem. In either case fix the problem by replacing the fcllowing FRUs
in the order listed:
1.

Replace the DSH32-B communications module and run the self-test
on both the DSH32-A and DSH32-S subsystems again.

If replacing the DSH32-B communications module did not fix the
problem, replace the distribution board. Run the self-tests again.

ifthe error is still disp.ayed, replace the cable between the DSH32-B
communications module and the distribution board.

Troubleshooting

2-43

If the error is still displayed on the DSH32-A subsystem and you are
running the self-tests with the asynchronous cable, cable concentrator,
and loopbacks connected to the system unit, replace the following
items in the order listed:

Replace the asynchronous cable. Run the self-test again.

If the error is still displayed, replace the cable concentrator.
NOTE

The self-tests provide the most complete testing of the DSH32S subsystem. Self-tests support the use of the H3248 and H3198
cable loopbacks while the system exerciser supports only the
H3199 80-pin loopback.

If the error is still displayed on the DSH32-S subsystem and you
are running the self-tests with the synchronous cable and either the
H3248 or H3198 loopback connected to the system unit, replace the
synchronous cable.

2.20.2 System Exerciser Errors
The DSH32-A and DSH32-S system exercisers are explained in the
following sections.

2.20.2.1 DSH32-A System Exerciser

Any error code in the system exerciser other than 00FF.0001 indicates a
fault in the DSH32-A subsystem. The following procedure describes how
to correct errors discovered in both the Customer and Field service mode
system exerciser display:
1.

If you are testing the DSH32-A subsystem in Customer mode, and
the error code is not 00FF.0001, replace the DSH32-B communications
module.

1If the DSH32-A subsystem passes the self-test but fails the Field
Service mode system exerciser, replace the distribution board.

2.20.2.2 DSH32-S System Exerciser

Use the system exerciser to isolate intermittent hardware faults.
A fault is indicated in the DSH32-S subsystem when two question marks
appears to the left of the DSH32-S mnemonic on the first or first and
second line of the DSH32-S display. The following procedure describes
how to correct errors discovered in both the Customer and Field service
mode system exerciser display:

2-44

Troubleshooting

If two question marks appear on both the first and second line in the
display, the error is on the DSH32-B communications module or in the
synchronous port on the distribution board.
Replace the distribution board. Run the system exerciser again.

If the exror still appears, then the error is on the DSH32-B
cormunications module and that module should be replaced.

NOTE
The systeTMm exerciser tests do not support testing with the H3248

or H3198 loopbkack connector installed.

2.21

TEST 1 — NI — Ethernet Network

The Ethernet network (NI) circuits control the communication protesol
over the ThinWire or standard Ethernet cables. The system contains
a ThinWire Ethernet port and a standard Ethernet port on the back of
the system box. A switch determines which Ethernet port is enabled
for transmission of IEEE 803.2 protocol and an LED lights next to the
enabled port.
A code of 0000.0001 (self-test) next to the NI mnemonic indicates no
errors detected with the Ethernet circuits. If an error code of xxxx.7001
or higher for ThinWire Ethernet or 0011.700E for standard Ethernet is
listed, check the termination of the enabled Ethernet port on tlie back
of the system box and retest. These two codes indicate that the external
isthernet network cable is not terminated correctly (for instance, no
loopback on the enabled port). A code of 0100.0001 is normal with the
standard Ethernet port enabled until the external Ethernet network is
nuerational. Be sure to set the Ethernet switch to snable the correct
tithernet port. Replace the system module if any other code is listed.
A code of 0000.0001 (system exerciser) next to the NI mnemonic indicates
no errors detected with the Ethernet circuits. Replace the system module
if any other code is listed.

Troubleshooting

2-45

2.21.1 Additional Ni Information
When running self-test on the NI circuits, the Ethernet connector on
the back of the system box must be terminated correctly. If an Ethernet
cable is connected to the enabled Ethernet port, it must be terminated
correctly. If no cable is connected to the enabled Ethernet port, put
together a loopback connector. Table 2-15 lists the parts that must be
assembled. Connect the loopback to the enabled port before running
self-test. If the enabled Ethernet port is not terminated correctly, the
NI self-test will detect an error of 0000.7001 or higher for the ThinWire
port and 0011.700E for the standard Ethernet port. These termination
error codes indicate a possible problem with the Ethernet cable and not
necessarily the Ethernet circuits on the system module. If an error still
shows up after replacing the system module and verifying the Ethernet
cable, replace the power supply. Since the 9 Vdc supply is only used by

the Ethernet circuits, a problem with this supply would not cause an error
code to appear during the testing of any other device.
See Appendix E for a complete list of the power-up and self-test error
codes. See Appendix F for a complete listing of the system exerciser error
codes.
Table 2-15

Ethernet Port Loopback Connectors
Part

Item

Number

Number of Parts Needed

Standard Ethernet Loopback
Connector terminator

12-22196-01

T-connector

12-25869-01

50 ohm terminator

12-26318-01

ThinWire Ethernet Loopback

If power-up testing detects an error with the Ethernet circuits, the SET
MOP, SHOW MOP, SET TRIG, SHOW TRIG, and SET PSWD commands
may not be usable. An error message when entering these commands
indicates this. To reenable these commands, you must fix the error on
the Ethernet circuits. If the NI error was an unterminated Ethernet port,
then you must terminate the port correctly and run TEST 1. Assuming
the test passed this time, enter UNJAM at the console prompt (>>>). This
command must be entered to reenable the SET and SHOW commands.

2-46

2.22

Troubleshooting

Power Supply Troubleshooting Procedures

Figure 2-31 shows the flowchart that must be followed if a problem with
the power supply exists.
Figure 2-21

Flowchart for Troubleshooting the Power Supply

Is power

present at

Call an Electrician.

outlet?

Is power

Piug in power cord.

cord plugged
in?

Switch on powaer switch.

Is the

green LED on

the front of tha

Replace pawer supply

system box
lit?

Check the voltages listed
in Tables 2-16 and 2-17.

‘

&
MLO-0026849

Figure 2-32 identifies the power connector pins on the system module.
Table 2-16 lists the voltages on the respective pins.

Troubleshooting

Figure 2-32

2-47

Power Connector Pin Voltages on the System Module

MLO-002945

Table 2-16
Pin Number

System Module Power Connector Voltages
Voltage

Tolerance

- 12.1 Vde

Ground

RS S

Ground
Ground

+ 5.1 Vde

+ 5.1 Vdc

[{-TE. I

+ 12.1 Vde

+ 5.1 Vde

Ground

+ 5.1 Vdc

+ 3.5 to + 5.25 Vdc

2-48

Troubleshooting

Table 2-16 (Cont.)

System Module Power Connector Voltages

Pin Number

Voltage

Tolerance

-9 Vdc!

- 9 Vde return?

—

'Measurement made with negative lead connected to pin 14

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

Figure 2-33 identifies the drive power connector pins. Table 2-17 lists

the voltages on the respective pins.

Figure 2-33

Drive Power Connector Pin Voitages.

Pin 4 (Red Cable)

Pin 3 (Black Cable)

Pin 2 (Black Cable)
Pin 1 (Orange Cable)

{8009}
O

MLO-002088

Table 2-17

Drive Power Connector Voltages

Pin Number

Voltage

Tolerance

+ 12.1 Vdc

Ground

—

Ground

+ 5.1 Vde

3
Utilities
The utilities help the user view diagnostics, set default and restart flags,
as well as other functions. Table 3~1 describes and lists the console mode
TEST (T) commands that invoke the utilities.

Each utility is available on the MicroVAX 3100 and the VAXserver 3100
Model 10 and Model 20 systems.
Table .1

Utllities

Test Number or
Command

Utility Invoked

T 50

Configuration table (also displays the Ethernet hardware

T 51

Set NVR default boot device.

T 52

Sei NVR default boot flags.

T 53

Set NVR default recovery action flags.

T 73

address, for example, ID 08-00-2B-03-79-1F).

Special key on tapes for Field Service mode system
exerciser.

T 74

Special key on diskettes for Field Service mode system
exerciser.

T75

SCSI disk dAnta era<er

T 76

Mass Storage Lnskette Formatter.

SHOW DEVICE

Display all devices connected to the SCSI bus

SHOW ESTAT

Show extended summaries of the system exerciser tests.

controllers.

3-2

Utilities

Table 3-1 (Cont.)

Utilitles

Test Number or

Command

Utility Invoked

SHOW VER

Determine the revision level of the system module’s
ROM.

3.1

Configuration Table (T 50)

The configuration table lists the status/errer of each device installed in

the system. This configuration table holds the results of the self-test
and power-up tests and is updated each time self-test is run. Figure 3-1
shows an example of a configuration table.
See Appendix E for a complete list of the power-up and self-test error
codes.
NOTE
Remember that the configuration table contains the results of
the self-test and power-up tests and not the results of the system
exerciser.

Utilities

Figure 3-1
>>> TEST

3-3

Example of the Configuration Table

KA41-A V1.3
ID

08-00-2B-02-CF-~A4

CLK

0000.0001

NVR

0000.0001

0000.0001
00000001

MEM

00000001

00000000

00000001

FFFFFF05

FFFFFFO0S

FFFFFFO3,

00000001

FFFFFFO0S

FFFFFF05

FFFFFFO3.

0004.0001

00400000
MM

0000.0001

0000.C001

SCSI-A

FFFFFFOS
SCSI-B

FFFFFF05

7717.0001

FFFFFF05S
1C1C. 0001

FFFFFF05

SYS

0000.0601

V1.0
FFFFFF0S

V1.0
00000001

DSH3Z-A

QO0FF
. 0001

ve. 0

DSH32-8

0000.0001

V2. 0

0000.0001

>>>

\Utilities

The first line contains the CPU and the ROM version (KA41-A V1.3).
The second line contains the Ethernet hardware address (in this example
it is ID 08-00-2B-02-CF-A4). The rest of the display contains the status
/error codes for the devices installed on the system. The configuration
table is built during power-up testing and the codes are the result of the
self-test and power-up tests. This configuration table is the only place the
results of self-test are indicated. It is updated every time you run selftest. Additional codes on the DZ, MEM, SCSI-A, and SCSI-B give a more
detailed status on these devices and are listed in the following section.

3.1.1 DZ Exolanation in Configuration Table
The DZ has six 8-digit numbers that contain the status of the four serial
lines. Any 8-digit number other than 00000001 for the four serial lines
indicates a failure on that line. The fifth and sixth numbers have the
number 00000000 and are unused.

Figure 3-2 shows what each 8-digit number represents.
Figure 3-2

Example of the DZ Line in the Configuration Tabie

0000.0061

00000001

MMJ port 1 (DEC423)

MMJ port 2 (DEC423)
Modem (RS232 Serial line port)

MMdJ port 3 (DEC423)
Unused

Unused

00000000 00000000

Utilities

3-5

3.1.2 MEM Explanation in Configuration Table
The Configuration display provides additional information about the
memory in the system. Figure 3-3 shows an example of the MEM
information in the configuration display.

Figure 3-3

MEM

Configuration Display MEM Information

0004.0020

00400000 00000003

@ The first four digits indicate the amount of memory available if no

errors are detected. The second four digits contain a status code for
the memory.

@ This code repeats the amount of memory in the system. Table 3-2

’

explains the codes.

@ This code contains the location of the failed memory. It is displayed
only if an error is detected.

Table 3-2
Codes

Hexadecimal Memory Codes
Mb of Memory

00400000

4Mb

00800000

8Mb

01000000

16Mb

01400600

20Mb

01800000

24Mb

0100000

28Mb

02000000

32Mb

If the 8-digit error code, @, appears, there is an error in one or more of
the memory modules. A code other than 0 in any of the digits indicates
& faulty module. The module indicated by that digit depends on the
configuration as shown in Table 3-3.

3-6

Utilities

Table 3-3

Locating a Falled Memory Bank
8-Digit Error Code for MEM

Installed Memory

System module

4Mb module

12Mb module

]

16Mb module

4Mb and 16Mb
modules

12Mb and 16Mb

168

modules

S—Represents the system module
4—Represents the 4Mb memory module
12-~Represents the 12Mb memory module
16~ Represents the 16Mb memory module

Figure 3—4 shows a typical error code for MEM in the configuration

display.
Figure 3-4

Configuration Dispiay MEM Error Code Example 1

HMEM

0020.0020
02000000

10002000

In this example, digits 1 and 5 of the error code are not zero. The system
has 32Mb of memory, therefore the 12Mb and 16Mb memory modules are
installed. Table 3-3 indicates that when the 12Mb aud 16Mb modules
are installed, digits 1 and 5 indicate errors on the 16Mb module and the
12Mb module respectively.
Figure 3-5 shows another MEM error code example.

Utilities

Figure 3-5

MEM

3-7

Configuration Display MEM Error Code Example 2

0020.0020
01000000 ©0003003

In this example, digits 5 and 8 of the error code are not zero. The system
has 16Mb of memory, therefore the 12Mb memory module is installed.
Table 3-3 indicates that when only the 12Mb module is installed, digits
5 and 8 indicate errors on the 12Mb module and the system module
respectively.
A code other than zero in digit 8 always indicates an error in the system
module memory.
L. 2 Appendix E for a complete list of the power-up and self-test error
codes. See Appendix F for a complete list of the system exerciser error

codes.

3.1.3 SCSI Bus Explanation (SCSi-A and SCSI-B) in the
Configuration Table
The SCSI bus device displays eight 8-digit numbers. See Figure 3-6.
Each of the 8-digit numbers contain the status of a device at a particular
SCSI address on the SCSI bus. To determine what a drive’s code
indicates, see the troubleshooting section for that drive.

3-8

Utilities

Figure 3—6 sho'ws the address ID locations for the six possible drives on
an SCSI bus.

Figure 3-6

SCSI Bus Lines in the Configuration Table

SCSI-A

7711.0001

V1.0

SCSI-B

1C1c.0001

V1.0

FFFFFF05 FFFFFF05 FFFFFF05 00000001 FFFFFF0S 00000001 FFFFFFO03 FFFFFFOS

FFFFFF05 FFFFFF05 00000001 00000001 FFFFFFO0S FFFFFFOS FFFFFF03 FFFFFFOS

SCSI address ID 0
SCSI address ID 1

SCSI address ID 2
SCSI address ID 3

SCSI address ID 4
SCSI address ID 5

SCSI address ID 6
SCSI address ID 7
3.1.3.1 SCSI Address ID Assignments

Each device on the SCSI bus, including the SCSI bus controller, has
its own address 1D location. The SCSI bus controller always holds the
address ID of 6 for 1 buses. Refer to Table 3-4 to determine the default
address ID assignments for both SCSI buses.

Utilities

Table 3-4

3-9

MicroVAX 3100 Family SCSI Bus ID Assignments

IDs

SCSI-A Bus

IDs

SCSI-B Bus

Unused

Reserved for expansion

SCS.-A bus controller

SCSI-B bus controller

TZ30, RX23, RZ23

TK50Z expansion box

Unused

RRD40 expansion box

RZ23 (system disk)

RZ23

Unused

RZ23

Unused

RZ55 expansion box

Unused

RZ23 or RX23

NOTE
Model 10 systems do not contain as many internal storage devices
as Model 20 systems; however, both systems use the same SCSI ID
assignments, as listed in Table 3-4. InfoServer 100 systems have
different SCSI A bus assignments. The system disk, RZ23E or
RZ23L, MUST be ID 1 and the internal RRD40 or RRD42 compact
disk drive on SCSI-A bus MUST be ID 2. InfoServer 100 systems
do not support the TZ30 or the RX23,

3.1.4 DSH32-A Explanation in the Configuration Table
Figure 3-7 shows an example of the DSH22-A information in the
configuration display.

Figure 3-7

DSH2Z2-A

Configuration Display DSH32-A Information

00FF.0001

V2.0

@ The device identifier, in this case, the DSH32-A subsystem.

@ A bitmap, in hexadecimal, that indicates which of the asyrchronous
lines are working. See Figure 3-8.

@ A device error code.

Uilities

3-10

€@ The revision level of the device.

Figure 3-8

[
31

Error Code Format for the DSH32-A Subsystem

O T

20 28 27

22 21

OIOIOIO ojojojogvir1l

F 1]

HGHISBITS

19 18 17 18

o-LINE ERROR-se RESERVED ftm—mmeme’ BIT MAP oo

FIELD

5 43 2

* 1 = LINE 15 WORKING
0 = ERROR DETECTED ON LINE

r—-—o—-—aio—o——-r-——o——.r—1—-—.|
514

13 12 11 10

9 8

o—— HEX

ololo'oloLolo[olo_[olofo olofo]1 ] towsears
3 DIGIT HEX ERROR
CODE —————s{RESERVED] *

* 1 =SUCCESSFUL

0= FATAL ERROR

NOTE: UNUGED BITS ARE ALWAYS 0

Figure 3-9 shows a typical error code for DSH32-A in the configuration
display.
Figure 3-9

DSH32-A

Configuiation Display DSH32-A Error Code Example 2

0O0B7.00A0 V2.0

To determine which asynchronous lines are working, convert B7 into
bir:ary format, giving 10110111. This indicates that asynchronous lines 7,
5, 4, 2, 1, and 0 are operating normally, while lines 6 and 3 are faulty, as
shown in Figure 3-8.

Utilities

3.2

3-11

Setting NVR Default Boot Device (T 51)

Enter TEST 51 (a utility) or SET BOOT (a command) to set the boot
device. Both methods set the default boot device in the NVR.
Figure 3-10 shows an example of changing the default boot device from
four periods .... (no default device stored in the NVR), which indicates
that ESA0 would be the boot device, to the system disk, DKA300 (an
RZ23 in the system box).
Figure 3-10

Example of Changing the Default Boot Device

>>> TEST 51

....

>>> DKA300

>>>

OR
>>>

SET BOOT DKA300

>>>

Press RETURN to exit TEST 51 without changing the default boot device.
Enter a period (.) to clear the default boot device from NVR. Enter the
device, such as DKA300, to set the default boot device to that device.
There are several boot device names to choose from. Table 3-5 lists the
boot device names and the devices they represent.

Lilities

3-12

Table 3-5

Boot Device Names

B st Device

Device Type

Explai:ation

DKAx00

Hard disk

RZ23 on SCSI-A bus at address ID x.

DKBx00

Hard disk

RZ23, or RZ55 on SCSI-B bus at address

MKAx00

Tape drive

TZ30 on SCSI-A bus at address ID x.

MKBx00

Tape drive

TK50Z on SCSI-B bus at address 1D x.

DUAx

Diskette drive

RX23 on SCS:-A bus at address 1D x

ESA0

Ethernet
network

System boots off another node.

3.3

ID x.

Setting NVR Default Boot Flags (T 52)

Enter TEST 52 (a utility) or SET BFLG (a command) to set the boot flags.
Both methods set the default boot flags in the NVR. Table 3-6 lists the
boot flags that the ULTRIX operating system uses. Table 3-7 lists the

boot flags that the VMS operating system uses. Figure 3-11 shows an
example of changing the default boot flag from 00000000 to 00000010

(diagnostic boot). Press RETURN to exit TEST 52 without changing the
default boot flag.
Figure 3—11

>>> TEST

Example of Changing the Default Boot Flag

00000000

>>>

00000N10

SET

00000010

OR
>>>

BFLG

>>>

It is possible to specify one or any combination of boot flags in the NVR.
Enter the sum value (in hexadecimal) of the flags that you want loaded
into the NVR. For example, to specify the RPB$V_DIAG flag, RPB$V_
HALT flag, and the RPB$V_MPM flag, add all three flags, and enter the
sum into NVR. Figure 3-12 shows this example.

Utilities

Figure 3-12

Determining the NVR Code for Three Boot Flags

RPBSV DIAG

=---

00000010

RPBSV_HALT

~---

00000200

RPBSV

---

MPM

00000800
——

Enter this

code

————

O0O0Q00AlO

Tabie 3-6 Boot Flags Used by ULTRIX
Flag

Definition

00000001

RPB$V_CONV —- Conversational boot. This wili force

00000102

3-13

00000004

ULTRIXBOOT to prompt the user for an image name. This
allows the user to specify an image name that is different from
the default ‘Ymunix’. If the DIAG is also on, then the user is
prompted for the diagnostic supervisor image name.

RPB$V_DEBUG — If this flag is set, the ULTRIX kernal image

is booted to single-user mode.

RPB$V_INIBPT — Initial breakpoint. If RPB$V_DEBUG is
set, ULTRIX executes a BPT instruction immediately after

enabling mapping.

00000008

RPB$V_BBLOCK — Secondary boot from boot block. Secondary
bootstrap is a single 512 byte Llock, whose LBN is specified in
R4. R4 must be 0 for ULTRIX.

00000010

RPB$V_DIAG — Diagnostic boot. This causes ULTRIXBOOT
to load the appropriate diagnostic superviser by CPU type. The
default path is /field/e?saa.exe, where the partition is specified

in bits 31:28 of this register.

00000020

RPB$V_BQOBPT -- Bootstrap breakpoint. Stops the primary
and secondary bootstraps with a breakpoint instruction before
testing memory.

00000040

00000080

RPB$V_HEADER -— image header. Takes the transfer address

of the secondary bootstrap image from that file’s image header.
If RPB$V_HEADER is not set, transfers control to the first byte
of the secondary boot file.

RPB$V_NOTEST — Memory test inhibit. Sets a bit in the PFN

bit map for each page of memory present. Does not test the
memory.

3-14

Utilities

Table 3-6 (Cont.)

Boot Flags Used by ULTRIX

Flag

Definition

00000100

RPB$V_SOLICT - File name. Prompt for the neme of a

00006200

secondary bootstrap file.

RPB$V_HALT — Halt before transfer. Executes a halt

instruction before transferring control to the secondary
bootstrap.

00000400

00000800

RPB$V_NOPFND — No PFN deletion (not implemented;

intended to tell VMB not to read a file from the boot device that
identifies bad or reserved memory pages, so that VMB does not
mark these pages as valid in the PFN bitmap).
RPB$V_MPM — Specifies that multiport memory is to be used
for the total exec memory requirement. No local memory is to
be used. This is for tightly-coupled multiprocessing.

00001000

RPB$V_USEMPM — Specifies that multiport memory should

be used in addition to local memory, as though both were one
single pool of pages.

00002000

RPB$V_MEMTEST — Specifies that a more extensive
algorithm be used when testing main memory for hardware
nonrecoverable (RDS) errors.

00004000

RPB$V_FINDMEM -— Requests use of MA78¢ memory if
MS780 is insufficient for booting. Used for 11/782 installations.

00008000

RPB$V_AUTOTEST -- Used by diagnostic supervisor.

00010000

RPB$V_CRDTEST — Request pages with CRD errors are not

X00060000

RPB$V_TOPSYS — Redefines the default load file system

to be removed from bitmap.

Y (Y1 O
T
N

TR e QA0 TP

Ne WO
N

partition. This field is used primarily with DIAG. The following
corresponding partition numbers and letters are:

Utilities

Table 3-7

3-15

Boot Flags Used by VMS

Flag

Definition

00000001

RPB$V_CONV
— Conversational boot. At various points in the

system boot procedure, the bootstrap code solicits parameters
and other input from the console terminal. If the DIAG is also
on, the diagnostic supervisor then enters MENU mode and
prompts the user for devices to test.
00000002

RPB$V_DEBUG - Debug. If this flag is set, VMS maps the

code for the XDELTA debugger into the system page tables of
the running system.

00000004

RPB$V_INIBPT — Initial breakpoint. If RPFB$V_DEBUG

is set, VMS exccuies a BPT instruction immediately after
enabling mapping.
00000008

RPB$V_BBLOCK — This skips the files-11 boot and performs
only the boot block type boot.

00000010
00000020

RPB$V_DIAG — Diagnostic boot. Secondary bootstrap is image
called [SYSMAINT|DIAGBOOT.EXE.

RPB$V_BOOBPT — Bootstrap breakpoint. Stops the primary

and secondary bootstraps with a breakpoint instruction before
testing memory.

00000040

RPB$V_HEADER — Image header. Takes the transfer address
of the secondary bootsirap image from that file’s image header.
If RPB$V_HEADER is not set, transfers control to the first byte
of the secondary boot file.

00000080

RPB$V_NOTEST — Memiory test inhibit. Sets a bit in the PFN
bit map for each page of memory present. Does not test the
memory.

00000100

RPB$V_SOLICT — File name. Prompt for the name of a
secondary bootstrap file.

00000200

RPB$V_HALT — Halt before transfer. Executes a halt

instruction before transferring control to the secondary
bootstrap.
00000400

RPB$V_NOPFND — No PFN deletion (not implemented;
intended to tell VMB not to read a file from the boot device that
identifies bad or reserved memory pages, so that VMB does not
mark these pages as valid in the PFN bitmap).

Utilities

3-16

Table 3-7 (Comt.)

Boot Flags Used by VMS

Flag

Definition

00000800

RPB$V_MPM — Specifies that multiport memory is to be
used for the total exec memory requirement. No local memory
is to be used. This is for tightly-coupled multiprocessing. If

the DIAG is also on, then the diagnostic superviscr enters
AUTOTEST mode.

00001000

RPB$V_PFILE — (overlays RPB$V_USEMPM) File name.
Prompt for the name of the parameters file on a network

bootstrap operation.

00002000

RPB$V_MEMTEST — Specifies that a more extensive

algorithm be used when testing main memory for hardware
nonrecoverable (RDS) errors.

00004000

RPB$V_FINDMEM — Requests use of MA780 memory if

00008000

RPB$V_AUTOTEST — Used by diagnostic supervisor.

00010000

RPB$V_CRDTEST — Request pages with CRD errors to be

MS780 is insufficient for booting. Used for 11/782 installations.

removed from bitmap.

X0000000

3.4

RPB$V_TOPSYS — The X position specifies the top level
directory number for system disks with multiple systems.

Setting the NVR Default Recovery Action Flags

(T 53)
Enter TEST 53 (a utility) or SET HALT (a command) to set the recovery
action flag. Both methods set the default recovery action in the NVR. The
default recovery action flag is used by the system during ;ower up and
also if the system detects a severe error in its operating environment.
There are three flags to choose from: restart, boot, or halt.
©

Restart searches for the restart parameter block (RPB) in memory
(the RPB contains addresses of certain registers that hold restart
information).

Boo* starts booting the operating system software.

Halt automatically halts the system and enters console mode.

Utilities

3-17

Table 3-8 lists the recovery flags available.
Table 3-8

Default Recovery Flags

Number

Recovery Action Flag
Restart

Boot

Halt

Figure 3-13 shows an example of changing the flag from 2 (boot) to 3
(halt). Press RETURN to exit TEST 53 without changing the flag.
Figure 3-13

Example of Changing the NVR Recovery Action Flags

>>> TEST 53
2

>>>

OR
>>>
>>>

SET HALT

3-18

Utilities

3.5 Tape Cartridge Special Diagnostic Key for Field
Service System Exerciser (T 73)
The tape cartridge in the maintenance kit must have a special diagnostic
code written on it that allows the system exerciser to write on this media
when running in Field Service mode. Normal customer media does not
have the diagnostic key and the system exerciser does not perform write
testing on the removable media devices. This safety feature protects the
customer’s programmed tapes.

TEST 73 is the utility that creates the special key on the tape. The tape
in the maintenance kit must be initialized with these special diagnostic
keys before they can be used. It must be initialized every time you use
it with the Field Service mode system exerciser, because the special
diagnostic key on the tape is destroyed once the exerciser recognizes the
key.

Figure 3-14 shows an example of successfully creating a special-key tape
cartridge. If any errors occur while running TEST 73, make sure the
drive is on-line and operating correctly and run the special-key command
again. Also, make sure the tape is not write-protected.
Figure 3-14

>>> TEST

Example of Creating the Special Key on a Tape Cartridge

73
KA41-A

VStmk
QUE port (A,B)

TPwrker

? A

VStmk_QUE
id (C,1,2,3,4,5,6,7)
VStmk
QUE RUsure (1/0)

7 1

VSEMK o vvennnnns OK
>>>

@ Enter port addvess.

@ Enter ID address of drive.
@

Enter 1 for yes, 0 for no.

@ Keyed successfully.

@
285

@
0

Litilities

3-19

3.6 Diskette Special Diagnostic Key for Field
Service System Exerciser (T 74)
The diskette in the maintenance kit must have a special diagnostic code
written on it that allows the system exerciser to write on this media
when running in Field Service mode. Without this special key, such as on
normal customer media, the system exerciser does not do write testing on
the removable media devices. This safety feature prevents accidentally
destroying the customers p. ogrammed diskettes.
T 74 is the utility that creates the special key on the diskette. The
diskette in the maintenance kit must be initialized with these special
diagnostic keys before they can be used. The special diagnostic key is not
destroyed when the diskette is used.
Figure 3-15

Example of Creating the Special Key on a Diskette

>>> T 74

KA4l

FLiker

VSflmk_QUEport (A,B) ? A

vsflmk_QUE_id (0,1,2,3,4,5,6,7) 2 5

VSflmk que_rusure (1/0)

? 1

VSEIMK. .o vvrnnnn. OK

>>>

@ Enter port A or B.
@ Enter ID of the drive.

@ Enter 1 for yes, 0 for no.
@ Keyed successfully.
Figure 3—15 shows an example of successfully creating a special-key
diskette. If any errors occur while running T 74, make sure the drive is

on-line and operating correctly and run the special-key command again.
Also, make sure the diskette is not write-protected.

3-20

Utilities

3.7

SCSI Mass Storage Disk Data Eraser (T 75)

This utility erases the data on a drive on one of the SCSI buses. Enter T
75 ¢o start the data eraser. Figure 3-16 shows an example of running the
data eraser on the drive located at SCSI address ID 1 on the SCSI-B bus.
CAUTION
This utility destroys all user data on the drive.
Figure 3-16
>»>

Example of Erasing Data on an RZ55

T 18

ScsHDerase

PV_SCs_FMT
_CHN
PV_SCS
FMT ID
PV

SCS

PV_SCS

(0=SCSIA

1=SCSIB)?

(0,1,2,.3,4,5,6,7)?

FMT RUsure

(1\NO)?

FMTing...........

PV_SCS
FMT BBrepl

PV_SCs_FMI_SUCC
>>>

Figure 3-17 shows an example of an error while running the data eraser
on the drive located at SCSI address 3 on the SCSI-A bus.
Figure 3-17

>>> T

Example of an Error While Erasing an RZ55

78
ScsHlDerase

SCS

FMT CHN

PV SCS FMT CHN
PV_SCS
FMT ID

(0=SCSIA

PV_SCS_FMT RUsure
PV

(1/0)?

SCS FMTing........... ?

PV_SCS_FMT ERR#3
>>>

1=SCSIB)?

(0,1,2,3,4,5,6,7)?
1

Utilities

3--21

3.7.1 SCSI Disk Eraser Messages
All messages for the data eraser start with PV_SCS_FMT. The second
segment of the message indicates what type of information the utility is
looking for: CHN for which SCSI bus the drive is on, ID (0,1,2,3,4,5,6,7)?
for the SCSI address ID of the drive, and RUsure (1/0)? for one last

verification that you do want to erase this drive. Table 3-9 lists all the
data erasure messages and gives an explanation for each. Table 3-10 lists
the error codes for the disk data eraser utility.
Table 3-9

SCSI Data Eraser Messages

Formatter Message

The Program is ...

PV_SCS_FMT_CHN (0=SCSIA \

Asking which SCSI bus the drive is
located on.

1=8SCSIB)?

PV_SCS_FMT_ID (0,1,2,3,4,5,8,7)?

Asking for the SCSI address ID of the
drive.

PV_SCS_FMT _RUsure (1\0)?

Asking, “Are you sure?” as a safety check.
If you want to erase the drive, enter 1;
otherwise, enter 0 or any other character
to abort the process.

PV_SCS_FMTing

Erasing the drive.

PV_SCS_FMT_ERR#

Stopping the eraser because of the error
code indicated by the #. Table 3-10 lists
the error codes.

Table 3-10

Illegal unit number entered.

Error occurred during an SCSI bus command.

Reassign blocks failed (no more replacement blocks available).

Description

Unit not ready.

Code

T 75 Error Codes for the SCSi Dats Eraser

Illegal device type for operation.

3-22

utilities

3.8

Mass Storage Diskette Formatter (T 76)

This utility formats RX23 diskettes. The command to start the formatter
is T 76. Figure 3-18 shows an example of running the formatter on DUA2

(RX23).

CAUTION
Formatting destroys all user data on the diskette.
Flgure 3-18

Exampile of Formatting an RX23 Diskette

>>> T 76
ScsFLpFmtter

PV_SCS_FMT
CHN (0=SCSIA \ 1=SCSIB)
PC_SCS_FMT
ID (0,1,2,3,4,5,6,7)
PV_SCS_FMT RUsure (1\0) ? 1
PV_SCS_FMTing ..... OK
PV_SCS_CKRXFMT ..... OK
PV_SCS_RES_Succ
>>>

Enter SCSI bus.
Enter drive number.

Enter 1 for yes, 0 for no.
Diskette formatted OK.
Diskette checked OK.

Diskette is formatted successfully.

2 1

? 2

@
@

@
©
@

Utilities

3-23

3.8.1 Diskette Formatter Messages
All messages for the formatter start with PV_SCS_. The second segment
of the message indicates the type of message. Table 3-11 lists all the
formatter messages and gives an explanation for each.
Table 3-11

Diskette Formatter Messages

Formatter Message

Explanation

PV_SCS_CkRXfmt

The RX23 diskette format is being

PV_SCS_FMTING

The RX23 diskette is being formatted.

PV_SCS_FMT_RUSURE (1/0) ?

The formatter uses this question as a

PV_SCS_FMT_ID (0,1,2,3,4,5,6,7)

Enter the drive that needs formatting.

checked.

safety check. If you want to format the
diskette that is indicated by the #, enter
1 for yes. Otherwise, enter any character
other than 1 to abort the formatter.
Enter 2 for DUA2 (a 0 is for DUAO, 1
is for DUALI, and 3 is for DUA3). Any
character other than listed aborts the
formatter.

PV_SCS_RES_Succ

The diskette has been successfully

PV_SCS_RES_Abtd

The RX23 formatter has been aborted.

PV_SCS_FMT
ERR #

The formatter has been stopped because
of the error code indicated by the #.
Table 3-12 lists the error codes.

formatted.

Table 3-12 ,,T 76 Error Codes for the Diskette Formatter
Code

Description

Illegal unit number entered.

Error occurred during formatting.

Error occurred during the diskette check pass.

No diskette is loaded in the diskette drive, or the diskette is not an

RX23 media.

3-24

Utilities

3.9

Determining SCSI Address IDs for Drives in the
System (SHOW DEVICE)

Enter SHOW DEVICE at the console prompt (>>>) to check the SCSI
address ID for a particular device or to determine whether the device is
on the SCSI-A or SCSI-B bus. The SHOW DEVICE command displays all
devices connected to the SCSI bus controllers. This display lists the SCSI
address ID of all devices on SCSI buses. Figure 3-19 shows an example
of this command.

Figure 3-19

>>>

Example of the SHOW DEVICE Coinmand

SHOW DEVICE

VMS/VME

ULTRIX

ADDR

DEVTYP

NUMBYTES

——

-——

- —

- -

— - —

ESAO

5E0

08-00-2B-03-79-1F @

DKA300

RZ3

A/3/0/00

DISK

104

T25

...Ho0stID....

A/5/0/00

A/6

TAPE

«uuu....

DKB200

RZ10

B/2/0/00

DISK

104

DKB300

RZ11

B/3/0/00

DISK

104

DKB400

RZ12

B/4/0/00

RODISK

935

RRD40

B/6

INITR

...HostID....

(]

DEVNAM

MKA500

INITR @

RM/FX

RZ23

R223
RZ23

>>>

ESAQ — the Ethernet device and the Ethernet address of the system.
...HostID... — the SCSI bus controller.

Device numbers for VAX/VMS operating systems.
Device numbers for ULTRIX operating systems.

Address.
Device type.

Number of megabytes.

Removable or fixed disk.
Write protected.
Device name.

Utilities

3-25

If the system does not contain a full configuration of drives internally,
additional expansion boxes can be connected to the SCSI-B port using one
of the unused SCSI address ID locations. See Section 2.12.4 for further
information on how to set the proper SCSI address IDs for all devices.

3.10

Extended Summaries for the System Exerciser
(SHOW ESTAT)

Extended summaries are available only when running the system
exerciser in Field Service mode.

When running TEST 101, extended summaries are available when the
testing automatically stops after the second pass.

When running TEST 102, extended summaries are available when
you halt the tests by pressing CTRL/C after the second pass of the
test is complete.

When running TEST 80000106, extended summaries are not
available. To display the results of the tests once again press the
halt button after the second pass of the test is complete and enter
SHOW ESTAT at the console prompt (>>>).

Extended summaries contain additional error information on some of the
devices run by the exerciser. Press RETURN to display the first extended
summary. Continue pressing a RETURN to display all of the extended
summaries until you return to the exerciser display. Press a second
CTRL/C to halt the extended summaries and return to the console prompt
(>>>). Press a RETURN to stop the extended summary for the SHOW
ESTAT command. The halt message is displayed when the exerciser is
stopped and control is returned to the console.

To display the extended summaries once again after exiting the system
exerciser, enter SHOW ESTAT. This command brings up extended
summary information from the last time the Field Service system
exerciser ran.

3-26

Utilities

Figure 3-20 shows an example of the extended summary for the SCSI-A
device and then an example for the SCSI-B device.
Figure 3-20

Example of SCSI-B Extended Summary Report

KA41-A

v1.3

senrursr

SCSI-A

STM_SUMM

0 00:05:57

*xkknx

adr

rds

wts

xfs

xferr

sde

003

008

000

157

000

txdwatwser

STM

TYPE

ANYTHING

>>>[ket
rr]
vekewkex

SCS1-B

STM_SUMM

00:05:57

*xwxrin

adr

rds

wts

xfs

xferr

sde

004

008

000

073

000

005

oos

004

023

000

#aseessss

STM TYPE ANYTHING

The SCSI address ID of a drive.
The number of reads performed on that drive.

The number of writes performed on that drive.

The number of data transfers performed on that drive.
The number of transfer errors on that drive.

Utilities

3.11

3-27

Determining the Revision Levels in the System
Module’s ROn! (SHOW VER)

The ROMs on the system module contain four separate sections of
program code. These sections are the sclf-test code (PST), console code
(CON), VMB code, and the ROM code; all huve different internal revision
levels. Enter SHOW VER to see the internal revision levels of the selftest, console, VMB, and ROM code displayed next to KA41-A. Figure 3-21
shows an example of these revision levels. The 16D is for the self-test
revision level, 1BC is the console code revision level, V4.6 is for the VMB
revision level, and 24B is the ROM code revision level.
Figure 3-21

Example of the System Motuie’s ROM Code Revision

Lovels

>>> SROW VER

KR41-A V1.3BC-16D-V4.6-24B
PST:

>>>

16D

CON:

1BC

VMB:

V4.6

ROM:

24B

4
The Model 10 System

4.1

Enclosure Description

The MicroVAX 3100 and VAXserver 3100 Model 10 systems are similar
in appearance. To identify whic: system you are working on, look at the
nameplate on the front of the system box.

The system box contains up to 11 Field Replaceable Units (FRUs):

System module.

Memory module.

Second memory daughter boaid.

DSH32-B communications module.

Floppy diskette interface (FDI) board.

Power supply.

Distribution board.

Up to three internal mass storage devices (TZ30 tape drive, RX23

e Battery pack.

diskette drive, and RZ22 disk drives).

There are also three expansion boxes availa.le that contain additional
mass storage devices (TK50Z expansion box, RZ55 disk drive expansion
box, and an RRD40 compact disc expansion box).

4-1

4-2

The Model 10 System

Figure 4-1 shows the front and rear panels of the system.
Figure 4~1

The System Box

Power On/Off Switch

Power Connactor

~——\

SCSI-8 Port

Synchronous Port
Heit Button

8-Asynchronous Port

Net Select Indicators

Standard Ethernet Part

T,y

PLOPUTEieN

Ethernet Switch
ThinWire Ethernat Port

N\ e

Ed ()]
\\— Dragnostic LEDs

““— PBreak Enable Switch

AMMJ Port 1

Modsm Port

MMJ Port 2

MMJ Port 3

C—

—

J
MLO 003276

You can connect VTxxx terminals to a MicroVAX 3100 or VAXserver 3100

Model 10 system through MMdJ ports 1, 2, and 3. A fourth Vtxxx terminal
can be connected if an adapter (H8571-4) is fitted to the modem port

(RS232). To connect more terminals, your system must have a DSH32-B

communications module with a cable concentrator connected to the eigiitasynchronous port. The cable concentrator provides an additional eight
MMJ ports. Alternatively, you can connect printers or modems to these
MMJ ports if you wish.

Connection to the Ethernet is done through either the ThinWire
Ethernet port or the standard Ethernet port dzpending on which type
of Ethernet network is available. The position: of the Ethernet switch
determines which of the Ethernet ports provides IEEE 802.3 network
communications. An LED is lit beside the enabled port.

The Model 10 System

4-3

The external SCSI port is used to connect external mass storage devices
to the system.
The position of the BREAK ENABLE switch at powerup determines the
function of MMJ port 3. If the switch is in the down position at powerup,
the port functions as a normal communications port. If the switch is in
the up position, the port functions as an alternative console port to which
you can connect 8 VTxxx terminal. When the VTxxx terminal connected
to the MMJ port 3 is enabled, you can press the BREAK key on the
keyboard to enter console mode directly.

4.2

FRU Removal and Replacement

This section describes the removal and replacement procedures for the
FRUs in MicroVAX 3100 or VAXserver 3100 Model 10 systems. Refer
to Table 4—-1 to find the name of the FRU that needs replacing. 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 replaced device for proper operation.
CAUTION
Wear a static wrist strap and use a static mat when replacing
FRUs.
Table -1

FRU Section Listings

FRU

Section

Distribution board

4.2.3

RZ23 disk drive

4.2.4

TZ30 tape drive

4.2.5

RX23 diskette drive and FDI board

4.2.6

DSH32-B communications module

4.2.1

Memory modules

4.2.8

System moduie

4.29

Battery pack

4.2.10

Power supply

4.2.11

Figur: 4-2 shows the locations of the FRUs.

4~-4

The Model 10 System

Figure 4-2

FRU Locations
a

Destribution

RZ23 Digk Drive

TZ30 Tapa Drive

{Optionally, RZ23 Disk Drive
or RX2S Disketta Drive)

Power Supply

Optional DSH32-8
Communications Module
tomory idodule

Battery Pack

4.2.1

System Box Cover Removal

Remove the system box as follows:
1.

Turn the system power switch off.

Disconnect all the cables connected to the system unit.

Loosen the two cover screws on the rear panel of the system box. See
Figure 4-3.

Slide the cover forward and up off the system box.

Figure 4-3

Cover Screw Locations

Covar Scraw Locations /
MLO-003278

4.2.2 Drive Mounting Panel Removal
The drive mounting panel contains storage devices in one of the

combinations shown in Figure 44, depending on the configuration.
Remove the drive mounting panel as follows:
1.

Remove the system box cover. See Section 4.2.1.

CAUTION
You must note which cables connect to which drives when
disconnecting them. Write the type of drive and ite position

on a piece of tape and wrap the tape around the connector

before disconnecting it. This will help you when reinstalling
the drives.

Disconnect the SCSI and power cables connected to the drives on the
drive mounting panel. See Figure 4-4.

Disconnect the cables connecting the distribution board to the system
module and DSH32-B communications module (if installed). See
Figure 44,

4-6

The Model 10 System

Figure 4-4

Storage Device Positioning and Cabling

-—

Distribution

| |_— scsi8

Board

" ———,

Power

DSHaz2-8

Supply

Unused

System Module

SCSI-A

To FDI Board
for RX23

Option
Addtional
Power

Connector

Unused

1230. RX23. or R723

R223

for RX23

Drive

SNSRI

Drive Mounting Panel

Boarg

| Distribuytien

scst-8
oo _l‘/—.‘
1]
c

Power

DSH32-8

Supply

System Module

=~ -— SCStA

To FDi Board

for RX23

Option

RZ23

F.J,L—--—-—- Additional
Power

RX23 or
RZ23

RZ23

Connecior

for AX23

Drive

Drive Mounting Panel
MLO-003373

The Model 10 System

Unscrew the seven screws. See Figure 4-5.

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

Figure 4-5

4-7

Unscrewing the Drive Mounting Panel

Ceptive Screw (1)

Captive Screws (2)

Panhead Screws
{3 Loosenad)
MLO-003279

4.2.3 Distribution Board Remova)

Figure 4--7 identifies the connectors on the distribution board. Remove

the distribution board as follows:
1.

Remove the system box cover. See Section 4.2.1.

Disconnect the SCSI-A cable and the SCSI-B cable from the
distribution board. See Figure 4-6.

4-8

The Model 10 System

3. Disconnect the DSH32-B communications module -able (if installed)
and the system module cable from the distribution board. See
Figure 4-6.

4. Unscrew the two captive grounding screws on the distribution board.
See Figure 4-6.

Figure 4~6

Removing the Distribution Board

SCSI-B Cable
DEH92-B Communicaunons

Module Cable

Caplive Screws

System Modute Cable

‘\\ }'

/{2

MLO-003263

5. Release the distribution board from the five standoffs and lift it out of
the system box.

The Modsl 10 System

Figure 4-7

4-9

Distribution Board Connectors

Synchronous Connector

To DSH32-8
Communications Module

8 Asynchronous Connettor

5CSI-A
SCSi-8
To Systam Module
MLO-002959

4.2.4 RZ23 Disk Drive Removal
Up to three RZ23 hard disk drives can be installed on the drive mounting
panel. The System disk and one other can be connected to the SCSI-A bus
and a third can be connected to the SCSI-B bus.
All RZ23 disk drives contain an internal FRU called the drive module
/frame. See Figure 4-8. Once you remove the drive from the system, you

must always replace the drive module/frame first before replacing the
whole drive.

If replacing the drive module/frame does not fix the fault in the drive, you
must replace the drive as one FRU since the head/disk assembly (HDA) is
not a separate FRU.
The following procedure describes how to remove a drive from the system
and remove and replace the drive module/frame:
1.

Remove the system box cover. See Section 4.2.1.

Remove the drive mounting panel. See Section 4.2.2.

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

4-10

The Model 10 System

Disconnect the drive interconnect cable and remove the two screws
with an 1/8 inch Allen wrench. See Figure 4-8.

Figure 48

Removing the HDA

118 %1298
g
WA Xig48 02

CAUTION
RZZ3 disks are fragile. Handle them with care.

The Model 10 System

4-11

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

6. Slide the HDA into the rubber stops on the new drive module/frame.
Screw in the two new screws supplied.

Connect the drive interconnect cable on the new drive module/frame

Position the jumpers on the new drive module to ths samie position as
the jumpers on the drive module you just removed. See Figure 4-9.

to the HDA.

Figure 4-9

Rz23 SCSI ID Jumper Locations

Signal Connector

Connactor to HDA Module

SCS8! 1D Jumpar Wires

Power Connector

—

4-12

The Model 10 System

4.2. T£30 Tepe Drive Removal
The TZ30 tape drive (if installed) is located on the right-hand side of the
drive mounting panel as viewed from the front.

Remove the TZ30 tape drive as follows:
1.

Remove the system box cover. See Section 4.2.1.

Remove the drive mounting panel. See Figure 4-5.

Turn the 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 on
the TZ30 you removed. Usually the switches are s2t as shown in
Figure 4-10.

NOTE
Ensure the rubber grommets stay in place.

Route the TZ30 power cable through the signal cable to make
assembly easier.

The Model 10 System

Figure 4-10

4-13

TZ30 Jumper Switch Location

=
31

<— ON

OFF —e»
WA XU79S 80

MLC-003379

4.2.6 RX23 Diskette Drive and FDI Board Removal

The drive mounting panel can contain an RX23 diskette drive in the

right-hand compartment.

Remove the RX23 diskette and the FDI board drive as follows:
1.

Remove the system box cover. See Section 4.2.1.

Disconnect the power and signal cables from the back of the RX23
diskette drive.

4-14 The Model 10 System

ing bracket to the
3. Unscrew the four screws securing the RX23's mount
drive mounting panel and lift out the RX23 with the bracket assembly
attached. See Figure 4-11.

Figure 4~11 RX23 Mounting Bracket Screws

R¥23 Mountng Bracket

MLO-003322

4. Remove the four screws securing the faulty RX23 to the mounting
bracket.

Disconnect all power and signal cables ronnected to the FDI board.
Release the FDI board from the four standoffs, then lift it off the drive
mount.ng panel. See Figure 4-12.

The Model 10 System

Figure 4-12

4-15

Removing the FDI Board

RX23 FDI Board

MLO-003318

Set the switches on the new FDI board to the settings on the drive

you removed. See Figure 4-13.

Figure 4-13

SCS! ID Switches

FDi Board SCSI Switch Locations

/'-

4-16 The Modsl 10 System

8. Set the select switch on the new drive to the sstting on the drive you
removed. See Figure 4-14.

Figure 4-14

RX23 Select Switch Position

ML0O-003383

4.2.7 DSH32-B Communications Module Remova!
Remove the DSH32-B communications module (if installed) &3 follows:
1.

Remove the system box cover. See Section 4.2.1.

Remove the drive mounting panel. See Section 4.2.2.

Release the DSH32-B communications module fiom the four standoffs,
then lift it off the system module. See Figure 4-15. Two connectors
disconnect as you lift the module.

The Model 10 System

Figure 4-15

4~17

DSH32-B Communications Module Removal

DSH32.B Communications
Module Cable

DSH32-B Communications Mod

MLO-003200

4.2.8 Memory Module Removal
There are three memory modules available: 4Mb, 12Mb, and 16Mb
modules. The 4Mb and 12Mb modules are physically e same. The
16Mb module is slightly larger than the other two and it contains two
additional connectors that allow one of the other two memory modules to
be connected piggyback style. This piggyback connection allows the 4Mb
and 12Mb modules to increase the total memory in (he system to 24Mb
and 32Mb (including 4Mb on the system module). The remaval procedure
for all memory modules is the same.

Remove the memory modules as follows:
1.

Remove the system box cover. See Section 4.2.1.

Remove the drive mounting panel. See Section 4.2.2.

Release the memory module from the four standoffs, then lift the
memory module off the system module. See Figure 4-16. Two
connectors disconnect as you lift the module.

4-18

The Model 10 System

Figure 4-16

Memory Module Removal

Memory Module

MLO-003281

If the 16Mb memory module is installed and a 4Mb or 12Mb memory
module is attached, separate the two modules and replace the faulty
module (see Figure 4-17). Reassemble the two modules before
reinstalling them onto the system module.

Figure 4-17

16hib Memory Module

16 Mbyte Memory Module

€E* Clips
Ci

(4 Places)

E: -4

S
12 Mbyte Memory Module

I
I

> 1

System Module
MLO-003292

The Model 10 System

4-19

4.2.9 System Module Removal

ol
A

Remove the system module as follows:
Remove the system box cover. See Section 4.2.1.

Remove the drive mounting panel. See Section 4.2.2.
Disconnect all cables from the back of the system box.

Release the DSH32-B communications module (if installed) from the
four standoffs, then lift the DSH32-B communications module off the
system module. See Figure 4-15. Two connectors disconnect as you
lift the module.
Release the memory module from the four standoffs, then lift the
memory module off the system module. Sce Figure 4-16. Two
connectors disconnect as you lift the module.
Disconnect the power cable and the battery cable from the system
module. See Figure 4-18.
NOTE
The pewer cable connector has a release tab which must be
pressed to remove it from the system module.

Remove the eight screws from the system module. See Figure 4-18.
Remove the system module by carefully popping the two front corners
off the two locating standoffs.
NOTE
When reinstalling the system module, install the connector

end first through the openings in the rear of the box, Push the
module back tc load the connector ground tabs and then snap
the module onto both locating stendoffs. All screw holes will
then be aligned.

CAUTION
Be careful not to bend the pins on the ROM.
Remove the Ethernet ID ROM from the system module you removed
(see Figure 4-19). Check the position of pin 1 (notched) on the ROM.
Install the ID ROM on the new system module.

4-20

The Model 10 System

10. Set the baud rate jumper on the new system module to the setting on
the system module you removed. See Figure 4-22.
System Module Screw Locations

Figure 4-18

Ground Taba

Power Cable

Panhead Screws (5)

Locating Standott

—
—— -

Panhead Screws (3)

Battery Catle
Locating Standoff

MLO-003282

Figure 4-19

Location of Ethernet ID ROM on System Module

Ethernat ID ROM

MLD-002944

The Model 10 System

4-21

4.2.10 Battery Pack Removal
Remove the battery pack as follows:
1.

Remove the system box cover. See Section 4.2.1.

Remove the drive mounting panel. See Section 4.2.2.

Disconnect the battery cable from the system module. See
Figure 4-20.

Figure 4-20

Battery Cable Location

Battery Cable
Battery Pack

MLO-0032683

Remove the battery pack from its holder.

NOTE
A new battery needs a minimum of 17 hours of continuous
power to fully charge the battery. If the battery’s charge is

low, you will see an error for the NVR (0000.0005) when you
power up the system.

4-22 The Model 10 System

4.2.11 Power Supply Removal
Remove the power supply as follows:
2,

Remove the system box cover. See Section 4.2.1.
Remove the drive mounting panel. See Section 4.2.2.

Disconnect the power cable from the system module.

Loosen the two captive screws and the two panhead screws. See
Figure 4-21.

Figure 4-21

Power Supply Screw Locations

Captive Screw

Panhead Scraws
Power Supply

Captive Screw

MLO- 003284

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

6. Lift the faulty power supply out of the system box.

The Model 10 System

4.3

4-23

Options

This section describes the options available for the system.

4.3.1

Internal Memory Options

Three memory modules are available: a 4Mb memory module, a 12Mb
memory module, and a 16Mb memory module. Only one memory module
can be plugged into the system module unless the 16Mb memory module
is installed. The 16Mb module has extra connectors which allows one of
the 4Mb or 12Mb memory modules to be plugged into it piggyback style.
With the 16Mb module plugged into the system module, a total of 24Mb
or 32Mb memory is possible (4Mb on the system module and the 12Mb
module piggybacked on the 16Mb module = 32Mb).
The procedure used to install memory modules is the reverse of the
procedure listed in Section 4.2.8.

4.3.2 DSH32-B Communications Module Options
The DSH32-B communications module is in the system box and plugs
directly into the system module. The DSH32-B communications module
provides one eight line asynchronous port and one synchronous port.

The procedure used to install the DSH32-B communications module is the
reverse of the procedure listed in Section 4.2.7.

4.3.3 Optional Storage Device Positioning
In Model 10 systems, up to three devices can be installed on the drive
mounting panel within the system enclosure. Depending on your system
configuration, your system may contain these devices in the combinations
listed in Table 4-2.

4~24

The Model 10 System

Table 4-2

Riodel 10 Internal Storage Device Combinations

Drive Mounting Panel

Left Compartment !

Right Compartment

One RZ23

TZ30

Cne or two RZ23s

RX23

One or two RZ23s

RZ23

1If only one RZ23 hard disk drive is installed in the left compartment, it is mounted in

parallel with the device in the right compartment. If two RZ23s are installed, they are
mounted side by side and at right angles to the device in the right compartment.

If the system already has two storage devices installed and you want

to install another, it may be necessary to move the device in the left
compartment to the position shown in Figure 4-4. Install the third device
in parallel with the device you have just moved.

4.4

Changing the Maximum Baud Rate of the MMJ
Ports and the Modem Port

When the system is delivered, the maximum baud rate of MMJ ports 1, 2,
3, and MODEM is preset to 19.2 Kbaud. This baud rate can be changed
to 19.8 Kbaud or 38.4 Kbaud by repositioning jumpers on the system
module.
Table 4-3 shows the nodes on the system module thet must be linked by
jumpers to obtain the desired baud rate.
Figure 4-22 shows the position of the nodes on the system module.
Table 4-3

Jumper Settings for Serial Port Baud Rates

Baud Rate

Nodes Linked

19.2 Kbaud (default)

SP18 and SP19

19.8 Kbaud

SP18 and SP19
SP20 and SP21

38.4 Kbaud

SP17 and SP18

The Model 10 System

Flgure 4-22

Power Supply

Connector

SP 18

SP 20

Location of Nodes on the System Module

L.t 0)

SP 21

Diagnostic LEDs

—

[

l:] E:-] [o]

4-25

S
The Model 20 System

5.1

Enclosure Description

The MicroVAX 3100 wiodel 26 and VAXserver 3100 Model 20 are similar
in appearance. To identify which system you are working on, look at the
nameplate on the front of the system box.
The system box contains up to 13 Field Replaceable Units (FRUs):
System module

Memory module

Second memory daughter board
DSH32-B communications module
Floppy diskette interface (FDI) board
Power supply

Distribution board
Battery pack

Up to five internal mass storage devices (TZ30 tape drive, RX23
diskette drives, and RZ23 disk drives)

There are also three expansion hoxes available that contain additional
mass storage devices (TK50Z expansion box, RZ55 disk drive expansion
box, and an RRD40 compact disc expansion box).

5-2

The Model 20 System

Figure 5-1 shows the front and rear panel of the system box.
Figure 5-1

Riodel 20 System Box

Power On/Ofl Switch
Power Connac

SCSI-B Port -——-————\
Reserved

Synchronous Port

\ .

Halt Button -

8-Asynchronous Port
Net Salect Indicators
Standard Ethernet Port

Ethernet Switch
ThinWire Ethernet Port

MMJ Port 1

MMJ Port 2

\ Oiagnostc LEDs
Bruak Enable Switch

~— Modem Port

MMy Port 3

631,0-002950

You can connect VIxxx terminals to a MicroVAX 3100 or VAXserver 3100
through MMJ ports 1, 2, and 3. A fourth Vtxxx terminal can be connected
if an adapter (H8571-A) is fitted to the modem port (RS232). To connect
more terminals, your system must have a DSH32-B communications
module with a cable concentrator connected to the eight-asynchronous

port. The cable concentrater provides an additiunal eight MMJ ports.
Alternatively, you can connect printers or modems to these MMJ ports if
you wish.
Connection to the Ethernet is done through either the ThinWire
Ethernet port or the standard Ethernet port depending on which type
of Ethernet network is available. The position of the Ethernet switch
determines which of the Ethernet poerts provides IEEE 802.3 network
communications. An LED is lit beside the enabled port.

The Model 20 System

5-3

The external SCSI port is used to connect external mass storage devices
to the system.

The position of the BREAK ENABLE switch at powerup determines the

funciion of MMJ port 3. If the switch is in the down position at powerup,

the port functions as a normal communications port. If the switch is in
the up position, the port functions as an alternative console port to which
you can connect a VTxxx terminal. When the VTxxx terminal connected
to the MMJ port 3 is enabled, you can press the BREAK key on the
keyboard to enter console mode directly.

5.2

FRU Removal and Replacement

This section describes the remoal and replacement procedures for
the FRUs in the MicroVAX 3100 or VAXserver 310U system. Refer to
Table 5-1 to find the name of the FRU that needs replacing. 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 replaced device for proper operation.
CAUTION

mr a static wrist strap end use a static mat when replacing
8.

Table 5~1

FRU Section Listings

FRU

Section

Distribution board

524

RZ23 disk drive

5.2.5

TZ30 tape drive

526

RX23 diskette drive

5.2.7

DSH32-B communications module

528

Memory modules

529

System module

5.2.10

Battery pack

5.2.11

Power supply

5.2.12

5-4

The Model 20 System

Figure 5-2 shows the 'ocations of the FRUs.
Flgure 5-2

FRU Locations

Upper Drive
Mounting Panal

R223 Disk Drives

Distribution
Board
R223 Disk Drive
(Optionaily,
RX23 Diskette Drive)

T230 Tapa Drive

(Optionally,AZ23 Disk Drive

or RX23 Diskette Drive)

Power Supply
Optional DSH32-8

Comimunications Module
Memory Module

Battery Pack

;

Mty burl

The Model 20 System

§.2.1

5-5

System Box Cover Removal

Remove the system box as follows:
Turn the system power switch off,
2.

Disconnect all the cables connected to the system unit.

Loosen the two cover screws on the rear panel of the system box. See
Figure 5-3.
|

Slide the cover forward and up off the system box.

Figure 5-3

Cover Screw Locations

Cover Screw Locanons

MLO-002046

5-8

The Model 20 System

5.2.2 Upper Drive Mounting Panel Removal
Depending on the configuration, the upper drive mounting panel may
contain one, two, or three RZ23 hard disk drives.
Remove the upper drive mounting panel as follows:
1.

Remove the system box cover. See Section 5.2.1.

CAUTION
You must note which cables connect to which drives when
disconnecting them. Write the type of drive and its position
on & piece of tape and wrap the tape around the connector

before disconnecting it. This will help you when reinstalling
the drives.

Disconnect the power cables and the SCSI bus cables from the drives
on the upper drive mounting panel. See Figure 5-4.
Unscrew the four captive screws. See Figure 5-5.

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

The Model 20 System

Figure 5-4

5-7

Drive Mounting Panel Power and Signal Cabling

Distribution Board

SCSi-B

SCSIA

Adapter (TZ30 Only)

_~\
AN

SCSIH-B Connector

Power

Supply

g)z(gg or

TZ30 Tape Drive,

RZ23 Disk Drive,

or RX23 Diskette

Drive

Lower Drive
Mounting Panel

RZ23
Disk
Drive

Upper Drive
Mounting Pane!

RZ23
Disk
Drve

RZ223
Disk
Drive

Upper Drive Panet Power
weomonaepotes

L OWar Drive Panel Power

exemmmmn Data

MLO-002060

5-8

The Model 20 System

Unscrewing the Upper Drive Mounting Panel

Figure 5-5

Captive Screws (2)

Upper Drive
M¢ .nting Panel

Screws (2)
MLO-002957

5.2.3 Lower Drive Mounting Panel Removal
The lower drive mounting panel contains storage devices in one of the
combinations given in Table 5-2, depending on the configuration.
Table 5-2

Lower Drive Mounting Panel Device Combinations

Left-Hand Compartment

Right-Hand Compartment

RZ23 hard disk

TZ30 tape drive

RX23 diskette drive

TZ30 tape drive

RZ23 hard disk

RX23 diskette drive

RZ23 hard disk

The Model 20 System

5-9

Remove the lower drive mounting panel as follows:
1.

Remove the upper drive mounting panel if not already removed. See
Section 5.2.2,

Disconnect the SCSI and power cables connected to the drives on the
lower drive mounting panel Figure 5—4.

Disconnect the cables connecting the distribution board to the system
module and DSH32-B communications module (if installed). See
Figure 5-6.

4. Unscrew the seven screws. See Figure 5-7.
Slide the panel forward (with the devices attached) then lift the nanel
from the system box and gently set it aside.

5~10

The Model 20 System

Figure 56

Distribution Board Cabling
System

Module
Cabtle

S———
P

SCSI1-8
Expansion Port

DSH32-B Communications —
#odule Cablo
Distribution Board

DSH32-8 Communications
dModule

SCSI-8

SCSI-A

System Madule _————-————/

SCSI-B

To Left-hand
Compartment
SCSI-8
Ta Upper
Drive Panel

_‘_ R
!

SCSHA

To System
Disk
SCSI-A
To Right-hand
Compartment
LO-002961

The Model 20 System

Figure 5-7

5-1

Unscrewing the Lower Drive Mounting Panel

Captive Scraw (1)

Captve Screws (3)

——

Lowsr Drive Mounting Panegi

Panhead Screws
(3 Loosened)
MLO-002956

5.2.4

Distribution Board Removal

Figure 5-9 shows the connector locations on the distribution board for
reference. Remove the distribution board as follows:
1.

Remove the system box cover. See Section 5.2.1.

Remove the upper drive mounting panel. See Section 5.2.2.

Disconnect the SCSI-A cable and the SCSI-B cable from the

distribution board. See Figure 5-8.
4.

Disconnect the DSH32-B communications module cable (if installed)

and the system module cable from the distribution board.
5.

Unscrew the two captive grounding screws on the distribution board

See Figure 5-8.
6.

Release the distribution board from the five standoffs and remove it.

gl 20 System

izenoving the Distribution Board

GLS518Canie

...

384328 Commurcations
tdodute Cabto

Captve Screws

8CS-A Cable

Systam blodute Cable

MLO-003285

Figure 5-9

Distribution Board Connectors

Synchronous Connector

Yo DSH32-B8

Communications Module

8 Asynchronous Connactor

SCS8I-A
SCSI-B

To Systam Module
MLO-002050

The Model 20 System

5-13

5.2.5 RZ23 Disk Drive Removal
RZ23 hard disk drives can be installed on the upper or lower drive
mounting panel or on both panels, depending on the system configuration.
Three RZ23 drives can be installed on the upper drive mounting panel.

One of the drives is the system disk and connects to the SCSI-A bus while
the other two are user disks and connect to the SCSI-B bus.
Two RZ23 drives can be installed on the lower drive mounting panel. The
right-hand drive (as viewed from the front) is connected to the SCSI-A
bus; the left-hand drive is connected to SCSI-B bus.
All RZ23 disk drives contain an internal FRU called the drive module
/frame. See Figure 5-10. Once you remove the drive from the system,
you must always replace the drive module/frame first before replacing the
whole drive. If replacing the drive module/frame does not fix the fault
in the drive, you must replace the drive as one FRU since the head/disk
assembly (HDA) is not a separate FRU.
The following procedure describes how to remove a drive from the system
and remove and replace the drive module/frame:
1.

Remove the system box cover. See Section 5.2.1.

Remove the drive mounting panel to which the faulty drive is
connected. See Section 5.2.2 or Section 5.2.3.

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

Disconnect the drive interconnect cable and remove the two screws
with an 1/8 inch Allen wrench. See Figure 5-10.

CAUTION
RBQWe9Af

The Model 20 System

5-15

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 drive module/fframe.
7.

Screw in the two new screws supplied.

Connect the drive interconnect cable on the new drive moduleframe
to the HDA.

Position the jumpers on the new drive module to the same position as
the jumpers on the drive module you just removed. See Figure 5-11.

Figure 5-11

RZ23 SCSI ID Jumper Locations

Signat Conrector

Connector to HDA Module

SCSi IC Jumper Wires

had

Power Connsctor
MLO 002943

5-16

The Model 20 Systam

5.2.6 TZ3D Tape Drive Removal
The TZ30 tape drive is on the lower drive mounting panel, positioned on
the righi-hand side as viewed from the front.
Remove the TZ30 tape drive as follows:
1

Remove the system box cover. See Section 5.2.1.

Remove the upper drive mounting panel. See Section 5.2.2.

Remove the lower drive mounting panel. See Section 5.2.3.

Turn the lower drive mounting panel over and while supporting the
T230 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 yne side and remove it from the mounting panel.
Set the switches on the right side of the new TZ30 to the setting on
the TZ30 you removed. See Figure 5-12.
NOTES

Ensure the rubber grommets stay in place.
Route the TZ30 power cable through the signal cable to make
assembly easier.

The Modsel 20 System

Figurc 5-12

5-17

TZ30 Jumper Switch Location

—_4

‘_—3
K]~
2

«+— ON

OFF o

MA-XG780 88

MLO-003379

5.2.7 RX23 Diskette Drive and FDI Board Removal
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 FDI board as follows:
1.

Remove the system box cover. See Section 5.2.1.

Remove the upper drive mounting panel. See Section 5.2.2,

Unscrew the four screws securing the RX23’s mounting bracket to the
drive mounting panel and lift out the RX23 with the bracket assembly
attached. See Figure 5-13.

board.FDIthetoconectedcablessignalandpowerallDisconnect5.
5mountingthetoRX23faultythes-e1c4u.rFiinggurscerSeewesfpoaunrelt.hmeoRuenmtoivneg4.
HLO-003322

drivetheofitlifttlienstandoffs,fourthefromboardFDItheRelease6.
bracket.

The Model 20 System

5-'9

Figure 5~-14 Removing the FDI Board

RX23 FD! Board

MLO-003287

Set the switches on the new FDI board to the settings on the drive

you removed. See Figure 5-15.

Figure 5-15

FDI Board SCSI Switch Locations

SCS! ID Switches
MO 003273

5-20

The Modsl 20 System

Set the select switch on the new drive to the setting on the drive you
removed Figure 5-16.

Flgure 5-16

RX23 Selsct Swiich Position

MLO-003383

The Mode! 20 System

5-21

5.2.8 DSH32-B Communications Module Removal
Remove the DSH32-B communications module (if installed) as follows:
Remove the system box cover. See Section §5.2.1.

Remove the lower drive mounting panel. See Section 5.2.3.

Remove the upper drive mounting panel. See Section 5.2.2.

Release the DSH32-B communications module from the four standoffs,
then lift it off the system module. See Figure 5-17. Two connectors
disconnect as you lift the module.

Figure 5-17

DSH32-B Communications Module Removal

DSH32-8 Communicatons
Module Cable

P ' fl

DSH32-B Communications Module

dr
.

BALO-C0203%

5.2.9 Memory Module Removal
There are three memory modules available: 4Mb, 12Mb, and 16Mb
modules. The 4Mb and 12Mb modules are physically the same. The
16Mb module is slightly larger than the other two and it contains two
additional connectors for connecting one of the other two memory modules
piggyback style. This piggyback connection allows the 4Mb and 12Mb
modules to increase the total memory in the system to 24Mb and 32Mb
(including 4Mb on the system module). The removal procedure for all
memory modules is the same.

5-22

The Model 20 System

Ll
A
e

Remove the memory modules as follows:

Remove the system box cover. See Section 5.2.1.
Remove the upper drive mounting panel. See Section 5.2.2.
Remove the lower drive mounting panel. See Section 5.2.3.

Release the memory module from the four standoffs, then lift the
memory module off the system module. See Figure 5-18. Two
connectors disconnect as you lift the module.

Figure 5~18

Memory Module Removal

fdemory Module

MLO-002083

The Model 20 System

5-23

If the 16Mb memory module is installed and a 4Mb or 12Mb memory
module is attached, separate the two modules and replace the faulty
module (see Figure 5-19). Reassemble the two modules before
reinstalling them onto the system module.
Figure 5-19

16Mb Memory Module

16 Mbyta Memory Module

(4 Places)

"E" Clips

12 Mbyte Memory Module

E '

System Module
MLO-003292

5.2.10 System Module Removal
Remove the system module as follows:
1.

Remove the system box cover. See Section 5.2.1.

Remove the upper drive mounting panel. See Section 5.2.2.

Remove the lower drive mounting panel. See Section 5.2.3.

Disconnect all cables from the back of the system box.

Release the DSH32-B communications module (if installed) from the
four standoffs, then lift the DSH32-B communications module off the

system module. See Figure 5~17. Two connectors disconnect as you
lift the module.
Release the memory module from the four standoffs, then lift the
memery module off the system medule. See Figure 5-18. Two
connectors disconnect as you lift the module.

$-24

The Model 20 System

Disconnect the power cable and the battery cable from the system
module. See Figure 5-20.

NOTE
The power cable connector has a release tab which must be
pressed to remove it from the system module.

Remove the eight screws from the system module. See Figure 5-20.
Remove the system module by carefully popping the two front corners
off the two locating standoffs.
NOTE

When reinstalling the system module, install the connector
end first through the openings in the rear of the box. Push the
module back to load the connector ground tabs and then snap
the module onto both locating standoffs. All screw holes will
then be aligned.

CAUTION
Be careful not to bend the pins on the ROM.
Figure 5-20

System Module Screw Locations
Ground Tabs

Panhead Screws (5)

Locating Standoft

Panhaad Screws (3)

Battery Cable

Locating Standoft

MLO-002051¢

The Model 20 System

5-25

10. Remove the Ethernet ID ROM from the system module you removed
(see Figure 5-21). Check the position of pin 1 (notched) on the ROM.
Install the ID ROM on the new system module.
11. Set the baud rate jumper on the new system module to the setting on

the system module you removed. See Figure 5-24.
Figure 5-21

Location of Ethernet ID ROM on System Module

Etharnet ID ROM

MLO-002944

5.2.11

Battery Pack Removal

Remove the battery pack as follows:
1.

Remove the system box cover. See Section 5.2.1.

Remove the upper drive mounting panel. See Section 5.2.2.

Remove the lower drive mounting panel. See Section 5.2.3.

5-26

The Model 20 System

Disconnect the baitery cable from the system module. See
Figure 5-22.

Remove the battery pack from its holder.
NOTE

A new battery needs a minimum of 17 hours of continuous
power to fully charge the battery. If the batiery’s charge is
low, you will see an error for the NVR (0000.0005) when you
power up the system.

Figure 5-22

Battery Cable Locatlon

Battery Cable
Battary Pack
MLO 002052

5.2.12 Power Supply Removal
Remove the power supply as follows:
1.

Remove the system box cover. See Section 5.2.1.

Remove thc upper drive mounting panel. See Section 5.2.2.

Remove the lower drive mounting panel. See Section 5.2.3.

Disconnect the power cable from the system module.

The Mode! 20 System

5-27

Loosen the two captive screws and the two panhead screws. See
Figure 5-23.

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

Lift the faulty power supply out of the system box.

Figure 5-23

Power Supply Screw Locations

Captive Screw

Panhead Screws
Powaer Supply

Captive Screw
MLO-002954

5-28

The Model 20 System

5.3

Internal Memory Options

With the 16Mb module plugged into the system medule, a total of 24Mb
or 32Mb memory is possible (4Mb on the system module and the 12Mb
module piggybacked on the 16Mb module = 32Mb).
The procedure used to install memory modules is the reverse of the

procedure listed in Section 5.2.9.

5.4

DSH32-B Communications Module Option

The DSH32-B communications module is in the system box and plugs

directly into the system module. The DSH32-B communications module
provides one eight line asynchronous port and one synchronous port.

The procedure used to install the DSH32-B communications module is the
reverse of the procedure listed in Section 5.2.8.

5.5

Changing the Maximum Baud Rate of the MMJ
Ports and the Modem Port

When the systera is delivered, the maximum baud rate of MMJ ports 1, 2,
3, and MODEM is preset to 19.2 Kbaud. This baud rate can be changed
to 19.8 Kbaud or 38.4 Kbaud by repositioning jumpers on the system
module.
Table 5-3 shows the nodes on the system module that must be linked by
jumpers to obtain the desired baud rate.
Figure 5-24 shows the position of the nodes on the system module.

The Model 20 System

Jumper Settings for Serial Port Baud Rates

Baud Rate

Neodes Linked

19.2 Kbaud (default)

SP18 and SP19

19.8 Kbaud

SP18 and SP19
SP20 and SP21

38.4 Rbaud

SP17 and SP18

Figure 5-24

Location of Nodes on the System Module

Power Supply
Connector

SP 17

SP i8

SP 20

SP 21

Diagnostc LEDs

}

)

@\
e 96

Table 5-3

.,.

Leom mo a1

///

MLO-003374

5-29

6
Expansion Boxes
This chapter describes the three expansion boxes available for use with

the MicroVAX 3100, the VAXserver 3100, and the InfoServer 100 systems.
These three expansion boxes are the RZ55 disk drive, the RRD40 compact
disc drive, and the TK50Z tape drive.
NOTE
SCSI IDs’s of expansion boxes are ¢etermined by the SCSI D)

switch positions on the device. To simplify explanations, the 3CSI
IDs mentioned in this chapter are the default values. They may
have been changed by the customer depending on the system
configuration.
Table 6- . lists each expansion box an . the section where it is described.
Table 6-1

Expansion Box Section Listing

Expansion Box

Section

RZ55 disk drive expansion box

6.1

RRD40 compact disc expansion box

TK50Z tape drive expansion box

6.3

6.1

RZ55 Expansion Box

The RZ55 expansio. box contains five FRUs:
e

The RZ55 drive

The RZ55 elecironmes module

The SCSI ID swiv"h module

6-1

6-2

Expansion Boxes

The power supply

The resistor load boe~d

Figure 6-1 shows the RZ55 expansion box.
Figure 6-1

RZS55 Expansion Box

MLO-003338

CAUTION

The RZ55 expansion box must always be switched on or off before
any other device so as not to disrupt the SCSI-B bus.
The RZ55 expansion box c¢inects to the svevem box through the external
SCSI port. The SCSI cable connects to either of the two ports on the back
of the expansion box. However, the SCSI terminator must be installed
on the unused connector unless another expansion box is daisy chained.
If the SCSI port already has a box connected to it, use another cable to
connect the RZ55 expansion box to the last box on the daisy chain. Be
sure to move the terminator onto the unused connector on the back of ti.e
last expansion box in the daisy chain. Figure 6-2 and Figure 63 show
how the RZ55 expansion box connects to the system box.

Exparsion Boxes

Figure 6-2

6-3

RZS55 Expansion Box Connection

Terminator

Connector Cable

MLO-002784

Flgure 6-3

Two Daisy Chalned RZ55 Expansion Boxes

Terminator

50-Pin to 50-Pin ---- —
Connsctor Cable

MLO 002762

6-4

Expansion Boxes

6.1.1 Troubleshooting the RZ55 Disk Drive Expansion Box
To troubleshoot the RZ55 disk in the expansion box, use the self-test and
system exerciser diagnostics in the system box. See Section 2.12.3 if you
are not familiar with testing the devices on the SCSI bus.
Self-test results for the RZ55 disk drive should contain 00000001 in the
SCSI address ID location set by the switches on the back of the expansion
box (should be ID 1). A code of FFFFFF05 for the RZ55 indicates that the

device is not installed, not powered up, not connected to the SCSI port

correctly, or faulty. A code of FFFFFFFF indicates that the device was not
tested because of an SCSI bus controller error. Any code other than those
previously listed indicates an error with the disk drive at that address
1D location, a cabling problem, or an error with the SCSI bus controller
on the system module. An additional RZ55 drive expansion box can be
installed at address ID 2 or 3 if no internal drives connect to these SCSI
address IDs on the external SCSI bus.
When running the system exerciser in Field Service mode, the code for
the disk drive shows that it is writable and that no errors are presen’

(1200.0001 for an SCSi ID of 1). Any error code other than those
previously listed indicates a possible disk error, but never rule out the
possibility of an error on the SCSI bus controller itself.
I7 the tests indicate an error on the RZ55, periorm the following steps
1.

Make sure the expansion box has power and is switched o°:

Make sure the SCSI port cable connects correctly to the cxternal SCSI

port on the system box, or to the previous expan<ion ' gx, and to the
back of the RZ55 expansion box.

Make sure the SCSI terminator is ins_talled on the unused connector
on the back of the box or that the cable is secured to the next daisychained box.

Run the tests again.
If the problem returns, disconnect the RZ55 expansion box from the

daisy chain or from the external SCSI port if no otlter boxes are
connecied. Instal! the SCSI terminator on the external SCSI port,
make sure the last expansion box is terminated correctly, and run
self-test (TEST 6).
6.

If the status code is not FFFFFFO05 for the address ID of the RZ55
expansgion box (normally address ID 1), check the SCSI address IDs
of all drives on the bus for correct settings. If the address IDs are set
correctly, replace the system module.

Expansion Boxes

6-5

If the status code is FFFFFF05, check the address ID switch on the
back of the RZ55 expansion box to make sure it is set correctly. See
Figure 6—13 for proper SCSI ID switch settings.

If the address ID and drive select jumpers ere set correctly, a fault in
w

the RZ55 expansion box exists.

Remove the cover of the expansion bex and check the internal cabling

for good connections.

10. Power up the expansion box and listen for the fan and the drive to

spin up. If the fan does not spin or the drive does not hum, replace

the power supply, reconnect the box to the SCSI port, and retest.
11, If the power supply operates normally, replace the RZ55 electronics

module, reconnect the box to the SCSI port, and retest.

12. If replacing the RZ55 electronics module did not fix the problem,

replace the whole R7Z55 drive, reconnect the box to the SCSI port, and
retest.

13. If replacing the RZ55 drive did not fix the problem, replace the SCSI

switch module, reconnect the box to the SCSI port, and retest.
14. If replacing the SCSI ID switch module did not fix the problem,

replace the resistor load board, reconnect the box to the SCSI port,
and retest.
15. If a probiem still exists, check the internal SCSI cable’s connector

for damaged pins or cut wires. Check the external SCSI cable for

damaged connector pins or cut wires. Then replace the system module
in the system box if the cables appear normal.

6-6

Expansion Boxes

6.1.2 RZ55 Expansiuva Box FRU Locations
Figure 64 shows the locations of the FRUs in the RZ55 expansion box.
Flgure 6-4

RZS55 Expansion Box FRU Locatlons

SC8! Switch Board

Hasistor Load Board

Power Supply

RZ55 Disk Drive

6.1.3 RZ55 Expansion Box FRU Removal and Replacement
This section describes the removal and replacement procedures for the
FRUs in the RZ55 expansion box. Refer to Table 6--2 to find the name

of the FRU that needs replacing, then go to the section listed beside the

FRU. Follow the steps in the section to remove the FRU and reverse the

procedures to replace the FRU.

CAUTION
Wear a static wrist strap and use a static mat when replacing an
TRy
& oaRir,

Expansion Boxes

Table 6-2

6-7

RZ55 Expansion Box FRU Section Listings

FRU

Section

RZ565 disk drive and electronics module

6.1.3.1

SCSI ID switch module

6.1.32

Power supply

6.1.3.3

Resistor load board

6.1.3.4

6.1.3.1 RZ55 Disk Drive Removal from Expansion Box
The following section describes the removal and replacement procedure
for the RZ55 and its electronics module. If you have already replaced the
drive’s electronics module and a problem still exists, you must replace the
complete drive instead of replacing just the following electronics module
as described. Remove the complete drive as follows:
1.

Switch off power to the expansion box.

Unscrew the four cover screws and remove the expansion box cover.
See Figure 6-5.

6-8

Expansio: Doxes

Flgure 6-5

RZS5 Expansion Box Cover Screws

Cover Screw Locatons

—-

MLO 003337

Expansion Boxes 6-9

3. Remove the three screws. See Figure 6-6.

ct the power cable from the resistor load
4 Lift the shield up, disconne
shield from the expansion box.
board, and remove the

Figure 6-6 RZ35 Expansion Box Shield Screws

Shield Screws

ML0-003338

6-10

Expansion Boxes

Remove the three drive mounting screws. See Figure 6-7.

Figure 67

RZS55 Expansion Box Drive Mounting Screws

Drive Mounting Screws

MLO-003339

Expansion Boxes

6-11

Slide the drive out halfway and disconnect the data cable, the SCSI
switch cable, and the power cable from the back of the drive, then
slide the drive all the way out of the box. See Figure 6-8.

Flgure 6-8

RZ55 Expansion Box Drive Cables

SCSI Switch Cable

Data Cable

Power Cable

MLO 003340

6-12

Expansion Boxes

Remove the four screws and the mounting brackets from the drive.
See Figure 6-9.

Figure 6-9

RZ55 Mounting Bracket Screws

Mounting Bracket Screws

#Mounting Brackei Screws

#4L.0-003341

Expansion Boxes

6-13

Position the drive as in Figure 6-10.

Flgure 6-10

RZ55 Bezel Removal

MLO-003274

If you have already replaced the electronics module on the drive, stop
here and replace the whole drive. Otherwise, replace the electronics
module as follows:

10. Carefully apply outward pressure te the bezel with your thumbs until
the two bezel locking pins clear the holes in the frame. Note that the
bezel must fiex (about 1/8 inch) to clear the pins.

11. While the bezel is clear of the locking pins, slide it upward until
movement stops (about 3/8 inch). Then remove the bezel from the
drive.

12. Remove the three screws. See Figure 6-11.

6~14

Expansion Boxes

Flgure 6-11

Drive Module Removal

Spindle Motor Connactor

255 Elactronics Board

—o

Insuylator

- oa

Insulater

Auxitiary Boara

Praamplifier

Cable Connactor
MLO-003275

13. Unplug the spindie motor connector at J5.

14. Unplug the preamplifier cable connector at the auxiliary board. When

setting the drive back on the work surface, place a support under the
drive to protect the loose preamplifier cable and connector.
15. Lift the drive module and the auxiliary board up and out of the drive.
16. Remove the screw and speednut hoiding the drive module.
17. Unplug the auxiliary board from J9 on the drive module.
18. Install the new module by reversing the previous procedure.

Expansion Boxes

6-15

19. The jumpers on the new module should not have to be set. Check
the new module to make sure that the jumpers are set to the same
position as on the old module you just removed and set thein if
necessary.

20. Reinstall the RZ55 into the expansion box.
6.1.3.2 RZ55 Expansion Box SCSi ID Switchboard
The SCS: ID switchboard is on the inside back wall of the RZ55 expansion
box. It contains two switch packs. Only one is on the RZ55 expansion box,

and ronnects to the smaller connector on the RZ55 drive by way of a cable.
The following procedure describes how to remove the switchboard:
1.

Switch off power to the expansion box.

Unscrew the four cover screws and remove the expansion box cover.
See Figure 6-5.

Remove the three screws. See Figure 6-6.

Lift the shield up, disconnect the power cable, and remove the shield

(with the resistor load board) frem the expansion box.
5.

Disconnect the cable from the SCSI ID switchboard.
Figure 6-12.

See

6-16

Erpansion Boxes

Filgure 6-12

RZ55 Expansion Box SCSI 1D Switchboard

BCS1 Switch Board

MLO-003342

Remove the two screws from the board and remove the board from the
expansion box.

Set the switch settings on the new SCSI ID switchboard to the same
position as on the old board you just removed.

Reverse this procedure to install the switchboard. Figure 6-13 shows

the default SCSI ID switch settings (ID=1).

Expansion Boxes

Figure 6-13

6-17

RZ55 Expansion Box SCSI ID Switch Setting

6.1.4.3 RZ55 Expansion Box Power Supply Removal
The following procedure describes how to remove the RZ55 expansion box

power supply:
1.

Switch off power to the expansion box.

Unscrew the four cover screws ai:d remove the expansion box cover.
See Figure 6-5.
Remove the three shield screws. See Figure 6-6.
Lift the shield up, disconnect the power cable from the resistor load
board, and remove the shield (with the resistor load board) from the
expansion box.

Remove the three drive mounting screws. See Figure 6-17.
Slide the drive out part way and disconnect the power cable, the SCSI
switch cable, and the data cable from the drive.

Remove the drive from the box.
Tip the RZ55 expansion box on its side, and remove the four power
supply screws. See Figure 6-14.

6~18

Expansion Boxes

9. Replace the power supply by reversing the previous procedure.
Flgure 6- 14

RZ35 Expansion Box Power Supply Screws

Power Supply Mounting Screws

6.1.3.4 Reslistor Load Board Renioval

The following procedure describes how to remove the RZ55 expansion box
resistor load board:

Switch off power to the expansion box.

Unscrew the four cover screws and remove the expansion box cover.

See Figure 6-5.

Remove the three shield screws. See Figure 6-6.

Lift the shield up, disconnect the power cable from the resistor load
board, and remove the shield (with the resistor load board) from the
expansion box.

Expansion Boxes

6-19

Remove the resistor load board from the standoffs on the shield. See
Figure 6-15.

Flgure 6--15

RZ55 Expansion Box Resistor Load Board

Resistor Load Board

Power Connector

;

MLO 0 3 48

Replace the resistor load board by reversing the previous procedure.

6.2

RRD40 Compact Disc Expansion Box

The RRD40 compact disc expansion box is one FRU. There are no
replaceable components inside the box. When you detect an error in
the RRD40 compact disc expansion box, replace the whole box as one
FRU.
The RRD40 compact disc expansion box connects to the svstem box
through the external SCSI port. The SCSI cable connects to either of the

two ports on the back of the expansion box. Install the SCSI terminator
on the unused connector, unless another expansiun box is daisy chained.
If the SCSI port already has a box connected to it, use another cable to
connect the RRD40 expansion box to the last box on the daisy chain. Be
sure to move the terminator onto the unused connector on the back of the
last expansion box in the daisy chain.

6-20

Expansion Boxes

Figure 6-16

RRD40 Compact Disc Expansion Box

Opaning tor Compact Disc

Activity Light
Power Light

MLO-000DTY

6.2.1

RRD40 Compact Disc Expansion Box Troubleshooting

To troubleshoot the RRD40 compact disc expansion box, use the self-test
and system exerciser diagnostics in the system box. See Section 2.12 if
you are not familiar with testing the devices on the SCSI bus.
Self-test results for the RRD40 box should contain 05000001 in the SCSI
address ID location set by the switches on the back of the expansion box
(should be ID 4). A code of FFFFFF05 for the RRD40 box indicates that
the box is not installed, not powered up, not connected to the external
SCSI port correctly, or faulty. A code of FFFFFFFF indicates that the
device was not tested because of a SCSI bus controller error. Any code
other than those previously listed indicates an error with the RRD40
compact disc expansion t._x at that address ID location (should be ID 4),
a cabling problem, or an error with the SCSI bus controller on the system
module. An additional RRD40 expansion box can be connected at address
ID 1 or 0 if no other external boxes are connected to these SCSI address
IDs on the external SCSI bus.
When running the system exerciser in Field Service mode, the code for
the RRD40 compact disc expansion box shows that the disc is removable,
but not writable, and that no errors are present (4109.0001 for SCSI ID of
4, 0100.0001 for SCSI ID of 0, and 1100.0001 for SCSI ID of 1). Any error
code other than those previously listed probably indicates an errov on the
RRD40 box, but never rule out the possibility of an error on the SCSI bus
controller itself.

Expansion Boxes

6-21

If the tests indicate an error on the RRD40 compact disc expansion box,
perform the following steps:
1.

Make sure the expansion box has power and 1s switched on.

Make sure the SCSI cable connects correctly to the external SCSI
port, or to the previous expansion box, and to the back of the RRD40
expansion box.
Make sure the SCSI terminator connects to the unused connector
on the back of the box or that the cable is secured to the next daisychained box.
Run the tests again.
If the problem returns, disconnect the RRD40 expansion box from the
daisy chain or from the SCSI port if no other boxes are connecied.
Install the SCSI terminator on the external SCSI port, and make sure
the last expansion box is terminated correctly. Run self-test (TEST 6).
If the status code is not FFFFFFO05 for the address ID of the RRD40
expansion box (normally address ID 4), check the SCSI address IDs
of all drives on the bus for proper settings. If the address IDs are set
correctly, replace the system module.

If the status code is FFFFFF05, check the address ID switch on the
back of the RRD40 expansion box to make sure 1t is set correctly. See
Figure 6-17 for proper SCSI ID switch settings.
If the address ID is set correctly, a fault in the RRD40 expansion box
or the SCSI cabling exists. Check the cabling for proper connections,
terminations, and damaged pins. If the cabling is good, replace the
RRD40 expansion box.
If a problem still exists, replace the system module in the system box.

622

Expansion Boxes

5.2.2 RRD40 Expansion Box Removal and Replacement
This section describes the removal and replacement procedure for the
RRD40 compact disc expansion box. The RRD40 expansion box is an
FRU. To remove the RRD40 expansion box, set the power switches on
the system unit and all peripherals, terminals, and expansion boxes to
the OFF (0) position, then disconnecting the cables and terminator (if
installed) on the back »f the box. Replace the RRD40 expansion box
by reconnecting the cables and terminator (if installed) on the back of
the box. Then set the SCSI address ID to the same as on the box you
removed. Figure 6—17 shows the default switch settings (ID=4). To test
the box, switch on the power and run self-test (TEST 6) from the s/stem
box.
Figure 6-17

RRD40 Expansion Box SCSI Address 1D Sefting

SC8iiD &

Location of SC81 Switchea

Bajl Lock

Powar Card

Voitage Selecior

Expansion Boxes

6.3

6-23

TKS50Z Expansion Box

The TK50Z-GA expansion box contains five FRUs: the TK50 tape drive, a
TZK50 controller board, a power supply, an SCSI ID switchboard, and a
resistor load beard (to regulate the power supply). Figure 6—18 shows the

TKS50Z expansion box.

Figure 6-18

TKS0Z Expansion Box

TKS0

BLO 003345

The TK50Z expansion box connects to the system box through the externa
SCSI port. The SCSI cable connects to either of the two ports on the back
of the expansion box. The SCSI terminator must be installed on the
unused connector unless another expansion box is daisy chained. If
the external SCSI port already has a box connected to it, you must use
another cable to connect the TK50Z expansion box to the last box on the
daisy chain. Be sure to move the terminator onto the unused connector or

the back of the last expansion box in the daisy chain. Figure 6-19 shows

how the TK50Z expansion box connects to the system box.

6-24

Expansion Boxes

Figure 6-19

TKS50Z Expansion Box Connection

Tarminator

Connector Cable

Power Cord

MLO 002764

6.3.1

Troubleshooting the TK50Z Expansion Box

To troubleshoot the TK50Z expansion box, use the self-test and the system
exerciser diagnostics in the system box. See Section 2.12.3 if you are not
familiar with testing the devices on the SCSI bus.
Self-test results for the TK50Z expansion box should contain 01000001
in the SCSI address ID location of the box (normally address ID 5). The
SCSI address ID is set by the switches on the back of the expansion box.
A code of FFFFFF05 for the TK50Z expansion box address ID indicates
that it is not installed, not powered up, not connected to the external
SCSI port correctly, or fauity. A code of FFFFFFFF indicates that the
device was not tested because of an SCSI bus controller error. Any code
other than those previously listed indicates an error with the TK50Z
expansion box at that address ID location, a cabling problem, or an error
with the SCSI bus controller on the system module.
When running the system exerciser in Field Service mode, the code tor
the TK50Z expansion box shows that it is removable, but not writable

during the first pass (5100.0001 for SCSI ID of 5). During the second
and subsequent passes, the code should indicate that it is removable
and writable (5300.0001) as long as the special-keyed diagnostic tape is
correctly loaded. If the special-keyed tape is not loaded, the 5100.0001
code indicates no errors. Any error code other than those previously listed
probably indicates an error on the TK50Z expansion box, but never rule
out the possibility of an error on the SCSI bus controller itself.

Expansion Boxes

6-25

If the test results indicate a problem in the TK50Z expansion box, the
problem could be the TK50 tape drive, the TZK50 controller board,
the power supply, the system module in the system box, the SCSI ID
awitchboard, or the SCSI cabling.

The following procedure describes how to troubleshoot the TK50Z
expansion box:

Make sure the expansion box has power and is switched on.

Make sure the SCSI port cable connects correctly to the external SCSI
port, or to the previous expansion box, and to the back of the TK50Z
expansion box.

Make sure the SCSI terminator is installed on the unused connector
on the back of the box or that the cable is secured to the next daisy-

Run the tests again.

_C)‘G

chained box.

If the problem returns, disconnect the TKS0Z expansion box from
the daisy chain or from the external SCSI port if no other boxes

are connected. If no other expansion boxes are connected to the
gystem unit, install the SCSI terminator on the external SCSI port.

Otherwise, make sure the last expansion box is correctly terminated.
Run self-test (TEST 6).

If the status code is not FFFFFFO05 for the address 1D of the TK50Z
expansion box (normally address ID 5), check the SCSI address IDs of
all drives on the SCSI bus for the correct settings. If the address IDs
are set correctly, replace the system module.

If the status code is FFFFFF05, check the SCSI address ID switch
settings on the back of the TK50Z expansion box to make sure they
are set correctly. See Figure 6-20 for proper SCSI switch settings.

If the SCSI address ID is set correctly (ID=5), there is a fault in the
TK50Z expansion box. Troubleshoot the TK50Z expansion box using
the box’s internal self-test. See Section 6.3.1.1.

6-26

Expansion Beves

Figure 6~20

TKS50Z-GA SCSI Address ID Switch Settings

123

il
OPEN

VAR

TS 68

.0 002320

6.3.1.1 Troubleshooting Inside the TKS0Z Expansion Box
The TK50 tape drive and the TZK50 controller board perform an internal
self-test every time the tape expansion box is powered up. To do an indepth self-test on the TK50 tape drive and the TZK50 controller board,
perform the following procedure. Do each step indicated until you find

and fix the problem.
The following procedure describes how to troubleshoot inside the TK50Z
expansion box:
1.

Remove the TK50Z expansion box cover.

Check all cables to make sure they connect correctly. Remove the
shield to check the cables on the back of the drive. Note that twe
power cables connect to the resistor load board.
Plug in the power cord and switch on power to the expansion box.
If the LED on the TZK50 controller board and on the TK50 tape drive
does not light when power is first turned on or the fan does not turn,
replace the power supply.

Watch the red light on the TK50 tape drive. It should shut off 5 to
6 seconds after power-up if no tape is installed. If it starts flashing,
replace the TK50 tape drive. If a tape is installed, the red light stays
on.

Expansion Boxes

6-27

Look at the LED on the TZK50 controller board. It turns on at powerup for 2 seconds, then turns off. It must stay off once it turns off. If it
does not stay off, replace the TZK50 controller board.
Insert and load a blank CompacTape cartridge into the tape drive. Do
not use a tape cartridge that contains good data, because the next few
®

Switch off power to the expansion box.

steps will erase the data.

Switch on the power switch.

. Wait about 1 minute for the test to finish. If the LED on the TZK50
controller board starts flashing during or at the end of the test,
ruplace the TK50 tape drive. If the LED does not flash, replace the
TZK50 controller board. If the LED is off, the TZK50 controller board
and the TK50 tape drive are operating correctly. Note that the LED
comes on again at the end of the test for about 2 seconds to indicate
that the testing cycle completed and is starting over again. The test
will continue to cycle until power is switched off and the P5 diagnostic
jumper is removed.
11. Replace the faulty FRU component, if any, and retest.

12 Set up the jumpers on the TZK50 controller board for normal

operation. Spare jumpers must be stored across P5 and one of the
spare posts.

6-26

Expansion Boxes

6.3.2 TKS0Z Expansion Box FRU Locations
Figure 6-21 shows the locations of the FRUs in the TK50Z expansion

box.

Flgure 6-21

TKS0Z Expansion Box FRU Locations

TZK50 Controlier Board

TS0
Resistor Load Board - -—

.L,l m

I(F

Powar Supply

:
e

¥
lfl

) hl
MLO-003346

6.2.3 TK50Z Expansion Box FRU Removal and Replacement
This section describes the removai and replacement procedures for the
FRUs in the TK50Z expansion box. Refer to Table 6-3 to find the name
of the FRU that needs replacing, then go to the section listed beside the
FRU. Follow the steps in the section to remove the FRU and reverse the
procedures to replace the FRU.
CAUTION
Wear a static wrist strap and us~ a static mat when repiacing an
FRU,
Table 6~3

TK50Z Expansion Box FRU Section Listings

FRU

Section

T7K50 coutroller board

6.3.3.1

TK50 tape drive

6.3.3.2

Power supply

6.3.3.3

SCSI 1D switchboard

6.3.3.4

Resgistor load board

6.3.3.5

Expansion Boxes

6-2¢

6.3.3.1 TZK50 Controller Board Removal

Remove the TK50 tape drive as follows:
1.

Switch off power to the expansion box.

Unscrew the four cover screws and remove the expansion box cover.
See Figure 6-22.

Disconnect the data cable (J3), the TK50 tape drive 1/0 cable (J1)
and the power cable (P1) from the TZKS50 controller board. See
Figure 6-23.

Figure 6-22

TK50Z Expansion Box Cover Screws

MLO- 003347

6-30

Expansion Boxes

If the TKS0Z expansion box contains the SCSI 1D switchboard,
disconnect the switchboard cable from the jumper pins on the TZK50
controller board.

Remove the TZIE9 controller board from the shield.
If you are removing the tope drive or the power supply, return to that
procedure now. Otherwise, proceed to the next step.
7.

Replace the TZK50 controller board by reversing the previous
procedure.

Figure 6-23 TZKS0 Conirolier Board Cables
Power Cable

‘

Data Cabie

TK50 170 Gable

E4LO 00338

Expansion Boxes

6-31

6.3.3.2 TKS0 Tape Drive Removal
The following procedure describes how to remove the TK50 tape drive:
1.

Remove the TZK50 controlle: board. See Section 6.3.3.1.

Disconnect the power cable on the resistor load board that comes from
the nower supply.
Remove the five shield screws. See Figure 6-24.

Disconnect the SCSI cable and the terminator, or both of the SCSI
cables from the rear of the TK50Z expansion box.
5.

Lift the shield up and off the chassis.

632

Expansion Boxes

Flgure 6-24 TIKS0Z Expansion Box Shield Screws

MLO-003240

Exparnsion Boxes

6-33

Remove the three drive mounting screws. See Figure 6-25.

Figure 6-25

TKS0Z Expansion Box Drive Mounting Screws

WLO-003350

6-34

Expansion Boxes

S8lide the tape drive out halfway and disconnect the /O cable and the
power cable from the back of the drive, then remove the drive. See
Figure 6-26.

Figure 6-26

Tape Drive Cables

44L.0-003
354

Expansion Boxes

6-35

Remove the four screws and remove the mounting brackets from the
drive. See Figure 6-27.

Flgure 6-27

TKS50 Mounting Brackets Screws

1ALO 003252

Replace the tape drive by reversing the previous procedure.

6.3.3.3 Power Supply Removal
Remove the TK50Z expansion box power supply as follows:
1.

Remove the TZK50 controller board. See Section 6.3.3.1.

Disconiiect the power cable on the resistor load board that comes from
the power supply.
Unscrew the five shield screws. See Figure 6-24.

Disconnect the SCSI cable(s) from the back of the expansion box.
Lift the shield up and off the main chassis.
Remove the three drive mounting screws. See Figure 6-25.

6~36

Expansion Boxes

Disconnect the power cable from the back of ihe drive.

8. Slide the drive back into the box, put the expansion box on its side,
and remove the four power supply screws. See Figure 6-28.

Replace the power supply by reversing the previous procedure.

Figure 6-28

Powar Supply

TKS50Z Expansion Box Power Supply Screws

Expansion Boxes

6-37

6.3.3.4 SCSi ID Switchboard Removal
The SCSI ID switchboard is on the inside back wall of the TK50Z-GA
expansion box. It contains two switch packs. Only one is on the TK50ZGA expansion box, and connects to the jumper connectors on the TZK50
controller board.

Remove the switchboard as follows:
1.

Switch off power to the expansion box.

Unscrew the four cover screws and remove the expansion box cover.
See Figure 6-22.
Disconnect the SCSI ID switch cable from the SCSI ID switchboard.

Remove the two screws from the board and remove the board from the

expansion box.

Set the switch settings on the new SCSI ID switchboard to the same
position as on the old board you just removed. Figure 6-20 shows the
default SCSI ID switch settings (ID=5).

Install the new SCSI ID switchboard by reversing the previous
procedure.

6.3.3.5 Resistor Load Board Removal

Remove the resistor load board as follows:
1.

Switch off power to the expansion box.

Unscrew the four cover screws and remove the expansion box cover.
See Figure 6-22.

Disconnect the two resistor load board power cables. See Figure 6-29.

Remove the resistor load board from the shield.
5.

Replace the resistor load board by reversing the previous procedure.

6-38

Expansion Boxes

Figure 6-29

TK30Z Expansion Box Resistor Load Board Power Cablss

Power Cablos

WiL0O-003354

7
Operating Information
This chapter describes the booting procedures for the MicroVAX 3100,
the VAXserver 3100, and the InfoServer 100 systems and the operating
procedures for the TZ30 tape drive, the RRD490 compact disk drive, and
the RX23 diskette drive.

7.1

Booting the MicroVAX 3100 and VAXserver 3100

The MicroVAX 3100 and VA{server 3100 have internal flags that govern
booting. When the system is shipped, these flags are set so that the
system runs the power-up tests, then halts, displaying the console prompt
(>>>). Use the BOOT command to boot the system from the system disk
(DKA300).
If the system is not new, these flags may have been changed. Therefore,
you need to determine which device you need to boot from before you
can boot the operating system. Enter BOOT and the device-name if you
already know which device you need to boot from, and the system boots
from that device. Enter SHOW DEVICE to view all the devices if you
do not know which device you need to boot from. Figure 7-1 shows an
example of the SHOW DEVICE command.

7-2

Operating Information

Figure 7-1

Example of the SHOW DEVICE Command

>>> SHOW DEVICE

VMS/VMB
o G

o .

ULTRIX
o - e

ADDR

DEVTYP

- -

NUMBYTES
-

- ————

RM/FX

DEVNAM

ESAD

SEO0

08-00-2B-03-79-1F @

DKA300

R2Z3

A/3/0/00

DISK

104.6 MB

MKAS00

T25

A/5/0/00

TAPE

........

A/6

INITR

B/2/0/00
B/3/0/00
B/4/0/00

DISK
DISK
RODISK

104.6 MB
102.4 MB
205
MB

FX
FX
RM

R223
RZ23
RRD40

9/6

INITR

. .HostID....

DKB200
DKB300
DKB400

R210
RZ11
RZ12

...HostID....

R223

32>

® ESA0 — the Ethernet device and the Ethernet address of the system.
@ ...HostID... — the SCSI bus controller.

@ Device numbers for VAX/VMS operating systems.
@ Device numbers for ULTRIX operating systems,
@ Address.
@ Device type.

@ Number of megabytes.
Removable or fixed disk.

@ Write protected.

@ Device name.
The system can include the following devices:

DKAx00! — RZ23 or RZ55 on SCSIA bus

DKBx00' — RZ23 or RZ55 on SCSI-B bus

D' Ax00! — RX23 on SCSI-A bus

DUBx00' — RX23 on SCSI-B bus

! The x indicates the SCSI address ID of the Avive (0 to 7)

Operating Information

ESAQ — Ethernet booting device.

MKAx00' — Tape drive on SCSI-A bus

MKBx00! — Tape drive on SCSI-B bus

7-3

If no device name is specified when entering the BOOT command, the
system checks NVR for a default device and boots off that device. If no

device is stored in NVR, the system automatically assigns ESAQ as the
boot de ice and sends out a boot inquiry over the Ethernet once every
30 seconds for 5 minutes. If no host responds within the first 5 minutes,
the system waits for 5 minutes. The system then starts sending a boot
inquiry again every 30 seconds for 5 more minutes. This pattern is
repeated until a host boots the node or until you press the halt button.

7.2

The TZ30 Tape Drive

The TZ30 is a cartridge tape drive that can store up to 95Mb (or
characters) per CompacTape cartridge or CompacTape Il cartridge. The
TZ30 has the same capabilities as larger tape drives from Digital (such as
TU81) and fits into a half height slot in your system.
The TZ30 can read data from, or write data to, a tape that was written by
a TK50. The TZ30, however, can not read or write data from a tape that
was written by the TK70.

The TZ30 is used primarily to bauckup storage devices, and to load
software onto your system. For cxample, the VMS operating svstem
may be loaded from the TZ3u. The tape-distributed version of VMS is
loaded from a TK50-formatte . ' ape.

In Model 10 systems, the TZ30 tape drive can be accessed directly. To
access the TZ30 tape drive in Model 20 systems, position the system unit
so that the front of it is facing you. Push and then reiease the cover in
the direction indicated by the arrows in Figure 7-2.

7-4

Operating Inforimation

Flgure 7-2

Accessing the TZ30 Tape Drive

T230

Taps Drve

e
WLO-0027

7.2.1 Tape Cartridges

The TZ30 uses a tape cartridge (labeled CompacTape or CompacTape 1I)
that contains the magnetic tape on a single reel. This single reel is an
impertant feature to understand, because it affects the use of the TZ30.
When you insert the tape cartridge into the drive and load it, the tape is
automatically threaded onto a take-up reel inside the drive. When the
tape has been fully wound anto the take-up reel, it can tike up to 100
seconds to rewind completely.

NOTE

The tape must be fully rewound before you can remove the
cartridge from the tape drive.

Operating Information

7-5

7.2.2 TZ30 Controls and Indicators
The TZ30 tape drive has two controls, an unload button and a cartridge
lever, and four indicators, tnree LEDs and a beeper. Figure 7-3 shows the
location of the controls and indicators on the TZ30 tape drive. Table 7-1
provides the functions of the controls and Table 7-2 gives the status
information proviced by the indicators.
Figure 7--3

TZ230 Tape Drive (Front View)

Lever

Write- Protect Light

Tape in Use Light

Coperate Laver Light

Unload Button

MLO-002745

Table 7-1

TZ30 Controls

Countrol

Function

Unload
Button

The unload button rewinds and disengages the tape from the
take-up reel inside the TZ30. The tape must be completely
rewound and unloaded back into the cartridge before the
cartridge can be removed from the drive.

7-&

Operating information

Table 7-1 (Coar)

TZ30 Controls

Control

Fanction

Cartridge
Levey'

The cartridge lever is used to lock or unlock a tape cartridge.
To insert a tape cartridge, the cartridge lever must be in the
unlock positicn. Once a cartridge is inserted and the green
LED lights, move the cartridge lever to the lock position. To
gject the cartridge from the drive, (only when the green LED is
on or blinking, and after the momentary beeper sounds), move
the cartridge lever to the unlock position.

'When using the cartridge lever, be sure it i8 completely positioned in the lock or unlock
position before beginning the next operation.

Teble 7-2

TZ30 indicators

Indicator

State

Condition

Green LED - Lever

OK to operate the cartridge lever.

Off

Don’t operate the cartridge lever.

Blinking

Yellow LED - Tape in

The drive has detected a cartridge or

calibration error.

Blinking'

Tape in use®.

Tape loaded and ready for use.

Tape is write protected.

Off

Tape is write enabled.

Al three LEDs

The power-up diagnostic is in progress’.

All three LEDs

Blinking

Drive fault.

Use

Orange LED - Write
Protected

Vintermittent fast blinking indicates that a write is in progress. Continuous fast blinking
indicates that a read is in progress. Medium blinking indicates calibration. Slow blinking

indicates that the tape is initializing, loading, unloading or rewinding.

2LED blinks slowly for 10 seconds indicating drive initialization. This occurs only on
power-up after the power-up diagnostic has run.

3All three LEDs light for a few seconds as the power-up diagnostic is running. If all three
LEDs stay on, the power-up diagnostic has failed.

Operating Information

Table 7-2 (Cont.)

7-7

TZ30 indlcaiors

Indicator

State

Beeper®

Two beeps

Condition

Indicates that the tape is unloaded and

can be removed from the drive.

“The drive beeps once when it is powered-up. If a tape cartridge is not locked in the drive,
it will beep twice after self-test diagnostics and drive initialization are completed. If a tape
- artridge is locked into the drive before power-down, then upon power-up the drive will
beep once and attempt to load the tape cartridge.

7.2.3 TZ30 Operation
Before inserting a new cartridge in the tape drive, open the cartridge doo

and inspect the position of the leader. See Figure 7—4.
Figure 7-4

TK50 Tape Cartridge Door

D100 LOCI es e e e /
(Release by L thing

Door Lock With Thumb)

\
MLO-002748

Before using the TZ30 for the first time, check the position of the takeup leader in the TZ30. Figure 7-5 shows some potential misalignments
and how to fix them. Use a small nonmetallic instrument to realign the
take-up leader if necessary.

7-8

Operating Information

7.2.3.1 inserting and Using the Tape Cartridge

To insert a tape cartridge, perform the following steps:
1.

Be sure thsi i cartridge lever is in the unlock position.

Insert the tape cartridge.

Once most of the cartridge is inserted into the drive, you must

complete this procedure. If you wish to use arother cartridge,
somplete this procedure and perform the unload procedure to remove
the tape cartridge.

If the ters cartridge cannot be inserted into the TZ30, move the
cartridge lever to the lock position. Now move the cartridge lever
back to the unlock position and reinsert the cartridge. Do not push
the tape cartridge into the TZ30 while moving the cartridge lever

between the lock and unlock positions. Otherwise the TZ30 interprets
this as an insertion of the tape cartridge.
The green LED will light.

Move the cartridge lever to the lock position to lock the tape cartridge
in the drive. The green LED turns off and the yellow LED begins to
blink, indicating that the tape is loading. When the tape is loaded
(ready for use), the yellow LED stays on steadily. Whenever the
yellow LED is on steadily and the green LED remains off, the tape is
ready to use.

If the write protect switch un the cartridge is in the protected position,

the orange write protect LED is on and you will be unable to write data
to the tape. If you move the write protect switch to the write enable
position during operation, the system software does not recognize the
fact that the tape is no longer write protected. You must reload the tape

cartridge again before the system software recognizes tue cartridge as
write enabled.

Similarly, if you move the write protect switch from the write enabled
position to the write protected position during operation, the tape is
not actually write protected until the operating system dismounts and
remounts the tape.

When the yellow LED is on steadily, you can proceed with your operation.
For example, you may boot your operating system, or possibly, back up
files onto the TZ30. Refer to your system documentation for instructions
for these and other operations.

‘

Operating Information

Figure 7-5

7-9

TZ30 Take-Up Leacer Adjustment

Taue up ' eadaer
Locshon

Cotrect Location of Leadar
Tahe-up

Buckling
Link

Leadsr

> Accoptable

Leadur Unhooked

Tako up
Leadar

Unaccopiable

A X080 88BA

When the tape drive is reading, writing, or rewinding a tape cartridge,
the yellow LED blinks rapidly.

7-10

Operating Information

If errors occur during an operation, all three LEDs blink. The green LED
will blink if a faulty tape cartridge is inserted.

Flgure 7-6

Inserting a Tape Cartridge

Levar

MLO-002748

7.2.3.2 Removing a Tape Cartridge from the Drive

The following procedure describes how to remove a tape cartridge:
1.

Press the unload button (Figure 7-7) or issue the appropriate system

software command. e yel..w LED will flash as the tape rewinds.
Once the tape has rewound completely, the beeper sounds twice and
the green LED will light.

NOTE

If you use the DISMOUNT command from the console,
you do not need to press the unload button. If you use
the /NOUNLOAD qualifier with the DISMOUNT command,
you must preas the unload button. If you do not use the
/NOUNLOAD qualifier with the DISMOUNT command, you
will receive a “device not software enabled” message from the
operating system since the tape will unload. If this occurs, you
will have to physically remove the cartridge and reload the
tape drive to recover.

Move the cartridge lever to the unlock position.

Operating Information

7-11

3. The cartridge ejects and can pe removed from the tape drive.

CAUTION

Remove the tape cartridges from the drive before turning off
the drive’s power. Failure to do this can result in damage to the

cartridge and tape drive.
Figure 7-7

Removing a Tape Cartridge

MLO-002747

7.2.4 RX23 Diskette Drive
Depending on the configuration, your system may include one or two

RX23 diskette drives. These devices enable you to read information from
and write information to 3.5 inch removable diskettes.

In Model 10 systems, the RX23 diskette drive can be accessed directly. To
access the RX23 diskette drive in Model 20 systems, position the system
unit so that the front of it is facing you. Open the cover by pushing it in
the direction indicated by the arrow in Figure 7-8 and then releasing it.
Use the same procedure to close the cover when you have finished using
the RX23.

7-12

Operating Information

Figure 7-8

Accessing the RX23 Diskette Drive

AX23
Digkette Drive

MLO-002789

NOTE
The RX23 diskette drive is shown in the right compartment. It
may also be installed in the left compartment.

7.2.4.1 Diskettes

The RX23 diskette drive uses RX23K diskettes which have a capacity of
1.4Mb.

‘

Operating Information

7-13

7.2.4.2 Inssrting a Diskette
The drive can hold one diskette.

CAUTION

Never remove or insert a diskette while the diskette drive is

performing a function. Inserting or removing a diskette while
your system is using the disketie can cause incorrect data to be
written to the diskette, and can cause damage to the diskette
itself. Wait until the diskette drive finishes doing whatever you
requested it to do. When the diskette drive is in use, the green
light on the front of the diskette drive is on.
To insert a diskette into the diskette drive slot, slide the diskette into the
drive, as shown in Figure 7-9.
The diskette slides straight in and drops down to its load position.
Figure 7-9

Inserting a Diskette

Diskatte

MLO 002770

7-14

Operating Information

7.2.4.3 Removing a Diskette

You must dismount the diskette drive before removing a diskette. For
information on dismounting, see your software documentation.

To remove a diskette from the diskette slot, push the eject button in the
lower right side of the diskette drive, as shown in Figure 7-10.
Figure 7-10

Removing a Diskette

Diskatte
Ejection Button

MLO-002038

Operating Information

7.3

7-15

The RRD40 Compact Disc Drive

The RRD40 is available in the InfoServer 100 system and as a ¢ ssktop
expansion box. Figure 7-11 shows the RRD40 expansion box.
Figure 7-11

RRD40 Compact Disc Expansion Box

Opaning tor Compaci Disc

Activity Light
Powar Light

MLO-000971

7.3.1

Front Panel of the RRD40 Expansion box

The front panel consists of a disc access door, an activity indicator, and
a power indicator. See Figure 7-11. The activity indicator lights when a
disc is correctly loaded into the RRD40 drive. The indicato: flashes when
the disc is transferring data. The power indicator lights when power is
on.

7.3.2 Loading a Disc
When loading a disc, the entire disc caddy is inserted into the disc access
door on the drive.
CAUTION
Do not remove the disc from the caddy.
The following procedure describes how to load a disc:
1.

Make sure the power is on.

7-16

Operating Information

Examine the disc caddy. Make sure that it is ot cracked or damaged
in any way. Never load a damaged caddy into an RRD40 drive.

Examine the disc inside the caddy. Note that one side is labeled. The
lahel shonid always be facing up as you insert the disc into the drive.
When the label is facing up, the four notches on the disc housing are
on the left. See Figure 7-12. These notches line up with the four
siinilar notches on the front of the RRD40 drive.
NOTE

If you have the disc positioned label side up and the notches
are on the right, then the disc is oriented incorrectly in
the caddy. Proceed no further with the disc loading. See
Section 7.3.4 and repair the disc and the caddy.
Insert the disc caddy. See Figure 7-12. Line up the notches on the
caddy with the notches on the disc access door. Slide the caddy in as
far as it will go and then remove it. When removed, notice that the
disc and its housing remain in the drive. Only the transparent sleeve
comes out.

Check that the front panel activity indicator lights within 5§ seconds.
If the drive accepted the disc and the activity indicator does not light,
then the disc may have been orientated in the caddy incorrectly.
Unload the dise using the instructions in the following section. Refer
back to step 3 and examine the disc orientation in the caddy. If the
disc is orientated correctly, the RRD40 drive may be faulty.

7.3.3 Uniloading a Disc
Before unloading a disc, make sure that the activity indicator is not
flashing. If it is flashing, then the RitD40 is transferring data. Wait until
the indicator stops flashing.
The following procedure describes how to unload a disc:
1.

Orient the transparent sleeve for loading. Make sure the arrow
is going into the drive first. See Figure 7-12 for guidelines (the
unloading procedure 1s the same as the loading procedure).
Insert the sleeve into the access door as far as it will go.

Remsve the c23dy. The disc and housing will be back in the sleeve.
The activity ndicator will go out.

Operating Information

Flgure 7-12

RRDA40 Compact Disc Loading

4.0 003293

7-17

7-18

Operating Information

7.3.4 Disc and Caddy Repair
The RRD40 media is contained inside a protective caddy. The caddy
consists of three parts: the disc, the disc housing, and the transparent
sleeve. See Figure 7-13.
Figure 7-13

Dlsc Parts

Lacking Tabs

Housing

Transparant Sigove

MLO-001008

If the transparent sleeve is damaged or cracked or if the disc needs
cleaning, the caddy can be taken apart.
It is very important that the disc is mounted in the caddy correctly.
Failure to mount the disc correctly makes the disc inaccessible to the
SCSI bus controller.

Operating information

7-19

7.3.5 Removing the Disc from the Caddy
To remove the disc from the caddy for cleaning or caddy repair, proceed as
follows:
1.

Hold the caddy so that it is facing label side down. Locate the locking
tabs on either side of the disc housing. See Figure 7-13.
For each locking tab, press down on the tab while slightly separating
the housing from the sleeve. Use your fingernail or a sharp, pointed
instrument.

When both tabs have been disengaged, pull the disc housing out to
about the midpoint of the disc. See Figure 7-14.
Figure 7-14

Sep rating the Disc from the Caddy

KLO-003360

Hold the disc housing on each side. See Figure 7-14. Exert inward
pressure on the housing so the disc does not fall out. Remove the

sleeve from the housing. Place the sleeve aside.
Grasp the disc with your free hand. See Figure 7-15. Position your
thumb on the outer edge of the disc and your index finger in the
center hole of the disc. Release pressure from the housing and remove
the disc.

7-20

Operating Information

Flgure 7-15

Removing the Disc

MLO-000975

7.3.6 Cleaning a Disc

The disc can be cleaned with a dry, lint-free cloth. The disc should always
be free of dust, dirt, and fingerprints. Always hold a disc by the edges.
Never touch the data area of the disc.

To clean, wipe from the center of the disc to the edges. Use amall circular
strokes.

CAUTION
Do not use a continuous circular stroke around the disc.

7.3.7 Replacing the Disc In the Caddy
Assembling the caddy is essentially the reverse of the removal procedures.
Make sure that your hands are positioned as shown in the illustrations.
It is very important that the disc is replaced correctly.

The following precedure describes how to replace a disc in a caddy:

1.
2.

Position the housing and disc. See Figure 7-15. Always work with

the disc so the label is facing down.

Insert the disc into the housing. The inside of the housing is grooved
to accept the disc. Exert inward pressure to hold the disc in the

housing.

Operating Information

7-21

Slide the housing into the transparent sleeve all the way until it clicks
into place.

Turn the assembly over so that the label on the disc is facing up.
Make sure that the notches on the housing are on the left. If the
notches are not on the left when the disc is label side up, then the
disc is mounted incorrectly inside the caddy. Remove the disc from
the caddy and reorientate the disc.

7.4

TK50Z Tape Expansion Box

The drive unit (TK50) is located behind a protective door; it holds one
removable TK50-K or TK52-K magnetic tape cartridge. Use the tape
cartridge to load software, data files, or to make copies (or backups) of
your files.

The TK50Z tape drive has two primary controls: the cartridge release
handle and the load/unload button. The cartridge release handle allows
cartridges to be inserted, locked into position, and removed. The load
/unload button controls winding and rewinding of the tape. The in (on)
position of the load/unload button is for loading tape cartridges. The out

(off) position is for unloading tape cartridges.

7.4.1

Inserting a Tape Cartridge

Make sure the load/unload button is in the out (unload) position.
The red load/unload button comes on for approximately 4 seconds during
the tape drive automatic power-up test.
The red light goes off and the green light comes on, indicating that it is
safe to move the cartridge release handle.

If a cartridge is new, the tape drive performz a calibration sequence that
takes approximately 40 seconds. The green light flashes rapidly ar |
irregularly during calibration.

CAUTION
Do not move the cartridge release handle unless ihe red light is
off and the green light is on.

Do not move the cartridge rclease handle while either light is
flashing.

If the red light flashes rapidly at any time, press the load/unload
button four times. If the problem persists, do not attempt to use
the tape drive and do not remove the cartridge.

7-22

Operating Information

Figure 7-16 shows you how to insert and load a tape cartridge.
Figure 7-16

Inserting and Loading a Tape in the TK50Z Expansion Box

Raige the cartridge

Cartridge
Release Handle

release handle.

With the arrow on the cartridge
tacing up and pointing into the

Cartridge
Arrow Is Facing Up

drive, tnsart the cartridge nto

the drive. The red hight comas
on and the gresen hight goes ofi.

Note
Make sure that the Load/Unload

Green Light

button is 1n the 'OUT" position

Red Light

before pushing -

o tape.

Lower the cartridge release
handie.
Tha rec hght goes off
and the grean hight comes on

Note:
Wait until the red tight goes off
betors prassing the Load button

=
Push the load/unioad button to
the 'n (load) position

Loasd/Unioad
Button ls In

The

red light comes on and stays
on. The green light bhnks and
1

then siays on, indiceting that

the cartridge is ready for use.

MLO-002064

‘

Operating Information

7-23

7.4.2 Summary of TKS0Z Controls and indicator Lights
Table 7-3 summarizes the function of the TK50Z controls.
Table 7-3

Function of TK50Z Physical Controls

Control

Position

Function

Load/unload

Loads the tape (10 to 15 seconds).

Out

Rewinds and unloads the tape.

Allows you insert a tape or remove a tape after
rewind and unload operations are completed.

Down

Locks tape in operating position.

button

Cartridge
release
handle

Table 7-4 summarizes the function of the TK50Z indicator lights.
Table 7-4

Function of TKS0Z indicator Lights

Green light

Red light

Function

Off

No power to the tape drive.

Off

Safe to move cartridge release handle. Power
i8 present.

Off

Do not move the cartridge release handle. One

Tape loaded successfully.

Flashing

Tape is in motion ‘except rewind). Read/write

of the following conditions is in effect: powerup test is occurring; cartridge is inserted but
handle is still up; tape is loading or unloading;
tape is stopped.

commands are being processed. Irregular fast
flashing of green light means tape calibration
is occurring (first use of tape).

Flashing
slowly

Off

Flashing

Tape is rewinding.

Flashing

Tape or drive fault exists.

slowly

rapidly

7-24

Operating Informatior,

Flgure 7-17

Unloading and Removing the TK50 Tape

1
Release the load/unioad button

Load/Unioad

to the out (unload) position.

Butten is Out

The red and green lights tash

slowly as the tape rewinds

When the tape is complately
unlogded, the red light goes oft
and the green light comes an.

Raise tha cartridge
release handle.

Remove the taps cartridge
and store it in its plastic
container

Lower the cartridge
relgase handle

7.4.3 Removing a Tape Cartridge
Tape cartridges must be unloaded (rewound) before being removed from
the drive. Rewinding a tape can be done under software control. Refer
to

your software documentation for information. Figure 7-17 shows how
to
remove a tape cartridge.

8
InfoServer 100

8.1

Enclosure Description

The InfoServer 100 system box is a 13.3 cm (5 % in) high box, the same
as used on the MicroVAX 3100 Mode! 20 or the VAXserver 3100 Model 20,
described in Chapter 5. The InfoServer 100 system has one or two RRD40
or RRD42 compact disk drives behind the front panel of the system unit
(Figure 8-1).
The InfoServer 100 contains the following FRUs:
¢

KA41-CA CVAX system module

H7822 or H7083 power supply

Either A or P below:
A.

1 or 2 RRD40 compact disk drives, plus 1 or 2 controller modules

1 or 2 RRD42 compact disk drives, with integral controller.

RZ23E 104-Mbyte or RZ23L 121-Mbyte hard disk drive

Battery pack

8-2

InfoServer 100

Figure 8-1

InfoServer 100 Front Panel
Drive Labals

Compact
Disc Drive

Compact

Dise Drive ___ .

S
...

Ethernot

Address Labe!
LJ- 00083 Ti0

A with the MicroVAX 3100 and the VAXserver 3100, one can connect

additional mass storage devices to the InfoServer 100, such as:
o

RZ55, RZ56 hard disk drive expansion box

RRD40, RRD42 compact disk expansion box

Refer to Appendix H for a complete list of FRUs for the system box and

for the expansion boxes.

The InfoServer 100 has various models, listed in Table 8-1. The newer
models have integral CD controllers and therefore, do not require the
extensive cabling required of the older models. To identify the number of

components inside the box, refer to the mode!l number on the back of the
system box. (Also refer to the MicroVAX 3100/ VAXserver 3160/ InfoServer
ifi()fl Systems Illustrated Parts Breakdaown, EK-A0372-1P revision 003 or
igher.)

InfeServer 100

Table 8-1
Model

8-3

InfoServer 100 Mode! Varlations
CD ROMs

Hard
Disk

Power
Supply

CD Cable

H7822

50-conductor,

Older Models

SEABB-AX

1 RRD40-EG

RZ23L
or

multiconnector,

RZ23E

flat cable,

17-02909-01-A01

SEABC-AX

2 RRD40-EG

RZ23L

H7822

+
Multiconnector,

RZ23E

50-pin,

rounu cable,
17-02297-01

SEABB-BX

1 RRD<2-GM

RZ23L

H7822

SEARC-BX

2 RRD42-GM

RZ23L

H7822

Newer Models

SEABB-CX

1 RRD42-GM

RZ23L

H7083-BA

50-conductor,
multiconnector,
17-02909-01-B01
+

SEABC-CX

2 RRD42-GM

RZ23L

H7083-BA

2-connector,
50-pin,

round cable,
17-03209-01

8-4

InfoSearver 100

8.1.1 InfoServer 100 System Box Back Panel
Figure 8-2 shows the back panel of the InfoServer 100 system box.
F'gure 8-2

InfoServer 100 Back Panel
Powear On/Off Switch Power Connector

SCSI-B Port ————-\
Reserved

Hait Button

l__ AND
=
’

Net Select Indicators

() [t

Standard Ethernet Port —yeE

Eihernet Switch

ThinWire Ethernet Port

—
=

OO . pless
LN

—

\M Diagnostic LEDs

Break Enable Switch

M Port 1

(na: Usefi)

Modem Port

MMJ Port 2

ot used)

(not used}

MMJ Pont 3 -

1J-00068-TI0

MM Port 1

You can connect VTwx terminals to the InfoServer 1060
through the MMJ port 1. This port is pre-set to run at
9600 baud, so any terminal connected to this port must
be set at 9600 baud.

You can use this port to connect a terminal to the server
to establish a local server management system. (See
the InfoServer 100 System Operations Guide for more
information.)

Modem Port,
MMJ Ports 2 & 3

The modem port and MMJ Ports 2 and 3 are not used or
supported by the server.

infoServer 100

Ethernet Ports

8-5

Connection to the Ethernet network is done through

either the Standard Ethernet connector or through
the ThinWire Ethernet connector. The position of
the Network Select Button determines which port is
enabled. An LED is lit beside the enabled port. Each
port provides IEEE 802.3 network communications.

SC8I Connectior

The external Small Computer Systems Interconnect
(SCSI) port is used to connect external mass storage
devices to the system. You can connect up to six external
drives to the server.

Break Enable

The position of the Break Enable Switch at power up
determines the function of the terminal attached to
MMJ Port 1. When the switch is up, you can press the
Break key on the console to enter console mode directly.

Power Supply

The power supply accepts inputs in the ranges of 100
Vac to 120 Vac and 200 Vac to 240 Vac, at 50 or 60 Hz.
A selection switch is not needed.

Switch

8.2

RRDA40 or RRD42 CD Drives

The RRD40 CD drives are used on earlier models. Each drive requires an
RRD40 controller module. Either one or two CD drives can be installed
on the lower drive mounting prnel. The right-hand drive (as viewed from
the front) is connected to the SCSI-A bus; the left-hand drive is connected
to the SCSI-B bus. Figure 8-3 shows the drive mounting panel power and
signal cabling for -AX Models.

InfoServer 100

Figure 8-3

Power and Signal Cabling for -AX Models
RRD40-AA
Controllars

SCsi B

:"'.'

To CPU

t scsiA

Power

Supply

RRD42

CD Drive

—

Terminator

B o

wmmmm Data
EzmmTa

Power

RZ23
Disk

Drive

L4-00969-T10

infloServer 100

8-7

The RRD42 CD drive is used on later model=. It has an integral
cuntroller, so no external module is needed. Figure 8-4 shows the power
and signal cabling for -BX and -CX Models.
Figure 8-4

Power and Signal Cabling for -BX and -CX Models
SCSi B

CPU SCSI

Power

Supply

RRD42
CD Drive

RRD42

CD Drive

1 Terminator

RZ223
Disk

Drive

Data

cmmEEn

Power

tJ 00970 TI0

8-8

InfoServer 100

8.3

FRU Removal and Replacement

This section describes the remova! and replacement procedures for the
FRUs in the InfoServer 100 system. For removal procedures that are
the same as the MicroVAX 3100 Model 20, a reference is made to that
procedure in Chapter 5, rather than repeating it here.

Refer to Table 8-2 to find the name of the FRU that needs replacing; 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. Test the replaced device for correct operation.

CAUTION
Wear a static wrist strap and use a static mat when replacing

FRUs.

Table 8-2

infoServer 100 FRU Section Listing

FRU

Section

Cover

Section 8.3.1

Upper drive mounting panel

Section 8.3.2

RRD40 controller

Section 8.3.3

Lower drive mounting panel

Section 8.3.4

CD Drive Removal

Section 8.3.6

RRD42 CD Drive Removal

Section 8.3.6

RZ23 disk drive

Section 8.3.7

System module

Section 8.3.8

Battery pack

Section 8.3.9

Power supply

Section 8.3.10

infoSarver 100

8-9

8.3.1 System Box Cover Removal
Remove the system box cover as follows:
Turn the system power switch off.

Disconnect all the cables connected to the system unit.

Loosen the two cover screws on the rear panel of the system box. See
Figure 8-5.

Slide the cover forward and up off the system box.

Figure 8-5

Cover Screw Locations

Qo
N

L4-00971-T10

8-10

IntoServer 100

8.3.2 Upper Drive Mounting Panel Removal
The upper drive mounting panel contains the RZ23 hard disk drive.
Remove the upper drive mounting panel as follows:
Remove the system box cover. See Section 8.3.1.

2. Disconnect the power cables and the SCSI bus cable from the RZ23 on
the upper drive mounting panel.

Unscrew the four captive screws. See Figure 8-6.

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

Figure 8-5

Unscrewing the Upper Drive Mounting Panel

Upper Drive
Mounting Panel

' Captive

Screws (2)
LJ4-00872-TWO

InfoServer 100

8-11

8.3.3 Removing the RRD40 Controller(s) (if present)
InfoServer 100 model SEABB-AX has one RRD40 controller medule.
Model SEABC-AX has two controller modules, one mounted component
side up, the other mounted component side down on top of the other using
a standoff.
CAUTION
Note which cable connectors connect to which drive and
connector before disconnecting them. To help in reassembly, use
a piece of tape on each connector and cable and note its position
before disconnecting the cable.

Use the procedure that follows to remove the RRD40 controllers. If your
unit only has one controller, skip steps that do not apply.
Remove power and data (50-pin) from RZ23.
Remove the upper drive mounting panel (Section 8.3.2).

Disconnect the cable(s) from the RRD40 CD drive(s).
Disconnect the 50-conductor, flat cable from the top RRD40 controller.
If replacing the cable, remove the SCSI terminator from the end of the
cable and install it on the new cable.

Loosen the top RRM10 controller module from the standoffs at each
corner and lift off the controller module.

Unscrew the standoffs from the corners of the lower RRD40 controller
module.

Disconnect the flat cable from the bottom RRD40 controller module.

8-12

IinfoServer 100

Figure 87

Removing the RRD40 Controller Module(s)

§0-Conductor
Flat Cable
SCSi
Terminator

To 50-Conductor
Round Cable

Connects

Te RZ23

0 -AA Controller

Connects To

CD Drive{s)

S (Comp onent Side Up)

Lower Drive Mounting TM
Panel (Shelt Assembly)

| !; ' l “! l l' gg
|‘ flflgu
4

Standotf

/ RRDA0-AA Controlier
(Component Side Down)

LJ-00046-1

infoServer 100

8-1:

8.3.4 Lower Drive Mounting Panel and CD Drive Removal
The lower drive mounting panel contains either one or two RRD40 CD
drives or one or two RRD42 CD drives, depending on the model of the
InfoServer 100 system. See Table 8-1.
Remove the lower drive mounting panel as follows:
1.

Remove the upper drive mounting panel if not already removed. See
Section 8.3.2.

Disconnect the SCSI and power cables connected to the drives on the
lower drive mounting panel (Figure 8--8).
Unscrew the seven screws.

Slide the panel forward with the CD drives attached; then, lift the
panel from the system box and gently set it aside.

8-14

InfoServer 100

Figure 8-8

Removing the Lower Drive Mounting Panel

GCaptive Screw (1)

Captive Scraws (3)

Lower Drive Mounting Panel

Panhead Screws
(3 Loosened)
LJ-00973.7i0

8.3.5 Remove the CD Drives from the Lowar Drive Mounting
Panel
Use the following procedure to remove the CD drives from the lower drive
mounting panel.

Remove the outer two screws and grommets that secure the CD drive

to the lower drive mounting panel. See Figure 8-9.

Loosen the inner two screws that secure the CD drive.

Slide the drive backward and lift it out of its slots on the lower drive
mounting panel.

NOTE
When installing the new CD drive, make sure you instaii the
rubber gromrmets on each screw before installing the screws. The
grommets may have stuck to the drive mounting parel.

infoServer 100

Figure 8-9

Grommet

Screw

8-15

Removing CD Drive from the Lower Drive Mounting Panel

Lower Drive Mounting

Tanel (Shelt Assembly) y

LJ~00047
-1

8-16

InfoServer 100

8.3.6 RRD42 CD Drive Removal
Remove the RRD42 CD drive as follows:
1.

Remove the upper drive mounting panel if not already removed. See
Section 8.3.2.

Disconnect the SCSI and power cables connected to the drive on the
lower drive mounting panel.

Remove the CD drive(s) per Section 8.3.5.

8.3.7 RZ23 Disk Drive Removal
An RZ23 hard disk drive is installed on the upper drive mounting panel.
The RZ23 contains a drive module/frame, which must be removed before
replacing the drive. The head/disk assembly inside the drive is not a
FRU, so replace the drive as one FRU.
Refer to Chapter 5, Section 5.2.5, for removal of the RZ23 disk drive and
drive module/frame.

8.3.8 System Module Removal
The InfoServer 100 system module (KA41-CA) is removed using the same
procedure as that of the MicroVAX 3100 or the VAXserver 3100 Model 20
system module, so you can use that procedure to remove the KA41-CA
system module. Install the new board as is; no jumpers or switches need
to be changed. See Chapter 5, Section 5.2.10.

8.3.9 Battery Pack Removal
See Chapter 5, Section 5.2.11.

8.3.10 Power Supply Removal
See Chapter 5, Section 5.2.12.

A
Console Test Commands
There are two types of consc ‘e test commands, diagnostic test commands
and utility commands. Table A-1 gives a complete list of the diagnostic
test commands. See Chapter 1 for a detailed description of these
commands. Table A-2 gives a complete list of the utility commands.
See Chapter 3 for a detailed description of these commands.
Table A-1

Test

Dlagnostic Test Commands

Description

Self-test for future option—no test run.

Self-test on time-of-year clock (CLK).

TMD

Self-test on nonvolatile RAM (NVR).

Self-test on serial line controller

Self-test on system memory (MEM).

Self-test on memory management unit (MM).

Self-test on floating point unit (FP).

Self-test on interval timer (IT).

Self-test on the SCSI-A bus.

Self-test on the SCSI-B bus.

Self-test on interrupt controller and Ethernet ID ROM (SYS).

Test DSH32-B communications module async. lines.

Test DSH32-B communications module sync. lines.

Self-test {for future option—no test run.

(DZ).

Console Test Commands

A-2

Table A-1 (Cont.)
Test

Diagnostic Test Commands

Description

Ssif-test on the Ethernet circuits (ND.

Customer mode system exerciser.

T 101

Field Service mode system exerciser (two passes).

T 102

Field Service mode system exerciser (continuous).

Manufacturing mode system exerciser.

Selscts individual devices for exerciser tests.

80000103
80000106

Table A-2
Test

Utllity Commands
Description

T 50

Configuration display.

T 51

Set NVR default boot device.

T 52

Set NVR default boot flags.

T 53

Set NVR default recovery action flags.

T73

Snecial key on CompacTapes.

T 74

Special key on diskettes.

T 76

SCSI disk data eraser.

T 76

SCSI diskette formatter.

Console Commands

B.1
@

Console Command Syntax
The console program accepts commands up to 80 characters long.
Longer commands result in an error message. The character
count does not include rubouts, rubbed-out characters, or the
terminating RETURN.
Type-ahead is not supported. The system disregards most
characters received before the console prompt (>>>) appears
on the screen. The following control sequences are exceptions:
CTRL/S, C FRL/Q, and CTRL/C.
Commands can be abbreviated by typing the first character in
the commr.and name. Most commands are recognized by their
first character. For example, B stands for the BOOT command
and T stands for the TEST corimand. The exceptions are DTIE],
HEILPI, SEIT|, and SHIOW|.
The console program treats multiple adjacent spaces and tabs as a
single :pace Leading and trailing spaces and tabs are ignored.

Command qualifiers can appear after the command keyword or
after any symbol or number in the command.
All numbers (addresses, data, and counts) are hexadecimal except
for symbolic register names which are decimal.
The console program accepts uppercase and lowercase letters.

B-1

B-2

Console Commands

B.2

Conscle Commands

The following sections describe the console commands:

B.2.1

BOOT

>>> BOOT [<qualifier>]i<device_name>]

The boot program is called Virtual Machine Boot (VMB). The console
program intializes and starts VMB running.

Qualifier
/Rb5:<data> - After initializing the processor and before starting VMB,
R5 is loaded with the specified data (in hexadecimal). This allows a
console user to pass a parameter to VMB.
Device_nxme
VMB boots the operating system from the device specified in the
<device_name>. The device_name is in the form LLLD, where the
first three characters arc uppercase letters and the fourth character
is a digit (0 through 9). A terminating colon in the device_name
is acceptable, but 1s not required. Devices for MicroVAX 3100 and
VAXserver 3100 systems are listed as follows:

Table B-1

System Device Names

Name

Deucription

DKAx00

RZ23 on SCSI-A bus at address [D x (0 to

MKAx00

TZ30 on SCSI-A bus at address ID x (0 to 7).

DUAx

KX23 on SCSI-A bus at address ID x (0 to 7).

ESA0

Etharnet booting device.

DKBx (0

RZ23/RZ55 on SCSI-B bus at address ID x (0 to 7).

MKBx00

TKB0Z on SCSI-B bus at address ID x (0 to 7).

DUBx

RX23 on SCSI-B bus at address ID x (0 to 7).

Enter the SHOW DEVICE command to see the list of devices installed
in the system.

Console Commands

B-3

If no device_name is specified, the console program automatically
assigns ESAQ as the boot device and sends out a boot inquiry over
the Ethernet once every 30 seconds for 5 minutes. If no host responds
within the first 5 minutes, the console program waits for 5 minutes
without sending out a boot inquiry. The console program then starts
sending a boot inquiry again every 30 seconds for 5 more minutes.
This pattern is repeated until a host boots the node or until you press
the halt button.

B.2.2 COMMENT
>>> ! <comment>

The COMMENT command (the exclamation point) is ignored by the
console program. It is used to annotate console I/0 command sequences.

B.2.3 CONTINUE
>>> CONTINUE

The processor begins instruction execution at the address currently

contained in the program counter. The address in the program counter
is the address that was saved when the conscle program was started
or is the address that was entered by the operator using the DEPOSIT
command. Processor initialization is not performed. The console program
enters program /O mode (operating system such as VMS or Ultrix).

B.2.4 DEPOSIT
>>> DEPOSIT [<qualifier>-j <address><data>

Deposits the data into the specified address. If no address space or data
size qualifiers are specified, the defaults are the address space and data
size used in the last DEPOSIT or EXAMINE command. After processor
initialization, the defauli address space is physical memory, the default
address is zero, and the default data size is longword.

Qualifiers
¢

/B — The data size is byte.

(/W — The data size is word.

/L — The data size is longword.

B-4

Console Commands

[V — The address space is virtual memory. !f memory

mapping is not enabled, virtual addresses are equal to

physical addresses.

/P — The address space i3 physical memory.

/I — The address space is internal processor registers.

/G — The address space is the general registers (RO through

/M — The address space is the machine register.

/U — Enables access to conscle program memory.

/N:<count> — The address is the first address in a range of
uddresses specified in count. The console program deposits
the <data> to the first address and then to the specified
number of succcedin, addrescc¢s. Even if the address is the
symbolic addvess "-", the su-ceeding addresses are at the
larger addresses. The symbolic address specifies only the
starting address, not the direction of successioi. For repeated
references (o preceding addresses, use "Repeat Deposit <data>".

R15).

Address
*

Processor siatus longword (PSL) — The address space is set to
/M automatically. Do not specify any address space qualifier:
with PSL.

Program counter (PC) (general register R15) — The address
space is set to /G automatically.

* Stack pointer (SP) (general register R14) — The address space
is set to /G automatically.

General register (RN) — The register number is in decimal.
The adaress space is /G.

+ (plus) — The location immediately following the last
location referenced in a DEPOSIT or EXAMINE command.
For references to physical or virtual memory spaces, the
location referenced is the last address plus the size of the last
reference (1 for byte, 2 for word, 4 for longword). For other
address spaces, the address is the last address referenced plus
one,

‘

Console Commands

B8-F

. (minus) — The location immediately preceding the last
location referenced in a DEPOSIT or EXAMINE command.
For references to physical or virtual memory spaces, the
location referenced is the last address minus the size of this
reference (1 for byte, 2 for word, 4 for longword). For other
address spaces, the address is the last address referenced
minus one.

* (gsterisk) — The location last referenced in a DEPOSIT or

EXAMINE command.

@ (at sign) — The location addressed by the last location
referenced in a DEPOSIT or EXAMINE command.

Data

B.25

The data is specified as a hexadecimal number. The default
number is zero.

DTE

>>> DTE

Converts the system into a dumb terminal emulator connected over a
serial line. This command is used when the boot node (server) needs a
remote operator’s console to run tests, boot the system, or whatever the
regular operator’s console is used for. If the boot node is a VAXserver
3100, the Break Enable switch on the back of the system box must be se
to the up position before entering this command on the remote console.
The boot node mu:t also be plugged into port 3 on the back of the syster
box.
An * is added to the console prompt (>>>) when the DTE command is
entered to indicate that you are operating the boot node. Press CTRL/P
at the special console prompt (*>>>) to return to normal console mode.

B.2.6

EXAMINE

>>> EXAMINE [<qualifier>} [<address>|
Examines the contents of the specified address. If no address is specified
+ is assumed. The address may also be one of the symbolic addresses
described ir deposit.

Qualifiers
Same qualifiers as deposit.

B-6

Console Commands

Address

Same address specifications as deposit.

The response is in the form: <address space><address><data>

8.2.7 FIND
>>> FIND [<qualifier>)

The console program searches main memory starting at address zero for a
page-aligned 128 Kbyte segment of geod memory or a restart parameter
block (RPB). If the segment or block ie found, its address plus 512 is left
in the SP. If the segmant or block is not found, an error message is issued
and the contents of the SP are unpredictable. If no qualifier is specified,
/MEMORY is assumed.

Qualifiers
¢

/Memory

Searches memory for a page-aligned 64 Kbyte segment of good
memory. The search includes a read/write test of memory and
leaves the contents of memory unpredictable.
*

/RPB

Searcihes memory for a restart parameter block. The search
leaves the contents of memory unchanged.

B.2.6 HALT
>>> HALT

A halt message is displayed, follewed by the console prompt (>>>). No

action is taken.

>>> HELP

Brings up a summary of the console coinmands, supported parameters,
and available options.

Console Commands

B-7

B.2.10 INITIALIZE
>>> INITIALIZE

A processor initialization is performed. Refer to Table B-2 for a list
of registers that are set and the values they are set to (all values are
hexadecimal).

Table B-2

INITIALIZE Command Register Values

Value

PSL

041F.0000

IPL

ASTLVL

SISR

ICCS

MAPEN

All other registers are urnredictable.

The defaults used to fill in unsupplied qualifiers for DEPOSIT and
EXAMINE commands are set to physical address, longword size, and
address 0.

B.2.11

REPEAT

>>>REPEAT <command>

The console program repeatedly displays and executes the specified
command. The repetition is stopped when you type CTRL/C. Any valid
console command may be specified for the command with the exception of

the REPEAT command.

B.2.12 SET
>>> SET <parameter-name> <value>

Set the console NVR parameter to the indicated value. The following
console parameters and their acceptable values are defined:

Parameter-name

BOOT -— Set the default boot device. The value must be a
valid boot device name as specified by the boot command. See
Section B.2.1. The only validation done is to verify that the fourth
character in the device name is a decimal number between ze-»

Console Commands

B-8

and nine. Entering "." resets the boot device to the default value
which is ESAQ.

BFLG — Set the default boot flags. The value must be a
hexadecimal number of up to eight characters. The value entered
is not checked for validity.

HALT — Set the default halt action code. This code specifies the
default action the console should take for all error halts and power
up halts. The default value is stored in nonvolatile RAM and is
retained across power cyvcles. If the nonvolatile RAM fails for any
reason, the console initializes this field to the value of 2 (boot).

Value

1 sets the default action to restart.

2 sets the default action to boot.

3 sets the default action to halt.

MOP — Set the network listener to be enabled or disabled.
The only acceptable values for this are listed as follows. If the
Ethernet self-test had failed, then this command is an illegal
command. If the nonvolatile RAM fails for any reason, the default
value is set to 1 (enabled).

Value

A 0 disables the network listener.

A 1 enables the network listener.

PSWD — Set the password for remote trigger verification. This
allows a user to set the password that will be verified if a remote
trigger is received by the network listener. An illegal command
will be displayed if the Ethernet self-test has failed or remote
triggers are not enabled. In order to set a new password, the
password must be known unless it is the first time a password is
set, in which case only a new password need be specified. There
is no corresponding SHOW command. For security reasons, the
password is one-way encrypted and canncot be displayed.

Console Commands

B-9

SCSIA — Set the SCSI address ID of the SCSI-A bus controller.
The address ID of the bus controller should be an ID of 6.

However, the address ID can be changed for whatever reason
using this command. Valid address IDs are 0 to 7. Enter SCSIA 6
at the console prompt to set the bus controller’s ID to 6.

SCSIB — Set the SCSI address 1D of the SCSI-B bus controller.
The address ID of the bus controller should be an ID of 6.
However, the address ID can be changed for whatever reason
using this command. Valid address IDs are 0 to 7. Enter SCSIB 6
at the console prompt to set the bus controller’s ID to 6.
TRIG — Set the remote trigger to be enabled or disabled. This
allows a remote system to request a local boot of the system. If
the Ethernet self-test has failed, then this is an illegal command.
If the nonvolatile RAM fails for any reason, the default value is
set to 0 (disabled, remote trigger is not allowed).

B.2.13 SHOW
>>> SHOW <parameter-name>

The SHOW command displays information about the parameter indicated.

Parameter-name

BOOT — Displays the default boot device as defined in the

previous SET command above. An empty field appears as "....".

BFLG — Displays the default koot flags. If no flags are specified,
then 00000000 is displayed.

DEVICE - Displays the devices currently operating in the system
including the drives and their SCSI address IDs on the SCSI
buses.

ESTAT — Displays the screens associated with the last execution
of the system exerciser test. This command is provided as a
means of determining the state of the system test if an abnormal
error occurs which causes the system exerciser test to either wait
or halt. It provides no more information than is available at the
normal completion of the system exerciser test.

ETHERNET — Displays the hardware Ethernet address. The
Ethernet address ROM is validated and is displayed as ID YY-YYYY-YY-¥Y-YY where YY is a valid two digit hexadecimal number.

B-10

Console Commands

If the Ethernet address ROM is invalid, then ID XX XX-XX-XXKX-XX is displayed to indicate that the Ethernet address RCM is
not vahd.
o

HALT — Displays the default action code.

MEM — Displays information concerring the KA-41 system
memory. The format of the display is as follows:
>>>

8H MEN

00400000

00000000
002FD400:CO3FFFFF

Where: The first eight-character field displays the total amount of
memory in the system including the console data structures. The
second eight-character field shows the first address of 256 Kbytes
of contiguous memory, generally used by VMB. The final line of
the displav shows the address range of the area of memory that
1s not available to the operating system. This includes the area
of memory that is reserved for use by the conscle program. This
field will be repeated as many times as needed to display all of the
address ranges that are not available to the operating system.

MOP — Displays the state of the enabled network listener bit. If
the value returned is 0, then the network listener is disabled. If
the state of the value returned is 1, then the listener is erabled. If
the Ethernet tests fail, then this command is an illegal command.

SCSIA — Displays the host ID to be used by the SCSI-A bus (0 to
7).

* SCSIB — Displays the host ID to be used by the SCSI-B bus (0 to
7).

TRIG — Displays the state of remote trigger enable. If the value
returned is 0, then a remote trigger is not allowed. If the state of
the returned is 1, then remote triggers are allowed provided the
remote trigger password is set correctly. If the Ethernet tests fail,
then this command is an illegal command.

VER — Displays information concerning the revision levels of
four separate sections of program code within the system module
ROMs. These sections are the self-test code, console code, VMB
code, and the ROM code. All four sections have different internal
revision levelz. Enter SHOW VER to see the internal revision
levels of the self-test, console, VMB, and ROM code displayed

‘

Console Commands

B-11

next to the KA41-A. The following is an example of these revision
levels:
>>>

SHOH VER

KA41-A V0.17C~0BF-V2.1-239
PST:

OBF

CON:

17C

VMB:

V2.1

ROM:

239

Where: The V0.17C is for the self-test revision level, OBF is the
console code revision level, V2.1 is for the VMB revision level, and
239 is the ROM code revision level.

B.2.14 START
>>> START [<address>|

The console program starts instruction execution at the specified address.
if no nadress is given, the current content of the PC is used. The START
command is equivalent to a deposit to PC fol'owed by a CONTINUE
command. No initialize is performed.

B.2.15 TEST
>>> TEST [<test number>]

The console program invokes a diagnostic test program specified by the
test number. Test numbers for Field Service diagnostics are rejected if
loopback connectors are not installed on all MMJ connectors. Some of the
test numbers are used to invoke utilities. See Appendix A for a list of the
test numbers.

B8.2.16

UNJAM

>>> UNJAM

A system reset is performed.

B-12

Console Commands

B.2.17 Transfer (XFER)
s>> X <address><count><RETURN><data stream><checksum>
Transfers binary data to and from physical memory. This command is
used by automatic systems communicating with the console program. It
is not intended for operator use. The console program writes or reads
in memory the specified number of data bytes, starting at the specified
address.

Address

The physical address the binary data is transferred to or from. It is
specified as a hexadecimal number.
Count
The number of uywes to be transferred. It is specified as a hexadecimal

number. If the high order bit of the count is one, the data is
transferred (read) from physical memory to the console device. If
the high order bit is zero, the data is transferred (written) from the
console device to physical memory.
RETURN
A carriage return.
Dats stream
"Count” bytes of binary data.

Checksum
The two’s complement checksum of the command string or data

stream. The checksum is one byte of data expressed as a two digit
hexadecimal number.

Console Commmands

B.3

B-13

Special Keys

Table B-3

Special Keys Used In Console Program Mode

Special Key

Explanation of use

RETURN

Terminates the command line so the console program can
execute the command.

@LETE

This is used to delete single characters within a commend

line. On video terminals and video monitors, the character(s)
deleted disappears (the console program sends a BS/SP/BS).
On hardcopy terminals, the deleted characters are retyped
after a backslash delimiter as they are deleted. For unknown
attached console devices, the console program assumes they are
hardcopy.

CTRL/C

Aborts the current command. The current progr-.in mode PC

will be displayed, and the console prompt (>>>! is displayed on
the next line. The console program echoes this as AC.

CTRL/O

Causes the console program to throw away transmissions to
the console device until the next CTRL/O is entered. CTRL/O
is echoed as *O when it disables output, but is not echoed
when it reenables output. Output is reenabled if the console
program prints an error message or if the console prompts for a
command from the console device.

Output is also enabled by entering program /O mode, and by
CTRL/.C. CTRL/O clears CTRI/S.
CTRL/R

Retypes the current command line. Deleted characters are not
displayed.

CTRL/S and
CTRI/Q

The console program supports CTRL/S and CTRL/Q on both the
normal and attached console devices. These keys are equivalent
to the corresponding line paciiig control characters XOFF and
XON. Characters received between the XOFF/XON pair may be
ignored.
The hold screen key on the normal console device is not used
for line pacir-.

CTRL/U

Ignores the current command line. The console prompt (>>>) is
displayed on the next line. This only affects entry of the current
line. The console program echoes this as "U. Pressing CTRL/U
when a command is executing does not abort the command.

MOTE
Special keys are ignored during TRANSFER.

C
Console Messages and Explanations

Table C-1

Console Error Megsages

Message

Ezplanation

02 EXT HLT

Fxternal halt.

04 ISP ERR

Attempt to push interrupt or exception state onto the
interrupt stack when the interrupt stack is mapped

NO ACCESS or NOT VALID.

05 DBL ERR1

A second machine check occurred while the processor
was attempting to report a machine check to the
operating system.

06 HLT INST

The processor executed a halt instruction in kernal
mode.

07 SCB ERR3

SCB interrupt vector bits <1:0> = 3.

08 SCB ERR2

SCB interrupt vector bits <1:0> = 2.

0A CHM FR ISTK

A change mode instruction was executed when
PSL<IS> was set.

0B CHM TO ISTk

Exception vector bit <0> was set for a change mode.

0C SCB RD ERP.

A hard memory error occurred during a processor read
of an exception or interrupt vector.

10 MCHK AV

An access violation or invalid translation occurred
during machine check exception processing.

11 KSP AV

An access violation or invalid translation occurred
during invalid kernel stack pointer exception
processing.

C-2

Console Messages and Explanations

Table C-1 (Cont.)

Console Error Messages

Message

Expianation

12 DBL ERR2

Double machine check error.

13 DBL ERR3

Double machine check error.

19 PSL EXC5

PSL26:24 = 5 on interrupt or exception.

1A PSL EXCé

PSL26:24 = 6 on interrupt or exception.

1B PSL EXC7

PSL26:24 = 7 on interrupt or exception.

1D PSL EXCT7

PSL26:24 = 5 on rei.

1E PSL EXC7

PSL26:24 = 6 on rei.

1F PSL EXC7

PSL26:24 = 7 on rei.

20 TOY ERR

Time-of-year (TOY) clock failure.

21 CORRPTN

The console database is corrupted. The console
simulates a power-up sequence and rebuiids its
database.

22 ILL REF

The requested reference violates virtual memory
protection and the address is not mapped. Fither the
reference is not valid in the specified address space or
the value is not valid in the specified destination.

23 ILL CMD

The command string cannot be parsed.

24 INV DGT

A number has an invauid digit.

25 LTL

The command is too large for the console to buffer.

26 ILL ADR

The specified address is not in the addresa space.

27 VAL TOO LRG

The specified value does not fit in the destination.

23 SW CONF

Conflicting switches. For rxample, an EXAMINE
command that sperifies two different data gi-es.

29 UNK SW

The switch is no: vecognized.

2A UNK SYM

The examine or deposit symbolic address is not

2B CHKSM

Either the whole transfer (X) command or just the
<data> portion of the TRANSFER command is not

recognized.

valid.

2C HLTED

The operator entered the HALT command.

Console Messages and Explanations

Table C-1 (Cont.)

C-3

Console Error Messages

Message

Explanation

2D FND ERR

A FIND command failed to find either the RPB or 64

2E TMOUT

Data failed to arrive in the expected time during a

2F MEM ERR

Parity or other memory error detected.

30 UNXINT

An unexpected interrupt or exception occurred.

40 NOSUCHDEV

VMB message: No boote':le device found.

41 DEVASSIGN

Device is not present.

42 NOSUCHFILE

Program image is not found.

43 FILESTRUCT

Invalid boot device file structure.

44 BADCHKSUM

Bad checksum on header file.

45 BADFILEHDR

Bad file header.

46 BADIRECTORY

Bad directory file.

47 FILNOTCN1G

Invalid program image file.

48 ENDOFFILE

Premature end-of-file encountered.

49 VADFILENAME

Bad file name given.

4A BUFFEROVF

Program image does not fit in available memory.

4B CTRLERR

Boot device I/O error.

4C DEVINACT

Failed to initialize boot device.

4D DEVOFFLINE

Device is off-line.

4E MEMERR

Memory initialization error.

4F SCBINT

Ur:axpected SCB exception or machine check.

50 SCBZNDINT

T'nexpected exception after starting program image.

51 NOROM

No valid ROM image found.

+2 NOSUCHNODE

No response from load server.

53 INSFMAPREG

Invalid memory configuration.

54 RETRY

No devices bootable, retrying.

55 NOWRT

Device is read-only or write locked.

Kbytes of good memory.
transfer (X) command.

C~4

Console Messages and Explanations

Table C-1 (Cont.)

Consoie Error Messages

Message

Explanation

56 DUPIDENT

Duplicate SCSI ID for device and CPU.

57 DEVCMIERR

DEVICE command error.

58 ILLIOFUNC

Illegal VO function.

81 SUCCESS

Success.

82 CVAXSTAR

Power-up message.

83 BOOT SASS

Bootstrapping.

84 FAIL

General failure.

86 RESTART SASS

Restarting system software.

86 RMT TRGGR

Remote trigger request.

87 TESTING_SP

A white space message to format countdown.

88 TESTING _DONE

Diagnostic conclusion.

89 IMPOSSIBLE

Operation is impossible.

8A PC_STR

PC introduction on halt display.

8B BKSP_DELETE

Backspace delete sequence.

8C CRLF

Simple CRLF.

8D CTRLC

Control C message.

8E CTRLU

Control U message.

8F CTRLO

Control O message.

90 DA_QUERY

Device attribute request.

91 TERMINIT

Terminal initialization.

92 APT_PRCMPT

Prompt to APT.

93 LK201_RESP

Console language response prompt.

+9 PROMPT

Conco!~ nrompt text.

9A BOOTFILE

Bootfile prompt message.

9B PARMFILE

Ethernet parameter file prom pt message.

9C RMT TRGGR

Bootstrap triggered remotely.

VMB Boct Error Status Codes
Figure D-1 shows the two types of VMB error displays. PC indicates the
contents of the pregram counter at the time of the error, RO indicates
the contents of register 0 at the time of the error, and PSL indicates the
contents of the program status longword. Table D-1 lists the VMB boot
error status codes.
Each error code’s lower three bits (hexadecimal) represent a severity level
and may be changed by the software. For example, 000001F4 is a parity
error and represents an error status, but 000001F0 through 000001F7
also represent parity errors of varying severity. Therefore, the error
code numbers represent the typical value of each error code. Refer to
Table D-1.
Figure D-1

VMB Error Displeys

error message

Generiec

where

$VMB-F-ERR,

nnnnnnnn

$VMB-1-STS,

nnnnnnnn

Unexpected

exception.

$VMB-F-SCBINT,

These

nnnnnnnn,

status

represent
PSL

1nternal

nnannnnn

$VMB-F-~-SCBINT2,

nnnnnnnn,

PSL

code.

nnnnnnnn

YMB

errors.

D-2

VB Boot Error Status Codes

Table D-1

VAMB Boot Error Status Codes

Error Code

Mnemonic

Definition

000600001

SS$_NORMAL

Normal successful completion.

00000054

88$_CTRLERR

Fatal controller error.

00000084

SS$_DEVOFFLINE

0000008C

8S$_DRVERR

Fatal drive error.

000000DC

SS$_ILLBLKNUM

Tllegal logical block number.

000001 A4

SS8$_MEDOFL

Medium is off-line.

000001AC

S8$_NODATA

Mailbox is empty.

000001F4

SS$_PARITY

Parity error.

0000022C

8S$_TIMEOUT

Device timeout.

0030028C

SS$_NOSUCHNODE

Remote node is unknown.

000002AC

SS$_FILNOTCNTG

File is not contiguous as required.

00000344

SS$_INSFMAPREG

Insufficient map registers.

00000601

SS$_BUFFrEROVF

Output buffer overflow.

00000808

SS$_BADCHKSUM

Bad file header checksum.

00000810

8S$_BADFILEHDR

Bad file header.

00000818

SS$_ BADFILENAME

Bad file name syntax.

00000828

SS$_BADIRECTORY

Bad directory file format.

00000848

SS$_DEVASSIGN

Device has channels assigned.

00000870

SS$_ENDOFFILE

End of file.

000008C0

SS$_FILESTRUCT

Unsupported 1 ¢ structure level.

00000908

SS$_NOSUCHDEV

No such device available.

00000910

SS$_NOSUCHFILE

No such file.

000020D4

SS$_DEVINACT

Device is inactive.

00002144

SS$_FORCEDERROR

Device is not in configuration or not

available.

For:;ed error flagged in last sector
read.

00008000

SS$_MEMERR

No good pages of memory found.

00008018

SS$_NOROM

System exerciser not present.

E
Power-Up and Self-Test Error Codes
This apperdix lists all of the power-up and self-test error codes. There
is no difference between the power-up error codes and the self-test error
codes. Table E~1 lists the contents of this appendix by sections.
Table E-1

Failing Test/Device Section References

Failing Test/Device

Section

Test F - Not supported

Test E - TOY clock (CLK)

Test D - Nonvolatile RAM (NVR)

E.2

Test C - Serial line controller (DZ)

Test B - System memory (MEM)

E.4

Test A - Memory management (MM)

E.5

Test 9 - Floating point (FP)

E.6

Test 8 - Interval timer (IT)

E.7

Tests 6 and 7 - SCSI bus controller (SCSI-A and
SCSI-B)

ES8

Test 5 - Interrupt controller and Ethernet ID
ROM (SYS)

E.9

Test 4 - DSH32-B communications module async.

E.10

lines

Test 3 - DSH32-B communications module sync.
lines

Test 2 - Not supported

E.11

E-2

Power-Up and Self-Test Error Codes

Table E-1 (Cont.)

Falling Test/Device Section Refeicnces

Failing Test/Device

Section

Tost 1 - Ethernet network (NI)

E.12

E.1

Time-Of-Year Clock (CLK)

Error code format: 0000.XXXX

Where XXXX is one of the error codes. Refer to Table E-2.
Table E-2

Time-Of-Year Clock (0000.XXXX)

Error
Codes

Definition

0001

No error.

0003

Tell dispatcher to check time at the end of the testing.

0004

Invalid time set.

0005

Clock has not been reset since the last time that battery voltage
level wae low.

0010

Failure in time-of-year test.

0020

Vrt bit failed to set after it was read the first time.

0040

Battery voltage level was down during the clock test.

‘

Power-Up and Self-Test Error Codes

E-3

E.2 Nonvolatile RAM (NVR)
Error code format: 0000.XXXX

Table E-3 lists the codes corresponding to XXXX. An error code of 5
indicates that the battery voltage is below an acceptable level for data in
the NVR to be valid.
Table E-3

Nonvolatile RAM Error Codes (0000.XXXX)

Error

Codes

Definition

0001

No error.

0004

Battery was down at last entry.

0008

NVR failed.

0080

E.3

The battery check code in the NVR did not agree with the

expected check code.

Serial Line Controller (DZ)

Error code format: 0000.XXXX

Table E-4 lists the error codes corresponding to XXXX.
Tab'a E-4

Serial Line Controlier (0U00.XXXX)

Error

Codes

Definition

0001

No error.

Master reset failed.

0004

Failure in basic CSR test.

0008

Failure in CSR read write test.

0010

Basic test of TCR failed.

0020

Read write test of TCR failed.

0040

Transmitter ready test faiied.

0080

Receiver ready test failed.

0100

Transmitter interrupt timeout.

E-4

Power-Up anc Self-Test Error Codes

Table E-4 (Cont.)

Serial Line Controller (0000.XXXX)

Error
Codos

Definition

0200

Receiver interrupt timeout.

0400

Either transmitter or receiver interrupted at the wrong priority.

0800

Receiver interrupt occurred when the receiver was not enabled.

1000

Data comparison error.

2000

Overrun error did not happen.

4000

This line is untested.

8000

Error in the modem control lcgic test.

The second line of six codes under the DZ error code contains the status
of each serial line. This line of status codes is provided so a failing serial
line can be isolated. The status codes in the second line have the following
format:
QO00WWWW

OOOOWWWW

OOOOWWWW OQ000OWWWW 00000000

00000000

line

modem

Unused

line

Unused

Table E-5 lists the codes corresponding to WWWW.

Power-Up and Self-Test Error Codes

Table E-5

E-5

Serlal Line Status Codes (0000WWWW)

Status

Code

Definition

0001

Serial line tested successfully.

4000

Serial line is untested.

E.4

System Memory (MEM)

Error code format: 0000.XXXX

Takle E~6 lists the codes corresponding to XXXX. These codes show the
error/status information for the memory on the system module and also
the option memory module. The second line under the MEM code contains
additional information on the memory in the system. These additicnal
codes have the following format.:

Second line status code format: YYYYYYYY ZZZZZZ277Z

Where YYYYYYYY is the total number of bytes of good memory found in
the system. If this field is not in an even megabyte value (for example,
00020000) then the second field, ZZZZZZZZ, is displayed to indicat~ the
failing megabyte bank. Each bit in the ZZZZZZZZ status code indicates
the status for one bank of memory. In some cases, where a parity error
is detected, the error may be on both the system module and the option
memory module.

Table E-6

System Memory Error Codes (0000.XXXX)

Error
Codes

Definitions

0001

No error.

0002

Failure in test address routine.

0004

Byte mask failure.

0008

Data’address test failure.

¢i10

No memory was found during sizing.

(6020

Unexpected parity error.

E-6

Power-Up and Sefi-Test Error Codes

E.5

Memory Management (MM)

Error code format: 0000.000X

Table E-7 lists the codes corresponding to X.
Table E-7

Memory Management Error Codes (0000.000X)

Es. w

Codes

Definition

No error.
Memory management error,

MNegal vector during MM test.

E.6

Floating Point (FP)

Error code format: 0000.000X

Table E-8 lists the codes corresponding to X.
T.ole E-8

Floating Point Error Codes (0000.000X)

Error
Codes

Definition.

0002

Floating point error.

0004

Invahid floating point exception.

E.7

Interval timer (IT)

Error code format: 0000.000X

Where X is either a 2 for a fatal error or a 1 for a success.

Power-Up and Seli-Test Error Codes

E.8

E-7

SCSI Bus Controller (SCSI-A and SCSI-B)

This section includes the codes for all of the SCSI bus controllers on all
systems.

Error code format: WWXX.YYZZ

Where WW is the bit mask field of the devices selected successfully on the
SCSI bus. Refer to Table E-9. XX is the bit mask field of the devices that
tested successfully. Refer to Table E-9. YY is a set of bitmap error flags.
Refer to Table E-10. ZZ is the status/error code of the SCSI bus controller
on the system module. Refer to Table E-11.
Second line error code format: DDMMSSTT
Where the DD is the status of the data in phase on the INQUIRY

command, MM is the status of the message in phase of the INQUIRY

command, SS is the status of the status phase of the INQUIRY command,
and TT is the status of the devices on the SCSI bus. All of these status
codes are identical. Refer to Table E-12.
The second line of code indicates the status of the eight possible devices
on the SCSI bus including the bus controller on the system module. The

first code in this second line is reserved for the SCSI bus contvoller on
the systemn module and the second through eight code is for the devires
connected to the SCSI bus.
Table E-9

Binary Mask of Selected Devices (WWXX.0000)

Binary Mask

Device ID

As Seen on the Screen

0000 0001

0000 0010

0000 0100

0000 1000

00661 0000

0010 0000

0100 0000

1000 0000

E-8

Power-Up and Sell-Test Error Codes

Table E-10

Binary Mask of Error Flags (0000.YY(0O0)
As Seen on the

Binary Mask

Definition

Screen

0000 0001

Problem is on the system module.

9000 0010

Problem is not on the system module.

0001 0000

Reset is required to free SCSI bus.

Not all selected devices are operating

0010 0000

0100 0000

Tabie E-11

correctly.

DTM A and interrupts are untested.

SCSI Bus Controller's Error Codes (0000.002Z)

Error Codes

Definition

No error

Data buffer RAM addressing failure.

Data buffer RAM byte mask failure.

Data buffer data path failure.

Error in SCS| bus controller registers during reset.

Error in SCSI bus controller registers after reset.

Unexpected interrupt after reset, {PL = 1F.

No interrupt request after reset.

No interrupt after reset when IPL has been lowered.

Interrupt request not cleared following ISR (after reset).

Multiple interrupts following reset.

Unknown interrupt following reset.

Wrong interrupt following reset.

Phase not bus free at start of test.

First attempt to read SCSI bus controller’s registers failed.

&CSI bus controller register address test failed at ini_cmd.

SCSI bus controller register address test failed at mode.

SCSI1 bus controller register address test failed at tar emd.

Power-Up and Self-Test Error Codes

Table E-11 (Cont.)

SCSI Bus Controller's Error Codes (0000.0022)

Error Codes

Definition

SCSI bus controller register address test falled at scd_cnt.

E-9

Mode(DMA) found set after being cleared when ini_cmdibsy)
clear.

Mode! DMA) found set after being set when ini_cmd(usy) clear.

Mode(DMA) found set after being cieared when ini_cmd(bsy)
set.

ModetDMA) found clear after being set when ini_cmd(bsy) set.

Data output to bus with ini_cmd(enout) clear.

No data to bus with ini_cmd(enout) set.

Parity bit cur_stat(dbp) did not match data on bus.

With bus free, data in dic not match data out.

ini_emdisill) to cur_stat(sel) mismatch.

1ini_cmd(ack) to status(ack! or ini_cmd{atn) to status(atn)
mismatch.

Tar_cmd(req) to cur_stat(req) or tar_cmd(msg) to cur_stat{msg)
or tar_cmd(ed) to cur_stat(cd) or tar_cmd(io) to cur_stat(io)
mismatch with mode(targ) set.

Clearing mode(targ) does not prevent tar ¢md bits from
appearing on the bus.

ISR hit with [PL = 1F and int_msktsc) clear.

Inter upt request int_reqisc) set for no reason.

SCSI bus statustintreq) set for no reason.

SCSI bus busy at start if interrupt test - no test done.

ISR hit following bus free with IPL = 1F and int_msk(sc) clear.

Interrupt request int_req(sc) not set following bus free.

SCSI bus status(in’req) not set following bus free.

Status(bsyerr) not set after it caused an interrupt.

SCSI bus busy during interrupt test - no test done.

ISR hit following bus free with IPL = 1F and int_msk(sc) set.

Interrupt request int_req{sc) not set following bus free.

E-10

Power-Up and Self-Test Error Codes

Table E-11 (Cont.)

SCSI Bus Controlier's Error Codes (0000.00Z2)

Error Codes

Definition

SCSI bus status(intreq) not set following bus free.

Status(bsyerr) not set following bus free.

SCSI bus busy during interrupt test - no test done.

Timesut waiting for bus free interrupt.

ISR not hit following bus free.

Interrupt request (nt_req(sc) not cleared following ISR after bus
free.

SCSI bus status(intreq) not set following bus free.

Multiple interrupts from bus free.

Unknown interrupt from bus free.

Wrong interrupt from bus free.

SCSi bus busy during interrupt test - no test done.

Timeout waiting for panty interrupt.

ISR not hit following parity.

Beé

Interrupt request int_req(SC) not cle: red following ISR after
parity.

SCSI bus status(intreq) not set following parity.

Multiple interrupts from parity.

Unknown interiupt from panty.

Wrong interrupt from parity.

Phase is not bus free before arbitration.

Ini_cmd(aip) bit failed to set.

Lost arbitration (first check of ini_cmd(la)).

Cé

Higher priority device in bus.

Lost arbitration (second check of ini_cmdila)).

Not all selected targets tested satisfactory.

Power-Up and Self-Test Error Codes

Table E-12

E-11

Device Status Codes (DDMMSSTT)

Status

Codes

Definition

Device is untested.

No error.

This device is reserved by the host (SCSI bus controller).

Device did not respond to selection.

Device did not set cur_stat(req) soon enough when changing

Jitter on the phase lines when changing phase.

Device set command phase twice.

Device changed phase before command complete.

Device failed to set cur_stat(req) when getting command.

Device failed to clear cur_stat(req) when getting command.

Command phase out of sequence.

Stuck in command phase.

Device set data in phase twice.

Device failed to set cur_stat(req) when returning data.

Device failed to clear cur_statireq) when returning data.

Device changed data in phase before transferring any data.

Data in phase out of sequence.

Stuck in data in phase.

Target set status phase twice.

Target failed to set cur_stat{req) when returning data.

Target failed to clear cur_statireq) when returning data.

Target changed status phase before transferring any data.

Status phase out of sequence.

Stuck in status phase.

Target set message in phase twice.

Target failed to set cur_statireq) when returning data.

phase.

E~-12

Power-Up and Seli-Test Error Codes

Table E-12 (Cont.)

Device Status Codes (DDMMSSTT)

Status

Codes

Definition

Target failed to clear cur_statireq) when retur ung data.

_in phase before trensferring any data.
Target changed message

Message in phase out of sequence.

Stuck in message in phase.

Target set data out phase (unexpectedly).

Target set phase to 100b (reserved phase).

Target set phase to 101b (reserved phase).

Target set message out phase.

Selected target did not set any phase before releasing bus.

Target not following expected phase uequence.

Parity error detected during programmed | ) transfer.

Unexpected interrupt at start of DMA test.

Target failed to set command phase.

Unexpected interrupt at start of command phase in DMS test.

Timeout waiting for DMA complete in command phiise in DMA
test.

No DMA end following command phase in DMA test.

Wrong interrupt following command in DMA test.

Sed _ent not zero following command in DMA test.

DMA not complete after EOP command phase (ACK not clear
soon enough).

Status(<imaend) bit not cleared by clearing mode(DMA) at start
o” data in phase in DMA test.

Target failed to set data in phase in DMA test.

Timeout waiting for DMA complete in data in phase in DMA test.

No statustdmaend) following data in phase in DMA test.

Wrong interrupt following data in phase in DMA test.

Scd_ent not zero following data in phase in DMA test.

Power-Up and Self-Test Error Codes

Table E~-12 (Cont.)

E-13

Device Status Codes (DDMMSSTT)

Status

Codes
AC

Definition
DMA not complete after EOP in data in phase (ACK not clear
soon enough).

Status(dmaend) not cleared by clearing mode(DMA) at start of
status phase in DMA test.

Target failed to set status phase in DMA test.

Timeout waiting for DMA complete in status phase in DMA test.

No status(dmaend) following status phase in DMA test.

Wrong interrupt following status in DMA test.

Scd_cnt not zero following status in DMA test.

DMA not complete after EOP in status phase (ACK not clear
soon enough).

Status(dmaend) not cleared by clearing mode(DMA) at start of
message in phase in DMA test.

Target failed to set message in phase in DMA test.

Timeout waiting for DMA complete in message in phase in DMA
test.

Cé

No status(dmaend) following message in phase in DMA test.

Wrong interrupt following message 1n phase in DMA test.

Scd_cnt not zero following message in phase in DMA test.

DMA not complete after EOP in message in phase (ACK not clear

soon enough).
Do

Status(dmaend) not cleared by clearing mode(DMA) at end of

DMA test.
D2

SCSI bus not free scon enough at end of DMA test.

E-14

Power-Up and Self-Test Error Codes

E.9

Interrupt Controlier and Ethernet ID ROM (SYS)

Error code format: 0000.XXXX

Table E-13 lists the codes corresponding to XXXX.
Table E~13

interrupt Controlier/Ethernet ID ROM Error Codes
(0000.X XXX}

Ervor Codes

Definition

0001

No error.

0002

System ROM failed checksum.

0004

Ethernet ROM failed checksum.

0008

No interrupts pending.

0010

All of the expected interrupts did not occur.

0020

Unexpected interrupt.

0040

Improper priority.

0080

Default interrupt service routine was called. An interrupt that
was not enabled occurred.

0100

No keyboard found in the configuration.

Power-Up and Self-Test Error Codes

E.10

E-15

DSH32-B Communications Module
Asynchronous Subsystem (DSH32-A)

Evror code format: 00XX.YYYZ

Where XX is a bitmap representing the number of the failed line.
Table E-14 lists the codes corresponding to YYYZ. If Z=0 then the error is
fatal.

Table E-14

DSH32-A Error Codes (06000.YYYZ)

Error Code'!

Definition

0001

Normal SLU module operation; no errors detected.

o010

Control and status register failed read after write test.

0020

Controller is hung; internal hardware self-test never flagged
completion by clearing CSR reset bit.

0030

Internal hardware self-test failed; diagnostic fail bit set.

0040

Internsl self-test result bytes failed to generate a receiver
interrupt.

0050

Receiver done not set following internal hardware self-test.

0060

Receiver done not clear after reading self-test bytes.

0070

Valid data not found in receiver FIFO.

00A0

Data valid bit was set when FIFO should have been empty.

00B0

Internal self-test error—low octart error.

00C0

Internal self-test error—high octart error.

09D0

Internal self-te<* error—RAM error.

00E0

Internal self-test error—undefined status code found.

0101

FIFO size register etior; FIFO SB empty, size register indicates
FIFO is not empty.

2000

An illegal transmitter interrupt was detected.

2020

A de‘a compare error was detected while performing

alternating bit pattern read after write test of the SLU RAM

space.

How 16-bits of the module information line or the appropriate 16-bits for a particular
communication line.

E-16

Power-Up and Seli-Test Error Codes

Tabie E-15

DSH32-A Fleld Service Mode Error Codes (0000.YYYZ)

Ervor Code'

Definition

0001

Normal operation; no errors detected.

0050

Receiver done not ready following internal autodiagnostics.

Receiver done not clear after reading self-test bytes.

00'0

Valid data not found in receiver FIFO.

2380

Transmitter failed to generate interrupt on transmit FIFO
empty.

011x

Transmitter did not become ready before timer expired

n20

Data not received; receiver done did not become ready before

following null character transmitted.

timer expired following transmission of an ASCII character.

0131

Null character expected in receiver FIFO, not found.

0141

Transmitt2d data expected in receiver FIFO, not found.

0161

’I‘mnsmit FIF() overrun error detected during basic cata
transmiision test.

0171

Fraining error occurred during basic data transmission test.

0181

Parity error occurred dunng basic data transmission test.

0190

FIFO data “receive line” bit field indicates that the data was

received on the wrong hne

01A0

Transmitter actior bit not clear with data sent on disabled line.

01B1

Receiver not done when data 1 expected from FIFO.

01D1

Port never became ready to send new data.

2010

Transmit ready bit did not clear with transmitter action FI1F0s
emptied.

Low 16-bits of t1e module information hine or the appropnate 16-bits for a particular

communication line.

Power-Up and Self-Test Error Codes

E.11

E-17

DSH32-B Communications Module
Synchronous Lines (DSH32-S)

Error code tormat:

XAXX YYYO

Where XXXX indicates the test number and YYY is the fault code.
Table E-16 lists the codes corresponding to XXXX.
NOTE

If a fault code is returning the address of the failing register, this
address is only the last three hex digits of the 32-bit address. It
should be understood that the prefix “39009” must be added to any
address that is returned.
Teble E-16

DSH32-S Error Codes (XXXX.YYYOQ)

Error Codes

Message Description

0001.YYYO

nDMA DAL bus test.

0002.YYYO

Static RAM checkerboard test.

0003.YYYO

Static RAM SNAIR test.

0004.YYYO

I/O register test.

0005.YYYO

DUSCC I loopback connector test.

0007.YYYO

nDMA static (register) test.

0008.YYYO

DUSCC 1 static (register) test.

000A.YYYO

Reset circuit test.

000B.YYYO

DUSCC I counter/timer test.

000D.YYYO

DUSCC I Modem signal test.

000F.Y1YO

DUSCC I BOP protocol transmit/receive test.

0011.YYYO

DUSCC I COP/BISYNC protocol test.

0013.YYYO

DUSCC I dynamic test.

0015.YYYO

pDMA-DUSCC I interrupt test.

0017.YYYO

DUSCC 1 interrupt test.

E-18

E.12

Power-Up and Seif-Test Error Codes

Ethernet Circuits (Ni)

Error code format: OWXX.YYYY
Where W = 1 if no heartbeat present (0 = heartbeat present), XX is the
number of retries over the Ethernet cable before a success. Table E-17
lists the codes corresponding to YYYY.
Table E-17
Error
Codes

Ethernet Circuits Error Codes (06000.YYYY)
Definition

Error
Codes

Definition

0001

No error.

4008

Bad filter value.

1002

Failed initialization.

400A

Initiahzation failed.

1004

RX not enabled.

400C

Failed loopback

10¢6

TX enabled.

4J0E

Imtiahization failed.

1008

Inmtialization failed.

4010

Failed loopback.

100A

RX enabled.

5002

Initialization failed.

100C

TX not enablec.

5004

OWN not toggled.

2002

Initialization failed.

5006

No RTRY error.

2004

Failed loop.

5008

TX turned off.

3002

Initialization fai'led.

500A

Initialization failed.

3004

Failed loop.

500C

TX failed.

3006

No CRC natch.

500E

No RCV MISS

3008

Inmtiidization failed.

6002

Initialization finled

300A

Failed TX.

6004

Loopback failed

300C

Failed RX.

6006

Bad CSRO.

300E

Initialization failed.

6008

No NI interrupt.

3010

Failed TX.

600A

Initialization failed.

3012

OWN not toggled.

600C

Loopback failed.

3014

No RX error.

600K

Wrong number of
interrupts.

3016

No STP.

6010

NI interrupts bits set.

3018

No ENP.

7002

Initialization failed.

Power-Up and Self-Test Error Codes

Teile E-17 (Cont.)

E-19

FEthemet Clicults Error Codes (0000.YYYY)

Error
Codes

Definition

Error
Codes

Definition

301A

No CRC error.

7004

OWN not toggled.

301C

No FRAM error.

7006

No BUFF ervor.

301E

No RINT.

7008

TX still on.

4002

Initialization failed.

700A

Initialization failed.

4004

Failed TX.

700C

TX failed.

4006

Packet received.

700E

RX failed.

F
System Exerciser Error Codes
This appenaix lists the status and error codes for the system exerciser.
When examining the exerc..er report, a single question mark (?) indicates
a soft error, two question marks (??) indicate a hard error. The absence
of question marks indicates success. Table F-1 lists the contents of this
appendix by sections.
Table F-1

Falling Test/Device Section References

Failing Test/Device

Section

Test F - Not supported

Test C - Serial line controller (DZ)

F.1

Test B - System memory (MEM)

Tests 6 and 7 - SCSI bus controller (SCSI-A and SCSI-B)

Test 4 - DSH32-B asynchronous subsystem

Test 3 - DSH32-B synchronous subsystem

Test 1 - Ethernet network (NI)

F.6

F.1

Serial Line Controller (DZ)

Error code format: O0LSS.ABCD

Where the OLSS is the status code and the ABCD is the error code.

F-2

System Exerciser Error Codes

The letters L, 88, A, B, C, and D indicate the following:
Table F-2

Status Code Format Significance

Letter

Significance

The serial line used by the console.

Whether the error code portior: CABCD) is indicating a device
hard error (FF), a system software error (0F), or the status of the
four serial lines (00).

ABCD

Either a device hard error (all four digits), a system software
error (all four digits), or the serial line status (one digit for each
of the four serial lines).

When S5 1s 00, each letter in the ABCD code represents a status/error tor
each senal lhine. Table F-3 gives the letter to semal hine assipmments.
Table F-3

Serlal Line Assignments (0000.ABCD)

Letter

Serial Line

MMJ Port 1

MMJ Port 2

Modem

MMJ Port 3

The following tables explain all error and status codes used:

Table F—1 hsts codes used to indicate the console (L

Table F-5 lists the senal hne status codes for each of the four senal
lines (ABCD) when S8 s 00.

Table F-6 lists the device hard error (ABCD) when SS 1s FF

When S8 is OF, system sottwarc error, the error codes in ABCD range
from 0001 to 000B and are considered fatal.

System Exerciser Error Codes

Table F-4

Serial Line Console Codes (0L.00.0000)

Code

Serial Line

MMJ Port 1

MMJ Port 2

Modem

MMJ Port 3

Tabie F-5

F-3

Each Serlal Line's Status/Error Codes (0000.ABCD)

Brror
Codes

Definition

No error is detected for this line.

No charecter is received.

Failed to transmit all characters or transfer took too long or lost

qmuompmmflmm&w

receive characters.

Too many characters received.
Character received not equal expected.

Parity, framing, or overrun error detected.
Baud rate timing error.

Modem signals not equal expected.
Overrun error not equal 0.
Character received not equal expected.
Overrun error failed to set.

Framing error failed to set.
TxRdy bit failed to set.
Transmit line received not equal expected.

Interrupt request bit ST not set in INT_REQ register.
Interrupt request bit ST not cleared in INT RiiQ register.

F-4

System Exerciser Error Codes

Table F-6

Fatal Device’s Error Codes (0OFF.ABCD)

Error

Codes

0001

Definition

Interrupt mask register, INT MSK register bits ST or SR stuck
at 1.

0002

Master clear failed to reset DZQ.

0003

CSR register: expected %x1028.

0004

CSR register failed t¢ clear.

0005

TCR register: expected % x0FOF

0006

TCR regster failed to clear.

0007

TRDY bit in CSR stuck at 1

0008

TRDY bit in CSR failed to set.

0009

TRDY bit 1n CSR failed o clear after transmitting a character.

000A

TRDY bit in CSR failed to set after transmitting a character.

000B

RDONE bit failed to set after transmitt'ng character in internal
loopback mode.

000C

SR bit in INT_REQ register not set by RDONE.

000D

SR bit in INT REG register not cieared by writing bit in INT
CLR register.

000E

Character received: 0 or line number not equal expected.

000F

Data valid bit not set in word read.

0010

Silo alarm enable failed w set 1in CSR.

ool

Silo alarm fanled to set after transmitting 16 characters in

internal loopback.
0012

RDONE not set after 16 characters received.

0013

SR bit in INT REQ register not set by silo alarm.

0014

Silo alarm failed to clear after reading a character from silo.

0015

Master clear failed to reset the DZQ.

0016

Unexpected transmit interrupt occurred with interrupt mask it
vleared.

System Exerciser Eror Codes

Table F-6 (Comt.)

-5

Faital Device's Error Codes (00FF.ABCD)

Error

Codes

Definition

0017

Unexpected receive interrupt occurred with interrupt mask bit

0018

INT_MSK register bit ST failed to set.

0019

Failed to receive a transmit interrupt.

001A

Transmit interrupt occurred with INT_MSK bit ST cleared.

001B

INT_MSK register bit SR failed to set.

001C

Failed to receive a receive interrupt.

001D

Receive interrupt occurred with INT_MSK bit SR cleared.

001E

TRDY failed to set after setting line enable for line in TCR

cleared.

001F

F.2

TRDY failed to set in allotted time.

System Memory (MEM)

Error code format: XXXX.00YZ

Where XXXX indicates the status code and Y and Z indicate the type of
error. Table F-7 lists the codes.

When there is no error, the status code (XXXX.0001) indicates the number
of pages tested at the time of the report. Otherwise, the status code
indicates the failing test.

Table F-7

System Memory Error Codes (XXXX.00Y2)

Error Codes

Definition

0000.0001

Success—No error.

0001.000F

System software error.

0002.000F

System software error.

2003.000F

System software error.

F-6

System Exerciser Error Codes

Table F-7 (Comt.)

System Memory Error Codes (XXXX.00YZ)

Brror Codesn

Definition

0004.000F

System software error.

0005.000F

System software error.

0006.000F

System software error.

0007.000F

System software error.

0008.000F

System software error.

0001.001F

Compare error on system module.

0002.001F

Compare error on option module.

0001.002F

Parity error on system module.

0002.002F

Parity error on option module.

F.3

SCSI Bus Controller (SCSI-A and SCSI-B)

This section includes the codes for all of the SCSI bus controllers on both
systems.

Bus controller code format: TUVV.XYZ1
The letters T, U, VV, X, Y, and Z indicates the following:
Table F-8

Bus Controller Code Format Significance

Letter

Significance

SCSI address ID of the SCSI bus controller (should be a 6).

Resuits of the transfer test.

\'AY

The error count (in hexadecimal) during the transfer test.

Results of the interrupt test.

Results of the register test.

Resu s of the buffer test.

Drive error code format: JKLL.PRS1

System Exerciser Error Codes

F-7

The letters J, K, LL, P, R, and S indicate the following:
Drive Cude Format Significance

Letter

Significance

The SCSI ID of the drive (1 through 7).

Whether the drive is removable (1) or writable (2) or removable and

cnw*vg:

Table F-9

The error count (in hexadecimal) for the drive.

writable (3).

The last command on the SCS] bus.
The status of the drive.
The results of the routine test on the drive.

The follewing tables explain all error and status codes used:

Table F-10 lists the error codes for the U, X, Y, and Z bit positions.

Table F-11 lists the last command codes (P).

Table F-12 lists the codes for drive status (R).

Table F-10 lists the error codes for the routine status (S).

Table F-10

SCSi Bus Controller Error Codes (0U00.XYZ1) (0000.00S1)

Error Code

Definition

Success—No error.

Controller error:
DMA bit will not set in TPC controller MODE register.
Target command register is not valid.
Initiator command regis.er is not valid.

Bus free is not valid.
Phase Match bit in bus and status register is not valid.

Interrupt Request bit in bus and status register is not valid.
2

Data path error:

F-8

System Exerciser Error Codes

Table £-10 (Cont.)

SCSI Bus Controlier Error Codes (0UCD.XYZ1)
(0000.00S1)

Error Code

Definition

Data path in longword, word, or byte access failed.
Unable to access all of data buffer.

Unable to reach TPC controller, and unable to write to mode
register.

DMA count error:

Count register is not verified.
Count is not 0 after DMA transfer.
Timeout error:

No phase match within timeout period.
Interrupt error:

Interrupt is not received when expected.

An error eccurred while testing the system interrupt logic.
Unexpected interrupt e*ror:

Unexpected interrupt received.
Command error:

Request SENCE command ended without sence data.
Command terminated with bad device status.
Phase error:

Unexpected phase, or phase change on the SCSI bus.
Buffer overflow error:

Too many bytes read from target.
Arbitration error:

AIP bit in initiater command register not set during arbitration
process, or arbitration lost during arbitration process, or
arbitration not wan.

Target will not set BSY during selection process, the controller
is busy at start of register test, or the INI_CMIXBSY) bit did
not toggle during the register test.

System Exerciser Error Codes

Table F-10 (Cont.)

F-9

SCSI Bus Controller Error Codes (0UG0.XYZ1)
{0000.00S1)

Error Code

Definition

Unable to loop data out onto SCSI bus and back in again.

Direction and phase of SCSI bus as set by the target and read
from the controller are incompatible.

SCSI bus does not drop REQ within timeout peniod or SCSI bus

DMAEnd bit not verified in bus and status register or DMA

Table F-11

does not assert REQ within timeout period.
data not matching expected data.

Last Command on the SCSI Bus Codes (0000.P001)
Last Command

Com$unitready

Com$requestsence

Com$inquiry

Com$senddiagnostics

Com$recdiagnostics

Com$read

Com$write

Comé$rewind

Com$filemark

[

Bus Code

Table F-12

Com$mode_sense

Drive Status Codes (0000.0R01)

Status Code

Definition

Ready - Drive is on-line and ready for commands.

Off-line - Status given to devices that will not respona to

selection process or status given to all devices for initialization.

F-10

System Exerciser Error Codes

Table F-12 (Cont.)
Status Code
4

Drive Status Codes (0000.0R01)

Definition
Not ready - Status given to devices that are selectable, but

return & not ready status during status phase of a command
{(command tried five times).

Diagnostic error - Device returned an error status after a

self-test.

F.4

Key error - Unable to rewrite Field Service key on removable
media sequential device.

DSH32-B Asynchronous Subsystem (DSH32-A)

Status code and error code format: 00XX.YYYY
Line status code format: YYYY

where XX is a bitmap indicating which lines have failed and YYYY is the
error code for that line.
The line status code format, YYYY, is repeated for each of the eight
asynchronous lines.
Table F-13

Exerciser Error Codes for the DSH32-A Subsystem

Error Code’

Definition

0000

Fatal software error occurred making a call to ELN KERNEL.

0001

Normal SLU" module operation; no errors detected (00FF.G001).

0010

Control and status register failed read after write test.

0020

Controller is hung, internal hardware self-test never flagged
completion by cleaning CSR reset bit.

0030

Internal hardware self-test failed, diagnostic fail bit set.

0050

Receiver done not set following internal auto diagnostics.

0070

Could not find any valid data in receiver FIFO.

00B0O

Internal self-test error—Lov, octart error.

00CO

Internal self-test error—High octart error.

'Low 16 bits of the module information line or he appropriate 16-bits for a particular
communication line.

System Exerciser Error Codes

Table F-13 (Cont.)

Exerciser Error Codes for the DSH32-/ Subsystem

Ervor Code’

Definition

00D0

Internal self-test error—RAM error.

00EQ

Internal self-test error—Undefined status code found.

010Y

FIFO size register error; FIFO SB empty but size register

indicates FIFO is not.

o11Y

Transmitter did not become ready before timer expired
following ASCII character transmitted; nonfatal error.

0110

Transmitter did not become ready before timer expired
following ASCII character transmitted; fatal error.

012Y

F-11

Receiver done did not become ready before timer expired
following ASCII character transmitted.

019Y

FIFO data “received line” bit field indicates that the data was
received on the wrong port during simultaneous channel data
transmission test.

020Y

Transmit FIFO overrun error detected during simultaneous
channel data ‘. -ansmission test.

021Y

Framing error occurred during simultaneous channel data
transmission test.

022Y

Parity error occurred during simultaneous channel data

023Y

Data error cn port; channel 0 dropped from test.

024Y

Data error on port; channei 1 dropped from test.

025Y

Data error on port; channel 2 dropped from test.

026Y

Data error on port; channel 3 dropped from test.

027Y

Data error on port; channel 4 dropped from test.

028Y

Data error on port; channel 5 dropped from test.

029Y

Data error on port; channel 6 dropped from test.

02AY

Data error on port; channel 7 dropped from test.

02B0

All lines have been dropped—Deta wrap tests can no longer

transmission test.

run.

Hiow 16 bits of the module inforiration line or the appropriate 16-bits for a particular

communicat;on line.

F-12

System Exerciser Error Codes

Table F-13 (Cont.)
Error Code!
02C0

Euerciser Error Codes for the DSH32-A Subsystem

Definition

Receive FIFO contained more than eight internal self-test result

bytes.

02DY

Parity error detected during multiport data wrap test.

02EY

Framing error detected during multiport data wrap test.

02FY

Overrun error detected during multiport data wrap test.

0300

Time-out occurred waiting for transmitter interrupt service

0310

Time-out occurred waiting for receiver interrupts.

032Y

Data lost on line.

0330

Receiver done did not clear after emptying receive FIFO.

0340

Data error detected while testing RCVR FIFO.

0350

Status error found while testing RCVR FIFO.

0360

Ran out of usable ports in testing RCVR FIFO; all lines failed.

0370

256 character packet not completely received during FIFO test.

0380

Data valid not clear after emptying receive FIFO.

03390

Failed to force overrun error in receive FIFO test.

0400

Controller is hung, internal hardware skip self-test did not flag
completion by setting receiver done bit.

0420

Entire data packet lost during simultaneous transmission test.

043Y

Transmit FIFO did not have ennugh space to transmit entire

routine to flag completion of data packet transmission.

data packet during receive FIFO test.
0440

SLU requested an interrupt for an unused line; interrupt
requests should come from lines 0 through 7 only.

045Y

Data packet only partially received from FIFO when timer for
receive data expired.

0460

Data was received on an unused line. Data should come from
lines 0 through 7 only.

1000

The base system firmware returned a fatal status condition
when the exerciser requested a communication port with the
system exerciser monitor.
e

0w 16 bits of the mudule information line or the appropriate 16-bits for a particular
commun® _..isn line.

System Exerciser Error Codes

Tabie F-13 (Cont.)

F-13

Exerciser Error Codes for the DSH32-A Subsystem

Error Code’

Definition

1010

Found background monitor error code (307 octal) during receive

1020

Found background monitor error code (307 actal) during

1030

A read of the CSR register wes returned as all 1s. May
indicate that the controller beard is not firmly plagged into

FIFO test.

simultaneous channel transmission test.

the MicroVAX 2000 system module.

1040

A read of the RBUF register was returned as all 1s. May
indicate that the controller board is not firmly plugged into the
MicroVAX 3100 or VAXserver 3100 system module.

How 16 bits of the module infermation line or the appropriate 16-bits for a particular

communication line.

F.5

DSH32-B Synchronous Subtsystem (DSH32-S)

The error code format for both lines of the display is as follows:
XXXX.YYYY

Where XXXX 1s the status code and YYYY is the error code.
Table F-14

Exerciser Error Codes for DSH32-S Subsystem

Status

Error

Diagnostic

Code

Message Description

00XX

YYYY

Basic system module running okay (&
p line
displayed).

0001

0000

1 line (port 0) running, no lines failed

0011

0000

2 lines (port ¢ and port 1) running, no lines failed.

0000

0001

No lines runn' .g, 1 line (port 0) faiied.

0000

0011

No lines running, 2 lines (port 0 and port 1) failed.

0001

0010

1 line (port 0) running, 1 line (port 1) failed.

0010

0001

1 line (port 1) running, 1 line (port 0) failed.

0000

0001

Successful running of an individual port line (2nd
and/or 3rd lines displayed).

F-14

System Exerciser Error Codes

Table F~14 (Cont.)

Exerclser Error Codes for DSH32-S Subsystem

Status
Code

Error
Code

Diagnostic
Message Description

1XXX

YYYY

Module system ervors.

1000

0001

Unable to communicate with VSE monitor.

1100

YYYY

Unable to attach ISR to device reason masks.

1100

7C1C

1100

7C3C

Bad value--The device_variable argument is an array

1100

7C74

Device already connected---The device named 1n

Bad mode—The procedure was called from a program

that was not running in kernal mode.
with more than 16 elements.

the ker$create_device call 1s already connected to a
DEVICE value.

No access- An argument specified is not accessed to

1100

7CaC

1100

7CF0

No object—No free job object table entres available.

1100

7CE4

No pool—No free system pool is available.

11¢0

7CFC

No such device—The device name specified in a
Ker$create_device=. Call cannot be found in the hst

the callinrg program

of devices.

1100

D24

No system pages—
No free system page table entries
are available to map the VO region.

1200

YYYY

Unable to map interrupt registers to physical memory

1200

7C1C

mask.

Bad mode - The physical address argument was

specified by a program that was not running in

kernal mode.

1200

7C3C

1200

7C9C

1200

7CB4

Bad value—The virtual address argument is not the

job's address space.

No access—An argument specified is not accessible to

the calling program.

No memory--No free pages of physical memory are
available.

1200

1D04

No virtual--No free contiguous virtual address space
1s available for process.

Systerm Exerciser Error Codes

Table F-14 (Cont.)

F-15

E.erciser Error Codes for DSH32-S Subsystem

Statue

Error

Diagnostic

Code

Message Description

1300

YYYY

Unable to map tx/rx buffers to physical memory
mask.

1300

7C1C

Bad mode—The physical address argument was
specified by a program that was not running in
kernal mode.

1300

7C3C

Bad value—The virtual_address argument is not in
the job's address space.

1300

7C9C

No access—An argument specified is not accessible to
the calling program.

1300

7CB4

No memory—No free pages of physical memory are
avilable.

1300

7D04

No virtual-—No free contiguous virtual address space
is available for the process.

1400

YYYY

Unable to free mapped tx/rx buffers to physical
memory mask.

1400

7C3C

Bad value—The virtual_address argument is not in
the job's address space.

1500

YYYY

Unable to allocate device type memory.

1500

7C1C

Bad mode-The physical address argument was
specified by a program that was not running in
kernal mode.

200

7C3C

Bad value—The virtual _address argument is not in
the job’s address space.

1530

7C8C

No access—An argument specified is not accessible to
the calling program.

1500

7CB4

No memory—No free pages of physical memory are
available.

1500

7D04

No virtual —No free contiguous virtual address space

2XXX

YYYY

Interrupt service routine (Individual port errors).

2001

0001

(System ervor) illegal port 1 interrupt.

is available for the process.

F-16

System Exerciser Error Codes

Table F-14 (Cont.)

Exerciser Error Codes for DSH32-S Subsystem

Status
Code

Error
Code

Diagnostic
Message Description

2002

YYYY

2003

YYYY

2004

YYYY

2005

YYYY

UDMA receive current byte count error port 0 YYYY

2200

YYYY

(System error) illegal port number detected in ISR

3XXX

YYYY

Loopback connector error tindividual port errors).

3000

YYYY

Port 0 loopback connector mask.

3000

000F

No cable.

3000

000E

V.35 cable (not used).

3000

000D

RS$-423/V.24 cable.

3000

000C

X.21 cable (not used).

3000

0008

V36/RS-422

3000

0000

Loopvack cable.

4xxx

YYYY

Individual port errors during burst test.

4000

7CH4

Time-out occurred waiting for the device to see it
indicating oneration complete during functional mode

DUSCC I RSRA error bit set YYYY = input register
value.

DUSCC I transmit error bit set YYYY = input register

value.

UDMA transmit current byte count error port 0

YYYY = input regist v value.
= input register value.

YYYY = port number which will be more than 2.

test (port U4

411X

YYYY

(System error) kernal error while testing port 0 (X
= test mode: 1 = Customer, 2 = Field Service, 3 =
manufacturing).

411X

7C04

411X

7€34

Bad count—-The procedure call specified an incorrect
number of arguments.
Bad type --An argument in the object list 1s not a type
that can be waited tor.

System Exerciser Error Codes

Table F-14 (Cont.)

F-17

Exerciser Error Codes for DSH32-S Subsystem

Status

Error

Diagnostic

Code

Message Description

411X

7C3C

Bad value-—An argument in the object list is invalid
or refers to a deleted object.

411X

7C9C

No access—An argument specified is not accessible to

412X

7C54

Time-out occurred waiting for the device to set DONE
bit indicating operation complete during burst test of
port 0 (X = test mode: 1 = customer, 2 = Field Service,

the calling program.

3 = manufacturing).

413X

YYYY

(System error) kernal error while testing port 0 (X

413X

7C04

Bad count-—The procedure call specified an incorrect

= test mode: 1 = customer, 2 = Field Service, 3 =
manufacturing).
number of arguments.

413X

7C34

Bad type--An argument 1n the object list is not a type
that can be waited for.

413X

7C3C

Bad value—An argument in the object list is invalid
or refers to a deleted object.

413X

7C9C

No access —An argument specified is not accessible
to the calling program.

414X

7C54

Time-out occurred waiting for device to set DONE bit
indicating operation complete during burst test for
port 0 (X = test mode: 1 = customer, 2 = Field Service,
3 = manufacturing).

41A0

YYYY

{System error) kernal to wait _any returned
unsuccessfully.

41A0

7C04

Bad count—The procedure call specified an incorrect
number of arguments.

41A0

7C34

Bad type—An argument in the object list is not a type
that can be waited for.

41A0

7C3C

Bad value—An argument in the object list is invalid
or refers to a deleted object.

F~-18

System Exerciser Error Codes

Table F-14 (Cont.)

Exerciser Error Codes for DSH32-S Subsystem

Status

Error

Diagnostic

Code

Message Description

41A0

7C9C

5XXX

YYYY

Individual port memory errors.

50XX

YYYY

Unable to initialize port 0 tx buffer memory with a

No access—An argument specified 18 not accessible te

the calling program.

0 at address 3900.YYYY with XX + 1 memory errors

encountered.

52XX

YYYY

54XX

YYYY

Unable to wnite pattern byte to nort 0 tx buffer

memory at address 3900.YYYY with XX + 1 memory
errors encountered.

Unable to initialize port 0 rx buffer memory with a

0 at address 3900.YYYY with XX + 1 memory errors
encountered.

56XX

YYYY

{ nmparison of transmit and receive buffer for port

6XX A

YyYvy

SYNC RAM longword test errors.

6000

YYYY

0 did not match at address 3960.YYYY with XX + 1
differences found.

Unable to allocate memory 32 Kbytes of SYNC RAM
space.

6100

YYYY

Unabile to free 32 Kbytes of allocated SYNC RAM
space.

6200

YYYY

SYNC memory longword compare error detected at
address equal to 3300.8000 + offset YYYY.

F.6

Ethernet Network (Ni)

Error code format: 000X.ZZZZ

Where X indicates the test number and ZZZZ indicates the error code.
Table F-15 lists the test numbers and the type of tests done. Table F-16
lists tae error codes that can cccur on any test.

System Exerciser Error Codes

Table F-15

F-19

Ethernet Test Numbers (000X.0000)

Teat

Numbers

Definition

Initialization and check for interrupt.

Internal loopback (with interrupt).

Check that the computed CRC is accepted and the incorrect
CRC 1s rejected.

Multicast addressing and promiscuous receive.

5,6

Force collision, miss errors.

External loopback (with interrupt ).

Table F-16

Ethernet Error Codes (000X.2222)

Error Code

Definition

0001

Success—No error.

0002

No_packet_received.

0004

Packet_miscompare.

0006

Wrong_received_crc.

0008

Initialization_failed.

000A

Received_packet_with bad_crc.

000C

Crc_flag_not_set_when forced.

000E

Received_illegal_multicast.

0010

Rejected_packet_in_prom_mode.

0012

Rejected_legal _multicast.

0014

Rtry_not_set_when_forced.

0016

Buff_not_set_when_forced.

0018

Miss_not_set_when_forced.

001A

Transmit_error.

001C

Transmit_timeout.

Diagnostic LED Definitions

This appendix defines the significance of the eight LEDs on the back
of the system box during each phase of the testing and power-up
initialization.
The LEDs are divided into two fields. The first four LEDs
indicate the current state of the syst m and the second set of four depend
on the previous four.
There are 16 possible combinations for each set of LEDs. The first four
LEDs indicate a particular state of the diagnostics, the second four LEDs
indicate a substate. Refer to Table G-1. The namber 1 indicates that the
LED is hit.
Table G-1

Diagnostic LEDs Definitions

State

Substate

Definitions

Recoramendations

1111

Power is applied but no instruction

See Section G.1.

is executed.

0000

Power is applied. The ROM code
is successfuily started and several
instructions nave been executed.

See Section G.1.

1110

0000

Console merwory sizing routine
18 entered. ‘lemory to hold the
console date structures located. The

See Section G.1.

substate variables have no meaning
in this sect.on of the test.

1161

G000

The console data structures are
initialized and have started testing
the NVR.

See Section G.1.

G-2

Diagnostic LED Definitions

Table G~1 (Cont.)

Dlagnostit LEDs Definitions

State

Substate

Definitions

Recommendations

1100

0000

The NVR test, is completed and the

See Section G.1.

1011

0001

The DZ test 18 completed.

See Section G.1.

1010

0000

The console initialization sequence
is entered.

See Section G.1.

1001

oxx!

The system initializes and power-up
tests are executed.

If the substate
contains any lit
LEDs, determine
the failing device.
If you have a

DZ test started.

working terminal,
troubleshoot
that device. See
Section .1 1f the
terminal screen s
blank.

1000

The solf-test completes with the
substate indicating the failing
subsystem.

Enter TEST 50 to
see the results.

0111

Self-test was entered from the
console TEST command. The
substate indicates the test currently

Enter TEST 50 to
see the results,

being executed.
0110

0101

XXX

The self-test completes from the
test command with the substate
indicating the failing subsystem.

Enter TEST 50 to
see the results.

The self-test started under control
of the APT system. The substate
indicates the test currently being
executed.

Enter TEST 50 to
see the results.

'1111=Not used, 1110=CLK, 1101=NVR, 1100=DZ, 1011=MEM, 1010=-MM, 1001=FP.
1000=IT, 0111=SCSI-A, 0110=SCSI-B, 0101=S8YS, 0100=DSH32 A 0011=DSH3Z-S, 0001 =NI

Diagnostic LED Detinitions

Table G-1 (Cont.)

G-3

Dlagnostic LEDs Definitions

State

Subestate

Definitions

Recommendations

0100

soexx!

The system exerciser started from
a console TEST command. The
substate indicate the value of the
lower four bits of the command. If
the system exerciser starts with a
T 101, the substate contains a 1
{hexadecimal).

Read the test
results on the
screen.Troubleshoot
the failing device.

0011

0000

The system exerciser started under
the controi of the APT test delivery

Read the results
on the screen.
Troubleshoot the
failing device.

system.

0010

0001

0000

The entity-based module received
a request from a host to enter
monitor mode. This lets the hinst
send commands to the system. ITMis
is indicated if the functionality of
the EBM is implemented at a later
release of the system ROM.

Reserved for future

Console mode was successfully
entered and is ready to accept
commands. This does not apply to
power on. The substate indicates
the failing subsystem if there is
one. This differs from a self-test
complete, because the console can be
entered from other means.

This code indicates
that the console
was entered from
something other
than a TEST

Attempting to boot the system. Once
control passes to VMB, the state
LEDs have no meaning.

System 1is booting.

use.

command or power
on halt, such as the
HALT button.

11111=Not used, 1110=CLK, 1101=NVR, 1100=DZ, 1011=-MEM, 1010-MM, 1001=FP,

1000=IT, 0111=SCSI-A, 0i10=SCSI-B, 0101=8YS, 0100=DSH32-A, 0011=DSH32-8, 00601=NI

Figure G—1 shows the layout of the LEDs on the back of the system box.

Diagnostic LED Definitions

G-4

Figure G-1

LED Layout

State

G.1

Substate

Additional LED Information

When the system does not power up successfully or if the diagnostics find
an error, the eight LEDs on the back of the system box usually indicate
the failing device (the system takes 2 to 5 minutes to complete power-up
initialization and testing). However, if the four state LEDs indicate 1111
(F in hexadecimal) through 1010 (A in hexadecimal), the substate LEDs
offer no help in determining the failing FRU. You must disconnect an
FRU as described in each step in the following procedure until the system
does power up normally. Once th. system does power-up normally, the
last FRU you disconnected is the failing FRU. Replace the failing FRU
and reset the system for any further problems.
1.

Power down the system, remove drive mounting panel(s) from
the system, and remove the DSH32-B communications module (if
installed) from the system module. If the DSH32-B communications

module is not installed, proceed to step 3.
Power up the system with the DSH32-B communications module
disconnected. If the system still does not power up cornectly, the
problem is not in the DSH32-B communications module, proceed to
step 3. If the system does power up successfully, replace the DSH32-B
communications module and retest the system.

Power down the system, .emove the memory module from the system
module.

Power up the system with the memory module disconnected. If the
system does not power up correctly, the problem is not the memory
module, proceed to step 5. If the system does power up successfully,
replace the memory module and retest the system.

Power down the system, replace the system module and power up the
system again. If the system stiil does rnot power up correctly after
replacing the system module, replace the power supply.

H
Recommended Spares List
This appendix provides the recommended spares listing for the following:
e MicroVAX 3100, VAXserver 3100

Table H-1

e InfoServer 100

Table H-2

e DSH32 Communications Subsystem

Table H-3

e RZ55-Fx Disk Expansion Box

Table H-4

e TK50Z2-Gx Tape Expansion Box

Table H-5

e 5Z12x-xx Storage Exnansion Box

Table H-6

o RRD40-Fx Compact Disk Expansion Box

Table H-7

e Miscellaneous Parts

Table H-8

Table H-1

MicroVAX 3100 and VAXserver 3100 FRUs

Part Number

Description

Quantity

54-18856-01

MicroVAX 3100 svstem module {KA41-AA)

54-18856-02

VAXserver 3100 system module (KA41-BA)

54-18856-04

MicroVAX 3100 system module (KA41-DA)

54-18856-05

VAXserver 3100 system module (KA41-EA)

54-18858-01

Distribution board

54-19051-AA

4MB Memory Module (MS42-AB)

54-19850-AA

8MB Memory Module (MS42-KA)

54.18287-BA

12MB Memory Module (MS42-BA)

54-18324-AA

16MB Memory Module (MS42-CA)

H-1

H-2

Recommended Spares List

Table H-1 (Cont.)

MicroVAX 3100 and VAXserver 3100 FRUs

Part Number

Description

Quantity

RZ23-EG

RZ23 104MB SCS! disk drive assembly

25-27240-01

RZ23 module/frame assembly

29.28144-01

£.724 drive logic module PCB

29-28145-01

RZ24 head/disk assembly (HDA)

TZ30-AX

TZ30 95MB tape drive

12-19245-00

5 Vdc battery pack

RX23-A

1.4MB diskette drive

54-19288-01

RX23 FDI module

17 )2221-02

RX23 FDI ribbon cable

H7821-0u

AC power supply (Model 10e)

H7822-00

AC power supply (Model 20e)

17-02294-01

Cal'e from DSH32-B module te Distribution
board

170229501

Cable from system module to Distribution board

17-02296-01

SCSI-A cable

17-02297-01

SCSI-B cable

Power cable for upper drive mount‘ng panel

17-02299-01

devices

54-18324-AA

Power cable for lower drive mounting panel

devices
17-02568-01

DC power harness (model 10e system oni:®

17-02219-01

DC power harness (for devices on upper drive
mour ting panel - medel 20e system only)

DC power harness (for devices on lower drive

17-00606-02

BN19P-1K system AC power cord (USA)

17.01351-01

50-pin to 50-pin SCSI cable

17-01351-04

50-pin SCSI cabie (18 inches)

12-30552-01

50-pin SCSI terminator

17-02464-01

mounting panel - model 20e system only)

Recommended Spares List

Table H-2

H-3

(InfoServer 100 FRUs

Part Number

Description

Quantity

70-28103-01

InfoServer 100 system module (KA41-CA)

H7822

Power Supply (Models SEABB/BC-AX and -BX)

H7083-BA

Power Supply (Models SEABB/BC-CX and later)

12-19245-00

5 Vdc battery pack

17-02219-01

Wire harness assy (disk power cable)

17-02297-01

Cable assy 50 cond round (8CSI B cable)

Cable assy 50 cond round (SCSI B for SEABB

12-33816-01

Terminator single-ended SCSI (internal)

17-02909-01

Cable assy 50-cond flat (SCSI A/B dist)

RRD40-AA

RRD40 CD Drive assy (factory integrated)

Embeded RZ23 104MB SCSI disk drive

17-03209-01

RZ23-EG

/BC-CX and later)

assembly

RZ23L-EG
RRD42-AA

Embeded RZ23L 121MB SCSI disk drive

Embeded RRD42 CD Drive assy 1Models

assembly

SEABB/BC-BX, -CX and later)

H-4

Recommended Spares List

Table H-3

DSH32 Communications Subsystem FRUs

Part Number

Description

Quantity

54-18905-01

DSH32-B communications controller!

54-17230-01

DSH32-Yx driver'/receiver module (2nd sync)

H3104 36-pin to 8 6-pin cable concentrator

17.01174-02

Cable assembly, 36-cond (for DSH32-B)

17-02298-01

Ribbon cable (from DSH32-B to 2nd sync driver/

17-02294-01

Ribbon cable (from DSH32-B module to

17-01871-01

BC19U.02 external 50-pin cable for RS422

17-01872-01

BC19V-02 external 50-pin cable for RS232

17-01873-01

BC19W-02 external 50-pin cable for RS423

30-28253-01

assemlbly

receiver module)

distribution module)

"The DSH32-B and NSH32-Yx combined is the same as the DSH32-Ex versiun of the

communication module.

Table H-4

RZ55-Fx Disk Expansion Box FRUs (BA40B-AA)

Part Number

Description

Quantity

54-19325-01

SCSI ID switch module

54-17163-01

Resistor load module

17-02299-01

SCSI ID switch cable

17-01249-01

Irternal 50-pin data cable

17-00342-01

Internal power supply extension cable

17-01351-04

External 50-pin cable (1.5 feet)

17-00606-10

Power cord 120 Vac (USA)

H7848-BA

Power supply (120 Vac)

H7848-BB

Power supply (240 Vac)

RZ55.E

RZ55 332 MB disk drive assembly

29-27347-01

RZ55 logic module PCB

Recommended Spares List

Table H-5

H-5

TKS50Z-Gx Tape Expansion Box FRUs (BA40B-AA)

Part Number

Description

Quantity

54-19325-01

SCSI ID switch module

54-17639-01

TK5U controller module (TZK50-AA)

54-17163-01

Resistor load module

17-02299-01

SCSI ID switch cable

17-01397-01

Internal load module extension cable

17-01351-04

External 50-pin cable (1.5 feet)

Internal 50-pin data cable (TZK50 to external

17-01249.01

connector)

17-01249-01

Internal 50-pin data cable

17 00606-10

Power cord 120 Vac (USA)

H7848-BA

Power supply (120 Vac)

H7848-BB

Power supply (240 Vac)

TK50-AX

TK50 95MB tape drive assembly

Table H-6

SZ12x-xx Storage Expansion Box FrUs

Part Number

Description

Quantity

17-00365-19

Cable assembly, 3-conductor IEC-IEC jumper

17-09606-10

Power cord 120 Vac (USA)

17-02445-01

Ceble assembly, 68-posn to 50-pusn RT.

17-02444-01

Cable assembly, 50-conductor, flat

17-02445-01

Cable assembly, 10-conductor, flat

17-12446-02

Cable assembly, 50-conductor, n'd.

17-02447-01

Cable assembly, round, power harness

54-19325-02

ID select switch module

H7821-00

AC power supply

H-6

Recommendod Spares List

Table H-7

RRD40-Fx Compact Disk Expansion Box FRUs

Part Number

Description

Quantity

17-01351-04

External 50-pin cable (1.5 feet)

17-02008-01

External 38-pin cable

RRD40-DA

RRD40 600MB compact disk drive assembly

Table H-8

Miscellaneous Parts

Part Number

Description

Quantity

30-23507-03

RRDA40 test disk

12-15336-08

Asynchronous loopback 25-pin tmodem port, FS

12-25146-01

H3101 36-pin asynchronous loopback

12-25083-01

H3103 MMJ “spoon-type” loopback 6-pin

12-26259-01

H3198 37-pin RS422 loopback

12.25852.01

H3199 50-posn loopback, synchronous

12-32442-01

HB8575-A 25-pin to D-sub ESD passive adapter

12-25869-01

ThinWire Ethernet T-connector

12-26318-01

ThinWire Ethernet cable 50-ohm terminator

12-22196-01

Standard Ethernet loopback

12-30552-01

SCSI 50-pin termini:t:.

17-01351-01

50-pin to 50-pin SCHI e

17-01351-04

50-pin SCSI cable (18 inchi

RX23K-10

RX23 diskettes (pkg 1

H3248

25-pin asynchronous R5.235.2 loopback

mode)

Index

Bocting information, 7-1

BREAK ENABLE switch
InfoServer 100 systems, 8-5

Alternative console

Model 10 systems, 4-3

InfoServer 100 systems, 8-5
Model 10 systems, 4-3
Model 20 systems, 5-3

Model 20 systems, 5-3
use, 1-2

BREAK key
on keyboard, 1-2

Battery pack
removal and replacement

InfoServer 100
See Section 5.2.11
Model 10 systems, 4-21

Model 20 systems, 5-25
Battery testing

see Troubleshooting, nonvoiatile
RAM
Baud rate
coneole device, 1-2
InfoServer 100 port, 8-4
Baud rate adjustment

Model 1¢ systems, 4-24
Model 20 systems, 5-28
Beeper

TZ3C tape drive, 7-6
Boot
device
names, 3-12

settings, 3-11

flags

settings, 3-12

ULTRIX, 3-13
VMS, 3-14
BOOT

C
Cables

InfoServer 100, 8-2, H-3
Model 10 systems, H-2

Model 20 systems, H-2
Cabling
InfoServer 100 -AX model, 8-5
InfoServer 100 -BX or -CX model,
8-17

Model 10 systems, 4-5

Model 20 systems, 5-6
Cartridge leader
TZ30 tape drive, 7-5
Cartridge release handle
TK50Z, 7-23
Commands
self-test, 1- 8
system exerciser, 1-16

COMMENT console command, B--3
CompacTape/CompacTape II
cartridges
insertion, 7-8
COMPACTnpe/COMPACTape 11
cartridges
removal, 7-10
Compact disc

command description, 14

loading, 7-15

command qualifiers, B-2

repair, 7-18

console command, B-2

unloading, 7-16

index

Index

Configuration table, 1-7, 3-2
DSH32-B asynchronous
subsystem (DSH32-A)
information, 3-9

onsole test commands (cont'd)

aulity test commands, A-2
CCONTINUE

command description, 14

console command, B--3

memory (MEM) information, 3-5
SCS! bus (SCSI-A and SCSI-B)

Controls

serial line controlier (DZ2)

Cover

TK50Z, 7-23

information, 3-7

informat:on, 3-4

removal and replacement

InfoServer 100, 8-9

Connectors

InfoServer 100 systems, 8-11
Model 10 systems, 4-1
Model 20 systems, 51
gystem, 1-2

Console commands, B-1
BOOT, 1-4, B-2

COMMENT, B-3
CONTINUE, 1 4, B-3

DEPOSIT, B -3
DTE, B-5

EXAMINE, B-5
FIND, B-6

HALT, B-6
HELP, B-6
IN.TIALIZE, B-7

Model 10 systems, 4-4
Model 20 systems, 5-5

D
EFEPOSIT command, B-3
qualifiers, B-3

Device
console, 1-2

Dragnostics

TZ30 tape drive, 7-7

Diagnostic rest commands, A-1
Diskette drive, 7-11 to 7--14
Diskett2 formatter, 3-22
mossages, 3-23

REPEAT, B-7
SET, B-7
SHOW, B-9

Dis xettes

START, 14, B-11

Distmbution board

Sy:tax, B-1

TEST. B-11
UNJA I, B 1
XFER, B-12
Console device
baud rate, 1-2
Console messages
explanations, C-1

Console mode
exat, 1-4

how to enter, 1-3
special keys defined, B-13
usage, 1-1

Console test commands, A 1

diagnostic test commands, A-1

inserting into RX23, 7-13

removing from RX23, 7-14
removal and replacement
Mode! 10 systems, 4-7
Model 20 systems, 5-11
Drive mounting panel

removal and replacement
Model 10 systems, 4-5
Vrive select settings, 2-21

DSH32-B usynchronous subsystem
(DSH32-A)
.nformation in configuration
display, 3-9
power-up and self-test error
codes, E-15

svstem exerciser error codes,
F 10
troubleshooting, 2-34

index

DSH32-B synchronous subsystem

(DSH32-S)

Model 10 systems, 4-20
Model 20 systems, 5-25

Ethernet ID ROM removal

Model 10, 4-23

Model 10 systems, 4-19

Model 20, 5-28
removal and replacement

Model 20 systems, 5-24
Ethernet ports

Model 10 ¢ stems, 4-16

Model 20 systems, 5-21
system exerciser error codes,

F-13
troubleshooting, 2-39

DSH32-B synchronous subsystem(DSH32.

terminating, 1-13

EXAMINE command, B-5
qualifiers, B-5
Expansion boxes, 6-1
Extended summary
example, 1-21

reporting, 1-20

power-up and self-test error

codes, E-17
DTE console command, B-5
DZ port mnemonics
ULTRIX, 2-8
VMS, 2-8

Ethernet ID ROM location

communications module
options

FDI board
removal and replacement

Model 10 systems, 4-13

Model 20 systems, §-17

Field Replaceable Units

Enclosure description
InfoServer 100 systems, 8--1

Model 10 systems, 4-1

Model 20 systems, 5-1
Error codes
power-up test, 1-7

self-test, 1--13
system exerciser, 1--17

Ethernet circuits (N
power-up and self-test error

codes, E-18
system exerciser error codes,

F-18
troubleshooting, 2-44
Ethernet connection
InfoServer 100 systems, 8—4
Muodel 10 systems, 4-2

Meodel 20 systems, 5-2
Ethernet IDD ROM (SYS,
troubleshooting, 2-34

InfoServer 100 systems, 8-1

Model 10 systens, 4-1
Model 20 systems, §5-1

FIND command, B-6
qualifiers, B-6

Floating point (FP)
power-up and self-test error

codes, E-6
troubleshooting, 2-13

FRU locations
Model 10 gystems, 4-3
Model 20 systems, 54
FRU removal and replacement
InfoServer 100, 8-8
battery pack
See Section 5.2.11, 8-16
lower drive mounting panel,
8-13
power supply

See Secton 5.2.12, 8-16

RRD40 controller, 8-11
RRD42 CD drive, 8-16

index

FRU removal and replacement
InfoServer 100 (cont’d)
RZ23 disk drive, 8-16
systemn module, 8-16

upper drive mounting panel,

INTTIALIZE console command, B-7
Inserting
diskettes, 7-13
Interrupt controller and Ethernet 1D
ROM (5YS)

8-10

Model 10 systems, 4-3
jodel 20 systems, 5-3
RZ55 expansion box, 6-6

power-up and self-test error
codes, E-14

Interval timer (IT)
power-up end self-test error
codes, E-6

troubleshooting, 2-13

Halt button
location, 4-1, 5-1

HALT console command, B-6
Hard errors
description, 1-6

HELP console command, B-6

L
LED
use, 1-7

LED definitions, G-1
LED summary
TZ30 tape drive, 7--6

Lights

TK5H0Z, 7-21 to 7-23
baud rate, 8-4

Loading
cempact dise, 7-15

BREAK ENABLE switch, 8-5

Load/unload button

cables, 8-2
cover removal, 8-9

Loopback connectors, 1-11

FRU removal, 8-8

Loopbacks

InfoServer 100

FRU removal and replacement
battery pack
See Section 5.2.11
lower drive mounting panel,
8-13
power supply

TKS50Z, 7-23

usage, 1-14

use in system exerciser, 1- 15

Lower drive mounting panel
removal and replacement
InfoServer 100, 8

Model 20 systems. 5-8

See Section 5.2.12

RRD40 controller, 8-11
RRD4%2 CD drive, 8-16
RZ23 disk drive, 8-16
system module, 8-16
upper drive mounting panel,
8-10

FRUs, 8-1
input voltages, 8-5

models, 8-2

Memory
information in configuration
display, 3-5
Memory (MEM)
troubleshooting, 2--8

Memory management (MM)
power-up and self-test error

coder, E-6

index

Memory management (MM) (cont’d)
troubleshooting, 2-12

Memory module

removal and replacement
Model 10 systems, 4-17
Model 20 systems, 5-21

Memory modules
options

Model 10, 4-23
Model 20, 5-28
Model 10 system options

DSH32 1 communications
module, 4-23
memory mudule, 4-23
storage device positioning, 4~23

Model 10 systems
alternative console, 4-3

baud rate adjustment, 4-24
BREAK ENABLE switch, 4-3
enclosure description, 4-1

Ethernet connection, 4-2

Ethernet ID ROM removal, 4-19
Field Replaceable Units, 4-1
FRU locations, 4-3
FRU removal and replacement,
4-3

Model 20 system options
DSH32-B communications
module, 5-28
memory module, 5-28
Model 20 systems
alternative console, 5-3

baud rate adjustment, 5-28

BREAK ENABLE switch, 5-3
enclosure description, 5-1

Ethernet connection, 5-2
Ethernet ID ROM removal, 5-24

Field Replaceable Units, 5-1
FRU locations, 54
FRU removal and replacement,
5-3

battery pack, 5-25
cover, 5-5

distribution board, 5-11

DSH32-B communications
module, 5-21
FDI board, 5-17
lower drive mounting panel,
5-8

memory module, 5-21
power supply, 526

RX23 diskette drive, 5-17

battery pack, 4-21

RZ23 disk drive, 5-13

cover, 4—4

system module, 5-23

distribution board, 4-7
drive mounting panel, 4-5

TZ30 tape drive, 5-16
upper drive mounting panel,

DSH32.-B communications
module, 4-16

5-6

maodems, 5.2

FDI board, 4-13

ports and connectors, 5--1

memory module, 4-17
power supply, 4-22

printers, 5-2

RX23 diskette drive, 4-13
RZ23 disk drive, 4-9
system module, 4-19

TZ30 tape drive, 4-12

modems, 4-2
ports and connectors, 4-1
printers, 4-2
SCSI connection, 4 2

terminals, 4-2

SCSI connection, 5-2
terminals, 5-2
Modems
InfoServer 100 systems, 8-4

Model 10 systems, 4-2
Model 20 systems, 5-2

Index

Power-up and self-test error codes

(cont’d)

DSH32-B synchronous subsystem

Nonvolatile RAM (NVR)
power-up and self-test error
codes, £-3
troubleshooting, 2-5

o
Operating inforination

RRD40 compact disc drive, 7-15
Options

DSH32-B communications module
Model 10, 4-23
Model 20, 5-28
memory modules

Model 10, 4-23
Model 20, 5-28
storage device positioning

(DSH32-8), E--17

Ethernet circuits (ND), E-18
floating point (FP), E-6
interrupt controller and Ethernet
ID ROM (8YS), E-14
interval timer (IT), E--6

memory management (MM), E-6
nonvolatile RAM (NVR), E-3
SCSI bus controller (SCSI-A and
SCSI-B), E-7
serial line controller (DZ), E-3
system memory (MEM), E-5
time-of-year Clock (CLK), E-2
Power-up test, 3-2

Power-up test error codes

explanations, -1
Power-up testing

error codes, 1-7

Model 10, 4-23

example display, 1-5
summary display, 1-5

symbols, 1-6

Power-up tests
running, 1-5

Parameters

TK50Z tape drive, 7-21
TZ30 tape drive, 7-7

SET command, B- 7
SHOW command, B-9

Printers

Ports

Model 10 systems, 4-2

InfoServer 100 systems, 8-4

Model 20 systems, 5-2

Model 10 systems, 4-1
Model 20 systems, 5-1

Program mode, 1-1

system, 1-2

Prompts, 1-2

Power supply
InfoServer 100
See Section 5.2.12

removal and replacement

Q
Qualifiers

Moael 10 systems, 4-22

BOOT command, B-2

Model 20 systems, 5-26

DEPOSIT command, B-3

troubleshooting, 2-46

Power-up and seli-test error codes
DSH3%.-B asynchionous
subsystem (DSH32-A),
E-15

EXAMINE command, B-5
FIND command, B-6

index

RZ23 disk drive

removal and replacement (cont’d)

InfoServer 102, 8-16
Model 10 systems, 4-9

Recommended Spares List, H-1

Model 20 systems, 5-13

Recovery action getting, 3-16

SCSI ID setting, 2-22

Removing
diskettes, 7-14

Repair
compact discs, 7-18

REPEAT console command, 1-11,
B-7
RRD40/42 compact disc
troubleshooting, 2-33

troubleshooting, 2-31

RZ55 disk drive expansion box, 6-1
FRU locations, 6-6
FRU removal and replacement,
6--6
power supply, 6-17

resistor load board, 6-18
RZ65 disk drive, 6-7

RRD40 compact disc drive
cleaning a disc, 7-20
disk and caddy repair, 7-18

SCSI ID switch board, 8-15

FRUs, 6-1
SCSI ID setting, 2-28

InfoServer 100, 8-5

troubleshooting, 64

operating information, 7-15

loading a disc, 7-15
unloading a disc, 7-16
RRD40 compact disc drive expansion
box

SCSI ID setting, 2-25
RRDM40 compact disc expansion box,
6-19

removal and replacement, 6-22
troubleshooting, 6-20

RRD40 controller
InfoServer 100, 8-11
RRD42 compact disc drive
InfoServer 100, 8-5, 8-16

RX23 diskette drive, 7-11 to 7-14
drive select switch settings, 2-25
inserting diskettes, 7-13

removal and replacement

Model 10 systems, 4-13
Model 20 systems, 5-17
removing diskettes, 7-14
SCSI ID setting, 2-24
storage capacity, 7-12

troubleshooting, 2-32

RX23K diskettes, 7-1i2
RZ23 disk drive
removal and roplacement

S
SCSI address 1D assignments, 3-8
SCSI-A drives (SCSI-A)
troubleshooting, 2-13
SCST bus
address ID settings, 2-21
background information, 2-18
controller {SCSI-A and SCSI-B)
power-up and self-test error

codes, E-7
system exerciser error codes,

F-6
information in configuration
display, "-7
SCSI connection
InfoServer 100 systems, 8-4
Model 10 systems, 4-2
Modei 20 systems, 5-2
SCSI device
SCSI-B system exerciser code,
2-18
SCSI disk data eraser, 3-20
disk example, 3-20
error example, 3-20
messages, 3-21

Index

SCSI ID setting

RRD40 compact disc drive
expansion box, 2-25
RX23 disk drive, 2-24

RZ23 disk drive, 2-22
RZ55 disk drive expansion box,
J_98

TK50Z-GA tape drive expansion

box, 2-29
TZ30 tape drive, 2-21
Self-test, 3-2

SHOW command

parameters (cont'd)

ESTAT, B-9
ETHERNET, B-9
HALT, B-10
MEM, B-10
MOP, B-10

SCSIA, B-10

SCSIB, B-19
TRIG, B-10
VER, B-10

additional commands, 1-13
error codes, 1-13

SHOW DEVICE utility, 3-24
SHOW ESTAT command, 1-21

example display, 1-11

SHOW ESTAT utility, 3-25

running, 1-10

SHOW VER utility, 3-27

using loopback connectors, 1-11
Self-test commands, 1-8, 1-10
Self-test error codes

Spares list, H -1
Special attached terminal, 1-2
Special diagnostic key

explanations E--1
Self.t 'sting
ccmmands, 1-8

on tape cartridge, 3-18, 5-19
Special keyed media
use in system exerciser, 1-15

Serial line controller

Special key for system exerciser,

display, 3-4
Serial line controller (DZ)

Special keys, B-13
START

information in configuration

power-up and self-test error
codes, E-3
system exerciser error codes, F-1
troubleshooting, 2-6

Serial line port mnemonics, 2-8

SET command, B-7

parameters, B-7
BFLG, B-8

3-18

command description, 1-4
console command, B--11
Storage device positioning
options

Model 10, 4-23

System
console device, 1--2
ports and connectors, 1-2

BOOT, B-7

System (SYS)

HALT, B-8
MOP, B-8

System exerciser, 1-15

PSWD, B-8

commands, 1--16

SCSI-A, B-8

display example, 1-18

‘tRIG, B-9

extended summary reporting,

SCsI-B, B-9
SHOW command. B-9

parameters, B-9

troubleshooting, 2-34

error codes, 1-17, -1
1-20

on individual devices, 1-15

BFLG, B-9

running, 1-14

BOOT, B-3

using loopbacks, 1-15

DEVICE, B-9

Index

System exerciser diagnostics, 1-14
Syst ‘'m exerciser error codes

DSH32-B asynchronous
subsysiwem (DSH32-A),
F-10

DSH32-B Synchronous
Subsystem (DSH32-S),
F-13
Ethernet circuits (NI), F-18

SCSI bus controller (SCSI-A and
SCsI-B), F-6

serial line controller (DZ), F-1
system memory (MEM), F-5

System memory (MEM)
power-up and self-test error

codes, E-5
System memory (MEM)
system exerciser error codes, F-5

System module
removal and replacement

InfoServer 100, 8-16

Mode! 10 systems, 4-19
Model 20 systems, 5-23

ROM revision levels, 3-27

Terminals (cont'd)
Model 20 systems, 5-2
TEST 0
description, 1-16
TEST 101
description, 1-16
TEST 102

description, 1 16
TEST 50
use, 1-7

TEST 80000103

description, 1-17
TEST 80000106
description, 1-17

Test commands, A-1
TEST console command, B-11
Testing, 1-1
power-up, 1-6

Self-tes., 1-10

self-test commands, 1-10
system exerciser, 1-14

Time-of-year clock (CLK)
power-up and self-test error
codes, E-2

troubleshooting, 2-5
TK50 tape drive
troubleshooting, 2-31

Tape cartridge

special diagnostic key, 3-18, 3-19

Tape cartridges
ingerting TZ30, 7-8

loading, 7-21 to 7-22

TKS50Z
controls, 7-21

lights, 7-21 to 7-23
loading tape cartridges, 7-21 to
7-22

removing TZ30, 7-10

storage capacity, 7-21

TK50, 7-21

unloading, 7-23

removing, 7-23

storage capacity, 7-21

TK50Z, 7-21, 7-22

Terminal, 1-2
blank screen, 1-7

special attached, 1-2
Terminals
connecting, 4-2, 5-2, 8-4

InfoServer 100 systems, 84

Model 10 systems, 4-2

using, 7-21 to 7-24

TK50Z expansion box, 6-23
FRU removal and replacement,
6-28
power supply, 6-35

resistor load board, 6-37
SCSI ID switchboard, 6-37

TKS50 tape drive, 6-31
TZK50 controller board, 6-29
internal self-test, 6-26
troubleshooting, 6-24

Index

TK50Z-GA tape drive expansion box

TZ30 tape drive

SCSI ID setting, 2-29
Troubleshooting, 2-1

beeper, 7-6
cartridge lever, 7-5

DSH32-B asynchronous

controls and indicators, 7-4

subsystem (DSH32-A),

inserting tape cartridges, 7-8

2 34

integral to system unit, 7-4

DSH32-B synchronous subsystem

LED summ: y, 7-6

(DSH32'$)’ 2-39
Ethernet circuits (ND), 2-44

Mode! 10 systems
removal and replacement,

Ethernet ID ROM (8YS), 2-34
ficating point (FP), 2-13
general! DSH32-B communications module, 2-42
avoral SCSI bus, 2-14

4-12
Model 20 systems

removal and replacement,
5-16
operating information, 7-3

int:rval timer (IT), 2-13

operation, 7-7

memory (MEM), 2-8
memory management (MM), 2-12

power-up test, 7-7

removing tape cartridges, 7-10

non-operating system, 2-2

SCSI ID setting, 2-21

nonvolatile RAM (NVR), 2-5

storage capacity, 7-3

no screen display, 2-2
power supply, 2-46

troubleshooting, 2-31
Unload Button, 7-5

procedures, 2-1

RRD40/42 compact disc drive,

2-33

RRD4£Oconé_pggt disc expansion
X, O-0
RX23 diskette drive, 2-32
RZ23 disk drive, 2-31

UNJAM console command, B-11
Unload button
'
‘
U TZ":’S tape cartridge, 7-5

SCSI-A drives (SCSI-A), 2-13

U ompact dise, TI6

RZ55 disk expansion box, 64

SCSI-B drive (SCSI-B), 2-14
SCSI bus self-test, 2-15

nloading -

pper drive mounting pane

removal and replacement

SCSI bus self-test codes, 2-15
SCSI bus system exerciser, 2-16
SCSI bus system exerciser codes,

InfoSer"fir‘ 100, 8-10
Utiliti Model 20 systems, 5-6

SCSI drive address ID settings,

;‘;"}?gt‘gt}zxfii:' 3?_222

serial line controller (D2), 2-6

ean‘gsdTi‘,I{;‘m;_ggs (SHOW

tiyme-of-year
clock (CLK), 2-5
TK50 tape drive, 2-31

SCSI
disk data eraser, 3-20
setting default boot device, 3-11

TZ30 tape drive, 2-31

setting default recovery action,
3-16

2-17

2-21

system (SYS), 2-34

tlc:)tr:ri,a?\:il 31
’

ske

’

index

Utilities (cont’d)

SHOW DEVICE utility, 3-24
SHOW VER utility, 3-27
special key for FS system
exerciser, 3-18

writing special key tape
cartridges, 3-18, 3-19

Utility test commands, A-2

v
VMB boot ervor rtatus codes, D-1
VTxxx terminal, 1-2
VT terminsls, 4-2, 5-2

X
XFER console command, B-12