Digital Equipment VAX 4000 Series Guide

VAX4000
Model500A/505A/600A/700A/705A
TroubleshootingandDiagnostics
Order Number: EK–495AB–TS. B01
Digital Equipment Corporation
Maynard, Massachusetts

First Printing, December 1991
Revised, February 1992
Revised, April 1992
Revised, July 1992
Revised, July 1993
Revised, July 1994
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, if any, 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 or equipment that is not supplied by Digital Equipment Corporation or its
affiliated companies.
Restricted Rights: Use, duplication or disclosure by the U.S. Government is subject to restrictions
as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause
at DFARS 252.227–7013.
Copyright © Digital Equipment Corporation 1991, 1992, 1993, 1994. All Rights Reserved.
The Reader’s Comments form at the end of this document requests your critical evaluation to assist
in preparing future documentation.
The following are trademarks of Digital Equipment Corporation: CompacTape, CX, DDCMP, DEC,
DECconnect, DECdirect, DECnet, DECscan, DECserver, DECUS, DECwindows, DELNI, DEMPR,
DESQA, DESTA, DSRVB, DSSI, IVAX, KDA, KLESI, KRQ50, MicroVAX, MSCP, Q–bus, Q22–bus,
RA, RQDX, RV20, SA, SDI, ThinWire, TK, TMSCP, TQK, TS05, TU, VAX, VAX 4000, VAXcluster,
VAX DOCUMENT, VAXELN, VAXlab, VAXserver, VMS, VT, and the DIGITAL logo.
All other trademarks and registered trademarks are the propery of their respective holders.
FCC NOTICE: The equipment described in this manual generates, uses, and may emit radio
frequency. The equipment has been type tested and found to comply with the limits for a Class A
computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide
reasonable protection against such radio frequency interference.
Operation of the equipment in a residential area may cause interference, in which case the user
at his own expense will be required to take whatever measures may be required to correct the
interference.
S2580
This document was prepared using VAX DOCUMENT Version 2.1.

Contents
Preface ................................................ v
1 Troubleshooting During Power-Up
1.1 Autobooting the System Software . . . . . . . . . . . . . . . . . . . 1–1
1.2 Troubleshooting Power-Up Problems . . . . . . . . . . . . . . . . . 1–2
1.2.1 Problems During Self-Tests . . . . . . . . . . . . . . . . . . . . . 1–2
1.2.2 General Problems During Boot Sequence . . . . . . . . . . . 1–4
1.2.3 Problems Booting from an EF/RF-Series Integrated
Storage Element (ISE) . . . . . . . . . . . . . . . . . . . . . . . . . 1–5
1.2.4 Problems Booting from a Tape Drive . . . . . . . . . . . . . . 1–6
2 Troubleshooting During Normal Operation
2.1 SystemProblems ................................ 2–1
2.2 EF/RF-Series Integrated Storage Element (ISE)
Problems ...................................... 2–4
2.3 RRD3 Compact Disc Drive Problems . . . . . . . . . . . . . . . . . 2–5
2.4 TF-Series Tape Drive Problems . . . . . . . . . . . . . . . . . . . . . 2–6
2.5 TK50 Tape Drive Problems . . . . . . . . . . . . . . . . . . . . . . . . 2–7
2.6 TK70 Tape Drive Problems . . . . . . . . . . . . . . . . . . . . . . . . 2–8
2.7 TLZ07 Cassette Tape Drive and Autoloader Problems . . . . 2–9
2.8 TZ86 Tabletop Cartridge Tape Subsystem Problems . . . . . 2–10
2.9 TZ87 Tabletop Cartridge Tape Subsystem Problems . . . . . 2–12
3 Running the MicroVAX Diagnostic Monitor (MDM)
3.1 MDMLimitations ............................... 3–1
3.2 PreparingtoRunMDM........................... 3–2
3.2.1 Preparing to Run MDM on a Diskless or Tapeless
System..................................... 3–2
3.2.2 Preparing to Run MDM on an EF/RF-Series
Integrated Storage Element (ISE) or Hard Disk . . . . . 3–3
iii

3.2.3 Preparing to Run MDM on a DSSI VAXcluster . . . . . . 3–3
3.2.3.1 MDM on a DSSI VAXcluster with One TK70 Tape
Drive ................................... 3–4
3.2.3.2 MDM on a DSSI VAXcluster with Two TK70 Tape
Drives .................................. 3–5
3.3 StartingMDM .................................. 3–6
3.3.1 Tape Drive Instructions . . . . . . . . . . . . . . . . . . . . . . . . 3–6
3.3.1.1 Booting MDM Manually . . . . . . . . . . . . . . . . . . . . . 3–7
3.3.1.2 Booting MDM Automatically . . . . . . . . . . . . . . . . . 3–7
3.3.2 RRD-Series Disc Instructions . . . . . . . . . . . . . . . . . . . . 3–8
3.4 MDM Introductory Display . . . . . . . . . . . . . . . . . . . . . . . . 3–9
3.5 MainMenuOptions.............................. 3–9
3.5.1 Test the System Option . . . . . . . . . . . . . . . . . . . . . . . . 3–10
3.5.2 Display System Configuration and Devices Option . . . 3–11
3.5.3 Display the System Utilities Menu Option . . . . . . . . . . 3–13
3.5.3.1 IOADDRESFunction....................... 3–13
3.5.3.2 Update Drive Unit Number for RRD-Series
Function................................. 3–14
3.5.4 Display the Service Menu Option . . . . . . . . . . . . . . . . . 3–14
3.5.5 Display the Connect/Ignore Menu Option . . . . . . . . . . 3–14
3.5.6 Select Single Device Tests Option . . . . . . . . . . . . . . . . 3–15
3.6 ExitingMDM................................... 3–16
A System Controls and Indicators
B Write-Protecting an EF/RF-Series ISE
B.1 Software Write-Protect for EF/RF-Series ISEs . . . . . . . . . . B–1
B.2 Hardware Write-Protect for EF/RF ISEs . . . . . . . . . . . . . . B–2
Index
Figures
A–1 System Control Panel and Power Supply . . . . . . . . . . . A–2
A–2 EF/RF-Series ISE and Console Module . . . . . . . . . . . . A–3
A–3 TK70 and TK50 Tape Drives . . . . . . . . . . . . . . . . . . . . A–4
A–4 TF-Series Tape Drive . . . . . . . . . . . . . . . . . . . . . . . . . . A–5
iv

Preface
Troubleshooting is the process of isolating and diagnosing problems. When
your system does not operate as described in your Operation manual, use the
information in this manual to isolate and diagnose the problem.
This manual contains three chapters and two appendixes:
• Chapter 1 lists problems you may experience at power-up and provides
corrective actions.
• Chapter 2 lists problems you may experience during normal operation and
provides corrective actions.
• Chapter 3 tells you how to run the MicroVAX Diagnostic Monitor (MDM),
a diagnostic tool you can use to test your system periodically or to isolate a
particular problem.
• Appendix A contains illustrations showing the location of your system controls
and indicators.
• Appendix B describes how to write-protect your EF/RF-Series ISE.
If the corrective actions suggested in Chapters 1 and 2 do not solve the problem,
call your Digital Services representative.
The following conventions are used in this manual.
Convention Meaning
Key A terminal key used in text and examples. For example, Break
indicates that you press the Break key on your terminal keyboard.
Ctrl/C Hold down the Ctrl key while you press the C key.
NOTE Provides general information about the current topic.
CAUTION Provides information to prevent damage to equipment or software.
v

1
Troubleshooting During Power-Up
After you turn on your system, the processor performs a series of self-tests
and startup routines. After successful completion of the self-tests, if the Break
Enable/Disable switch is set to disable (down), your system autoboots system
software.
1.1 Autobooting the System Software
Your system boots automatically (autoboots) from a specified drive if you have
specified a boot device by way of the command SET BOOT device-name from
console mode. Your system continues to boot from the specified drive each time
it is turned on, until you specify a different device by entering the SET BOOT
device-name command again.
Your system stores the following console parameters in nonvolatile memory.
Parameter Values Comment
Language 1 - 15 Sets the language and the
keyboard type used under the
console
ControlP 0,1 (disabled,enabled) Sets ControlP as a halt condition
instead of a break, if the break
enable switch is set for enable.
Halt 0 - 4 (or DEFAULT,
RESTART, REBOOT,
HALT, RESTART_
REBOOT)
Defines the action on halt
DSSI_ID Bus 0/A 0 - 7 The DSSI node ID for the CPU
DSSI adapter 0
DSSI_ID Bus 1/B 0 - 7 The DSSI node ID for the CPU
DSSI adapter 1
Troubleshooting During Power-Up 1–1

Parameter Values Comment
DSSI_ID Bus 2/C 0 - 7 The DSSI node ID for the CPU
DSSI adapter 2
DSSI_ID Bus 3/D 0 - 7 The DSSI node ID for the CPU
DSSI adapter 3
BFLG Hex number up to 8
digits Sets the default R5 boot flag
BOOT Boot device Sets the default boot device
If ac power is lost, this information is retained. When ac power is restored,
type SHOW SAVED_STATE at the >>> prompt. Your system displays these
parameters with the values they had at the time of the ac power loss. You can
then change any of these values. To boot your system, type Bat the >>> prompt.
If you do not enter the SET BOOT device-name command, your system boots
from the Ethernet port, EZA0.
1.2 Troubleshooting Power-Up Problems
Refer to the descriptions of problems and corrective actions in the following
sections. If the action(s) listed do not solve the problem, call your Digital service
representative.
1.2.1 Problems During Self-Tests
Problem Possible Cause Corrective Action
No response when
Power switch turned
on; AC
Present indicator not lit.
System not plugged in. Set Power switch to 0. Plug in
system. Set Power switch to 1.
No power at wall outlet. Use different wall outlet or check
circuit breaker controlling power to
wall outlet.
Power switch (circuit
breaker) tripped (in
position 0).
Wait 1 minute, then set Power
switch to position 1. If it trips
again, call your Digital Services
representative.
Power cable incorrectly
installed. Set Power switch to 0. Check that
cable is fully seated in socket. Set
Power switch to 1.
1–2 Troubleshooting During Power-Up

Problem Possible Cause Corrective Action
AC Present indicator lit;
DC OK indicator not lit. Power Control Bus cable connected to Secondary
In (SI) connector on
power supply.
Turn on system or expander
connected to Power Bus Out (MO)
connector on power supply.
BA400-series expander
not turned on. Turn on expander.
Power supply or module
failure. Call your Digital Services representative.
System has power; AC
Present and DC OK
indicators lit; nothing
displays on console
terminal.
Console terminal off. Turn on console terminal.
Console terminal off
line. Put terminal on line as described
in terminal document.
Hold key activated. Deactivate hold key.
Console terminal cable
incorrectly installed. Make sure cable is installed
properly at both ends.
Console terminal setup
not done correctly. Reread setup instructions in terminal manual.
Baud rate of system and
terminal do not match. Set terminal baud rate to match system rate.
Power-Up Mode switch
on console module set to
T.
Set that switch to Run (indicated
by arrow).
Terminal defective. Turn off terminal and turn it on
again. If it fails self-tests, call your
Digital Services representative.
If printer connected to
obtain copy of console
interaction, fault in
printer.
Turn off printer and turn it on
again. If it fails self-tests, call your
Digital Services representative.
Problem in CPU. Call your Digital Services
representative.
System has power; DC
OK indicator lit; nothing
displays on console
terminal; LED on
console module displays
E or F.
Problem in CPU. Call your Digital Services
representative.
Troubleshooting During Power-Up 1–3

Problem Possible Cause Corrective Action
Self-tests halt; error
message or error
summary displays on
console terminal.
System detected error
while running self-tests. Copy number following question mark in error message or summary
and call your Digital service
representative.
Language Selection
Menu does not appear. Baud rate on console terminal different from
baud rate on system.
Check that baud rate on console
terminal agrees with system rate.
Terminal does not
support multinational
character set (MCS).
Obtain terminal that supports
MCS, or use the default language
(English). If this is not a problem
continue.
1.2.2 General Problems During Boot Sequence
Problem Possible Cause Corrective Action
System returns to BOOT
prompt after 4 minutes. Sanity timer enabled on DESQA module. Disable sanity timer as described
in DESQA Option Installation
Guide.
>>> displays on console
terminal. Break Enable/Disable switch set to enable (up);
system in console mode.
To autoboot, set Break Enable
/Disable switch on console module
to disable (down). Reset system by
pressing Restart button on system
control panel. To boot manually
from console mode, use BOOT
device-name command.
>>> displays on console
terminal; Break Enable
/Disable switch set to
disable (down).
User-defined halt action
set to HALT. From console mode, enter SET
HALT DEFAULT command.
?54 RETRY displays
twice on console
terminal.
No bootable medium
found. See actions listed for boot device in
subsequent sections.
Countdown does not
continue from 2 through
0; Break Enable/Disable
switch set to disable
(down).
System cannot load
software from disk
drive,
tape drive or Ethernet.
See actions listed for boot device in
subsequent sections.
1–4 Troubleshooting During Power-Up