Summary of Contents for Digital Equipment VAX 4000 Series
Page 1
VAX 4000 Model 500A/505A/600A/700A/705A Troubleshooting and Diagnostics Order Number: EK–495AB–TS. B01 Digital Equipment Corporation Maynard, Massachusetts...
Page 2
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.
Contents ..........Preface 1 Troubleshooting During Power-Up Autobooting the System Software .
Page 4
Preparing to Run MDM on a DSSI VAXcluster ..3.2.3 3–3 MDM on a DSSI VAXcluster with One TK70 Tape 3.2.3.1 Drive ........3–4 MDM on a DSSI VAXcluster with Two TK70 Tape 3.2.3.2...
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: •...
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...
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 Sets the default R5 boot flag digits BOOT...
Page 9
Problem Possible Cause Corrective Action AC Present indicator lit; Power Control Bus cable Turn on system or expander DC OK indicator not lit. connected to Secondary connected to Power Bus Out (MO) In (SI) connector on connector on power supply. power supply.
Problem Possible Cause Corrective Action Self-tests halt; error System detected error Copy number following question message or error while running self-tests. mark in error message or summary summary displays on and call your Digital service console terminal. representative. Language Selection Baud rate on console Check that baud rate on console Menu does not appear.
1.2.3 Problems Booting from an EF/RF-Series Integrated Storage Element (ISE) Problem Possible Cause Corrective Action Countdown continues System disk Push in and release Write-Protect from 2 through 0; write-protected. button to out (unlit) position. console terminal Make sure Write-Protect button displays operating corresponds to system disk.
1.2.4 Problems Booting from a Tape Drive Problem Possible Cause Corrective Action Countdown does not No tape cartridge in Insert cartridge containing system continue from 2 to 0 tape drive. software into tape drive. or system boots from another device (wrong software displays on console terminal).
Troubleshooting During Normal Operation Problems that occur during normal operation of your system may result from a system defect, faulty setting, or incorrect procedure. The following sections list problems, possible causes, and corrective actions. If the action(s) listed do not solve the problem, call your Digital Services representative. 2.1 System Problems Problem Possible Cause...
Page 14
Problem Possible Cause Corrective Action Alarm sounding and Systems internal Make sure that the system air Over Temperature temperature rising and vents are not blocked. Keep system Warning indicator approaching maximum away from heat sources, Check flashing. limit. room temperature per your Site Preperation manual.
Page 15
Problem Possible Cause Corrective Action Loose or missing DSSI Make sure terminators are terminators. installed properly. Damaged DSSI cable or Replace cable. cable connector. DSSI bus length exceeds Call your Digital Services limit specified in DSSI representative. VMScluster Installation and Troubleshooting manual.
2.2 EF/RF-Series Integrated Storage Element (ISE) Problems Problem Possible Cause Corrective Action Write error message ISE write-protected. Press and release Write-Protect displayed; Write- button. For EF/RF, remove Write- Protect button glows Protect per Appendix B. orange. For EF/RF ISEs, Mounted displays when wrtlck DCL command SHOW...
2.3 RRD3 Compact Disc Drive Problems Problem Possible Cause Corrective Action The drive does not The disc is upside-down Remove the disc from the tray and accept the disc. in the tray or it is not reinsert it properly. placed correctly in the tray.
2.4 TF-Series Tape Drive Problems Problem Possible Cause Corrective Action Tape not software Drive not loaded, or Load drive. Ensure that yellow write-enabled. unloaded by software. indicator is lit. Cartridge has TK50 Use cartridge with correct format. or TK70 format (drive cannot write to those devices).
2.5 TK50 Tape Drive Problems Problem Possible Cause Corrective Action Red light blinking; no Problem in drive. Press Load/Unload button four unusual sounds. times. If problem persists, do not use drive or remove cartridge. Call your Digital Services representative. Red light blinking; Tape leader not coupled Turn off system.
2.6 TK70 Tape Drive Problems Problem Possible Cause Corrective Action Green light blinking Tape leader defective. Pull handle open and remove after tape insertion. cartridge. Use another cartridge. Orange, yellow, and Problem in drive. Press Unload button once. If green lights blinking. orange and green lights go out and yellow light starts blinking, cartridge is unloading.
2.7 TLZ07 Cassette Tape Drive and Autoloader Problems The embedded TLZ07 is only supported when the HSD05 DSSI-to-SCSI bus adapter option is installed in the system backplane. For more information about HSD05 and supported devices, see HSD05 DSSI–to–SCSI Bus Adapter Operation Information for BA400–Based VAX 4000 Systems.
2.8 TZ86 Tabletop Cartridge Tape Subsystem Problems Problem Possible Cause Corrective Action Your system does not Your system is not Configure your system to see the recognize the TZ86. configured to see the ID. For example, use SYSGEN SCSI ID. AUTOCONFIG on the VMS operating system.
Page 23
Problem Possible Cause Corrective Action You are finding fatal or The bus termination Make sure the SCSI bus is nonfatal errors for which or SCSI signal cable terminated. you cannot determine connections may be the cause. incorrect. The ac power source Use an ac outlet for the TZ86 on grounding may be the same ac line that is powering...
2.9 TZ87 Tabletop Cartridge Tape Subsystem Problems Problem Possible Cause Corrective Action Your system does not Your system is not Configure your system to see the recognize the TZ87. configured to see the ID. For example, use SYSGEN SCSI ID. AUTOCONFIG on the VMS operating system.
Page 25
Problem Possible Cause Corrective Action You are finding fatal or The bus termination Make sure the SCSI bus is nonfatal errors for which or SCSI signal cable terminated. you cannot determine connections may be the cause. incorrect. The ac power source Use an ac outlet for the TZ87 on grounding may be the same ac line that is powering...
Running the MicroVAX Diagnostic Monitor (MDM) The MicroVAX Diagnostic Monitor (MDM) is an optional software package containing diagnostic tests that isolate and identify faults in your system. MDM also lets you display your system configuration and test how devices work together.
Note MDM tests a tape or diskette drive only after the medium (tape or diskette) is inserted into the drive. • MDM checks devices on the system as well as the system and interconnects. • MDM checks terminal interfaces (but not terminals) by means of feedback connectors.
Refer to the MicroVAX Diagnostic Monitor Ethernet Server User’s Guide at this time. After you install and downline load MDM, refer again to that manual for instructions on running MDM. Note If you have a diskless or tapeless system that is not part of a local area network, you cannot run MDM.
Use the procedure in Section 3.2.3.2 to prepare to run MDM in a DSSI VAXcluster with a TK70 tape drive in each host. 3.2.3.1 MDM on a DSSI VAXcluster with One TK70 Tape Drive To run MDM on a DSSI VAXcluster with one TK70 tape drive (one or more tapeless hosts): •...
Run MDM as you did for the first system. 3.2.3.2 MDM on a DSSI VAXcluster with Two TK70 Tape Drives To run MDM on a DSSI VAXcluster with two tape drives in each system: Note You can also use the MDM Hard Disk Kit as described in the previous section.
3.3 Starting MDM You must start MDM differently for different media: If you are booting MDM from a tape drive, read Section 3.3.1. If you are booting MDM from an RRD-series disc drive, read Section 3.3.2. If you are booting MDM from a hard disk or an EF/RF-series ISE, refer to the MicroVAX Diagnostic Monitor Hard Disk User’s Guide.
3.3.1.1 Booting MDM Manually Use this procedure to boot MDM from a TF-series, TK50 or TK70 tape drive. 1. If software is installed on your system: a. Warn all users to log off. b. Perform system shutdown as described in your software manuals. 2.
3. Make sure the write protect switch on the tape cartridge is in the write- protect position. 4. Remove any removable disks, and place all fixed-disk drives and RF-series ISEs off line. 5. Write-protect all disk drives and EF/RF-series ISEs. 6.
7. Tell your system to load MDM from the disc: For a KZQSA adapter, enter the command BOOT DKxnnn, where x is the adapter designator and nnn is the drive unit number. For a KRQ50 controller, enter the command BOOT/100 DUcu, where c is the controller designator and u is the drive unit number.
Select an option by typing its number and Return The next six sections describe the options on the Main Menu. 3.5.1 Test the System Option The Test the System option tests the devices it sees in your system and how they work together.
Ethernet controller If your system has serious problems, the following message appears. All devices disabled, no tests run. Report that message to your Digital Services representative. After a failure message appears, the testing stops. After all devices pass the first part of the test, the exerciser tests begin. Those tests take about 4 minutes and test how the devices work together.
Page 38
Up to two lines of information are provided for each device: One line lists the name of the device and gives a brief description. A second line may indicate the revision level of the device. The revision level can refer to hardware or microcode. For example, the KA6nn CPU described above is at revision 3.9 for microcode (MC=01).
A Digital device that has no diagnostic is attached to your system. That can occur if a device not supported on your system is attached. A non-Digital device is attached to your system. After all devices are listed, you can return to the Main Menu by pressing Return From the Main Menu you can exit MDM as described in Section 3.6 or you can select one of the other options.
The IOADDRES function gives you a list of standard CSR addresses and interrupt vectors that MDM uses in testing devices. The first available CSR and interrupt vector for configuring devices with a nonstandard address is also given. IOADDRES does not look at devices on the bus; it lists devices supported by Digital Customer Services.
3.5.6 Select Single Device Tests Option The Select Single Device Tests option lets you run tests for a single device. • A functional test is performed on the device circuits. • An exerciser test ensures that the device works properly. After you select this option, the diagnostics are prepared for testing.
This shows an example of a successful test. BEGIN FUNCTIONAL TEST Device Result CPUA ....PASSED BEGIN EXERCISER TEST Results are reported at the end of the testing. SINGLE DEVICE TEST PASSED If a device fails the test, you receive a failure message which identifies: The device tested When the failure occurred The field-replaceable unit (FRU)
Page 43
If you ran MDM on a new system, you are ready to install your software. Set the write protect button to write-enable and then follow the instructions in your software manuals. If you ran MDM on a system containing software, you must reboot that software. You can reboot your system software in one of two ways: •...
System Controls and Indicators The illustrations in this appendix show the controls and indicators on your system: Figure A–1: System Control Panel and Power Supply Figure A–2: Integrated Storage Element and Console Module Figure A–3: TK70 and TK50 Tape Drives Figure A–4: TF-Series and TLZ04 Tape Drives System Controls and Indicators A–1...
Figure A–1 System Control Panel and Power Supply System Control Panel Over Temperature Warning Indicator DC OK Indicator Halt Button Restart Button Power Supply Power Switch AC Present Indicator DC OK Indicator Fan Failure Indicator Over Temperature Condition Indicator Power Bus Connectors Power Cable Connector...
Write-Protecting an EF/RF-Series ISE You may want to write-protect an ISE containing sensitive data you do not want changed or accidentally erased. For all 3.5-inch drives, you write-protect an ISE by setting the Write-Protect button to in (lit). For the EF/RF ISE, which has no Write-Protect button, you set write-protection through VMS commands or through firmware commands in console mode, explained later in this section.
Dismounting, and then remounting the device (without using the /NOWRITE qualifier), will write-enable the device. Use the VMS DCL command SHOW DEVICE DI to check the protection status of the drive. A write-protected drive will show a device status of Mounted wrtlck Refer to your VMS documentation for more information on using the MOUNT Utility.
Page 53
Caution Halting your system without following the shutdown procedure described in your system software manuals may result in loss of data. b. Access the DUP driver by setting host to the specific device you want to write protect. Use the following command for embedded DSSI. SET HOST/DUP/DSSI/BUS:<bus_number>...
Page 54
DUP driver PARAMS> utility for the specified device. This is an example of setting a hardware write-protect through firmware. >>>SET HOST/DUP/DSSI/BUS:0 1 PARAMS Starting DUP server... Copyright (c) 1992 Digital Equipment Corporation PARAMS>SET WRT_PROT 1 PARAMS>WRITE PARAMS>SHOW WRT_PROT Parameter Current...
Page 55
You can verify that the device is write-protected while running VMS—when you issue the VMS DCL command SHOW DEVICE DI, a write-protected drive will show a device status of . If you issue the VMS command SHOW Mounted wrtlck DEVICE/FULL, a write-protected drive will be listed as software write-locked Note You cannot remove hardware write-protection using the VMS MOUNT...
Page 61
Write-enabling a storage element, B–1 an EF/RF storage element, B–1 to B–5 an RF35 storage element, B–1 to B–5 Write-protecting a storage element, B–1 an EF/RF storage element, B–1 to B–5 an RF35 storage element, B–1 to B–5 Index–5...
Page 63
Reader’s Comments VAX 4000 Model 500A/505A/600A/700A/705A Troubleshooting and Diagnostics EK–495AB–TS. B01 Your comments and suggestions help us improve the quality of our publications. Thank you for your assistance. I rate this manual’s: Excellent Good Fair Poor Accuracy (product works as manual says) Completeness (enough information) Clarity (easy to understand) Organization (structure of subject matter)
Page 64
United States BUSINESS REPLY MAIL FIRST CLASS PERMIT NO. 33 MAYNARD MASS. POSTAGE WILL BE PAID BY ADDRESSEE DIGITAL EQUIPMENT CORPORATION Information Design and Consulting MRO1–3/K10 200 FOREST STREET MARLBORO, MA 01752-3011 Do Not Tear – Fold Here...
Need help?
Do you have a question about the VAX 4000 Series and is the answer not in the manual?
Questions and answers