Digital PDFs

EK-BA641-IN-A01

March 1993

338 pages

Original

6.3MB

Document:	DEC 4000 Model 600 AXP Rackmount Series Installation/Owner's Guide
Order Number:	EK-BA641-IN
Revision:	A01
Pages:	338
Original Filename:

OCR Text

DEC 4000 Model 600 AXP
Rackmount Series Installation
/Owner’s Guide
Order Number: EK–BA641–IN. A01

Digital Equipment Corporation
Maynard, Massachusetts

First Printing, March 1993
The information in this document is subject to change without notice and
should not be construed as a commitment by Digital Equipment Corporation.
Digital Equipment Corporation assumes no responsibility for any errors that
may appear in this document.
The software described in this document is furnished under a license and may
be used or copied only in accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment
that is not supplied by Digital Equipment Corporation or its affiliated
companies.
© Digital Equipment Corporation 1993.
All Rights Reserved.
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: Alpha
AXP, AXP, CI, CompacTape, DEC, DECchip, DECdirect, DECnet, DNA, DSSI,
OpenVMS AXP, RRD42, RZ, ThinWire, TK, TZ, VAX, VAXcluster, VAXsimPLUS,
VMS, VMScluster, VT, the AXP logo, and the DIGITAL logo.
OSF/1 is a registered trademark of Open Software Foundation, Inc.
UNIX is a registered trademark of UNIX System Laboratories, Inc.
Xerox is a registered trademark of Xerox Corporation.
All other trademarks and registered trademarks are the property of their
respective owners.

This document was prepared using VAX DOCUMENT, Version 2.1.

DEC 4000 AXP (all configurations with RF/RZ73, RZ26 drives) acoustics —
declared values per ISO 9296 and ISO 7779 (June 22, 1992):

Idle
Operating

LwAd , B

LpAm , dBA
(Bystander Positions)

6.4
6.5

45
46

Current values for specific configurations are available from Digital
representatives. 1 B = 10 dBA.
Schallemissionswerte — Werteangaben nach ISO 9296 und ISO 7779
/DIN45635-19:

Leerlauf
Betrieb

Schalleistungspegel
LwAd , B

Schalldruckpegel
LpAm , dBA
(Zuschauerpositionen)

6.4
6.5

45
46

Aktuelle Werte für spezielle Ausrüstungsstufen sind über die Digital Equipment
Vertretungen erhältlich. 1 B = 10 dBA.

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

xix

1 Introduction
Introducing the DEC 4000 AXP Rackmount Server . . . . . . . . . .
The New Arrival . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Components and Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gaining Access to Controls . . . . . . . . . . . . . . . . . . . . . . . . . . .
Components: Front of System . . . . . . . . . . . . . . . . . . . . . . . .
Opening the OCP Door . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Components: Top of System . . . . . . . . . . . . . . . . . . . . . . . . . .
System Modules and Options . . . . . . . . . . . . . . . . . . . . . . . .
Power Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rear Compartment Components . . . . . . . . . . . . . . . . . . . . . .
Components: Bottom Tray . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–1
1–1
1–2
1–2
1–2
1–4
1–5
1–6
1–7
1–8
1–10
1–12
1–13

2 Installation
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before Installing Your System . . . . . . . . . . . . . . . . . . . . . . . .
Verifying the Site Preparation . . . . . . . . . . . . . . . . . . . . . . . . . .
Site Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Required Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tools Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unpacking the Shipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking the Shipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unpacking the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment Slides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–1
2–1
2–1
2–2
2–2
2–2
2–4
2–5
2–5
2–6
2–8
2–10
2–10

iii

Preparing the Slides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Slide Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Attaching Slide Races to Chassis . . . . . . . . . . . . . . . . . . . . . .
Locating the Rail Mounting Holes . . . . . . . . . . . . . . . . . . . . .
Installing System U-Nuts . . . . . . . . . . . . . . . . . . . . . . . . . . .
Attaching the Slides to Rails . . . . . . . . . . . . . . . . . . . . . . . . .
Mounting the Chassis on Equipment Slides . . . . . . . . . . . . . .
Installing the Interlock Actuator Bracket . . . . . . . . . . . . . . .
Installing the Cable Management System . . . . . . . . . . . . . . .
Preparing the System for Operation . . . . . . . . . . . . . . . . . . . . . .
Checking the Switch Settings . . . . . . . . . . . . . . . . . . . . . . . .
Connecting the Console Terminal and Modem . . . . . . . . . . . .
Connecting the Power Cords . . . . . . . . . . . . . . . . . . . . . . . . .
Expanding the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Turning On the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting to the Network . . . . . . . . . . . . . . . . . . . . . . . . . .

2–10
2–11
2–12
2–14
2–14
2–16
2–18
2–20
2–22
2–24
2–24
2–26
2–28
2–30
2–32
2–35
2–36

3 System Operation
Chapter Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Two Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operating System Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before You Start the System . . . . . . . . . . . . . . . . . . . . . . . . .
When to Start the System . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of the Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Up External Devices . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Up the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
If You Have a Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . .
Boot Operating System Software . . . . . . . . . . . . . . . . . . . . . .
Using the Operator Control Panel . . . . . . . . . . . . . . . . . . . . . . .
Before You Use the Control Panel . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Invoke Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reset the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Down the System . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Monitor Self-Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . .
Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–1
3–1
3–2
3–2
3–2
3–2
3–3
3–3
3–3
3–3
3–4
3–4
3–5
3–6
3–7
3–9
3–9
3–9
3–11
3–12
3–13
3–13
3–14

Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–14
3–15

4 Console Subsystem
Chapter Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What Is the Console Subsystem? . . . . . . . . . . . . . . . . . . . . . .
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Components of the Console Subsystem . . . . . . . . . . . . . . . . . . . .
Console Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Running the Console Program: Invoking Console Mode . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
From the Console Terminal . . . . . . . . . . . . . . . . . . . . . . . . . .
From the Auxiliary Serial Port . . . . . . . . . . . . . . . . . . . . . . .
From Across the Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Mode User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Keyboard Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–1
4–1
4–1
4–2
4–2
4–4
4–4
4–4
4–5
4–5
4–6
4–6
4–6
4–8

5 Console Commands
What Are the Console Commands? . . . . . . . . . . . . . . . . . . . . . . .
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Levels of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Basic Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Comprehensive Commands . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Console Commands . . . . . . . . . . . . . . . . . . . . . . . . . . .
New Console Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . .
Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Display Output One Page at a Time . . . . . . . . . . . . .
boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
cdp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
help or man . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
init . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
man . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
set host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–7
5–8
5–9
5–10
5–10
5–10
5–10
5–11
5–11
5–11
5–11
5–12
5–13
5–13
5–13
5–13
5–13
5–14
5–14
5–14
5–14
5–15
5–16
5–16
5–16
5–16
5–16
5–16
5–18
5–18
5–19
5–19
5–19
5–19
5–19
5–20
5–21
5–21
5–21
5–21
5–22
5–23
5–23

test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–24
5–24
5–24
5–24
5–25

6 Setting Environment Variables
Chapter Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What Is an Environment Variable? . . . . . . . . . . . . . . . . . . . .
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview: Do I Need to Set Environment Variables? . . . . . . . . .
Deciding to Set Environment Variables . . . . . . . . . . . . . . . . .
What Variables Can I Set? . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Current Environment Variables . . . . . . . . . . . . . .
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preliminary Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the Default Startup Action (auto_action) . . . . . . . . . .
Default Startup Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Your System’s Current Startup Action . . . . . . . . . . . . . . . . . .
Choosing ‘‘Halt’’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Choosing ‘‘Boot’’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Choosing ‘‘Restart’’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set the Default Startup Action . . . . . . . . . . . . . . . . . . . . . . .
Undo the Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting or Changing the Default Boot Device (bootdef_dev) . . . .
Default Boot Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Why Set the Default Boot Device? . . . . . . . . . . . . . . . . . . . . .
Your System’s Current Default Boot Device . . . . . . . . . . . . . .
Which One Is the Boot Device? . . . . . . . . . . . . . . . . . . . . . . .
Preliminary Considerations . . . . . . . . . . . . . . . . . . . . . . . . . .
Set or Change the Default Boot Device . . . . . . . . . . . . . . . . .
Undo the Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Boot Flags (boot_osflags) . . . . . . . . . . . . . . . . . . . . . . . . .
What Are Boot Flags? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Boot Flags Settings for OpenVMS AXP Systems . . . . . . . . . .
Boot Flags Settings for DEC OSF/1 AXP Systems . . . . . . . . .
Your System’s Current Default Boot Flags . . . . . . . . . . . . . . .
When to Set Boot Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set Boot Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the Language (language) . . . . . . . . . . . . . . . . . . . . . . . .
Do I Need to Set the Language? . . . . . . . . . . . . . . . . . . . . . .
Possible Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

vii

Your System’s Current Language . . . . . . . . . . . . . . . . . . . . . .
Change the Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the Baud Rate (tta0_baud and tta1_baud) . . . . . . . . .
Which Baud Rates Can I Change? . . . . . . . . . . . . . . . . . . . . .
Displaying the Current Baud Rates . . . . . . . . . . . . . . . . . . . .
Change the Baud Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enabling Halt Key Functions (tta0_halts and tta1_halts) . . . . . .
Why Enable Halt Key Functions? . . . . . . . . . . . . . . . . . . . . .
Possible Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Your System’s Current Halt Key Settings . . . . . . . . . . . . . . .
Set or Change the Halt Key Functions . . . . . . . . . . . . . . . . .
When You Have Finished Setting Variables . . . . . . . . . . . . . . . .
Reboot the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6–14
6–15
6–15
6–15
6–16
6–17
6–18
6–18
6–18
6–18
6–19
6–19
6–19

7 Operating Mass Storage Devices
Chapter Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
For Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . .
DEC 4000 AXP Rackmount Mass Storage Devices and
Compartments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Locating Mass Storage Devices . . . . . . . . . . . . . . . . . . . . . . .
Local Disk Converter (LDC) . . . . . . . . . . . . . . . . . . . . . . . . . .
Operating DEC 4000 AXP Rackmount Mass Storage Devices . . .
Before You Operate Mass Storage Devices . . . . . . . . . . . . . . .
Operating DEC 4000 AXP Rackmount Devices . . . . . . . . . . .
Operating RZ- and RF-Series Disk Drives . . . . . . . . . . . . . . . . .
RZ- and RF-Series Description . . . . . . . . . . . . . . . . . . . . . . . .
External Fast SCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RZ-Series Fault Light . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Write-Protecting an RF-Series and RZ-Series Disk . . . . . . . .
Operating the RRD42 Compact Disc Drive . . . . . . . . . . . . . . . . .
RRD42 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inserting a Compact Disc . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing a Compact Disc . . . . . . . . . . . . . . . . . . . . . . . . . . .
RRD42 Light . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operating the TLZ06 Tape Drive . . . . . . . . . . . . . . . . . . . . . . . .
TLZ06 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compatible Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inserting a Tape into the TLZ06 . . . . . . . . . . . . . . . . . . . . . .
Removing a Tape from the TLZ06 . . . . . . . . . . . . . . . . . . . . .
TLZ06 Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

viii

7–1
7–1
7–1
7–1
7–2
7–2
7–3
7–4
7–4
7–6
7–7
7–7
7–7
7–7
7–8
7–12
7–12
7–14
7–14
7–14
7–16
7–16
7–16
7–18
7–18
7–20

Operating the TZ30 Tape Drive . . . . . . . . . . . . . . . . . . . . . . . . .
TZ30 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compatible Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inserting a Tape into the TZ30 . . . . . . . . . . . . . . . . . . . . . . .
Remove Tapes Before Power-Down . . . . . . . . . . . . . . . . . . . .
Removing a Tape from the TZ30 . . . . . . . . . . . . . . . . . . . . . .
TZ30 Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintaining Mass Storage Media and Devices . . . . . . . . . . . . . .
Task Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting a Media Write Setting . . . . . . . . . . . . . . . . . . . . . . .
For More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Labeling Removable Media . . . . . . . . . . . . . . . . . . . . . . . . . .
Handling Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handling and Storing Discs and Caddies . . . . . . . . . . . . . . . .
Handling and Storing Tapes . . . . . . . . . . . . . . . . . . . . . . . . .
Cleaning the TLZ06 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cleaning the TZ30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7–21
7–21
7–21
7–24
7–26
7–26
7–28
7–29
7–29
7–29
7–29
7–30
7–30
7–31
7–32
7–32
7–33
7–34

8 System Configuration
Chapter Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Identifying Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Types of Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Special Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dual CPU Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DSSI VMSCluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Benefits of a DSSI VMScluster . . . . . . . . . . . . . . . . . . . . . . .
Identifying System Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifics of Your Configuration . . . . . . . . . . . . . . . . . . . . . . . .
System Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Internal Mass Storage Devices . . . . . . . . . . . . . . . . . . . . . . . .
External Mass Storage Devices . . . . . . . . . . . . . . . . . . . . . . .
Network Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Identifying Mass Storage Devices . . . . . . . . . . . . . . . . . . . . . . . .
DSSI and SCSI Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Configuration Information Online . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying System Configuration . . . . . . . . . . . . . . . . . . . . .

8–1
8–1
8–1
8–2
8–2
8–2
8–4
8–4
8–4
8–4
8–5
8–6
8–6
8–6
8–6
8–7
8–7
8–7
8–7
8–8
8–8
8–8

Displaying Memory Information . . . . . . . . . . . . . . . . . . . . . .
Displaying Device Information . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Console Program Version . . . . . . . . . . . . . . . . . . .
Displaying PALcode Version . . . . . . . . . . . . . . . . . . . . . . . . . .
Planning a Change to Your Configuration . . . . . . . . . . . . . . . . . .
Perform Pre-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Third-Party Devices . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting Additional Devices to Your System . . . . . . . . . . . . . .
External Media Expansion Ports . . . . . . . . . . . . . . . . . . . . . .
DSSI/SCSI Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Extending the Internal Bus (SCSI Only) . . . . . . . . . . . . . . . .
Terminating and Extending a SCSI Bus . . . . . . . . . . . . . . . .
Terminating and Extending a DSSI Bus . . . . . . . . . . . . . . . .
Example of Terminating and Extending a Bus . . . . . . . . . . . .
Terminating an Extended Bus . . . . . . . . . . . . . . . . . . . . . . . .
Changing Drive ID Numbers (External Media) . . . . . . . . . . . . . .
When to Change Drive ID Numbers . . . . . . . . . . . . . . . . . . .
Changing a Drive ID: Rules . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting and Examining Parameters for DSSI Devices . . . . . . . .
When to Change DSSI Device Parameters . . . . . . . . . . . . . . .
Changing DSSI Device Parameters: Rules . . . . . . . . . . . . . .
Using cdp and show device du pu Commands . . . . . . . . . . . .
show device du pu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
cdp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DSSI Device Parameters: Definitions and Function . . . . . . .
DSSI Device Parameter Descriptions . . . . . . . . . . . . . . . . . . .
How OpenVMS AXP Uses the DSSI Device Parameters . . . .
Example: Modifying DSSI Device Parameters . . . . . . . . . . . .
Using the Power Control Bus with a Storage Expander . . . . . . .
Power Control Bus for Expanded Systems . . . . . . . . . . . . . . .
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8–10
8–11
8–13
8–13
8–14
8–14
8–15
8–16
8–16
8–16
8–16
8–18
8–18
8–18
8–18
8–20
8–20
8–20
8–21
8–21
8–21
8–21
8–22
8–23
8–23
8–24
8–25
8–26
8–29
8–29
8–30

9 Learning More About Your System
Chapter Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What Makes It a DEC 4000 AXP Rackmount System? . . . . .
Alpha AXP Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RISC Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Support of Multiple Operating Systems . . . . . . . . . . . . . . . . .
Integration with Existing Technology . . . . . . . . . . . . . . . . . . .

9–1
9–1
9–1
9–2
9–2
9–2
9–2
9–3
9–3

DSSI VMScluster Support . . . . . . . . . . . . . . . . . . . . . . . . . . .
Subsystems and Components . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CPU Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Central Processing Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Memory Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I/O Daughter Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serial Control Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uninterruptible Power Supply (Optional) . . . . . . . . . . . . . . .
Storage Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mass Storage Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mass Storage Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mass Storage Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Futurebus+ Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9–3
9–4
9–4
9–6
9–6
9–6
9–6
9–7
9–7
9–8
9–8
9–9
9–9
9–9
9–10
9–10
9–10
9–10
9–10
9–11
9–11
9–11

10 Care, Maintenance, and Exterior Customizations
Chapter Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customizing the System Unit . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Locate Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Label the System Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replace English-Language Labels . . . . . . . . . . . . . . . . . . . . .
Antistatic Wrist Strap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the Baud Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintaining the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Environmental Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . .
Liquid on the System Unit . . . . . . . . . . . . . . . . . . . . . . . . . . .

10–1
10–1
10–1
10–1
10–1
10–2
10–4
10–6
10–6
10–7
10–9
10–9
10–9
10–9

11 Troubleshooting the System
Chapter Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Two Ways to Solve System Problems . . . . . . . . . . . . . . . . . . .
Method to Identify Problems . . . . . . . . . . . . . . . . . . . . . . . . .
Task Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Steps to Identifying a Problem . . . . . . . . . . . . . . . . . . . . . . . .
Determining Type of Problem . . . . . . . . . . . . . . . . . . . . . . . . . . .
Types of System Problems . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Supply Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problems Getting to Console Mode . . . . . . . . . . . . . . . . . . . . . . .
Pre-Console Mode Problems . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator Control Panel Lights . . . . . . . . . . . . . . . . . . . . . . . .
Console Mode Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Mode Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Boot Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Boot Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operating System Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operating System Problems . . . . . . . . . . . . . . . . . . . . . . . . . .
Mass Storage Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mass Storage Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RRD42 Disc Caddy Removal Problem . . . . . . . . . . . . . . . . . .
Network Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reporting Problems to Digital Services . . . . . . . . . . . . . . . . . . . .
Digital Support Centers . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Report Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Digital Support Center Contact Numbers . . . . . . . . . . . . . . .
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11–1
11–1
11–1
11–2
11–2
11–2
11–3
11–3
11–4
11–4
11–5
11–5
11–5
11–9
11–9
11–10
11–12
11–12
11–13
11–13
11–14
11–14
11–15
11–15
11–17
11–18
11–18
11–19
11–19
11–19
11–19
11–20

12 Removal and Installation Procedures
Chapter Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FRU Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Accessing Top FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Extending Chassis For Service . . . . . . . . . . . . . . . . . . . . . . . .

xii

12–1
12–1
12–2
12–2
12–5
12–5

Placing the System Back into the Rack . . . . . . . . . . . . . . . . .
Accessing Bottom FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Opening the Bottom Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Closing the Bottom Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bottom Tray, Removal/Installation . . . . . . . . . . . . . . . . . . . . . . .
Bottom Tray, Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bottom Tray, Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modules, Removal/Installation . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Module Location and Installation . . . . . . . . . . . . . . . . . . . . . .
B2001 CPU Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B2002 Memory Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B2101-AA I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B2101-BA I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OCP, Removal/Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OCP Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OCP Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I/O Daughter Board Assembly, Removal/Installation . . . . . . . . .
I/O Daughter Board Assembly Removal . . . . . . . . . . . . . . . . .
I/O Daughter Board Assembly, Installation . . . . . . . . . . . . . .
LDC Board, Removal/Installation . . . . . . . . . . . . . . . . . . . . . . . .
LDC Board Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LDC Board Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fan, Removal/Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fan Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fan Assembly Installation . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disk Drives, Removal/Installation . . . . . . . . . . . . . . . . . . . . . . . .
Types of Disk Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disk Drive Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the ID Jumper or Switches . . . . . . . . . . . . . . . . . . . .
Disk Drive Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fingerstock, Removal/Installation . . . . . . . . . . . . . . . . . . . . . . . .
When to Replace Fingerstock . . . . . . . . . . . . . . . . . . . . . . . . .
Fingerstock Lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fingerstock Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCSI to DSSI Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCSI to DSSI Adapters, Installation . . . . . . . . . . . . . . . . . . .
Backplane, Removal/Installation . . . . . . . . . . . . . . . . . . . . . . . . .
Backplane, Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pull Out the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remove the System Modules and the Power System
Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Lower the Bottom Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12–8
12–10
12–10
12–12
12–13
12–13
12–16
12–17
12–17
12–17
12–18
12–20
12–22
12–24
12–26
12–26
12–26
12–28
12–28
12–32
12–33
12–33
12–33
12–35
12–35
12–36
12–38
12–38
12–39
12–41
12–41
12–43
12–43
12–43
12–44
12–45
12–45
12–47
12–47
12–47
12–47
12–47

xiii

Remove the Bottom Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remove the Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12–48
12–50
12–50

A Specifications
B Field Replaceable Units (FRU)
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B–1
B–1

Booting OpenVMS AXP System Software Screen . . . . . . . . . .
Booting DEC OSF/1 AXP System Software Screen . . . . . . . .
Setting Hardware Write-Protection Through Firmware . . . . .
System Configuration Display . . . . . . . . . . . . . . . . . . . . . . . .
Memory Configuration Display . . . . . . . . . . . . . . . . . . . . . . .
Device Configuration Display . . . . . . . . . . . . . . . . . . . . . . . . .
Console Program Version . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PALcode Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–8
3–8
7–11
8–9
8–10
8–11
8–13
8–13

Location of System Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Front Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unlocking the OCP Door . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Top View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Modules and Options . . . . . . . . . . . . . . . . . . . . . . . .
Power Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rear Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bottom Tray Components . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Clearance Requirements . . . . . . . . . . . . . . . . . . . . . .

1–3
1–4
1–5
1–6
1–7
1–9
1–11
1–12
1–14
2–3

Glossary
Index
Examples
3–1
3–2
7–1
8–1
8–2
8–3
8–4
8–5

Figures
1–1
1–2
1–3
1–4
1–5
1–6
1–7
1–8
1–9
2–1
xiv

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

Shipping Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Slide Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Attaching Slide Races . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Establishing Mounting Location . . . . . . . . . . . . . . . . . . . . . .
Attaching the Slides to the Cabinet Rails . . . . . . . . . . . . . . .
Installing the System on the Slides . . . . . . . . . . . . . . . . . . . .
Installing the Interlock Actuator Bracket . . . . . . . . . . . . . . .
Installing the Cable Management System . . . . . . . . . . . . . . .
Switch Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modem and Console Connections . . . . . . . . . . . . . . . . . . . . . .
Power Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCSI and DSSI Connections . . . . . . . . . . . . . . . . . . . . . . . . .
Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Option 1: ThinWire Ethernet Connection . . . . . . . . . . . . . . .
Option 2: Standard Ethernet, Thickwire Connection . . . . . . .
Option 3: 10BASE-T (Twisted-Pair) Connection . . . . . . . . . .
System Power-Up Self-Test Screen . . . . . . . . . . . . . . . . . . . . .
Sample Power-Up Configuration Screen . . . . . . . . . . . . . . . . .
Operator Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supported Keys on a VT420 Keyboard . . . . . . . . . . . . . . . . .
Bottom Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RRD42 Compact Disc Drive and Compact Disc . . . . . . . . . . .
Inserting and Removing a Compact Disc . . . . . . . . . . . . . . .
TLZ06 Drive and Compatible Tape . . . . . . . . . . . . . . . . . . . .
Inserting and Removing a Tape: TLZ06 . . . . . . . . . . . . . . . . .
TZ30 Tape Drive and Compatible Tape . . . . . . . . . . . . . . . . .
Inserting a Tape into the TZ30 . . . . . . . . . . . . . . . . . . . . . . .
Removing a Tape from the TZ30 . . . . . . . . . . . . . . . . . . . . . .
Affixing Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Caddy Shutter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Types of Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Device Name Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mass Storage Bus Expansion Ports . . . . . . . . . . . . . . . . . . . .
Terminating and Extending a Bus . . . . . . . . . . . . . . . . . . . . .

2–7
2–11
2–13
2–15
2–17
2–19
2–21
2–23
2–25
2–27
2–29
2–31
2–33
2–34
2–37
2–38
2–39
3–5
3–6
3–10
4–3
4–7
7–5
7–13
7–15
7–17
7–19
7–23
7–25
7–27
7–30
7–31
8–3
8–12
8–17
8–19

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

xvi

How OpenVMS AXP Sees Unit Numbers for DSSI
Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample DSSI Buses for an Expanded DEC 4000 AXP
Rackmount System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample Power Bus Configuration . . . . . . . . . . . . . . . . . . . . . .
DEC 4000 AXP Rackmount System Architecture . . . . . . . . . .
Accessories Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Labeling the System Name . . . . . . . . . . . . . . . . . . . . . . . . . .
Location of the Baud Rate Switch . . . . . . . . . . . . . . . . . . . . .
Power Supply Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator Control Panel Lights . . . . . . . . . . . . . . . . . . . . . . . .
Manually Removing a Disc Caddy . . . . . . . . . . . . . . . . . . . . .
Location of FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing the Front Bezel . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pulling Out the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Placing System Back Into the Rack . . . . . . . . . . . . . . . . . . . .
Opening the Bottom Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing the Bottom Tray . . . . . . . . . . . . . . . . . . . . . . . . . .
B2001 CPU Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B2002 Memory Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B2101-AA I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B2101-BA I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing the OCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I/O Daughter Board Cable Connections . . . . . . . . . . . . . . . . .
Removing the I/O Daughter Board Assembly . . . . . . . . . . . . .
Removing the LDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing the Fan Assembly . . . . . . . . . . . . . . . . . . . . . . . . .
Removing a Disk Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removable-Media Drive Mounting Bracket, Mounting
Holes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fingerstock Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example of Connection Using SCSI to DSSI Adapter . . . . . .
Removing the Bottom Tray . . . . . . . . . . . . . . . . . . . . . . . . . .
I/O Daughter Board Cable Connections . . . . . . . . . . . . . . . . .
Removing the Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8–26
8–27
8–30
9–5
10–3
10–5
10–8
11–6
11–10
11–17
12–4
12–6
12–7
12–9
12–11
12–15
12–19
12–21
12–23
12–25
12–27
12–29
12–31
12–34
12–37
12–40
12–42
12–44
12–46
12–49
12–51
12–52

Tables
2–1
5–1
5–2
6–1
7–1
7–2
7–3
7–4
9–1
11–1
11–2
11–3
11–4
11–5
11–6
11–7
11–8
11–9
11–10
11–11
11–12
11–13
11–14
12–1
12–2
A–1
B–1
B–2

Accessory Kit Contents (P/N 70-30535-01/02) . . . . . . . . . . . .
Basic Console Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Differences Between VAX and DEC 4000 AXP Rackmount
Console Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Devices Supported Internally to the DEC 4000 AXP
Rackmount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Devices Supported Externally to the DEC 4000 AXP
Rackmount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TLZ06 Light Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TZ30 Light Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DEC 4000 AXP Rackmount Subsystems . . . . . . . . . . . . . . . .
How to Identify a Problem . . . . . . . . . . . . . . . . . . . . . . . . . . .
Steps to Resolving Problems . . . . . . . . . . . . . . . . . . . . . . . . .
Type of Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostic Flow for Power Problems . . . . . . . . . . . . . . . . . . .
Interpreting Power Supply Lights . . . . . . . . . . . . . . . . . . . . .
Diagnostic Flow for Problems Getting to Console . . . . . . . . . .
Interpreting Operator Control Panel Lights . . . . . . . . . . . . . .
Diagnostic Flow for Console Mode Problems . . . . . . . . . . . . .
Diagnostic Flow for Boot Problems . . . . . . . . . . . . . . . . . . . .
Diagnostic Flow for Operating System Errors . . . . . . . . . . . .
Diagnostic Flow for Mass Storage Problems . . . . . . . . . . . . .
Manual Removal of a Disc Caddy . . . . . . . . . . . . . . . . . . . . .
Resolving Ethernet Problems . . . . . . . . . . . . . . . . . . . . . . . . .
Telephone Numbers of Digital Support Centers . . . . . . . . . . .
Recommended Spares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fingerstock Replacement Lengths . . . . . . . . . . . . . . . . . . . . .
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recommended Spares List Unique to the DEC 4000 AXP
Rackmount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other Field Replaceable Units (FRUs) . . . . . . . . . . . . . . . . . .

2–8
5–2
5–3
6–3
7–6
7–6
7–20
7–28
9–4
11–2
11–3
11–4
11–5
11–7
11–9
11–11
11–12
11–13
11–14
11–15
11–17
11–18
11–20
12–3
12–43
A–1
B–2
B–3

xvii

Preface

Purpose of This
Guide

This guide describes how to install, operate, troubleshoot, and
maintain the DEC 4000 AXP Rackmount system.

Who Should
Use This Guide

This guide is for Digital service personal or qualified selfmaintenance customers who are familiar with installing
computer systems, and for system managers and others who
perform system management tasks.

Structure of
This Guide

This guide contains information about installing and using your
system to best advantage:
•

Chapter 1 introduces the system.

•

Chapter 2 describes how to install your system into a
standard EIA 19-inch cabinet and make the appropriate
connections.

•

Chapter 3 describes the basic system management tasks and
how to start the system.

•

Chapter 4 describes how to use the console mode
environment.

•

Chapter 5 describes the console commands.

•

Chapter 6 describes how to set environment variables.

•

Chapter 7 describes how to operate mass storage devices.

•

Chapter 8 describes how to identify your system
configuration and how to change your configuration.

•

Chapter 9 describes system features.

•

Chapter 10 describes how to maintain your system and
customize its exterior.

xix

Finding More
Information

•

Chapter 11 explains how to identify and resolve problems
that prevent you from operating the system.

•

Chapter 12 provides the removal and installation procedures
for the recommended spare parts. This chapter is for use
by Digital customer service personnel and qualified
self-maintenance customers only.

•

Appendix A provides the specifications for the DEC 4000
AXP Rackmount Series System.

•

Appendix B lists the recommended spare parts and other
system field replaceable units unique to the DEC 4000 AXP
Rackmount Series System.

•

The Glossary contains technical terms that are used in this
book.

Occasionally, this guide directs you to a different document (also
listed below). The last page of each chapter shows you where to
find more information about the topics in that chapter.
•

DEC 4000 Model 600 Series Site Preparation Checklist
(EK-KN430-SP)

•

DEC 4000 Model 600 Series Technical Manual (EK-KN430TM)

•

DEC 4000 AXP Model 600 Series Service Guide (EK-KN430SV)

•

DEC 4000 AXP Model 600 Series Options Guide (EK–KN430OG)

•

R400X Expander Installation (EK–R400X–CM)

•

OpenVMS Alpha Version 1.0 Upgrade and Installation
Manual (AA–PQYSA–TE)

•

Network Installation Guide for your network

Conventions

The following table lists conventions used in this guide.

Convention

Meaning

Return

A key name enclosed in a box indicates that you press that key.

Ctrl/x

Ctrl/x indicates that you hold down the Ctrl key while you
press another key, indicated here by x. In examples, this key
combination is enclosed in a box, for example, Ctrl/C .

lowercase

Lowercase letters in commands indicate that commands can be
entered in uppercase or lowercase.
In some illustrations, small drawings of the DEC 4000 AXP
Rackmount system appear in the left margin. Shaded areas
help you locate components on the front or back of the system.

Warning

Warnings contain information to prevent personal injury.

Caution

Cautions provide information to prevent damage to equipment
or software.

Note

Notes call the reader’s attention to any item of information
that may be of special importance.

[]

In command format descriptions, brackets indicate optional
elements.

console command
abbreviations

Console command abbreviations must be entered exactly as
shown.

boot

Console and operating system commands are shown in this
special typeface.

italic type

Italic type in console command sections indicates a variable.

In console mode online help, angle brackets enclose a
placeholder for which you must specify a value.

{}

In command descriptions, braces containing items separated by
commas imply mutually exclusive items.

! "# ...

In figures, labels a part of the figure. In text, refers to a
labeled part of a corresponding figure.

xxi

Safety Symbols

The following symbols appear on the power supply. Please review
their definitions below:
This Dangerous Voltage warning symbol indicates
risk of electric shock and indicates hazards from
dangerous voltage.
This Attention symbol is used to alert readers
about specific safety conditions, and to instruct
the reader to read separate instructional
material.

xxii

1
Introduction
Introducing the DEC 4000 AXP Rackmount Server
The New Arrival

Congratulations on the purchase of your new DEC 4000 AXP
Rackmount system!

X=32.975
Y=26.974
SCALE=1/8
NUO-420-00-DG

Introduction 1–1

Introducing the DEC 4000 AXP Rackmount Server

In This Chapter

The DEC 4000 AXP Rackmount system is a high-performance
superserver for multi-user environments. The system is
contained in a slide-mounted chassis that fits into a standard
48.26-cm (19-inch) EIA enclosure.
This chapter introduces you to the location of the system
components and controls.

Components and Controls
Gaining Access
to Controls

System components and controls are located at the front, top,
rear, and bottom of the system.
There are different ways to access the system components and
controls, depending on their location. The front components
(Operator Control Panel (OCP) and removable-media mass
storage compartments) are accessible through openings in the
front bezel. A key is used to open a door to gain access to
the OCP. The key comes in a plastic bag taped to the top of
the accessories box that is shipped with your DEC 4000 AXP
Rackmount system. Figure 1–1 shows the location of the keys in
your system shipment.
The rear components are accessible through the rear opening in
the host cabinet.
The top components are accessible by removing the front bezel
and pulling the system out of the cabinet.
The bottom components are located in a hinged tray in the
bottom of the system chassis. You gain access to these
components by removing the front bezel, pulling the system
out of the cabinet, and then unlatching and lowering the hinged
bottom tray from the right-hand side.

1–2 Introduction

Components and Controls

Figure 1–1 Location of System Keys

NUO-420-01-DG

Introduction 1–3

Components and Controls

Components:
Front of
System

Figure 1–2 shows the components on the front of the system.
Figure 1–2 Front Components
1

NUO-420-03-DG

! Operator control panel (OCP)
" Air plenum
# Removable-media mass storage device
$ Removable-media mass storage device
For information about mass storage controls, refer to devicespecific information in Chapter 7 of this guide.

1–4 Introduction

Components and Controls

To open the OCP door, unlock the door
and pull the upper
right edge toward you
as shown in Figure 1–3.

Figure 1–3 Unlocking the OCP Door

X=32.975
Y=26.974

0 1

Opening the
OCP Door

2
SCALE=1/8

NUO-420-02-DG

Introduction 1–5

Components and Controls

Operator
Control Panel

Figure 1–4 shows the individual controls and indicators on the
OCP.
Figure 1–4 Operator Control Panel

Halt
6-1

MEM

0 1

Reset

CPU

I/O

2
NUO-420-04-DG

! DC power light
" Self-test status lights
# Halt button
$ Reset button

1–6 Introduction

Components and Controls

Components:
Top of System

Figure 1–5 shows the major components in the top of the
system.
Figure 1–5 Top View

NUO-420-05-DG

! Rear compartment (contains fans, I/O daughter board)
" AC circuit breaker
# System modules and options
$ Power subsystem

Introduction 1–7

Components and Controls

System
Modules and
Options

Figure 1–6 shows the module locations, lights, switches, and
connectors on the card cage in the top of the system.

! Ethernet port 1
" Ethernet port 21
# Thickwire fuse OK indicator
$ Thickwire port
% Select switch
& ThinWire port
' ThinWire fuse OK indicator
( Auxiliary serial port
) Console terminal ground lug
+> Console terminal port
+? Futurebus+ option OK (green) indicator
+@ Futurebus+ option fault (amber) indicator

1–8 Introduction

Note: Fast SCSI I/O board option has only one Ethernet port.

Components and Controls

Figure 1–6 System Modules and Options

I/O
3

4
5

CPU

6
1

MEM
0

5
6

7
8

9
10

11
12
NUO-420-06-DG

Introduction 1–9

Components and Controls

Power
Subsystem

Figure 1–7 shows the lights, switches, and connectors on the
power supply in the top of the system.

! AC power port
" AC present light
# UPS signal control port
$ Fault ID display light
% Disk power failure light
& Fan failure light
' Over-temperature shutdown light
( PSC OK light
) PSC failure light
+> Secondary power out (SO)
+? Secondary power in (SI)
+@ Main power out (MO)
+A DC5 OK light
+B DC5 failure light
+C DC3 OK light
+D DC3 fault lights
+E FEU OK light
+F FEU failure light
+G AC circuit breaker

1–10 Introduction

Components and Controls

Figure 1–7 Power Subsystem
1
2
3
4
5
6
7
8
9
SO

11
MO

12
13
14
15
16
17
18
19

DC3

DC5

PSC

FEU
NUO-420-07-DG

Introduction 1–11

Components and Controls

Rear
Compartment
Components

Figure 1–8 shows the major components at the rear of the
system.
Figure 1–8 Rear Components

2
3
NUO-420-08-DG

! Fans
" SCSI only port
# SCSI/DSSI ports (DSSI use requires adapter1)

1–12 Introduction

DSSI option does not apply with Fast SCSI option.

Components and Controls

Components:
Bottom Tray

Figure 1–9 shows the major components in the bottom tray of
the system.

! Removable-media mass storage device
" Removable-media mass storage device
# Fixed-media mass storage device
$ Fixed-media mass storage device
% Local disk converter (LDC) power board
& Bottom tray latch

See Opening the Bottom Tray for detailed instructions on
opening the bottom tray.

Introduction 1–13

Components and Controls

Figure 1–9 Bottom Tray Components

1
5
4
3

NUO-420-09-DG

1–14 Introduction

2
Installation
Introduction
In This Chapter

Before
Installing Your
System

This chapter explains how to install your Rackmount DEC 4000
AXP Server system. The information includes the following:
•

Verifying the Site Preparation

•

Tools Required

•

Unpacking the Shipment

•

Installing the System

•

Preparing the System for Operation
Caution
Review your system warranty. It may require that
a Digital service representative install your system
to prevent damage to equipment or software.

Warning
The system weighs 65.7 kg (146 lbs). To prevent
personal injury and equipment damage, install
the system chassis in an enclosure that can be
stabilized when the system is pulled out on its
slides.

Installation 2–1

Verifying the Site Preparation

Verifying the Site Preparation
Site
Preparation

The installation instructions that follow assume:
•

Your site meets all the requirements listed in the system Site
Preparation manual (not supplied with the system).

•

All cables that you plan to connect to your system are in
place and clearly labeled:
Terminal data cables
Telephone cables
Network cables

•

Required
Clearance

The specifications and conditions listed in Appendix A have
been met.
Caution
Airflow through the system is from front to
back. The front and rear of the unit must not be
obstructed. If the internal temperature limits are
exceeded, the reliability of the system could be
affected.

Locate the system in an area that provides sufficient clearance
for ventilation and servicing. Figure 2–1 shows the clearance
required around the system.

2–2 Installation

Verifying the Site Preparation

Figure 2–1 System Clearance Requirements

48.3 cm
(19 in)

61 cm
(24 in)

1
61 cm
(24 in)

61 cm
(24 in)

2
71.1 cm
(28 in)

44.5 cm
(17.5 in)

61 cm
(24 in)

NUO-420-10-DG

! Front of unit
" Top of unit
Installation 2–3

Tools Required

Tools Required
You will need the following tools to install the equipment:

2–4 Installation

•

Scissors

•

Flat blade screwdriver

•

Phillips screwdriver

•

Adjustable wrench

•

Set of nut drivers

•

Allen wrench

Unpacking the Shipment

Unpacking the Shipment
Checking the
Shipment

Note
Save all packing materials in case you need to
return the system for service or reship the system.

Check the packing list to ensure that all items listed have
been received. If any item is missing or damaged, contact your
delivery agent immediately, and contact your Digital sales
representative.
Figure 2–2 shows the contents of the system shipping carton.
Your shipment may include several cartons. One carton contains
the system, hardware documentation, software documentation,
system software, diagnostic software, and software licenses.
Depending on your order, your shipment may also include some
of the following devices:
•

Terminals

•

Printers

•

Modems

•

Options

Installation 2–5

Unpacking the Shipment

Unpacking the
System

Figure 2–2 shows how to unpack the system and the shipping
contents.

! Accessories
" OCP door key and loose hardware
# Information envelope
$ Factory Installed Software Installation Cards
% Console terminal cable
& Power cord
' Documentation
( Slide assemblies (one pair)
) Interlock actuator bracket
+> Cable management system

2–6 Installation

Unpacking the Shipment

Figure 2–2 Shipping Contents

9
3

10
4

NUO-420-11-DG

Installation 2–7

Unpacking the Shipment

Accessories

Table 2–1 lists the mounting hardware included with the
system.
Table 2–1 Accessory Kit Contents (P/N 70-30535-01/02)
Description

Part Number

Quantity

Key, 1/4 turn

90-11194-01

Bracket, slide mounting, left

74-46127-01

Bracket, slide mounting,
right

74-46127-02

Bracket, cable management,
left

74-46815-01

Bracket, cable management,
right

74-46815-02

U-nut, 10/32

90-07786-00

Tubing, cable management

74-46816-01

Washer, flat

90-10010-00

Cotter pin, 1 1/4-inch long

90-11366-01

Bracket, interlock actuator

74-46795-01

Screw, sems, M4 Pan head,
10 mm (.39 inch) long

90-40146-04

Accuride Slides 771-245-1/R,
Rev. C

12-40248-01

1 set

Screw, flat head, 100D

90-00039-25

Screw, 10-32 x .375-inch, Pan
head

90-09228-10

Screw, 10-32, Hex head,
slotted

90-00061-46

Bar nut, 10-32 x 2.5-inch long

12-14406-00

SCSI terminator

12-30552-01

SCSI to DSSI adapter

12-39838-01

Power cord

17-00083-32 or 17-00083-48

(continued on next page)

2–8 Installation

Unpacking the Shipment

Table 2–1 (Cont.) Accessory Kit Contents (P/N 70-30535-01/02)
Description

Part Number

Quantity

Screw 6-32 x .25-inch, TRS

90-00063-10

Cable clamp

90-07084-00

Screw, sems, M3 Pan head

90-09984-20

Installation Manual

EK-BA641-IN

Node name label

36-38609-01

Tee, coax, BNC

12-25869-01

Connector, coax, BNC, 50
ohms

12-26318-01

Cable assembly

17-01364-02

Installation 2–9

Installing the System

Installing the System
Equipment
Slides

Remove the following material from the slide carton labeled
C-711:
•

One pair of slides:
One right-hand slide
One left-hand slide

Remove the following material from the accessories carton:
•

Two mounting brackets:
One left rear bracket (P/N 74-46127-01) stamped LEFT
One right rear bracket (P/N 74-46127-02) stamped
RIGHT

•

Preparing the
Slides

Package containing the mounting hardware (see Table 2–1
for listing)

Refer to Figure 2–3 and prepare the slides as follows:

1. Locate the left slide
in the kit. (The left slide has the slide
lock on the left when the smooth side of the slide is facing
away from you. See Figure 2–3.)

2. Remove the inner slide race
from the left slide
by
pushing down on the slide lock , and then pulling out the
inner slide race from the left slide.

3. Attach the LEFT rear bracket
to the left slide
using
and nut bar , but do not tighten
10-32 Pan head screws
at this time.

4. Locate the right slide
in the kit. (The right slide has the
slide lock on the left when the smooth side of the slide is
facing you. See Figure 2–3.)

(

5. Remove the inner slide race
from the right slide
by
pushing down on the slide lock , and then pulling out the
inner slide race from the right slide.

)

6. Attach the RIGHT rear bracket
to the right slide
using
10-32 Pan head screws
and nut bar , but do not tighten
at this time.

2–10 Installation

Installing the System

Slide
Assemblies

Figure 2–3 shows the slide assemblies and how the left and right
slide extenders are installed.
5

Figure 2–3 Slide Assemblies

1
3
2

10
11

NUO-420-12-DG

! Left slide
" Left inner slide race
# Left slide lock
$ Left rear bracket
% Nut bar
& 10-32 Pan head screws

' Right slide
( Right inner slide race
) Right slide lock
+> Right bracket
+? Nut bar
+@ 10-32 Pan head screws

Installation 2–11

Installing the System

Attaching
Slide Races to
Chassis

To attach the slide races to the chassis, refer to Figure 2–4 and
proceed as follows:

1. Attach the right slide race
to the right side of the system
chassis
using four flat head screws .

2. Attach the left slide race to the left side of the system chassis
using four flat head screws.

2–12 Installation

Installing the System

Figure 2–4 Attaching Slide Races

SCALE .0900

2
D.DG
NUO-420-13-DG

Installation 2–13

Installing the System

Locating the
Rail Mounting
Holes

Before attaching the slides to the rack, you must first identify
the system location in the rack and establish a datum line. The
datum line serves as a reference to identify the mounting hole
positions for the slide bracket, U-nuts and cable management
bracket. To establish a datum line:
1. Determine the area of the rack where the system will be
installed (44.5 cm [17.5 in] or 30 contiguous holes).

at the base of
2. Refer to Figure 2–5. Establish a datum line
the area between two holes with 1.3 cm (.5 in) spacing. The
first hole above the datum line is identified as hole 1 . This
establishes the location of the bottom edge of the system.

The U-nuts are mounted using the 6th hole # and the 22nd hole
& on the front rails. The slides are installed using the 11th hole
$ through the 14th hole % from the datum line. The mounting
holes for the cable management brackets are the 22nd hole &
and the 25th hole ' on the rear rails. The cable management
bracket is installed later in this chapter.
Note
Because of the bottom hinged tray, the bottom edge
of the system must be mounted at least (44.5 cm (17
1/2 in) or 30 contiguous holes) from the bottom of
the cabinet to the datum line mentioned above.

Installing
System U-Nuts

Four U-nuts must be installed on the rails to receive the screws
that secure the system to the rails. To install the U-nuts:
1. Refer to Figure 2–5.
2. Install four U-nuts on the front left and right rails. The
U-nuts should be installed at the 6th hole
and the 22nd
hole .

2–14 Installation

Installing the System

Figure 2–5 Establishing Mounting Location

17 1/2"

15 3/4"
Hole 25

Hole 22

14 "

12 1/4"

10 1/2"

"Installation Area"
Hole 14

8 3/4"

Hole 11

7 "

5 1/4"
Hole 6

3
3 1/2"

Hole 1

1 3/4"

Scale = 17/64

NUO-420-14-DG

Installation 2–15

Installing the System

Attaching the
Slides to Rails

The slides are installed using the 11th hole
through the 14th
hole
from the datum line. To install the slides to the rails,
refer to Figure 2–6 and proceed as follows:

1. Adjust the left rear bracket so that it is flush with the
outside left rail.
2. Tighten the screws securing the bracket to the slide at this
time.
3. Repeat steps 1 and 2 for the right rear bracket.

to the left front rail
using four
4. Attach the left slide
screws
and nut bar . Do not tighten the screws at this
time.

'
(

5. Attach the left slide
to the left rear rail
screws
and nut bar .

& using four

6. Tighten screws on the front and rear rails.
Note
Pull the slide upward when securing it to the rails.
Also, ensure that the slide is level and that the
slides are at the same height within the cabinet.

7. Repeat steps 1 through 3 to attach the right slide to right
rails.

2–16 Installation

Installing the System

Figure 2–6 Attaching the Slides to the Cabinet Rails

4
3

8
6

CE.DG
NUO-420-15-DG

Installation 2–17

Installing the System

Mounting the
Chassis on
Equipment
Slides

To mount the chassis on the slides, refer to Figure 2–7 and
proceed as follows:
Warning
Use sufficient personnel and proper equipment
when lifting or moving the Rackmount DEC 4000
computer system. The fully loaded system weighs
65.7 kg (146 lb).
Do not lift or carry the system using the system
handle. Only use the system handle to pull the
system out of the rack on its slides.
Ensure that the enclosure is stabilized when the
system is extended on its slides. Figure 2–7 shows
an example of a cabinet with the stabilizer foot
extended.

1. Pull both equipment slides
positions.

" out fully to their locked

2. Lift the chassis
and position it so that you can insert the
slide races into the front end of the slides.
3. Push the system into the slides until it stops. Then push
down on the two slide locks, and then push the system into
the cabinet.
4. Tighten the screws that fasten the system to the rails.

2–18 Installation

Installing the System

Figure 2–7 Installing the System on the Slides

AE.DG
NUO-420-16-DG

Installation 2–19

Installing the System

Installing
the Interlock
Actuator
Bracket

The interlock actuator bracket prevents cabinet instability
by allowing only one system at a time to be pulled out of the
cabinet. Install the interlock actuator bracket if the system
cabinet has an interlock system.
Figure 2–8 shows how to mount the interlock actuator bracket.
at the rear of the system
Mount the interlock actuator bracket
using two M4 10 mm screws .

2–20 Installation

Installing the System

Figure 2–8 Installing the Interlock Actuator Bracket

Scale = 1/8

NUO-420-29-DG

Installation 2–21

Installing the System

Installing
the Cable
Management
System

To install the cable management system, refer to Figure 2–9, and
proceed as follows:
1. Slide the system into the rack.

mounting holes that are just
2. Locate the second rear rail
below the top rear edge of the system chassis.

3. Align the top hole of the cable management bracket
with
mounting hole identified in step 2. Then
the rear rail
install the cable management bracket using two hex head
10-32 screws
and two U-nuts. .

#
"

(

4. Align the top hole of the cable management bracket
with
the rear rail mounting hole identified in step 2. Then install
the cable management bracket using two hex head 10-32
screws and two U-nuts.

5. Insert one end of the 1-inch tubing
into the cable
and slide the other end into the
management bracket
cable management bracket .

(

,
6. To prevent the tube from sliding out of the brackets
slide a flat washer
on to each end of the tube just past the
cotter pin hole. Then install a cotter pin
into each hole.

2–22 Installation

Installing the System

Figure 2–9 Installing the Cable Management System

4
3

6
1

2
8

NUO-420-17-DG

! Cable management bracket
(74-46815-01)
" Hex head 10-32 screws
(90-00061-46)
# Rear rail
$ U-nut (90-07786-00)

% 1-inch tubing
(74-46816-01)
& Flat washer
(90-10010-00)
' Cotter pin
(90-11366-01)
( Cable management
bracket (74-46815-02)

Installation 2–23

Preparing the System for Operation

Preparing the System for Operation
Checking the
Switch Settings

2–24 Installation

Figure 2–10 shows the location of the switches on the front of
the system
and on the top of the system . Ensure that the
Halt switch
is set to the in position. Also be sure that the ac
circuit breaker
is set to OFF (O).

!
#

Preparing the System for Operation

0 1

Figure 2–10 Switch Locations

Halt

F4
1
F3
F2
0
F1

2
NUO-420-18-DG

Installation 2–25

Preparing the System for Operation

Connecting
the Console
Terminal and
Modem

Refer to the documentation that is shipped with the terminal
for information on how to connect the keyboard and set up the
console. Make sure that the console baud rate is set to 9600.
Note
Use the cord shipped with the system, not the one
shipped with the console terminal.
If you need to change the system baud rate, refer
to Chapter 9.

If you have a modem, connect it now. Figure 2–11 shows the
console terminal and modem connections.

! Connection of console
terminal
" Connection of optional
modem.
# Optional modem

2–26 Installation

$ Console terminal
% Top of system

Preparing the System for Operation

Figure 2–11 Modem and Console Connections
4

5
NUO-420-19-DG

Installation 2–27

Preparing the System for Operation

Connecting the
Power Cords

Warning
To avoid risk of injury, do not remove modules,
storage devices, or power supply. No userserviceable parts are inside. Refer servicing
questions to a Digital service representative or
qualified self-maintenance personnel.
This equipment is not designed for connection to
an IT power system (a power system without a
directly grounded neutral conductor).
Plug this equipment into a properly grounded
power receptacle.
The green fastener is a Safety Earth Bonding
Point. Do not attempt to loosen.
Voltage selection is not required.

The power connections are shown in Figure 2–12.

! System, top view
" AC power port connection
# AC power cord
$ Active wall outlet (20 A)

2–28 Installation

% Modem
& Modem power cord
' Console terminal
( Console terminal power

cord

Preparing the System for Operation

Figure 2–12 Power Connections
7
5
4

8
3

1
NUO-420-20-DG

Installation 2–29

Preparing the System for Operation

Expanding the
System

The Rackmount DEC 4000 system can be expanded from any of
the five ports on the rear of the system. These ports are labeled
A-E. Ports A-D are the four top ports (left to right) as shown in
Figure 2–13; these are SCSI/DSSI ports. Port E is the bottom
port, and is SCSI only. Depending on your order, your system
may differ from the example shown in Figure 2–13.
Figure 2–13 shows:
•

SCSI terminator

•

SCSI cable

! connection to port A

" connection to port E
• DSSI adapter $ on port D
• DSSI cable connecton # to port D

2–30 Installation

Preparing the System for Operation

Figure 2–13 SCSI and DSSI Connections

Scale = 1/8

2
4
NUO-420-21-DG

Installation 2–31

Preparing the System for Operation

Turning On the
System

Turn the system on in the following order:
1. Uninterruptable power supply UPS (optional)
2. Console terminal
3. Peripherals, expanders, and modems
4. AC circuit breaker (top of system)
After about a minute, you will see two displays similar to those
shown in Figure 2–14 and Figure 2–15.

2–32 Installation

Preparing the System for Operation

Figure 2–14 Displays

08:52:07 Wednesday, July 29, 1992
Digital Equipment Corporation
DEC 4000
Executing Power-Up Diagnostics
CPU
01

Memory
0123

Storage
ABCDE

Net
01

Futurebus+
123 456

P-

---P

- - - - -

* *

- - - - - -

*Test in progress

P Pass

F Fail

- Not Present

NUO-420-22-DW

Installation 2–33

Preparing the System for Operation

Figure 2–15 Displays

Console V2.3-2001
CPU 0
CPU 1
Memory 0
Memory 1
Memory 2
Memory 3
Ethernet 0
Ethernet 1

A SCSI
B SCSI
C SCSI
D
E SCSI
Futurebus+

VMS PALcode X5.12B, OSF PALcode X1.09A

P B2001-AA DECchip (tm) 21064-2
P B2002-BA 32 MB
P Address 08-00-2B-2A-D4-43
P Address 08-00-2B-2A-EC-7D

P
P
P
P
P
P

System Status Pass

ID 0

ID 1

ID 2

ID 3

RZ26
RZ26
RZ26

RZ26
RZ26

RZ26
RZ26
RZ26

TLZ06 RRD42 RZ26
-

RZ26
-

ID 4

ID 5

ID 6

ID 7
Host
Host
Host

TZ85
-

RZ73
-

Host

Type "b" to boot dka0.0.0.1.0

DEC 4000 console V2.3-2001, built on July 29, 1992 at 10:02:19
>>>
NUO-420-23-DW

2–34 Installation

Preparing the System for Operation

Installing the
Software

If your system includes an internal disk drive pre-loaded with
operating system software, then:
If you ordered . . .

Refer to . . .

OpenVMS Alpha AXP

Open VMS Factory Installed
Software User Information,
provided with your system.

DEC OSF/1 Alpha AXP

Guide to Starting the Factory
Installed Software System,
provided with your system.

If you need more detail, or you plan to install from compact disc,
use the OpenVMS or DEC OSF/1 installation guide that comes
with your operating system software.
For more information on your hardware or console diagnostics:
When you need . . .

Refer to . . .

Console user information
System configuration
SCSI drive removal and
replacement
System troubleshooting

This guide

Power-up diagnostics
Running diagnostics
Symptom-directed diagnostics
System repair and
replacement
System configuration

DEC 4000 AXP Model 600 Series
Service Guide

Information on additional
options available

DEC 4000 Options Guide

CPU operation
Memory operation
I/O operation
System operation

DEC 4000 Model 600 Series
Technical Manual

Installation 2–35

Preparing the System for Operation

Connecting to
the Network

There are three networking options: ThinWire, standard
Ethernet (thickwire), and 10BASE-T Ethernet. Depending on the
type of network you have, follow the instructions in Figure 2–16,
Figure 2–17, or Figure 2–18 to make the connection.

! Remove the T-connector and terminator (save the
terminator).

" Make sure that the Ethernet select switch is positioned
toward the ThinWire connector.

# Connect ThinWire cable and reconnect T-connector.
$ System, top view

2–36 Installation

Preparing the System for Operation

Figure 2–16 Option 1: ThinWire Ethernet Connection

F2
1

0
F1
2

F2
3
4

0
F1
NUO-420-24-DG

Installation 2–37

Preparing the System for Operation

Figure 2–17 Option 2: Standard Ethernet, Thickwire
Connection

F2
2

F1
4

NUO-420-25-DG

! Slide Ethernet select switch
toward 15-pin D-sub connector.
" Connect transceiver cable.

2–38 Installation

# Slide latch toward the Select
switch.
$ System, top view

Preparing the System for Operation

Figure 2–18 Option 3: 10BASE-T (Twisted-Pair) Connection

350

F2
0

F1
5
NUO-420-26-DG

! Slide Ethernet select switch
toward 15-pin D-sub connector.
" Insert transceiver cable.
# Slide latch toward the Select

$ Connect 10BASE-T (twistedpair) cable.
% System, top view

switch.

Installation 2–39

3
System Operation
Chapter Description
In This Chapter

This chapter covers the following information:
•

Modes of Operation

•

Starting the System

•

Using the Operator Control Panel

•

Help

System Operation 3–1

Modes of Operation

Modes of Operation
Two Modes of
Operation

Console Mode

The system can run in one of two environments:
•

Console mode

•

Operating system mode

In console mode, the system and the console terminal operate
under the control of the console subsystem. All user input is
passed to the console subsystem.
The system runs in console mode under two circumstances:
•

The system is powered up and operating system software has
not been booted.

•

Operating system software has been shut down or has
crashed.

Chapter 4 describes how to use the system in console mode.

Operating
System Mode

In operating system mode, the system and console terminal are
under control of the operating system. All user input is passed
to the operating system.
The system runs in operating system mode if the system
is powered up and operating system software is running
uninterrupted.
Once you complete the steps described in Starting the System
your system will be running in operating system mode. Refer
to your operating system documentation for information about
using the system in operating system mode.

3–2 System Operation

Starting the System

Starting the System
Before You
Start the
System

You start a system by bringing it from a powered-down state
to the point at which the operating system login banner is
displayed on the console terminal.
Before starting the system, you should be familiar with system
components, lights, and controls. Use the diagrams on previous
pages to familiarize yourself with these features.

When to Start
the System

Your system may already be started. If the operating system
login banner or prompt is displayed on your console terminal, the
system is already started. Skip this section and proceed to the
next section in this chapter, Using the Operator Control Panel .
If the console prompt (>>>) is displayed on your console terminal,
the system is in console mode. To finish starting the system,
set environment variables (described in Chapter 6) and boot
operating system software (described in Boot Operating System
Software, in this chapter).

Overview of the
Task

Start the system by performing the following steps:
1. Power up external devices
2. Power up the system
3. Set environment variables
4. Boot operating system software
Once the system is booted, you can begin normal operation.

System Operation 3–3

Starting the System

Power Up
External
Devices

Begin starting your system by powering up external devices,
which may include the following:
•

Uninterruptable power supply (UPS) (optional)

•

Console terminal

•

Local printer (optional)

•

Standalone external devices (optional)

Refer to the device’s installation instructions for information
about powering up that device.

Power Up the
System

Power up your system as follows:
Step

3–4 System Operation

Action

Find the ac circuit breaker at the top of the system.
Press the switch to the ON ( | ) position.
The ac power light comes on.
Each light on the control panel comes on briefly and
then goes off.

Check the display on the console terminal screen:
•

If the startup screens (Figure 3–1 and
Figure 3–2) are displayed, either set environment
variables or boot the operating system.

•

If the booting system software screen
(Example 3–1 or Example 3–2) is displayed,
your system has begun booting operating system
software. After several minutes, the operating
system login banner is displayed. Log in to the
system at the login prompt. You are ready to
begin normal operation once the operating system
prompt is displayed.

Starting the System

If You Have a
Problem

If any of the steps in the preceding procedure do not work as
stated, go to Chapter 11 for troubleshooting information.
Figure 3–1 shows an example of a system startup screen
during self-tests. The screen shows the status and result of the
self-tests.

Figure 3–1 System Power-Up Self-Test Screen

17:33:56 Tuesday, January 26, 1993
Digital Equipment Corporation
DEC 4000 AXP (tm)

\ Executing Power-Up Diagnostics

CPU Memory Storage Net Futurebus+
0 1 0 1 2 3 ABCDE 0 1 1 2 3 4 5 6

* Test in progress

P PPPPP PP

P Pass

F Fail

- Not Present
MLO-009902

When the power-up self-tests are completed, a second screen
similar to the one shown in Figure 3–2 is displayed. This screen
provides configuration information for the system.

System Operation 3–5

Starting the System

Figure 3–2 Sample Power-Up Configuration Screen

CPU 0
CPU 1
Memory 0
Memory 1
Memory 2
Memory 3
Ethernet 0
Ethernet 1

P
P
P
P

DECchip 21064 PALcode Xn.nn, Firmware Tn.n-nnnn

B2002-DA 128 MB
Address 08-00-2B-2A-D6-97
Address 08-00-2B-2A-D6-A6
ID 0

A
SCSI
B
DSSI
C
DSSI
D
DSSI
E
SCSI
Futurebus+

P
P
P
P
P
P

System Status Pass

ID 1

ID 2

ID 3

ID 4

ID 5

ID 6

RZ73
RF73
Host
Host
TZ85
-

TLZ06
-

ID 7
Host
Host
Host
Host
Host

Type b to boot

>>>
MLO-009903

Set
Environment
Variables

Before you boot operating system software, you may want to
set or change the setting of some environment variables. By
customizing the setting of the system’s environment variables,
you can control how the system powers up and boots operating
system software in the future.
For example, you can do the following:
•

Set the default system startup action to boot. If the startup
action is set to boot, the system will automatically boot
operating system software when you power up or reset the
system.

•

Set or change the default boot device.

In most cases, some environment variables on your system were
preset when your system shipped from the factory.

3–6 System Operation

Starting the System

For information about setting environment variables and the
values to which environment variables have been preset, refer to
What Variables Can I Set? in Chapter 6.

Boot Operating
System
Software

Boot operating system software as follows:
Step

Action

Enter boot or b at the console prompt.
>>> b
A booting system software screen (Example 3–1 or
Example 3–2) is displayed on your console terminal.
After several minutes, the operating system login
banner is displayed on your console terminal.

Log in to the system at the login prompt. You are
ready to begin normal operation once the operating
system prompt is displayed.

Boot and b are abbreviations of the boot command. When you
enter either of these abbreviations, the value of an environment
variable (shown in parenthesis) provides the following additional
information during booting:
•

Boot device (bootdef_dev)

•

Boot flags (boot_osflags)

For information about setting or displaying the current value for
either of these environment variables, refer to Chapter 6.
For complete information about the boot command, refer to boot
in Chapter 5.

System Operation 3–7

Starting the System

Example 3–1 shows a system booting OpenVMS AXP software.
Example 3–1 Booting OpenVMS AXP System Software Screen
OpenVMS AXP Version 1.0 Major version id = 1 Minor version id = 1
%SYSINIT-I-start
%SYSINIT-I-finish
OpenVMS AXP V1.0 Installation Procedure
Model: DEC 4000 Model 610
System device: RZ57 - _DKIO:
Free Blocks: 1804734
System type: 01
* Please enter the date and time (DD-MMM-YYYY HH:MM)22-OCT-1992 15:21
STDRV-I-STARTUP, VMS startup begun at 22-OCT-1992 15:21:00.13
%SET-I-NEWAUDSERV, identification of new audit server process is 00000027
%%%%%%%%%%% OPCOM 22-OCT-1992 15:21:21.83 %%%%%%%%%%%
Example 3–2 shows a system booting DEC OSF/1 AXP software.
Example 3–2 Booting DEC OSF/1 AXP System Software Screen
(boot dka0.0.0.0.0 -flags 0)
block 0 of dka0.0.0.0.0 is a valid boot block
reading 16 blocks from dka0.0.0.0.0
bootstrap code read in
base = 1f2000, image_start = 0, image_bytes = 2000
initializing HWRPB at 2000
initializing page table at 1e4000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
Alphaboot - Wed May 13 16:29:59 EDT 1992
OSF boot - Sat May 9 08:43:49 EDT 1992
Loading vmunix ...

3–8 System Operation

Using the Operator Control Panel

Using the Operator Control Panel
Before You Use
the Control
Panel

Once the operating system is running, pressing a control panel
button or switch interrupts operation. Before you press a control
panel button or switch, you may need to shut down the system.
You shut down the system by performing the operating system
software shutdown procedure. Refer to your operating system
documentation.

Overview

You can use the switches and buttons on the DEC 4000 AXP
Rackmount control panel to do the following:
•

Invoke console mode from operating system mode

•

Reset a hung system

•

Monitor self-test results

System Operation 3–9

Using the Operator Control Panel

Use Figure 3–3 to locate the controls that are identified in the
procedures on the following pages.
Figure 3–3 Operator Control Panel

Halt
6-1

MEM

0 1

Reset

CPU

I/O

2
NUO-420-04-DG

! DC power light
" Self-test status
lights

3–10 System Operation

# Halt button
$ Reset button

Using the Operator Control Panel

Invoke Console
Mode

You may want to invoke console mode in order to set
environment variables or to enter other console commands.
You use the Halt button (Figure 3–3) to invoke console mode
from operating system mode on your console terminal. The
system then halts.
For information about invoking console mode from a remote
device or from a powered-down state, refer to Running the
Console Program: Invoking Console Mode in Chapter 4.
Invoke console mode as follows:
Step

Action

Press the Halt button on the front of the system to
the in position or do one of the following:
•

If the tta0_halts environment variable is set
to 4 or 6, enter Break on the console terminal
keyboard.

•

If the tta0_halts environment variable is set
to 2 or 6, press Ctrl/P on the console terminal
keyboard.

The console mode prompt is displayed on the console
terminal:
>>>
2

The system is now in console mode. You can begin
entering console commands.

If you invoked console mode by pressing the Halt
button to the in position, press the Halt button to the
out position.

To return to operating system mode, enter the
continue command at the console prompt.
If the system does not respond to the continue
command, reboot by entering the boot command at
the console prompt.

For general information about console mode, refer to Chapter 4.
For information about setting environment variables, refer to
Chapter 6.

System Operation 3–11

Using the Operator Control Panel

Reset the
System

Pressing the Reset button (shown in Figure 3–3) resets the
system. The system aborts all current processes, initializes, and
performs startup self-tests.
When the system is in console mode or in operating system
mode, you use the Reset button, as a last resort, to reset the
system if it hangs. (First, try pressing Ctrl/C or Ctrl/Y or
entering other operating system commands before pressing the
Reset button.)
Caution
Pressing the Reset button halts all system
processes. Do not perform this procedure from
operating system mode unless your system is
hung and you have exhausted all other ways of
terminating the process.

When you press the Reset button, the system will reset itself and
perform system self-tests.
Reset a system as follows:
Step

3–12 System Operation

Action

Press the Reset button on the control panel
(Figure 3–3.)
If the auto_action environment variable is set to boot
and the bootdef_dev environment variable specifies
the boot device, your system will perform a self-test
and autoboot. Once you log in to the system, you
can resume normal operation. It is not necessary to
perform the next step.
If not, proceed to the next step.

Return to operating system mode by entering the
boot command at the console terminal prompt (>>>).

Using the Operator Control Panel

Power Down
the System

You use the ac circuit breaker to power down the system.
Note
You rarely need to power down the system.
You may be able to accomplish your task by
pressing the Reset button (See Reset the System,
earlier in this chapter.) For maximum reliability,
Digital recommends that you run your system
continuously.

Power down the system as follows:
Step

Monitor
Self-Test
Results

Action

Shut down the system using the shutdown
procedure described in your system software
manual.

Extend the system on the rails and press the ac
circuit breaker at the rear of the system to the
OFF position (0). See Chapter 12 for instructions
on extending the system.

Power down external devices if you have them.
Refer to the device installation guide.

You can use the self-test status lights (shown in Figure 3–3) to
check the results of the system self-test.
The system performs its self-test when you reset the system
(press the Reset button) and when you power up the system.
During the self-test, the system tests each module in the card
cage. As a module is tested, the light representing that module
on the operator control panel comes on. The light goes off when
the test completes successfully.
If one or more of the self-test status lights remains on after the
self-tests, refer to Chapter 11.

System Operation 3–13

Help

Help
Getting Help

Get help from the following sources:
•

In console mode, access help by entering help or man at the
console terminal prompt (>>>).

•

In operating system mode:
If you are running OpenVMS AXP, enter HELP at the
DCL prompt $.
If you are running DEC OSF/1 AXP, enter man and the
command for which you wish to receive information.

3–14 System Operation

•

For information about other documentation that is available
for your system, refer to the preface of this manual. It lists
related documents and their order numbers.

•

Contact Digital Services at the locations listed in the
following table. If your Digital Services number is not listed,
contact your local Digital office for assistance.
Country

Telephone Number

United States

1-800-354-9000

Canada

1-800-267-5251

Canada (Quebec)

1-800-267-2603

United Kingdom

[44]256 59200

France

[33]92955111

Germany

[49]-(89)-95913218

References

References
The following table describes where to find additional
introductory information.
Task

Document

Prepare the system site

DEC 4000 Model 600 Series Site
Preparation Checklist

Install the system

This guide

Install operating system
software

Operating system software
installation guide

Power up and power down
external devices

Installation guide for the device

Shut down operating system
software

Troubleshooting

•

In OpenVMS AXP, refer to
OpenVMS Alpha Version 1.0
Upgrade and Installation
Manual.

•

In DEC OSF/1 AXP, refer to
DEC OSF/1 AXP Guide to
System Administration.

Chapter 11 of this manual and
DEC 4000 AXP Model 600 Series
Service Guide.

System Operation 3–15

4
Console Subsystem
Chapter Description
What Is the
Console
Subsystem?

This chapter focuses on the console subsystem. The console
subsystem provides the DEC 4000 AXP Rackmount user
interface when operating system software is not running or is
halted.
For example, you use the console subsystem:

In This Chapter

•

To boot operating system software.

•

To set or display environment variables.

•

To upgrade the firmware.

•

To test your system.

•

To modify DSSI or Fast SCSI parameters.

This chapter covers the following information:
•

Components of the Console Subsystem

•

Running the Console Program: Invoking Console Mode

•

Console Mode User Interface

Console Subsystem 4–1

Components of the Console Subsystem

Components of the Console Subsystem
Console
Subsystem

Figure 4–1 and the following list identifies the components of the
console subsystem.
•

Console program — is the software that executes when
operating system software is not executing; it provides the
user interface, interprets and executes user commands.
When the console program is executing, the system is
running in console mode.

4–2 Console Subsystem

! — is the module in the card cage at the top of

•

I/O module
the system.

•

Console terminal port
— connects the console terminal to
the system; it is located on the I/O module.

•

— is used exclusively for entering
Console terminal
console commands when the console program is executing. It
connects to the console terminal port on the I/O module.

•

Auxiliary serial port
— connects the remote access device,
which can function as a remote console device to the system.
It is located on the I/O module.

•

Remote access device ,
— is the external hardware,
possibly at a remote site, that can act as a console terminal.

•

Ethernet port
— connects the console subsystem to an
Ethernet network. Devices on this network can function as
remote access devices. Depending on the type of system you
ordered, one or two Ethernet ports are located on the I/O
module.

Components of the Console Subsystem

Figure 4–1 Console Subsystem

F4
1
F3

Test
Loop

TM
lat igid

Data
Talk
SI TR CD RD SD

SCHOLAR
Plus

Off
On

NUO-420-27-DG

Console Subsystem 4–3

Running the Console Program: Invoking Console Mode

Running the Console Program: Invoking Console Mode
Overview

From the
Console
Terminal

You can invoke console mode on the system through the following
devices:
•

Console terminal

•

Remote access device: either a device connected to the
auxiliary serial port on your system’s I/O module or a device
that is on the same Ethernet segment as the system.

The system’s console terminal is the terminal that is plugged in
to the system’s console terminal port on the I/O module at the
rear of the system.
From a powered-down state, invoke console mode from the
console terminal as follows:
Step

Action

Press the Halt button on the control panel to the in
position.

Power up the system (described in Chapter 3). After
the system performs a self-test, the console prompt
(>>>) displays on the console terminal.

Press the Halt button on the control panel to the out
position.

You can begin entering console commands.

To continue to operating system mode, refer to Boot
Operating System Software in Chapter 3.

For information about invoking console mode from operating
system mode, refer to Invoke Console Mode in Chapter 3.

4–4 Console Subsystem

Running the Console Program: Invoking Console Mode

From the
Auxiliary Serial
Port

One way to access your system from a remote site is through
a device at the remote site that is connected to your system’s
auxiliary serial port on the I/O module at the rear of the system.
When your system is running in operating system mode, you can
access console mode from this remote access device as follows:
1. Set host to your system from the remote access device.
2. Shut down the operating system or:
If the tta1_halts environment variable on your system is set
to 2, press Ctrl/P on the remote access device keyboard.
For information about setting the tta1_halts environment
variable, refer to Enabling Halt Key Functions (tta0_halts and
tta1_halts) in Chapter 6.

From Across
the Ethernet

Another way to access your system from a remote site is
through the Ethernet. You can connect to your DEC 4000 AXP
Rackmount system from any device that is on the same Ethernet
segment, or local area network (LAN).
Accessing your system from across the Ethernet differs
depending on whether your system is in console or operating
system mode.
In Operating System Mode
If your system is in operating system mode, access console mode
from this remote device as follows:
1. Set host to your system using the protocol appropriate to
your network device, possibly DECnet or MOP. Refer to your
operating system documentation for information about the
appropriate protocol for your system.
2. Shut down the operating system. Refer to your operating
system documentation for instructions.
As the operating system shuts down, you will lose the
connection to your system.
3. Under the OpenVMS AXP operating system, reconnect to
your system using the instructions that follow.

Console Subsystem 4–5

Running the Console Program: Invoking Console Mode

In Console Mode
Note
If your system crashed during operation, the
MOP drivers will not be running, and you will not
be able to access your system using the method
described in this section.

If your system is in console mode, access it as follows:
If you are running OpenVMS AXP software, set host to your
system using the ncp connect command and the MOP protocol.
For example:
$ MCR NCP
NCP> CONNECT VIA device-name physical address ethernet-address
For information about the ncp connect command, refer to the
DECnet for OpenVMS AXP Network Management Utilities
Manual.

Console Mode User Interface
Console
Prompt

The console mode prompt is:
>>>
You can enter supported keys, control characters, and console
commands at the console prompt.

Keyboard
Characters

4–6 Console Subsystem

Figure 4–2 shows the keyboard characters that are supported in
console mode. Some DEC 4000 AXP Rackmount systems come
with a VT420 terminal and keyboard. However, you can enter
the following keyboard characters in console mode, regardless of
your terminal type.

Console Mode User Interface

Callout

Key

Function

Deletes the last character you entered.
With a hardcopy terminal, <x is echoed with \
followed by the character being deleted. If you delete
several characters consecutively, the system echoes
with \, the deleted characters, followed by another \
at the end of the series.

"
#
$
%
&
'
(

Recalls up to 32 previous commands.

Ctrl

Begins a control character.

\ (Backslash)

Extends a command onto the next line. Must be the
last character on the line to be continued.

Return

Enters a command on the command line. The cursor
need not be at the end of the command line.
Moves the cursor left one position.

#
!

Reverses the order of recalled commands after using
.
Moves the cursor right one position.

Figure 4–2 Supported Keys on a VT420 Keyboard
Hold
Screen

Print
Set-Up
Screen

Break

F11
(ESC)

F10

F12
(BS)

F13
(LF)

F14

Hold Screen Lock

Compose

Help

Tab

Ctrl

Lock

>
<

Shift

R
D

G
V

*
8

^
6

J
N

(

)

I
K
M

,
,

_
-

:
;
.
.

+
=

}

]

}

~
‘

]

F18

F19

F20

PF4

Find

Insert
Here

Remove

PF1

PF2

PF3

Select

Prev
Screen

Next
Screen

\
Shift

Compose
Character

F17

"
’
?
/

Return

Wait

_
,
Enter

8
MLO-008207

Console Subsystem 4–7

Console Mode User Interface

Control
Characters

4–8 Console Subsystem

Enter control characters by holding down the key labeled Ctrl
while pressing another key. You can enter the following control
characters in console mode:
Character

Function

Ctrl/A

Toggles between insertion and overstrike mode so
you can edit text on the current command line.
Default mode is overstrike.

Ctrl/C

Interrupts a command process and returns control
to the console command line.

Ctrl/E

Moves the cursor to the end of the line.

Ctrl/H

Moves the cursor to the beginning of the line.

Ctrl/O

Suppresses output to console terminal until you
enter Ctrl/O again. Output is also re-enabled when
the console prompts for a command, issues an
error message, or enters operating system mode.

Ctrl/S

Suspends output to the console terminal until you
enter Ctrl/Q .

Ctrl/Q

Resumes output to the console terminal that you
suspended with Ctrl/S .

Ctrl/U

Deletes the entire line. Line deletion is followed
with a carriage return, line feed, and a new
prompt.

Ctrl/R

Redisplays the current line, omitting deleted
characters.

5
Console Commands
What Are the Console Commands?
In This Chapter

The previous chapter describes the console subsystem. This
chapter covers the console commands.

Levels of
Commands

There are two levels of console commands:

Basic
Commands

•

Basic

•

Comprehensive

Most of the time, you will use the basic console commands. All of
the basic console commands are described in alphabetical order
in this chapter. Table 5–1 lists the basic console commands.

Console Commands 5–1

What Are the Console Commands?

Table 5–1 Basic Console Commands
Command

Syntax

Description

boot

boot [-flags [longword,]longword] [-halt]
[boot_device]

Boots the operating system.

cdp

cdp [-{a,i,n,o,u}] [-sn] [-sa allclass] [-su
unitnum] [dssi_device]

Configures DSSI drive IDs.

continue

Resumes program execution.

date

date [yyyymmddhhmm.ss]

Displays or sets the current date
and time.

help

help [command . . . ]

In OpenVMS AXP, displays online
help using console commands.

init

Initializes the system.

man

man [command . . . ]

In DEC OSF/1 AXP, displays online
help using console commands.

set

set [-default] envar val

Sets an environment variable.

set host

set host [-dup] [-task task_name] device

Sets host to another MSCP DUP
server on a DSSI device.

show

show [envar] [{config,device,memory, pal,
version}]

Displays the value of an
environment variable or displays
configuration information.

test

Tests the system and displays
results.

Comprehensive
Commands

It should rarely be necessary for you to enter comprehensive
console commands. Using these commands requires detailed
knowledge of your system. Do not use these commands without
fully understanding the effect they can have on your DEC 4000
AXP Rackmount system.
To see a list of the comprehensive commands, enter help or man
at the console prompt.
For information about comprehensive console commands, refer to
the DEC 4000 Model 600 Series Technical Manual.

5–2 Console Commands

Entering Console Commands

Entering Console Commands
New Console
Commands

The DEC 4000 AXP Rackmount system features new console
commands. Most of the DEC 4000 AXP Rackmount console
commands are similar, but not identical to, the console
commands supported on VAX systems. (See Table 5–2.) If
you are familiar with VAX console commands, familiarize
yourself with the new commands before proceeding.
Table 5–2 Differences Between VAX and DEC 4000 AXP
Rackmount Console Commands

Console
Command
Format

VAX Console Command

DEC 4000 AXP Rackmount Console
Command

set boot

set bootdef_dev

show boot

show bootdef_dev

show bflags

show boot_osflags

/qualifier (indicates
optional qualifiers)

-flag (indicates optional flags)

Enter a console command in the following format. To specify a
flag, you must precede the flag with a space and a hyphen.
>>> command [-flags] [parameters..]
For information about entering a specific console command, refer
to the console command reference pages, in the next section of
this chapter.

Online Help

Once the system is running in console mode, get online
information about console commands by entering help or
man at the console terminal.
This book documents only basic console commands. Online help,
however, provides information for the complete list of console
commands.

Console Commands 5–3

Entering Console Commands

How to Display
Output One
Page at a Time

The help and show commands instruct the system to display
information. When information fills more than one screen, the
information scrolls until all information has been displayed.
To make the system output easier to read, you can use the
more command to display the output one screen at a time.
Enter | more after the command you are entering. For instance:
>>> help | more

Return

The system responds with the following display:
NAME
help or man
FUNCTION
Display information about console commands.
SYNOPSIS
help or man [<command>...]
Command synopsis conventions:
<item> Implies a placeholder for user specified item.
<item>... Implies an item or list of items.
[] Implies optional keyword or item.
{a,b,c} Implies any one of a, b, c.
{a|b|c} Implies any combination of a, b, c.
The following help topics are available:
alloc
bin
boot
cbcc
cdp
check
clear
cmp
continue
deposit
dynamic
echo
examine
exer
exer_read
fbus_diag
find_field
free
help or man
init
io_test
line
ls
memexer
net
netexer
nettest
--More--

build
chmod
crc
edit
exer_write
grep
kill
memexer_mp
ntlpex

cat
chown
date
eval
exit
hd
kill_diags
memtest
ps

From the more prompt, you can proceed either one line or one
screen at a time as follows:
•

To proceed one line at a time, press the Return key.

•

To proceed one page at a time, press the space bar on the
console terminal keyboard.

The remainder of this chapter describes the basic console
commands.

5–4 Console Commands

boot

boot
Synopsis

Bootstrap the system.
boot [-flags [longword,]longword] [-halt] [boot_device]

Description

Initializes the processor, loads a program image from the
specified boot device, and transfers control to that image.
If you specify a list of devices, a bootstrap is attempted from
each device in order. Then control passes to the first successfully
booted image. In a list, always enter network devices last, since
network bootstraps only terminate if a fatal error occurs or an
image is successfully loaded.
The -flags option can pass additional information to the operating
system about the boot that you are requesting.
You can abbreviate the boot command by entering boot or b.
When you enter either of these abbreviations, an environment
variable (shown in parenthesis) provides a default value for the
following information:
•

Boot device (bootdef_dev)

•

Boot flags (boot_osflags)

If you specify the boot device or boot flags on the command
line, the current default value is overridden for the current boot
request. However, the corresponding environment variable is not
changed.

Parameters

Parameter

Description

boot_device

A device path or list of devices from which
the console program attempts to boot, or
a saved boot specification in the form of
an environment variable. Use the set
bootdef_dev command to define the default
boot device.

Console Commands 5–5

boot

Flags

Examples

Flag

Description

-flags [longword,]
longword

Specifies additional information to the
operating system. In OpenVMS AXP,
specifies system root number and boot flags.
In DEC OSF/1 AXP, specifies boot flags.
Refer to Setting Boot Flags (boot_osflags) in
Chapter 6 for a list of possible settings and
their meanings.
The default boot flag setting is null. Use the
set boot_osflags command to change the
default boot flag setting.

-halt

Forces the bootstrap operation to halt and
invoke the console program once the image
is loaded and page tables and other data
structures are set up. Console device drivers
are not shut down when this qualifier is
present. Transfer control to the image by
entering the continue command.

In the following example, an OpenVMS AXP system boots from
the SCSI disk, dka0. If bootable software cannot be found on
dka0, the system attempts to boot from Ethernet port, eza0.
Boot flag settings are 0 and 1.
>>> boot -flags 0,1 dka0,eza0
In the next example, a DEC OSF/1 AXP system boots from the
SCSI disk, dka0, using boot flag setting i.
>>> boot -flags i dka0
In the next example, the system boots from the SCSI disk, dka0,
but remains in console mode. Subsequently, you can enter the
continue command to transfer control to the operating system.
>>> boot -halt dka0
In the next example, the system boots from the default boot
device. The console program returns an error message if a
default boot device has not been set.
>>> boot

Reference

5–6 Console Commands

set, show

cdp

cdp
Synopsis

Configure DSSI parameters.
cdp [-{a,i,n,o,u}] [-sn] [-sa allclass] [-su unitnum] [dssi_device]

Description

The cdp command allows you to modify DSSI device parameters
from the console terminal without connecting to a node’s DUP
server. The parameters that are modified are the DUP task
parameters: NODENAME, ALLCLASS, and UNITNUM.
If you enter cdp without an option or target device, the system
displays parameters for all DSSI devices in the system.

Parameters

Flags

Parameter

Description

dssi_device

Name of the DSSI device or DSSI controller.
Only the parameters for this device or the
devices on this controller will be modified.

Flag

Description

-a

Sets device allocation class, ALLCLASS.

-i

Selective interactive mode, for setting all
parameters.

-n

Sets device node name, NODENAME (up to
16 characters).

-o

Overrides warning messages.

-u

Sets device unit number, UNITNUM.

-sa allclass

Sets the allocation class (ALLCLASS) for
all DSSI devices in the system to the value
specified.

Console Commands 5–7

cdp

Examples

Flag

Description

-sn

Sets the node name (NODENAME) for
all DSSI devices in the system to either
RFhscn or TFhscn, where h is the device
host number (0), s is the device slot number
(0), c is the device channel number (0..3),
and n is the device node ID number (0..6).

-su unitnum

Sets the starting unit number (UNITNUM)
for the first DSSI device in the system
to the value specified. The unit number
for subsequent DSSI devices will be
incremented from this base.

In the following example, the system lists the DSSI parameters
for all DSSI drives on the system.
>>> cdp

pua0.0.0.0.0
pua0.1.0.0.0
pua0.2.0.0.0
pua0.3.0.0.0
>>>

ALPHA0
ALPHA1
ALPHA2
ALPHA3

0411214901371
0411214901506
041122A001625
0411214901286

! Storage adapter device name
" Node name (NODENAME)
# System ID (SYSTEMID)
$ Allocation class (ALLCLASS)
% Unit number (UNITNUM)
& Operating system device name

5–8 Console Commands

$%&
2
2
2
2

0
1
2
3

$2$DIA0
$2$DIA1
$2$DIA2
$2$DIA3

cdp

In the next example, the system sets the starting unit number
for the first dua device in the system to the number 10. In
increasing increments of 1, each subsequent dua device is also
assigned a new unit number.
>>> cdp dua* -su 10
pua0.0.0.0.0
pua0.1.0.0.0
pua0.2.0.0.0
pua0.3.0.0.0
>>>

ALPHA0
ALPHA1
ALPHA2
ALPHA3

0411214901371
0411214901506
041122A001625
0411214901286

2
2
2
2

10
11
12
13

$2$DIA10
$2$DIA11
$2$DIA12
$2$DIA13

In the next example, the node name for all DSSI devices in the
system is set to RFhscn using the default naming scheme (see
the description of the -sn flag).
>>> cdp -sn
pua0.0.0.0.0
pua0.1.0.0.0
pua0.2.0.0.0
pua0.3.0.0.0
>>>

RF0000
RF0001
RF0002
RF0003

0411214901371
0411214901506
041122A001625
0411214901286

2
2
2
2

10
11
12
13

$2$DIA10
$2$DIA11
$2$DIA12
$2$DIA13

In the next example, interactive editing mode is requested for
the drive dua13, or RF0003 from the previous example. In
the interaction that follows, the user sets the node name to
ALPHA13, the allocation class to 1, and the unit number to 5.
>>> cdp -i dua13
pua13.3.0.0.0:
Node Name [RF0003]? ALPHA13
Allocation Class [2]? 1
Unit Number [13]? 5
>>>

Reference

Setting and Examining Parameters for DSSI Devices in
Chapter 8.

Console Commands 5–9

continue

continue
Synopsis

Resume program execution on the specified processor.
continue

Description

Continues execution on the specified processor, or the primary
processor if a processor is not specified. The processor begins
executing instructions at the address that is currently in the
program counter. The processor is not initialized.
The continue command is only valid if you have not disturbed
the system state and if you halted the system by one of two
methods: either by pressing the Halt button on the operator
control panel or by entering Ctrl/P on the console terminal.
Note
Some console commands, for example, boot, may
alter the machine state so that program mode
cannot be successfully resumed. If program mode
cannot be successfully resumed, you may need to
reset the system.

Examples

In the following example, a system is commanded to resume
operating system mode.
>>> continue
In the next example, a system’s second processor is commanded
to resume operating system mode.
>>> continue &p1

5–10 Console Commands

date

date
Synopsis

Display or modify the current date and time.
date [yyyymmddhhmm.ss]

Description

Displays or modifies the current date and time. If you do not
specify any arguments, the current date and time are displayed.
If you specify arguments, date modifies the arguments that you
specify in the time-of-year (TOY) clock.
To modify the time, specify at least four digits, those that
represent the hour and minute (hhmm). Omitted fields are
not modified. When you set the date, the day of the week is
generated automatically.

Parameters

Parameter

Description

[yyyymmddhhmm.ss]

Specifies the date and time string
consisting of decimal pairs:
•

yyyy (0000–9999) year

•

mm (01–12) month

•

dd (01–31) day

•

hh (00–23) hour, required when
setting time

•

mm (00–59) minute, required when
setting time

•

ss (00–59) second

Console Commands 5–11

date

Examples

In the following example, the system is commanded to display
the current date and time.
>>> date
23:29:10 Monday, May 11, 1992
In the next example, the year, month, date, hour, and minute are
set on the system.
>>> date 199302260814
In the next example, the date and time are set on the system.
>>> date 121537
In the next example, the hour, minute, and second are set on the
system.
>>> date 1620.05

5–12 Console Commands

help or man

help or man
Synopsis

Display information about console commands.
help or man [command . . . ]

Description

The help command in OpenVMS AXP, and the man command
in DEC OSF/1 AXP, displays basic information about the use of
console commands when the system is in console mode.
With no options or arguments, the help command displays the
complete list of commands for which you can receive help.
•

If you enter a console command, the help command displays
information about that command.

•

If you enter the help argument after the help command, the
help command displays general information about the DEC
4000 AXP Rackmount system’s console commands and online
help.

Parameters

Examples

Parameter

Description

command . . .

Commands or topics for which help is
requested.

In the following example, the system is commanded to display
the topics for which help is available.
>>> help
In the next example, the system is commanded to display help
on all commands that begin with ‘‘ex’’.
>>> help ex
In the next example, the system is commanded to display help
on the boot command.
>>> help boot

Console Commands 5–13

init

init
Synopsis

Initialize the system.
init

Description

Initializes the system. The system performs a software reset and
executes the power-up self-tests.
Entering the init command is nearly equivalent to pressing
the Reset button. The difference is that part of memory is not
retested when you enter the init command.

Examples

In the following example, the system is initialized.
>>> init
...

5–14 Console Commands

man

man
See help.

Console Commands 5–15

set

set
Synopsis

Set or modify the value of an environment variable.
set [-default] envar val

Description

Sets or modifies the value of an environment variable.
Environment variables are used to pass configuration
information between the console and the operating system.

Parameters

Parameter

Description

envar

The environment variable to be assigned a
new value. Refer to the list of commonly
used environment variables below.

val

The value that is assigned to the
environment variable. Either a numeric
value or an ASCII string.

Flag

Description

-default

Restores an environment variable to its
default value.

Variable

Description

auto_action

Sets the console action following an error,
halt, or power-up, to halt, boot, or restart.
The default setting is halt.

bootdef_dev

Sets the default device or device list from
which the system attempts to boot. For
systems that ship with Factory Installed
Software (FIS), the default device is preset
at the factory to the device that contains
FIS. For systems that do not ship with FIS,
the default setting is null.

Flags

Environment
Variables

5–16 Console Commands

set

Variable

Description

boot_osflags

Sets additional parameters to be passed to
system software. When using OpenVMS
AXP software, these parameters are the
system root number and boot flags. When
using DEC OSF/1 AXP software, this
parameter is boot flag. The default setting
is null.

language

Sets the language in which system software
and layered products will be displayed.
The default setting may vary depending on
where your system was manufactured. The
codes for the languages are:
0 none (cryptic)
30 Dansk
32 Deutsch
34 Deutsch (Schweiz)
36 English (American)
38 English (British/Irish)
3A Espanol
3C Francais
3E Francais (Canadian)
40 Francais (Suisse Romande)
42 Italiano
44 Nederlands
46 Norsk
48 Portugues
4A Suomi
4C Svenska
4E Vlaams

tta0_baud

Sets the baud rate for the console terminal
port. Possible settings are 600, 1200,
2400, 4800, 9600, or 19,200. This setting
is volatile: if you cycle power on the system,
the baud rate switch setting (behind the
operator control panel) overrides the tta0_
baud setting.

tta1_baud

Sets the baud rate for the auxiliary serial
port. Possible settings are 600, 1200, 2400,
4800, 9600, or 19,200. The default setting is
9600.

Console Commands 5–17

set

Examples

Variable

Description

tta0_halts

Sets the ability to halt the system from the
console terminal keyboard by pressing Ctrl/P
or Break . Possible settings are 0: Ctrl/P and
Break are disabled; 2: Ctrl/P is enabled; 4:
Break is enabled; 6 Ctrl/P and Break are
enabled.

tta1_halts

Sets the ability to halt the system from the
device that is connected to the auxiliary
serial port by pressing Ctrl/P. Possible
settings are 0: Ctrl/P is disabled; 2: Ctrl/P
is enabled.

In the following example, the default device from which the
system attempts to boot is set to eza0.
>>> set bootdef_dev eza0
In the next example, the system’s default console action following
error, halt, or power-up is set to boot.
>>> set auto_action boot
In the next example, the baud rate of the auxiliary serial port is
set to 9600.
>>> set tta1_baud 9600
In the next example, the system default boot flags are set to 0,1.
>>> set boot_osflags 0,1
In the next example, the system default language is set to 32
(German).
>>> set language 32
In the next example, an environment variable called foo is
created and given a value of 5.
>>> set foo 5

Reference

clear, set host, show, and Chapter 6.

5–18 Console Commands

set host

set host
Synopsis

Connect the console program to the MSCP DUP server on a
DSSI device.
set host -dup [-task task_name] device

Description

Connects the console program to another DUP server on a DSSI
device. In the syntax, device is the name of the device to attach
to the console program. Using the -dup option invokes the DSSI
DUP server on the selected device. You can use the DUP protocol
to examine and modify parameters of a DSSI device.

Parameters

Parameter

Description

device

Specifies the device to attach to the console
program.

Flag

Description

-dup

Specifies connection to an MSCP DUP
server. The DUP service may be used to
examine and modify parameters of a DSSI
device.

-task task_name

Specifies which DUP service utility to
invoke. Refer to the example that follows for
a list of utilities. If you do not specify this
qualifier, a directory of utilities is displayed.

Flags

Console Commands 5–19

set host

Examples

The following example shows how to connect to the MSCP DUP
server on a device.

>>> show device du
dud0.0.0.3.0
R2YQYA$DIA0
>>> set host -dup dud0
starting DIRECT on pud0.0.0.3.0 (R2YQYA)

RF72

Copyright (C) 1990 Digital Equipment Corporation
PRFMON V1.0 D 2-NOV-1990 10:30:58
DKCOPY V1.0 D 2-NOV-1990 10:30:58
DRVEXR V2.0 D 2-NOV-1990 10:30:58
DRVTST V2.0 D 2-NOV-1990 10:30:58
HISTRY V1.1 D 2-NOV-1990 10:30:58
DIRECT V1.0 D 2-NOV-1990 10:30:58
ERASE V2.0 D 2-NOV-1990 10:30:58
VERIFY V1.0 D 2-NOV-1990 10:30:58
DKUTIL V1.0 D 2-NOV-1990 10:30:58
PARAMS V2.0 D 2-NOV-1990 10:30:58
Total of 10 programs.
Task?
>>> set host -dup -task params dud0
starting PARAMS on pud0.0.0.3.0 (R2YQYA)
Copyright (C) 1990 Digital Equipment Corporation
PARAMS> show allclass
Parameter
Current
Default
Type
Radix
--------- ---------------- ---------------- -------- ----ALLCLASS
0
0
Byte
Dec
PARAMS>exit
Exiting...
>>>

5–20 Console Commands

show

show
Synopsis

Display an environment variable value or other information.
show [envar] [{config,device,memory,pal,version}]

Description

Displays the current value (or setting) for an environment
variable that you specify.
Alternatively, displays other information about the system,
according to the parameters that you enter on the command
line. For example, you can display the system configuration by
entering show config.

Parameters

Parameter

Description

envar

Displays the value of the environment
variable specified. Refer to the list of
commonly used environment variables
described in the next table.

config

Displays the current system configuration.

device

Displays devices and controllers in the
system.

memory

Displays the memory module configuration.

pal

Displays the Privileged Architecture Library
code (PALcode) version.

version

Displays the console program version.

Console Commands 5–21

show

Environment
Variables

Variable

Description

auto_action

Displays the console action following an
error, halt, or power-up: either halt, boot, or
restart.

bootdef_dev

Displays the device or device list from which
bootstrapping is attempted.

boot_osflags

Displays the additional parameters to be
passed to system software.

language

Displays the language in which system
software and layered products are displayed.

tta0_baud

Displays the baud rate for the console
terminal port.

tta1_baud

Displays the baud rate for the auxiliary
serial port.

tta0_halts

Displays the setting that indicates whether
you can halt the system from the console
terminal by pressing Ctrl/P or Break .
Possible settings are:

tta1_halts

5–22 Console Commands

•

0: Ctrl/P and Break are disabled.

•

2: Ctrl/P is enabled.

•

6: Ctrl/P and Break are enabled.

Break is enabled.

Displays the setting that indicates whether
you can halt the system from the device that
is connected to the auxiliary serial port by
pressing Ctrl/P. Possible settings are:
•

0: Ctrl/P is disabled.

•

2: Ctrl/P is enabled.

show

Examples

In the following example, the system displays the version of the
console program that is installed on the system. The console
program version is V3.0-1.
>>> show version
version
>>>

V3.0-1 Sep 20 1992 00:28:54

In the next example, the default system power-up action is
displayed.
>>> show auto_action
auto_action
boot
>>>
In the next example, a system’s default boot device is displayed.
The default boot device in the example is eza0.
>>> show bootdef_dev
bootdef_dev
eza0.0.0.6.0
>>>
In the next example, the baud rate for the auxiliary serial port is
displayed. The baud rate in the example is 1200.
>>> show tta1_baud
tta1_baud
1200
>>>

Reference

set and in Chapter 8: show cluster, show config, show device,
show pal, show memory, show version

Console Commands 5–23

test

test
Synopsis

Tests the system.
test

Description

Performs a test on the entire system, excepting tape drives.
When the tests are successfully completed, the message ‘‘tests
done’’ is displayed. If any of the tests fail, a failure message is
displayed.
All tests run concurrently for a minimum of 30 seconds. Tests
complete when all component tests have completed at least one
pass. Test passes are repeated for any component that completes
its test before other components.
The run time of a test is proportional to the amount of memory
to be tested and the number of disk drives to be tested. Running
test on a system with fully configured 512-MB memory takes
approximately 10 minutes to complete.

Examples

In the following example, the system, excepting tape drives, is
tested, and the tests complete successfully.
>>> test
tape drives, if any, will not be tested
tests done
>>>

5–24 Console Commands

test

In the next example, the system, excepting tape drives, is tested,
and the system reports an error message.
>>> test
tape drives, if any, will not be tested
retries to pkd0.2.0.3.0 exhausted
failed to send Read to dkd200.2.0.3.0
*** Hard Error - Error #5 Diagnostic Name
ID
Device Pass Test Hard/Soft
29-JAN-1970
exer_kid
00000129
dkd200.2.0.3
0
0
1
0
1:14:05
Error in read of 0 bytes at location 0005D200 from device dkd200.2.0.3.0
*** End of Error ***
tests done
>>>

References
The following table describes where to find additional
information about the console commands.
Task

Document

Enter comprehensive console
commands

DEC 4000 Model 600 Series
Technical Manual

Console Commands 5–25

6
Setting Environment Variables
Chapter Description
What Is an
Environment
Variable?

This chapter describes the DEC 4000 AXP Rackmount
environment variables.

In This Chapter

This chapter covers the following information:

An environment variable is a firmware parameter that you
can access from console mode. The DEC 4000 AXP Rackmount
console program includes multiple environment variables. The
setting of these firmware parameters affects the way the system
powers up and boots operating system software.

•

Overview: Do I Need to Set Environment Variables?

•

Before You Begin

•

Changing the Default Startup Action (auto_action)

•

Setting or Changing the Default Boot Device (bootdef_dev)

•

Setting Boot Flags (boot_osflags)

•

Setting the Language (language)

•

Changing the Baud Rate (tta0_baud and tta1_baud)

•

Enabling Halt Key Functions (tta0_halts and tta1_halts)

•

When You Have Finished Setting Variables

Setting Environment Variables

6–1

Overview: Do I Need to Set Environment Variables?

Overview: Do I Need to Set Environment Variables?
Deciding to Set
Environment
Variables

Although it is not essential to set environment variables, setting
environment variables can simplify the operation of your system.
You set environment variables from console mode. The ideal
time to set environment variables is before you boot operating
system software. If your operating system is up and running,
you must invoke console mode. (Refer to Invoke Console Mode in
Chapter 3.)
After you have finished setting environment variables, you can
begin or resume operating your system in operating system
mode.

What Variables
Can I Set?

Table 6–1 describes the environment variables and their factory
settings.

Displaying
Current
Environment
Variables

You can use the show command to display the current setting of
any environment variable described in Table 6–1. For instance,
to display the current setting of the auto_action environment
variable, enter the following:
>>> show auto_action

Return

The system responds with a display similar to the following:
auto_action

boot

In this example, the auto_action environment variable is set to
boot.

6–2 Setting Environment Variables

Overview: Do I Need to Set Environment Variables?

Table 6–1 Environment Variables
Variable

Function

Factory Setting

auto_action

Specifies what action the console should
take any time the system is powered up,
crashes, or the Reset button is pressed.

Halt

bootdef_dev

Specifies the default boot device to the
system.

System device on which
Factory Installed
Software (FIS) was
loaded.

boot_osflags

Sets the boot flags and in OpenVMS AXP,
a root number.

Null

language

Sets the console keyboard layout to a
supported language.

Language used where
your system was built.

tta0_baud

Specifies the baud rate for the console
terminal port. (This setting is volatile.)

9600

tta1_baud

Specifies the baud rate for the auxiliary
serial port.

9600

tta0_halts

Specifies whether Ctrl/P and Break
are enabled on the console terminal
keyboard.

4 ( Break is enabled.)

tta1_halts

Specifies whether Ctrl/P and Break are
enabled on the device connected to the
auxiliary serial port.

0 (Ctrl/P and Break are
disabled.)

Setting Environment Variables

6–3

Before You Begin

Before You Begin
Preliminary
Actions

Before changing any environment variables, you should have
done the following:
•

Placed your system at the console prompt.
If your system is not displaying the >>> prompt, refer to
Invoke Console Mode in Chapter 3.

•

Determined which variables, if any, you wish to set.
Each of the following sections in this chapter describes a
particular environment variable. For information about why
you might want to set a variable, refer to the section that
describes that variable.

•

Read a summary of the set command and the environment
variables in set in Chapter 5.

•

Read Chapter 4 and the rest of this chapter.

Changing the Default Startup Action (auto_action)
Default Startup
Actions

The setting of the auto_action environment variable determines
how your system reacts when you power up the system, or press
the Reset button, or when the system crashes. There are three
possible settings:
•

halt

•

boot

•

restart

The default setting is halt.

6–4 Setting Environment Variables

Changing the Default Startup Action (auto_action)

Your System’s
Current Startup
Action

To display your system’s current default startup action, enter the
following:
>>> show auto_action

Return

The system responds with a display similar to the following:
auto_action

boot

In this example, the default startup action is boot.

Choosing
‘‘Halt’’

Setting the default startup action to halt causes your system to
remain in console mode when you power up the system, when
the system crashes, or when you press the Reset button.

Choosing
‘‘Boot’’

If you plan to boot your system from the same device, you may
want to set your system’s default startup action to boot.
The bootdef_dev environment variable works in conjunction
with this setting: whenever you power up your system or press
the Reset button, or the system crashes, your system boots
automatically from the boot device identified by the bootdef_dev
environment variable. The system is said to ‘‘autoboot.’’
Autobooting:

Choosing
‘‘Restart’’

•

Causes the operating system to automatically restart in the
event of a power interrupt.

•

Simplifies the boot process for a less experienced user trying
to boot operating system software.

•

Decreases the user response required to get to the operating
system level.

Setting the default startup action to restart causes your system
to attempt to restart the operating system automatically if
the system crashes. If the restart attempt is unsuccessful, the
system reboots the operating system.
When you power up the system or press the Reset button, the
system automatically boots the operating system (autoboot).
Refer to Choosing Boot for more information about autobooting.

Setting Environment Variables

6–5

Changing the Default Startup Action (auto_action)

Set the Default
Startup Action

To set the default startup action, complete the following steps:
Step

Action

Are you choosing the boot or the restart startup
action?
•

No. Proceed to the next step.

•

Yes. Identify the boot device to the system if
it is not already identified. Refer to the next
section, Setting or Changing the Default Boot
Device (bootdef_dev) .

Set the default startup action by entering the
following command:
>>> set auto_action action
For example, to set the startup action to boot,
enter the following:
>>> set auto_action boot

Undo the
Setting

Set another environment variable or reboot the
system.

Clear the auto_action environment variable or set your system to
manual boot by entering the following command:
>>> set auto_action halt

6–6 Setting Environment Variables

Setting or Changing the Default Boot Device (bootdef_dev)

Setting or Changing the Default Boot Device (bootdef_dev)
Default Boot
Device

The boot device is the device from which the bootstrap system
software is acquired. In most cases, the default boot device has
been identified on your system as the device on which Factory
Installed Software (FIS) was loaded.

Why Set the
Default Boot
Device?

By identifying the boot device to your system, you can simplify
the process of booting operating system software as follows:

Your System’s
Current Default
Boot Device

•

You can enter b and press Return at the console prompt and
the system will find and boot operating system software.

•

You can automatically boot operating system software
by setting the default startup action to boot (using the
auto_action environment variable) in conjunction with this
variable.

To display your system’s current default boot device, enter the
following:
>>> show bootdef_dev

Return

The system responds with a display similar to the following:
bootdef_dev

dka0

In this example, the default boot device is dka0.

Which One
Is the Boot
Device?

If a default boot device has not been set and you do not know
which device is the boot device, determine your system’s boot
device as follows:
•

Display the devices connected to your system:
>>> show device
...

•

Beginning at the top of the list of devices that are displayed
and working downward, try booting operating system
software from each device.

Setting Environment Variables

6–7

Setting or Changing the Default Boot Device (bootdef_dev)

For instance, to try booting software from SCSI devices:
>>> boot dka0
boot dka0.1.0.2.0 -flags 0
block 0 of dka0.1.0.2.0 is not a valid boot block
bootstrap failure
>>>
>>>boot dka1
boot dka1.1.0.2.0 -flags 0
booting system software...
To try booting software from DSSI devices:
>>> boot dua0
boot dua0.1.0.2.0 -flags 0
block 0 of dua0.1.0.2.0 is not a valid boot block
bootstrap failure
>>>
>>>boot dua1
boot dua1.1.0.2.0 -flags 0
booting system software...
The system begins booting when you have found the boot
device.

Preliminary
Considerations

Before identifying the boot device, consider the following:
•

Your boot device may already be set. (See previous section.)

•

You can identify multiple boot devices to the system. By
doing so, when you enter b or boot at the console prompt, the
system searches for a bootable device from the list of devices
that you specify. The system then automatically boots from
the first device on which it finds software.

•

You can override the default boot device by specifying an
alternative device name on the boot command line.
Note
When you identify multiple devices, the system
attempts to boot operating system software from
each device in the order that you list the devices.
Always list network devices last.

6–8 Setting Environment Variables

Setting or Changing the Default Boot Device (bootdef_dev)

Set or Change
the Default
Boot Device

Set or change the default boot device as follows:
Step

Action

Determine the device or devices that you wish to
set as the default.
If a default boot device has not been set and you
do not know your system’s boot device, see the
previous section Which One Is the Boot Device?

Set the environment variable by entering the
following command, substituting for device_name
the name (or names) of your boot devices:
set bootdef_dev device_name
For example:
If the boot
device is . . .

The SCSI drive,
DKA0
The DSSI drive,
DUB0
Multiple devices,
DUB0 and DKA0

Undo the
Setting

Enter . . .

>>> set bootdef_dev DKA0

>>> set bootdef_dev DUB0

>>> set bootdef_dev DUB0,DKA0

Set another environment variable or reboot the
system.

Clear the bootdef_dev environment variable by entering the
following command:
>>> set bootdef_dev ""

Setting Environment Variables

6–9

Setting Boot Flags (boot_osflags)

Setting Boot Flags (boot_osflags)
What Are Boot
Flags?

Boot flags contain information that is read and used by the
operating system during a system bootstrap procedure.
Boot flags may be passed to the operating system either on the
boot command line with the -flags option (see boot in Chapter 5)
or by setting the boot_osflags environment variable as described
in this section. The default boot flag setting is null.
The interpretation of the boot flags is operating system
dependent.

Boot Flags
Settings for
OpenVMS AXP
Systems

The OpenVMS AXP operating system takes two boot flag
arguments:
•

root number

•

boot flags

If the boot_osflags environment variable is given or has been set
to only one argument, the argument designates the boot flag and
not the root number.
Root Number Settings
The root number is the directory number on the system disk on
which OpenVMS AXP files are located.
For instance:
If OpenVMS AXP
files are located
on . . .

The root number
for the system is . . .

[SYS0.SYSEXE]

0 (default)

[SYS1.SYSEXE]

[SYS2.SYSEXE]

[SYS3.SYSEXE]

If your files are located on the default disk [SYS0.SYSEXE], you
do not need to specify the root number.

6–10 Setting Environment Variables

Setting Boot Flags (boot_osflags)

Boot Flag Settings
Possible boot flags settings and their meanings for OpenVMS
AXP systems are:
Flag Setting

Bit Number

Meaning

Bootstrap conversationally (enables
you to modify SYSGEN parameters
in SYSBOOT).

Map XDELTA to running system.

Stop at initial system breakpoint.

Perform diagnostic bootstrap.

Stop at the bootstrap breakpoints.

Omit header from secondary
bootstrap image.

Prompt for the name of the
secondary bootstrap file.

100

Halt before secondary bootstrap.

10000

Display debug messages during
booting.

20000

Display user messages during
booting.

For more information about boot flags, refer to OpenVMS Alpha
Version 1.0 Upgrade and Installation Manual.

Setting Environment Variables

6–11

Setting Boot Flags (boot_osflags)

Boot Flags
Settings for
DEC OSF/1
AXP Systems

Your System’s
Current Default
Boot Flags

The DEC OSF/1 AXP operating system takes only one boot flag
argument: the boot flag.
Possible boot flag settings and their meanings for DEC OSF/1
AXP systems are:
Flag Setting

Meaning

Load operating system software from the specified
boot device (autoboot). Boot to multiuser mode.

Prompt for the name of a file to load and other
options (boot interactively). Boot to single user
mode.

To display your system’s current default boot flags, enter the
following:
>>> show boot_osflags

Return

The system responds with a display similar to the following:
boot_osflags

1,8

In this example, the default root setting is 1 and the boot flag
setting is 8.
If the boot_osflags environment variable is given or has been set
to only one argument, the argument designates the boot flag and
not the root number.

When to Set
Boot Flags

Under normal circumstances, the default boot flag settings will
suit your environment.
If you wish to change your system’s boot process, using the
possible flag settings and their meanings, set your system boot
flags according to how you want the default boot process to work.

6–12 Setting Environment Variables

Setting Boot Flags (boot_osflags)

Set Boot Flags

Set boot flags as follows:
Step

Action

Set the environment variable by entering the
following command, substituting for root_number
and bootflag the values to which you wish to set
the root number and boot flags.
>>> set boot_osflags root_number,bootflag
For instance, in OpenVMS AXP, to set the root
number to 1 and the boot flags to 2, enter the
following:
>>> set boot_osflags 1,2
In OpenVMS AXP, to set the boot flags to 1 and
to leave the root number as the default, enter the
following:
>>> set boot_osflags 1
In DEC OSF/1 AXP, to set the boot flags to
autoboot, enter the following:
>>> set boot_osflags a

Set another environment variable or reboot the
system.

Setting Environment Variables

6–13

Setting the Language (language)

Setting the Language (language)
Do I Need
to Set the
Language?

The DEC 4000 AXP Rackmount system ships from the factory
with a default language setting that determines the language
that the system will display on the console terminal.
If the default language differs from the language you want the
system to display, you can change the language setting.

Possible
Settings

Possible language settings and their codes are as follows:

Your System’s
Current
Language

To display your system’s current language, enter the following:

0 none (cryptic)
30 Dansk
32 Deutsch
34 Deutsch (Schweiz)
36 English (American)
38 English (British/Irish)
3A Espanol
3C Francais
3E Francais (Canadian)
40 Francais (Suisse Romande)
42 Italiano
44 Nederlands
46 Norsk
48 Portugues
4A Suomi
4C Svenska
4E Vlaams

>>> show language

Return

The system responds with a display similar to the following:
language

In this example, the language is set to 36: the system displays
text written in American English.

6–14 Setting Environment Variables

Setting the Language (language)

Change the
Language

To set the language that the system displays on output devices,
do the following:
Step

Action

Determine the code number for the language you
want system output devices to display.

Enter the following:
>>> set language language_code
For example:
>>> set language 3A
This commands sets the display to Spanish.

Changing the Baud Rate (tta0_baud and tta1_baud)
Which Baud
Rates Can I
Change?

Two environment variables allow you to change the baud rate of
the console terminal port and the auxiliary serial port from the
console terminal:
•

tta0_baud allows you to set the baud rate for the console
terminal port.

•

tta1_baud allows you to set the baud rate for the auxiliary
serial port.

The setting of tta0_baud is volatile, that is, if you cycle power on
the system, the value of tta0_baud is overridden by the setting of
the baud rate switch that is located behind the system’s operator
control panel. Refer to Changing the Baud Rate in Chapter 10
for information about setting the console terminal port baud rate
more permanently.

Setting Environment Variables

6–15

Changing the Baud Rate (tta0_baud and tta1_baud)

Displaying the
Current Baud
Rates

The default setting for both tta0_baud and tta1_baud is 9600.
Displaying the Console Terminal Port Baud Rate
To display your console terminal port’s baud rate, enter the
following:
>>> show tta0_baud

Return

The system responds with a display similar to the following:
tta0_baud

9600

In this example, the system’s console terminal port baud rate is
9600.
Displaying the Auxiliary Serial Port Baud Rate
To display your auxiliary serial port baud rate, enter the
following:
>>> show tta1_baud

Return

The system responds with a display similar to the following:
tta1_baud

9600

In this example, the system’s auxiliary serial port baud rate is
9600.

6–16 Setting Environment Variables

Changing the Baud Rate (tta0_baud and tta1_baud)

Change the
Baud Rate

Change a baud rate as follows:
Step

Action

Determine the baud rate to which you must set
the console terminal or auxiliary serial port. The
possible settings are:
600
1200
2400
4800
9600
19,200

Set the baud rate by entering the following
command, substituting for port_envar the
environment variable for the port you wish to
set, and for baud_rate the baud rate to which you
wish to set the port.
>>> set port_envar baud_rate
For instance, to set the console terminal port to
1200 baud, enter the following:
>>> set tta0_baud 1200
To set the auxiliary serial port to 1200 baud, enter
the following:
>>> set tta1_baud 1200

Set another environment variable or reboot the
system.

Setting Environment Variables

6–17

Enabling Halt Key Functions (tta0_halts and tta1_halts)

Enabling Halt Key Functions (tta0_halts and tta1_halts)
Why Enable
Halt Key
Functions?

Possible
Settings

Your System’s
Current Halt
Key Settings

To invoke console mode (halt the system), you must press the
Halt button on the system. Alternatively, you can invoke console
mode from a terminal keyboard. You enable this ability by
setting an environment variable:
•

tta0_halts allows you to invoke console mode from the
console terminal keyboard by pressing Ctrl/P or Break .

•

tta1_halts allows you to invoke console mode from the
keyboard of a device connected to the auxiliary serial port by
pressing Ctrl/P.

Possible settings for each environment variable are as follows:
tta0_halts
Setting

tta1_halts
Setting

Description

0 (default)

Ctrl/P and Break are disabled.

Ctrl/P is enabled.

4 (default)

–

Break is enabled.

–

Both Ctrl/P and Break are enabled.

Display the current halt key settings for the two different ports
as follows.
Displaying Your Console Terminal’s Halt Key Settings
To display your console terminal keyboard’s current halt key
settings, enter the following:
>>> show tta0_halts
tta0_halts
4

Return

In this example, tta0_halts is set to 4: Break is enabled.

6–18 Setting Environment Variables

Enabling Halt Key Functions (tta0_halts and tta1_halts)

Displaying Your Auxiliary Serial Device’s Halt Key Settings
To display current halt key settings for the device connected to
the auxiliary serial port, enter the following:
>>> show tta1_halts
tta1_halts
0

Return

In this example, tta1_halts is set to 0: Ctrl/P and Break are
disabled.

Set or Change
the Halt Key
Functions

Set the tta0_halts and tta1_halts environment variables to suit
your system environment. For example, to enable Ctrl/P and
Break on the console terminal keyboard, enter the following:
>>> set tta0_halts 6
To enable Ctrl/P on the remote console device, enter the
following:
>>> set tta1_halts 2

When You Have Finished Setting Variables
Reboot the
System

When you have finished setting environment variables, return to
normal operation by rebooting your system:
Step

Action

Did you invoke console mode by pressing the Halt
button on the control panel?
•

Yes. Press the Halt button on the control panel to
the out position.

•

No. Proceed to the next step.

Boot the system using the boot command.

Setting Environment Variables

6–19

7
Operating Mass Storage Devices
Chapter Description
Overview

Mass storage devices are drives that are used to store large
amounts of data for extended periods. The DEC 4000 AXP
Rackmount system uses both DSSI and SCSI mass storage
devices to store data.

In This Chapter

This chapter covers the following information:
•

DEC 4000 AXP Rackmount Mass Storage Devices and
Compartments

•

Operating DEC 4000 AXP Rackmount Mass Storage Devices
The devices described are: RZ-series drives, the RRD42, the
TLZ06, and the TZ30.

•

For Additional
Information

Maintaining Mass Storage Media and Devices

This chapter does not describe how to read data to or copy data
from a drive. Consult your system software documentation for
this type of information.

Operating Mass Storage Devices 7–1

DEC 4000 AXP Rackmount Mass Storage Devices and Compartments

DEC 4000 AXP Rackmount Mass Storage Devices and
Compartments
Locating
Mass Storage
Devices

Warning
The bottom tray is available for service access
only. This area is for use by Digital customer
service personnel and qualified self-maintenance
customers only.

Mass storage devices are located in the bottom tray inside your
system as shown in Figure 7–1. Two mounts are reserved for
fixed-media drives ( – ); these drives are RZ-series only.

Two mounts are reserved for removable-media devices ( – );
these devices include the RRD42, the TLZ06, and the TZ30.

7–2 Operating Mass Storage Devices

DEC 4000 AXP Rackmount Mass Storage Devices and Compartments

Local Disk
Converter
(LDC)

A local disk converter (LDC)
that is located in the bottom tray
powers the internal mass storage devices.
Note
Indicators and lights on any storage media
installed in the center mounting positions of the
bottom tray are not visible without lowering the
tray.

The DEC 4000 AXP Rackmount only supports one (1) Local
Disk Converter (LDC). Therefore, should this LDC fail, the
Disk Power Failure Indicator on the Power System Controller
(PSC) will light and a "3" is displayed in the hexadecimal Fault
ID display. Any other error code displayed in the Fault ID
display in conjunction with a Disk Power Failure indication,
is not applicable to the DEC 4000 AXP Rackmount. For more
information on interpreting LDC error codes, refer to Figure 11–1
and Table 11–5.

Operating Mass Storage Devices 7–3

Operating DEC 4000 AXP Rackmount Mass Storage Devices

Operating DEC 4000 AXP Rackmount Mass Storage Devices
Before You
Operate Mass
Storage
Devices

Before operating mass storage devices:
•

Mount the device.
Typically, you must mount a device before you can begin
using it. You mount a device while the system is in operating
system mode. Refer to your operating system documentation
for information about how to mount a device.

•

Familiarize yourself with the care and maintenance required
by the device.
These tasks are described in Maintaining Mass Storage
Media and Devices later in this chapter.

7–4 Operating Mass Storage Devices

Operating DEC 4000 AXP Rackmount Mass Storage Devices

Figure 7–1 Bottom Tray

5
4
3
2
1

NUO-420-28-DG

Operating Mass Storage Devices 7–5

Operating DEC 4000 AXP Rackmount Mass Storage Devices

Operating
DEC 4000 AXP
Rackmount
Devices

The remaining sections of this chapter describe how to operate
each DEC 4000 AXP Rackmount mass storage device. Table 7–1
describes the half height devices that are available for use in the
bottom tray of the DEC 4000 AXP Rackmount system.
NOTE
The DEC 4000 AXP Rackmount system supports
only half height storage devices internally.

Table 7–2 describes the devices that may be mounted and
supported externally to the DEC 4000 AXP Rackmount system.
Table 7–1 Devices Supported Internally to the DEC 4000 AXP Rackmount
Storage
Option

Capacity

Form
Factor

Seek
Time

Transfer
Rate

Interface

RRD42

600 MB

5 1/4 in

300 ms

150 KB/s

SCSI

RZ26

1.0 GB

3 1/2 in

9.5 ms

3.3 MB/s

SCSI/Fast SCSI

RZ27

1.6 GB

3 1/2 in

9.5 ms

44 MB/s

SCSI/Fast SCSI

TLZ06

4.0 GB

5 1/4 in

—

366 KB/s

SCSI

TZ30

95 MB

5 1/4 in

—

62.5 KB/s

SCSI

Table 7–2 Devices Supported Externally to the DEC 4000 AXP Rackmount
Storage
Option

Capacity

Form
Factor

Seek
Time

Transfer
Rate

Interface

RF35

852 MB

3 1/2 in

9.5 ms

4.0 MB/s

DSSI

RF73

2.0 GB

5 1/4 in

12.9 ms

2.2 MB/s

DSSI

RZ73

2.0 GB

5 1/4 in

12 ms

2.2 MB/s

SCSI

TSZ07

160 MB

—

4.0 MB/s

SCSI

TZ85

2.6 GB

5 1/4 in

—

800 KB/s

SCSI

TZ857

18.2 GB

—

800 KB/s

SCSI

7–6 Operating Mass Storage Devices

Operating RZ- and RF-Series Disk Drives

Operating RZ- and RF-Series Disk Drives
RZ- and
RF-Series
Description

RZ- and RF-series drives are fixed-media disk drives that store
up to 3.2 gigabytes of information on a disk that remains fixed
inside the drive. RZ-series drives are SCSI compatible; RF-series
drives are DSSI compatible.
Four SCSI-compatible mass storage devices can be mounted
internally in your system. Other SCSI or DSSI devices can be
mounted externally. (See Figure 7–1.)

External Fast
SCSI

Depending on the configuration you ordered, your system can
support fast SCSI speed on external RZ-series drives. Fast
SCSI speed is an optional mode of SCSI-2 that allows data
transmission rates of up to 10 MB/s. Actual transmission rate is
dependent on cable length and the amount of devices on the bus.
For further information on fast SCSI devices contact your Digital
Sales Representative.

RZ-Series Fault
Light

Each RZ-series disk drive has a fault light. If the fault light
comes on blinking amber the drive is executing self-tests. If the
fault light comes on solid amber, the drive has failed.
Note
Indicators and lights on any storage media
installed in the center mounting positions of the
bottom tray are not visible without lowering the
tray.

Operating Mass Storage Devices 7–7

Operating RZ- and RF-Series Disk Drives

Write-Protecting
an RF-Series
and RZ-Series
Disk

The RF-Series and RZ-series drives have no Write-Protect
button. You set write-protection through console commands in
console mode.
Software Write-Protect for RF- and RZ-Series Drives
To software write-protect an RF-series drive or an RZ-series drive
on the OpenVMS AXP operating system, enter the following DCL
command:
$ MOUNT device_name volume_label/SYSTEM/NOWRITE
The device_name is the device name shown using the OpenVMS
AXP DCL command SHOW DEVICE DI. The volume_label is the
volume label for the device. For example, the following command
will software write-protect device $1$DIA1:
$ MOUNT $1$DIA1 OMEGA/SYSTEM/NOWRITE
To write-enable the device, dismount the device, and then
remount it (without using the /NOWRITE qualifier). For
example:
$ DISMOUNT $1$DIA1 OMEGA/SYSTEM
$ MOUNT $1$DIA1 OMEGA/SYSTEM
To check the protection status of the drive on the OpenVMS AXP
operating system, enter SHOW DEVICE DI. A write-protected drive
will show a device status of ‘‘Mounted wrtlck’’. Refer to your
OpenVMS AXP documentation for more information on using the
MOUNT utility.
Caution
When you dismount the device, then mount it
again, it will no longer be write-protected, unless
you use the /NOWRITE qualifier.

7–8 Operating Mass Storage Devices

Operating RZ- and RF-Series Disk Drives

Console Mode Write-Protect For RF-Series and RZ-Series
Drives
Note
RF-series drives can only be incorporated into
the DEC 4000 AXP Rackmount system via the
external media expansion ports (A, B, C, or D). See
Chapter 8 for information on using external media
expansion ports.

The console mode write-protect provides a more permanent
write-protection than the software write-protect. Once you
write-protect an RF-series drive from console mode, it remains
write-protected, regardless of the availability of the operating
system or if the system is powered down. You cannot remove a
console mode write-protection using the mount command.
Consider write-protecting an RF-series drive from console mode
in the following situations:
•

To write-protect an RF-series drive when the OpenVMS AXP
operating system is not available

•

To ensure that an RF-series drive remains write-protected
under all circumstances

To write-protect an RF-series drive through console commands
entered at the console prompt (>>>), use the following
instructions:
1. Access the Diagnostic and Utility Program (DUP) driver for
the device you want to write-protect.
To access the DUP driver from console mode:
a. Invoke console mode by pressing the Halt button or
powering up the system with the Halt button pressed to
the in position.
Caution
Halting your system without following the
shutdown procedure described in your system
software manuals can result in loss of data.

Operating Mass Storage Devices 7–9

Operating RZ- and RF-Series Disk Drives

b. Access the DUP driver by setting host to the specific
device you want to write protect.
Use the following command:
>>> set host -dup device_name -task params
The device_name is the complete device name (console
device name or OpenVMS AXP device name) as shown
using the show device du command.
2. At the PARAMS> prompt, enter SET WRT_PROT 1 to write-protect
the RF-series drive to which you are currently connected.
Note
To verify that you have set host to the intended
drive, enter the locate command at the PARAMS>
prompt. The locate command causes the drive’s
fault light to blink momentarily.

3. At the PARAMS> prompt, enter SHOW WRT_PROT to verify that
the WRT_PROT parameter is set to 1.
4. After you have completed setting and examining the WRT_
PROT device parameter, enter the write command at the
PARAMS> prompt to save the device parameter. The change is
recorded to nonvolatile memory.
5. Enter the EXIT command at the PARAMS> prompt to exit the
DUP driver utility for the specified device.
Example 7–1 provides an example of setting a write-protect
through console commands in console mode.

7–10 Operating Mass Storage Devices

Operating RZ- and RF-Series Disk Drives

Example 7–1 Setting Hardware Write-Protection Through
Firmware
>>> set host -dup dua0.0.0.0.0 -task params
Starting DUP server...
Copyright (c) 1992 Digital Equipment Corporation
PARAMS> SET WRT_PROT 1
PARAMS> WRITE
PARAMS> SHOW WRT_PROT
Parameter
Current
Default
Type
Radix
--------- ---------------- ---------------- -------- ----WRT_PROT
1
0 Boolean
0/1
PARAMS> EXIT
Exiting...
Stopping DUP server...
>>>
To remove the console mode write-protection, repeat the above
procedure, but set the WRT_PROT value to 0.
You can verify that the device is write-protected while running
OpenVMS AXP. Enter the DCL command show device di. A
write-protected drive will show a device status of ‘‘Mounted
wrtlck’’. If you enter the OpenVMS AXP command show
device/full, a write-protected drive will be listed as ‘‘software
write-locked’’.
Note
You cannot remove console mode write-protection
using the OpenVMS AXP MOUNT utility.

Operating Mass Storage Devices 7–11

Operating the RRD42 Compact Disc Drive

Operating the RRD42 Compact Disc Drive
RRD42
Description

The RRD42 compact disc drive reads information from
removable, read-only compact discs that hold up to 600
megabytes per compact disc. Figure 7–2 shows the components
of the RRD42.

! Headphone port
" Headphone volume control
# Disc caddy slot
$ ID dimple
% Busy light
& Eject button
' Manual eject hole
( Compact disc caddy
) Compact disc

Up to two RRD42 drives can be located in the bottom tray.
Caution
Handle a compact disc by its edges. Do not touch
the surface of a disc. Fingerprints and dust can
cause the disc to malfunction.

7–12 Operating Mass Storage Devices

Operating the RRD42 Compact Disc Drive

Figure 7–2 RRD42 Compact Disc Drive and Compact Disc

9
XXXX
XXXXXX
XXXX
XX
XX
XX
XX XX
XX
XX
XX
XX
XX
XXXXXX
XX XX
XXXXXX
XXXXXX
XXXX
XXXX
XX
XX XX
XXXX
XXXX
XX XX
XXXX XX
XX
XXXXXX

NUO-420-30-DG

Operating Mass Storage Devices 7–13

Operating the RRD42 Compact Disc Drive

Inserting a
Compact Disc

To insert a compact disc into the RRD42 (Figure 7–3):
1. Gather both the compact disc caddy and the disc you wish to
insert.
2. If there is a protective film on the center of the caddy lid,
remove the film .

3. Open the caddy by pressing the tabs on both sides of the
caddy at the end opposite the shutter .

4. Set the disc, printed side up, into the caddy as shown

5. Press firmly on both corners to close the caddy lid.

6. Insert the disc caddy into the drive . Push the caddy
gently into the drive as far as it will go. The caddy should be
completely inside the drive when properly inserted.
The busy light comes on when the caddy has been inserted
correctly.
7. When the busy light goes off, the compact disc drive is
ready to use. To operate the compact disc drive, follow the
instructions provided with your system software.

Removing a
Compact Disc

To remove a compact disc (Figure 7–3):
1. Press the eject button

The caddy will automatically eject part way.
2. Remove the caddy from the drive

RRD42 Light

The RRD42 busy light comes on when the system is reading data
from the compact disc.

7–14 Operating Mass Storage Devices

Operating the RRD42 Compact Disc Drive

Figure 7–3 Inserting and Removing a Compact Disc
1

3
XXXXXX
XXXXXX
XXXXXX
XX
XXXX
XX
XX
XX
XX
XXXXXX
XX
XX
XX
XX XX XXXX
XX
XX
XXXX
XXXX
XX
XXXX
XXXX
XXXX
XXXX
XXXX
XXXX
XXXX
XX

NUO-420-31-DG

Operating Mass Storage Devices 7–15

Operating the TLZ06 Tape Drive

Operating the TLZ06 Tape Drive
TLZ06
Description

The TLZ06 tape drive stores information on removable tape
cartridges that can hold up to 4 gigabytes per tape cartridge.
Figure 7–4 shows the components of the TLZ06.

! Tape/activity light
" Write-protect light
# Tape cassette slot
$ Tape unload button
% DDS tape

Up to two TLZ06 drives (one if an RRD42 drive is present) can
be located in the bottom tray.

Compatible
Tapes

Digital recommends that you use DDS certified tapes.

7–16 Operating Mass Storage Devices

Operating the TLZ06 Tape Drive

Figure 7–4 TLZ06 Drive and Compatible Tape

D
D ig
S at ita
to a l
ra
g
e

NUO-420-32-DG

Operating Mass Storage Devices 7–17

Operating the TLZ06 Tape Drive

Inserting a Tape
into the TLZ06

To insert the DDS tape into the TLZ06 (Figure 7–5):
1. Check to see that the tape/activity light on the drive is unlit.
If it is lit, there is already a tape in the drive. Remove the
tape from the drive before continuing. (See Removing a Tape
from the TLZ06, below.)
2. Set the write-protect switch on the DDS tape that you wish
or write-enabled
to insert to either the write-protected
position.

3. Insert the DDS tape into the drive, with the tape oriented as
shown in .

Removing a
Tape from the
TLZ06

To remove a DDS tape from the TLZ06 (Figure 7–5):
1. Check to see that the tape/activity light is on solid green. If
the tape/activity light is flashing, the drive has not finished
completing a data transfer. Wait until the tape/activity light
comes on solid green before proceeding.
2. Press the unload button to eject the tape
The tape ejects part way.
3. Remove the tape from the drive

7–18 Operating Mass Storage Devices

Operating the TLZ06 Tape Drive

Figure 7–5 Inserting and Removing a Tape: TLZ06

Digital
Dat
Sto
a
rag
e

5
4
NUO-420-33-DG

Operating Mass Storage Devices 7–19

Operating the TLZ06 Tape Drive

TLZ06 Lights

Table 7–3 summarizes the conditions indicated by the TLZ06
lights.
Table 7–3 TLZ06 Light Summary
Write-Protect
Light

Tape/Activity Light

Condition

Off

No tape loaded

Off

Green

Tape loaded and
write-enabled

Off

Blinking green

Busy

Amber

Green

Tape loaded and
write-protected.
No SCSI drive
activity

Amber

Blinking green

SCSI drive
activity

Off to amber

Blinking green. Goes to
solid green when done.
Indicates drive activity.

Load sequence

Amber goes off

Blinking green. Goes to
off when done. Indicates
drive activity.

Unload sequence

Amber 1–2
seconds, then
off

Green for 1–2 seconds.
Green blinking for
remainder of poweron self-test (POST).
When POST successfully
completed, normal
indications.1

Power-on/ reset
sequence

Amber

Blinking green until
test completes (1–4
minutes). When test
successfully completed,
normal indications.1

POST:Self-test:lvl
1 (basic self-test)
and Lvl 2
(extended selftest)

1 Normal indications: Both lights off when tape is not inserted.

Both lights on when tape is inserted and write-protected.
Amber off and green on when tape is loaded and write-enabled.

(continued on next page)

7–20 Operating Mass Storage Devices

Operating the TLZ06 Tape Drive

Table 7–3 (Cont.) TLZ06 Light Summary
Write-Protect
Light

Tape/Activity Light

Condition

Blinking
amber

Blinking green. Test
failure.

Drive fault.

Operating the TZ30 Tape Drive
TZ30
Description

The TZ30 cartridge tape drive stores information on removable
tape cartridges that can hold up to 95 megabytes per tape
cartridge. Figure 7–6 shows the components of the TZ30.
Up to two TZ30 drives (one if an RRD42 drive is present) can be
located in the removable-media mass storage compartment.

Compatible
Tapes

The TZ30 can use CompacTape and CompacTape II cartridges
that:
•

Have not been written to.

•

Have been written to by a TZ30 or a TK50 tape drive.

The TZ30 tape drive cannot use:
•

A CompacTape III cartridge.

•

Any tape that has been written to by a TK70 tape drive.

Operating Mass Storage Devices 7–21

Operating the TZ30 Tape Drive

! Write Protect light (orange)
" Tape in Use light (yellow)
# Operate Lever light (green)
$ Unload button
% Drive lever
& CompacTape slot
' CompacTape cartridge
Caution
Do not push a tape cartridge into the TZ30 while
moving the cartridge lever between the lock and
unlock positions. Doing so can damage the drive.

7–22 Operating Mass Storage Devices

Operating the TZ30 Tape Drive

Figure 7–6 TZ30 Tape Drive and Compatible Tape

1
2
3
Write
Protect
Tape in Use
Operate
Lever

Unload

NUO-420-34-DG

Operating Mass Storage Devices 7–23

Operating the TZ30 Tape Drive

Inserting a Tape
into the TZ30

To insert the TZ30 tape into the drive (Figure 7–7):
1. If the cartridge lever on the drive is in the lock position,
move the lever to the unlock position .

2. Set the Write Protect switch on the tape cartridge to either
the write-protected
or write-enabled
position.

3. Insert the tape cartridge

The green light comes on.
Once you have inserted the cartridge more than halfway into
the drive, you must complete this procedure. If you wish
to use another cartridge, complete this procedure and then
perform the unload procedure to remove the tape.
If you encounter resistance when attempting to insert the
tape cartridge into the TZ30, remove the tape from the drive
and move the cartridge lever to the lock position. Now move
the cartridge lever back to the unlock position and reinsert
the cartridge.
4. Move the cartridge lever to the lock position
the tape cartridge into the drive.

%, which locks

The green light goes off and the yellow light begins to blink,
which indicates that the tape is loading. When the tape is
loaded (ready for use), the yellow light remains on and the
green light remains off.

7–24 Operating Mass Storage Devices

Operating the TZ30 Tape Drive

Figure 7–7 Inserting a Tape into the TZ30

108%

Write
Protect
Tape in Use
Operate
Lever

Unload

108%

Write
Protect
Tape in Use

30%

Operate
Lever

Unload

4
2
108%

Write
Protect
Tape in Use
Operate
Lever

Unload

3
5

NUO-420-35-DG

Operating Mass Storage Devices 7–25

Operating the TZ30 Tape Drive

Remove
Tapes Before
Power-Down

Removing a
Tape from the
TZ30

Caution
Remove tape cartridges from the TZ30 before
turning off power to the drive or the system.
Failure to do so can damage the cartridge and tape
drive.

To remove a tape from the TZ30 drive (Figure 7–8):
1. Press the Unload button

The yellow light flashes while the tape rewinds. Wait for the
tape to rewind fully: The beeper will sound twice and the
green light will come on.
2. Move the cartridge lever to the unlock position
The cartridge ejects.
3. Remove the tape from the drive

7–26 Operating Mass Storage Devices

Operating the TZ30 Tape Drive

Figure 7–8 Removing a Tape from the TZ30

108%

Write
Protect
Tape in Use
Operate
Lever

Unload

108%

Write
Protect
Tape in Use
Operate
Lever

Unload

108%

Write
Protect
Tape in Use

30%

Operate
Lever

Unload

3
NUO-420-36-DG

Operating Mass Storage Devices 7–27

Operating the TZ30 Tape Drive

TZ30 Lights

Table 7–4 summarizes the conditions indicated by the TZ30
lights.
Table 7–4 TZ30 Light Summary
Light

State

Condition

Green

Okay to operate the
cartridge lever.

Off

Do not operate the
cartridge lever.

Blinking

The drive detected
a cartridge or
calibration error.

Blinking fast
intermittently

Data is being written
to the tape.

Blinking fast
continuously

Data is being read
from the tape.

Blinking slowly

Tape is initializing,
loading, unloading, or
rewinding.

Blinking slowly,
after the power-up
diagnostic has run

Tape is initializing.

Tape is loaded and
ready for use.

Tape is writeprotected.

Off

Tape is write-enabled.

The power-up
diagnostic is in
progress.

Blinking

Drive fault has
occurred.

Yellow

Orange

All three lights

7–28 Operating Mass Storage Devices

Maintaining Mass Storage Media and Devices

Maintaining Mass Storage Media and Devices
Task Overview

Selecting a
Media Write
Setting

Several tasks go hand-in-hand with using mass storage devices:
•

Write-enabling and write-protecting media

•

Labeling removable media

•

Handling the media according to its care instructions

•

Cleaning the device

Mass storage media that can be read from or written to. For
example, a TLZ06 removable tape has a write-protect feature
that allows you to enable data to be written onto the media
(write-enable) or to prevent data from being written onto the
media and overwriting existing data (write-protect).
Switch the media setting back and forth, depending on the
operation you wish to perform.

For More
Information

Media Setting

Operation

Write-enabled

Write data onto the media.

Write-protected

Protect data that has been written
to the media from being accidentally
overwritten.

For information about setting the write-protect feature on a
specific device, refer to the section on that device in this chapter.

Operating Mass Storage Devices 7–29

Maintaining Mass Storage Media and Devices

Labeling
Removable
Media

Once you copy information onto removable media, label the
contents of the media with the labels provided in the media’s
packaging.
Each type of tape has a label position, usually indicated by an
indentation in the media. Affix labels only onto the designated
label position. Figure 7–9 shows where to place a label on a
CompacTape ( ) and on a DSS tape ( ).

Figure 7–9 Affixing Labels

D
D ig
S at ita
to a l
ra
g
e

Digital
Data
Storage

MLO-009226

Handling Media

Handle cassette tapes and compact discs carefully. The following
sections provide care and handling instructions for cassette tapes
and compact discs.
Note
Over ninety percent of drive-related problems
are associated with the media. Therefore, Digital
strongly recommends that you follow the mass
storage care and handling instructions described
in the following sections.

7–30 Operating Mass Storage Devices

Maintaining Mass Storage Media and Devices

Handling and
Storing Discs
and Caddies

Handle and store RRD42 discs and caddies as follows:
•

Do not drop or strike the disc or the caddy.

•

Do not disassemble the caddy.

•

Store discs and caddies away from dust.

•

Keep discs and caddies out of direct sunlight and away from
heaters and other heat sources. Store discs and caddies at
a constant temperature between 10°C and 40°C (50°F and
104°F), and where the relative humidity is between 10% and
90%.

•

Do not touch the surface of a disc. Handle a disc by its edges.

•

Wipe a disc with a compact disc cleaner when dust or
fingerprints contaminate its surface.

•

Never manually open the caddy shutter, shown in
Figure 7–10, or touch the disc. The caddy shutter opens
automatically when you insert the caddy into the drive.

Figure 7–10 Caddy Shutter

MLO-007517

Operating Mass Storage Devices 7–31

Maintaining Mass Storage Media and Devices

Handling and
Storing Tapes

Cartridge tapes, used by all tape drives, store information on
the magnetic surface of the tape. Do not touch these exposed
magnetic surfaces.
If the tape leader is not in the correct position, do not try to fix
it. Use a new cartridge instead.
Handle and store tape cartridges as follows:

Cleaning the
TLZ06

•

Keep tapes dry.

•

Avoid dropping or banging the cartridge, which can displace
the drive leader and make the tape unusable.

•

Store tapes in moderate temperatures of between 10°C and
40°C (50° and 104°F).

•

If a tape cartridge has been exposed to extreme heat or cold,
allow the tape to stabilize at room temperature for the same
amount of time it was exposed—up to 24 hours.

•

Keep tapes out of direct sunlight and away from sources of
heat.

•

Keep tapes away from anything that contains a magnet or a
magnetic field, such as a telephone or a computer monitor.
Any tape exposed to a magnetic field can lose information.

•

Store tapes in a dust-free area where the relative humidity is
between 20% and 80%.

•

Place an identification label only in the space provided for
the label.

This section shows you how to perform TLZ06 head cleaning.
The heads are the components in a drive that physically read
and write data to and from the media (in this case, a cassette
tape).
Digital recommends that you perform the head cleaning
procedure about every 2 weeks, or after every 50 hours of drive
usage.
Under normal conditions, it should not be necessary to exceed
this cleaning schedule. If a particular data cassette causes
problems, try changing to another data cassette.

7–32 Operating Mass Storage Devices

Maintaining Mass Storage Media and Devices

Caution
Never attempt to clean the heads in a manner
other than described here. Doing so may damage
the drive tape head.

To clean the heads, use the head cleaning cassette as follows:
1. Make sure the power switch is in the on position ( | ) to apply
power to the drive.
2. Insert the head cleaning cassette (part number TLZ04–HA)
into the drive.
3. With the head cleaning cassette inserted, the drive
automatically executes head cleaning. The drive ejects
the head cleaning cassette after approximately 30 seconds.
4. In the space provided on the card enclosed with the head
cleaning cassette, place a check mark every time you use the
head cleaning cassette.
Under normal conditions, the head cleaning cassette is good
for approximately 25 cleanings. Additional cassettes are
available from your Digital sales representative or DECdirect
(800-DIGITAL).
If the head cleaning cassette has been used more than 25
times, both the tape/activity and write-protect lights will
flash. Press the eject button to remove the cleaning cassette.
No cleaning action will have occurred.

Cleaning the
TZ30

Clean the drive head as follows:
1. Insert the CleaningTape into the TZ30 using the instructions
in Inserting a Tape into the TZ30 in this chapter.
When cleaning is complete, the beeper sounds for you to
remove the CleaningTape.
2. The drive head has been cleaned if the Use Cleaning Tape
light goes off after the beeper sounds.
If the Use Cleaning Tape light remains on after the beeper
sounds, the drive head has not been cleaned and the
cartridge has expired. Replace the cleaning cartridge. (The
CleaningTape expires after approximately 20 uses.)

Operating Mass Storage Devices 7–33

References

References
The following table describes where to find additional
information about DEC 4000 AXP Rackmount mass storage
devices.
Task

Document

Obtain a list of all DEC 4000
AXP Rackmount–compatible
devices

Systems and Options Catalog

Write data to or from a drive
•

In OpenVMS AXP, refer to
OpenVMS System Manager’s
Manual.

•

In DEC OSF/1 AXP, refer to
DEC OSF/1 AXP Guide to
System Administration.

•

In OpenVMS AXP, refer to
OpenVMS System Manager’s
Manual.

•

In DEC OSF/1 AXP, refer to
DEC OSF/1 AXP Guide to
System Administration.

Mount a device

7–34 Operating Mass Storage Devices

8
System Configuration
Chapter Description
Introduction

This chapter describes your system configuration and explains
how to plan changes in the configuration.
Your system configuration is defined by the modules and mass
storage devices inside your system, as well as the external
options to which your system is connected. Your system
configuration also includes the type of operating environment
and applications.

In This Chapter

This chapter covers the following information:
•

Identifying Your Configuration

•

Special Configurations

•

Identifying System Options

•

Identifying Mass Storage Devices

•

Displaying Configuration Information Online

•

Planning a Change to Your Configuration

•

Connecting Additional Devices to Your System

•

Changing Drive ID Numbers (External Media)

•

Setting and Examining Parameters for DSSI Devices

•

Using the Power Control Bus with a Storage Expander

System Configuration

8–1

Identifying Your Configuration

Identifying Your Configuration
Overview

Types of
Configurations

You may need to know your system configuration in the following
situations:
•

When assigning an identification number to a device

•

When ordering additional equipment

•

When connecting to a network

Figure 8–1 illustrates the most common DEC 4000 AXP
Rackmount configurations:
•

Standalone system

! with or without external mass storage

A standalone system is not connected to any other systems
or to a network. It can connect to multiple user terminals.
•

Clustered system

" (OpenVMS AXP systems only)

Two systems are connected. Total compute power is double
the power of one system.
•

Single-node system

# connected to a network

A single system is connected to a network of systems.
•

Clustered networked system
only)

$ (OpenVMS AXP systems

Two systems are connected to each other and to a network of
systems.

8–2 System Configuration

Identifying Your Configuration

Figure 8–1 Types of Configurations

Ethernet

NUO-420-37-DG

System Configuration

8–3

Special Configurations

Special Configurations
Overview

The following special configurations create a unique system
environment:
•

Dual CPU systems

•

DSSI VMScluster

Dual CPU
Systems

A second CPU can be added to any DEC 4000 AXP Rackmount
system. Adding a second CPU approximately doubles the
computing power of the original system.

DSSI
VMSCluster

A DSSI VMScluster configuration consists of two or more
systems, running VMS software, configured as a DSSI cluster
sharing their DSSI devices through a bus. Each system can have
direct access to any of the devices on a shared DSSI bus; this can
include a shared common disk.
The simplest DSSI VMScluster configuration, a two-system DSSI
VMScluster, for example, can allow one system disk to be used
as the system disk for both systems. The system disk physically
resides in one enclosure; however, both systems have equal
access to the system disk and to any other DSSI mass storage
device in either enclosure.
A DSSI device, such as the RF73, has a built-in DSSI
VMScluster capability that allows it to serve two or more
systems simultaneously. The SCSI to DSSI adapters provided
with systems having DSSI I/O modules allow you to extend a
DSSI bus by physically connecting it to another system.

8–4 System Configuration

Special Configurations

Benefits
of a DSSI
VMScluster

The benefits of a DSSI VMScluster configuration are:
•

Cluster features such as shared data across systems and
satellite nodes.

•

High system availability. If one of the systems is unavailable,
for example, due to a system malfunction, the satellites
booted through it are able to continue operating through the
other system.

If one of the systems fails, all satellite nodes booted through that
system lose connections to the system disk. Each satellite node,
however, can access the system disk through a second path. The
satellite nodes establish a new connection through the other
system and continue operation.
To increase system availability, a second system disk may be
added to each boot node. If one system disk fails, the remaining
system disk would continue to service one system and the
satellite nodes booted through it.

System Configuration

8–5

Identifying System Options

Identifying System Options
Specifics
of Your
Configuration

In addition to your configuration type, your system configuration
includes the following:
•

System modules

•

Mass storage devices

•

External mass storage devices that are connected to the
system (optional)

•

Network components (optional)

The number and type of system modules, mass storage
devices, and network components in your system depend on
the configuration you have selected.

System
Modules

The card cage at the rear of the system holds system modules.
Your system includes a combination of the following:
•

Up to two CPU modules

•

One I/O module

•

Up to four memory modules

•

Up to six Futurebus+ modules

You can determine the number and type of modules in your
system by reading the label that runs lengthwise on each
module.

Internal Mass
Storage
Devices

Internal mass storage devices are located in the tray at the
bottom of your system.
For information about how to identify the devices in your system,
refer to Identifying Mass Storage Devices .
The DEC 4000 AXP Rackmount does not require the device
mounting brackets included with internal disk and tape options.
These may be discarded. Mounting brackets are provided in the
bottom tray of the DEC 4000 AXP Rackmount.

8–6 System Configuration

Identifying System Options

External
Mass Storage
Devices

Your system can support devices that are outside the system
unit (external devices) in addition to the devices that are in
the system. External devices can sit or stand alone beside your
system, or they can be housed in a separate enclosure, such as
the R400X mass storage expander.
For a list of the devices that can be connected to your system,
refer to the Systems and Options Catalog, or contact your Digital
sales representative.
For information about how to connect an external mass storage
device to your system, refer to Connecting Additional Devices to
Your System , later in this chapter.

Network
Devices

Depending on the configuration you selected, your system comes
with one or two Ethernet ports on the I/O module.
Each Ethernet port has two associated ports: thickwire
(standard Ethernet) and ThinWire. You select either thickwire
or ThinWire with a switch that is located halfway between
the thickwire and the ThinWire ports. You can connect to a
twisted-pair Ethernet by connecting a twisted-pair H3350 media
access unit to the thickwire port, using a standard transceiver
cable.

Identifying Mass Storage Devices
DSSI and SCSI
Devices

In addition to the SCSI devices in the bottom tray, both DSSI
and SCSI mass storage devices can be connected to your system
via connectors at the rear of the chassis. The devices from
a single connector, however, are either SCSI devices or DSSI
devices. Refer to Connecting Additional Devices to Your System
later in this chapter.

System Configuration

8–7

Displaying Configuration Information Online

Displaying Configuration Information Online
Overview

You can examine information about your system configuration on
line from console mode by entering a command at your console
terminal. The system responds by displaying information about
the topic that you specify.
You can display information about the following topics:
•

System configuration

•

Memory

•

Mass storage devices

•

Console program

•

Privileged Architecture Library code (PALcode)

If a configuration screen does not show what you expect or what
you ordered, there may be a problem with your system. Contact
your Digital representative.

Displaying
System
Configuration

To display system configuration information from console mode,
enter show config at the console prompt:
>>> show config
Your system configuration is displayed on the terminal screen.
Example 8–1 shows a possible system configuration display.

8–8 System Configuration

Displaying Configuration Information Online

Example 8–1 System Configuration Display
>>> show config

Return

Console T2.4-2859

VMS PALcode X5.12F, OSF PALcode X1.09B

CPU 0
CPU 1
Memory 0
Memory 1
Memory 2
Memory 3
Ethernet 0
Ethernet 1

P
P
P
P

B2001-AA DECchip (tm) 21064-2

A
SCSI
B
C
DSSI
D
SCSI
E
SCSI
Futurebus+

P
P
P
P
P
P

System Status Pass

B2002-DA 128 MB

08-00-2B-1D-02-8F
08-00-2B-1D-02-90
ID 0

ID 1

ID 2
RZ57

RZ35

RF72
RZ35
TLZ04
-

ID 3

ID 4

ID 5

ID 6

Host
Host
Host

RZ35
-

ID 7
Host

Type b to boot

>>>

! Module, network component, or mass storage bus label
" Component’s status after last self-test: either ‘‘P’’ for pass or
‘‘F’’ for fail.

# Description of the component: describes modules, provides
Ethernet addresses, and lists the devices on each mass
storage bus.

System Configuration

8–9

Displaying Configuration Information Online

Displaying
Memory
Information

To display memory information from console mode, enter show

memory at the console prompt.
>>> show memory
Your system memory is displayed on the terminal screen.
Example 8–2 shows a possible memory configuration display.
Example 8–2 Memory Configuration Display
>>> show memory
>>>show memory

Module
-----0
1
2
3

Return

Size
Base Addr
----- --------Not Installed
Not Installed
Not Installed
128Mb 00000000

Intlv Mode Intlv Unit Bad Pages
---------- ---------- ---------

1-Way

>>>

! Module slot number
" Size of memory module
# Base or starting address of memory module
$ Interleave mode—number of modules interleaved (1–4-way
interleaving)

% Interleave unit number
& Number of bad pages in memory (8 K/page)

8–10 System Configuration

Displaying Configuration Information Online

Displaying
Device
Information

To display device information from console mode, enter show

device at the console prompt.
>>> show device
Your device configuration is displayed on the terminal screen.
Example 8–3 shows a possible device configuration display.
Example 8–3 Device Configuration Display
>>> show device
dka200.2.0.0.0
dkd0.0.0.3.0
dkd100.1.0.3.0
dkd300.3.0.3.0
duc1.1.0.2.0
mke100.1.0.4.0
eza0.0.0.6.0
ezb0.0.0.7.0
p_b0.6.0.1.0
pka0.7.0.0.0
pkd0.7.0.3.0
pke0.7.0.4.0
puc0.7.0.2.0
>>>

Return

DKA200
RZ57
DKD0
RZ35
DKD100
RZ35
DKD300
RZ35
$1$DIA1 (RF0201)
RF72
MKE100
TLZ04
EZA0
08-00-2B-1D-02-8F
EZB0
08-00-2B-1D-02-90
Bus ID 6
PKA0
SCSI Bus ID 7
PKD0
SCSI Bus ID 7
PKE0
SCSI Bus ID 7
PIC0
DSSI Bus ID 7

Note
If no devices or terminators are present for
a SCSI-2/DSSI bus, the display will show an
indeterminant device type for that controller, such
as p_a0 or p_b0.

System Configuration

8–11

Displaying Configuration Information Online

The device naming convention is shown in Figure 8–2.
Figure 8–2 Device Name Convention

dka0.0.0.0.0
0 LBus; 1 Futurebus+
0-4 SCSI/DSSI; 6, 7 Ethernet; 2-13 Futurebus+ nodes
Used for multi-channel devices.
Bus Node ID (from bus node ID plug)
Unique device unit number (MSCP Unit Number)
For Futurebus+ modules, node number, 0 or 1
Storage Adapter ID: One-letter storage adapter designator (A,B,C,D, or E)
For Futurebus+ modules, A--F, corresponding
to Futurebus+ adapter slots 1--6
Driver ID: Two-letter port or class driver designator
EZ - Ethernet port
PU - DSSI port, DU - DSSI disk, MU-DSSI tape
PK - SCSI port, DK - SCSI disk, MK-SCSI tape
FB - Futurebus+ port

Bus Number:
Slot Number:
Channel Number:
Bus Node Number:
Device Unit Number:

LJ-02061-TI0

Note
Slot numbers for SCSI-2/DSSI buses (0–4)
correspond to mass storage buses as follows:
External Media:
Bus A, Slot 0
Bus B, Slot 1
Bus C, Slot 2
Bus D, Slot 3
Internal/External SCSI Media:
Bus E, Slot 4

8–12 System Configuration

Displaying Configuration Information Online

Displaying
Console
Program
Version

To display the version of the console program that you are using,
enter show version at the console prompt.
>>> show version
The version of the console program that your system is using is
displayed on the terminal screen. Example 8–4 shows a possible
console program version.
Example 8–4 Console Program Version
>>> show version
version

Displaying
PALcode
Version

Return

T2.1-213 Jul 28 1992 01:01:25

Privileged Architecture Library code, (PALcode) written for AXP
processors, implements architecturally defined behavior.
To display the version of PALcode that you are using, enter show
pal at the console prompt:
>>> show pal
The version of PALcode that your system is using is displayed
on the terminal screen. Example 8–5 shows a possible PALcode
version.
Example 8–5 PALcode Version
>>> show pal
pal

Return

VMS PALcode X5.04A, OSF PALcode X1.04A

System Configuration

8–13

Planning a Change to Your Configuration

Planning a Change to Your Configuration
Perform
Pre-Upgrade
Tasks

Although the replacement or addition of system hardware is
generally performed by Digital Services, you should plan an
upgrade by performing the following tasks:
1. Discuss with your sales representative how you wish to
change your system: the options you wish to add and
whether they are compatible with your system.
2. Obtain a copy of the Systems and Options Catalog from your
Digital sales representative and fill out the DEC 4000 AXP
Rackmount configuration worksheet that can be found in the
catalog.
3. Order the options and arrange for Digital Services to install
them.
For information about current products, refer to Digital’s latest
Systems and Options Catalog. To obtain a copy, contact your
Digital sales representative.

8–14 System Configuration

Planning a Change to Your Configuration

Adding
Third-Party
Devices

You can connect third-party SCSI, or licensed DSSI devices
to the system by extending one of the system’s mass storage
buses. See Terminating and Extending a DSSI Bus, later in this
chapter.

System Configuration

8–15

Connecting Additional Devices to Your System

Connecting Additional Devices to Your System
External Media
Expansion
Ports

External media expansion ports on the rear of the chassis enable
you to extend the bus that is connected to that port outside
the system. As a result, you can connect external mass storage
devices, either standalone devices or devices in an expander, such
as the R400X, to the buses inside your system. Note, however,
that you can only connect DSSI devices to a DSSI bus and only
SCSI devices to a SCSI bus.
Figure 8–3 shows the location of the bus expansion ports on the
DEC 4000 AXP Rackmount system.

DSSI/SCSI
Ports

Each expansion port is accessed via a SCSI 50-pin IEEE
connector. The port in this configuration is intended to connect
to single-ended SCSI devices only. Terminator power is provided
by the port on the appropriate pins.
To connect a DSSI bus, attach one of the supplied SCSI/DSSI
adapters (P/N 12-39838-01) to the desired port. The 50-pin
D connector end of the plug is configured in a DSSI pinout
scheme, which can be attached to external DSSI devices. The
adapter flags the processor that the port is to be utilized as
a DSSI device. However, this only occurs if the adapter is
attached before system initialization takes place. If the adapter
is attached after system power up, the port remains in a SCSI
configuration. Each bus can support up to seven devices using
ports A through D.

Extending the
Internal Bus
(SCSI Only)

The internal storage compartment can hold up to four mass
storage devices, however, the bus supports up to seven mass
storage devices.
Additional devices can be attached to this bus by extending port
E (see Figure 8–3) to the desired external media.

8–16 System Configuration

Connecting Additional Devices to Your System

Figure 8–3 Mass Storage Bus Expansion Ports

5
1

NUO-420-38-DG

! Bus A expansion port
" Bus B expansion port
# Bus C expansion port
$ Bus D expansion port
% Bus E expansion port1

Bus E expansion port is for SCSI use only.

System Configuration

8–17

Connecting Additional Devices to Your System

Terminating
and Extending
a SCSI Bus

To extend a SCSI bus, you attach a SCSI bus expansion cable to
the bus expansion port and attach the other end of the cable into
the external SCSI device.
Terminate any unused ports by attaching an H8574-A SCSI
terminator (P/N 12-30552-01) to the bus expansion port.

Terminating
and Extending
a DSSI Bus

To extend a DSSI bus, first you attach the SCSI/DSSI adapter
(P/N 12-39838-01) described in DSSI/SCSI Ports. Then you
attach a DSSI bus expansion cable to the bus expansion port and
attach the other end of the cable into the external DSSI device.

Example of
Terminating
and Extending
a Bus

Figure 8–4 shows a system with SCSI terminators and extended
DSSI and SCSI buses.
•

Bus A, in the example, is a DSSI bus.
Extend a DSSI bus by attaching a SCSI/DSSI adapter (P/N
12-39838-01), then a DSSI expansion cable
into the bus
expansion port.

•

Bus E, in the example, is a SCSI bus.
Terminate a SCSI bus by attaching a SCSI terminator
into the bus expansion port.

Extend a SCSI bus by attaching a SCSI expansion cable
into the bus expansion port.

You can terminate a DSSI bus by removing the SCSI/DSSI
adapter and using the SCSI terminator as shown in Figure 8–4.
You can also terminate the DSSI bus by attaching a DSSI
terminator to the SCSI/DSSI adapter (not shown in figure).

Terminating an
Extended Bus

Always terminate a bus. If you extend a bus, move the
terminator (either DSSI or SCSI to match the bus) from the
bus expansion port on the system to the bus expansion port or
connector on the expansion enclosure or standalone device.
For information about attaching a terminator to an R400X
expander, refer to the R400X Expander Installation (EK–R400X–
CM).

8–18 System Configuration

Connecting Additional Devices to Your System

Figure 8–4 Terminating and Extending a Bus

NUO-420-39-DG

System Configuration

8–19

Changing Drive ID Numbers (External Media)

Changing Drive ID Numbers (External Media)
When to
Change Drive
ID Numbers

Refer to your external media documentation for instructions on
when and how to set ID numbers.
Note
If you cluster two or more DSSI systems, you may
need to set DSSI parameters instead of changing
drive ID numbers. For information about setting
DSSI parameters, refer to Setting and Examining
Parameters for DSSI Devices later in this chapter.

Changing a
Drive ID: Rules

Use the following rules to decide how to renumber your storage
devices:
•

For each bus, do not duplicate drive ID numbers for storage
devices/adapters. For Bus A, you can have only one storage
device identified as drive 0, one storage device as drive 1,
and so on; for Bus B, you can have only one storage device
identified as drive 0, one storage device as drive 1, and so on.

•

By convention, the fixed-disk drives are numbered in
increasing order from right to left, beginning with zero.

•

Adapters use the highest available drive ID numbers.

•

The controller ID number is 7.
Note
External media must have only one terminator
located at the end of the bus. Ensure terminator
resistor paks are removed from any drives located
at intermediate points on a multidrive string. If
an external terminator is used, remove all resistor
paks.

8–20 System Configuration

Setting and Examining Parameters for DSSI Devices

Setting and Examining Parameters for DSSI Devices
When to
Change
DSSI Device
Parameters

Changing
DSSI Device
Parameters:
Rules

Using cdp and
show device du
pu Commands

You may need to change DSSI device parameters under the
following circumstances:
•

If you reconfigure your system to include DSSI devices in an
expander

•

If you create a DSSI VMScluster configuration

Use the following rules to decide how to renumber your DSSI
storage devices:
•

For each DSSI bus, do not duplicate drive ID numbers for
storage devices/adapters. For Bus A, you can have only one
storage device identified as drive 0, one storage device as
drive 1, and so on; for Bus B, you can have only one storage
device identified as drive 0, one storage device as drive 1,
and so on. (See the previous section, Changing Drive ID
Numbers (External Media) , for information about changing
a drive’s ID number.)

•

When more than one DSSI bus is being used and the system
is using a nonzero allocation class, you need to assign new
MSCP unit numbers for devices on all but one of the DSSI
buses. This is necessary because the unit numbers for all
DSSI devices connected to a system’s associated DSSI buses
must be unique.

You set and examine DSSI device parameters by using the show
device du pu and cdp console commands:
•

show device du pu — displays information for each DSSI
device on the system (du specifies drives, pu specifies storage
adapters).

•

cdp — allows you to modify the following device parameters
from console mode: NODENAME, ALLCLASS, and
UNITNUM. The cdp command automatically connects
to the device’s DUP driver for all devices or any number of
specified devices.

System Configuration

8–21

Setting and Examining Parameters for DSSI Devices

show device du
pu

The show device du pu command displays information for all
DSSI devices in the system. The du argument lists all DSSI
drives; the pu argument lists the storage adapters for all DSSI
buses found on the system.
Synopsis:

show device du pu
Example:
>>> show device du pu

dua0.0.0.0.0
dua1.1.0.0.0
dua2.2.0.0.0
dua3.3.0.0.0
pua0.7.0.0.0
pub0.7.0.1.0
>>>
dka0.0.0.0.0

$2$DIA0 (ALPHA0)
$2$DIA1 (ALPHA1)
$2$DIA2 (ALPHA2)
$2$DIA3 (ALPHA3)
PIA0
PIB0

RF35
RF35
RF35
RF35
DSSI Bus ID 7
DSSI Bus ID 7

! Console device name:

Bus Number:
Slot Number:
Channel Number:
Bus Node Number:
Device Unit Number:

0 LBus; 1 Futurebus+
0-4 SCSI/DSSI; 6, 7 Ethernet; 2-13 Futurebus+ nodes
Used for multi-channel devices.
Bus Node ID (from bus node ID plug)
Unique device unit number (MSCP Unit Number)
For Futurebus+ modules, node number, 0 or 1
Storage Adapter ID: One-letter storage adapter designator (A,B,C,D, or E)
For Futurebus+ modules, A--F, corresponding
to Futurebus+ adapter slots 1--6
Driver ID: Two-letter port or class driver designator
EZ - Ethernet port
PU - DSSI port, DU - DSSI disk, MU-DSSI tape
PK - SCSI port, DK - SCSI disk, MK-SCSI tape
FB - Futurebus+ port
LJ-02061-TI0

" Operating system device name:
•

For an allocation class of zero: NODENAME$DIAu
NODENAME is a unique node name and u is the unit
number. For example, R7BUCC$DIA0.

•

For a nonzero allocation class:
$ALLCLASS$DIAu

8–22 System Configuration

Setting and Examining Parameters for DSSI Devices

ALLCLASS is the allocation class for the system and
devices, and u is a unique unit number. For example,
$1$DIA0.

# Node name (alphanumeric, up to six characters)
$ Device type
cdp

The cdp command allows you to modify NODENAME,
ALLCLASS, and UNITNUM from the console program without
explicit connection to a node’s DUP server.
For more information about the cdp command, refer to cdp in
Chapter 5.

DSSI Device
Parameters:
Definitions and
Function

Five principal parameters are associated with each DSSI device:
•

Drive ID

•

ALLCLASS

•

UNITNUM

•

NODENAME

•

SYSTEMID
Note
ALLCLASS, NODENAME, and UNITNUM are
examined and modified using the cdp command.
SYSTEMID is examined and modified using the
console-based Diagnostic and Utility Program
(DUP) driver utility.
The drive ID is physically determined by the
numbered drive ID plug that inserts into the front
panel of the storage compartment.

A brief description of each parameter follows.

System Configuration

8–23

Setting and Examining Parameters for DSSI Devices

DSSI Device
Parameter
Descriptions

Drive ID
The drive ID parameter is provided by the drive ID plug on the
front panel of the external storage compartment if so equipped,
otherwise the ID parameter is set by jumpers on the individual
devices. See your documentation for the external storage media
for specific information. Each DSSI bus can support up to eight
devices, (drive IDs 0–7). Each DSSI adapter and each device
count as a node. Hence, in a single-system configuration, a DSSI
bus can support up to seven devices, drive IDs 0–6 (with drive
ID 7 reserved for the adapter).
ALLCLASS
The ALLCLASS parameter determines the device allocation
class. The allocation class is a numeric value from 0–255 that
is used by the OpenVMS AXP operating system to derive a
path-independent name for multiple access paths to the same
device. The ALLCLASS parameter corresponds to the OpenVMS
AXP IOGEN parameter ALLOCLASS.
DSSI devices are shipped from the factory with a default
allocation class of zero. Each device to be served to a cluster
must have a nonzero allocation class that matches the allocation
class of the system. Refer to the VMS VAXcluster Manual for
rules on specifying allocation class values.
UNITNUM
The UNITNUM parameter determines the unit number of the
device. By default, the device unit number is supplied by the
drive ID plug on the front panel of the storage compartment.
Systems using multiple DSSI buses, as described later in this
section, require that the default values be replaced with unique
unit numbers. To set unit numbers and override the default
values, you use the cdp console command to supply values to the
UNITNUM parameter.
NODENAME
The NODENAME parameter allows each device to have an
alphanumeric node name of up to six characters. DSSI devices
are shipped from the factory with a unique identifier, such as
R7CZZC, R7ALUC, and so on. You can provide your own node
name.

8–24 System Configuration

Setting and Examining Parameters for DSSI Devices

SYSTEMID
The SYSTEMID parameter provides a number that uniquely
identifies the device to the operating system.

How OpenVMS
AXP Uses the
DSSI Device
Parameters

This section describes how the OpenVMS AXP operating system
uses the parameters to form unique identifiers for each device.
Configurations that require you to assign new unit numbers for
devices are also described.
•

With an allocation class of zero, the operating system can
use the default parameter values to provide each device with
a unique device name. The operating system uses the node
name along with the device logical name in the following
manner:
NODENAME$DIAu
NODENAME is a unique node name and u is the unit
number.

•

With a nonzero allocation class, the operating system uses
unit number values to create a unique device name. The
operating system uses the allocation class along with the
device logical name in the following manner:
$ALLCLASS$DIAu
ALLCLASS is the allocation class for the system and devices,
and u is a unique unit number.

With DEC 4000 AXP Rackmount systems, you can fill multiple
DSSI buses: buses A–D (slot numbers 0–3). Each bus can have
up to seven DSSI devices (drive IDs 0–6). When more than one
bus is being used, and your system is using a nonzero allocation
class, you need to assign new unit numbers for devices on all
but one of the DSSI buses, since the unit numbers for all DSSI
storage devices connected to a system’s associated DSSI buses
must be unique.
Figure 8–5 illustrates the problem of duplicate operating system
device names for a system that is using more than one DSSI
bus and a nonzero allocation class. In the case of the nonzero
allocation class, the operating system sees four of the devices
as having duplicate device names. This is an error, as all unit
numbers must be unique. The unit numbers for one of the two
DSSI buses in this example need to be reprogrammed.

System Configuration

8–25

Setting and Examining Parameters for DSSI Devices

Figure 8–5 How OpenVMS AXP Sees Unit Numbers for DSSI Devices

Allocation Class=0

Nonzero Allocation Class
(Example: ALLCLASS=1)

R7BUCC$DIA0

$1$DIA0

R7CZZC$DIA1

$1$DIA1

R7ALUC$DIA2

$1$DIA2

R7EB3C$DIA3

$1$DIA3

R7IDFC$DIA0

$1$DIA0

R7IBZC$DIA1

$1$DIA1

R7IKJC$DIA2

$1$DIA2

R7ID3C$DIA3

$1$DIA3

R7XA4C$DIA4

$1$DIA4

R7QIYC$DIA5

$1$DIA5

R7DA4C$DIA6

$1$DIA6

* Duplicate 0
* Duplicate 1
* Duplicate 2
* Duplicate 3

* Nonzero allocation class examples with an asterisk indicate duplicate device names.

For one of the DSSI buses, the unit numbers need to be reprogrammed to avoid this error.
LJ-02063-TI0

Example:
Modifying
DSSI Device
Parameters

Figure 8–6 shows sample DSSI buses and drive IDs for a sample
expanded DEC 4000 AXP Rackmount system.
Following Figure 8–6 is an example in which the allocation class
will be set to 1, the devices for Bus A (in the DEC 4000 AXP
Rackmount) will be assigned new unit numbers (to avoid the
problem of duplicate unit numbers), and the system disk will be
assigned a new node name.

! System
" Expander

8–26 System Configuration

# Cable

Setting and Examining Parameters for DSSI Devices

Figure 8–6 Sample DSSI Buses for an Expanded DEC 4000
AXP Rackmount System

NUO-420-40-DG

System Configuration

8–27

Setting and Examining Parameters for DSSI Devices

In this part of the example, the system displays all DSSI devices.
>>> show device du pu
dua0.0.0.0.0
dua1.1.0.0.0
dua2.2.0.0.0
dua3.3.0.0.0
dub0.0.0.1.0
dub1.1.0.1.0
dub2.2.0.1.0
dub3.3.0.1.0
dub4.4.0.1.0
dub5.5.0.1.0
dub6.6.0.1.0
pua0.7.0.0.0
pub0.7.0.1.0

$2$DIA0 (ALPHA0)
$2$DIA1 (ALPHA1)
$2$DIA2 (ALPHA2)
$2$DIA3 (ALPHA3)
$2$DIA0 (SNEEZY)
$2$DIA1 (DOPEY)
$2$DIA2 (SLEEPY)
$2$DIA3 (GRUMPY)
$2$DIA4 (BASHFUL)
$2$DIA5 (HAPPY)
$2$DIA6 (DOC)
PIA0
PIB0

RF35
RF35
RF35
RF35
RF73
RF73
RF73
RF73
RF73
RF73
RF73
DSSI Bus ID 7
DSSI Bus ID 7

In the next part of the example, the system assigns ALLCLASS
of 1 to all drives in the system; assigns UNITNUM 10, 11, 12,
and 13 to the drives on Bus A.
>>> cdp -sa 1 -su 10 dua*
pua0.0.0.0.0
pua0.1.0.0.0
pua0.2.0.0.0
pua0.3.0.0.0
pub0.0.0.1.0
pub1.1.0.1.0
pub2.2.0.1.0
pub3.3.0.1.0
pub4.4.0.1.0
pub5.5.0.1.0
pub6.6.0.1.0

ALPHA0
ALPHA1
ALPHA2
ALPHA3
SNEEZY
DOPEY
SLEEPY
GRUMPY
BASHFL
HAPPY
DOC

0411214901371
0411214901506
041122A001625
0411214901286
0411214906794
0411214457623
0478512447890
0571292500565
0768443122700
0768443122259
0768442231111

1
1
1
1
1
1
1
1
1
1
1

10
11
12
13
0
1
2
3
4
5
6

$1$DIA10
$1$DIA11
$1$DIA12
$1$DIA13
$1$DIA0
$1$DIA1
$1$DIA2
$1$DIA3
$1$DIA4
$1$DIA5
$1$DIA6

In the next part of the example, the user modifies the
NODENAME for the specified drive.
>>> cdp -n dub0
pub0.0.0.1.0:
Node Name [SNEEZY]? SYSTEM
>>> show device du pu

8–28 System Configuration

Setting and Examining Parameters for DSSI Devices

dua10.0.0.0.0
dua11.1.0.0.0
dua12.2.0.0.0
dua13.3.0.0.0
dub0.0.0.1.0
dub1.1.0.1.0
dub2.2.0.1.0
dub3.3.0.1.0
dub4.4.0.1.0
dub5.5.0.1.0
dub6.6.0.1.0
pua0.7.0.0.0
pub0.7.0.1.0
>>>

$1$DIA10 (ALPHA0)
$1$DIA11 (ALPHA1)
$1$DIA12 (ALPHA2)
$2$DIA13 (ALPHA3)
$1$DIA0 (SYSTEM)
$1$DIA1 (DOPEY)
$1$DIA2 (SLEEPY)
$1$DIA3 (GRUMPY)
$1$DIA4 (BASHFL)
$1$DIA5 (HAPPY)
$1$DIA6 (DOC)
PIA0
PIB0

RF35
RF35
RF35
RF35
RF73
RF73
RF73
RF73
RF73
RF73
RF73
DSSI Bus ID 7
DSSI Bus ID 7

Using the Power Control Bus with a Storage Expander
Power Control
Bus for
Expanded
Systems

The three power bus connectors on the power system controller
at the top of the DEC 4000 AXP Rackmount system allow you
to configure a power bus for storage systems external to the
main chassis. The power bus allows you to turn power on and
off for one or more external storage systems through the power
supply designated as the main power supply. Figure 8–7 shows
a sample power bus configuration. Figure 1–7 shows the power
bus connector locations.
Note
DSSI VMScluster systems should not be configured
with a power bus. Inadvertently bringing down
the cluster defeats the added reliability of a DSSI
VMScluster.

System Configuration

8–29

Using the Power Control Bus with a Storage Expander

Figure 8–7 Sample Power Bus Configuration
System

Expander 1

Expander 2

MLO-009370

References
The following table describes where to find additional
configuration information.
Task

Document

Review available options

Systems and Options Catalog

Connect your system to the
network

Network Installation Guide

8–30 System Configuration

9
Learning More About Your System
Chapter Description
Introduction

This chapter describes your system’s design and the design of its
subsystems and components.

In This Chapter

This chapter covers the following information:
•

System Features

•

Subsystems and Components

•

CPU Subsystem

•

Power Subsystem

•

Storage Subsystem

•

Futurebus+ Subsystem

Learning More About Your System 9–1

System Features

System Features
What Makes It a
DEC 4000 AXP
Rackmount
System?

The following characteristics define the DEC 4000 AXP
Rackmount system:
•

Alpha AXP architecture

•

RISC technology

•

Support of multiple operating systems

•

Integration with VAX hardware and VMS and OSF/1
software and VAX investment protection

•

DSSI VMScluster support

•

19-inch EIA form factor

Alpha AXP
Architecture

The DEC 4000 AXP Rackmount system is part of a family of
flagship computers that are based on the new Alpha AXP system
architecture. Alpha AXP architecture employs the DECchip
21064 microprocessor, which is located on the CPU module
of each Alpha AXP system. The 21064 chip employs RISC
technology.

RISC
Technology

RISC (Reduced Instruction Set Computer) technology uses
an instruction set that is reduced in complexity. High-level
compilers synthesize the more complex, least frequently used
instructions by breaking them down into simpler instructions.
This approach allows the RISC architecture to implement a
small, hardware-assisted instruction set, thus eliminating the
need for microcode.
The Alpha AXP RISC technology provides exceptionally fast
compute power to the DEC 4000 AXP Rackmount system.

9–2 Learning More About Your System

System Features

Support
of Multiple
Operating
Systems

Currently, the DEC 4000 AXP Rackmount can run two different
operating systems:
•

OpenVMS AXP

•

DEC OSF/1 AXP

The NT AXP operating system and other operating systems are
planned to be supported in the future.

Integration
with Existing
Technology

The DEC 4000 AXP Rackmount system is designed to be
compatible with existing technology:
•

VAX hardware
DEC 4000 AXP Rackmount, like all Alpha AXP systems,
can connect to your existing VAX hardware in clusters and
networks.

•

VMS and UNIX software environments
By upgrading the operating system software, existing
versions of VMS or OSF/1 can support any Alpha AXP
system.

DSSI
VMScluster
Support

Learning More About Your System 9–3

Subsystems and Components

Subsystems and Components
Overview

The subsystems that make up the DEC 4000 AXP Rackmount
system are described in Table 9–1 and shown in Figure 9–1.
Table 9–1 DEC 4000 AXP Rackmount Subsystems
Subsystem

Features

System bus

Supports:
•

Up to two CPU modules

•

Up to four memory modules. Each module
can provide 64, or 128 MB of memory.

•

One I/O module

Power
subsystem

Supports 20-ampere systems, providing up to
1480 watts

I/O Module

Supports:

Futurebus+

9–4 Learning More About Your System

•

Two fixed-media SCSI devices

•

Two internal removable-media SCSI devices

•

Up to 35 drives total (includes fixed and
removable), 31 external devices

Industry-standard high-performance bus

Subsystems and Components

Figure 9–1 DEC 4000 AXP Rackmount System Architecture
Power Subsystem
Front
End
Unit

Power
System
Contr

To Outlet
DC5

DC3

Serial Control Bus
Memory 3
Memory 2
CPU 1

Memory 0
64, 128 MB

CPU 0

Operator
Control
Panel

Memory 1

System Bus
Serial Control Bus

DSSI/SCSI Bus A

Ethernet Port 0

DSSI/SCSI Bus B

Ethernet Port 1
di gi t al

SCHOLAR
Plus

Data
T alk

T est
Loop

Off
On

SD RD CD T R SI

Con sole
Ter min al

I/O
Module

Asynchronous Serial Line
(with modem control)

DSSI/SCSI Bus C
DSSI/SCSI Bus D
SCSI Only Bus E
(Removable Media)

Asynchronous Serial Line
(Console Line)

Futurebus+

Futurebus+ Option 6
Futurebus+ Option 5
Futurebus+ Option 4
Futurebus+ Option 3
Futurebus+ Option 2
Futurebus+ Option 1
Indicates Optional

MLO-009365

Learning More About Your System 9–5

CPU Subsystem

CPU Subsystem
Components

System Bus

The CPU subsystem consists of the following components:
•

System bus

•

Central processing units (1 or 2)

•

Memory modules (1 to 4)

•

I/O module

The system bus interconnects the CPUs, memory modules,
and I/O module. The I/O module provides access to basic I/O
functions (network, storage devices, and console program).
The I/O module also is the bridge to the I/O expansion bus,
Futurebus+.
The system bus is a shared-memory bus designed to support the
Alpha AXP architecture and up to two processors. It supports a
‘‘snooping protocol’’ that allows a CPU’s first-level write-through
cache and second-level write-back cache to maintain consistent
data with another processor’s caches, system memory, and the
I/O port on a transaction-by-transaction basis.
The system bus is a synchronous, multiplexed interconnect that
can transfer a 34-bit address or a 128-bit data with 32-bit parity
in a single cycle. Two CPU modules and an I/O module arbitrate
for the system bus via a prioritized scheme that allows the I/O
module to interleave with the two CPU modules. The arbitration
function and system bus clock generators are located on the CPU
1 module.

Central
Processing Unit

The KN430 CPU module houses the DECchip 21064 processor,
which implements the Alpha architecture. The system supports
up to two CPU modules in a symmetric multiprocessing
configuration.
The CPU controls the execution of all instructions and processes.
The CPU circuits contain the logic, arithmetic, and control
functions used by the system.

9–6 Learning More About Your System

CPU Subsystem

Memory Module

Main memory provides the electrical storage area for data
and instructions used by the CPU. DEC 4000 AXP Rackmount
systems support from one to four memory modules.
Each memory module features the following:

I/O Module

•

Error detection and correction (EDC) logic

•

Memory interleaving across two or four modules of like sizes

•

Read prefetch buffers

•

Write transaction buffers

•

Block exchange

•

Read data wrapping

•

Intelligent refresh control

Each system has an I/O (input/output) module that allows the
system to access mass storage, backup, and network resources.
The I/O module contains the following:
•

One or two Ethernet ports, based on the third-generation
Ethernet chip (TGEC).
Each Ethernet port has two associated ports: thickwire
(standard Ethernet) and ThinWire. You select either
thickwire or ThinWire with a switch that is located halfway
between the thickwire and the ThinWire ports. You can
connect to a twisted-pair Ethernet by connecting a twistedpair H3350 media access unit to the thickwire port, using a
standard transceiver cable.

•

Futurebus+ Profile B interface (allows both 32- and 64-bit
data transfers).

•

Console and diagnostic firmware (512-KB of flash-erasable
read only memory—FEPROM).

•

8-KB of EEROM for console use.

•

Time-of-year (TOY) clock, based on Dallas Semiconductor
DS1287.

Learning More About Your System 9–7

CPU Subsystem

I/O Daughter
Board

Serial Control
Bus

•

One asynchronous serial line unit (SLU) dedicated to the
console subsystem.

•

One additional asynchronous SLU with modem control.

•

Serial control bus controller for communications with other
components of the system.

Each system has an I/O daughter board that allows the system
to access mass storage and backup resources via five ports:
•

Four SCSI-2/DSSI buses for external fixed-media devices,
each supporting up to seven external devices.

•

One SCSI-2 bus for internal removable-media and fixedmedia devices, limited expansion for up to three external
devices.

The serial control bus is a two-conductor serial interconnect bus
that is independent of the system bus. The serial control bus
connects the following modules:
•

CPUs

•

I/O module

•

Memory modules

•

Power system controller (PSC)

•

Operator control panel (OCP)

The serial control bus is used by the system to communicate with
the main interfaces on the OCP and power system controller, and
with the 256 x 8 error log EEPROM devices on the CPU, I/O,
and memory modules.
The serial control bus is also used by the system for maintenance
and control functions, such as power-up and power-down
sequencing, error-logging, and error-reporting.

9–8 Learning More About Your System

Power Subsystem

Power Subsystem
Components

The power subsystem is a universal supply that automatically
selects the correct operational voltage range. Some elements of
the supply are distributed, others are centralized and modular.
Power for the backplanes is provided by the centralized power
source. Internal storage devices are powered by a dc-dc converter
(local disk converter) included in the bottom tray.
The power subsystem has five basic components:
•

Front end unit (ac to 48 V dc with power factor correction)

•

Power system controller

•

DC-DC converter unit—5 V at 150 A.

•

DC-DC converter unit—This unit generates three voltages:
12 V at 4 A, 3.3 V at 20 A, and 2.1 V at 10 A (Futurebus+
terminator power).

•

Local disk converters. The local disk converters generate
three voltages for storage devices (+5, +12, and +5 V
SCSI-2/DSSI terminator voltage).

All of the power supply components (except the local disk
converter) plug into and mount in a card cage attached to the
system backplane. The local disk converter is mounted in the
bottom tray.
You can enhance system availability with an optional external
uninterruptible power supply (UPS). A UPS is able to keep the
system running in the event of a power failure.

Uninterruptible
Power Supply
(Optional)

You can connect an optional uninterruptible power supply to
your system. Connecting an uninterruptible power supply (UPS)
to the DEC 4000 AXP Rackmount system can keep the system
running for approximately 30 minutes after a power failure.
For information about ordering a UPS for your system, refer to
the Systems and Options Catalog.

Learning More About Your System 9–9

Storage Subsystem

Storage Subsystem
Components

Each system has a storage subsystem, which consists of an
internal mass storage compartment and, optionally, external
devices.

Mass Storage
Adapters

Your system has five adapters built into the I/O module. The
adapters provide a path to each mass storage bus through which
the CPU can communicate with mass storage devices.
Each of the five adapters can support up to eight nodes. The
adapter and each device count as one node; hence, each adapter
can support seven storage devices.
DSSI adapters allow you to link one system to another to form a
DSSI VMScluster configuration. When a DSSI bus is extended to
a second system, both systems can share up to six DSSI storage
devices.

Mass Storage
Devices

Mass storage devices record data on media. Use mass storage
devices to store data and software permanently. When the data
or software is needed, the CPU copies it from the mass storage
device into main memory. The two primary types of mass storage
devices are fixed-media devices, such as fixed-disk drives and
removable-media devices, such as tape cartridges and compact
discs.

Mass Storage
Expansion

You can expand mass storage capacity on a DEC 4000 AXP
Rackmount system by rackmounting extra drives within the
same or another enclosure.

9–10 Learning More About Your System

Futurebus+ Subsystem

Futurebus+ Subsystem
Overview

DEC 4000 AXP Rackmount systems implement Futurebus+
Profile B as the I/O bus. Features of Futurebus+ include:
•

Industry open standard bus.

•

32- or 64-bit, multiplexed address and data bus.

•

Asynchronous protocol.

•

Centralized arbitration.

•

160 MB/s bandwidth, asymptotic/100 MB/s sustained.

Six Futurebus+ modules can reside in the Futurebus+ portion of
the card cage. The slots are numbered 1–6, from right to left.

References
The following table describes additional sources of information
about your system.
Task

Document

Understand system unit
internals

DEC 4000 Model 600 Series
Technical Manual

Understand mass storage
devices

Device-specific owner’s guide

Order a UPS

Systems and Options Catalog

Learning More About Your System 9–11

10
Care, Maintenance, and Exterior
Customizations
Chapter Description
Introduction

This chapter focuses on the care and maintenance of your system
as well as the customizations that you can make to the system’s
exterior.

In This Chapter

This chapter covers the following information:
•

Customizing the System Unit

•

Maintaining the System

Customizing the System Unit
Overview

You can customize the system unit in the following ways:
•

Label the system name

•

Replace English-language labels

•

Change the baud rate

Care, Maintenance, and Exterior Customizations 10–1

Customizing the System Unit

Locate
Accessories

Locate the accessories box in the system shipping carton.
(Figure 10–1).

! Blank media
" Logical ID label
# Tape cleaning kits

10–2 Care, Maintenance, and Exterior Customizations

Customizing the System Unit

Figure 10–1 Accessories Box

NUO-420-41-DG

Care, Maintenance, and Exterior Customizations 10–3

Customizing the System Unit

Label the
System Name

Your operating system software instructs you in how to name
your system. You can add the system name (network node name)
in a convenient location on the system using the logical node
name label letter card from the accessories box as shown in
Figure 10–2.

10–4 Care, Maintenance, and Exterior Customizations

Customizing the System Unit

Figure 10–2 Labeling the System Name

AB
AA
B C
A
B
A BB CCC DD E
A
B CC DDD E E F F G
AA
BB
E EF F F
GG H H I
CC DD
E
E F F GGG H HI I I
F GG H H HI I
HI I

X=32.975
Y=26.974
SCALE=1/8
NUO-420-42-DG

Care, Maintenance, and Exterior Customizations 10–5

Customizing the System Unit

Replace
English-Language
Labels

If you wish, place labels written in an alternate language on top
of the English-language labels, using the language set of your
choice from the sets of language labels in the accessories box.

Antistatic Wrist
Strap

An antistatic wrist strap, labeled Disposable Grounding Wrist
Strap, is included in the system accessories box. Use of this
strap is required when you are performing system maintenance
and handling static-sensitive modules. If you are not performing
system maintenance, it is not necessary to use this strap.
For information about how to use the strap, refer to the
Disposable Grounding Wrist Strap envelope.

10–6 Care, Maintenance, and Exterior Customizations

Customizing the System Unit

Changing the
Baud Rate

The system’s baud rate is set at the factory to 9600. Change the
console terminal port baud rate by following the instructions in
this section.
Note
To change the baud rate of the console terminal
port temporarily, you can change the setting
of the tta0_baud environment variable. (See
Changing the Baud Rate (tta0_baud and tta1_
baud) in Chapter 6.) The baud rate switch setting
(described in this section) overrides the tta0_baud
setting when you cycle power on the system.

Change the baud rate as follows:
Note
The switch is only accessable by removing the
front bezel and extending the chassis on its rails.

1. On the back of the operator control panel, the number in the
view window (5 in Figure 10–3) signifies the current baud
rate setting. The numbers and the baud rate they represent
are as follows:
View Window
Number

Baud Rate
Equivalent

600

1200

2400

4800

9600

19,200

2. On the back of the panel, turn the black plastic screw ( in
Figure 10–3) to the number that represents the setting you
desire.

Care, Maintenance, and Exterior Customizations 10–7

Customizing the System Unit

3. Restore the chassis to the cabinet and reinstall the bezel.
Figure 10–3 Location of the Baud Rate Switch

5
NUO-420-43-DG

10–8 Care, Maintenance, and Exterior Customizations

Maintaining the System

Maintaining the System
Overview

While your DEC 4000 AXP Rackmount is designed to function in
a range of environmental conditions, it should be treated with
care and maintained properly.
Correct use and maintenance of your system, monitor, and
keyboard not only assures that the system functions properly,
but also helps avoid more serious problems that could cause
permanant damage and corrupt your files.

Environmental
Guidelines

Apart from performing maintenance tasks, you should be
operating your system within the guidelines described in
the DEC 4000 Model 600 Series Site Preparation Checklist.
Refer to the card for a description of the range of acceptable
environmental conditions for your system.
The DEC 4000 AXP Rackmount system unit requires adequate
ventilation. Ideally, the system unit should be positioned in a
dust-free environment. Also, never position the system unit in
direct sunlight where it may become too hot.
Clean your system regularly by wiping dust and particles from
the system unit and the keyboard with a soft cloth.

Liquid on the
System Unit

If you inadvertently spill liquid on the system unit and it seeps
inside, turn off the system and contact your Digital Services
representative.

Care, Maintenance, and Exterior Customizations 10–9

11
Troubleshooting the System
Chapter Description
Introduction

Troubleshooting generally means encountering and resolving a
system problem that is preventing you from using your system to
perform normal operations.
Though your DEC 4000 AXP Rackmount system is a highquality, thoroughly tested product, it is also an electrical device
that may exhibit problems on occasion. If you are experiencing
problems with your system, this chapter will help you identify
and fix the problem.

In This Chapter

This chapter covers the following information:
•

Before You Begin

•

Task Overview

•

Determining Type of Problem

•

Power Problems

•

Problems Getting to Console Mode

•

Console Mode Problems

•

Boot Problems

•

Operating System Problems

•

Mass Storage Problems

•

Network Problems

•

Reporting Problems to Digital Services

Troubleshooting the System

11–1

Before You Begin

Before You Begin
Two Ways to
Solve System
Problems

There are two ways to solve problems with the DEC 4000 AXP
Rackmount system:
1. Use the information in this chapter to help identify and fix
the problem yourself.
2. Contact your Digital service representative to diagnose and
fix the problem for you.

Method to
Identify
Problems

Table 11–1 lists ways to identify problems, and indicates where
each method is described:
Table 11–1 How to Identify a Problem
To identify a problem this
way . . .

Refer to . . .

Using the troubleshooting
tables

This chapter

Running diagnostic tests

test command (test ) in
Chapter 5

Using the troubleshooting tables in this chapter is the easiest
and most direct approach to identifying and correcting a problem
with your DEC 4000 AXP Rackmount system. Therefore, this
is the method you should begin with if you are experiencing
problems.

11–2 Troubleshooting the System

Task Overview

Task Overview
Steps to
Identifying a
Problem

Table 11–2 describes the steps required to identify and fix system
problems.
Table 11–2 Steps to Resolving Problems
Step

Description

Determine type of problem.

Locate problem in troubleshooting tables.

Follow suggested actions to resolve problem.

If necessary, run diagnostic tests.

Contact Digital service representative.

The next sections describe these steps.

Troubleshooting the System

11–3

Determining Type of Problem

Types of
System
Problems

Determine the type of problem that your system is experiencing
from the list in Table 11–3.
Table 11–3 Type of Problem
For this kind of problem . . .

See this section . . .

Power

Power Problems

Getting to console mode

Problems Getting to Console Mode

Console mode

Console Mode Problems

Boot

Boot Problems

Operating system

Operating System Problems

Drive access

Mass Storage Problems

Network

Network Problems

If you cannot locate the problem your system is experiencing,
or if the corrective actions in the troubleshooting tables do not
resolve the problem, see the Reporting Problems to Digital
Services section, later in this chapter.

11–4 Troubleshooting the System

Power Problems

Power Problems
Power
Problems

This section describes how to troubleshoot the system when
there is no power at the system enclosure or the power supply
subsystem lights indicate power trouble.
Table 11–4 describes possible power problems and their solutions.
The next section, Power Supply Lights, explains how to interpret
the lights.

Table 11–4 Diagnostic Flow for Power Problems
Symptom

Action

Reference

No ac power at system. AC
present light is off.

Check the power source and power cord.

AC power is present, but
system does not power on.

Check the ac circuit breaker setting.
Examine power supply subsystem lights to
determine if a power supply unit or fan has
failed, or if the system has shut down due to an
overtemperature condition.

Power Supply
Lights

Figure 11–1,
Table 11–5

The power supply lights on the top of the system (Figure 11–1)
are used to indicate the status of the components that make up
the power supply subsystem. Refer to Table 11–5 for information
on interpreting the lights and determining what actions to take
when a failure is indicated.
Note
The chassis must be extended on its rails for the
power supply lights/indicators to be visible.

Troubleshooting the System

11–5

Power Problems

Figure 11–1 Power Supply Lights

1
2
3
4
5
6
7
SO
SI
MO

8
9
10
11
12
13
14

DC3

DC5

PSC

FEU
NUO-420-44-DG

! AC present indicator
" Fault ID display
# Disk power failure
indicator
$ Fan failure indicator
% Overtemperature
shutdown indicator
& PSC OK indicator
' PSC failure indicator

11–6 Troubleshooting the System

( DC5 OK indicator
) DC5 failure indicator
+> DC3 OK indicator
+? DC3 failure indicator
+@ FEU OK indicator
+A FEU failure indicator
+B AC circuit breaker

Power Problems

Table 11–5 Interpreting Power Supply Lights
Light

Meaning

Action on Error

Front End Unit (FEU)
AC Present

When on, indicates ac power is present
at the ac input connector (regardless of
circuit breaker position).

FEU OK

When on, indicates dc output voltages
for the FEU are above the specified
minimum.

FEU Failure

When on, indicates dc output voltages
for the FEU are less than the specified
minimum.

If ac power is not present, check
the power source and power cord.
If the system will not power up
and the ac light is the only light
that is on, check the ac circuit
breaker.

Call Digital Services.

Power System Controller (PSC)
PSC OK

When blinking, indicates the PSC is
performing power-up self-tests.
When steady, indicates the PSC is
functioning normally.

PSC Failure

When on, indicates the PSC has detected
a fault in itself.

Call Digital Services.

Disk Power
Failure

When on, indicates the local disk
converter has failed. The number "3"
is displayed in the hexadecimal fault ID
display.1

Call Digital Services.

Fan Failure

When on, indicates a fan has failed. The
failing fan is identified by a number
displayed in the hexadecimal fault ID
display.

Call Digital Services.

1 The Rackmount DEC 4000 only supports one (1) Local Disk Converter (LDC). Any code other than "3"
displayed in the Fault ID display, in conjunction with a "DISK POWER FAILURE" indication, is not applicable
to the Rackmount DEC 4000 Model 600.

(continued on next page)

Troubleshooting the System

11–7

Power Problems

Table 11–5 (Cont.) Interpreting Power Supply Lights
Light

Meaning

Action on Error

Power System Controller (PSC)
Overtemperature When on, indicates the PSC has shut
Shutdown
down the system due to excessive internal
temperature.

Set the dc On/Off switch to off
(0). Examine the air plenum at
the top of the system and the air
exhaust ports at the bottom sides
of the system, making sure they
are not blocked. Power up the
system when you have removed
ventilation blocks. Wait at least
one minute before turning on the
system.

DC-DC Converter (DC3)
DC3 OK

When on, indicates that all of the output
voltages are within specified tolerances.

DC3 Failure

When on, indicates that one of the output
voltages is outside specified tolerances.

Call Digital Services.

DC-DC Converter (DC5)
DC5 OK

When on, indicates the 5 V output voltage
is within specified tolerances.

DC5 Failure

When on, indicates the 5 V output voltage
is outside specified tolerances.

11–8 Troubleshooting the System

Call Digital Services.

Problems Getting to Console Mode

Problems Getting to Console Mode
Pre-Console
Mode Problems

This section describes how to troubleshoot the system when you
power up the system, but the console terminal does not display
on the power-up screen.
•

Table 11–6 describes possible problems when getting to
console mode and their solutions.

•

Table 11–7 explains how to interpret the lights on the
operator control panel.

Table 11–6 Diagnostic Flow for Problems Getting to Console
Symptom

Action

Power-up screens
are not displayed on
console terminal.

Check terminal power source and
power cord.

Reference

Check terminal brightness and
contrast controls. Verify that the
terminal power switch is on.
Check system operator control panel
lights for a failure during self-tests.
If two operator control panel lights
remain on, either option could be at
fault.

Figure 11–2 and Table 11–7

Make sure that baud rate settings
for terminal and system match. The
system default baud rate setting is
9600.

Changing the Baud Rate in
Chapter 10

Try connecting the console terminal
to the auxiliary serial port.

Troubleshooting the System

11–9

Problems Getting to Console Mode

The operator control panel lights (Figure 11–2) are used to
indicate the progress and result of self-tests for Futurebus+,
memory, CPU, and I/O modules. Refer to Table 11–7 for
information on interpreting the lights and determining what
actions to take when a failure is indicated.

Operator
Control Panel
Lights

! DC power light
" Self-test status lights
Figure 11–2 Operator Control Panel Lights

Halt
6-1

MEM

0 1

Reset

CPU

I/O

2
NUO-420-64-DG

11–10 Troubleshooting the System

Problems Getting to Console Mode

Table 11–7 Interpreting Operator Control Panel Lights
Light

Meaning

Action on Error

6–1

Remains on if a Futurebus+
option has failed self-tests.

Call Digital Services.

MEM 3, 2, 1, 0

Remains on if a memory
module has failed self-tests.

Call Digital Services.

CPU 0, 1

Remains on if a CPU module
has failed self-tests.

Call Digital Services.

I/O

Remains on if the I/O module
has failed self-tests.

Call Digital Services.

DC Power

When on, indicates that dc
power is present.
When not on, indicates that
dc power is not present.

If the ac circuit breaker is set to ON ( | ), reset
the system and examine the power supply
lights. If the problem persists, call Digital
Services.

Troubleshooting the System

11–11

Console Mode Problems

Console Mode Problems
Console Mode
Problems

This section describes how to troubleshoot your system when
self-tests do not complete or when error messages are displayed
on your console terminal in console mode.
Table 11–8 describes problems reported by the console and their
solutions.

Table 11–8 Diagnostic Flow for Console Mode Problems
Symptom

Action

Reference

Power-up screens are
displayed, but tests do
not complete.

Use power-up display and/or operator
control panel lights to determine
error.

Figure 11–2, Table 11–7,
Figure 3–1, and Figure 3–2
(in Chapter 3)

Console error message
appears.

Call Digital Services.

11–12 Troubleshooting the System

Boot Problems

Boot Problems
Boot Problems

This section describes how to troubleshoot problems that occur
while the system is booting operating system software.
Table 11–9 describes possible problems during booting and their
solutions.

Table 11–9 Diagnostic Flow for Boot Problems
Symptom

Action

Reference

System cannot find
boot device.

Check the default boot device and
boot flag settings.

Setting or Changing the Default
Boot Device (bootdef_dev) and
Setting Boot Flags (boot_osflags)
in Chapter 6.

Check system configuration for
correct device parameters (drive ID,
device name, and so on) by entering
show device command.

Displaying System
Configuration , Changing Drive
ID Numbers (External Media)
and Setting and Examining
Parameters for DSSI Devices in
Chapter 8.

Run the test command to check
that boot device is healthy.

The test command (test in
Chapter 5). If device is not
operating, call Digital Services.

Boot the system interactively or
using a diagnostic bootstrap.

Setting Boot Flags (boot_osflags)
in Chapter 6.

Device does not boot.

Troubleshooting the System

11–13

Operating System Problems

Operating System Problems
Operating
System
Problems

This section desribes how to troubleshoot system problems that
occur while operating system software is up and running.
Table 11–10 describes possible operating system problems and
their solutions.
Table 11–10 Diagnostic Flow for Operating System Errors
Symptom

Action

System halts; >>> displayed on
console terminal.

Check to see whether the
system was accidentally
halted by entering the
continue command and
pressing Return . If the
system resumes program
execution, the system
was accidentally halted.
Record screen display
error messages and call
Digital Services.

System reboots unexpectedly.

Let rebooting complete.
Record screen display
error messages and call
Digital Services.

11–14 Troubleshooting the System

Mass Storage Problems

Mass Storage Problems
Mass Storage
Problems

This section describes how to troubleshoot mass storage-related
problems. Typically, these problems occur while operating system
software is up and running.
Table 11–11 describes possible drive problems and their
solutions.
Note
The bottom tray must be lowered to see the hard
drive fault lights.

Table 11–11 Diagnostic Flow for Mass Storage Problems
Symptom

Action

Write error message
displayed or unable to
copy to media.

Check that media is not writeprotected.

Drive fault light comes on
or blinks.

Check that drive ID is correct.
Correct drive ID plug if it is
incorrect.

Reference

Make sure all devices and
controllers or adapters on same
bus have unique drive IDs.

Changing Drive ID Numbers
(External Media) in
Chapter 8.

Abnormal environmental condition.
Reset temperature or humidity to
normal condition.
If fault light stops blinking, system
may have corrected itself. If fault
light remains on, call your Digital
service representative.
(continued on next page)

Troubleshooting the System

11–15

Mass Storage Problems

Table 11–11 (Cont.) Diagnostic Flow for Mass Storage Problems
Symptom

Read error message
displayed.

Action

Reference

Check that bus is properly
terminated.

Terminating and Extending a
DSSI Bus in Chapter 8.

Wait for drive to spin up. Continue
entering show device command
until device is displayed in
list of devices. If device is not
displayed, call your Digital service
representative.
Perform corrective actions listed if
drive fault light comes on or blinks.

11–16 Troubleshooting the System

Mass Storage Problems

RRD42 Disc
Caddy Removal
Problem

If you are unable to eject a disc caddy using the drive eject
button, the Eject button may be disabled by software.
Table 11–12 describes how to manually remove the caddy.
Table 11–11 describes how to troubleshoot all other RRD42
problems.
Manually remove the disc caddy as follows:
Table 11–12 Manual Removal of a Disc Caddy
Step

Action

Shut down the system.

Set the ac circuit breaker to the OFF position (0).

Insert the end of a steel rod the size of a large paper clip
into the manual eject hole, as shown in Figure 11–3, and
push until the disc emerges from the drive.

Figure 11–3 Manually Removing a Disc Caddy

NUO-420-45-DG

Troubleshooting the System

11–17

Network Problems

Network Problems
Ethernet
Problems

If an error message displays when verifying or testing the
Ethernet connection, see Table 11–13.
Table 11–13 Resolving Ethernet Problems
Symptom

Action

Ethernet error message is
displayed.

Check to see if an Ethernet cable was
removed. If so, replace the cable with a
terminator.
Check that all connections on the
Ethernet segment are secure.
Check that Ethernet switch on the rear
of the system is in proper position for
the port (either thickwire or ThinWire)
that you are using.

11–18 Troubleshooting the System

Reporting Problems to Digital Services

Reporting Problems to Digital Services
Digital Support
Centers

Digital service representatives are available at Digital support
centers for customers who have on-site warranty and service
contracts. If you wish to purchase a service contract, contact
either a Digital support center listed in Table 11–14, or your
local Digital office.

How to Report
Problems

If you are unable to locate the system problem in the previous
sections of this chapter, or the actions suggested could not
resolve the problem, contact your Digital service representative.
Before calling to report a problem, complete these steps.
1. Locate the part and serial numbers, printed on the label at
the rear of your system. Record these numbers on a copy of
the Problem Worksheet at the end of this chapter.
Your Digital service representative will need this information
when you call.
2. Fill in the ‘‘Status of the System’’ information on the
worksheet.
3. Note the problem, possible causes if you know them, and
solutions suggested in the previous sections. Also indicate
what actions (if any) you have already taken to try to correct
the problem.
4. Be prepared to read information from the screen and to enter
commands at the keyboard while you talk to your Digital
service representative.

Digital Support
Center Contact
Numbers

Table 11–14 lists the telephone numbers for contacting a Digital
service representative at your Digital support center.
If your Digital Services number is not listed in Table 11–14,
contact your local Digital office for assistance.

Troubleshooting the System

11–19

Reporting Problems to Digital Services

Table 11–14 Telephone Numbers of Digital Support Centers
Country

Telephone Number

United States

1-800-354-9000

Canada

1-800-267-5251

Canada (Quebec)

1-800-267-2603

United Kingdom

[44]256 59200

France

[33]92955111

Germany

[49]-(89)-95913218

References
The following table describes where to find additional
troubleshooting information.
Task

Document

Power up, put on line, install
terminal cable, reset setup,
or set terminal baud rate of
the console terminal

Terminal installation guide

Look up appropriate
temperature range for system
environment

Appendix A

Diagnostics, troubleshooting,
error log analysis, system
integration

DEC 4000 AXP Model 600 Series
Service Guide

11–20 Troubleshooting the System

12
Removal and Installation Procedures
Chapter Description
Introduction
Warning
The information in this chapter is for use by
Digital customer service personnel and qualified
self-maintenance customers.

This chapter describes how to remove and install the
recommended spare parts (also referred to as field replaceable
units (FRUs)). For troubleshooting information, refer to
Chapter 11.
Warning
Whenever performing any removal or installation
procedure, ensure that the ac circuit breaker
located at the top of the DEC 4000 AXP Rackmount
system is in the OFF position and the power cord
is disconnected from the ac power source.
The system weighs 65.7 kg (146 lbs). Ensure that
the enclosure is stabilized before the system is
extended on its slides.

Removal and Installation Procedures 12–1

Chapter Description

In This Chapter

FRU Location

This chapter provides information concerning the following:
•

FRU Location

•

Accessing Top FRUs

•

Accessing Bottom FRUs

•

Bottom Tray, Removal/Installation

•

Modules, Removal/Installation

•

OCP, Removal/Installation

•

I/O Daughter Board Assembly, Removal/Installation

•

LDC Board, Removal/Installation

•

Fan, Removal/Installation

•

Disk Drives, Removal/Installation

•

Fingerstock, Removal/Installation

•

SCSI to DSSI Adapters, Removal/Installation

•

Back Plane Assembly, Removal/Installation

This chapter covers the removal and installation of the FRUs
listed in Table 12–1. Figure 12–1 shows the location of those
FRUs in the DEC 4000 AXP Rackmount system. For a complete
list of part numbers of all recommended spares and other FRUs,
refer to Appendix B.
Depending on where the FRU is located, you may need to pull
the system out of the rack to gain access to the FRUs in the top
of the system. You may also need to lower the bottom tray to
access FRUs in the tray or access cable connections to FRUs at
the rear of the system.

12–2 Removal and Installation Procedures

Chapter Description

Table 12–1 Recommended Spares
Item

Part Number

OCP Module

54-22569-01

I/O Daughter Board

54-21779-01

LDC Power Board

54-20868-01

Fan

12-36202-01

Disk Drives

See Chapter 7 for list

Bottom Tray Fingerstock

See Appendix B for list

SCSI to DSSI Adapters

12-39838-01

Back Plane Assembly

70-30518-01

Removal and Installation Procedures 12–3

Chapter Description

Figure 12–1 Location of FRUs
1

4
7
Scale = 1/8
5

6
NUO-420-46-DG

! Modules
% Local Disk Converter (LDC) board
" Operator Control Panel & Media drives
(OCP)
' Backplane
# Fans
$ Input/Output (I/O)
board

12–4 Removal and Installation Procedures

Accessing Top FRUs

Accessing Top FRUs
Extending
Chassis For
Service

To access the top FRUs, you need to remove the front bezel and
pull out the system on its slides. To do this, refer to Figure 12–2
and proceed as follows:
1. Remove the front bezel by inserting a flat blade screwdriver
into the top, left slot
of the bezel , and then push toward
the system to release the top, left side of the bezel from the
ball stud
on the chassis.

2. Repeat the procedure using the right slot
top, right side of the bezel.
3. Pull the bezel away from the system.
4. Remove the four system retaining screws
front of the system to the rails.

$ to release the

% fastening the

5. Stabilize the enclosure. For example, pull out the cabinet
stabilizer foot
as shown in Figure 12–3. The stabilizing
feature may be different depending on your cabinet.

Warning
The system weighs 65.7 kg (146 lbs). Ensure
the enclosure is stabilized before the system is
extended on its slides.

6. Using the system handle , pull the system out of the rack
on its slides. You can now access the FRUs in the top of the
system.
Note
If you intend to open the bottom tray, pull the
system out to the full travel of the slides to the
point where the two slide locks are locked.

Removal and Installation Procedures 12–5

Accessing Top FRUs

Figure 12–2 Removing the Front Bezel

3
1

2
NUO-65B.DG
SC,F,1.69
NUO-420-65-DG

12–6 Removal and Installation Procedures

Accessing Top FRUs

Figure 12–3 Pulling Out the System

ADD-2

NUO-420-47-DG

Warning
The system weighs 65.7 kg (146 lbs). Ensure
the enclosure is stabilized before the system is
extended on its slides.

Removal and Installation Procedures 12–7

Accessing Top FRUs

Placing the
System Back
into the Rack

To place the system back into the rack, refer to Figure 12–4 and
proceed as follows:

was pulled out all the way, push down on
1. If the system
the two slide locks
before pushing the system back into
the rack.

2. Refer to Figure 12–2 and install the four system retaining
and tighten.
screws

3. Install the bezel
by aligning it with the four ball studs
and pushing it into place.

12–8 Removal and Installation Procedures

Accessing Top FRUs

Figure 12–4 Placing System Back Into the Rack

ADD-1

NUO-420-48-DG

Removal and Installation Procedures 12–9

Accessing Bottom FRUs

Accessing Bottom FRUs
Opening the
Bottom Tray

To gain access to the FRUs in the bottom of the system or to the
cable connections of the I/O daughter board at the rear of the
system, you need to pull the system out of the cabinet and lower
the bottom tray.
To gain access to the FRUs, refer to Figure 12–5 and proceed as
follows:
1. Pull the system out of the rack using the procedure in
Extending Chassis For Service.
Warning
There is an energy hazard near the LDC board.
Make sure the system is shut down before opening
the bottom tray.

2. While holding up the bottom tray
with one hand, release
the latch
by pushing in on one end
of the latch to make
and turn the
the latch handle accessible. Then pull down
handle clockwise
to release the bottom tray.

3. Allow the bottom tray to lower to its vertical position. This
provides access to the FRUs in the bottom tray and cable
connections to the I/O daughter board at the rear of the
system.

12–10 Removal and Installation Procedures

Accessing Bottom FRUs

Figure 12–5 Opening the Bottom Tray

1
2

NUO-420-49-DG

Removal and Installation Procedures 12–11

Accessing Bottom FRUs

Closing the
Bottom Tray

Caution
Before closing the bottom tray, ensure that all
cables are properly positioned so that none are
pinched when closing the bottom tray.

To close the bottom tray and place the system back into the rack,
refer to Figure 12–5 and proceed as follows:

1. Push the bottom tray
hold with one hand.

! back up into the system chassis and
"

2. Turn the latch handle
counterclockwise to secure the tray
and then push the handle back into its resting place.
3. Place the system back into the rack by following the
instructions in Placing the System Back into the Rack.

12–12 Removal and Installation Procedures

Bottom Tray, Removal/Installation

Bottom Tray, Removal/Installation
Bottom Tray,
Removal

There may be times when it is necessary, or more convenient, to
work on the system with the bottom tray removed.
Warning
The bottom tray weighs approximately 25 pounds,
and it is awkward to handle. To prevent injury
or damage to the equipment, it is recommended
that at least two people be involved in removing or
installing the bottom tray.

To remove the bottom tray, refer to Figure 12–6 and proceed as
follows:
1. Pull the system out of the rack and open the bottom tray as
described in Opening the Bottom Tray.
2. Disconnect the black/purple twisted-pair cable
LDC board .

3. Disconnect the I/O cable (flat cable)
.

! from the

# from the LDC board

4. From the rear of the unit, remove one retaining screw
from the SCSI connector .

5. Loosen the other retaining screw and remove the SCSI
connector. This cable comes from the fixed-media drive.

6. Disconnect the white SCSI cable
from the I/O daughter
board . This cable comes from the removable-media drive.

Removal and Installation Procedures 12–13

Bottom Tray, Removal/Installation

(

7. Disconnect the end of the gas strut
attached to the ball
in the bottom tray . This is done by inserting a
stud
flat blade screwdriver as shown in Figure 12–6. Twist the
screwdriver to release the gas strut from the ball stud. Then
pull the gas strut away from the ball stud.

)

8. While one person holds the bottom tray
in place (open
position), squeeze the two hinge pins
on each hinge as
shown in Figure 12–6 into the locked position.

9. Separate and remove the bottom tray
the system.

12–14 Removal and Installation Procedures

+> from the hinges and

Bottom Tray, Removal/Installation

Figure 12–6 Removing the Bottom Tray

4
6

7
11
11

9
8
10

NUO-420-50-DG

Removal and Installation Procedures 12–15

Bottom Tray, Removal/Installation

Bottom Tray,
Installation

To install the bottom tray, refer to Figure 12–6 and proceed as
follows:
Warning
The bottom tray weighs approximately 25 pounds,
and it is awkward to handle. To prevent injury
or damage to the equipment, it is recommended
that at least two people be involved in removing or
installing the bottom tray.

+> vertically and up into the system.
2. Squeeze the hinge pins +? of the bottom tray into the locked
1. Position the bottom tray
position.

3. Align the hinges on the bottom tray with the chassis hinges,
and then release the hinge pins , allowing them to snap
into place.

4. Push the end of the gas strut
bottom tray .

( onto the ball stud ) in the

&
'
6. Attach the white SCSI cable % from the fixed-media drive to
the rear of the unit using two screws $.
7. Connect the I/O cable (flat cable) # to the LDC board ".
8. Connect the black/purple twisted-pair cable ! to the LDC
board ".
from the removable-media
5. Connect the white SCSI cable
drive to the I/O daughter board .

9. This completes the bottom tray installation. To close the
bottom tray and place the system back into the rack, follow
the instructions in Closing the Bottom Tray.

12–16 Removal and Installation Procedures

Modules, Removal/Installation

Modules, Removal/Installation
Introduction

The DEC 4000 AXP Rackmount supports the same optional
modules as described in the DEC 4000 AXP Model 600 Series
Options Guide. However, because the DEC 4000 AXP Rackmount
is a rackmounted unit, the modules are oriented differently. The
following information shows where the modules are installed in
the DEC 4000 AXP Rackmount.
Caution
Static electricity can damage modules and
electronic components. Digital recommends
using a grounded antistatic wrist strap when
working with internal parts of a system or option.

Module
Location and
Installation

Figure 12–7 through Figure 12–10 show the modules listed below
and where they are installed in the DEC 4000 AXP Rackmount
system. The shaded area in the icon in each figure shows the
location where the module is installed.

•

B2001-AA CPU Module

•

B2002-CA or -DA Memory Module

•

B2101-AA I/O Module

•

B2101-BA I/O Module

Removal and Installation Procedures 12–17

Modules, Removal/Installation

B2001 CPU
Module

Figure 12–7 shows the B2001 CPU Module and where it is
plugged into the system card cage.

! System bus
" Futurebus+
# I²C bus

12–18 Removal and Installation Procedures

Modules, Removal/Installation

Figure 12–7 B2001 CPU Module

2
3
NUO-420-51-DG

Removal and Installation Procedures 12–19

Modules, Removal/Installation

B2002 Memory
Module

Figure 12–8 shows the B2002 (-CA or -DA) Memory Module and
where it is plugged into the system card cage.

! System bus
" Futurebus+
# I²C bus

12–20 Removal and Installation Procedures

Modules, Removal/Installation

Figure 12–8 B2002 Memory Module

2
3
NUO-420-52-DG

Removal and Installation Procedures 12–21

Modules, Removal/Installation

B2101-AA I/O
Module

Figure 12–9 shows the B2101-AA I/O Module and where it is
plugged into the system card cage.

! Ethernet port 1
" Ethernet port 2
# Thickwire fuse ok indicator
$ Thickwire port
% Selection switch
& ThinWire port
' ThinWire fuse ok indicator
( Auxiliary serial port
) Console terminal ground lug
+> Console terminal port
+? Storage bus (SCSI/DSSI)
+@ System bus
+A Futurebus+
+B I²C bus

12–22 Removal and Installation Procedures

Modules, Removal/Installation

Figure 12–9 B2101-AA I/O Module

1
3

8
F2

0
F1

12
13
14
NUO-420-53-DG

Removal and Installation Procedures 12–23

Modules, Removal/Installation

B2101-BA I/O
Module

Figure 12–10 shows the B2101-BA I/O Module and where it is
plugged into the system card cage.

! Ethernet port 0
" Thickwire fuse OK indicator
# Thickwire port
$ Selection switch
% ThinWire port
& ThinWire fuse ok indicator
' Auxiliary serial port
( Console terminal ground lug
) Console terminal port
+> Storage bus (SCSI)
+? System bus
+@ Futurebus+
+A I²C bus

12–24 Removal and Installation Procedures

Modules, Removal/Installation

Figure 12–10 B2101-BA I/O Module

1
2

6
7

0
F1

11
12
13
NUO-420-54-DG

Removal and Installation Procedures 12–25

OCP, Removal/Installation

OCP, Removal/Installation
OCP Removal

To remove the OCP, refer to Figure 12–11 and proceed as follows:
1. Pull the system out of the rack using the procedure in
Extending Chassis For Service.
2. Remove and save the two nuts
cover
to the chassis.

3. Remove the OCP rear cover
4. Disconnect the OCP cable

! fastening the OCP rear

5. Remove the OCP board
from the inside of the OCP rear
cover by pulling it off from the four locking standoffs .

OCP
Installation

To install the OCP, refer to Figure 12–11 and proceed as follows:

$ on to the four locking standoffs %.
2. Connect the OCP cable #.
3. Position the OCP rear cover " over the OCP board. Secure
the OCP rear cover to the chassis using two nuts !.
1. Push the OCP board

4. The OCP is now installed. To place the system back into the
rack, follow the instructions in Placing the System Back into
the Rack.

12–26 Removal and Installation Procedures

OCP, Removal/Installation

Figure 12–11 Removing the OCP

Scale = 1/2
1
5
2

5
5

NUO-420-55-DG

Removal and Installation Procedures 12–27

I/O Daughter Board Assembly, Removal/Installation

I/O Daughter Board Assembly, Removal/Installation
I/O Daughter
Board
Assembly
Removal

To remove the I/O daughter board assembly, proceed as follows:
1. Pull the system out of the rack and open the bottom tray as
described in Opening the Bottom Tray.
Note
Before performing step 2, note that the cables
connected to J3 and J4 on the I/O daughter
board assembly are reversible. Mark which
cable connects to J3 and J4 before disconnecting
the cables. Other cables connected to the I/O
daughter board assembly are keyed and cannot be
misconnected.

2. Disconnect the cables (shown in Figure 12–12) from the I/O
daughter board assembly.

! Ribbon cable from backplane (connects to J3 on I/O
daughter board assembly)

" Ribbon cable from backplane (connects to J4 on I/O
daughter board assembly)

# Ribbon cable from backplane (connects to J1 on I/O
daughter board assembly)

$ Ribbon cable from OCP (connects to J9 on I/O daughter
board assembly)

% Red/Black twisted-pair cable from backplane (connects to
J2 on I/O daughter board assembly)

& Round white SCSI cable from removable-media device
(connects to J11 on I/O daughter board assembly)

' Ribbon cable from LDC board (connects to J10 on I/O
daughter board assembly)

12–28 Removal and Installation Procedures

I/O Daughter Board Assembly, Removal/Installation

Figure 12–12 I/O Daughter Board Cable Connections

NUO-420-56-DG

Removal and Installation Procedures 12–29

I/O Daughter Board Assembly, Removal/Installation

3. Refer to Figure 12–13. Remove and save the ten Phillips
screws
fastening the rear I/O assembly
to the rear of
the system chassis .

Caution
Be careful not to damage the connector on the
underside of the I/O daughter board when pulling
it out of the chassis.

4. Pull the rear I/O assembly

" out of the system chassis.#.

5. Remove eight screws
attaching the I/O daughter board to
the rear I/O weldment.

6. Remove six screws
attaching the I/O daughter board to the
rear I/O weldment. Remove the I/O daughter board .

12–30 Removal and Installation Procedures

I/O Daughter Board Assembly, Removal/Installation

Figure 12–13 Removing the I/O Daughter Board Assembly

3
2

NUO-420-57-DG

Removal and Installation Procedures 12–31

I/O Daughter Board Assembly, Removal/Installation

I/O Daughter
Board
Assembly,
Installation

To install the I/O daughter board assembly, proceed as follows:
Caution
Be careful not to damage the connector on the
underside of the I/O daughter board when pushing
it into the chassis.

1. Place the four I/O daughter board port connectors through
the opening of the rear I/O weldment .

2. Fasten the port connectors to the rear I/O weldment
eight screws .

3. Fasten the I/O daughter board assembly
weldment
using six screws .

" using

% to the rear I/O

4. Insert the I/O daughter board assembly
into the rear of
the system chassis , and fasten it using ten Phillips screws
(see Figure 12–13).

5. Connect the cables
to the I/O daughter board assembly
as shown in Figure 12–12. Be sure to connect cables J3 and
J4 according to the markings done in the removal procedure.
6. The I/O daughter board assembly is now installed. To place
the system back into the rack, follow the instructions in
Closing the Bottom Tray.

12–32 Removal and Installation Procedures

LDC Board, Removal/Installation

LDC Board, Removal/Installation
LDC Board
Removal

To remove the LDC board, refer to Figure 12–14 and proceed as
follows:

1. Pull the system out of the rack and open the bottom tray as
described in Opening the Bottom Tray.

! " # $ from the LDC board %.
3. Pull the LDC board % off the four locking standoffs &.
2. Remove cables

LDC Board
Installation

To install the LDC board, refer to Figure 12–14 proceed as
follows:
Caution

' is present

Make sure that the white isolator
before installing the LDC board .

% on to the four locking standoffs &.
2. Connect cables ! " # $ to the LDC board %.

1. Push the LDC board

3. The LDC board is now installed. To place the system back
into the rack, follow the instructions in Closing the Bottom
Tray.

Removal and Installation Procedures 12–33

LDC Board, Removal/Installation

Figure 12–14 Removing the LDC

2
5
3

NUO-420-58-DG

12–34 Removal and Installation Procedures

Fan, Removal/Installation

Fan, Removal/Installation
Fan Removal

To remove a fan, refer to Figure 12–15 and proceed as follows:

Warning
To prevent injury from revolving fan blades, make
sure the system is shut down and fans blades
are not moving before performing the following
procedure.

1. From the rear of the system chassis, loosen the five captive
fastening the rear cover
of the fan assembly
screws
to the system chassis .

2. Lift out the fan assembly
part way (just enough to reach
in and disconnect the two power connectors ).
3. Lift the fan assembly

# out of the rear of the system.

4. To remove a fan from the fan assembly, proceed as follows:

)

a. Remove the M4 screw and washer
fastening the
ground lead
to the fan . The screw hole on the fan is
marked M.

from the rear cover , remove and
b. To remove the fan
save the four retaining screws
and other hardware
fastening the fan and finger guard
to the rear cover.
Note how the hardware was installed.

Removal and Installation Procedures 12–35

Fan, Removal/Installation

Fan Assembly
Installation

To install a fan onto the rear cover and then install the rear
cover in the rear of the system, refer to Figure 12–15 and
proceed as follows:
Warning
To prevent injury, make sure the system is shut
down before performing the following procedure.

1. Install the fan on the rear cover as follows:

)

a. Using the M4 screw and washer , fasten the ground
lead
to the fan . Use the metric screw hole in the
fan marked M.

+@
&

b. Fasten the fan
and finger guard
to the rear cover
, using the four retaining screws
and other hardware
saved when removing the fan from the rear cover.

Note
Make sure the fan is installed so that the air flows
from front to rear in the system.

2. Rest the three tabs
on the bottom edge of the rear cover
in the system chassis slots .

(

3. Connect the two power connectors

4. Fasten the rear cover to the system chassis using the five
captive screws .

12–36 Removal and Installation Procedures

Fan, Removal/Installation

Figure 12–15 Removing the Fan Assembly
10

1
5
8

2
7

NUO-59

Removal and Installation Procedures 12–37

Disk Drives, Removal/Installation

Disk Drives, Removal/Installation
Types of Disk
Drives

The bottom tray supports any half-height SCSI storage device
described in the DEC 4000 AXP Model 600 Series Options Guide.
Full height storage devices are supported as external devices
installed in the rack and connected via the system I/O ports.
The bottom tray supports two fixed-media mass storage devices
(hard disk drives) and two removable-media mass storage devices
(tapes, CD-ROM drives).
The disk drives are mounted on brackets that lock into position
in the bottom tray. One or two hard disk drives can be mounted
on a mounting bracket installed in the center of the bottom tray.
Removable-media disk drives are mounted on separate mounting
brackets toward the front of the bottom tray and accessible
through openings in the front of the tray. Each drive is attached
to the associated mounting bracket by four screws.

12–38 Removal and Installation Procedures

Disk Drives, Removal/Installation

Disk Drive
Removal

The disk drive removal procedure is similar for all the drives.
The following procedure uses the removal of a hard disk drive as
a specific example.
To remove a disk drive, refer to Figure 12–16 and proceed as
follows:
1. Pull the system out of the rack and open the bottom tray as
described in Opening the Bottom Tray.
2. Disconnect the power
disk drive .

! and data cables " from the hard

3. Pull out and then turn the knurled plunger
turn counterclockwise to disengage it.

$ one quarter

4. Slide the assembly backward to release the mounting bracket
from under the head of the drive mounts , and then
remove the assembly.

5. To remove a drive from the mounting bracket, remove the
four retaining screws .

Note
The hard disk drive mounting bracket is a wide
mounting bracket that can hold up to two hard
disk drives.

Note
The removable-media drives are secured by two
screws going through mounting holes in the left
and right sides of their mounting bracket. If
replacing the drive with another of the same type,
note and use the same mounting holes.

Removal and Installation Procedures 12–39

Disk Drives, Removal/Installation

Figure 12–16 Removing a Disk Drive

1
2

4
5

12–40 Removal and Installation Procedures

3
NUO-420-60-DG

Disk Drives, Removal/Installation

Setting the
ID Jumper or
Switches

Before installing a disk drive it may be necessary to set the ID
jumper or switches, if applicable.

Disk Drive
Installation

For a list of disk drives that can be installed in the bottom tray,
refer to Table 7–1. For a list of disk drives supported externally,
refer to Table 7–2.

If a disk drive is being replaced by the same type, use the same
jumper or switch settings as the old drive. For information
concerning ID jumper or switch settings for other disk
drives, refer to the DEC 4000 Model 600 Series Options Guide
(EK-KN430-OG).

To install a disk drive, refer to Figure 12–16 and proceed as
follows:
1. Set the ID jumper or ID switches as applicable (refer to DEC
4000 Model 400 Series Options Guide for settings).
2. Attach the drive to the mounting bracket using four retaining
screws . Ensure the side of the mounting bracket marked
UP faces the bottom of the drive.

Note
When installing a removable-media drive, see
Figure 12–17 for the correct bracket mounting
holes used to attach the replacement drive to the
bracket.

3. Align the mounting holes in the mounting bracket
with
the drive mount heads , and then push in and slide the
assembly downward as far as possible.

4. Push in and turn the knurled plunger
clockwise to engage it.

$ one quarter turn
"

5. Connect the power
and data cables
to the hard disk
drives . Ensure that the cables are routed as shown in the
figure.

6. The hard disk drive is now installed. To close the bottom
tray and place the system back into the rack, follow the
instructions in Closing the Bottom Tray.

Removal and Installation Procedures 12–41

Disk Drives, Removal/Installation

Figure 12–17 Removable-Media Drive Mounting Bracket,
Mounting Holes

NUO-46

! Removable-media mounting bracket, side view, front
" Mounting holes for TLZ06 and RRD42 drives (use metric
hardware only)

# Mounting holes, not used
$ Mounting holes for TZ30 drive (use English hardware only)

12–42 Removal and Installation Procedures

Fingerstock, Removal/Installation

Fingerstock, Removal/Installation
When to
Replace
Fingerstock

The fingerstock is located along the top edge of the bottom tray.
Replace the fingerstock when finger segments are broken, lifted
out of place, or no longer retain a curved shape for good contact.

Fingerstock
Lengths

There are five different lengths of replacement fingerstock.
Table 12–2 provides a list of the different lengths and the
associated part number. Figure 12–18 shows how and where the
fingerstock is installed according to Table 12–2.
Table 12–2 Fingerstock Replacement Lengths
Figure
Ref.

!
"
#
$
%

Fingerstock Length
(Inches)

Part Number

12-26922-06

12-40169-01

12-40169-02

6.5

12-40169-03

12-40169-04

Removal and Installation Procedures 12–43

Fingerstock, Removal/Installation

Fingerstock
Replacement

To replace one or more segments of fingerstock, refer to
Figure 12–18 and proceed as follows:
1. Pull the system out of the rack and open the bottom tray as
described in Opening the Bottom Tray.
2. Identify the damaged fingerstock according to the criteria
previously mentioned.
3. Identify the specific segments needed according to
Figure 12–18 and Table 12–2.

"
!

through
slide on or off the edge of the
4. Fingerstock
bottom tray.
is removed by pressing down and lifting one
side out to release it from the tray.
Figure 12–18 Fingerstock Installation

5
4
5

2
13.5%

5
3

2
NUO-420-61-DG

12–44 Removal and Installation Procedures

SCSI to DSSI Adapters

SCSI to DSSI Adapters
SCSI to DSSI
Adapters,
Installation

The SCSI to DSSI adapter is plugged into a SCSI port so that a
DSSI cable can be connected. Figure 12–19 shows an example of
how a DSSI cable is connected to a SCSI port using the adapter.

! DSSI Cable
" SCSI to DSSI Adapter
# SCSI port

Removal and Installation Procedures 12–45

SCSI to DSSI Adapters

Figure 12–19 Example of Connection Using SCSI to DSSI
Adapter

2
NUO-420-62-DG

12–46 Removal and Installation Procedures

Backplane, Removal/Installation

Backplane, Removal/Installation
Backplane,
Removal

To remove the backplane, you need to:
•

Pull out the system from the cabinet

•

Remove the system modules and the power system modules

•

Lower the bottom tray

•

Remove the bottom tray

•

Remove the backplane
Warning
Before performing any of the following procedures,
be sure that the ac circuit breaker located at the
top of the system is in the OFF (O) position and
that the power cord is disconnected from the ac
power source.

Pull Out the
System

Refer to Extending Chassis For Service at the beginning of this
chapter for instructions on how to pull the system out of the
rack.

Remove
the System
Modules and
the Power
System
Modules
Lower the
Bottom Tray

Disconnect the fan power cable going to the connector near the
ac circuit breaker of the power supply. Each module is fastened
to the card cage by two captive screws on their faceplate. Loosen
the screws and eject the modules using their ejector levers.
Remove the modules from the card cage.
Refer to Opening the Bottom Tray at the beginning of this
chapter for instructions on how to lower the bottom tray.

Removal and Installation Procedures 12–47

Backplane, Removal/Installation

Remove the
Bottom Tray

To remove the bottom tray, refer to Figure 12–20 and proceed as
follows:
1. Pull the system out of the rack and open the bottom tray as
described in Opening the Bottom Tray.
2. Disconnect the black/purple twisted-pair cable
LDC board .

3. Disconnect the I/O cable (flat cable)
.

! from the

# from the LDC board

4. From the rear of the unit, remove one retaining screw
from the SCSI connector .

5. Loosen the other retaining screw and remove the SCSI
connector. This cable comes from the fixed-media drive.

6. Disconnect the white SCSI cable
from the I/O daughter
board . This cable comes from the removable-media drive.

(

7. Disconnect the end of the gas strut
attached to the ball
stud
in the bottom tray . This is done by inserting a
flat blade screwdriver as shown in Figure 12–20. Twist the
screwdriver to release the gas strut from the ball stud. Then
pull the gas strut away from the ball stud.

)

8. Repeat step 7 to remove the other end of the gas strut.

9. While one person holds the bottom tray
in place (open
position), squeeze the two hinge pins
on each hinge as
shown in Figure 12–20 into the locked position.

10. Separate and remove the bottom tray
the system.

12–48 Removal and Installation Procedures

+> from the hinges and

Backplane, Removal/Installation

Figure 12–20 Removing the Bottom Tray

4
6

7
11
11

9
8
10

NUO-420-50-DG

Removal and Installation Procedures 12–49

Backplane, Removal/Installation

Remove the
Backplane

To remove the backplane, refer to Figure 12–21 and Figure 12–22
and proceed as follows:
Note
Before performing step 1, note that the cables
connected to J3 and J4 on the I/O daughter
board assembly are reversible. Mark which
cable connects to J3 and J4 before disconnecting
the cables. Other cables connected to the I/O
daughter board assembly are keyed and cannot be
misconnected.

1. Refer to Figure 12–21 and disconnect three ribbon cables
, and red/black twisted-pair cable
from the I/O
daughter board .

!"#

2. Refer to Figure 12–22 and remove 17 screws
perimeter of the backplane
to the chassis.

' fastening the

3. While holding up the backplane
with one hand, remove
the center screw . Then lower and remove the backplane.

(

Note
Be sure that the EMI gasket

) remains in place.

4. This completes the backplane removal procedure.

Installing the
Backplane

To install the backplane, reverse the steps in the removal
procedure. Be sure that the EMI gasket remains in place.

12–50 Removal and Installation Procedures

Backplane, Removal/Installation

Figure 12–21 I/O Daughter Board Cable Connections

NUO-420-66-DG

Removal and Installation Procedures 12–51

Backplane, Removal/Installation

Figure 12–22 Removing the Backplane

8
NUO-420-63-DG

12–52 Removal and Installation Procedures

A
Specifications
Table A–1 lists the specifications for the DEC 4000 AXP
Rackmount system.

Table A–1 Specifications
Specification

Measurement

Height

44.4 cm (17.5 in)

Width

48.26 cm (19 in)

Depth

75.7 cm (29.8 in) with
mounting brackets

Weight

65.7 kg (146 lbs)

Operating temperature

10-40°C (50-104°F)

Relative humidity (noncondensing)

20-80% operating
10-90% nonoperating

Heat dissipation

@1400 W, 4774 Btu/hr

Minimum airflow required

200 linear ft/minute

Maximum operating altitude

2438 m (8000 ft)

Maximum power consumption

1650 W

Operating power range (1 phase)

104 V ac to 128 V ac/208
V ac to 256 V ac

Power cord length

2.4 m (8 ft)

Declared operating acoustic level

LWAd=6.3B/LpAm=44
dBA
DEC4000 with 4 SCSI
drives, ISO 9296

Specifications A–1

B
Field Replaceable Units (FRU)
Introduction
This appendix lists the FRUs associated with the DEC 4000 AXP
Rackmount system.

FRUs

Table B–1 and Table B–2 provide the Recommended Spares List
(RSL) and other Field Replaceable Units (FRU), respectively,
that are unique to the DEC 4000 AXP Rackmount system.
Combined, they form the complete FRU listing for the DEC 4000
AXP Rackmount system.

Field Replaceable Units (FRU) B–1

Introduction

Table B–1 Recommended Spares List Unique to the DEC 4000
AXP Rackmount

Part Number

Description

Quantity
per
Assy

54-22569-01

OCP Module

54-20868-01

LDC Power Board

54-21779-01

I/O Daughter Board

12-36202-01

Fans

12-39838-01

Adaptor, SCSI to DSSI

12-30552-01

SCSI Loopback Connector

17-03719-01

Fan Cable Harness Assy

17-03720-01

Disk Cable Assy, 50 cond

70-30956-01

Cable Assy, OCP

17-03080-01

SCSI Power Cable

17-01476-02

LDC Data Cable

B–2 Field Replaceable Units (FRU)

Introduction

Table B–2 Other Field Replaceable Units (FRUs)

Part Number

Description

Quantity
per
Assy

70-30518-01

Back Plane Assy

74-46132-01

Bracket, RRD42/TZ30

74-46133-01

Bracket, RZ2x/TL06

90-11194-01

Key Door, OCP

12-40122-01

Bottom Tray Latch Assy

12-40128-01

Cylinder, Hydraulic

12-40169-01

Finger Stock, Bottom Tray Section A,
8 Segments (4.00")

12-40169-02

Finger Stock, Bottom Tray Section B,
10 Segments (5.00")

12-40169-03

Finger Stock, Bottom Tray Section C,
13 Segments (6.50")

12-40169-04

Finger Stock, Bottom Tray Section D,
16 Segments (8.00")

12-40169-05

Finger Stock, Storage Media
Mounting Plate, 2 Segments (1.00")

12-26922-06

Finger Stock, Bottom Tray Section E,
7 Segments (2.00")

12-28686-27

Finger Stock, Fan Panel Section A,
20 Segments (3.74")

12-28686-26

Finger Stock, Fan Panel Section B,
27 Segments (5.05")

12-28686-25

Finger Stock, Fan Panel Section C
and Front Panel SCSI Filler Plate,
35 Segments (6.54")

12-28686-28

Finger Stock, Fan Panel Section D
and Rear I/O Panel Section A, 15
Segments (2.79")

12-28686-29

Finger Stock, Rear I/O Panel Section
B and Front Panel SCSI Filler Plate,
8 Segments (1.50")

Field Replaceable Units (FRU) B–3

Glossary
ANSI
American National Standards Institute, an organization that
develops and publishes standards for the computer industry.
autoboot
The process by which the system boots automatically.
auxiliary serial port
The EIA 232 serial port on the I/O module of the DEC 4000
AXP Rackmount system. This port provides asynchronous
communication with a device, such as a modem.
availability
The amount of scheduled time that a computing system provides
application service during the year. Availability is typically
measured as either a percentage of ‘‘uptime’’ per year or as
system ‘‘unavailability,’’ the number of hours or minutes of
downtime per year.
BA641
The enclosure that houses the DEC 4000 AXP Rackmount
system. The BA641 is compatible with the departmental
environment and is designed for maximum flexibility in system
configuration. Employing an open system architecture, the
BA641 incorporates a state-of-the-art Futurebus+ area, which
allows for expansion of the DEC 4000 AXP Rackmount system
with options available from Digital and other vendors.

Glossary–1

bandwidth
Bandwidth is often used to express ‘‘high rate of data transfer’’
in an I/O channel. This usage assumes that a wide bandwidth
may contain a high frequency, which can accommodate a high
rate of data transfer.
baud rate
The speed at which data is transmitted over a data line; baud
rates are measured in bits per second.
bit
Binary digit. The smallest unit of data in a binary notation
system, designated as 0 or 1.
boot
Short for bootstrap. Loading an operating system into memory is
called booting.
boot device
The device from which the system bootstrap software is acquired.
boot flags
Boot flags contain information that is read and used by the
bootstrap software during a system bootstrap procedure.
boot server
A system that provides boot services to remote devices such as
network routers and VAXcluster satellite nodes.
bootstrap
See boot.
bus
A group of signals that consists of many transmission lines
or wires. It interconnects computer system components to
provide communications paths for addresses, data, and control
information.

Glossary–2

byte
Eight contiguous bits starting on an addressable byte boundary.
The bits are numbered right to left, 0 through 7.
cache memory
A small, high-speed memory placed between slower main
memory and the processor. A cache increases effective memory
transfer rates and processor speed. It contains copies of data
recently used by the processor and fetches several bytes of data
from memory in anticipation that the processor will access the
next sequential series of bytes.
card cage
A mechanical assembly in the shape of a frame that holds
modules against the system and storage backplanes.
CD-ROM
Compact disc read-only memory. The optical removable media
used in a compact disc reader mass storage device.
central processing unit (CPU)
The unit of the computer that is responsible for interpreting and
executing instructions.
client-server computing
An approach to computing that enables personal computer and
workstation users—the ‘‘client’’—to work cooperatively with
software programs stored on a mainframe or minicomputer—the
‘‘server.’’
clock
A signal used to synchronize the circuits in a computer system.
cluster
A group of systems and hardware that communicate over a
common interface. See also VMScluster system.
console mode
The state in which the system and the console terminal operate
under the control of the console program.

Glossary–3

console program
The code that the CPU executes during console mode.
console subsystem
The subsystem that provides the user interface for a system
when operating system software is not running. The console
subsystem consists of the following components:
console program
console terminal
console terminal port
remote access device
remote access port
Ethernet ports
console terminal
The terminal connected to the console subsystem. The console
is used to start the system and direct activities between the
computer operator and the computer system.
console terminal port
The connector to which the console terminal cable is attached.
CPU
See central processing unit.
DC-DC converter
A device that converts one dc voltage to another dc voltage.
DECchip 21064 processor
The CMOS-4, Alpha AXP architecture, single-chip processor used
on Alpha AXP based computers.
DECnet
Networking software designed and developed by Digital. DECnet
is an implementation of the Digital Network Architecture (DNA).
DEC OSF/1 AXP operating system
A general-purpose operating system based on the Open Software
Foundation OSF/1 1.0 technology. DEC OSF/1 Version 1.2
runs on the range of Alpha AXP systems, from workstations to
servers.
Glossary–4

DRAM
Dynamic random-access memory. Read/write memory that must
be refreshed (read from or written to) periodically to maintain
the storage of information.
DSSI
Digital’s proprietary data bus that uses the System
Communication Architecture (SCA) protocols for direct
host-to-storage communications.
DSSI VMScluster
A VMScluster system that uses the DSSI bus as the interconnect
between DSSI disks and systems.
EEPROM
Electrically erasable programmable read-only memory. A
memory device that can be byte-erased, written to, and read
from. Contrast with FEPROM.
environment variable
Global data structures that can be accessed from console mode.
The setting of these data structures determines how a system
powers up, boots operating system software, and operates.
Ethernet
A local area network (LAN) that was originally developed by
Xerox Corporation and has become the IEEE 802.3 standard
LAN. Ethernet LANs use bus topology.
Ethernet ports
The connectors through which the Ethernet is connected to the
system.
Factory Installed Software (FIS)
Operating system software that is loaded into a system disk
during manufacture. On site, the FIS is bootstrapped in the
system, prompting a predefined menu of questions on the final
configuration.

Glossary–5

fast SCSI
An optional mode of SCSI-2 that allows transmission rates of up
to 10 MB/s. See also SCSI.
FDDI
Fiber Distributed Data Interface. A high-speed networking
technology that uses fiber optics as the transmissions medium.
FEPROM
Flash-erasable programmable read-only memory. FEPROMs can
be bank- or bulk-erased. Contrast with EEPROM.
FIS
See Factory Installed Software.
firmware
Software code stored in hardware.
fixed-media compartments
Compartments that house nonremovable storage media.
front end unit (FEU)
One of four modules in the DEC 4000 AXP Rackmount system
power supply. The FEU converts alternating current from a wall
plug to 48 V dc that the rest of the power subsystem can use and
convert.
full-height device
Standard form factor for 5 1/4-inch storage devices.
Futurebus+
A computer bus architecture that provides performance scalable
over both time and cost. It is the IEEE 896 open standard.
Futurebus+ Profile B
A profile is a specification that calls out a subset of functions
from a larger specification. Profile B satisfies the requirements
for an I/O bus. See also Futurebus+.

Glossary–6

half-height device
Standard form factor for storage devices that are not the height
of full-height devices.
halt
The action of transferring control to the console program.
initialization
The sequence of steps that prepare the system to start.
Initialization occurs after a system has been powered up.
interleaving
See memory interleaving.
LAN (local area network)
A network that supports servers, PCs, printers, minicomputers,
and mainframe computers that are connected over limited
distances.
latency
The amount of time it takes the system to respond to an event.
LED
Light-emitting diode. A semiconductor device that glows when
supplied with voltage.
local area VMScluster system
Digital’s VMScluster configuration in which cluster
communication is carried out over the Ethernet by software that
emulates certain computer interconnect (CI) port functions.
mass storage device
An input/output device on which data is stored. Typical mass
storage devices include disks, magnetic tapes, and floppy disks.
memory interleaving
The process of assigning consecutive physical memory addresses
across multiple memory controllers. Improves total memory
bandwidth by overlapping system bus command execution across
two or four memory modules.

Glossary–7

MIPS
Millions of instructions per second.
mixed-interconnect VMScluster system
Digital’s VMScluster system that uses multiple interconnect
types between systems; for example, CI, Ethernet, DSSI, or
FDDI.
MOP
Maintenance Operations Protocol. The transport protocol for
network bootstraps and other network operations.
multiprocessing system
A system that executes multiple tasks simultaneously.
node
A device that has an address on, is connected to, and is able
to communicate with other devices on the bus. In a computer
network, an individual computer system connected to the
network that can communicate with other systems on the
network.
OCP
Operator control panel. The panel on the top right side of the
DEC 4000 AXP Rackmount system that contains the power,
Reset, and Halt switches and system status lights.
open system
A system that implements sufficient open specifications
for interfaces, services, and supporting formats to enable
applications software to:

Glossary–8

•

Be ported across a wide range of systems with minimal
changes.

•

Interoperate with other applications on local and remote
systems.

•

Interact with users in a style that facilitates user portability.

Open Systems Interconnect standards
Communications reference model defined by the ISO
(International Organization for Standards). The OSI reference
model consists of seven layers and defines protocols for the
physical transmission of data, as well as the structuring and
organization of data, so that it can be sent and received in a
form that can be understood by conforming implementations.
Conformance to the OSI standard will enable communication
among computer systems from different vendors.
OpenVMS AXP operating system
Digital’s open version of the VMS operating system, which runs
on Alpha AXP machines. See also open system.
operating system mode
The state in which the system console terminal is under the
control of the operating system software. Also called program
mode.
operator control panel
See OCP.
PALcode
Alpha AXP Privileged Architecture Library code, written
to support Alpha AXP processors. PALcode implements
architecturally defined behavior.
power down
The sequence of steps that stops the flow of electricity to a
system or its components.
power system controller (PSC)
One of four units in the DEC 4000 AXP Rackmount power
supply subsystem. The H7851AA PSC monitors signals from
the rest of the system including temperature, fan rotation,
and dc voltages, as well as provides power-up and power-down
sequencing to the dc-dc converters and communicates with the
system CPU across the serial control bus.

Glossary–9

power up
The sequence of events that starts the flow of electrical current
to a system or its components.
primary cache
The cache that is the fastest and closest to the processor.
processor module
Module that contains the CPU chip.
program mode
See operating system mode.
RAID
Redundant array of inexpensive disks. A technique that
organizes disk data to improve performance and reliability.
RAID has three attributes:
1. It is a set of physical disks viewed by the user as a single
logical device.
2. The user’s data is distributed across the physical set of
drives in a defined manner.
3. Redundant disk capacity is added so that the user’s data can
be recovered even if a drive fails.
Contrast with striping.
reliability
The probability a device or system will not fail to perform
its intended functions during a specified time interval when
operated under stated conditions.
remote access device
Hardware other than the local console terminal that can access a
system’s console user interface. The remote device is connected
to the system through the system’s auxiliary serial port or
Ethernet.
removable-media compartment
Compartment in the enclosure that houses removable media.

Glossary–10

RISC
Reduced instruction set computer. A computer with an
instruction set that is reduced in complexity.
SCSI
Small Computer System Interface. An ANSI-standard interface
for connecting disks and other peripheral devices to computer
systems. See also fast SCSI.
self-test
A test that is invoked automatically when the system powers up.
serial control bus
A two-conductor serial interconnect that is independent of the
system bus. This bus links the processor modules, the I/O, the
memory, the power subsystem, and the OCP. It reports any failed
devices to the processor module so the processor module can
illuminate LEDs on the OCP.
shadowing
See volume shadowing.
shadow set
In volume shadowing, the set of disks on which the data is
duplicated. Access to a shadow set is achieved by means of a
virtual disk unit. After a shadow set is created, applications and
users access the virtual disk unit as if it were a physical disk.
See also volume shadowing.
SMP
See symmetric multiprocessing.
storage array
A group of mass storage devices, frequently configured as one
logical disk.
stripe set
A group of physical disks that are used for disk striping. See
also striping.

Glossary–11

striping
A storage option that increases I/O performance. With disk
striping, a single file is split between multiple physical disks.
Read and write disk performance is increased by sharing
input/output operations between multiple spindles, which allows
an I/O rate greater than that of any one disk member of the
stripe set. In striping, the loss of any one member of the stripe
set causes loss of the set. Striping is particularly useful for
applications that move large amounts of disk-based information,
for example, graphic imaging. Contrast with RAID.
symmetric multiprocessing (SMP)
A processing configuration in which multiple processors in a
system operate as equals, dividing and sharing the workload.
OpenVMS AXP SMP provides two forms of multiprocessing:
multiple processes can execute simultaneously on different
CPUs, thereby maximizing overall system performance; and
single-stream application programs can be partitioned into
multistream jobs, minimizing the processing time for a particular
program. Contrast with distributed processing.
system bus
The private interconnect used on the DEC 4000 AXP Rackmount
CPU subsystem. This bus connects the B2001 processor module,
the B2002 memory module, and the B2101 I/O module.
system disk
The device on which operating system software resides.
TCP/IP
Transmission Control Protocol/Internet Protocol. A set of
software communications protocols widely used in UNIX
operating environments. TCP delivers data over a connection
between applications on different computers on a network; IP
controls how packets (units of data) are transferred between
computers on a network.
thickwire
An IEEE standard 802.3-compliant Ethernet network made of
standard Ethernet cable, as opposed to ThinWire Ethernet cable.
Also called standard Ethernet. Contrast with ThinWire.

Glossary–12

ThinWire
Digital’s proprietary Ethernet products used for local distribution
of data communications. Contrast with thickwire.
uninterruptible power supply (UPS)
A battery-backup option that maintains ac power if a power
failure occurs.
UPS
See uninterruptible power supply.
VMScluster system
A highly integrated organization of Digital’s VMS systems
that communicate over a high-speed communications path.
VMScluster configurations have all the functions of single-node
systems, plus the ability to share CPU resources, queues, and
disk storage.
volume shadowing
The process of maintaining multiple copies of the same data on
two or more disk volumes. When data is recorded on more than
one disk volume, you have access to critical data even when one
volume is unavailable. Also called disk mirroring.
warm swap
The shutdown and removal and replacement of a failing DSSI
disk from an active bus.
word
Two contiguous bytes (16 bits) starting on an arbitrary byte
boundary. The bits are numbered from right to left, 0 through
15.
write-enabled
A device is write-enabled when data can be written to it.
Contrast with write-protected.
write-protected
A device is write-protected when transfers are prevented from
writing information to it. Contrast with write-enabled.

Glossary–13

Index
A

AC circuit breaker, 1–10
AC present light, 11–7
Accessories box, 10–3
Accessory kit contents, 2–8
Adapters, mass storage, 9–10
Airflow requirements, 2–2
ALLCLASS parameter, 8–24
Allocation classes, changing, 8–21
Alpha AXP architecture
See System architecture
Alpha AXP chip
See DECchip 21064 microprocessor
Antistatic wrist strap, 10–6
Architecture
See System architecture
Attaching slides to chassis, 2–12
Attaching slides to rails, 2–16
Autoboot, 6–5
auto_action environment variable
described, 6–2
displaying current value, 6–5
setting, 6–6
settings, 6–4
uses of, 6–5
Auxiliary serial port, 4–2
changing baud rate setting, 6–15
Availability, system, 8–5

Backplane
installation of, 12–50
removal of, 12–47
10BASE-T connection, 2–39
Baud rate, changing, 10–7
on auxiliary serial port, 6–15
temporarily, on console terminal port,
6–15
Bezel
installation of, 12–8
removal of, 12–5
boot command, 5–5
Boot device
changing default, 6–7, 6–9
disabling default, 6–9
displaying default value, 6–7
Boot flags
default value, 6–10
defined, 6–10
displaying current value, 6–12
setting, 6–13
when to change, 6–12
Boot procedure, 3–7
Boot sequence, troubleshooting, 11–13
bootdef_dev environment variable
described, 6–2
disabling, 6–9
displaying current value, 6–7
setting, 6–7
Booting system software screen, 3–8
examples of, 3–8

Index–1

boot_osflags environment variable
default value, 6–10
described, 6–2
displaying current value, 6–12
setting, 6–13
when to change, 6–12
Bottom FRUs, how to access, 12–10
Bottom tray
how to close, 12–12
installation of, 12–16
opening of, 12–10
removal of, 12–13
Bus expansion ports
location of, 8–17
Buses, storage
extending, 8–16
terminating and extending, 8–18

C
Cable guide, location, 1–4
Cable management system, installation of,
2–22
Caddy
See Compact disc caddy
Card cage
contents, 8–6
lights, 1–8
location, 1–7, 1–12
Cartridges
See CompacTape cartridges;
CompacTape II cartridges;
CompacTape III cartridges; Tape drive
media
cdp command, 5–7, 8–23
Central processing unit
See CPU
Characters, control, supported in console
mode, 4–8
Characters, keyboard, supported in console
mode, 4–6, 4–8
Chassis
attaching slides to, 2–12
mounting on slides, 2–18

Index–2

Checking content of shipment, 2–5
Checking switch settings, 2–24
Clearance, required, 2–2
Compact disc caddy
handling and storage, 7–31
loading a disc into, 7–14
Compact disc drives
See also RRD42 drives
operating, 7–12
CompacTape cartridges
compatibility with TZ30, 7–21
handling and storage, 7–32
inserting into TZ30, 7–24
label position, 7–30
removing from TZ30, 7–26
CompacTape II cartridges
compatibility with TZ30, 7–21
inserting into TZ30, 7–24
label position, 7–30
removing from TZ30, 7–26
CompacTape III cartridges
compatibility with TZ30, 7–21
label position, 7–30
Compatibility, system, with OpenVMS AXP
and DEC OSF/1 AXP, 9–3
Configuration, system, 8–2
DSSI VMScluster, 8–4
Dual CPU, 8–4
Connecting 10BASE-T, 2–39
Connecting console terminal, 2–26
Connecting modem, 2–26
Connecting thickwire Ethernet, 2–38
Connecting ThinWire Ethernet, 2–36
Connecting to network, 2–36
Console commands
See also specific commands
contrasted with VAX commands, 5–3
displaying, 5–3
editing, 4–6
entering, 5–3
extending to a second line, 4–6
levels, 5–1
list of, 5–1
recalling, 4–6

Console mode
See also Console program
control characters supported in, 4–8
defined, 3–2
invoking, 3–11
invoking from a powered-down state, 4–4
invoking from a remote device, 4–5
invoking from across the Ethernet, 4–5
keyboard characters, supported, 4–6
online help in, 5–3
prompt, 4–6
troubleshooting, 11–9, 11–12
uses of, 4–1
Console program, 4–2
Console prompt, 4–6
Console subsystem
components, 4–2, 4–3
finding additional information about,
5–25
Console terminal, 4–2
connecting, 2–26
remote, 4–2, 4–5
Console terminal port, 4–2
changing baud rate setting, 6–15
continue command, 5–10
Control characters, 4–8
Controls, accessing, 1–2
CPU
adapter, 9–10
benefits of two, 8–4
DEC 4000 AXP Rackmount design, 9–2
described, 9–6
modules, location of, 1–7, 1–12
CPU subsystem components, 9–6
Ctrl/A, function in console mode, 4–8
Ctrl/C, function in console mode, 4–8
Ctrl/E, function in console mode, 4–8
Ctrl/H, function in console mode, 4–8
Ctrl/O, function in console mode, 4–8
Ctrl/P, function in console mode, 4–8
Ctrl/Q, function in console mode, 4–8
Ctrl/R, function in console mode, 4–8
Ctrl/S, function in console mode, 4–8

Ctrl/U, function in console mode, 4–8
Ctrl/X, function in console mode, 4–8
Ctrl/Z, function in console mode, 4–8

D
date command, 5–11
Date, setting, 5–11
Datum line, establishing, 2–14
DC on/off switch, 1–6
DC3 lights, 11–8
DC5 lights, 11–8
DDS tapes
and TLZ06 drive, 7–16
inserting into TLZ06, 7–18
label position, 7–30
removing from TLZ06, 7–18
DEC OSF/1 AXP operating system
booting software on, 3–8
compatibility with DEC 4000 AXP
Rackmount, 9–3
shutdown, 3–9
DECchip 21064 microprocessor, 9–2
DECnet protocol, 4–5
Default boot device
changing, 6–7, 6–9
disabling, 6–9
displaying, 6–7
setting, 6–9
Default startup action, setting, 6–6
Devices
changing DSSI device parameters, 8–21
connecting external, 8–16
displaying status of in console mode,
8–11
Diagnostic flow
boot problems, 11–13
console mode problems, 11–12
mass storage problems, 11–15
operating system errors, 11–14
power problems, 11–5
pre-console mode problems, 11–9
Disk drives
See also RRD42 drives
described, 7–7

Index–3

Disk drives (cont’d)
installation of, 12–41
jumper settings, 12–41
mounting, 7–4
operating, 7–7
removal of, 12–39
supported, 12–38
Disk power failure light, 11–7
Documentation, additional, 9–11
for configuration information, 8–30
for console commands, 5–25
for mass storage devices, 7–34
for preparing the system for use, 3–15
for troubleshooting, 11–20
Door, OCP
opening, 1–5
unlocking, 1–5
Drive ID plugs
when to change, 8–20
Drives
See Mass storage devices; Tape drives;
Disk drives
DSSI adapters, function of, 9–10
DSSI buses, terminating and extending,
8–18
DSSI device allocation classes, changing,
8–21
DSSI devices
changing allocation classes for, 8–21
cluster capability, 8–4
DSSI parameters, 8–23
DSSI VMScluster configurations, 8–4
Dual CPU systems, 8–4
DUP driver utility, 8–23

E
Environment variables
defined, 6–1
described, 6–2
displaying current status, 6–2
preset values, 6–2
setting before booting, 3–6, 6–2
tasks after setting, 6–19
tasks before setting, 6–4

Index–4

Equipment slides
attaching to chassis, 2–12
attaching to rails, 2–16
installation of, 2–10
mounting chassis on, 2–18
preparation of, 2–10
Establishing a datum line, 2–14
Ethernet connection, thickwire, 2–38
Ethernet connection, ThinWire, 2–36
Ethernet ports, 4–2
Ethernet, invoking console mode across, 4–5
Expanding the system, 2–30
Extending chassis, how to, 12–5
External devices, 3–4
connecting to the system, 8–7
guidelines for connecting, 8–16
External media expansion ports
described, 8–16
External SCSI
described, 7–7

F
Fan
installation of, 12–36
removal of, 12–35
Fan failure light, 11–7
Fast SCSI
described, 7–7
Fbus
See Futurebus+ subsystem
FEU lights, 11–7
Fingerstock
installation of, 12–44
location of, 12–43
removal of, 12–44
types of, 12–43
Fixed-disk drives, 7–7
See also Disk drives; specific drives
FRUs, location of, 12–2
Futurebus+ subsystem
described, 9–4, 9–11
module location, 1–7, 1–12

G
Grounding wrist strap, 10–6

H
Halt button
location, 1–6
using, 3–11
Halt procedure, 3–11
Halt startup action, 6–5
Head cleaning, 7–32
Head cleaning cassette, 7–33
Help
accessing all types, 3–14
accessing in console mode, 5–3
types available, 3–14
help command, 5–13

I
I/O daughter board assembly
installation of, 12–32
removal of, 12–28
I/O module
described, 9–7
location, 1–7, 1–12
I/O subsystem, 9–4
init command, 5–14
Insert mode, 4–8
Installation
attaching slides to rails, 2–16
cable management system, 2–22
checking content of shipment, 2–5
clearance required, 2–2
connecting console terminal, 2–26
connecting modem, 2–26
connecting power cords, 2–28
connecting to network, 2–36
equipment slides, 2–10
interlock actuator bracket, 2–20
software, 2–35
tools required, 2–4
unpacking, 2–6

Installation of
backplane, 12–50
bezel, 12–8
disk drives, 12–41
fan, 12–36
fingerstock, 12–44
I/O daughter board assembly, 12–32
modules, 12–17
OCP, 12–26
SCSI to DSSI adapters, 12–45
Interlock actuator bracket, installation of,
2–20

J
Jumper settings, disk drives, 12–41

K
Keyboard characters, supported in console
mode, 4–6, 4–8
Keyboard, maintenance, 10–9
Keys
See Keyboard characters; System keys

L
Labeling
mass storage media, 7–30
system name, 10–4
Labels, language, replacing, 10–6
language environment variable
changing default, 6–14
described, 6–2
displaying default, 6–14
Language labels, replacing, 10–6
Language setting
changing default, 6–14
displaying current default, 6–14
LDC board
removal of, 12–33
Lights
operator control panel, 11–10
power supply, 11–5

Index–5

Locating rail mounting holes, 2–14

M
Maintenance, 10–9
of mass storage media and devices, 7–29
of monitor keyboards, 10–9
of system unit, 10–9
Mass storage
actions before operating devices, 7–4
compartments, location, 7–2
devices supported in the DEC 4000 AXP
Rackmount, 7–6
finding additional information on, 7–34
media, labeling, 7–30
Mass storage adapters, 9–10
Mass storage compartments
fixed media, location, 1–13
location, 7–2
removable media, location, 1–4, 1–13
Mass storage devices
See also Drive ID plugs
actions before operating, 7–4
changing DSSI device parameters, 8–21
cluster capability, 8–4
connecting external, 8–16
finding additional information on, 7–34
function of, 9–10
labeling, 7–30
list of, 7–6
maintaining, 7–29
mounting, 7–4
supported in the DEC 4000 AXP
Rackmount, 7–6
Mass storage media
labeling, 7–30
maintaining, 7–29
write-protecting and write-enabling, 7–29
Media
See Mass storage media
Memory modules, 9–7
Memory, displaying, 8–10
Modem, connecting, 2–26

Index–6

Modules
installation of, 12–17
location of, 1–8, 12–17
removal of, 12–17
Modules, system, 8–6
more command, 5–4
Mounting chassis on slides, 2–18
Mounting holes, location of, 2–14

N
Network, connecting to, 2–36
Networked system, 8–2
Node name, labeling, 10–4
NODENAME parameter, 8–24
NT AXP operating system, 9–3

O
OCP
installation of, 12–26
removal of, 12–26
See Operator control panel, 1–4
Online help, in console mode, 5–3
OpenVMS AXP operating system
booting software on, 3–8
compatibility with DEC 4000 AXP
Rackmount, 9–3
shutdown, 3–9
Operating system mode
defined, 3–2
returning to from console mode, 3–11
Operating system software, booting, 3–7
Operating system, reporting failures, 11–14
Operating systems, supported on DEC 4000
AXP Rackmount, 9–3
Operator control panel
controls, 1–6
location, 1–4
operations, 3–9
shutting down system before using, 3–9
using self-test lights on, 3–13
Operator control panel lights, 11–10, 11–11

Options, 8–6
OSF
See DEC OSF/1 AXP operating system
Overstrike mode, 4–8
Overtemperature shutdown light, 11–7

P
PALcode
See show pal command
Parameters, DSSI, 8–21
Port locations, 2–30
Power cords, connecing, 2–28
Power subsystem, 9–4
components, 9–9
location, 1–7, 1–12
Power supply lights, 11–5
Power, diagnostic flow, 11–5
Power-down procedure, 3–13
Power-up procedure, 3–4
actions before beginning, 3–3
task overview, 3–3
Power-up screen, 3–5
Preparing system for operation, 2–24
Preparing the site, 2–2
Preparing the slides, 2–10
Problems
determining type, 11–4
identifying, 11–1, 11–3
Program mode
See Operating system mode, 3–2
PSC lights, 11–7

R
R400X expander, 9–10
Rail mounting holes, location of, 2–14
Reboot procedure, 3–7
Reduced Instruction Set Computer
See RISC technology
Remote access devices
defined, 4–2
using, 4–5
using to log into the console, 4–5

Remote console device
changing baud rate of, 6–15
using, 4–5
Removable media, labeling, 7–30
Removable-media drives
See Tape drives; specific drives
Removal and installation procedures
introduction to, 12–1
Removal of
backplane, 12–47
bezel, 12–5
bottom tray, 12–13
disk drives, 12–39
fan, 12–35
fingerstock, 12–44
I/O daughter board assembly, 12–28
LDC board, 12–33
modules, 12–17
OCP, 12–26
Required clearance, 2–2
Reset button
location, 1–6
using, 3–12
Reset procedure, 3–12
Restart startup action, 6–5
RF-series drives
capacity allowed in R400X, 9–10
changing device parameters for, 8–21
cluster capability, 8–4
described, 7–7
lights, 7–7
troubleshooting, 11–15
write-protecting and write-enabling, 7–8
RF36 drive
components, 7–7
described, 7–7
hardware specifications, 7–6
lights, 7–7
write-protecting and write-enabling, 7–8
RF73 drive
components, 7–7
described, 7–7
hardware specifications, 7–6
lights, 7–7
write-protecting and write-enabling, 7–8

Index–7

RISC technology, 9–2
Root number, 6–10
RRD42 compact disc drives
See RRD42 drives
RRD42 compact discs
caring for, 7–31
handling, 7–31
RRD42 drives
busy light, 7–14
components, 7–12
described, 7–12
hardware specifications, 7–6
inserting a disc into, 7–14
operating, 7–12
removing a disc from, 7–14
troubleshooting, 11–15, 11–17
RZ-series drives
capacity in R400X, 9–10
described, 7–7
lights, 7–7
troubleshooting, 11–15
write-protecting and write-enabling,
RZ26 drive
components, 7–7
described, 7–7
hardware specifications, 7–6
lights, 7–7
write-protecting and write-enabling,
RZ27 drive
hardware specifications, 7–6
RZ36 drive
components, 7–7
described, 7–7
hardware specifications, 7–6
lights, 7–7
write-protecting and write-enabling,
RZ73 drive
components, 7–7
described, 7–7
hardware specifications, 7–6
lights, 7–7
write-protecting and write-enabling,

Index–8

7–8

Screen output, displaying, 5–4
Scrolling, preventing, 5–4
SCSI buses, terminating and extending,
8–18
SCSI port, 2–30
SCSI to DSSI adapters
installation of, 12–45
SCSI, fast
described, 7–7
Self-test
checking results of, 3–13
screen display, 3–5
Self-test status lights
location, 1–6
using, 3–13
Serial port, changing baud rate setting of,
6–15
set command, 5–16
set host command, 5–19
Shipment
checking content of, 2–5
unpacking of, 2–6
Shipping carton contents, 10–3
show boot command
See show bootdef_dev command
show command, 5–21
See also show configuration command;
show device command; show memory
command; show pal command; show
version command
to display environment variables’ status,
6–2
show configuration command, 8–8
show device command, 8–11
show device du pu command, 8–22
show memory command, 8–10
show pal command, 8–13
show version command, 8–13
Single-node system, 8–2
Site Preparation
required clearance, 2–2
verification of, 2–2

Slide assemblies, 2–11
Slides
attaching to chassis, 2–12
attaching to rails, 2–16
installation of, 2–10
mounting chassis on, 2–18
preparation of, 2–10
Software installation, 2–35
Software restart, 6–5
Software screens, 3–8
Software shutdown, 3–9
Standalone system, 8–2
Startup action, setting, 6–6
Startup procedure, 3–4
See also Power-up procedure
Startup screen, 3–8
Startup status, 3–3
Storage subsystem, 9–10
Subsystems, DEC 4000 AXP Rackmount,
9–4
Switch locations, 2–24
Switch settings, checking, 2–24
Symmetric multiprocessing, 8–4
System
characteristics, 9–2
expansion of, 2–30
location of ports, 2–30
preparing for operation, 2–24
turning on power, 2–32
System architecture
design, 9–4
overview, 9–2
System bus, 9–4
System components
bottom, 1–13
front, 1–4
rear, 1–12
top, 1–7
System configuration, 8–2
adding third-party devices, 8–15
additional documentation about, 8–30
displaying in console mode, 8–8
planning, 8–14

System keys, locating, 1–2
System maintenance, 10–9
System modules, 8–6
System modules and options, 1–8
System operation
actions before power-up, 3–3
boot, 3–7
halt, 3–11
overview, 3–2
power-down, 3–13
power-up, 3–4
reboot, 3–7
reset, 3–12
System power down, 3–13
System power-up
actions before beginning, 3–3
procedure, 3–4
task overview, 3–3
System power-up screen, 3–5
System setting, date and time, 5–11
System software
booting, 3–7
shutdown, 3–9
System startup status, determining, 3–3
SYSTEMID parameter, 8–25

T
Tape drive media, labeling, 7–30
Tape drives
See also specific drives
handling and storing, 7–32
mounting, 7–4
TLZ06, 7–16
TZ30, 7–21
Tapes
See CompacTape cartridges;
CompacTape II
cartridges;CompacTape III
cartridges; Tape drive media
test command, 5–24
Test procedure
monitoring self-test, 3–13
sample self-test screen, 3–5

Index–9

Thickwire connection, 2–38
ThinWire connection, 2–36
Third-party devices, adding, 8–15
Time, displaying and modifying, 5–11
TLZ06 drives
cleaning, 7–32
compatible tapes, 7–16
components, 7–16
described, 7–16
hardware specifications, 7–6
inserting a tape into, 7–18
lights (table), 7–20
operating, 7–16
removing a tape from, 7–18
tapes, labeling, 7–30
troubleshooting, 11–15
Tools required, 2–4
Troubleshooting
boot problems, 11–13
console mode problems, 11–12
finding additional information about,
11–20
mass storage devices, 11–15
network problems, 11–18
operating system errors, 11–14
power problems, 11–5
pre-console mode problems, 11–9
TSZ07 drives
finding information on, 7–34
hardware specifications, 7–6
tta0_baud environment variable
described, 6–2
displaying current value, 6–16
tta0_halts environment variable
described, 6–2
tta1_baud environment variable
described, 6–2
displaying current value, 6–16
tta1_halts environment variable
described, 6–2
Turning on system, 2–32
Twisted-pair connection, 2–39
TZ30 drives
cleaning, 7–33
compatible tapes, 7–21

Index–10

TZ30 drives (cont’d)
components, 7–21
described, 7–21
hardware specifications, 7–6
inserting a tape into, 7–24
lights, 7–28
operating, 7–21
removing a tape from, 7–26
tapes, labeling, 7–30
troubleshooting, 11–15
TZ85 drives
hardware specifications, 7–6
tapes, labeling, 7–30
troubleshooting, 11–15

U
Uninterruptible power supply
See UPS
UNITNUM parameter, 8–24
Unpacking shipment, 2–6
UPS, 9–9

V
VAX architecture, 9–3
VAX console commands, 5–3
Ventilation requirements, 2–2
Verifying site preparation, 2–2
VMS
See OpenVMS AXP operating system
VMS operating system, 9–3
See also OpenVMS AXP operating system
VMScluster configurations, 8–4
VT420 terminal, keyboard characters, 4–6

W
Wrist strap, using, 10–6
Write-enabling
defined, 7–29
RF-series drive, 7–8
RZ-series drive, 7–8

Write-protecting
defined, 7–29
RF-series drive, 7–8
RZ-series drive, 7–8

Index–11