DEC 4000 Model 600 Series Owner’s Guide Order Number: EK–KN430–OP.
First Printing, October 1992 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license.
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.6 6.7 48 49 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.6 6.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix 1 Getting Started Introducing the DEC 4000 AXP Server The New Arrival . . . . . . . . . . . . . . In This Chapter . . . . . . . . . . . . . . . Components and Controls . . . . . . . . . . Gaining Access to Controls . . . . . . . Opening System Doors . . . . . . . . . . Components: Front of System . . . . Operator Control Panel . . . . . . . . . Components: Rear of System . . . . .
Power Down the System . Monitor Self-Test Results Help . . . . . . . . . . . . . . . . . . . . Getting Help . . . . . . . . . . References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . Description . . . . . . . . . . Parameters . . . . . . . . . Flags . . . . . . . . . . . . . . Examples . . . . . . . . . . . Reference . . . . . . . . . . . continue . . . . . . . . . . . . . . . Synopsis . . . . . . . . . . . . Description . . . . . . . . . . Examples . . . . . . . . . . . date . . . . . . . . . . . . . . . . . . Synopsis . . . . . . . . . . . . Description . . . . . . . . . . Parameters . . . . . . . . . Examples . . . . . . . . . . . help or man . . . .
Environment Variables . Examples . . . . . . . . . . . Reference . . . . . . . . . . . test . . . . . . . . . . . . . . . . . . . Synopsis . . . . . . . . . . . . Description . . . . . . . . . . Examples . . . . . . . . . . . References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the Language (language) . . . . . . . . . . . . . . . . . . . Do I Need to Set the Language? . . . . . . . . . . . . . . . . Possible Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . .
TLZ06 Lights . . . . . . . . . . . . . . . . . . . . . . . Operating the TZ85 Tape Drive . . . . . . . . . . . . TZ85 Description . . . . . . . . . . . . . . . . . . . . Compatible Tapes . . . . . . . . . . . . . . . . . . . . Inserting a Tape into the TZ85 . . . . . . . . . Removing a Tape from the TZ85 . . . . . . . . TZ85 Lights . . . . . . . . . . . . . . . . . . . . . . . . Operating the TZ30 Tape Drive . . . . . . . . . . . . TZ30 Description . . . . . . . . . . . . . . . . . . . . Compatible Tapes .
Mass Storage Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . External Mass Storage Devices . . . . . . . . . . . . . . . . . . . Network Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identifying Mass Storage Devices . . . . . . . . . . . . . . . . . . . . DSSI and SCSI Devices . . . . . . . . . . . . . . . . . . . . . . . . . Buses Associated with Each Compartment . . . . . . . . . . Drive IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 Learning More About Your System Chapter Description . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . In This Chapter . . . . . . . . . . . . . . . . . . . . . System Features . . . . . . . . . . . . . . . . . . . . . . . What Makes It a DEC 4000 AXP System? . Alpha AXP Architecture . . . . . . . . . . . . . . . RISC Technology . . . . . . . . . . . . . . . . . . . . Support of Multiple Operating Systems . . . Integration with Existing Technology . . .
Remove System Doors . . . . Move the System . . . . . . . . Antistatic Wrist Strap . . . . Changing the Baud Rate . . Maintaining the System . . . . . Overview . . . . . . . . . . . . . . Environmental Guidelines . Liquid on the System Unit . References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–19 Glossary Index Examples 1–1 1–2 5–1 6–1 6–2 6–3 6–4 6–5 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 . . . . . . . . . . . . . . . . . . .
5–7 5–8 5–9 5–10 5–11 5–12 5–13 5–14 5–15 6–1 6–2 6–3 6–4 6–5 6–6 6–7 6–8 6–9 7–1 8–1 8–2 8–3 8–4 8–5 9–1 9–2 9–3 Inserting and Removing a Tape: TLZ06 . . . . . . . . . . . . TZ85 Drive and Compatible Tape . . . . . . . . . . . . . . . . . Inserting a Tape into the TZ85 . . . . . . . . . . . . . . . . . . Removing a Tape from the TZ85 . . . . . . . . . . . . . . . . . TZ30 Tape Drive and Compatible Tape . . . . . . . . . . . . Inserting a Tape into the TZ30 . . . . . . . . . . . . . . . . . .
5–2 5–3 5–4 6–1 7–1 9–1 9–2 9–3 9–4 9–5 9–6 9–7 9–8 9–9 9–10 9–11 9–12 9–13 9–14 xviii TLZ06 Light Summary . . . . . . . . . . . . . . . . . . . . . TZ85 Light Summary . . . . . . . . . . . . . . . . . . . . . . TZ30 Light Summary . . . . . . . . . . . . . . . . . . . . . . Mass Storage Compartments and Devices . . . . . . DEC 4000 AXP Subsystems . . . . . . . . . . . . . . . . . How to Identify a Problem . . . . . . . . . . . . . . . . . . Steps to Resolving Problems . . . . . . . . . . . . . . . .
Preface Purpose of This Guide This guide describes how to operate, troubleshoot, and maintain the DEC 4000 AXP system. Before You Use This Guide This guide assumes that you are ready to operate your system. Before using this guide, you or a Digital service representative should complete the following tasks: Who Should Use This Guide • Prepare your site so that it meets the requirements described in the DEC 4000 Model 600 Series Site Preparation Checklist. • Install the system at your site.
Structure of This Guide Finding More Information xx This guide contains information about how to use your system to best advantage: • Chapter 1 introduces the system and describes basic system management tasks. • Chapter 2 describes how to use the console mode environment. • Chapter 3 describes the console commands. • Chapter 4 describes how to set environment variables. • Chapter 5 describes how to operate mass storage devices.
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 . bold type In the online book (Bookreader), bold type in examples indicates commands and other instructions that you enter at the keyboard.
1 Getting Started Introducing the DEC 4000 AXP Server The New Arrival Congratulations on the purchase of your new DEC 4000 AXP system! Getting Started 1–1 Getting Started The DEC 4000 AXP system is a high-performance superserver for multi-user environments.
Introducing the DEC 4000 AXP Server In This Chapter This chapter covers the following information: • Components and Controls • System Operation: Overview • Starting the System • Using the Operator Control Panel • Help Components and Controls Gaining Access to Controls System components and controls are located at the front and rear of the system. You access these system features by opening the front and rear system doors.
Components and Controls Figure 1–1 Location of System Keys MLO-008861 Getting Started 1–3
Components and Controls Opening System Doors ! To open the front or rear door, unlock the door and pull the upper right edge toward you as shown in Figure 1–2.
Components and Controls Components: Front of System Figure 1–3 shows the components on the front of the system.
Components and Controls Operator Control Panel Figure 1–4 shows the operator control panel on the front of the system. Figure 1–4 Operator Control Panel DC On/Off Switch DC Power Light Self-Test Status Lights Reset Halt 6-1 3 2 1 MEM 0 0 1 CPU I/O MLO-008872 For information about mass storage controls, refer to devicespecific information in Chapter 5 of this guide.
Components and Controls Components: Rear of System Figure 1–5 shows the major components at the rear of the system.
Components and Controls Figure 1–6 shows the module locations, lights, switches, and connectors on the card cage at the rear of the system.
Components and Controls Power Subsystem Figure 1–7 shows the lights, switches, and connectors on the power supply at the rear of the system.
System Operation: Overview System Operation: Overview Two Levels 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.
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.
Starting the System • Local printer (optional) • Storage expander boxes (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 1–12 Getting Started Action 1 Find the AC circuit breaker at the rear of the system. Press the switch to the on ( | ) position. The AC power light comes on. 2 Find the DC on/off switch at the front of the system.
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 9 for troubleshooting information. Figure 1–8 shows an example of a system startup screen during self-tests. The screen shows the status and result of the self-tests.
Starting the System Figure 1–9 Sample Power-Up Configuration Screen CPU 0 CPU 1 Memory 0 Memory 1 Memory 2 Memory 3 Ethernet 0 Ethernet 1 TM DECchip 21064 PALcode Xn.nn, Firmware Tn.
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 4. Boot Operating System Software Boot operating system software as follows: Step 1 Action Enter boot or b at the console prompt. >>> b A booting system software screen (Example 1–1 or Example 1–2) is displayed on your console terminal.
Starting the System Example 1–1 shows a system booting OpenVMS AXP software. Example 1–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: System device: Free Blocks: System type: DEC 4000 Model 610 RZ57 - _DKIO: 1804734 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.
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.
Using the Operator Control Panel Use Figure 1–10 to locate the controls that are identified in the procedures on the following pages. Figure 1–10 Operator Control Panel DC On/Off Switch DC Power Light Self-Test Status Lights Reset Halt 6-1 3 2 1 MEM 0 0 1 CPU I/O MLO-008872 Invoke Console Mode You may want to invoke console mode in order to set environment variables or to enter other console commands.
Using the Operator Control Panel Invoke console mode as follows: Step 1 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.
Using the Operator Control Panel Reset the System Pressing the Reset button (shown in Figure 1–10) 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.
Using the Operator Control Panel Power Down the System You use the DC on/off switch (shown in Figure 1–10) in conjunction with 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.
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.
References References The following table describes where to find additional introductory information.
2 Console Subsystem Chapter Description This chapter focuses on the console subsystem. The console subsystem provides the DEC 4000 AXP user interface when operating system software is not running or is halted.
Components of the Console Subsystem Components of the Console Subsystem Console Subsystem Figure 2–1 identifies the components of the console subsystem. • Console program — Software that executes when operating system software is not executing; provides the user interface, interprets and executes user commands. When the console program is executing, the system is running in console mode. 2–2 Console Subsystem ! — module in the card cage at the rear of the • I/O module system.
Components of the Console Subsystem Figure 2–1 Console Subsystem 1 3 2 4 5 F1 di gi t al TM SCHOLAR Plus Data Talk Test Loop Off On SD RD CD TR SI 0 F1 6 F3 7 2 F4 MLO-008871 Console Subsystem 2–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.
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.
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.
Console Mode User Interface Callout ! Key Function
Console Mode User Interface Control Characters 2–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.
3 Console Commands What Are the Console Commands? 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 3–1 lists the basic console commands.
What Are the Console Commands? Table 3–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 continue Resumes program execution. date date [yyyymmddhhmm.ss] Displays or sets the current date and time. help help [command . . . ] Displays online help using console commands.
Entering Console Commands Entering Console Commands New Console Commands The DEC 4000 AXP system features new console commands. Most of the DEC 4000 AXP console commands are similar, but not identical to, the console commands supported on VAX systems. (See Table 3–2.) If you are familiar with VAX console commands, familiarize yourself with the new commands before proceeding.
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.
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.
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 4 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.
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.
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 hose 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.
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.
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.
date date Synopsis Display or modify the current date and time. date [yyyymmddhhmm.ss] Description Displays or modifies the current time and date. 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.
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.
help or man help or man Synopsis Display information about console commands. help or man [command . . . ] Description The help command, interchangeable with the man command, 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.
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 ...
man man See help.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
4 Setting Environment Variables Chapter Description This chapter describes the DEC 4000 AXP 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 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? 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.
Overview: Do I Need to Set Environment Variables? Table 4–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.
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 1. • Determined which variables, if any, you wish to set. Each of the following sections in this chapter describes a particular environment variable.
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.
Changing the Default Startup Action (auto_action) Set the Default Startup Action To set the default startup action, complete the following steps: Step 1 2 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).
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.
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.
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 1 Determine the device or devices that you wish to set as the default.
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 3) or by setting the boot_osflags environment variable as described in this section. The default boot flag setting is null.
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 1 0 Bootstrap conversationally (enables you to modify SYSGEN parameters in SYSBOOT). 2 1 Map XDELTA to running system. 4 2 Stop at initial system breakpoint. 8 3 Perform diagnostic bootstrap. 10 4 Stop at the bootstrap breakpoints. 20 5 Omit header from secondary bootstrap image.
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 a Load operating system software from the specified boot device (autoboot). Boot to multiuser mode. i Prompt for the name of a file to load and other options (boot interactively).
Setting Boot Flags (boot_osflags) Set Boot Flags Set boot flags as follows: Step 1 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.
Setting the Language (language) Setting the Language (language) Do I Need to Set the Language? The DEC 4000 AXP 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.
Setting the Language (language) Change the Language To set the language that the system displays on output devices, do the following: Step Action 1 Determine the code number for the language you want system output devices to display. 2 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) 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.
Changing the Baud Rate (tta0_baud and tta1_baud) Change the Baud Rate Change a baud rate as follows: Step 1 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 2 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.
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.
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 disabled. Set or Change the Halt Key Functions Break are Set the tta0_halts and tta1_halts environment variables to suit your system environment.
5 Operating Mass Storage Devices Chapter Description Mass storage devices are drives that are used to store large amounts of data for extended periods. The DEC 4000 AXP system uses both DSSI and SCSI mass storage devices to store data. In This Chapter This chapter covers the following information: • DEC 4000 AXP Mass Storage Devices and Compartments • Operating DEC 4000 AXP Mass Storage Devices The devices described are: RZ-series drives, RF-series drives, the RRD42, the TLZ06, the TZ30, and the TZ85.
DEC 4000 AXP Mass Storage Devices and Compartments DEC 4000 AXP Mass Storage Devices and Compartments Identifying Mass Storage Compartments Mass storage devices are located in five compartments inside your system as shown in Figure 5–1. Four compartments are reserved for fixed-media drives ( – ); these drives include RZ-series and RF-series drives. !$ % One compartment is reserved for removable-media drives ( ); these drives include the RRD42, the TLZ06, the TZ30, and the TZ85.
Operating DEC 4000 AXP Mass Storage Devices Figure 5–1 Storage Compartments 1 A 2 B 3 C 4 5 D E Fixed-Media Mass Storage Compartments Removable-Media Mass Storage Compartment MLO-009360 Operating Mass Storage Devices 5–3
Operating DEC 4000 AXP Mass Storage Devices Operating DEC 4000 AXP Devices The remaining sections of this chapter describe how to operate each DEC 4000 AXP mass storage device. Table 5–1 describes the devices that are available for use with the DEC 4000 AXP system: Table 5–1 Devices Supported by the DEC 4000 AXP 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.
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 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 of the five mass storage compartments in your system are reserved for these fixed-media drives. (See Figure 5–1.
Operating RZ- and RF-Series Disk Drives Figure 5–2 Front Panels for RZ-Series (SCSI) Disk Drives Fast SCSI 1 2 3 3.5-Inch SCSI 1 2 3 4 5.
Operating RZ- and RF-Series Disk Drives Figure 5–3 Front Panels for RF-Series (DSSI) Disk Drives 3.5-Inch DSSI 1 2 3 4 5.25-Inch DSSI 1 5 2 6 4 MLO-009369 ! " # $ % & RZ- and RF-Series Fault Light Fault light (amber) Local disk converter OK light Online light DSSI terminator Write-Protect button Run/Ready button Each RZ- and RF-series disk drive has a fault light located on the front panel (see Figure 5–2 and Figure 5–3). If the fault light comes on blinking amber the drive is executing self-tests.
Operating RZ- and RF-Series Disk Drives Write-Protecting an RZ- or RF-Series Disk The RZ- and some RF-series drives, have no Write-Protect button. You set write-protection through console commands in console mode.
Operating RZ- and RF-Series Disk Drives Console Mode Write-Protect For RF-Series Drives 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.
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.
Operating RZ- and RF-Series Disk Drives Example 5–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...
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 5–4 shows the components of the RRD42.
Operating the RRD42 Compact Disc Drive Figure 5–4 RRD42 Compact Disc Drive and Compact Disc 1 2 3 4 5 8 6 9 7 XXXX XXXXXXXX XX XXXX XXXXXXXX XXXXXXXX XXXXXX XXXXXXXX XXXXXXXX XXXX XX XXXXXXXX XX XXXX XX XXXX XXXX XXXXXXXXXX MLO-008851 Operating Mass Storage Devices 5–13
Operating the RRD42 Compact Disc Drive Inserting a Compact Disc To insert a compact disc into the RRD42 (Figure 5–5): 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.
Operating the RRD42 Compact Disc Drive Figure 5–5 Inserting and Removing a Compact Disc 1 2 3 XXXXX XXX XXXXX XXXXX XXX X XX XXXX XXXXX XXXXX XXXXX XXXXX XXX XXXXX XX XXXXXXX XXXX XXXXX XXXXXX XXXXX XX XXXX XXXXX 4 5 6 MLO-008864 Operating Mass Storage Devices 5–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 5–6 shows the components of the TLZ06. ! " # $ % Tape unload button Tape cassette slot Write-protect light Tape/activity light DDS tape Up to four TLZ06 drives (three if the compartment contains an RRD42 drive) can be located in the removable-media mass storage compartment.
Operating the TLZ06 Tape Drive Figure 5–6 TLZ06 Drive and Compatible Tape 1 2 D D igit S ata al to ra g e 5 3 4 MLO-008194 Operating Mass Storage Devices 5–17
Operating the TLZ06 Tape Drive Inserting a Tape into the TLZ06 To insert the DDS tape into the TLZ06 (Figure 5–7): 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.
Operating the TLZ06 Tape Drive Figure 5–7 Inserting and Removing a Tape: TLZ06 2 3 4 5 Digital Data Storage Digital Data Storage 1 MLO-008865 Operating Mass Storage Devices 5–19
Operating the TLZ06 Tape Drive TLZ06 Lights Table 5–2 summarizes the conditions indicated by the TLZ06 lights. Table 5–2 TLZ06 Light Summary Write-Protect Light Tape/Activity Light Condition Off 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.
Operating the TLZ06 Tape Drive Table 5–2 (Cont.) TLZ06 Light Summary Write-Protect Light Tape/Activity Light Condition Blinking amber Blinking green. Test failure. Drive fault.
Operating the TZ85 Tape Drive Operating the TZ85 Tape Drive TZ85 Description The TZ85 tape drive stores information on removable cassette tapes that can hold up to 2.6 gigabytes each. Figure 5–8 shows the components of the TZ85. ! " # $ % & ' ( Unload button Operate Handle light Use Cleaning Tape light Tape in Use light Write Protect light Insert/release handle CompacTape slot CompactTape III One or two TZ85 drives can be located in the removable-media mass storage compartment.
To Re Han Op Pr W Un ai es d e m t lo s ov le n t ad hi e Li But s Ta gh to pe n t To H Ha C O Lo nd los Inse and pe Wa it ad n l le e r th th t Ta e Li is is pe gh t lo 85 ad TZ 3 Un 2 pe Ha rat nd e le 1 O W ri Pr te ot ec te Ta d pe in Us Us e e Cl e Ta ani pe ng Operating the TZ85 Tape Drive Figure 5–8 TZ85 Drive and Compatible Tape 4 5 8 6 7 MLO-008850 Operating Mass Storage Devices 5–23
Operating the TZ85 Tape Drive Inserting a Tape into the TZ85 To insert the TZ85 tape cartridge into the drive (Figure 5–9): 1. If the Operate Handle light is on solid green, proceed to the next step. If the Operate Handle light is not on, there is probably a tape in the drive. Remove the tape following the instructions in Removing a Tape from the TZ85 (next section). 2. Open the drive door by pulling the cartridge insert/release handle to the left . ! 3.
Operating the TZ85 Tape Drive d loa Un era Ha te nd le Op ed pe in Use Use Cle a Ta nin pe g Ta 2 d a o L ht ig L it a is W th n e p O dle e n p a Ta H rt se is In th se lo C dle n a H U re lo a u ig tt h o n t is era Ha te nd le Op Ta ed pe in Use Use Cle a Ta nin pe g d 85 n e e p O le ap d n T a e H ov m e R d a o L ht ig L it a is W th n e p O dle e n p a Ta H rt se is In th se lo C dle n a H T T o o P U re n lo ss a 4 d B L u ig tt h o n t it d loa Un era H
Operating the TZ85 Tape Drive Removing a Tape from the TZ85 To remove a tape cartridge from the TZ85 (Figure 5–10): 1. Press the Unload button on the front of the drive !. Wait for the Tape in Use light to go off and the Operate Handle light to come on. 2. Pull the cartridge insert/release handle open The tape ejects part way. 3. Remove the tape from the drive 4. Push the handle closed 5–26 Operating Mass Storage Devices #. ". $ or reinsert another tape.
Operating the TZ85 Tape Drive d loa Un Ta Op era Ha te nd le ed pe in Use Use Cle a Ta nin pe g 1 d loa Un Op era Ha te nd le ed pe in Use Use Cle a Ta nin pe g Ta W rite Pro tect n Bu ht ss Re Ha O W ait mo ndle pen this ve Ta pe Pre T Lig To d a o L ht ig L it a is W th n e p O dle e n p a Ta H rt se is In th se lo C dle n a H tto Un loa d Ha TZ 85 To H Lo nd Close Inse and Ope Wa it ad le n le this this rt Ta Lig pe ht W rite Pro tect TZ 85 Figure 5–10 Removing a Tape fr
Operating the TZ85 Tape Drive TZ85 Lights Table 5–3 summarizes the conditions indicated by the TZ85 lights. Table 5–3 TZ85 Light Summary Light State Condition Green On Okay to operate the cartridge insert/release handle. Off Not okay to operate the cartridge insert/release handle. Blinking regularly Tape is loading or unloading. Blinking irregularly Data read or write is in progress. On Tape is loaded (ready for use). On Tape is writeprotected. Off Tape is write-enabled.
Operating the TZ30 Tape Drive 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 5–11 shows the components of the TZ30. Up to four TZ30 drives 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.
Operating the TZ30 Tape Drive Figure 5–11 TZ30 Tape Drive and Compatible Tape 1 2 Unload Tape in Use Operate Lever Write Protect 3 4 7 5 6 MLO-007725 5–30 Operating Mass Storage Devices
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.
Operating the TZ30 Tape Drive Inserting a Tape into the TZ30 To insert the TZ30 tape into the drive (Figure 5–12): 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 that you wish to insert to either the write-protected or write-enabled position. # 3. Insert the tape cartridge " $. The green light comes on.
Operating the TZ30 Tape Drive Unload 1 3 Unload Operate Lever Tape in Use 2 Write Protect 108% 30% Unload Operate Lever Tape in Use 4 Write Protect Operate Lever Tape in Use Write Protect Figure 5–12 Inserting a Tape into the TZ30 5 MLO-008837 Operating Mass Storage Devices 5–33
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 5–13): 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.
Operating the TZ30 Tape Drive Unload Operate Lever Tape in Use Write Protect Figure 5–13 Removing a Tape from the TZ30 1 Unload Operate Lever Tape in Use Write Protect 108% 108% Unload Operate Lever Tape in Use Write Protect 2 108% 30% 3 MLO-008838 Operating Mass Storage Devices 5–35
Operating the TZ30 Tape Drive TZ30 Lights Table 5–4 summarizes the conditions indicated by the TZ30 lights. Table 5–4 TZ30 Light Summary Light State Condition Green On 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.
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.
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 5–14 shows where to place a label on a CompacTape ( ) and on a DSS tape ( ).
Maintaining Mass Storage Media and Devices • 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 5–15, or touch the disc. The caddy shutter opens automatically when you insert the caddy into the drive.
Maintaining Mass Storage Media and Devices Cleaning the TLZ06 • 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.
Maintaining Mass Storage Media and Devices 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.
References References The following table describes where to find additional information about DEC 4000 AXP mass storage devices. Task Document Obtain a list of all DEC 4000 AXP–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.
6 System Configuration Chapter Description Introduction This chapter describes your system configuration and explains how to plan changes in the configuration.
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 6–1 illustrates the most common DEC 4000 AXP configurations: • Standalone system ! with or without external mass storage A standalone system is not connected to any other systems or to a network.
Identifying Your Configuration Figure 6–1 Types of Configurations 1 2 Ethernet 3 4 MLO-009227 System Configuration 6–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 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.
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.
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.
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.
Identifying Mass Storage Devices Table 6–1 Mass Storage Compartments and Devices Buses Associated with Each Compartment Drive IDs DSSI Compartments SCSI Compartments Contain DSSI bus Contain SCSI bus Hold only DSSI devices Hold only SCSI devices Are fixed-media and contain RF-series drives If fixed-media, contain RZseries drives No support for removable-media If removable-media, contain some combination of RRD42, TLZ-series, and TZ-series drives Each compartment’s bus has a unique identificati
Identifying Mass Storage Devices Determine a drive address by identifying the bus on which the drive is located and the drive ID. The letter of the drive is etched on the machine. For example, the address of the drive in Figure 6–2 ( ) is Bus E, Drive ID 1. ! Figure 6–2 Drive Addresses A 1 B C 1 D E MLO-009229 The system sometimes displays this information in numerical form (see Example 6–3).
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.
Displaying Configuration Information Online Example 6–1 System Configuration Display >>> show config Return Console T2.4-2859 ! " CPU 0 CPU 1 Memory 0 Memory 1 Memory 2 Memory 3 Ethernet 0 Ethernet 1 P P P P A SCSI B C DSSI D SCSI E SCSI Futurebus+ P P P P P P VMS PALcode X5.12F, OSF PALcode X1.
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 6–2 shows a possible memory configuration display.
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 6–3 shows a possible device configuration display. Example 6–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.
Displaying Configuration Information Online The device naming convention is shown in Figure 6–3. Figure 6–3 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.
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 6–4 shows a possible console program version. Example 6–4 Console Program Version >>> show version version Displaying PALcode Version Return T2.
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.
Planning a Change to Your Configuration Perform Post-Upgrade Tasks After Digital Services installs the options, you may want to do one or more of the following tasks: • Set parameters for DSSI devices For information about how to do this, refer to Setting and Examining Parameters for DSSI Devices, later in this chapter. • Change drive ID numbers For information about how to do this, refer to Changing Drive ID Numbers, covered earlier in this chapter.
Connecting Additional Devices to Your System Connecting Additional Devices to Your System Bus Expansion Ports A bus expansion port on the front of most mass storage compartments enables you to extend the bus that runs through that compartment 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.
Connecting Additional Devices to Your System Figure 6–4 Mass Storage Bus Expansion Ports 1 A 2 B 3 C 4 5 D E Fixed-Media Mass Storage Compartment • • • • • ! Bus B expansion port " Bus C expansion port # Bus D expansion port $ Bus E expansion port % MLO-009359 Bus A expansion port System Configuration 6–19
Connecting Additional Devices to Your System Terminating and Extending a Bus To extend a bus, you attach a bus expansion cable (either DSSI or SCSI, to match the bus) to the bus expansion port and attach the other end of the cable into the external device. To terminate a bus, you attach a terminator (either DSSI or SCSI, to match the bus) to the bus expansion port. Figure 6–5 shows a system with terminated and extended DSSI and SCSI buses. • Bus A, in the example, is a SCSI bus.
Connecting Additional Devices to Your System Figure 6–5 Terminating and Extending a Bus 1 2 A B C D E 3 4 MLO-008869 System Configuration 6–21
Changing Drive ID Numbers Changing Drive ID Numbers When to Change Drive ID Numbers Each drive ID number is determined at the factory. Extra drive ID plugs are supplied with your system. You may need to use the extra plugs to renumber your drives under the following circumstances: • If you connect additional devices to your system • If you cluster two systems Note If you cluster two or more DSSI systems, you may need to set DSSI parameters instead of changing drive ID numbers.
Changing Drive ID Numbers Changing a Drive ID Plug The drive ID plugs have prongs on the back that indicate the bus node number (and by default, the unit number) of the drive. Change a drive ID plug as shown in Figure 6–6. • To remove a drive ID plug, grasp it firmly and pull it straight out. • To insert a drive ID plug, align the two center prongs with the two center slots and press the plug into the slots.
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 e
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.
Setting and Examining Parameters for DSSI Devices # $ cdp 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 6 characters) Device type 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 3.
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 storage compartment. 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).
Setting and Examining Parameters for DSSI Devices 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.
Setting and Examining Parameters for DSSI Devices Figure 6–7 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 exam
Setting and Examining Parameters for DSSI Devices Figure 6–8 Sample DSSI Buses for an Expanded DEC 4000 AXP System System 32 10 Bus A Expander 3 2 1 6 5 4 0 DSSI Cable Bus B DSSI Terminator Locations LJ-02065-TI0 6–30 System Configuration
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.
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.
Using the Power Control Bus with a Storage Expander Figure 6–9 Sample Power Bus Configuration System Expander 1 Expander 2 MLO-009370 References The following table describes where to find additional configuration information.
7 Learning More About Your System Chapter Description This chapter describes your system’s design and the design of its subsystems and components.
System Features System Features What Makes It a DEC 4000 AXP System? The following characteristics define the DEC 4000 AXP 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 Alpha AXP Architecture The DEC 4000 AXP system is part of a family of flagship computers that are based on the new Alpha AXP system architecture.
System Features Support of Multiple Operating Systems Currently, the DEC 4000 AXP 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 system is designed to be compatible with existing technology: • VAX hardware DEC 4000 AXP, like all Alpha AXP systems, can connect to your existing VAX hardware in clusters and networks.
Subsystems and Components Subsystems and Components Overview The subsystems that make up the DEC 4000 AXP system are described in Table 7–1 and shown in Figure 7–1. Table 7–1 DEC 4000 AXP 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.
Subsystems and Components Figure 7–1 DEC 4000 AXP System Architecture Power Subsystem Front End Unit Power System Contr To Outlet DC5 DC3 Serial Control Bus Memory 3 Memory 2 CPU 1 Memory 1 CPU 0 Operator Control Panel Memory 0 64, 128 MB System Bus Serial Control Bus DSSI/SCSI Bus A Ethernet Port 0 DSSI/SCSI Bus B Ethernet Port 1 di gi t al TM SCHOLAR Plus Data T alk T est Loop Off On SD RD CD T R SI Con sole Ter min al Asynchronous Serial Line (with modem control) I/O Module DSSI/S
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+.
CPU Subsystem Memory Module Main memory provides the electrical storage area for data and instructions used by the CPU. DEC 4000 AXP systems support from one to four memory modules.
CPU Subsystem 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. The serial control bus is a two-conductor serial interconnect bus that is independent of the system bus.
Power Subsystem The power subsystem has five basic components: • Front end unit (AC to 48 VDC 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).
Storage Subsystem Storage Subsystem Components Each system has a storage subsystem, which consists of mass storage adapters and mass storage devices. An expander cabinet allows you to place additional mass storage near the system. 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.
Futurebus+ Subsystem Futurebus+ Subsystem Overview DEC 4000 AXP 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.
8 Care, Maintenance, and Exterior Customizations 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.
Customizing the System Unit Locate Accessories Locate the accessories box in the system shipping carton. (Figure 8–1).
Customizing the System Unit Label the System Name Your operating system software instructs you in how to name your system. If you wish, add the system name (network node name), in the spaces provided, using the logical node name label letter card from the accessories box as shown in Figure 8–2.
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. Remove System Doors Front and rear doors have been designed for the DEC 4000 AXP system for aesthetic reasons and so that you can prevent access to components and controls, if need be. If you wish, you can remove these doors.
Customizing the System Unit Figure 8–3 Removing Front and Rear Doors 1 2 3 MLO-008870 Store the doors in a secure place. Always replace the doors before moving the system.
Customizing the System Unit Move the System If you wish to move the system to a new environment, you probably need to repack the system in its original shipping carton. Refer to the DEC 4000 Model 600 Series Site Preparation Checklist and DEC 4000 Model 600 Series Quick Installation for information about how to prepare the new site and reinstall the system. If you are repositioning the system within the same environment, unlock the casters and push the system to the new destination.
Customizing the System Unit Figure 8–4 Positioning the System Leave 25.4 mm (1 in) airflow clearance rear and sides. .5 m (1.6 ft) 1.1 m (3.7 ft) 1.7 m (5.
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 4.
Customizing the System Unit 4. Replace the operator control panel on the system unit. Figure 8–5 Location of the Baud Rate Switch 1 5 5 MLO-007720 Maintaining the System Overview While your DEC 4000 AXP is designed to function in a range of environmental conditions, it should be treated with care and maintained properly.
Maintaining the System 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 system unit requires adequate ventilation. Ideally, the system unit should be positioned in a dust-free environment.
9 Troubleshooting the System Chapter Description 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 system is a high-quality, 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.
Before You Begin Before You Begin Two Ways to Solve System Problems There are two ways to solve problems with the DEC 4000 AXP 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 9–1 lists ways to identify problems, and indicates where each method is described: Table 9–1 How to Identify a Problem To identify a problem this way . . .
Task Overview Task Overview Steps to Identifying a Problem Table 9–2 describes the steps required to identify and fix system problems. Table 9–2 Steps to Resolving Problems Step Description 1. Determine type of problem. 2. Locate problem in troubleshooting tables. 3. Follow suggested actions to resolve problem. 4. If necessary, run diagnostic tests. 5. Contact Digital service representative. The next sections describe these steps.
Determining Type of Problem Determining Type of Problem Types of System Problems Determine the type of problem that your system is experiencing from the list in Table 9–3. Table 9–3 Type of Problem For this kind of problem . . . See this section . . .
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 9–4 describes possible power problems and their solutions. The next section, Power Supply Lights, explains how to interpret the lights. Table 9–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.
Power Problems Figure 9–1 Power Supply Lights FEU PSC DC5 DC3 AC Circuit Breaker FEU Failure FEU OK DC3 Failure DC3 OK DC5 Failure MO DC5 OK SI SO PSC Failure PSC OK Over Overtemperature Shutdown Fan Failure Disk Power Failure Fault ID Display AC Present LJ-02011-TI0 Table 9–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).
Power Problems Table 9–5 (Cont.) Interpreting Power Supply Lights Light Meaning Action on Error Front End Unit (FEU) 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. 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.
Power Problems Table 9–5 (Cont.) Interpreting Power Supply Lights Light Meaning Action on Error 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.
Problems Getting to Console Mode Table 9–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.
Problems Getting to Console Mode Figure 9–2 Operator Control Panel Lights DC On/Off Switch DC Power Light Self-Test Status Lights Reset Halt 6-1 3 2 1 0 MEM 0 1 CPU I/O MLO-008872 Table 9–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.
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 9–8 describes problems reported by the console and their solutions. Table 9–8 Diagnostic Flow for Console Mode Problems Symptom Action Reference Power-up screens are displayed, but tests do not complete.
Boot Problems Boot Problems Boot Problems This section describes how to troubleshoot problems that occur while the system is booting operating system software. Table 9–9 describes possible problems during booting and their solutions. Table 9–9 Diagnostic Flow for Boot Problems Symptom Action Reference System cannot find boot device. Check the default boot device and boot flag settings.
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 9–10 describes possible operating system problems and their solutions. Table 9–10 Diagnostic Flow for Operating System Errors Symptom Action Reference System halts; >>> displayed on console terminal.
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 9–11 describes possible drive problems and their solutions. Table 9–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.
Mass Storage Problems Table 9–11 (Cont.) Diagnostic Flow for Mass Storage Problems Read error message displayed. 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.
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 9–12 describes how to manually remove the caddy. Table 9–11 describes how to troubleshoot all other RRD42 problems. Manually remove the disc caddy as follows: Table 9–12 Manual Removal of a Disc Caddy Step Action 1 Shut down the system. 2 Press the DC on/off switch to the off position (0).
Network Problems Network Problems Ethernet Problems If an error message displays when verifying or testing the Ethernet connection, see Table 9–13. Table 9–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.
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 9–14, or your local Digital office.
Reporting Problems to Digital Services Table 9–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.
References DEC 4000 AXP Problem Worksheet DEC service representative telephone number: Model Number (circle one): Model 610 Model 612 Serial Number: Status of the System (check all that apply): DC power light is not on Console program fails to boot Self-test status lights remain on Console error message Operating system fails to boot Fan failure light is on Diagnostic test error message Self-test status lights Diagnostic Test Screen Display: Troubleshooting notes: MLO-009900 9–20 Troubleshoot
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 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.
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.
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.
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.
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.
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.
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.
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.
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 The panel on the top right side of the DEC 4000 AXP system that contains the power, Reset, and Halt switches and system status lights.
program mode See operating system mode. R400X mass storage expander A Digital enclosure used for mass storage expansion. 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.
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 operator control panel.
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.
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.
Index A B AC circuit breaker, 1–9 AC present light, 9–6 Accessories box, 8–2 Adapters, mass storage, 7–10 Addresses See Drive addresses Ethernet addresses ALLCLASS parameter, 6–27 Allocation classes, changing, 6–24 Alpha AXP architecture See System architecture Alpha AXP chip See DECchip 21064 microprocessor Antistatic wrist strap, 8–6 Architecture See System architecture Autoboot, 4–5 auto_action environment variable described, 4–2 displaying current value, 4–5 setting, 4–6 settings, 4–4 uses of, 4–5 Aux
Bus expansion ports described, 6–18 location of, 6–19 Buses, storage extending, 6–18 extending fast SCSI, 6–18 named by compartment, 6–8 terminating and extending, 6–20 C Cable guide, location, 1–5 Caddy See Compact disc caddy Card cage contents, 6–6 lights, 1–8 location, 1–7 Cartridges See CompacTape cartridges; CompacTape II cartridges; CompacTape III cartridges; Tape drive media cdp command, 3–7, 6–26 Central processing unit See CPU Characters, control, supported in console mode, 2–8 Characters, keyboar
Console program, 2–2 Console prompt, 2–6 Console subsystem components, 2–2, 2–3 finding additional information about, 3–25 Console terminal, 2–2 remote, 2–2, 2–5 Console terminal port, 2–2 changing baud rate setting, 4–15 continue command, 3–10 Control characters, 2–8 Controls, accessing, 1–2 CPU adapter, 7–10 benefits of two, 6–4 DEC 4000 AXP design, 7–2 described, 7–6 modules, location of, 1–7 CPU subsystem components, 7–6 Ctrl/A, function in console mode, 2–8 Ctrl/C, function in console mode, 2–8 Ctrl/E,
Drive ID plugs changing, 6–23 function, 6–8 using to color-code drives, 6–8 when to change, 6–22 Drives See Mass storage devices; Tape drives; Disk drives DSSI adapters, function of, 7–10 DSSI buses, terminating and extending, 6–20 DSSI device allocation classes, changing, 6–24 DSSI devices changing allocation classes for, 6–24 cluster capability, 6–4 DSSI ID plugs, 6–8 See also Drive ID plugs DSSI parameters, 6–26 DSSI VMScluster configurations, 6–4 Dual CPU systems, 6–4 DUP driver utility, 6–26 E Environ
Installation, xix K Keyboard characters, supported in console mode, 2–6, 2–8 Keyboard, maintenance, 8–10 Keys See Keyboard characters; System keys L Labeling mass storage media, 5–38 system name, 8–3 Labels, language, replacing, 8–4 language environment variable changing default, 4–14 described, 4–2 displaying default, 4–14 Language labels, replacing, 8–4 Language setting changing default, 4–14 displaying current default, 4–14 Lights operator control panel, 9–9 power supply, 9–5 M Maintenance, 8–9 of mas
Operating system software, booting, 1–15 Operating system, reporting failures, 9–13 Operating systems, supported on DEC 4000 AXP, 7–3 Operator control panel controls, 1–6 location, 1–5 operations, 1–17 shutting down system before using, 1–17 using self-test lights on, 1–21 Operator control panel lights, 9–9, 9–10 Options, 6–6 OSF See DEC OSF/1 AXP operating system Overstrike mode, 2–8 Overtemperature shutdown light, 9–7 P PALcode See show pal command Parameters, DSSI, 6–24 Power subsystem, 7–4 components,
RRD42 compact discs caring for, 5–38 handling, 5–38 RRD42 drives busy light, 5–14 components, 5–12 described, 5–12 hardware specifications, 5–4 inserting a disc into, 5–14 operating, 5–12 removing a disc from, 5–14 troubleshooting, 9–14, 9–16 RZ-series drives capacity in R400X, 7–10 changing drive ID plugs, 6–23 described, 5–5 lights, 5–7 troubleshooting, 9–14 write-protecting and write-enabling, RZ26 drive components, 5–6 described, 5–5 hardware specifications, 5–4 lights, 5–7 write-protecting and write-en
Startup screen, 1–16 Startup status, 1–11 Storage subsystem, 7–10 Subsystems, DEC 4000 AXP, 7–4 Symmetric multiprocessing, 6–4 System characteristics, 7–2 moving, 8–6 System architecture design, 7–4 overview, 7–2 System bus, 7–4 System components front, 1–5 rear, 1–7 System configuration, 6–2 adding third-party devices, 6–17 additional documentation about, 6–33 displaying in console mode, 6–10 planning, 6–16 System doors, removing, 8–4 System keys, locating, 1–2 System maintenance, 8–9 System modules, 6–6 S
Troubleshooting (cont’d) pre-console mode problems, 9–9 TSZ07 drives finding information on, 5–42 hardware specifications, 5–4 tta0_baud environment variable described, 4–2 displaying current value, 4–16 tta0_halts environment variable described, 4–2 tta1_baud environment variable described, 4–2 displaying current value, 4–16 tta1_halts environment variable described, 4–2 TZ30 drives cleaning, 5–41 compatible tapes, 5–29 components, 5–29 described, 5–29 hardware specifications, 5–4 inserting a tape into, 5–
Reader’s Comments DEC 4000 Model 600 Series Owner’s Guide EK–KN430–OP. A01 Your comments and suggestions help us improve the quality of our publications.
d Do Not Tear – Fold Here and Tape NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST CLASS PERMIT NO. 33 MAYNARD MASS.
