Copyright: Copyright ® Digital Equipment Corp. 1995
Citation: Copyright ® Digital Equipment Corp. 1995


Troubleshooting Menu


Troubleshooting
Overview

Troubleshooting Overview

Before troubleshooting any system problem, check the site maintenance log

for the system's service history.  Be sure to ask the system manager the

following questions:

1.	Has the system been used before and did it work correctly?

2.	Have changes to hardware or updates to firmware or software been

made to the system recently?

3.	What is the state of the system -- is the operating system running?

If the operating system is down and you are not able to bring it up, use the console environment diagnostic tools, such as the power-up/diagnostic displays and ROM-based diagnostics (RBDs).

If the operating system is running, use the operating system environment diagnostic tools, such as error logs, crash dumps, and exercisers (DEC VET).

System problems can be classified into the categories listed on the troubleshooting menu.  Using these categories, you can quickly determine a starting point for diagnosis and eliminate the unlikely sources of the problem.


Power Problems

Diagnostic Flow for Power Problems

AlphaServer 2000 (BA720 Pedestal Enclosure)

AlphaServer 2100 (BA740 Pedestal Enclosure)

AlphaServer 2100 RM/CAB (BA741 Rackmount Enclosure)


Power Problems

Troubleshooting
Power Problems

AlphaServer 2000  (BA720 Pedestal Enclosure)

Symptom	Action
System does not power on.	Check the power source and power cord.
	Check that the system cover is in place.  A safety interlock switch shuts off power to the system if the system cover is not properly secured.
	If there are two power supplies, make sure both power supplies are plugged in.
	Check the DC On/Off button setting on the operator control panel.
	Check that the ambient room temperature is within environmental specifications (10-40ºC, 50-104ºF).
	Check power configuration rules.  If you have two CPUs, you need two power supplies operating in full power mode.
	Check that internal power supply cables are plugged in at both the power supply and system bus backplane.
Power supply shuts down after approximately 5 seconds (fan failure).	Using a flashlight, look through the front (to the left of the internal StorageWorks shelf) to determine if the 6.75-inch and 4.5-inch fans are spinning at power-up.  A failure of either fan causes the system to shut down after approximately 5 seconds.
More information on power-up


Power Supply Cable Connections (BA720 Enclosure)


Power Supply Configuration Rules (BA720)

Troubleshooting
Power Problems

Power Supply Configuration Rules (BA720 Enclosure)

The power supplies for AlphaServer 2000 systems support three different modes of operation. In addition, UPS options are available.

Note:  AlphaServer 2000 systems (BA720 enclosure), unlike the AlphaServer 2100 systems (BA740/BA741 enclosures), use power supply cables.

Power supply modes of operation:

1.	Single power supply---Supports systems with:

      One CPU

      Two memory modules

      One diskette drive

      Two removable drives

      Eight 3.5-inch StorageWorks hard disks

      Ten I/O slots

2.	Dual power supply (redundant mode)---Provides redundant power (n + 1) for the system described above.

In redundant mode, the failure of one power supply does not cause the system to shut down. Normal operation continues with no impact on the system.

The power supply mode jumper (J3) on the I/O backplane module must be installed to activate redundant mode power.

3.	Dual power supply (full power mode)---Provides full power for systems with two CPUs. Systems with two CPUs need a second power supply.

The single and redundant mode power supply configurations are available to those systems drawing the following power levels:

Note:  Total combined power of all outputs per supply cannot exceed 400 watts.

 36 A or less of 3.3 V power

 52 A or less of 5.0 V power

 11 A or less of +12.0 V power

 0.2 A or less of -12.0 V power

 0.2 A or less of -5.0 V power

 The combination of 3.3 V power and 5.0 V power cannot exceed 335 watts.

If you add a second CPU to an AlphaServer 2000-series system, you will need to do one of the following:

 Install a second power supply (H7845-AA).

 If a dual power supply is configured in redundant mode, reconfigure it into full power mode.


Power Problems

Troubleshooting
Power Problems

AlphaServer 2100 (BA740 Pedestal Enclosure)

Symptom	Action
No AC power at system, as indicated by AC OK LED on the power supply when the AC On/Off switch is set to "on." Note:  Later revisions of the power supply do no have an AC On/Off switch or an AC OK LED.	Check the power source and power cord. Check that the left panel is properly secured.  A safety interlock switch shuts off power to the system if the panel is removed. If there are two power supplies, make sure both have the AC On/Off switch set to "on", or that both power supplies are plugged in (systems with no AC On/Off switches).
AC power is present, but system does not power on.	Check the DC On/Off button setting on the operator control panel. Check that the ambient room temperature is within environmental specifications (10-35ºC, 50-95ºF) and reset the AC On/Off switch.
	Check power configuration rules. If you have more than two CPUs or more than one internal StorageWorks shelf, you need two power supplies operating in full power mode.
Power supply shuts down after approximately 5 seconds (fan failure).	Using a flashlight, look through the front (to the left of the internal StorageWorks shelf) to determine if the 6.75-inch fan is spinning at power-up.  A failure of the 6.75-inch fan causes the system to shut down after approximately 5 seconds.
More information on power-up


Power Supply Configuration Rules (BA740)

Troubleshooting
Power Problems

Power Supply Configuration Rules (BA740 Enclosure)

The power supplies for model pedestal systems support three different modes of operation. In addition, UPS options are available.

Power supply modes of operation:

1.	Single power supply---Supports entry-level systems, such as a  system with two CPUs, one memory module, one floppy drive, one CD-ROM drive, one internal StorageWorks shelf with eight 3.5-in drives, and up to eight EISA/PCI options.

2.	Dual Power Supply (redundant mode)---Provides redundant power (n + 1) for entry-level systems, such as a system with two CPUs, one memory module, one floppy drive, one CD-ROM drive, one internal StorageWorks shelf with eight 3.5-in drives, and up to eight EISA/PCI options.

In redundant mode, the failure of one power supply does not cause the system to shut down. Normal operation continues with no impact on the system.

The power supply mode jumper (J3) on the standard I/O module must be installed to activate redundant mode power.

3.	Dual Power Supply (full power mode) --- Provides full power for system configurations beyond entry level, such as system with more than two CPUs or more than one internal StorageWorks shelf. These systems require the power of two power supplies.

Note:  The single and redundant mode power supply configurations are available to those systems drawing:

 602 watts DC output power or less

 39 A or less of 3.3 V power

 62 A or less of 5.1 V power

 12.5 A or less of +12 V power

 1.0 A of -12 V power


Power Problems

Troubleshooting
Power Problems

AlphaServer 2100 RM/CAB (BA741 Rackmount Enclosure)

Symptom	Action
Fans do not spin up when the AC power cable is plugged into the power supply.	Check the power source and power cord. If there are two power supplies, make sure both are plugged in.
AC power is present, as indicated by spinning fans, but system does not power on.	Check the DC On/Off button setting on the operator control panel. Check that the ambient room temperature is within environmental specifications (10-35ºC, 50-95ºF).
Power supply shuts down after approximately 5 seconds (fan failure).	Check to see if both 6.75-inch fans are operating.  A failure of either 6.75-inch fan causes the system to shut down after approximately 5 seconds.
More information on power-up


AC OK LED, BA740 Enclosure

Power Supply LEDs (BA740) Enclosure

Note:  The internal power supply fuse in not a serviceable part.  Return to factory for service.

Note:  Later revisions of the power supply do not have an AC power switch or AC OK LED.


Problems Getting to Console Mode

Troubleshooting
No Access to Console Mode

Diagnostic Flow for Problems Getting to Console Mode

Symptom	Action
Power-up screen is not displayed.	Check power-up/diagnostic display on the operator control panel for a failure during self-tests. Check that keyboard and monitor are properly connected and powered on.   If the power-up screen is not displayed, yet the system enters console mode when you press the Return key, check that the console environment variableis set correctly.  If you are using a VGA console terminal, the console variable should be set to graphics.  If you are using a serial console terminal, the console variable should be set to serial.   If console is set to serial, the power-up screen is routed to the COM1 serial communication port and cannot be viewed from the VGA monitor. Try connecting a console terminal to the COM1 serial communication port.  If necessary use an MMJ-to-9-pin adapter (H8571-J).  Check baud rate setting for console terminal and system.  The system baud rate setting is 9600.  When using the COM1 port, you must set the console environment variable to "serial." If the system has a customized NVRAM file, try powering up with the Halt button set to the in position. The NVRAM file will not be executed when powering up with the Halt button depressed. For certain situations, power up using the fail-safe loader to bypass the power-up script and get to a low-level console.  From the fail-safe loader console, you can edit the nvram file, set and examine environment variables, and initialize drivers.


Fail-Safe Loader

Troubleshooting
No Access to Console Mode

Fail-Safe Loader

The fail-safe loader (FSL) allows you to power up without initializing drivers or running power-up diagnostics.

Note:  The fail-safe loader should be used only when a failure at power-up prohibits you from getting to the console program.  You cannot boot an operating system from the fail-safe loader.

If a checksum error is detected when the SRM console is loading at power-up, the fail-safe loader is automatically loaded into memory and the system displays the FSL prompt ash>.  If the system automatically powers up to the ash> prompt, reinstall firmware according to the instructions provided with the firmware.

Whenever the fail-safe loader console is activated, the power-up/diagnostic display on the operator control panel displays a FAIL I/O_00 message.

The FSL permits you to get to a console, with limited functionality, when one of the following is the cause of a problem getting to the console program under normal power-up:

A power failure or accidental power down during a firmware upgrade

An error in the nonvolatile nvram file

An incorrect environment variable setting

A driver error

Note:  The FSL program, indicated by the ash> prompt, has limited functionality.  A simple shell is indicated by the letters "ash" contained in the console prompt.

Fail-Safe Loader Functions

Activating the Fail-Safe Loader


Fail-Safe Loader Functions

From the FSL program, you can:

Edit the nvram file using the edit command

Assign a correct value to an environment variable (using the show and set commands)

Start individual drivers using the init -driver ew command to start the MOP driver or init -driver dv to start the floppy driver.  The init -driver 6 command in FSL mode starts all available drivers.

Note:  The nonvolatile file, nvram, is shipped from the factory with no contents.  The customer can use the edit command to create a customized script or command file that is executed as the last step of every power-up.


Activating the Fail-Safe Loader

Troubleshooting
No Access to Console Mode

Activating the Fail-Safe Loader

To activate the FSL:

Install jumper J6 on the standard I/O module.  For 2000-series systems (BA720 enclosure), jumper J6 is located on the I/O backplane. The jumper is stored on one of the pins of the J6 jumper.

Turn on the system.

Use the FSL program, ash>, to make corrections, edit the nvram file, set environment variables, or initialize phase 6 drivers.

When you have finished, power down and remove the FSL jumper.


Fail-Safe Loader Jumper (BA470/BA741)

Fail-Safe Loader Jumper (J6) on the Standard I/O (BA740/BA741 Enclosures)

J3--Power supply mode	When installed, dual power supplies operate in redundant mode
J5--Programming voltage	Internal use only
J6--Fail-safe	When installed, selects the fail-safe loader firmware


Fail-Safe Loader Jumper (BA720)

Fail-Safe Loader Jumper (J6) on the I/O Backplane (BA720 Enclosure)

J3--Power supply mode	When installed, dual power supplies operate in redundant mode
J5--Programming voltage	Internal use only
J6--Fail-safe	When installed, selects the fail-safe loader firmware


Console Event Log

Troubleshooting
Console-Reported Failures

Console Event Log

AlphaServer systems maintain a console event log consisting of status messages received during power-on self-tests.  If problems occur during power-up, standard error messages indicated by asterisks (***) may be embedded in the console event log.  To display a console event log, use the cat el command.

Note:  To stop the screen display from scrolling, enter Ctrl/S.  To resume scrolling, enter Ctrl/Q.  You can also use the command, more el, to display the console event log one screen at a time.

Note:  Click on the [image] icon above to view an example.


Console Event Log Example

Troubleshooting
Console-Reported Failures

Console Event Log Example

The following example shows abbreviated console event logs that contain standard error messages:

1.	The first indicates a problem with the mouse driver.

2.	The second indicates the Ethernet loopback test failed (possibly the result of a missing terminator or disconnection from a live network).

3.	The third indicates a failing SIMM on memory board 0.

P00>>> cat el

starting console on CPU 0

initialized idle PCB

initializing semaphores

initializing heap

.

.

.

CPU 0 speed is 5.26 ns (190MHz)

access NVRAM

entering idle loop

Starting Memory Diagnostics

.

.

.

initializing keyboard

** no mouse interrupts received **   (1)

.

.

.

Change mode to Internal loopback.

*** Error (ewa0), Mop loop message timed out from: 08-00-2b-3d-63-10  (2)

*** List index: 0 received count: 0 expected count 1

.

.

.

Change to Normal Operating Mode.

P00>>>

P00>>> cat el

starting console on CPU 0

initialized idle PCB

initializing semaphores

.

.

.

Testing 1st 2MB(s) on memory module 0

***Error - Memory Board 0 ***   (3)

Failing address:     00000020

Bank Number:         0

ASIC ID:             1

Error Type:          0

Error Syndrome:      00000710

Failing SIMM module  J28

.

.

.

P00>>>


Boot Problems

Troubleshooting
Boot Failures

Diagnostic Flow for Boot Problems

Symptom	Action
System cannot find boot device.	Check system configuration for correct device parameters (node ID, device name, and so on).  For DEC OSF/1 and OpenVMS:      show config      show device For Windows NT:      Display hardware configuration      Set default variables Check the system configuration for correct environment variable settings.  For DEC OSF/1 and OpenVMS:     auto_action     bootdef_dev     boot_osflags     os_type For problems booting over a network, check the ew*0_protocols or er*0_protocols environment variable settings: Systems booting from a DEC OSF/1 server should be set to bootp; systems booting from an OpenVMS server should be set to mop. For Windows NT: FWSEARCHPATH AUTOLOAD COUNTDOWN
Device does not boot.	Check that the Halt button is not set to in (depressed). For problems booting over a network, check the ew*0_protocols or er*0_protocols environment variable settings: Systems booting from a DEC OSF/1 server should be set to bootp; systems booting from an OpenVMS server should be set to mop. Run device tests to check that boot device is operating.


Operating System Reported Problems

Troubleshooting
Operating System-Reported Failures

Diagnostic Flow for Errors Reported by the Operating System

Symptom	Action
System is hung or has crashed.	Examine the crash dump file.   Refer to OpenVMS AXP Alpha System Dump Analyzer Utility Manual for information on how to interpret OpenVMS crash dump files. Refer to the Guide to Kernel Debugging (AA-PS2TA-TE) for information on using the DEC OSF/1 Krash Utility. Use the show error command to examine error information contained in serial control bus EEPROMs (console environment error log).
Errors have been logged and the operating system is up.	Examine the operating system error log files to isolate the problem.   If the problem occurs intermittently, run an operating system exerciser, such as DEC VET, to stress the system. Refer to the DEC Verifier and Exerciser Tool User's Guide (AA-PTTMA-TE) for instructions on running DEC VET.


Mass Storage Problems at Power-Up

Troubleshooting
Console-Reported Failures

Mass Storage Problems Indicated at Power-Up

Mass storage failures at power-up are usually indicated by read fail messages.  Other problems are indicated by storage devices missing from the show config display.  The mass storage troubleshooting tables can help you diagnose the likely cause of the problem.

Fixed-Media Troubleshooting Table

Removable-Media Troubleshooting Table


Fixed-Media Mass Storage Troubleshooting Table

Troubleshooting
Console-Reported Failures

Fixed-Media Mass Storage Troubleshooting Table

Problem	Symptom	Corrective Action
Drive failure	Fault LED for drive is on (steady).	Replace drive.
Duplicate SCSI IDs (when removable-media bus is extended to StorageWorks shelf)	Drives with duplicate SCSI IDs are missing from the show config display	Correct removable-media SCSI IDs.
SCSI ID set to 7 (reserved for host ID)	Valid drives are missing from the show config display. One drive may appear seven times on the configuration screen display.	Correct SCSI IDs.
Duplicate host IDs on a shared bus	Valid drives are missing from the show config display. One drive may appear seven times on the configuration screen display.	Change host ID through the pk*0_host_id environment variable, using set pk*0_host_id.
Extra terminator	Devices produce errors or device IDs are dropped.	Check that bus is terminated only at beginning and end.  Remove unnecessary terminators.
I/O module failure (if removable-media bus is extended to StorageWorks shelf) or PCI or EISA storage adapter option failure	Problems persist after eliminating the above problem sources.	Replace storage adapter module or standard I/O (I/O backplane for 2000-series systems).

Troubleshooting tips for AlphaServer systems using the SWXCR-XX controller.


Power-Up Sequence

Troubleshooting
Console-Reported Failures

Power-Up Sequence

During the AlphaServer power-up sequence, the power supplies are stabilized and the system is initialized and tested via the firmware power-on self-tests.

The power-up sequence includes the following:

Power supply power-up:

AC power-up

DC power-up

Two sets of power-on diagnostics:

Serial ROM diagnostics

Console firmware-based diagnostics

Caution:  The BA740 pedestal enclosure will not power up if the left side panel is not securely attached. Removing the side panel will cause the system to shut down.  The BA720 pedestal enclosure will not power up if the system cover is not securely attached.  Removing the system cover will cause the system to shut down.


AC Power-Up Sequence

Troubleshooting
Console-Reported Failures

AC Power-Up Sequence

When AC power is applied to the system (systems is plugged in) or, for BA740 enclosures with an AC On/Off switch, when the AC On/Off switch is set to "on;" or when electricity is restored after a power outage, the following sequence occurs:

The front end of the power supply begins operation and energizes.

The power supply then waits for the DC power to be enabled.

For BA740 enclosures with power supply LEDs, the AC OK LED is illuminated when AC power is applied.

Note:  For rackmount systems, you should hear the fans spin up when the system is plugged in (AC power applied).

For pedestal systems, the left side panel (BA740 enclosure) or system cover (BA720) must be securely installed.  A safety interlock prevents the system from being powered on with the panel or cover removed.


DC Power-Up Sequence

Troubleshooting
Console-Reported Failures

DC Power-Up Sequence

DC power is applied to the system with the DC On/Off button on the

operator control panel.

A summary of the DC power-up sequence is provided below:

1.	When the DC On/Off button is pressed, the power supply checks for a POK_H condition.

2.	12V, 5V, 3.3V, and -12V outputs are energized and stabilized.  If the outputs do not come into regulation, the power-up is aborted and the power supply enters the latching-shutdown mode.

3.	With a POK_H condition established and DC voltages stabilized, the power supply delivers a DCOK_H signal to the standard I/O and motherboard.

Note:  AlphaServer 2000-series systems (BA720 enclosure) do not have a DCOK_H signal.

4.	The  standard I/O then generates the ASYNC_RESET_L.  In the case of a full power supply configuration, each DCOK_H signal must be asserted; in the case of a redundant power supply configuration, either one of DCOK_H signals must be asserted.

Redundant:	POK_H = PS1_POK_H or PS2_POK_H

       DCOK_H = PS1_DCOK_H or PS2_DCOK_H

Full:	POK_H = PS1_POK_H and PS2_POK_H

       DCOK_H = PS1_DCOK_H and PS2_DCOK_H

The power supply mode jumper (J3) on the standard I/O module controls the mode of power supply operation.  For 2000-series systems, J3 is located on the I/O backplane.  With the jumper installed, the power supplies operate in redundant mode. Full power mode, with the jumper removed, is the default setting.

Note:  Rackmount systems always use the redundant mode setting when two power supplies are used.

5.	For systems with power supply LEDs, the DC OK LED on the power supply is lit.  Firmware power-up diagnostics begin.


Power Supply Mode Jumper (J3)- BA740/BA741

Power Supply Mode Jumper (J3) on the Standard I/O (BA740/BA741 Enclosures)

J3--Power supply mode	When installed, dual power supplies operate in redundant mode.
J5--Program voltage	Internal use only.
J6--Fail-Safe	When installed, selects the fail-safe loader firmware.


Power Supply Mode Jumper (J3)- BA720

Power Supply Mode Jumper (J3) on the Standard I/O (BA720 Enclosure)

J3--Power supply mode	When installed, dual power supplies operate in redundant mode.
J5--Program voltage	Internal use only.
J6--Fail-Safe	When installed, selects the fail-safe loader firmware.


Firmware Power-Up Diagnostics

Troubleshooting
Power Problems

Firmware Power-Up Diagnostics

Serial-ROM Diagnostics

Console Firmware-Based Diagnostics

After successful completion of AC and DC power-up sequences, the processor performs its power-up diagnostics.  These tests verify system operation, load the system console, and test the core system (CPU, memory, standard I/O, or I/O backplane, and motherboard), including all boot path devices.

These tests are performed as two distinct sets of diagnostics:

Serial ROM diagnostics --These tests are loaded from the serial ROM located on the CPU module into the CPU's instruction cache (I-cache). They check the basic functionality of the system and load the console code from the FEPROM on the standard I/O module (or I/O backplane for BA720 enclosures) into system memory.

Failures during these tests are indicated by the power-up/diagnostic display on the operator control panel.  Diagnostic test and exerciser failures are also logged in EEPROM as TDD error logs via the serial control bus for CPU, memory, and standard I/O modules (or I/O backplane for BA720 enclosures).

Console firmware-based diagnostics --These tests are executed by the console code.  They test the core system, including all boot path devices.

Failures during these tests are reported to the console terminal via the power-up screen or console event log.  Diagnostic test and exerciser failures are also logged in EEPROM as TDD or SDD error logs via the serial control bus for CPU, memory, and standard I/O modules.


Serial ROM Diagnostics

Troubleshooting
Power Problems

Serial ROM Diagnostics

The serial ROM diagnostics are loaded into the CPU's instruction cache from the serial ROM on the CPU module.  They test the system in the following order:

1.	Test the CPU and backup cache located on the CPU module.  If the backup cache fails testing, a CPU failure is indicated on the power-up/diagnostic display on the operator control panel (OCP), the error is logged to the serial control bus EEPROM, and remaining backup cache tests are completed.

2.	Test the CPU module's system bus interface.

3.	Test the system bus to PCI bus bridge and system bus to EISA bus bridge. If the PCI bridge fail, or EISA bridge fail, a standard I/O (or I/O backplane for BA720 enclosure) failure is indicated on the power-up/diagnostic display on the OCP.  The power-up tests continue despite these errors.

4.	CPUs determine which CPU will serve as the primary CPU.  Each CPU reads error log information from every CPU EEPROM.  The lowest numbered passing CPU is selected as the primary CPU in a process called multiprocessor failover.  If all CPUs fail power-up diagnostics, then CPU0 is selected as the primary CPU.  The primary CPU then takes control and completes the remaining steps.

5.	Locate the largest memory module in the system and test the first 32 MB of memory on the module.  Only the first 32 MB of memory are tested.  If there is more than one memory module of the same size, the lowest numbered memory module (one closest to the CPU) is tested first.

If the memory test fails, the next largest memory module in the system is tested.  Testing continues until a good memory module is found.  If a good memory module is not found, a memory failure is indicated on the power-up/diagnostic display on the OCP, and the power-up tests are terminated.

6.	Check the access to the FEPROMs on the standard I/O module, or I/O backplane for BA720 enclosures.

7.	The SRM console program is loaded into memory from the FEPROM on the standard I/O module (or I/O backplane for BA720 enclosures).  A checksum test is executed for the console image.  If the checksum test fails, the fail-safe loader (FSL) is automatically loaded into memory and the system displays the FSL prompt, ash>.

If the checksum test passes, control is passed to the console code, and the console firmware-based diagnostics are run.

While the console is being loaded into memory, CPUs with errors logged are disabled (if not the primary CPU).  Working CPUs spin on mailbox (they continuously read the mailbox address).


Console Firmware-Based Diagnostics

Troubleshooting
Power Problems

Console Firmware-Based Diagnostics

Console firmware-based tests are executed once control is passed to the console code in memory.  They check the system in the following order:

1.	Perform a complete check of system memory.  If a system has more than one memory module, the modules are checked in parallel.

2.	Set memory interleave to maximize interleave factor across as many memory modules as possible (one, two, or four-way interleaving). During this time the console firmware is moved into backup cache on the primary CPU module. After memory interleave is set, the console firmware is moved back into memory.

Steps 3--6 may be completed in parallel.

3.	Start the I/O drivers for mass storage devices and tapes. At this time a complete functional check of the machine is made. After the I/O drivers are started, the console program continuously polls the bus for devices (approximately every 20 or 30 seconds).

4.	Check that EISA configuration information is present in NVRAM for each EISA module detected and that no information is present for modules that have been removed.

5.	Run exercisers on the drives currently seen by the system.

Note:  This step does not ensure that all disks in the system will be tested or that any device drivers will be completely tested.  Spin-up time varies for different drives, so not all disks may be on line at this point in the power-up.  To ensure complete testing of disk devices, use the test command.

6.	If the Halt button is set to "in" (depressed), the customized NVRAM script (if the customer has created one) is not executed.

7.	Enter console mode or boot the operating system.  This action is determined by the Halt button setting or auto_action environment variable.

If the os_type environment variable is set to NT, the ARC console is loaded into memory, and control is passed to the ARC console.


Removable-Media Mass Storage Troubleshooting Table

Troubleshooting
Console-Reported Failures

Removable-Media Mass Storage Troubleshooting Table

Problem	Symptom	Corrective Action
Drive failure	Fault LED for drive is on (steady).	Replace drive.
Duplicate SCSI IDs	Drives with duplicate SCSI IDs are missing from the show config display.	Correct SCSI IDs.
SCSI ID set to 7 (reserved for host ID)	Valid drives are missing from the show config display. One drive may appear seven times on the show config display.	Correct SCSI IDs
Duplicate host IDs on a shared bus	Valid drives are missing from the show config display. One drive may appear seven times on the configuration screen display.	Change host ID through the pk*0_host_id environment variable, using set pk*0_host_id.
Missing or loose cables.	Activity LEDs do not come on.  Drive missing from the show config display.	Remove device and inspect cable connections.
Terminator missing.	Read/write errors in console event log; storage adapter port may fail.	Attach terminators as needed: internal SCSI terminator (12-41296-01) or external SCSI terminator (12-37004-04).
I/O module failure	Problems persist after eliminating the above problem sources.	Replace standard I/O module (I/O backplane for 2000-series systems).


Troubleshooting Table for Console Reported Problems

Troubleshooting
Console-Reported Failures

Diagnostic Flow for Problems Reported by the Console Program

Symptom	Action
Power-up tests do not complete.	Use power-up/diagnostic display on the operator control panel and/or console terminal to determine error.
The system powers up to the ash> prompt.	Reinstall firmware.  Refer to the procedure provided with the firmware update documentation.
Console program reports error: Operator control panel displays failure message at power-up Halt button LED lights during power-up Power-up screen includes error messages Console prompt indicates a CPU failover	Use power-up/diagnostic display on the operator control panel and/or console terminal to determine error. Use the show fru command and show error command to see if errors have been logged and to examine error information contained in serial control bus EEPROMs. Examine the console event log (enter the cat el command) or power-up screen to check for embedded error messages recorded during power-up. If power-up screen or console event log indicate problems with mass storage devices, or if storage devices are missing from the show config display, use the mass storage troubleshooting tables to determine the problem. If power-up screens or console event log indicate problems with EISA devices, or if EISA devices are missing from the show config display, use the EISA troubleshooting table to determine the problem. If power-up screens or console event log indicate problems with PCI devices, or if PCI devices are missing from the show config display, use the PCI troubleshooting table to determine the problem. Run RBD tests to verify problem.

More information on firmware power-up diagnostics


EISA Bus Problems

Troubleshooting
Console-Reported Failures

EISA Bus Problems Indicated at Power-Up

EISA bus failures at power-up are usually indicated by the following message displayed during power-up:

EISA Configuration Error. Run the EISA Configuration Utility.

Run the EISA Configuration Utility (ECU) when this message is displayed.  Other problems are indicated by EISA devices missing from the show config display.

Use the EISA Troubleshooting Table below to troubleshoot EISA bus problems that continue after you run the ECU.

Step	Action
1	Confirm that the EISA module and any cabling are properly seated.
2	Run the ECU to: Confirm that the system has been configured with the most recently installed controller. See what the hardware jumper and switch setting should be for each ISA controller. See what the software setting should be for each ISA and EISA controller. See if the ECU deactivated (<>) any controllers to prevent conflict. See if any controllers are locked (!), which limits the ECU's ability to change resource assignments.
3	Confirm that hardware jumpers and switches on ISA controllers reflect the settings indicated by the ECU.  Start with the last ISA module installed.
4	Run ROM-based diagnostics for the type of option: Storage adapter -- Run exer_read to exercise the storage devices off the EISA controller option. Ethernet adapter -- Run nettest to exercise an Ethernet adapter.
5	Check for bad slot by moving the last installed controller to a different slot.
6	Call option manufacturer or support for help.
Additional EISA Troubleshooting Tips


Additional EISA Troubleshooting Tips

Troubleshooting
Console-Reported Failures

Additional EISA Troubleshooting Tips

The following tips can aid in isolating EISA bus problems.

Peripheral device controllers need to be seated (inserted) carefully, but firmly, into their slots to make all necessary contacts.  Improper seating is a common source of problems for EISA modules.

The CFG files supplied with the option you want to install may not work on AlphaServer systems.  Some CFG files call overlay files that are not required on this system or may reference inappropriate system resources, for example, BIOS addresses.  Contact the option vender to obtain the proper CFG file.

Peripherals cannot share direct memory access (DMA) channels.  Assignment of more than one peripheral to the same DMA channel can cause unpredictable results or even loss of function of the EISA module.

Systems running Windows NT can assign shared interrupt lines (IRQs).   DEC OSF/1 and OpenVMS do not allow shared interrupts.

Not all EISA products work together.  EISA is an open standard, and not every EISA product or combination of products can be tested.  Violations of specifications may matter in some configurations, but do not in others.

Manufacturers of EISA options often test the most common combinations and may have a list of ISA and EISA options that do not function in combination with particular systems.  Be sure to check the documentation or contact the option vender for the most up-to-date information.

EISA systems will not function unless they are first configured using the ECU.

The ECU will not notify you if the configuration program diskette is write-protected when it attempts to write the system configuration file (system.sci) to the diskette.


PCI Problems at Power-Up

Troubleshooting
Console-Reported Failures

PCI Bus Problems Indicated at Power-Up

PCI bus failures at power-up are usually indicated by the inability of the system to see the device. Use the PCI Troubleshooting Table below to diagnose the likely cause of the problem.

Step	Action
1	Confirm that the PCI module and any cabling are properly seated.
2	Run ROM-based diagnostics for the type of option: Storage adapter -- Run exer_read to exercise the storage devices off the PCI controller option. Ethernet adapter -- Run nettest to exercise an Ethernet adapter.
3	Check for bad slot by moving the last installed controller to a different slot.
4	Call option manufacturer or support for help.


Interpreting Operator Control Panel Display Messages

Troubleshooting
No Access to Console Mode

Interpreting Operator Control Panel Power-Up Display

The following table describes the messages that may be displayed on the operator control panel power-up display on the front of the system.

Message	Meaning
TEST	Displayed while the system performs diagnostic tests and exercisers.  The type of module under test, its slot number, and the currently executing test number are also displayed.
NO MEM INSTALLED	Displayed if you power up with no memory installed.
FAIL module_type	If an error is detected in the CPU, memory, or I/O, a failure message is displayed and the Halt button LED lights for a few seconds.  The error is logged to the appropriate module via the serial control bus.  In nearly all cases, the power-up tests continue. The module_type and slot number for the field replaceable unit (FRU) that failed, along with the test number that detected the error, are also displayed. AlphaServer 2000 Note Isolating Failing SIMMs Module types and slot numbers: CPU_nn--CPU module (0--3; 0 or 1 for 2000  series systems) MEM_nn--Memory module (0--3; 0 or 1 for  2000 series systems) I/O_0--Standard I/O module (I/O backplane for  2000 series systems) I/O_1--Expansion I/O module (PCI)
CPU STATUS	Summary of CPU testing --The status of each CPU f, starting with CPU0, is displayed: "P"--CPU passed "F"--CPU failed "--"--CPU not present
STARTING CPU #	The console is starting the primary CPU.
TEST MEM BANK #	The console is testing memory.
PROBE I/O SUBSYS	The console is checking the PCI and EISA bridges.
SYSTEM RESET	The Reset button has been pressed.
Model x/xxx	When the system is under operating system control, the CPU variant (x) and the approximate CPU speed (xxx) are displayed unless you supply your own text using the ocp_text environment variable.


SIMM Note

Note:  For AlphaServer 2000 series systems, which use single-inline memory modules (SIMMs), serial ROM power-up tests will terminate if one bank of good memory is not detected.  The first two bits of bad memory (in hexadecimal) are displayed along with the FAIL MEM_nn display.


Isolating Failing SIMMs

Troubleshooting
Failing SIMMs Reported by OCP Power-Up Display

Isolating Failing SIMMs

Using the Memory Data Bits in Error Table

AlphaServer 2000 Memory Module Layout

Memory Data Bits in Error and Corresponding SIMM Positions

00-J28	20-J28	40-J28	60-J32	80-J28	A0-J28	C0-J28	E0-J32
01-J28	21-J28	41-J28	61-J32	81-J28	A1-J28	C1-J28	E1-J32
02-J28	22-J28	42-J29	62-J32	82-J28	A2-J28	C2-J29	E2-J32
03-J28	23-J28	43-J29	63-J32	83-J28	A3-J28	C3-J29	E3-J32
04-J29	24-J29	44-J30	64-J33	84-J29	A4-J29	C4-J30	E4-J33
05-J29	25-J29	45-J30	65-J33	85-J29	A5-J29	C5-J30	E5-J33
06-J29	26-J29	46-J31	66-J33	86-J29	A6-J29	C6-J31	E6-J33
07-J29	27-J29	47-J31	67-J33	87-J29	A7-J29	C7-J31	E7-J33
08-J30	28-J30	48-J32	68-J34	88-J30	A8-J30	C8-J32	E8-J34
09-J30	29-J30	49-J32	69-J34	89-J30	A9-J30	C9-J32	E9-J34
0A-J30	2A-J30	4A-J33	6A-J34	8A-J30	AA-J30	CA-J33	EA-J34
0B-J30	2B-J30	4B-J33	6B-J34	8B-J30	AB-J30	CB-J33	EB-J34
0C-J30	2C-J31	4C-J34	6C-J35	8C-J31	AC-J31	CC-J34	EC-J35
0D-J30	2D-J31	4D-J34	6D-J35	8D-J31	AD-J31	CD-J34	ED-J35
0E-J30	2E-J31	4E-J35	6E-J35	8E-J31	AE-J31	CE-J35	EE-J35
0F-J30	2F-J31	4F-J35	6F-J35	8F-J31	AF-J31	CF-J35	EF-J35
10-J32	30-J32	50-J28	70-J28	90-J32	B0-J32	D0-J28	F0-J28
11-J32	31-J32	51-J28	71-J28	91-J32	B1-J32	D1-J28	F1-J28
12-J32	32-J32	52-J28	72-J28	92-J32	B2-J32	D2-J28	F2-J28
13-J32	33-J32	53-J28	73-J28	93-J32	B3-J32	D3-J28	F3-J28
14-J33	34-J33	54-J29	74-J29	94-J33	B4-J33	D4-J29	F4-J29
15-J33	35-J33	55-J29	75-J29	95-J33	B5-J33	D5-J29	F5-J29
16-J33	36-J33	56-J29	76-J29	96-J33	B6-J33	D6-J29	F6-J29
17-J33	37-J33	57-J29	77-J29	97-J33	B7-J33	D7-J29	F7-J29
18-J34	38-J34	58-J30	78-J30	98-J34	B8-J34	D8-J30	F8-J30
19-J34	39-J34	59-J30	79-J30	99-J34	B9-J34	D9-J30	F9-J30
1A-J34	3A-J34	5A-J30	7A-J30	9A-J34	BA-J34	DA-J30	FA-J30
1B-J34	3B-J34	5B-J30	7B-J30	9B-J34	BB-J34	DB-J30	FB-J30
1C-J35	3C-J35	5C-J31	7C-J31	9C-J35	BC-J35	DC-J31	FC-J31
1D-J35	3D-J35	5D-J31	7D-J31	9D-J35	BD-J35	DD-J31	FD-J31
1E-J35	3E-J35	5E-J31	7E-J31	9E-J35	BE-J35	DE-J31	FE-J31
1F-J35	3F-J35	5F-J31	7F-J31	9F-J35	BF-J35	DF-J31	FF-J31


Using the Memory Data Bits in Error Table

For AlphaServer 2000 series systems, which use single-inline memory modules (SIMMs), serial ROM power-up tests will terminate if one bank of good memory is not detected and the console firmware cannot be loaded.  The first two data bits of bad memory (in hexadecimal) are displayed along with the FAIL MEM_nn display on the OCP.

Use the Memory Data Bits in Error table to find the corresponding SIMM position on the memory carrier module for the failing data bits.  For example; the following OCP power-up display message indicates a bad SIMM at position J28.

FAIL MEM_00 01

The following OCP power-up display message indicates two bad SIMMs at positions J33 and J34.

FAIL MEM_00 1718

After determining the position for the bad SIMMs, replace the SIMMs.

Note:  Only two bad memory data bits at a time are captured by the system diagnostics.  If more than two SIMMs are bad, you may need to repeat the SIMM isolation and replacement procedures until all bad SIMMs are replaced.


Memory Module Layout

AlphaServer 2000 Memory Module (Carrier) Layout


Power-Up Test Description and Field Replaceable Units

Troubleshooting
No Access to Console Mode

Power-Up Test Description and Field Replaceable Units (FRUs)

Test Number	Description	Likely FRU
95	SROM unloaded, sync byte sent to the DECchip 21064 processor	CPU
91	Sync byte received from the DECchip 21064 processor	CPU
8d	First backup cache initialization	CPU
89	Backup cache data line test	CPU
85	Backup cache graycode test	CPU
81	DECchip 21064 processor ECC generation test	CPU
7d	Backup cache tag store test	CPU
79	I/O tests: system bus, PCI bus, EISA bus	CPU, standard I/O (I/O backplane for 2000-series systems), or motherboard (system bus motherboard for rackmount and 2000-series systems) Note
75	Second backup cache initialization	CPU
0c	End of initial test sequence (CPU and all buses good)	CPU
18	Memory 0	MEM
16	Memory 1	MEM
14	Memory 2	MEM
12	Memory 3	MEM
07- CPU #	End of memory test (32 MB)	MEM
06	Start ESC configuration	I/O_0
05	End of ESC config/start FEPROM unload	I/O_0
04	End of FEPROM unload/start checking	I/O_0
03	End of checking, jump to unloaded console	I/O_0


Test Number 79 and show error Command

Use the show error cpu command to isolate the failing FRU.  If an error log indicates that the CPU failed test number 7, the CPU module is faulty.

If no error is logged for test number 7, the standard I/O (or I/O backplane for 2000-series systems) is the likely module at fault.  If replacing the standard I/O module does not solve the problem, the system bus motherboard is probably faulty.

For rackmount systems, which have a system bus motherboard and PCI/EISA daughter board, the system bus motherboard, that contains the T2 (system bus-to-PCI-bus bridge chip) is the motherboard most likely to fail.


Startup Action (set auto_action)

Troubleshooting
Boot Failures

Startup Action (set auto_action)

Synopsis

Set the console action at power-up.

Command

set auto_action [-default] val

Note:  Click on the [image] icon above to view an example.


Qualifier	Description
-default	Restores an environment variable to its default value.


Value	Description
halt	Causes the system to remain in console mode after the system is powered up or it crashes.
boot	Causes the system to boot automatically when it is turned on.  Causes the system to halt after a system failure.
restart	Causes the system to boot automatically when it is turned on or after it fails.


Startup Action -- Description

Set the action the console should take any time the system is powered up, crashes, or the Reset button is pressed.  When the setting involves autobooting, the system boots from the default boot device that is specified by the value of the bootdef_dev environment variable.


Startup Action - Example

Troubleshooting
Boot Failures

Example

In the following example, the system's default console action following error, halt, or power-up is changed from halt to boot.

>>> show auto_action

auto_action	halt

>>> set auto_action boot

>>> show auto_action

auto_action	boot


Boot Device (set bootdef_dev)

Troubleshooting
Boot Failures

Boot Device (set bootdef_dev)

Synopsis

Set the default boot device

Command

set bootdef_dev boot device

Note:  Click on the [image] icon above to view an example.


Qualifier	Description
boot_device	Name (or names) of your boot devices.


Boot Device -- Description

Troubleshooting
Boot Failures

Boot Device -- Description

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

Setting the default boot device simplifies the process of booting the operating system as follows:

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

Assuming the default startup action is set to boot or restart (using the set auto_action command), the system will automatically boot the operating system at power-up.

Before identifying the boot device, consider the following:

Your boot device may already be set.  (Enter the command show bootdef_dev to display the current default boot device).

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

Anytime you boot the operating system, you can override the default boot device by specifying an alternative device name on the boot command line.


Default Boot Device - Example

Troubleshooting
Boot Failures

Example

In the following example, the default device from which the system attempts to boot is set to dka0.

>>> set bootdef_dev dka0

In the next example, the default devices are set to dub0 and dka0.

>>> set bootdef_dev dub0,dka0

>>> show bootdef_dev

bootdef_dev dub0,dka0


Boot Flags (set boot_osflags)

Troubleshooting
Boot Failures

Boot Flags (set boot_osflags)

Synopsis

Set the default boot flags, and in OpenVMS, a root number.

DEC OSF/1 Command:

set boot_osflags bootflag

OpenVMS Command:

set boot_osflags root number,bootflag

Note:  Click on the [image] icon above to view examples.


Boot Flags (DEC OSF/1)

Possible boot flag settings and their meanings for DEC OSF/1 systems are:

Flag Setting	Meaning
a	Load operating system software from the specified boot device (autoboot). Boot to multi-user mode.
i	Prompt for the name of a file to load and other options (boot interactively). Boot to single user mode.
s	Stop in single-user mode. Boots /vmunix to single-user mode and stops at the # (root) prompt.
D	Full dump, implies "s" as well. By default, if DEC OSF/1 crashes, it completes a partial memory dump. Specifying "D" forces a full dump at system crash.


Root Number Settings (OpenVMS)

The root number is the directory number on the system disk on which OpenVMS files are located.  For instance:

File Location	Corresponding Root Number
[SYS0.SYSEXE]	0 (default)
[SYS1.SYSEXE]	1
[SYS2.SYSEXE]	2
[SYS3.SYSEXE]	3


Boot Flags (OpenVMS)

Possible boot flags settings and their meanings for OpenVMS 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 breakpoints.
10	4	Stop at the bootstrap breakpoints.
20	5	Omit header from secondary bootstrap image.
80	7	Prompt for the name of the secondary bootstrap file.
100	8	Halt before secondary bootstrap.
10000	16	Display debug messages during booting.
20000	17	Display user messages during booting.

Note:  Using logical ORing, you can identify multiple boot flags.


Boot Flags -- Description

Boot flags contain information that is read and used by the operating system to determine some aspects of a system bootstrap.  Under normal circumstances, the default boot flag settings will suit your environment.

To change the boot flags for the current boot only, you can pass boot flags to the operating system on the boot command line with the -flags option.

The interpretation of the boot flags is operating system dependent.

The DEC OSF/1 operating system takes only one boot flag argument, the boot flag.

The OpenVMS operating system takes two boot flag arguments, root number and boot flags.  If you specify only one argument, the argument designates the boot flag.


Default Boot Flags - Example

Troubleshooting
Boot Failures

Example 1 -- DEC OSF/1

The boot flags are set to autoboot:

>>> set boot_osflags a

Example 2-- OpenVMS

The root number is set to 1 and the boot flags are set to 2:

>>> set boot_osflags 1,2

Example 3 -- OpenVMS

The boot flags are set to 1 and the root number is not changed:

>>> set boot_osflags 1


Operating System (set os_type)

Troubleshooting
Boot Failures

Operating System (set os_type)

Synopsis

Set the default operating system

Command

set os_type os type

Note:  Click on the [image] icon above to view an example.


Operating Systems (set os_type) - Example

Troubleshooting
Boot Failures

Example

The default operating system is set to Windows NT.  When the system is powered up, halted, or restarted, the ARC console firmware will be booted.

>>> set os_type nt


os type	Description
osf	Sets the default operating system to DEC OSF/1; boots SRM firmware
vms	Sets the default operating system to OpenVMS 1; boots SRM firmware
nt	Sets the default operating system to Windows NT; boots ARC_firmware


Operating System -- Description

Before booting the operating system, you must specify the operating system that will be booted.  If the operating system that you specify, does not match the operating that is booted, you may experience problems while the operating system is running.

You specify the operating system by setting the os_type environment variable to the desired operating system.

The os_type environment variable also controls the firmware that will be booted when the system powers up, is halted or restarted, or the operating system is shut down:

If os_type is set to "vms" or "osf", the SRM firmware will be booted.

If os_type is set to "nt", the ARC firmware will be booted.

If you run the firmware for a different operating system (in order to enter the test command or run the ECU), you must reset the os_type before booting your operating system.


Controller Host Bus Node ID (set pk*0_host_id)

Troubleshooting
Console Reported Failures

set pk*0_host_id (Controller Host Bus Node ID)

Synopsis

Set the controller host bus node ID to a value between 0 and 7.

Command

set pk*0_host_id scsi controller bus node id

Note:  Replace the asterisk (*) with the adapter ID for the SCSI controller for which you are setting the default.

To get a list of the controllers on your system, enter the show config command. A list of all system devices is displayed.  The third letter is the adapter ID for the controller.

Note:  Click on the [image] icon above to view an example.


Controller Bus Node ID - Example

Troubleshooting
Console Reported Failures

Example

The default bus node ID for a SCSI controller with an adapter ID of "b" is set to bus node ID 6.

>>> set pkb0_host_id 6

>>> show pkb0_host_id

pkb0_host_id 	6


Bus Node ID	Description
0-7	Indicates the bus node ID.


Controller Host Bus Node ID --- Description

Each SCSI bus in the system requires a controller.  Buses can theoretically support up to eight devices; however, the eighth device must always be a controller.  Each device on the bus, including the controller, must have a unique ID, which is a number between 0 and 7.  This is the bus node ID number.

On each bus, the default bus node ID for the controller is set to 7.  You should not need to change the controller bus node ID unless you place two or more controllers on the same bus.

Replace the asterisk (*) with the adapter ID for the SCSI controller for which you are setting the default.

To get a list of the controllers on your system, enter the show config command.  A list of all system devices is displayed.  The third letter is the adapter ID for the controller.


Listing ARC Firmware Boot Device Names

Troubleshooting
Boot Failures

Listing ARC Firmware Boot Device Names

Step	Action	Result
1	If necessary, access the Supplementary menu.	The system displays the Supplementary menu.
2	Choose the List available boot devices... menu item and press Enter.	The system displays the Available boot devices display.
ARC Firmware Boot Device Names

Note:  The Available hardware devices display does not list tape drives or network devices.

Name	Description
multi(0)key(0)keyboard(0) multi(0)serial(0) multi(0)serial(1)	The multi() devices are located on the system module. These devices include the keyboard port and the serial line ports.
eisa(0)video(0)monitor(0) eisa(0)disk(0)fdisk(0)	The eisa() devices are provided by devices on the EISA bus. These devices include the monitor and the floppy drive.
scsi(0)disk(0)rdisk(0) scsi(0)cdrom(4)fdisk(0)	The scsi() devices are SCSI disk or CD-ROM devices. These examples represent SCSI devices on SCSI bus A. The disk drive is set to SCSI ID 0 and the CD-ROM drive is set to SCSI ID 4. Both devices have logical unit numbers of 0.

Note: Click on the [image] icon above to view an example.


Listing ARC Firmware Boot Device Names - Example

Troubleshooting
Boot Failures

Example

Hardware Configuration Display

                        Wednesday, 8-31-1994  10:51:32 AM

Devices detected and supported by the firmware:

(1)	(2)	(3)
eisa(0)video(0)monitor(0)
multi(0)key(0)keyboard(0)
eisa(0)disk(0)fdisk(0)	(Removable)
multi(0)serial(0)
multi(0)serial(1)
scsi(0)disk(0)rdisk(0)	(1 Partition)	DEC  RZ26L  (C)DEC440C
scsi(0)cdrom(5)fdisk(0)	(Removable)	DEC  RRD43  (C)DEC 0064

Press any key to continue...

                       Wednesday, 8-31-1994  10:51:32 AM

Alpha AXP Processor and System Information:

Processor ID	21064
Processor Revision	3
System Revision	0
Processor Speed	190.11 Mhz
Physical Memory	128 MB

Video Option detected:

  BIOS controlled video card

 Press any key to continue...

                        Wednesday, 8-31-1994  10:51:32 AM

EISA slot information:

Slot	Device	Identifier
0	Other	DEC2A01
1	Disk	ADP0001
2	Network	DEC4220
5	Network	DEC3002
6	Network	DEC4250
7	Display	CPQ3011
0	Disk	FLOPPY

 Press any key to continue...

                        Wednesday, 8-31-1994  10:51:32 AM

PCI slot information:

Bus	Virtual Slot	Function	Vendor	Device	Revision	Device  type
0	1	0	1000	1	1	SCSI
0	2	0	8086	482	3	EISA bridge
0	7	0	1011	2	23	Ethernet
1	0	0	1011	2	21	Ethernet
1	1	0	1000	1	2	SCSI
1	2	0	1077	1020	1	SCSI
1	3	0	1077	1020	1	SCSI
2	0	0	1011	2	23	Ethernet
2	1	0	1011	2	23	Ethernet
2	2	0	1011	2	23	Ethernet
2	3	0	1011	2	23	Ethernet

 Press any key to continue...


Hardware Configuration Display - Example

Device -- Indicates the type of device, for example, EISA or SCSI.


Hardware Configuration Display - Example

Configuration -- Indicates how the device is configured, the number of

partitions, and whether the device is a removable device.


Hardware Configuration Display - Example

Identifier string -- Indicates the device manufacturer, model number,

and other identification.


Default ARC Environment Variables

Troubleshooting
Boot Failures

Set Default Environment Variables

Caution:  Do not edit or delete the default firmware ARC environment variables. Editing the values of the default ARC firmware environment variables could result in corrupted data, or make the system inoperable.  To modify the values of the environment variables, use the menu options on the Setup the system menu.

Variable	Description
CONSOLEIN	The console input device. The default value is multi()key()keyboard()console().
CONSOLEOUT	The console output device. The default value is eisa()video()monitor()console().
FWSEARCHPATH	The search path used by the ARC firmware and other programs to locate particular files. The default value is the same as the SYSTEMPARTITION environment variable value.
TIMEZONE	The time zone in which the system is located. This variable accepts ISO/IEC9945-1 (POSIX) standard values.
A:	The default floppy drive. The default value is eisa()disk()fdisk().
FLOPPY	The capacity of the default floppy drive, either 1 (1.2 MB), 2 (1.44 MB), or 3 (2.88 MB).
FLOPPY2	The capacity of an optional second floppy drive, either N (not installed), 1, 2, or 3.
AUTOLOAD	The default startup action, either YES (boot) or  NO or undefined (remain in ARC firmware).
COUNTDOWN	The default time limit in seconds before the system boots automatically when AUTOLOAD is set to yes. The default value is 10.
KEYBOARDTYPE	The keyboard language. The default is U.S. (English).
DISABLEPCIPARITY CHECKING	Disables parity checking on the PCI bus in order to prevent machine check errors that can occur if the PCI devices has not properly set the parity on the bus. The default value is FALSE---PCI parity checking is enabled.

Other Environment Variables


Default Environment Variables

Other Environment Variables

The operating system or other programs, for example, the ECU, may create either temporary or permanent environment variables for their own use. Do not edit or delete these environment variables.


show config

Troubleshooting
Boot Failures

show config

The show config command displays all devices found on the system bus, PCI bus, and EISA bus.  You can use the information in the display to identify target devices for commands such as boot and test, as well as to verify that the system sees all the devices that are installed.

The configuration display includes the following:

Core System Status

Hose 0, 32-bit PCI

Hose 1, Bus 0, EISA

Hose 2, Bus 0, PCI

Note:  Click on the [image] icon above to view an example.


show config

Core System Status

CPU, memory, standard I/O or I/O backplane are shown with the results of power-up tests:  P (pass) or F (fail)


show config

Hose 0, Bus 0, 32-Bit PCI

Slot 0 = Ethernet adapter (ewa0)---(not present on 2000-series systems, BA720 enclosures)

Slot 1 = SCSI controller on standard I/O or I/O backplane, along with storage drives on the bus.

Slot 2 = EISA to PCI bridge chip

Slots 3-5 = Reserved

Slots 6-8 = Correspond to PCI card cage slots: PCI0, PCI1, and PCI2. In the case of storage controllers, the devices off the controller are also displayed.


show config

Hose 1, Bus 0, EISA

Slot numbers correspond to EISA card cage slots (1-8) or (1-7 for 2000-series systems, BA720 enclosures).  In the case of storage controllers, the devices off the controller are also displayed.


show config

Hose 2, Bus 0, PCI

Reserved for future expansion.


show config - Example

Troubleshooting
Boot Failures

Example

P00>>> show config

                  Digital Equipment Corporation

                      AlphaServer 2100 4/200

SRM Console T3.8-33      VMS PALcode X5.48-64, OSF PALcode X1.35-42

Component       Status  Module ID

CPU 0           P       B2020-AA DECchip (tm) 21064-3

CPU 1           P       B2020-AA DECchip (tm) 21064-3

CPU 2           P       B2020-AA DECchip (tm) 21064-3

CPU 3           P       B2020-AA DECchip (tm) 21064-3

Memory 1        P       B2021-BA  64 MB

I/O                     B2110-AA

                        dva0.0.0.0.1      RX26

 Slot Option            Hose 0, Bus 0, PCI

  0  DECchip 21040-AA   ewa0.0.0.0.0      08-00-2B-E1-01-ED

  1  NCR 53C810         pka0.7.0.1.0      SCSI Bus ID 7

                        dka0.0.0.1.0      RZ26L

                        dka600.6.0.1.0    RRD43

                        mka400.4.0.1.0    TLZ06

                        mka500.5.0.1.0    TZK11

  2  Intel 82375EB                        Bridge to Hose 1, EISA

  7  DECchip 21040-AA   ewb0.0.0.7.0      08-00-2B-3F-5B-D7

 Slot Option            Hose 1, Bus 0, EISA

  2   CPQ3011

  4   DEC4220           era0.0.0.4.1      08-00-2B-3C-B2-52

  5   DEC2500

  6   DEC4250           ewc0.0.0.6.1      08-00-2B-3A-C5-DC

 Slot Option            Hose 2, Bus 0, PCI

P00>>>


show device

Troubleshooting
Boot Failures

show device

The show device command displays the devices and controllers in the system. Use the following device name convention to interpret the system response.

Driver ID

Adapter ID

Device Unit Number

Bus Node Number

Channel Number

Slot Number

Hose Number

Note:  Click on the [image] icon above to view an example.


show device - Example

Troubleshooting
Boot Failures

Examples

>>> show device

dka0.0.0.1.0               DKA0                          RZ25L  0006

dka100.1.0.1.0             DKA100                        RZ25L  0006

dka600.6.0.1.0             DKA600                        RRD43  2893

dva0.0.0.0.1               DVA0                          RX26

mka500.5.0.1.0             MKA500                        TLZ06  0435

ewa0.0.0.0.0               EWA0              08-00-2B-3B-42-FD

pka0.7.0.1.0               PKA0                  SCSI Bus ID 7

>>> show device dk pk

dka0.0.0.1.0               DKA0                          RZ25L  0006

dka100.1.0.1.0             DKA100                        RZ25L  0006

dka600.6.0.1.0             DKA600                        RRD43  2893

dva0.0.0.0.1               DVA0                          RX26

mka500.5.0.1.0             MKA500                        TLZ06  0435

pka0.7.0.1.0               PKA0                  SCSI Bus ID 7

>>>


Storage Adapter ID

One-letter adapter designator (A,B,C. . .)


Device Unit Number

Unique device unit number; SCSI unit numbers are forced to 100 X Node ID.


Bus Node Number

Bus Node ID


Channel Number

Used for multi-channel devices


Hose Number

0 PCI_0 (32-bit PCI_); 1 EISA; 2 PCI_1


show device

Two-letter port or class driver designator

DR-RAID set device

DV-Floppy drive

ER-Ethernet port (LANCE chip, DEC 4220)

EW-Ethernet port (TULIP chip, DECchip 21040)

PK-SCSI port, DK-SCSI disk, MK-SCSI tape

PU-DSSI port, DU-DSSI disk, MU-DSSI tape


show device
For EISA options -- Correspond to EISA card cage slot numbers (1-*)

For PCI options

Slot 0 = Ethernet adapter (EWA0)---(not present on 2000-series systems, BA720 enclosures)

Slot 1=SCSI controller on standard I/O or I/O backplane, along with storage drives on the bus

Slot 2=EISA to PCI bridge chip

Slots 3-5=Reserved

Slots 6-8=Correspond to PCI card cage slots: PCI0, PCI1, and PCI2. In the case of storage controllers, the devices off the controller are also displayed.


Multiprocessor Failover

Troubleshooting
Power Problems

Multiprocessor Failover

AlphaServer systems support multiprocessor failover, which allows the system to power up and boot the operating system even if only one CPU is working.

During power-up or system reset, the serial ROM tests check for a good CPU, starting with CPU0, to serve as the primary CPU.  The primary CPU is the only CPU that tests memory and reads the flash ROM code. If a CPU fails serial  ROM tests, or if the CPU has an error logged to its serial control bus EEPROM, that CPU is disabled. The lowest numbered passing CPU serves as the primary CPU.  If all CPU modules fail their power-up diagnostics, then CPU0 will serve as the primary CPU.

If any of the CPUs fail during power-up, the halt button LED on the operator control panel lights for a few seconds and the CPU status message on the

power-up/diagnostic display indicates which CPU failed.

The following firmware commands can also be used to determine if a CPU failed

power-up tests.

show fru

show error

show config

Note:  The CPU number of the CPU serving as the primary CPU is displayed in the SRM prompt; for example, P01>>> or P02>>>, and so on.


SWXCR-XX controller

Troubleshooting
Console-Reported Failures

Troubleshooting Problems with SWXCR-xx RAID Controller

Symptom	Action
Some RAID drives do not appear on the show device display.	Valid configured RAID logical drives will appear as DRA0-DRAn, not as DKn.  Configure the drives by running the RAID Configuration Utility (RCU), following the instructions in the StorageWorks RAID Array 200 Subsystem Family Installation and Configuration Guide, EK-SWRA2-IG. Reminder: several physical disks can be grouped as a single logical DRAn device.
Drives on the SWXCR controller power up with the amber Fault light on.	Whenever you move drives onto or off the SWXCR controller, run the RAID configuration Utility to set up the drives and logical units.  Follow the instructions in the StorageWorks RAID Array 200 Subsystem Family Installation and Configuration Guide.
Image copy of DRA logical drive does not boot (OpenVMS AXP systems only).	If you copy the contents of a system disk to your RAID subsystem using the BACKUP/IMAGE command, for example, you will need to repeat several steps in the data device installation procedure, as described in the StorageWorks RAID Array 200 Subsystem Family Software User's Guide for OpenVMS AXP, AA-Q6WVA-TE, in order to make the second device a bootable device.


ew*0_protocols, er*0_protocols

Troubleshooting
Boot Failures

er*0_protocols, ew*0_protocols

Synopsis

Determine which network protocols are enabled for booting and other functions. These environment variables apply to systems with a Digital Ethernet controller (er* for the LANCE chip, DEC 4220; ew* for the TULIP chip, DECchip 21040).

set ew*0_protocols qualifier

set er*0_protocols qualifier

When entering this command, replace "*" with the adapter ID for the Ethernet controller for which you are setting the default.

To get a list of Ethernet controllers on the system, enter the show config command.  A list of all system devices is displayed.  The Ethernet controllers for which this command setting is pertinent start with the letters "ew" or "er."  The third letter is the adapter ID for the Ethernet controller.

Note:  Click on the [image] icon above to view examples.


er*0_protocols, ew*0_protocols: Qualifiers

Qualifier	Meaning
mop	Sets the network protocol to mop: the setting typically used for systems using the OpenVMS operating system.
bootp	Sets the network protocol to bootp: the setting typically used for systems using the DEC OSF/1 operating system.
bootp,mop	When the settings are used in a list, the mop protocol is attempted first, followed by bootp.


Default Boot Flags - Example

Troubleshooting
Boot Failures

Example 1

The network protocol is set to mop.

P00>>> set ewa0_protocols mop

P00>>> show ewa0_protocols

ewa0_protocols          MOP

Example 2

The network protocol is set to bootp.

P00>>> set ewa0_protocols bootp

P00>>> show ewa0_protocols

ewa0_protocols          BOOTP

Example 3

The network protocol is set to mop or bootp.

P00>>> set ewa0_protocols bootp,mop

P00>>> show ewa0_protocols

ewa0_protocols          BOOTP,MOP


Removal and Replacement: Guidelines and Warnings, BA741

Warning: Before accessing enclosure compartments:

1.	Perform orderly shutdown of the operating system.
2.	Set the DC power switch on the operator control panel to off.
3.	Remove power by unplugging the AC power cored from each power supply.

The system weighs 45.4 kg (100 lb).  To prevent personal injury and equipment damage, ensure that only one system is extended out of the cabinet at any one time and that the cabinet is stabilized before pulling the system out on its slides.

The adjustable leveling feet should be down and the cabinet's stabilizing bar fully extended before any component is extended out of the cabinet on slides.

Caution:  Static electricity can damage integrated circuits.  Always use a grounded wrist strap (29-26246) and grounded work surface when working with internal parts of a computer system.

Unless otherwise specified, you can install a field-replaceable unit (FRU) by reversing the steps shown in the removal procedure.

Continue. . .


FRU List - BA741

Removal and Replacement -
Field-Replaceable Units for AlphaServer 2100 RM/CAB (BA741 Enclosure)

Part #	Description

Cables
17-03871-01	Floppy drive cable (34-pin)
17-03940-01	KFESA DSSI internal cable (50-pin)
17-04013-01	Multinode fan/storage device cable (4-pin)
17-04031-01	OCP module cable (10-pin)
17-00083-15	Power cord
17-04014-01	Power supply control cable assembly (24-pin to 15-pin)
17-04015-01	Power supply 12V cable assembly (16-pin to 8-pin)
17-02784-03	Remote I/O cable (60-pin)
17-04025-01 or 17-04093-01	SCSI multinode cable (50-pin)
17-03664-02	SCSI RAID internal cable (50-pin)
CPU Modules
B2020-AA	KN450-AA CPU module
B2024-AA	KN460-AA CPU module
Fans
12-36202-02 or 12-36202-02	6.75-Inch Fan
54-22615-01	Fan speed control board
I/O Modules
B2110-AA  (54-23146-01)	KFE40 standard I/O module
54-23151-01	Remote I/O module
Memory Modules
B2021-BA	MS450-BA, 64MB, 80-ns memory module
B2021-CA	MS450-CA, 128MB, 80-ns memory module
B2022-CA	MS451-CA, 512MB, 80-ns memory module
Other Modules and Components
54-23180-03	OCP module
30-41765-01	Power supply
12-39309-03	Speaker
54-22601-01	System bus motherboard
54-22603-01	PCI/EISA bus daughter board
09-11194-01	Key, 1/4-turn fastener
12-37004-04	External SCSI terminator
Removable Media
RRDnn -AA	CD-ROM drives
TLZnn -LG	Tape drives
TZKnn -LG	Tape drives
RXnn -AA	Floppy drive
Fixed Disk Drives
RZnn -AA	Disk drive


Motherboard Removal, BA741: Step 1

Removal and Replacement
Motherboard/Daughter Board, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 1:  Remove all power supply cables from motherboard.

From the bottom cover, remove the power supply control and 12V cables from their connectors beneath the motherboard.  Unscrew the 3V and 5V leads from the power bus bars.

Note:  Click on the [image] icon above to go to next step.


Motherboard Removal, BA741: Step 2

Removal and Replacement
Motherboard/Daughter Board, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 2:  Remove cable bracket from rear.

Cables can remain attached to the cable bracket.

Note:  Click on the [image] icon above to go to next step.


Motherboard Removal, BA741: Step 3

Removal and Replacement
Motherboard/Daughter Board, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 3:  Remove enclosure from cabinet.

Warning: Use sufficient personnel and proper equipment when lifting and moving the rackmount server system.  The fully loaded system weighs 45.5 kg (100 lb.)

Note:  Click on the [image] icon above to go to next step.


Motherboard Removal, BA741: Step 4 and Step 5

Removal and Replacement
Motherboard/Daughter Board, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 4:  Remove CPU and memory modules.

Warning: CPU and memory modules have parts that operate at high temperatures.  Wait 2 minutes after power is removed before handling these modules.

Step 5:  Remove any cables exiting the PCI/EISA bus compartment.

Unplug and remove the standard I/O cables from the PCI/EISA bus compartment.  Remove any other cables that exit from the PCI/EISA bus compartment.  If you are going to replace the PCI/EISA bus daughter board, remove all the modules from the compartment as well.

Note:  Click on the [image] icon above to go to next step.


Motherboard Removal, BA741: Step 6

Removal and Replacement
Motherboard/Daughter Board, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 6:  Separate the front and rear halves of the enclosure.

Remove the four screws and pull the rear half back until it separates from the front.

Note:  Click on the [image] icon above to go to next step.


Motherboard Removal, BA741: Step 7

Removal and Replacement
Motherboard/Daughter Board, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 7:  Lift off rear half and stand on rear.

Note:  Click on the [image] icon above to go to next step.


Motherboard Removal, BA741: Step 8

Removal and Replacement
Motherboard/Daughter Board, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 8:  Remove the four power bus bars.

Note:  Click on the [image] icon above to go to next step.


Motherboard Removal, BA741: Step 9

Removal and Replacement
Motherboard/Daughter Board, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 9:  Separate system bus and PCI/EISA bus compartments.

Note:  Click on the [image] icon above to go to next step.


Motherboard Removal, BA741: Step 10

Removal and Replacement
Motherboard/Daughter Board, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 10:  Remove system bus motherboard.

Note:  When replacing module, install screws in order indicated.

Note:  Click on the [image] icon above to go to next step.


Motherboard Removal, BA741: Step 11

Removal and Replacement
Motherboard/Daughter Board, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 11:  Remove PCI/EISA daughter board.

Note:  When replacing module, install screws in order indicated.


Remote I/O Module Removal, BA741: Step 1

Removal and Replacement
Remote I/O Module, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 1: Remove screw at rear cutout.

Note:  Click on the [image] icon above to go to next step.


Remote I/O Module Removal, BA741: Step 2

Removal and Replacement
Remote I/O Module, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 2: Remove remote I/O module through bottom cover.


Standard I/O Removal, BA741: Step 1

Removal and Replacement
Standard I/O, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 1:  Open the PCI/EISA compartment door, disconnect the cables and remove the module.

Note:  Click on the [image] icon above to go to next step.


Standard I/O Removal, BA741: Step 2

Removal and Replacement
Standard I/O, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 2: Move chips to new module.

Move the socketed Ethernet station address ROM (position E72) and NVRAM chip (position E30) to the replacement standard I/O module and set jumpers to match previous settings.

J3--Power supply mode jumper	When installed, dual power supplies operate in redundant mode
J5--Programming voltage jumper	Internal use only
J6--Fail-safe jumper	When installed, selects the fail-safe loader firmware


OCP Cable Removal, BA741

OCP Module Cable (10-pin)


Floppy Cable Removal, BA741

Floppy Drive Cable (34-pin)


SCSI Multinode Cable (50-pin) Removal, BA741

SCSI Multinode Cable (50-pin)


KFESA DSSI Internal Cable (50-pin) Removal, BA741

KFESA DSSI Internal Cable (50-pin)


Remote I/O Cable Removal, BA741

Remote I/O Cable (60-pin)


OCP Module Removal, BA741

Removal and Replacement
OCP Module, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Open the mass storage compartment, disconnect the OCP cable and remove the OCP module.


CPU Module Removal, BA741: Step 1

Removal and Replacement
CPU Module, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Note: Different CPU types  cannot be used within the same system.  Example: A KN450 CPU module and a KN460 CPU module cannot be used in the same system.

Step 1: Check for errors logged to the CPU.

Verify that errors have been logged through the serial control bus before replacing a CPU module.

1.  Enter the show fru command to check for test-directed diagnostic (TDD) errors logged to the CPU.

In the following example, a test-directed diagnostic (TDD) is logged for CPU0.

Example

P00>>> show fru

                           Rev               Events logged

Slot   Option  Part#      Hw Sw  Serial#     SDD     TDD

  0    IO      B2110-AA   C4 0   KA347DWV06  00      00

  2    CPU0    B2020-AA   B2 9   ML33900048  00      01

  3    CPU1    B2020-AA   B2 9   KA34509090  00      00

  6    MEM2    B2022-CA   A1 0   ML34100009  00      00

  7    MEM3    B2022-CA   A1 0   ML34100008  00      00

.

.

.

P00>>>

2.  Enter the show error cpu0 command to verify that an error, other than test number 00, is currently logged for that CPU.

Example

P00>>> show error cpu0

CPU0 Module EEROM Event Log

Test Directed Errors

Entry: 0  Test Number: 02       Subtest Number: 02

Parameter 1: 00000000,00000010

Parameter 2: ffffffff,ffffffff

Parameter 3: fffffeff,ffffffff

CPU Event Counters

C3_CA_NOACK     0

.

.

.

C3_DT_PAR_E     0

C3_DT_PAR_O     0

B-Cache Correctable Errors

Entry   Syndrome        Offset L        Offset H        Count

No Entries Found

P00>>>

Note:  Click on the [image] icon above to go to next step.


CPU Module Removal, BA741: Step 2

Removal and Replacement
CPU Module, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 2: If the CPU has an error logged, other than for test number 00, perform power shutdown, remove system bus cover, and replace the CPU module.

An event log for test  number 00 does not indicate a bad CPU.  Test number 00 indicates that a CPU failover occurred sometime in the past.

Note: All systems must have a CPU module installed in system bus slot 2 (CPU0).

All system bus slots must be populated with a printed circuit board (PCB)

module or a clear plastic module to assure proper airflow over each PCB

module.

Warning: CPU and memory modules have parts that operate at high temperatures.  Wait 2 minutes after power is removed before handling these modules.

System Bus Card Cage

System Bus Configuration (according to number of CPUs)

Note:  Click on the [image] icon above to go to next step.


System Bus Card Cage


System Bus Configurations


CPU Module Removal, BA741: Step 3

Removal and Replacement
CPU Module, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 3: Verify that errors are no longer logged for the CPU.

Use the show fru command to verify that the errors are cleared.

Note:  To clear an event logged for test number 00 (CPU failover), use the clear_error cpu# command.

Example

P00>>> show fru

                           Rev               Events logged

Slot   Option  Part#      Hw Sw  Serial#     SDD     TDD

  0    IO      B2110-AA   C4 0   KA347DWV06  00      00

  2    CPU0    B2020-AA   B2 9   ML33900048  00      00

  3    CPU1    B2020-AA   B2 9   KA34509090  00      00

  6    MEM2    B2022-CA   A1 0   ML34100009  00      00

  7    MEM3    B2022-CA   A1 0   ML34100008  00      00

.

.

.

P00>>>


Memory Module Removal, BA741

Removal and Replacement
Memory Module, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Remove the system bus compartment cover and remove the memory module.

Note: All system bus slots must be populated with a printed circuit board (PCB)

module or a clear plastic module to assure proper airflow over each PCB

module.

Warning: Memory and CPU modules have parts that operate at high temperatures.  Wait 2 minutes after power is removed before handling these modules.


Fans, Fan Speed Control Module Removal, BA741: Step 1

Removal and Replacement
Fans, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 1:  Unplug fans.

Note:  Click on the [image] icon above to go to next step.


Fans, Fan Speed Control Module Removal, BA741: Step 2

Removal and Replacement
Fans, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 2:  Remove fan assembly and replace failing fan.


Removal - Fan Speed Control Board, BA741

Fan Speed Control Board


Removal - Multinode fan/storage device cable, BA741

Multinode Fan/Storage Device Cable (4-pin)


Floppy Drive, BA741

Floppy Drive


Speaker, BA741

Speaker


Removable Media Devices, Removing, BA741

Removable Media Drives (Tape and CD-ROM)


Power Cord Removal, BA741

Removal and Replacement
Power Cord, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Power Cord


Power Cord Part Numbers, BA741

Removal and Replacement
Power Cord, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Power Cord Numbers

Country	Power Cord BN Number	Digital Number
U.S., Japan, Canada	Included	17-00083-51
Australia, New Zealand	BN19J-2E	17-00198-13
Central European (Aus, Bel, Fra, Ger, Fin, Hol, Nor, Swe, Por, Spa)	BN19D-2E	17-00199-22
U.K., Ireland	BN19B-2E	17-00209-12
Switzerland	BN04B-2E	17-00210-12
Denmark	BN19L-2E	17-00310-06
Italy	BN19N-2E	17-00364-17
India, South Africa	BN19T-2E	17-00456-15
Israel	BN18Y-2E	17-00457-15


Power Supply Removal, BA741: Step 1 and Step 2

Removal and Replacement
Power Supply, AlphaServer 2100 RM/CAB (BA471 Enclosure)

Step 1:  Remove power supply control and 12V cables.

Step 2:  Unscrew 3V and 5V leads from power bus bars.

Use a number two Phillips screwdriver to remove the power supply leads.

Note:  When reinstalling cables click here for an illustration of labeled power bus bars and cable connectors.

Note:  Click on the [image] icon above to go to next step.


Power Supply Removal, BA741: Step 3

Removal and Replacement
Power Supply, AlphaServer 2100 RM/CAB (BA471 Enclosure)

Step 3:  Remove power supply.

Warning:  Hazardous voltages contained within.  Do not service.  Return to factory for service.


Power Bus Bars and Connectors on Motherboard, BA741

Power Bus Bars and Power Connectors on Motherboard


Accessing FRUs, BA741: Step 1

Removal and Replacement
Accessing FRUs, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 1:  Stabilize cabinet.

Warning:  The system weighs 45.4 kg (100 lb).  To prevent personal injury and equipment damage, ensure that only one system is extended out of the cabinet at any one time and that the cabinet is stabilized before pulling the system out on its slides.

The adjustable leveling feet should be down and the cabinet's stabilizing bar fully extended before any component is extended out of the cabinet on slides.

Example of Cabinet Stabilized with Leveling Feet and Stabilizing Bar

Note:  Click on the [image] icon above to go to next step.


Accessing FRUs, BA741: Step 2

Removal and Replacement
Accessing FRUs, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 2:  Remove front panel.

Note:  Click on the [image] icon above to go to next step.


Accessing FRUs, BA741: Step 3

Removal and Replacement
Accessing FRUs, AlphaServer 2100 RM/CAB (BA741 Enclosure)

Step 3:  Slide out rackmount system.

 Accessing the mass storage compartment.

 Accessing the PCI/EISA bus compartment.

 Accessing the system bus compartment.


Accessing the Mass Storage Compartment, BA741

Accessing the Mass Storage Compartment

Note:  The mass storage compartment cover requires a number 1 screwdriver.


Accessing the PCI/EISA Compartment, BA741

Accessing the PCI/EISA Compartment


Accessing the System Bus Compartment, BA741

Accessing the System Bus Compartment


FRUs, Upper Compartments, BA741

Removal and Replacement
Upper Compartments--FRUs, AlphaServer 2100 RM/CAB (BA741 Enclosure)


FRUs, Lower Compartments, BA741

Removal and Replacement
Lower Compartments--FRUs, AlphaServer 2100 RM/CAB (BA741 Enclosure)


Power Supply Control Cable, BA741

Power Supply Control Cable Assembly


Power Supply 12V Cable Assembly, BA741

Power Supply 12V Cable Assembly


SCSI RAID Internal Cable, BA741

SCSI RAID Internal Cable (50 pin)


Disk Drives, BA741

Disk Drives


BA740 Enclosure FRUs and Procedures

FRU List and Procedures

AlphaServer 2000 (BA720 Enclosure)---FRU Removal and Replacement

AlphaServer 2100 (BA740 Enclosure)---FRU Removal and Replacement

AlphaServer 2100 RM/CAB (BA741 Enclosure)---FRU Removal and Replacement


Removal and Replacement: Guidelines and Warnings, BA740

Caution: Before opening or removing system panels:

1.	Perform orderly shutdown of the operating system.
2.	Set the DC power switch on the operator control panel to off.
3.	For power supplies with AC On/Off switches, set switches to off.
4.	Unplug AC power cords.

Static electricity can damage integrated circuits.  Always use a grounded wrist strap (29-26246) and grounded work surface when working with internal parts of a computer system.

Unless otherwise specified, you can install a field-replaceable unit (FRU) by reversing the steps shown in the removal procedure.

Continue. . .


FRU List - BA740

Removal and Replacement -
Field-Replaceable Units for AlphaServer 2100 Systems (BA740 Enclosure)

Part #	Description

Cables
17-03870-01	Fan/removable media cable (12-pin)
17-03871-01	Floppy drive cable (34-pin)
17-03868-01	Internal StorageWorks power cable (5-pin)
17-03869-01	OCP module cable (10-pin)
17-00083-15	Power cord
17-02784-03	Remote I/O cable (60-pin)
17-03872-01	SCSI cable (50-pin)
17-03873-01	SCSI multinode cable (50-pin)
17-03948-01	SCSI RAID internal cable (50-pin)
CPU Modules
B2020-AA	KN450-AA CPU module
B2024-AA	KN460-AA CPU module
Fans
12-23609-09	4.5-Inch Fan
12-36202-02	6.75-Inch Fan
54-23260-01	Fan speed control board
I/O Modules
B2110-AA  (54-23146-01)	KFE40 standard I/O module
54-23151-01	Remote I/O module
Internal StorageWorks
RZnn - VA	StorageWorks disk drive
54-22903-01	Internal StorageWorks backplane
BA35X-MB	Internal StorageWorks terminator
BA35X-MC	Internal StorageWorks jumper
Memory Modules
B2021-BA	MS450-BA, 64MB, 80-ns memory module
B2021-CA	MS450-CA, 128MB, 80-ns memory module
B2022-CA	MS451-CA, 512MB, 80-ns memory module
Other Modules and Components
54-23149-01	Motherboard
54-23180-01	OCP module
30-41274-01	Power supply
12-39309-01	Speaker
12-36437-03	Key for door
12-37004-04	External SCSI terminator
12-41296-01	Internal SCSI terminator
Removable Media
RRDnn -CA	CD-ROM drives
TLZnn -LG	Tape drives
TZKnn -LG	Tape drives
RXnn -AA	Floppy drive


Motherboard Removal, BA740: Step 1

Removal and Replacement
Motherboard, AlphaServer 2100 (BA740 Enclosure)

Step 1:  Remove modules and divider

Warning: Memory and CPU modules have parts that operate at high temperatures.  Wait 2 minutes after power is removed before handling these modules.

Note:  Click on the [image] icon above to go to next step.


Motherboard Removal, BA740: Step 2

Removal and Replacement
Motherboard, AlphaServer 2100 (BA740 Enclosure)

Step 2:  Remove power supplies.

Note:  Click on the [image] icon above to go to next step.


Motherboard Removal, BA740: Step 3

Removal and Replacement
Motherboard, AlphaServer 2100 (BA740 Enclosure)

Step 3:  Detatch cables and remove motherboard.

When replacing motherboard, install screws in order indicated.


Remote I/O Removal, BA740

Remote I/O Module


Standard I/O Removal, BA740: Step 1

Removal and Replacement
Standard I/O, AlphaServer 2100 (BA740 Enclosure)

Step 1: Disconnect the cables and remove the module.

Note:  Click on the [image] icon above to go to next step.


Standard I/O Removal, BA740: Step 2

Removal and Replacement
Standard I/O, AlphaServer 2100 (BA740 Enclosure)

Step 2: Move chips to new module.

Move the socketed Ethernet station address ROM (position E72) and NVRAM chip (position E30) to the replacement standard I/O module and set jumpers to match previous settings.

J3--Power supply mode jumper	When installed, dual power supplies operate in redundant mode
J5--Programming voltage jumper	Internal use only
J6--Fail-safe jumper	When installed, selects the fail-safe loader firmware


OCP Cable Removal, BA740

OCP Module Cable (10-pin)


SCSI RAID Internal Cable, Removal, BA740

SCSI RAID Internal Cable (50-pin)


Floppy Cable Removal, BA740

Floppy Drive Cable (34-pin)


SCSI Cable (50-pin) Removal, BA740

SCSI Cable (50-pin)


SCSI Multinode Cable (50-pin) Removal, BA740

SCSI Multinode Cable (50-pin)


Remote I/O Cable Removal, BA740

Remote I/O Cable (60-pin)


OCP Module Removal, BA740: Step 1

Removal and Replacement
OCP Module, AlphaServer 2100 (BA740 Enclosure)

Step 1:  Detatch OCP cable and remove OCP cover.

Note:  Click on the [image] icon above to go to next step.


OCP Module Removal, BA740: Step 2

Removal and Replacement
OCP Module, AlphaServer 2100 (BA740 Enclosure)

Step 2:  Remove OCP module.


CPU Module Removal, BA740: Step 1

Removal and Replacement
CPU Module, AlphaServer 2100 (BA740 Enclosure)

Note: Different CPU types  cannot be used within the same system.  Example: A KN450 CPU module and a KN460 CPU module cannot be used in the same system.

Step 1: Check for errors logged to the CPU.

Verify that errors have been logged through the serial control bus before replacing a CPU module.

1.  Enter the show fru command to check for test-directed diagnostic (TDD) errors logged to the CPU.

In the following example, a test-directed diagnostic (TDD) is logged for CPU0.

Example

P00>>> show fru

                           Rev               Events logged

Slot   Option  Part#      Hw Sw  Serial#     SDD     TDD

  0    IO      B2110-AA   C4 0   KA347DWV06  00      00

  2    CPU0    B2020-AA   B2 9   ML33900048  00      01

  3    CPU1    B2020-AA   B2 9   KA34509090  00      00

  6    MEM2    B2022-CA   A1 0   ML34100009  00      00

  7    MEM3    B2022-CA   A1 0   ML34100008  00      00

.

.

.

P00>>>

2.  Enter the show error cpu0 command to verify that an error, other than test number 00, is currently logged for that CPU.

Example

P00>>> show error cpu0

CPU0 Module EEROM Event Log

Test Directed Errors

Entry: 0  Test Number: 02       Subtest Number: 02

Parameter 1: 00000000,00000010

Parameter 2: ffffffff,ffffffff

Parameter 3: fffffeff,ffffffff

CPU Event Counters

C3_CA_NOACK     0

.

.

.

C3_DT_PAR_E     0

C3_DT_PAR_O     0

B-Cache Correctable Errors

Entry   Syndrome        Offset L        Offset H        Count

No Entries Found

P00>>>

Note:  Click on the [image] icon above to go to next step.


CPU Module Removal, BA740: Step 2

Removal and Replacement
CPU Module, AlphaServer 2100 (BA740 Enclosure)

Step 2: If the CPU has an error logged, other than for test number 00, perform power shutdown and replace the CPU module.

An event log for test  number 00 does not indicate a bad CPU.  Test number 00 indicates that a CPU failover occurred sometime in the past.

Note: All systems must have a CPU module installed in system bus slot 2 (CPU0).

All system bus slots must be populated with a printed circuit board (PCB)

module or a clear plastic module to assure proper airflow over each PCB

module.

Warning: CPU and memory modules have parts that operate at high temperatures.  Wait 2 minutes after power is removed before handling these modules.

System Bus Card Cage

System Bus Configuration (according to number of CPUs)

Note:  Click on the [image] icon above to go to next step.


System Bus Card Cage


System Bus Configuration

System Bus Configurations


CPU Module Removal, BA740: Step 3

Removal and Replacement
CPU Module, AlphaServer 2100 (BA740 Enclosure)

Step 3: Verify that errors are no longer logged for the CPU.

Use the show fru command to verify that the errors are cleared.

Note:  To clear an event logged for test number 00 (CPU failover), use the clear_error cpu# command.

Example

P00>>> show fru

                           Rev               Events logged

Slot   Option  Part#      Hw Sw  Serial#     SDD     TDD

  0    IO      B2110-AA   C4 0   KA347DWV06  00      00

  2    CPU0    B2020-AA   B2 9   ML33900048  00      00

  3    CPU1    B2001-AA   B2 9   KA34509090  00      00

  6    MEM2    B2022-CA   A1 0   ML34100009  00      00

  7    MEM3    B2022-CA   A1 0   ML34100008  00      00

.

.

.

P00>>>


Memory Removal, BA740

Memory Module

Note: All system bus slots must be populated with a printed circuit board (PCB)

module or a clear plastic module to assure proper airflow over each PCB

module.

Warning: Memory and CPU modules have parts that operate at high temperatures.  Wait 2 minutes after power is removed before handling these modules.


Fans, Fan Speed Control Module Removal, BA740: Step 1

Removal and Replacement
Fans and Fan Speed Control Board, AlphaServer 2100 (BA470 Enclosure)

Step 1:  Remove fan assembly.

Note:  Click on the [image] icon above to go to next step.


Fans, Fan Speed Control Module Removal, BA740: Step 2

Removal and Replacement
Fans and Fan Speed Control Board, AlphaServer 2100 (BA470 Enclosure)

Step 2:  Remove fan component.

Caution:  Two types of 6.75 inch fans are used with the BA740 enclosure. One type, shown as Model A in the illustration, manufactured by Sanyo Denki, needs to be oriented with the ground boss to the top.  If this fan is not in the proper orientation, system bus components may overheat.


Fan/Removable media Cable Removal, BA740

Fan/Removable Media Cable (12-pin)


Internal Storage Works Terminator and Jumper Removal, BA740

Internal StorageWorks Terminator and Jumper


Removal - Internal Storage Works Drive, BA740

StorageWorks Disk Drive

Note:  If the StorageWorks drives are plugged into an SWXCR-xx controller,

you can "hot swap" drives, that is, you can add or replace drives without first shutting down the operating system or powering down the server hardware.

For more information, see StorageWorks RAID Array 200 Subsystem Family Installation and Configuration Guide, EK-SWRA2-IG.

If the StorageWorks drives are not plugged into an SWXCR-xx controller,

you will need to shut down the operating system before swapping a drive. However, you will not need to power down the server before installing the drives.


Floppy Drive Removal, BA740

Floppy Drive


Removal - Internal Storage Works Power Cable

Internal StorageWorks Power Cable (5-pin)


Floppy Cable Removal, BA740

Speaker


Removable Media Devices, Removing, BA740

Removable Media Drives (Tape and CD-ROM)


Power Cord Removal, BA740

Removal and Replacement
Power Cord, AlphaServer 2100 (BA740 Enclosure)

Power Cord


Power Cord Part Numbers

Removal and Replacement
Power Cord, AlphaServer 2100 (BA740 Enclosure)

Power Cord Numbers

Country	Power Cord BN Number	Digital Number
U.S., Japan, Canada	BN27Y-1J	17-00083-15
Australia, New Zealand	BN19H-2E	17-00198-14
Central European (Aus, Bel, Fra, Ger, Fin, Hol, Nor, Swe, Por, Spa)	BN19C-2E	17-00199-21
U.K., Ireland	BN19A-2E	17-00209-15
Switzerland	BN19E-2E	17-00210-13
Denmark	BN19K-2E	17-00310-08
Italy	BN19M-2E	17-00364-18
India, South Africa	BN19S-2E	17-00456-16
Israel	BN18L-2E	17-00457-16


Storageworks Backplane Removal, BA740: Step 1

Removal and Replacement
StorageWorks Backplane, AlphaServer 2100 (BA740 Enclosure)

Step 1:  Remove internal StorageWorks shelf.

Note:  Click on the [image] icon above to go to next step.


Storageworks Backplane Removal, BA740: Step 2

Removal and Replacement
StorageWorks Backplane, AlphaServer 2100 (BA740 Enclosure)

Step 2:  Remove internal StorageWorks backplane.


Power Supply Removal, BA740

Power Supply

Warning:  Hazardous voltages contained within.  Do not service.  Return to factory for service.


Door and Panel Removal, BA740

Removal and Replacement
Removal of Door and Panels, AlphaServer 2100 (BA740 Enclosure)

Caution:  Unit will shut down when side panel is opened.  Access only after performing an orderly shut down and unplugging the AC power cord(s).


Front/Left View, BA740

Removal and Replacement
Front/Left View--FRUs, AlphaServer 2100 (BA740 Enclosure)


Rear/Right View, BA740

Removal and Replacement
Rear/Right View--FRUs, AlphaServer 2100 (BA740 Enclosure)


Running ROM-Based Diagnostics

Troubleshooting
ROM-Based Diagnostics (RBDs)

Running ROM-Based Diagnostics

ROM-based diagnostics (RBDs), which are part of the console firmware that is loaded from the FEPROM on the standard I/O module(or I/O backplane on BA720 enclosures), offer many powerful diagnostic utilities, including the ability to examine error logs from the console environment and run system- or device-specific exercisers.

AlphaServer RBDs rely on exerciser modules, rather than functional tests, to isolate errors. The exercisers are designed to run concurrently, providing a maximum bus interaction between the console drivers and the target devices.

The multitasking ability of the console firmware allows you to run diagnostics in the background (using the background operator & at the end of the command).  You run RBDs by using console commands.

Note:  ROM-based diagnostics, including the test command, are run from the SRM console (firmware used by OpenVMS and DEC OSF/1).  If you are running Windows NT, you will need to switch consoles.

RBD console commands do not log errors to the serial control bus EEPROMs.  Errors are reported to the console terminal and/or the console event log.

Acceptance Testing and Initialization


Acceptance Testing and Initialization

Perform the acceptance testing procedure listed below after installing a system or whenever adding or replacing the following:

CPU modules

Memory modules

Standard I/O module or I/O backplane

Motherboard or system bus motherboard

Daughter board (rackmount systems)

Storage devices

EISA or PCI options

1.  Run the RBD acceptance tests using the test command.

2.  If you have added, moved, or removed an EISA or ISA option, run the EISA    Configuration Utility (ECU).

3.  Bring up the operating system.

4.  Run DEC VET to test that the operating system is correctly installed.


DEC VET

Digital's DEC Verifier and Exerciser Tool (DEC VET) software is a mulitpurpose system maintenance tool that performs exerciser-oriented maintenance testing.  DEC VET consists of a manager and exercisers.  The DEC VET manager controls the exercisers.  The exercisers test system hardware and the operating system.  DEC VET supports various exerciser configurations, ranging from a single device exerciser to full sysetm loading -- that is, simultaneous exercising of multiple devices.


Diagnostic Commands

Troubleshooting
ROM-Based Diagnostics (RBDs)

Running Systems Diagnostics

Summary of Diagnostic and Related Commands

Command	Function
Acceptance Testing
test	Quickly tests the core system.  The test command is the primary diagnostic for acceptance testing and console environment diagnosis.
Error Reporting
clear_error	Clears error information logged through the serial control bus.  The show error command displays errors logged to the serial control bus EEROMs.
show error	Reports core system errors captured by test-directed diagnostics (TDD), via the RBDs, and symptom-directed diagnostics (SDD), via the operating system.
show fru	Reports system bus module identification numbers and summary error information.
Extended Testing and Troubleshooting
exer_read	Tests a disk by performing random reads on the specified device.
memexer	Exercises memory by running a specified number of memory tests.  The tests are run in the background.
memexer_mp	Tests memory in a multiprocessor system by running a specified number of memory exerciser sets.  The tests are run in the background.
net -ic	Initializes the MOP counters for the specified Ethernet port.
net -s	Displays the MOP counters for the specified Ethernet port.
nettest	Runs external loopback tests for specified EISA- or PCI-based Ethernet ports.
sys_exer	Exercises core system.  Runs tests concurrently.
Loopback Testing
test_lb	Conducts loopback tests for COM2 and the parallel port in addition to quick core system tests.
sys_exer lb	Conducts loopback tests for COM2 and the parallel port in addition to core system tests.
nettest	Runs external or internal loopback tests for specified EISA- or PCI-based Ethernet ports.
Diagnostic-Related Commands
kill	Terminates a specified process.
kill_diags	Terminates all currently executing diagnostics.
show_status	Reports the status of currently executing test/exercisers.


Command Reference --- sys_exer

Troubleshooting
ROM-Based Diagnostics (RBDs)

sys_exer

Synopsis

Exercises core system.  Runs tests concurrently.

Command

sys_exer ([lb])

Note:  Click on the [image] icon above to view an example.


sys_exer --- Description

The sys_exer command runs firmware diagnostics for the entire core system.  The same tests that are run using the test command are run with sys_exer, only these tests are run concurrently and in the background.  Nothing is displayed unless an error occurs.

Note:  Some processes started using sys_exer are not stopped using the kill and kill_diags commands.  Use the init command to terminate all sys_exer processes.

Because the sys_exer tests are run concurrently and indefinitely (until you stop them with the init command), they are useful in flushing out intermittent hardware problems.

Note:  By default, no write tests are performed on disk and tape drives.  Media must be installed to test the floppy drive and tape drives.  Certain memory errors that are reported by the OCP may not be reported by the ROM-based diagnositcs.  Always check the power-up/diagnostic display before running diagnostic commands.


Arguments	Description
[lb]	The loopback option includes console loopback tests for the COM2 serial port and the parallel port during the test sequence.


sys_exer - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example

>>> sys_exer

>>> sys_exer

Exercising the Memory

Exercising the DK* Disks (read only)

Exercising the MK* Disks (read only)

Exercising the Floppy (read only)

Exercising the VGA (Alphanumeric Mode only)

Exercising the EWA0 network

Type init in order to boot the operating system

>>>show_status

ID -------	Program -------	Device ------	Pass ----	Hard/Soft -----	Bytes Written -------	Bytes Read -------
00000001	idle	system	0	0    0	0	0
0000006f	memtest	memory	1	0    0	35651584	35651584
00000070	memtest	memory	1	0    0	35651584	35651584
00000077	memtest	memory	1	0    0	37748736	37748736
0000007e	exer_kid	dka0.0.0.1.0	0	0    0	0	69120
0000007f	exer_kid	dka600.6.0.1	0	0    0	0	66560
00000093	exer_kid	dva0.0.0.0.1	0	0    0	0	0
000000d5	nettest	ewa0.0.0.0.0	13	0    0	308672	308672
>>> init


Command Reference --- show error

Troubleshooting
ROM-Based Diagnostics (RBDs)

show error

Synopsis

Reports kernal system errors captured by test-directed diagnostics (TDD) and symptom-directed diagnostics (SDD).

Command

show error ([target [target . . . ]])

Memory Errors

CPU Errors


show error --- Description

The show error command reports error information based on the serial control bus EEPROM data.  Both the operating system and the ROM-based diagnostics log errors to the serial control bus EEPROMs.  This functionality provides the ability to generate an error log from the console environment.

A closely related command, show fru, reports FRU and error information for FRUs.


Argument	Description
[target]	CPU{0,1,2,3}, mem{0,1,2,3}, and io.


Memory Error - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example -- Memory Errors

Note:  Certain memory errors that are reported by the OCP may not be reported by the ROM-based diagnostics.  Always check the power-up/diagnostic display before running diagnostic commands.  Correctible errors are logged for the same memory module, the specified correctible errors are logged for the same memory module, the specified SIMMs (AlphaServer 2000 systems) or module should be replace.  For all unncorrectible errors, indicated by event types 01 and 10, you should replace the failing SIMM(s) (AlphaServer 2000 systems) or memory module.  Only two bad memory data bits at a time are caputed by the system diagnostics.  For AlphaServer 2000 systems:  If more than two SIMMs are bad, you may need to repeat the SIMM isolation and replacement procedures until all bad SIMMs are replaced.

>>> show error mem3

Test Directed Errors

No Entries Found

Symptom Directed Errors

Entry	Fail Address	Bits/Syndrome	Bank #	ASIC #	Source	Event Type
0	0be21e00	0cd2	1	1	1	00
1	0be26b80	0cd2	1	1	1	00
2	04224020	14,09	2	1	1	01
>>>


CPU Error - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example -- CPU Errors

Note:  Different CPU types cannot be used within the same system.  Example:  A KN450 CPU module and a KN460 CPU module cannot be used in the same system.  If an event is logged for any other test than test number 00, the CPU should be replace.  Event logs with just test number 00 do not indicate a bad CPU.  Test number 00 indicates that a CPU failover occurred sometime in the past.  All systems must have a CPU module installed in system bus slot 2 (CPU0).

>>> show error cpu0

CPU0 Module EEROM Event Log

Test Directed Errors

Entry:  0	Test Number:  02	Subtest Number:  02
Parameter 1:  00000000,00000010

Parameter 2:  ffffffff,ffffffff

Parameter 3:  ffffffff,ffffffff

CPU Event Counters

C3_CA_NOACK     0

    .

    .

    .

C3_DT_PAR_E     0

C3_DT_PAR_O     0

B-Cache Correctable Errors

Entry    Syndrome    Offset L    Offset H     Count

No Entries Found

>>>


Test Number

A test number other than 00 indicates the CPU should be replaced.  Test number 00 indicates a CPU failover has occured.


Entry

Event log entry number.


Fail Address

The zero-based module failing address.  If the module is configured at base address zero, then the failing address is the offset to the failing DRAM.


Bits/Syndrome

First two failing bits (in hexadecimal) for uncorrectable errors; syndrome (in hexadecimal) for correctable errors.  For SIMM memory (AlphaServer 2000 systems), the postion (J#) for the corresponding failing SIMMs is also displayed.


Bank Number

The bank number of the failing DRAM.


ASIC Number

The asic chip that detected the error.


Source

The software or firmware that logged the error.

0	SROM

1	SRM firmware (RBDs)

2	OSF

3	VMS

4	NT

5-7	Reserved


Event Type

00	Data correctable

01	Data uncorrectable

10	Data uncorrectable (first two bits logged)

11	Other (address and syndrome fields not valid)


Command Reference --- clear_error

Troubleshooting
ROM-Based Diagnostics (RBDs)

clear_error

Synopsis

Clears error information logged through the serial control bus.

Command

Clear_error ([all, cpu0-3, mem0-3, io])

Example

Note:  Click on the [image] icon above to view an example.


clear_error --- Description

The clear_error command clears error information logged to the serial control bus EEPROMs.  The show fru command can be used to verify that errors have been cleared ( the events logged columns will be set to zeros).


Argument	Description
[target]	all, CPU{0,1,2,3}, mem{0,1,2,3}, and io.


clear_error - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example

>>> clear_error all

>>>


Command Reference --- exer_read

Troubleshooting
ROM-Based Diagnostics (RBDs)

exer_read

Synopsis

Test a disk by performing random reads.

Command

exer_read [-sec seconds] [device name device name . . . ]

Note:  Click on the [image] icon above to view an example.


exer_read --- Description

The exer_read command tests a disk by performing random reads of 2048 bytes on one or more devices.  The exercisers are run in the background and nothing is displayed unless an error occurs.

The tests continue until one of the following conditions occurs:

1.	All blocks on the device have been read for a passcount of d_passes (default is 1).

2.	The exer_read process has been terminated via the kill or kill_diags commands, or Ctrl/C.

3.	The specified time has elapsed.

To terminate the read tests, enter Ctrl/C, or use the kill command to terminate an individual diagnostic or the kill_diags command to terminate all diagnostics..  Use the show_status display to determine the process ID when terminating an individual diagnostic test.


Arguments	Description
[device_name]	One or more device names to be tested.  The default is du*.*,dk*.*, and dr*.* to test all DSSI and SCSI disks and floppy drives that are on line.  These drives may be on the native SCSI bus or connected to an EISA- or PCI-based controller.


Option	Description
[-sec seconds]	Number of seconds to run exercisers.  If you do not enter the number of seconds, the tests will run until d_passes have completed (d_passes default is 1). If you want to test the entire disk, run at least one pass across the disk.  If you do not need to test the entire disk, run the test for 5 or 10 minutes.


exer_read - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example

>>> exer_read

failed to send command to pkc0.1.0.2.0

failed to send Read to dkc100.1.0.2.0

*** Hard Error - Error #5 -

Diagnostic Name	ID	Device	Pass	Test	Hard/Soft
31-JUL 1992 exer_kid 14:54:18	00000175	dkc100.1.0.2	0	0	1    0
Error in read of 0 bytes at location 014DD400 from device dkc100.1.0.2.0

*** End of Error

>>>


Command Reference --- memexer

Troubleshooting
ROM-Based Diagnostics (RBDs)

memexer

Synopsis

Exercises memory by running a specified number of memory tests.

Command

memexer [number]

Note:  Click on the [image] icon above to view examples.


memexer --- Description

The memexer command tests memory by running a specified number of memory exercisers.  The exercisers are run in the background and nothing is displayed unless an error occurs.  Each exerciser tests all available memory

in 2 x the backup cache size blocks for each pass.

Note:  Certain memory errors that are reported by the OCP may not be reported by the ROM-based diagnostics.  Always check the power-up/diagnostic display before running diagnostic commands.

To terminate the memory tests, use the kill command to terminate an individual diagnostic or the kill_diags command to terminate all diagnostics.  Use the show_status display to determine the process ID when terminating an individual diagnostic test.


Number	Description
[number]	Number of memory exercisers to start.  The default is 1. The number of exercisers, as well as the length of time for testing, depends on the context of the testing.  Generally, running three to five exercisers for 15 minutes to 1 hour is sufficient for troubleshooting most memory problems.


memexer - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example with no errors

>>> memexer 4

>>> show_status

ID --------	Program -------	Device -----------	Pass ----	Hard/Soft -----	Bytes Written -------	Bytes Read -------
00000001	idle	system	0	0    0	0	0
000000c7	memtest	memory	3	0    0	635651584	62565154
000000cc	memtest	memory	2	0    0	635651584	62565154
000000d0	memtest	memory	2	0    0	635651584	62565154
000000d1	memtest	memory	3	0    0	635651584	62565154
>>> kill diags

>>>

Example with a memory compare error indicated bad SIMMs

>>> memexer 4

*** Hard Error - Error #44 - Memory compare error

Diagnostic Name	ID	Device	Pass	Test	Hard/Soft	1-JAN-2066
memtest	000000c8	brd0	1	1	1     0	12:00:01
Expected value:	00000004
Received value:	80000001
Failing addr:	800001c

Failing SIMM module    J32

Failing SIMM module    J31

>>> kill diags

>>>


Command Reference --- memexer_mp

Troubleshooting
ROM-Based Diagnostics (RBDs)

memexer_mp

Synopsis

Tests memory in a multiprocessor system.

Command

memexer_mp [number]

Note:  Click on the [image] icon above to view an example.


memexer_mp -- Description

The memexer_mp command tests memory cache coherency in a multiprocessor system by running a specified number of memory exerciser sets.  A set is a memory test that runs on each processor checking alternate longwords.  The exercisers are run in the background and nothing is diplayed unless an error occurs.

Note:  Certain memory errors that are reported by the OCP may not be reported by the ROM-based diagnostics.  Always check the power-up/diagnostic display before running diagnostic commands.

To terminate the memory tests, use the kill command to terminate an individual diagnostic or the kill_diags command to terminate all diagnostics.  Use the show_status display to determine the process ID when terminating an individual diagnostic test.


Number	Description
[number]	Number of memory exerciser sets to start.  The default is 1. The number of exercisers, as well as the length of time for testing, depends on the context of the testing.  Generally, running two or three exercisers for 5 minutes is sufficient.


memexer_mp - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example

>>> memexer_mp 2

>>> show status

ID --------	Program -------	Device -----------	Pass ----	Hard/Soft -----	Bytes Written -------	Bytes Read -------
00000001	idle	system	0	0    0	0	0
00000197	memtest	memory	50	0    0	51380224	51380224
000001a1	memtest	memory	49	0    0	50331648	50331648
000001c2	memtest	memory	23	0    0	23068672	23068672
000001cc	memtest	memory	19	0    0	18874368	18874368
>>> kill diags

>>>


Command Reference --- nettest

Troubleshooting
ROM-Based Diagnostics (RBDs)

nettest

Synopsis

Runs external loopback tests for specified EISA- or PCI-based Ethernet ports.

Command

nettest [-mode port_mode] [-p pass_count] [port]

Note:  Click on the [image] icon above to view examples.


nettest --- Description

The nettest command can be used to run loopback tests for any EISA- or PCI-based Ethernet ports.  It can also be used to test a port on a "live" network.

If the loopback tests are set to run continuously (-p pass_count set to 0), use the kill command (or Ctrl/C) to terminate an individual diagnostic or the kill_diags command to terminate all diagnostics.  Use the show_status display to determine the process ID when terminating an individual diagnostic test.


Port	Description
[port]	Specifies the Ethernet port on which to run the test; for example, ewa0 for the DECchip 21040-AA (TULIP) controller; or era0 for the LANCE chip controller.


Options	Description
[-p pass_count]	Specifies the number of times to run the test.  If 0, then run continuously.  The default value is 1.  This is the number of passes for the diagnostic.  Each pass sends the number of loop messages as set by the environment variable, era*_loop_count.
[-mode port_mode]	Specifies the mode to set the port adapter. ex -- external loopback, the default setting (requires a loopback connector or connection to a live network) in -- internal loopback (loopbacks are conducted within the chip only) Note:  Not all network controllers support internal loopback protocol.


nettest - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example -- Testing an Ethernet Port:

>>> nettest ewa0 -p 0 &

>>> show_status

ID --------	Program -------	Device ----------	Pass ----	Hard/Soft -----	Bytes Written -------	Bytes Read ------
00000001	idle	system	0	0    0	0	0
000000d5	nettest	ewa0.0.0.0.0	13	0    0	308672	308672

>>>kill_diags

>>>

Example -- Testing an Ethernet Port on a Live Network:

1.  Create a list of nodes for which to send MOP loopback packets from port era0.

P00>>> echo : 08-00-2B-E2-56-2A > ndbr/lp_nodes_era0

2. View the list nodes.

P00>>>P00>>>cat ndbr/lp_nodes_era0

3. Start the testing using the -mode nc flag to leave the port in the default state.

P00>>>nettest era0 -mode nc -p 0 &

4. View the status of the test.

P00>>> show_status

ID --------	Program -------	Device ----------	Pass ----	Hard/Soft -----	Bytes Written -------	Bytes Read ------
00000001	idle	system	0	0    0	0	0
000000d5	nettest	era0.0.0.4.0	7	0    0	322068	322000

5. Stop the testing.

P00>>kill_diags

P00>>


Command Reference --- net-s

Troubleshooting
ROM-Based Diagnostics (RBDs)

net -s

Synopsis

The net -s command displays the MOP counters for the specified Ethernet port.

Command

net -s ewa0

Note:  Click on the [image] icon above to view an example.


net-s - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example

>>> net -s ewa0

Status counts:

ti: 72 tps: 0 tu: 47 tjt: 0 unf: 0 ri: 70 ru: 0

rps: 0 rwt: 0 at: 0 fd: 0 lnf: 0 se: 0 tbf: 0

tto: 1 lkf: 1 ato: 1 nc: 71 oc: 0

MOP BLOCK:

 Network list size: 0

MOP COUNTERS:

Time since zeroed (Secs): 42

TX:

 Bytes: 0 Frames: 0

 Deferred: 1 One collision: 0 Multi collisions: 0

TX Failures:

 Excessive collisions: 0 Carrier check: 0 Short circuit: 71

 Open circuit: 0 Long frame: 0 Remote defer: 0

 Collision detect: 71

RX:

 Bytes: 49972 Frames: 70

 Multicast bytes: 0 Multicast frames: 0

RX Failures:

 Block check: 0 Framing error: 0 Long frame: 0

 Unknown destination: 0 Data overrun: 0 No system buffer: 0

 No user buffers: 0

>>>


Command Reference --- net -ic

Troubleshooting
ROM-Based Diagnostics (RBDs)

net -ic

Synopsis

The net -ic command initializes the MOP counters for the specified Ethernet port.

Command

net -ic ewa0

Note:  Click on the [image] icon above to view an example.


net -ic - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example

>>> net -ic ewa0

>>> net -s ewa0

Status counts:

ti: 72 tps: 0 tu: 47 tjt: 0 unf: 0 ri: 70 ru: 0

rps: 0 rwt: 0 at: 0 fd: 0 lnf: 0 se: 0 tbf: 0

tto: 1 lkf: 1 ato: 1 nc: 71 oc: 0

MOP BLOCK:

 Network list size: 0

MOP COUNTERS:

Time since zeroed (Secs): 3

TX:

 Bytes: 0 Frames: 0

 Deferred: 0 One collision: 0 Multi collisions: 0

TX Failures:

 Excessive collisions: 0 Carrier check: 0 Short circuit: 0

 Open circuit: 0 Long frame: 0 Remote defer: 0

 Collision detect: 0

RX:

 Bytes: 0 Frames: 0

 Multicast bytes: 0 Multicast frames: 0

RX Failures:

 Block check: 0 Framing error: 0 Long frame: 0

 Unknown destination: 0 Data overrun: 0 No system buffer: 0

 No user buffers: 0

>>>


Command Reference --- kill and kill_diags

Troubleshooting
ROM-Based Diagnostics (RBDs)

kill and kill_diags

Synopsis

The kill and kill_diags commands terminate diagnostics that are currently executing.

Command

kill_diags

kill [PID . . . ]


kill --- Description

The kill command terminates a specified process.


kill_diags --- Description

The kill_diags command terminates all diagnostics.


PID	Description
[PID. . .]	The process ID of the diagnostic to terminate.  Use the show_status command to determine the process ID.


Command Reference --- show_status

Troubleshooting
ROM-Based Diagnostics (RBDs)

show_status

Synopsis

Reports the status of currently executing test/exercisers.

Command

show_status

Note:  Click on the [image] icon above to view an example.


show_status -- Description

The show_status command reports one line of information per executing diagnostic.  The information includes ID, diagnostic program, device under test, error counts, passes completed, bytes written and read.

Many of the diagnostics run in the background and provide information only if an error occurs.  Use the show_status command to display the progress of diagnostics.

The following command string is useful for periodically displaying diagnostic status information for diagnostics running in the background:

>>> while true;show_status;sleep n;done

Where n is the number of seconds between show_status displays.


show_status - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example

>>>show_status

ID -------	Program -------	Device ------	Pass ----	Hard/Soft -----	Bytes Written -------	Bytes Read -------
00000001	idle	system	0	0    0	0	0
0000006f	memtest	memory	1	0    0	35651584	35651584
00000070	memtest	memory	1	0    0	35651584	35651584
00000077	memtest	memory	1	0    0	37748736	37748736
0000007e	exer_kid	dka0.0.0.1.0	0	0    0	0	69120
0000007f	exer_kid	dka600.6.0.1	0	0    0	0	66560
00000093	exer_kid	dva0.0.0.0.1	0	0    0	0	0
000000d5	nettest	ewa0.0.0.0.0	13	0    0	308672	308672


ID

Process ID.


Program

Program module name.


Device

Device under test.


Pass

Diagnostic pass count.


Hard/Soft

Error count (hard and soft):  Soft errors are not usually fatal; hard errors halt the system or prevent completion of the diagnostics.


Bytes Written

Bytes successfully written by diagnostic.


Bytes Read

Bytes successfully read by diagnostic.


Exit

Do you want to exit this application?


Testing the System (test)

Console Firmware
ROM-Based Diagnostics (RBDs)

Testing the System (test)

Synopsis

Runs firmware diagnostics on the system.

Command

test ([lb])

Note:  If you are running the Windows NT operating system, you need to switch to the SRM console in order to enter the test command.

To display errors for system bus options, enter the show fru command.

Note:  Click on the [image] icon above to view examples.


Testing the system (test)- Example

Console Firmware
ROM-Based Diagnostics (RBDs)

Example 1

The system is tested, and the tests complete successfully.

>>> test

Testing the Memory

Testing the DK* Disks(read only)

dkb600.6.0.2.1 has no media present or is disabled via the RUN/STOP switch

file open failed for dkb600.6.0.2.1

No DR* Disks available for testing

Testing the MK* Tapes(read only)

Testing the DV* Floppy Disks(read only)

file open failed for dva0.0.0.0.1

Testing the VGA(Alphanumeric Mode only)

Testing the EW* Network

>>>

Example 2

The system is tested, and the system reports an error message.  No network server responded to a loopback message.  Ethernet connectivity on this system should be checked.

>>> test

Testing the Memory

Testing the DK* Disks(read only)

No DR* Disks available for testing

Testing the MK* Tapes(read only)

Testing the DV* Floppy Disks(read only)

Testing the VGA(Alphanumeric Mode only)

Testing the EW* Network

*** Error (ewa0), Mop loop message timed out from: 08-00-2b-3b-42-fd

*** List index: 7 received count: 0 expected count 2

>>>


Test Command --Description

The test command runs firmware diagnostics for the entire core system.  The tests are run sequentially and the status of each subsystem test is displayed to the console terminal as the tests progress.  If a particular device is not available to test, a message is displayed.

The test script tests devices in the following order:

1.	Memory tests (one pass)

Note:  Certian memory erros that are reported by the OCP may not be reported by the ROM-based diagnostics.  Always check the power-up/diagnostic display before running diagnostic commands.

2.	Read-only tests:  DK* disks, DR* disks, DU* disks, MK* tapes, DV* floppy

3.	Console loopback tests if lb argument is specified:  COM2 serial port and parallel port

4.	VGA console test -- These tests are only run if the console environment variable is set to "serial."  The VGA console test displays rows of the letter "H".

5.	Network external loopback tests for EWA0 -- This test requires that the Ethernet port be terminated or connected to a live network; otherwise, the test will fail.

Note:  By default, no write tests are performed on disk and tape drives.  Media must be installed to test the floppy drive and tape drives.


Arguments	Description
[lb]	The loopback option includes console loopback tests for the COM2 serial port and the parallel port during the test sequence.


show fru Command

Troubleshooting
ROM-Based Diagnostics (RBDs)

show fru

Synopsis:

Entering show fru displays the serial number and revision level of system bus options and any errors for those options.

Command:

show fru ([target [target ... ])

Example -- for AlphaServer 2100 Systems

Example -- for AlphaServer 2000 Systems


show fru Command

The show fru command reports FRU and error information for the following FRUs based on the serial control bus EEPROM data:

CPU modules

Memory modules

I/O modules

For each of the above FRUs, the slot position, option, part, revision, and serial numbers, as well as any reported symptom-directed diagnostics (SDD) and test-directed diagnostics (TDD) event logs are displayed.  In addition, installed PCI and EISA modules are displayed with their respective slot numbers.


Arguments	Description
[target]	CPU{0,1,2,3}, mem{0,1,2,3}, io.


show fru Command - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example -- for AlphaServer 2100 Systems

>>>show fru

                             Rev                   Events

                                                   Logged

Slot   Option     Part#      Hw  Sw    Serial#     SDD TDD

  0    I/O        B2110-AA   H2  0     KA427P0593  00  00

  2    CPU0       B2020-AA   B2  0     KA426C0457  00  00

  4    MEM0       B2021-BA   A1  0     ML34156292  00  00

Slot   Option                Hose 0, PCI

Slot   Option                Hose 1, EISA

  2    CPQ3011

  4    DEC4220

Slot   Option                Hose 2, PCI

>>>


show fru Command - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example -- for AlphaServer 2000 Systems

>>>show fru

                             Rev                   Events

                                                   Logged

Slot   Option     Part#      Hw  Sw    Serial#     SDD TDD

  0    I/O        B2111-AA   H2  0     KA347DWV06  00  00

  2    CPU0       B2020-AA   B2  9     ML43400028  00  00

  3    MEM0       B2023-BA   A1  0     AY34915430  00  00

Slot   Option                Hose 0, PCI

  6    DECchip     21050-AA

  7    DECchip     21040-AA

  8    DECchip     21050-AA

Slot   Option                Hose 1, EISA

  1    ADP0001

  2    DEC4220

  3    DEC23F0

  5    DEC3002

  6    DEC4250

  7    CPQ3011

Slot   Option                Hose 2, PCI

>>>


show fru

System bus slot number for FRU (slots 0--7 top to bottom)

Slot 0:Standard I/O module (dedicated EISA/PCI card cage slot

Slot 1--3, 5: CPU modules

Slot 4--7: Memory modules


Option

Option name (I/O, CPU#, or MEM#)


Part#

Part number of option


Rev

Revision numbers (hardware and firmware)


Serial#
Serial number


Events Logged

Events logged:

Numbers other than "00" indicate that errors have been logged.

SDD	Number of symptom-directed diagnostic events logged by the serial ROM diagnostics at power up.
TDD	Number of test-directed diagnostic events logged by the firmware diagnostics at power up.


Switching Between Interfaces

Console Firmware
ROM-Based Diagnostics (RBDs)

Switching Between Interfaces

For a few procedures it is necessary to switch from one console interface to the other.

The test command is run from the SRM interface.

The EISA Configuration Utility (ECU) and the RAID Configuration Utility (RCU) are run from the ARC interface.

Switching from SRM to ARC

Switching from ARC to SRM


Switching from SRM to ARC

Two SRM console commands are used to switch to the ARC console:

The arc command loads the ARC firmware and switches to the ARC menu interface.

The ecu command loads the ARC firmware and then boots the ECU diskette.


Switching from ARC to SRM

Switch from the ARC console to the SRM console as follows:

1.  From the Boot menu, select the Supplementary menu.

2.  From the Supplementary menu, select Set up the system.

3.  From the Setup menu, select Switch to OpenVMS or OSF console.  This allows you to select your operating system console.

4.  Select your operating system, then press enter on Setup menu.

5.  When the "Power-cycle the system to implement the change" message is displayed, press the Reset button.  Once the console firmware is loaded and device drivers are initialized, you can boot the operating system.


Error Log Analysis

Troubleshooting
Error Log Analysis

Fault Detection and Reporting

Machine Check/Interrupts

System Bus Transaction Cycle

Error Logging and Event Log Entry Format

Event Record Translation

Interpreting System Faults

Error Field Bit Definition Tables

Sample System Error Report


Fault Detection and Reporting

Troubleshooting
Error Log Analysis

PALcode Exception Handling

Fault Detection and Reporting

Component	Fault Detection/Correction Capability
KN450/KN460 Processor Module
DECchip 21064 and 2106A microprocessor	Contains error detection and correction (EDC) logic for data cycles. There are check bits associated for all data entering and exiting the 21064 microprocessor. A single-bit error on any of the four longwords being read can be corrected (per cycle).
Backup cache (B-cache)	EDC check bits on the data store; and parity on the tag store and control store.
MS450/MS452 Memory Modules
Memory module	EDC logic protects data by detecting and correcting up to 2 bits per DRAM chip per gate array. The four bits of data per DRAM are spread across two gate arrays (one for even longwords, the other for odd longwords).
Standard I/O Module or I/O Backplane
I/O module or backplane	SCSI Controller: SCSI data parity is generated. PCI Ethernet chip (AlphaServer 2100 systems): PCI data parity is generated. EISA to PCI Bridge chip: PCI data parity is generated.
System Bus
System bus	Longword parity on command, address, and data.
T2 System Bus to PCI Bus Bridge (on motherboard MBD)
System bus to PCI bus bridge chip	Longword parity on address and data.


Fault Detection and Reporting

PALcode Exception Handling

Generally, PALcode handles exceptions as follows:

The PALcode determines the cause of the exception.

If possible, it corrects the problem and passes control to the operating system for reporting before returning the system to normal operation.

If error/event logging is required, control is passed through the system control block (SCB) to the appropriate exception handler.


Machine Check/Interrupts; Processor machine check; system machine check; processor-corrected machine check

Troubleshooting
Error Log Analysis

Machine Check/Interrupts

The exceptions that result from hardware system errors are called machine check/interrupts.  They occur when a system error is detected during the processing of a data request.

There are three types of machine check/interrupts related to system events:

Processor Machine Check

System Machine Check

Processor-Corrected Machine Check

Note: The causes of each of the machine check/interrupts are as follows.  The system control block (SCB) vector through which PALcode transfers controls to the operating system is shown in parentheses.


Processor Machine Check

Processor Machine Check (SCB: 670)

Processor machine check errors are fatal system errors and will result in a system crash.

The DECchip 21064 microprocessor detected one or more of the following uncorrectable data errors:

--Uncorrectable B-cache data error

--Uncorrectable memory data error (CU_ERR asserted)

--Uncorrectable data from other CPU's B-cache (CU_ERR asserted)

A B-cache tag or tag control parity error occurred

Hard error was asserted in response to:

--A system bus read data parity error

--System bus timeouts (NOACK error bit asserted) -- The bus responder detected a write data parity or command address parity error and did not acknowledge the bus cycle.


System Machine Check

System Machine Check (SCB: 660)

A system machine check is a system detected error, external to the DECchip 21064 microprocessor and possibly not related to the activities of the CPU.  It occurs when C_ERROR is asserted on the system bus.

Fatal errors:

The standard I/O module detected a system bus data parity error while serving as system bus commander:

--System bus errors (NOACK error bit asserted) -- The bus responder detected a write data parity or command address parity error and did not acknowledge the bus cycle

--Uncorrectable data (CU-ERR asserted) from a responder on the system bus

--PCI-reported address data or timeout errors

Any system bus device detected a command/address parity error

A bus responder detected a write data parity error

Memory or standard I/O system bus gate array detected an internal error (SYNC error)

Nonfatal errors:

A memory module corrected data

Correctable B-cache errors were detected while the B-cache was providing data to the system bus (errors from other CPU)

Duplicate tag store parity errors occurred


Processor-Corrected Machine Check

Processor-Corrected Machine Check (SCB: 630)

Processor-corrected machine checks are caused by B-cache errors that are detected and corrected by the DECchip 21064 microprocessor.  These are nonfatal errors and result in an error log entry.


System Bus Transaction Cycle

Troubleshooting
Error Log Analysis

System Bus Transaction Cycle

In order to interpret error logs for system bus errors, you need a basic understanding of the system bus transaction cycle and the function of the commander, responder, and bystanders.

For any particular bus transaction cycle there is one commander (either CPU or standard I/O) that initiates bus transactions and one responder (memory, CPU, or I/O) that accepts or supplies data in response to a command/address from the system bus commander. A bystander is a system bus node (CPU, standard I/O, or memory) that is not addressed by a current system bus commander.

There are four system bus transaction types: read, write, exchange, and nut.

Read and write transactions consist of a command/address cycle followed by two data cycles.

Exchange transactions are used to replace the cache block when a cache block resource conflict occurs. They consist of a command/address cycle followed by four data cycles: two writes and two reads.

Nut transactions consist of a command/address cycle and two dummy data cycles for which no data is transferred.


Error Log Format

Troubleshooting
Error Log Analysis

Error Logging and Event Log Entry Format

Error Log Format Example

The DEC OSF/1 and OpenVMS error handlers can generate several entry types.  All error entries, with the exception of correctable memory errors, are logged immediately.  Entries can be of variable length based on the number of registers within the entry.

Each entry consists of an operating system header, kernel event frame, several device frames, and an end frame.  Most entries have a PAL-generated logout frame, and may contain other CPU frames(0--3), memory (0--3), and I/O.

By examining the error fields (0--3) of the kernel event frame, you can isolate the failing system FRU for system faults reported by the operating system.  One or more bits are set in the error fields as the result of the system error handling process.  During the error handling process, errors are first handled by the appropriate PALcode error routine and then by the associated operating system error handler.

Interpreting the Error Field


Error Log Format Example

Error Log Format


Event Record Translation

Troubleshooting
Error Log Analysis

Event Record Translation

Error Log Format

OpenVMS AXP Translation Using DECevent

OpenVMS AXP Translation Using ERF

DEC OSF/1 Translation Using uerf

Note:  At product introduction, Microsoft Windows NT does not provide bit-to-text translation of system errors.


OpenVMS AXP Translation Using DECevent

Troubleshooting
Error Log Analysis

OpenVMS Translation Using DECevent

The kernel error log entries are translated from binary to ASCII using the DIAGNOSE command. To invoke the error log utility, enter the DCL command DIAGNOSE.

Format:

DIAGNOSE/TRANSLATE [qualifier] [ ,...] [infile[,...]]

Example:

$ DIAGNOSE/TRANSLATE/SINCE=14-jun-1994

For more information on generating error log reports using DECevent, refer to the DECevent Translation and Reporting Utility for OpenVMS.

DECevent bit-to-text translation highlights all error fields that are set, and other significant state.  These are displayed in capital letters in the third column of the error log.  Otherwise, nothing is shown in the translation column.

Sample DECevent-Generated Error Log


OpenVMS AXP Translation Using ERF

Troubleshooting
Error Log Analysis

OpenVMS Translation Using ERF

The kernel error log entries are translated from binary to ASCII using the ANALYZE/ERROR command. To invoke the error log utility, enter the DCL command ANALYZE/ERROR_LOG.

Format:

ANALYZE_ERROR_LOG [/(qualifier(s)] [(file-spec)] [,...]

Example:

$ ANALYZE/ERROR_LOG/INCLUDE=(CPU,MEMORY)/SINCE=TODAY)

As shown in the above example, the OpenVMS error handler also supports the /INCLUDE qualifier, such that CPU and memory error entries can  be translated selectively.

ERF bit-to-text translation highlights all error fields that are set, and other significant state.  These are displayed in capital letters in the third column of the error log.  Otherwise, nothing is shown in the translation column.


DEC OSF/1 Translation Using uerf

Troubleshooting
Error Log Analysis

DEC OSF/1 Translation Using uerf

Error log information is written to /var/adm/binary.errlog. Use the following command to save the error log information by copying it to another file:

$ cp /var/adm/binary.errlog /tmp/errors_upto_today

To clear the error log file, use the following command:

$ cp /dev/null /var/adm/binary.errlog

To produce a bit-to-text translation of the error log file, use the following command:

$ uerf -f /tmp/errors_upto_today -R

To view all error logs in reverse chronological order, use the following command:

$ uerf -R

For filtering of error logs, see the reference page (man page) for uerf on the system you are currently using:

$ man uerf


Interpreting System Faults

Troubleshooting
Error Log Analysis

Interpreting System Faults

Sample DECevent-Generated Error Log

Use the following steps to determine the failing FRU when a system error is reported via an error log.

Examine the error fields of the kernel event frame.

If a system error has been reported, one or more bits may be set for the error fields, 0--3, and their corresponding bit-to-text definition will be listed.

Using the error field bit definition tables, find the entry that matches the set bit and bit-to-text to determine the most probable source of the fault listed in the third column. The field replaceable units (FRUs) for the core system are listed as follows:

CPUnn -- CPU module (0--3)

MEMnn -- Memory module (0--3)

I/O_0 -- Standard I/O module or I/O backplane

I/O_1 -- Extended I/O module (PCI)

PCInn -- PCI modules (0--2)

MBD -- System motherboard, which contains the T2, system bus to PCI bus bridge chip.

If the table entry lists a note number along with the most probable failing module, refer to that note.  There are five possible notes:

Note 1--Note 5.  Each note provides a synopsis of the problem and additional information to consider for analysis.


Sample System Error Report (DECevent)

Troubleshooting
Error Log Analysis

Sample System Error Report (DECevent)

The example below provides an abbreviated DECevent-generated error log entry for a processor machine check, SCB 670 (1).

Error field 0 (2), has one bit set. The corresponding bit-to-text translation (3) is provided in the third column.

*********************** ENTRY    1 ********************

Logging OS	3. OpenVMS AXP
OS version	X5OJ-FT3
Event sequence number	2.
Timestamp of occurrence	22-JUN-1994 17:46:03
System uptime in seconds	79.
VMS error mask	x00000000
VMS flags	x0000
Host name
AXP HW model	AlphaServer 2100
System type register	x00000009
Unique CPU ID	x00000002
mpnum	x000000FF
mperr	x000000FF
Event validity	-1. Unknown validity code
Event severity	-1. Unknown severity code
Entry type	2.
Major Event class	1. CPU
AXP Device Type	0.
CPU Minor class	1. Machine check (670 entry) (1)
Entry Byte Count	x00000420
frame revision	x0000
scb vector	x0670  processor machine check
severity	x0000  field not valid
cpu id	x0000
error count	x0001
fail code	x0000  field not valid
error field0 (2)	x0000000000000005
	CPU_0 Bus Command No-Ack (3)
	CPU_0 Bus Parity Error
error field1	x0000000000000000
error field2	x0008000000000000
	CPU cycle aborted with HARD ERROR
error field3	x0000000000000000
frame id	x00000002   MC 670 Frame
.
.
.


The example below provides an abbreviated DECevent-generated error log entry for a processor machine check, SCB 670 (1).

Error field 0 (2), has one bit set. The corresponding bit-to-text translation (3) is provided in the third column.


Note 1: System Bus Address Cycle Failures

Troubleshooting
Error Log Analysis

Note 1:  System Bus Address Cycle Failures

Synopsis:

System bus address cycle failures can be reported by the bus commander,

responders, or both:

By commander:  _CA_NOACK--Bus Command Address No-Ack  Commander did not receive an acknowledgment command/address.  Probable causes are:

--A programming error, software fault (addressed nonexistent address)

--A bus buffer failure on the bus commander

By responders:  _CA_PAR---Bus Command/Address Parity Error  Responder detected a parity error during the command/address cycle.  The bus was corrupted by commander module (I/O or CPU), backplane, or responder module (I/O, memory, or CPU).

Analysis:

Note:   All bus nodes check command/address parity during the command/address cycle.

_CA_NOACK errors without respective command/address parity errors are most likely caused by problems in the bus commander, such as programming errors, address generation, and the like.  You should consider the context of the error; for example, a software fault may cause the system to crash each time you run a particular piece of software.

_CA_NOACK errors with all responders reporting command/address parity errors are most likely caused by a bus commander failure or bus failure.

_CA_PAR errors, without respective command/address NOACKs, are most likely the result of a failing buffer within the device reporting the isolated CA_PAR error.


Note 2: System Write Data Cycle Failures

Troubleshooting
Error Log Analysis

Note 2:  System Write-Data Cycle Failures

Synopsis:

System Bus Write Data failures can be reported by the bus commander, responders, or both.

By commander:  _WD_NOACK---Write-Data No-Ack  Commander did not receive an acknowledgment to write-data cycle.  A bus buffer failure on the bus commander is the probable cause.

By responders:  _WD_PAR---Write-Data Parity Error  Responder detected a parity error during the write-data cycle.  The bus was corrupted by commander module (I/O or CPU), backplane, or responder module (I/O, memory, or CPU).

Analysis:

Note:  Only the addressed bus responder checks write-data parity.

_WD_NOACK (write-data NOACK) errors without respective WD_PAR (write-data parity) errors are most likely caused by problems in the bus commander.  However, there is a small probability that the responder could be at fault.  Examine the commander's command trap register to identify the respective responder.

_WD_NOACK errors with the responder reporting _WD_PAR errors could indicate a failure with either device.

_WD_PAR errors without respective _WD_NOACK would require two failures to occur:

1.  Bad data received by responder

2.  A valid response was received when one should not have been sent.

The failing module could be either partner in the transfer.


Note 3: System Read Parity Error

Troubleshooting
Error Log Analysis

Note 3:  System Bus Read Parity Error

Synopsis:

System bus read-data failures are reported only by the bus commander.

By commander:  _RD_PAR error---Read-data parity error.

The bus commander (device reporting _RD_PAR) detected a parity error on data received from the system bus.

Analysis:

Note:  Only the bus commander checks write-data parity on bus reads.

The failure could be caused by either the bus commander or responder. The failing data's address is captured in the commander's bus trap register.

A system bus read parity error can result as a side effect of command/address NOACK.


Note 4: Backup Cache Uncorrectable Error

Troubleshooting
Error Log Analysis

Note 4:  Backup Cache Uncorrectable Error

Synopsis:

Data from the backup cache is either delivered to the DECchip 21064 microprocessor or the system bus interface chip is corrupted.

Analysis:

The failing module is the CPU reporting the failure, except:

If EV_SYN_1F ("CPU reported syndrome 0x1f") or C3_SYN_1F ("C3 reported syndrome 0x1f") bits are set in the error field, known bad data was supplied to the CPU from another source (either memory or the other CPU).

--If C3_MEM_R_ERROR ("CPU error caused by memory") bit is set, examine MEMn_UNCORR ("MEM_n Uncorrectable Error") or MEMn_SYNC_Error ("MEM_n Chip Sync Error") to identify which memory was the source of the error.

--If C3_OCPU_ADD_MATCH ("CPU error caused by other CPU") is set, the other CPU caused the error.

If other error bits associated with the CPU reporting the error are also set, it is likely that the fault is associated with this CPU module.


Note 5: Data Delivered to I/O is Known Bad

Troubleshooting
Error Log Analysis

Note 5:  Data Delivered to I/O is Known Bad

Synopsis:

IO_CB_UNCORR---I/O module received data identified as bad from system bus.

Analysis:

Check to see if the following bits are set for the error field:

MEMn_UNCORR ("MEM_n Uncorrectable Error")

MEMn_SYNC_Error ("MEM_n Chip Sync Error")

CPUn_XXXXXX errors ("CPU_n xxx... error")


This is left in here for future use!

Note 6:  Multi-Event Analysis of Command/Address Parity, Write-Data Parity, or Read-Data Parity Errors

Analysis:

Because  command/address, read-data, and write-data share the backplane and bus transverse, problems with these components can be seen as failures in any of these cycles. It may be possible to identify the failing module by examining several failure entries and drawing a conclusion as to the failing module.

Are the parity errors always associated with the same responder?

If so, the fault is most likely with the responder.

Are the read-parity errors always associated with the same commander?

If so, the fault is most likely with the commander.

Is one module never reporting or associated with an error?

If so, this module could be corrupting the bus.


Error Field Bit Definition Tables

Troubleshooting
Error Log Analysis

Error Field Bit Definition Tables

Quadword 0, error_field_0 ,<63:0>, CPU0-Detected

Quadword 1, CPU1-Detected

Quadword 2, CPU2-Detected

Quadword 3, CPU3-Detected

Quadword 1, error_field_1<63:0> --- I/O as Commander (bus errors that the T2 system bus to EISA bus bridge chip can detect while the I/O module is commander)

Quadword 1, error_field_0 <63:0>, Responder Errors

Miscellaneous Flags

Quadword 3, error_field_3 <63:0>), PCI and EISA Errors


Quadword 0, error_field_0 ,<63:0>, CPU0-Detected

Troubleshooting
Error Log Analysis

Error Field Bit Definitions for Error Log Interpretation

Error Field Bits	Bit-to-Text Definition	Module/Notes
Quadword 0, error_field_0,63:0>, CPU0-Detected

W0-Byte-0, CPU Machine Check Related Errors

<0> C3_0_CA_NOACK	CPU_0 Bus Command No-Ack	CPU_0, Note 1
<1> C3_0_WD_NOACK	CPU_0 Bus Write Data No-Ack	CPU_0, Note 2
<2> C3_0_RD_PAR	CPU_0 Bus Read Data Parity Error	CPU_0, Note 3
<3> EV_0_C_UNCORR	CPU_0 Cache Uncorrectable	CPU_0, Note 4
<4> EV_0_TC_PAR	CPU_0 Cache Tag Control Parity Error	CPU_0
<5> EV_0_T_PAR	CPU_0 Cache Tag Parity Error	CPU_0
<6> C3_0_EV	CPU_0 CPU to System Bus Interface Data Error	CPU_0
<7> C3_0_RETRY_FAILED	CPU_0 Retry Failed	CPU_0
W0-Byte-1, CPU Interrupt and Machine Check

Related Errors

<0> C3_0_C_UNCORR	CPU_0 Cache Uncorrectable (system bus interface detected)	CPU_0, Note 4
<1> C3_0_TC_PAR	CPU_0 Cache Tag Control Parity Error	CPU_0
<2> C3_0_T_PAR	CPU_0 Cache Tag Parity Error	CPU_0
<3> C3_0_C_CORR	CPU_0 Cache Correctable (system bus interface detected)	CPU_0
<4> EV_0_C_CORR	CPU_0 Cache Correctable (CPU detected)	CPU_0
<5> C3_0_SYN_1F	CPU_0 Cache Uncorrectable (0x1f Syndrome)	CPU_0


Quadword 1, CPU1-Detected

Troubleshooting
Error Log Analysis

Error Field Bit Definitions for Error Log Interpretation

Error Field Bits	Bit-to-Text Definition	Module/Notes
Quadword 1, CPU1-Detected

W1-Byte-0, CPU Machine Check Related Errors

<0> C3_1_CA_NOACK	CPU_1 Bus Command No-Ack	CPU_1, Note 1
<1> C3_1_WD_NOACK	CPU_1 Bus Write Data No-Ack	CPU_1, Note 2
<2> C3_1_RD_PAR	CPU_1 Bus Read Data Parity Error	CPU_1, Note 3
<3> EV_1_C_UNCORR	CPU_1 Cache Uncorrectable (CPU detected)	CPU_1, Note 4
<4> EV_1_TC_PAR	CPU_1 Cache Tag Control Parity Error	CPU_1
<5> EV_1_T_PAR	CPU_1 Cache Tag Parity Error	CPU_1
<6> C3_1_EV	CPU_1 CPU to System Bus Interface Data Error	CPU_1
<7> C3_1_RETRY_FAILED	CPU_1 Retry Failed	CPU_1, MBD, or PCI target
W1Byte-1, CPU Interrupt and Machine Check

Related Errors

<0> C3_1_C_UNCORR	CPU_1 Cache Uncorrectable (system bus interface detected)	CPU_1, Note 4
<1> C3_1_TC_PAR	CPU_1 Cache Tag Control Parity Error	CPU_1
<2> C3_1_T_PAR	CPU_1 Cache Tag Parity Error	CPU_1
<3> C3_1_C_CORR	CPU_1 Cache Correctable (system bus interface detected)	CPU_1
<4> EV_1_C_CORR	CPU_1 Cache Correctable (CPU detected)	CPU_1
<5> C3_1_SYN_1F	CPU_1 Cache Uncorrectable (0x1f Syndrome)	CPU_1


Quadword 2, CPU2-Detected

Troubleshooting
Error Log Analysis

Error Field Bit Definitions for Error Log Interpretation

Error Field Bits	Bit-to-Text Definition	Module/Notes
Quadword 2, CPU2-Detected

W2-Byte-0, CPU Machine Check Related Errors

<0> C3_2_CA_NOACK	CPU_2 Bus Command No-Ack	CPU_2, Note 1
<1> C3_2_WD_NOACK	CPU_2 Bus Write Data No-Ack	CPU_2, Note 2
<2> C3_2_RD_PAR	CPU_2 Bus Read Data Parity Error	CPU_2, Note 3
<3> EV_2_C_UNCORR	CPU_2 Cache Uncorrectable (CPU detected)	CPU_2, Note 4
<4> EV_2_TC_PAR	CPU_2 Cache Tag Control Parity Error	CPU_2
<5> EV_2_T_PAR	CPU_2 Cache Tag Parity Error	CPU_2
<6> C3_2_EV	CPU_2 CPU to System Bus Interface Data Error	CPU_2
<7> C3_2_RETRY_FAILED	CPU_2 Retry Failed	CPU_2
W2Byte-1, CPU Interrupt and Machine Check

Related Errors

<0> C3_2_C_UNCORR	CPU_2 Cache Uncorrectable (system bus interface detected)	CPU_2 Note 4
<1> C3_2_TC_PAR	CPU_2 Cache Tag Control Parity Error	CPU_2
<2> C3_2_T_PAR	CPU_2 Cache Tag Parity Error	CPU_2
<3> C3_2_C_CORR	CPU_2 Cache Correctable (system bus interface detected)	CPU_2
<4> EV_2_C_CORR	CPU_2 Cache Correctable (CPU detected)	CPU_2
<5> C3_2_SYN_1F	CPU_2 Cache Uncorrectable (0x1f Syndrome)	CPU_2


Quadword 3, CPU3-Detected

Troubleshooting
Error Log Analysis

Error Field Bit Definitions for Error Log Interpretation

Error Field Bits	Bit-to-Text Definition	Module/Notes
Quadword 3, CPU3-Detected

W3-Byte-0, CPU Machine Check Related Errors

<0> C3_3_CA_NOACK	CPU_3 Bus Command No-Ack	CPU_3, Note 1
<1> C3_3_WD_NOACK	CPU_3 Bus Write Data No-Ack	CPU_3, Note 2
<2> C3_3_RD_PAR	CPU_3 Bus Read Data Parity Error	CPU_3, Note 3
<3> EV_3_C_UNCORR	CPU_3 Cache Uncorrectable (CPU detected)	CPU_3, Note 4
<4>EV_3_TC_PAR	CPU_3 Cache Tag Control Parity Error	CPU_3
<5> EV_3_T_PAR	CPU_3 Cache Tag Parity Error	CPU_3
<6> C3_3_EV	CPU_3 CPU to System Bus Interface Data Error	CPU_3
<7> C3_3_RETRY_FAILED	CPU_3 Retry Failed	CPU_3
W3Byte-1, CPU Interrupt and Machine Check

Related Errors

<0> C3_3_C_UNCORR	CPU_3 Cache Uncorrectable (system bus interface detected)	CPU_3 Note 4
<1> C3_3_TC_PAR	CPU_3 Cache Tag Control Parity Error	CPU_3
<2> C3_3_T_PAR	CPU_3 Cache Tag Parity Error	CPU_3
<3> C3_3_C_CORR	CPU_3 Cache Correctable (system bus interface detected)	CPU_3
<4> EV_3_C_CORR	CPU_3 Cache Correctable (CPU detected)	CPU_3
<5> C3_3_SYN_1F	CPU_3 Cache Uncorrectable (0x1f Syndrome)	CPU_3


Quadword 1, error_field_1<63:0> -- I/O as Commander

Troubleshooting
Error Log Analysis

Error Field Bit Definitions for Error Log Interpretation

Error Field Bits	Bit-to-Text Definition	Module/Notes
Quadword 1, error_field_1<63:0> -- I/O as Commander (bus errors that the T2 system bus to EISA bus bridge chip can detect while the I/O module is commander)

W0-Byte-0, External Cause

<0> IO_CA_NOACK	T2 detected Bus Command/Add No-Ack	MBD or responder, Note 1
<1> IO_WD_NOACK	T2 detected Bus Write Data No-Ack	MBD or responder,  Note 2
<2> IO_RD_PAR	T2 detected Bus Read Parity Error	MBD or target, Note 3
<3> IO_CB_UNCORR	Data received by T2 is corrupted	Target, Note 5
W0Byte-1, Internal Cause

<0> PCI_WR_PAR	T2 - PCI Write Data Parity Error	I/O
<1> PCI_ADD_PAR	T2 - PCI Address Parity Error	I/O
<2> PCI_RD_PAR	T2 - PCI Read Data Parity Error	I/O
<3> PCI_DEV_PAR	T2 - PCI Parity Error	I/O
<4> PCI_SYS_ERR	T2 - PCI System Error	I/O
<5> PCI_TIMEOUT	T2 - PCI Timeout Error	I/O
<6> PCI_NMI	T2 - PCI NMI Asserted	I/O


Quadword 1, error_field_0<63:>Responder Errors

Troubleshooting
Error Log Analysis

Error Field Bit Definitions for Error Log Interpretation

Error Field Bits	Bit-to-Text Definition	Module/Notes
Quadword 1, error_field_0<63:0>, Responder Errors

W0-Byte-0, Command/Address Parity Error Detected

<0> C3_0_CA_PAR	CPU_0 Command/Address Parity Error	CPU_O, Note 1
<1> C3_1_CA_PAR	CPU_1 Command/Address Parity Error	CPU_1, Note 1
<2> MEM0_CA_PAR	MEM_0 Command/Address Parity Error	MEM_0, Note 1
<3> MEM1_C3_2_CA_PAR	MEM_1 or CPU_2 Command/Address Parity Error	MEM_1, CPU2, Note 1
<4> MEM2_CA_PAR	MEM_2 Command/Address Parity Error	MEM_2, Note 1
<5> MEM3_CA_PAR	MEM_3 Command/Address Parity Error	MEM_3, Note 1
<6> IO_CA_PAR	I/O Command/Address Parity Error	I/O_0, Note 1
<7> EXT_IO_C3_3_CA_PAR	External I/O or CPU3 Command/Address Parity Error	I/O_1, CPU3, Note 1
W0-Byte-1, System Bus Interface Write Data Parity Errors

<0> C3_0_WD_PAR	CPU_0 Write Data Parity Error	CPU_O, Note 2
<1> C3_1_WD_PAR	CPU_1 Write Data Parity Error	CPU_1, Note 2
<2> MEM0_WD_PAR	MEM_0 Write Data Parity Error	MEM_0, Note 2
<3> MEM1_C3_2_WD_PAR	MEM_1 or CPU_2 Write Data Parity Error	MEM_1, CPU2, Note 2
<4> MEM2_WD_PAR	MEM_2 Write Data Parity Error	MEM_2, Note 2
<5> MEM3_WD_PAR	MEM_3 Write Data Parity Error	MEM_3
<6> IO_WD_PAR	I/O Write Data Parity Error	I/O_0
<7> EXT_IO_C3_3_WD_PAR	External I/O or CPU3 Write Data Parity Error	I/O_1
W1-Byte-0, Memory Uncorrectable Errors

<0>MEM0_UNCORR	MEM_0 Uncorrectable Error	MEM_0
<1>MEM1_UNCORR	MEM_1 Uncorrectable Error	MEM_1
<2>MEM2_UNCORR	MEM_2 Uncorrectable Error	MEM_2
<3>MEM3_UNCORR	MEM_3 Uncorrectable Error	MEM_3
W1-Byte-1, Memory Correctable Errors

<0>MEM0_CORR	MEM_0 Correctable Error	MEM_0
<1>MEM1_CORR	MEM_1 Correctable Error	MEM_1
<2>MEM2_CORR	MEM_2 Correctable Error	MEM_2
<3>MEM3_CORR	MEM_3 Correctable Error	MEM_3
<4> MEM0_COR_DIS	MEM_0 EDC Correction Disabled	MEM_0
<5> MEM1_COR_DIS	MEM_1 EDC_Correction Disabled	MEM_1
<6> MEM2_COR_DIS	MEM_2 EDC_Correction Disabled	MEM_2
<7> MEM3_COR_DIS	MEM_3 EDC_Correction Disabled	MEM_3
W2-Byte-0, Sync Errors (the two gate arrays are not working together)

<0> MEM0_SYNC_Error	MEM_0 Chip Sync Error	MEM_0
<1> MEM1_SYNC_Error	MEM_1 Chip Sync Error	MEM_1
<2> MEM2_SYNC_Error	MEM_2 Chip Sync Error	MEM_2
<2> MEM3_SYNC_Error	MEM_3 Chip Sync Error	MEM_3
<4> IO_BUSSYNC	I/O Module System Bus Sync Error	MBD


Miscellaneous Flags

Troubleshooting
Error Log Analysis

Error Field Bit Definitions for Error Log Interpretation

Error Field Bits	Bit-to-Text Definition	Module/Notes
Miscellaneous Flags

W3-Byte-0, CPU-Specific (in context of CPU that is reporting the error)

<0>EV_SYN_1F	CPU Reported Syndrome 0x1f	Note 4
<1> Reserved	Reserved SBZ
<2> DT_PAR	Duplicate Tag Store Parity Error	This CPU
<3> EV_HARD_ERROR	CPU Cycle Aborted with HARD ERROR
W3-Byte-1, Event Correlation Flags

<0> C3_MEM_R_ERROR	CPU error caused by memory	Note 4
<1> IO_MEM_R_ERROR	I/O error caused by memory
<2> C3_OCPU_ADD_MATCH	CPU error caused by other CPU	Note 4
<3> MIXED_ERRORS	Mixed errors (no correlation)


Quadword 3, error_field_3<63:0>, PCI and EISA Errors

Troubleshooting
Error Log Analysis

Error Field Bit Definitions for Error Log Interpretation

Error Field Bits	Bit-to-Text Definition	Module/Notes
Quadword 3, error_field_3<63:0>, PCI and EISA Errors

W0-Byte-0, PCI 0 Status Reported Errors

<0> PCI_0_PARR_Detected _as_Master	PCI 0 Data Parr Detected While Bus Master	PCI0 or MBD
<1> PCI_0_SIG_Target_Abort	PCI 0 Aborted with Target-Abort While Target	PCI0 or MBD
<2> PCI_0_REC_Target_Abort	PCI 0 Received Target-Abort While Target	PCI0 or MBD
<3> PCI_0_REC _Master_Abort	PCI 0 Cycle Terminated with Master-Abort While Master	PCI0 or MBD
<4> PCI_0_SIG_System_Error	PCI 0 Signaled System Error	PCI0 or MBD
<5> PCI_0_Detected _Parity_Error	PCI 0 Detected Parity Error	PCI0 or MBD
W0-Byte-1, PCI 1 Status Reported Errors

<0> PCI_1_PARR_Detected _as_Master	PCI 1 Data Parr Detected While Bus Master	PCI1 or MBD
<1> PCI_1_SIG_Target_Abort	PCI 1 Aborted with Target-Abort While Target	PCI1 or MBD
<2> PCI_1_REC_Target_Abort	PCI 1 Received Target-Abort While Master	PCI1 or MBD
<3> PCI_1_REC_ Master_Abort	PCI 1 Cycle Terminated with Master-Abort While Master	PCI1 or MBD
<4> PCI_1_SIG_System_Error	PCI 1 Signaled System Error	PCI1 or MBD
<5> PCI_1_Detected_ Parity_Error	PCI 1 Detected Parity Error	PCI1 or MBD
W1-Byte-0, PCI 2 Status Reported Errors

<0> PCI_2_PARR_Detected _as_Master	PCI 2 Data Parr Detected While Bus Master	PCI2 or MBD
<1> PCI_2_SIG_Target_Abort	PCI 2 Aborted with Target-Abort While Target	PCI2 or MBD
<2> PCI_2_REC_Target_Abort	PCI 2 Received Target-Abort While Master	PCI2 or MBD
<3> PCI_2_REC_ Master_Abort	PCI 2 Cycle Terminated with Master-Abort While Master	PCI2 or MBD
<4> PCI_2_SIG_System_Error	PCI 2 Signaled System Error	PCI2 or MBD
<5> PCI_2_Detected_ Parity_Error	PCI 2 Detected Parity Error	PCI2 or MBD
W2-Byte-0, PCI Ethernet Chip (TULIP) Status Reported Errors

<0> TULIP_PARR_Detected _as_Master	TULIP Parr Detected While Bus Master	I/O_0
<1>TULIP_SIG_Target_Abort	TULIP Aborted with Target-Abort While Target	I/O_0
<2> TULIP_REC_Target_Abort	TULIP Received Target-Abort While Master	I/O_0
<3> TULIP_REC_ Master_Abort	TULIP Cycle Terminated with Master-Abort While Master	I/O_0
<4> TULIP_SIG_System_Error	TULIP Signaled System Error\	I/O_0
<5>TULIP_Detected_ Parity_Error	TULIP Detected Parity Error	I/O_0
W2-Byte-1, SCSI Controller (NCR) Status Reported Errors

<0> NCR_PARR_Detected _as_Master	NCR Data Parr Detected While Bus Master	I/O_0
<1>NCR_SIG_Target_Abort	NCR Aborted with Target-Abort While Target	I/O_0
<2> NCR_REC_Target_Abort	NCR Received Target-Abort While Master	I/O_0
<3> NCR_REC_ Master_Abort	NCR Cycle Terminated with Master-Abort While Master	I/O_0
<4> NCR_SIG_System_Error	NCR Signaled System Error	I/O_0
<5> NCR_Detected_ Parity_Error	NCR Detected Parity Error	I/O_0
W3-Byte-0, PCI-EISA Bridge, PCI Status Reported Errors

<0> PCEB_PARR_Detected _as_Master	PCEB Data Parr Detected While Bus Master	I/O_0
<2>PCEB_SIG_Target_Abort	PCEB Aborted with Target-Abort While Target	I/O_0
<3> PCEB_REC_ Master_Abort	PCEB Cycle Terminated with Master-Abort While Master	I/O_0
<4> PCEB_SIG_System_Error	PCEB Signaled System Error	I/O_0
<5> PCEB_Detected_ Parity_Error	PCEB Detected Parity Error	I/O_0
W3-Byte-1, EISA System Component (ESC) Reported Errors

<0> ESC_PCI_ PERR_Detected	ESC Detected PCI Perr	I/O_0
<1> ESC_EISA_Timeout	ESC Detected EISA Bus Time-Out	I/O_0
<2> ESC_EISA_IOCHK	ESC Detected EISA IOCHK	I/O_0
<3> ESC_FAIL-SAFE	ESC Fail-Safe Timer Expired	I/O_0


Removal and Replacement: Guidelines and Warnings, BA720

Caution: Before removing the system cover:

1.	Perform orderly shutdown of the operating system.
2.	Set the DC power switch on the operator control panel to off.
3.	Unplug AC power cords.

Static electricity can damage integrated circuits.  Always use a grounded wrist strap (29-26246) and grounded work surface when working with internal parts of a computer system.

Unless otherwise specified, you can install a field-replaceable unit (FRU) by reversing the steps shown in the removal procedure.

Continue. . .


FRU List - BA720

Removal and Replacement -
Field-Replaceable Units for AlphaServer 2000 Systems (BA720 Enclosure)

Part #	Description

Cables
17-04083-01	Fan harness (6-pin)
17-04085-01	Floppy drive cable (34-pin)
17-03971-01	OCP module cable (10-pin)
17-00083-09	Power cord
17-03964-01	Power supply current sharing cable (3-pin)
17-03965-01	Power supply signal/misc harness (15-pin)
17-04084-01	Power supply storage harness (12-pin)
17-04087-01	Power supply +5V harness (24-pin)
17-04110-01	Power supply +3.3V harness (20-pin)
17-02784-03	Remote I/O cable (60-pin)
17-04086-01	SCSI (embedded 8-bit) multinode cable (50-pin)
17-03960-02	SCSI RAID internal cable (50-pin)
CPU Modules
B2020-AA	KN450-AA CPU module
B2024-AA	KN460-AA CPU module
Fans
12-23609-09	4.5-Inch Fan
12-36202-03	6.75-Inch Fan
I/O Modules
B2111-AA	I/O backplane
54-23151-01	Remote I/O module
Internal StorageWorks
RZnn - VA	StorageWorks disk drive
54-23343-01	Internal StorageWorks backplane
BA35X-ME	Internal StorageWorks terminator
BA35X-MF	Internal StorageWorks jumper
Memory Modules
ME524-DE (54-21225-BA)	1 x 4MB SIMM
ME644-DE (54-23170-AA)	1 x 16MB SIMM
B2023-BA	32-SIMM carrier module
Other Modules and Components
54-23294-01	System bus motherboard
54-23765-01	OCP module
30-43049-01	OCP LCD display module
30-43049-01	Power supply
12-39309-01	Speaker
12-37004-04	External SCSI terminator
12-41296-01	Internal SCSI terminator
12-36437-03	Key for door
Removable Media
RRDnn -CA	CD-ROM drives
TLZnn -LG	Tape drives
TZKnn -LG	Tape drives
RXnn -AA	Floppy drive


System Bus Motherboard Removal, BA720: Step 1

Removal and Replacement
System Bus Motherboard, AlphaServer 2000 (BA720 Enclosure)

Step 1:  Remove system bus cover and modules

Warning: Memory and CPU modules have parts that operate at high temperatures.  Wait 2 minutes after power is removed before handling these modules.

Note:  Click on the [image] icon above to go to next step.


System Bus Motherboard Removal, BA720: Step 2

Removal and Replacement
System Bus Motherboard, AlphaServer 2000 (BA720 Enclosure)

Step 2:  Detach motherboard cables, remove screws, and disconnect motherboard from I/O backplane.

Caution:  When replacing the system bus motherboard, carefully guide motherboard connectors into the I/O backplane. Install the screws in the order indicated.


Remote I/O Removal, BA720

Remote I/O Module


I/O Backplane Removal, BA720: Steps 1 & 2

Removal and Replacement
I/O Backplane, AlphaServer 2000 (BA720 Enclosure)

Step 1: Record the position of EISA and PCI options.

Step 2: Remove EISA and PCI options.

Note:  Click on the [image] icon above to go to next step.


I/O Backplane Removal, BA720: Step 3

Removal and Replacement
I/O Backplane, AlphaServer 2000 (BA720 Enclosure)

Step 3: Disconnect all I/O backplane cables and remove the I/O backplane.

Note:  Click on the [image] icon above to go to next step.


I/O Backplane Removal, BA720: Step 4

Removal and Replacement
I/O Backplane, AlphaServer 2000 (BA720 Enclosure)

Step 4: Move the NVRAM chip to new backplane.

Move the socketed NVRAM chip (position E47) to the replacement I/O backplane and set jumpers to match previous settings.

J3--Power supply mode jumper	When installed, dual power supplies operate in redundant mode
J5--Programming voltage jumper	Internal use only
J6--Fail-safe jumper	When installed, selects the fail-safe loader firmware


OCP Cable Removal, BA720

OCP Module Cable (10-pin)


SCSI RAID Internal Cable, Removal, BA720

SCSI RAID Internal Cable (50-pin)


Floppy Cable Removal, BA720

Floppy Drive Cable (34-pin)


SCSI (embedded 8-bit) Multinode Cable (50-pin) Removal, BA720

SCSI (embedded 8-bit) Multinode Cable (50-pin)


Power Supply Current Sharing Cable (3-pin) Removal, BA720

Power Supply Current Sharing Cable (3-pin)


Power Supply Signal/Misc Harness (15-pin) Removal, BA720

Power Supply Signal/Misc Harness (15-pin)


Power Supply Storage Harness (12-pin) Removal, BA720

Power Supply Storage Harness (12-pin)


Power Supply +5V Harness (24-pin) Removal, BA720

Power Supply +5V Harness (24-pin)


Power Supply +3.3V Harness (20-pin) Removal, BA720

Power Supply +3.3V Harness (20-pin)


Remote I/O Cable Removal, BA720

Remote I/O Cable (60-pin)


OCP Module Removal, BA720: Step 1

Removal and Replacement
OCP Module, AlphaServer 2000 (BA720 Enclosure)

Note: AlphaServer 2000 systems (BA720 enclosures) have a contrast control for the power-up/diagnostic display on the OCP.  If power-up messages do not display on the OCP, try adjusting the contrast control for your viewing angle.

Step 1:  Remove screw, tip OCP display forward and detatch LCD cable.

Note:  Click on the [image] icon above to go to next step.


OCP Module Removal, BA720: Step 2

Removal and Replacement
OCP Module, AlphaServer 2000 (BA720 Enclosure)

Step 2:  Remove OCP module.

Note:  If replacing the OCP module does not solve the problem, replace the LDC display module.


LCD Module Removal, BA720: Step 1

Removal and Replacement
OCP LCD Display Module, AlphaServer 2000 (BA720 Enclosure)

Note: AlphaServer 2000 systems (BA720 enclosures) have a contrast control for the power-up/diagnostic display on the OCP.  If power-up messages do not display on the OCP, try adjusting the contrast control for your viewing angle.

Replace this module if replacing the OCP module did not solve the problem.

Step 1:  Remove screw, tip OCP display forward and detatch LCD cable.

Note:  Click on the [image] icon above to go to next step.


LCD Module Removal, BA720: Step 2

Removal and Replacement
OCP LCD Display Module, AlphaServer 2000 (BA720 Enclosure)

Step 2:  Detach antistatic lens and remove the LCD display.


CPU Module Removal, BA720: Step 1

Removal and Replacement
CPU Module, AlphaServer 2000 (BA720 Enclosure)

Note: Different CPU types  cannot be used within the same system.  Example: A KN450 CPU module and a KN460 CPU module cannot be used in the same system.

Step 1: Check for errors logged to the CPU.

Verify that errors have been logged through the serial control bus before replacing a CPU module.

1.  Enter the show fru command to check for test-directed diagnostic (TDD) errors logged to the CPU.

In the following example, a test-directed diagnostic (TDD) is logged for CPU0.

Example

P00>>> show fru

                           Rev               Events logged

Slot   Option  Part#      Hw Sw  Serial#     SDD     TDD

  0    IO      B2111-AA   H2 0   KA347DWV06  00      00

  2    CPU0    B2020-AA   B2 9   ML33900048  00      01

  1    CPU1    B2020-AA   B2 9   KA34509090  00      00

  3    MEM0    B2023-AA   A1 0   ML41400005  00      00

  4    MEM1    B2023-AA   A1 0   ML34100008  00      00

.

.

.

P00>>>

2.  Enter the show error cpu0 command to verify that an error, other than test number 00, is currently logged for that CPU.

Example

P00>>> show error cpu0

CPU0 Module EEROM Event Log

Test Directed Errors

Entry: 0  Test Number: 02       Subtest Number: 02

Parameter 1: 00000000,00000010

Parameter 2: ffffffff,ffffffff

Parameter 3: fffffeff,ffffffff

CPU Event Counters

C3_CA_NOACK     0

.

.

.

C3_DT_PAR_E     0

C3_DT_PAR_O     0

B-Cache Correctable Errors

Entry   Syndrome        Offset L        Offset H        Count

No Entries Found

P00>>>

Note:  Click on the [image] icon above to go to next step.


CPU Module Removal, BA720: Step 2

Removal and Replacement
CPU Module, AlphaServer 2000 (BA720 Enclosure)

Step 2: If the CPU has an error logged, other than for test number 00, perform power shutdown and replace the CPU module.

An event log for test  number 00 does not indicate a bad CPU.  Test number 00 indicates that a CPU failover occurred sometime in the past.

Note: All systems must have a CPU module installed in system bus slot 2 (CPU0).

All system bus slots must be populated with a printed circuit board (PCB)

module or a clear plastic module to assure proper airflow over each PCB

module.

Warning: CPU and memory modules have parts that operate at high temperatures.  Wait 2 minutes after power is removed before handling these modules.

System Bus Card Cage

System Bus Configuration (according to number of CPUs)

Note:  Click on the [image] icon above to go to next step.


System Bus Card Cage


System Bus Configuration

System Bus Configurations


CPU Module Removal, BA720: Step 3

Removal and Replacement
CPU Module, AlphaServer 2000 (BA720 Enclosure)

Step 3: Verify that errors are no longer logged for the CPU.

Use the show fru command to verify that the errors are cleared.

Note:  To clear an event logged for test number 00 (CPU failover), use the clear_error cpu# command.

Example

P00>>> show fru

                           Rev               Events logged

Slot   Option  Part#      Hw Sw  Serial#     SDD     TDD

  0    IO      B2111-AA   H2 0   KA347DWV06  00      00

  2    CPU0    B2020-AA   B2 9   ML33900048  00      00

  1    CPU1    B2020-AA   B2 9   KA34509090  00      00

  3    MEM0    B2023-AA   A1 0   ML41400005  00      00

  4    MEM1    B2023-AA   A1 0   ML34100008  00      00

.

.

.

P00>>>


Memory Module Removal, BA720: Step 1

Removal and Replacement
Memory Modules, AlphaServer 2000 (BA720 Enclosure)

SIMM Memory Modules

The position of the failing single-inline memory modules (SIMMs) are

reported by:

The power-up screen and console event log (using the cat el command)

The power-up/diagnostic display on the operator control panel (OCP) when 1 bank of good memory is not detected

The show error console command

ROM-based diagnostics

Certain memory errors that are reported by the OCP may not be reported by the ROM-based diagnostics. Always check the power-up/diagnostic display before running diagnostic commands.

If 1 bank of good memory is not detected at power-up, the firmware console cannot be loaded and the power-up terminates. In this case, the first two data bits of bad memory are displayed in hexadecimal on the power-up/diagnostics display on the operator control panel (OCP).

AlphaServer 2000 system memory configuration rules

Note:  Click on the [image] icon above to go to next step.


AlphaServer 2000 Memory Configuration Rules, BA720

AlphaServer 2000 System (BA720 Enclosure) Memory Configuration Rules

You cannot mix 4-megabyte SIMMs and 16-megabyte SIMMs on an individual module.

Fill your first memory module to capacity before adding memory to the second module.

The second memory module can be filled with 1, 2, or 4 banks of SIMMs. The second memory module cannot be filled with 3 banks of memory.

Maximum memory is 640 megabytes using: One fully-populated module with 4-megabyte SIMMs and one fully populated module with 16-megabyte SIMMs.

The maximum height for SIMMs in the AlphaServer 2000 system is 1.1 inches.


Memory Module Removal, BA720: Step 1

Removal and Replacement
Memory Modules, AlphaServer 2000 (BA720 Enclosure)

Step 1: Check for errors logged against SIMMs.

Verify that errors have been logged through the serial control bus before replacing a CPU module. Use the show fru command to determin if memory errors have been logged.  Use the show error command to determine the type of error (correctible or uncorrectible) and to which SIMMs they are logged against.

1.	Enter the show fru command to check for events logged for memory.

In the following example, a symptom-directed diagnostic (SDD) is logged for MEM1.

Example

P00>>> show fru

                           Rev               Events logged

Slot   Option  Part#      Hw Sw  Serial#     SDD     TDD

  0    IO      B2111-AA   H2 0   ML41100003  00      00

  2    CPU0    B2020-AA   B2 9   ML33900048  00      00

  1    CPU1    B2020-AA   B2 9   KA34509090  00      00

  3    MEM0    B2023-BA   A1 0   ML41400005  00      00

  4    MEM1    B2023-BA   A1 0   ML34100008  01      00

.

.

.

P00>>>

2.	Enter the show error mem1 command to determine the type of error and position of the failing SIMM.

In the following example, an uncorrectible error is logged for the SIMMs at position J31 and J34.

Note:  Correctible errors are indicated by event type 00. If five or more  correctible errors are logged for the same memory carrier, the specified SIMMs should be replaced.

For all unncorrectible errors, indicated by event types 01 and 10, you should replace the failing SIMM(s).

Only two bad memory data bits at a time are captured by the system diagnostics. If more than two SIMMs are bad, you may need to repeat the SIMM isolation and replacement procedures until all bad SIMMs are replaced.

Example

P00>>> show error mem1

MEM1 Module EEROM Event Log

Test Directed Errors

No Entries Found

Symptom Directed Errors

Entry  Fail Address Bits/Syndrome Bank # ASIC # Event Type

  00    00000040   70(J31), 76(34)  0      0        01

P00>>>

Note:  Click on the [image] icon above to go to next step.


Memory Module Removal, BA720: Steps 2 and 3

Removal and Replacement
Memory Modules, AlphaServer 2000 (BA720 Enclosure)

Step 2: Record the position of the failing SIMMs.

Step 3: Remove the memory module that contains the failing SIMMs.

Note: All system bus slots must be populated with a printed circuit board (PCB)

module or a clear plastic module to assure proper airflow over each PCB

module.

Warning: CPU and memory modules have parts that operate at high temperatures.  Wait 2 minutes after power is removed before handling these modules.

System Bus Card Cage

System Bus Configuration (according to number of CPUs)

Note:  Click on the [image] icon above to go to next step.


Memory Module Removal, BA720: Step 4

Removal and Replacement
Memory Modules, AlphaServer 2000 (BA720 Enclosure)

Step 4: Locate the J# on the memory module for the failing SIMM.

Note:  Click on the [image] icon above to go to next step.


Memory Module Removal, BA720: Step 5

Removal and Replacement
Memory Modules, AlphaServer 2000 (BA720 Enclosure)

Step 5: Replace the failing SIMM(s).

Caution:  Do note use any metallic tools or implements including pencils to release SIMM latches.  Static discharge can damage the SIMMs.

Removing SIMMs from Memory Module (Carrier)

Installing SIMMs on Memory Module (Carrier)

Note:  Click on the [image] icon above to go to next step.


SIMM Memory Removal, BA720

Removing SIMMs

Note:  SIMMs can only be removed and installed in successive order. For example; to remove a SIMM at position J35, SIMMs at J20 through J34 must first be removed.


SIMM Memory Installation, BA720

Installing SIMMs

Note:  When installing SIMMs, make sure that the SIMMs are fully seated. The two latches on each SIMM connector should lock around the edges of the SIMMs.


Memory Module Removal, BA720: Step 6

Removal and Replacement
Memory Modules, AlphaServer 2000 (BA720 Enclosure)

Step 6: Clear errors that were logged against the SIMMs.

Use the clear_error command to clear errors logged for the SIMMs that have been replaced.  If you do not clear the memory errors, the new replacement SIMMs will be reported as failing.

In the following example, errors logged against SIMMs on carrier or memory module 1 are cleared.

Example

P00>>> clear_error mem1

P00>>>


Fans, BA720: Step 1

Removal and Replacement
Fans, AlphaServer 2000 (BA720 Enclosure)

Step 1:  Disconnect fan harness at fans and remove fan assembly.

Note:  Click on the [image] icon above to go to next step.


Fans, BA720: Step 2

Removal and Replacement
Fans, AlphaServer 2000 (BA720 Enclosure)

Step 2:  Remove fan.

Caution:  Two types of 6.75 inch fans are used with the BA720 enclosure. One type, shown as Model A in the illustration, manufactured by Sanyo Denki, needs to be oriented with the ground boss to the top.  If this fan is not in the proper orientation, system bus components may overheat.


Fan Harness Removal, BA720

Fan Harness (6-pin)


Internal Storage Works Terminator and Jumper Removal, BA720

Internal StorageWorks Terminator and Jumper


Removal - Internal Storage Works Drive, BA720

StorageWorks Disk Drive

Note:  If the StorageWorks drives are plugged into an SWXCR-xx controller,

you can "hot swap" drives, that is, you can add or replace drives without first shutting down the operating system or powering down the server hardware.

For more information, see StorageWorks RAID Array 200 Subsystem Family Installation and Configuration Guide, EK-SWRA2-IG.

If the StorageWorks drives are not plugged into an SWXCR-xx controller,

you will need to shut down the operating system before swapping a drive. However, you will not need to power down the server before installing the drives.


Floppy Drive Removal, BA740

Floppy Drive


Speaker, BA720

Speaker


Removable Media Devices, Removing, BA720

Removable Media Drives (Tape and CD-ROM)


Power Cord Removal, BA720

Removal and Replacement
Power Cord, AlphaServer 2000 (BA720 Enclosure)

Power Cord


Power Cord Part Numbers, BA720

Removal and Replacement
Power Cord, AlphaServer 2000 (BA720 Enclosure)

Power Cord Numbers

Country	Power Cord BN Number	Digital Number
U.S., Japan, Canada	BN09A-1K	17-00083-09
Australia, New Zealand	BN019H-2E	17-00198-14
Central European (Aus, Bel, Fra, Ger, Fin, Hol, Nor, Swe, Por, Spa)	BN19C-2E	17-00199-21
U.K., Ireland	BN19A-2E	17-00209-15
Switzerland	BN19E-2E	17-00210-13
Denmark	BN19K-2E	17-00310-08
Italy	BN19M-2E	17-00364-18
India, South Africa	BN19S-2E	17-00456-16
Israel	BN18L-2E	17-00457-16


Storageworks Backplane Removal, BA720: Step 1

Removal and Replacement
StorageWorks Backplane, AlphaServer 2000 (BA720 Enclosure)

Step 1:  Remove internal StorageWorks shelf.

Note:  Click on the [image] icon above to go to next step.


Storageworks Backplane Removal, BA720: Step 2

Removal and Replacement
StorageWorks Backplane, AlphaServer 2000 (BA720 Enclosure)

Step 2:  Remove internal StorageWorks backplane.


Power Supply Removal, BA720

Power Supply

Warning:  Hazardous voltages contained within.  Do not service.  Return to factory for service.


Door and Cover Removal, BA720

Removal and Replacement
Removal of Door and Covers, AlphaServer 2000 (BA720 Enclosure)

Step 1:  Remove front door.

Note:  Click on the [image] icon above to go to next step.


Door and Cover Removal, BA720

Removal and Replacement
Removal of Door and Covers, AlphaServer 2000 (BA720 Enclosure)

Step 2:  Remove system cover.

Caution:  Unit will shut down when the system cover is removed.  Access only after performing an orderly shut down and unplugging the AC power cord(s).

Note:  Click on the [image] icon above to go to next step.


Door and Cover Removal, BA720

Removal and Replacement
Removal of Door and Covers, AlphaServer 2000 (BA720 Enclosure)

Step 3:  Remove system bus compartment cover.


Front/Left View, BA720

Removal and Replacement
Front/Left View--FRUs, AlphaServer 2000 (BA720 Enclosure)


Rear/Right View, BA720

Removal and Replacement
Rear/Right View--FRUs, AlphaServer 2000 (BA720 Enclosure)


Installing Storage Devices

Removal and Replacement
Installing Storage Devices

SCSI Buses

A Fast SCSI-2 adapter on the standard I/O module (BA740/BA741 enclosures) or I/O backplane (BA720 enclosures) provides a single-ended SCSI bus for AlphaServer systems.

All tabletop or rackmounted SCSI-2 devices are supported via EISA- or PCI-based SCSI adapters. Use the following rules to determine if a device can be used on your system:

The device must be supported by the operating system. Consult the software product description or hardware vendor.

No more than seven devices can be on any one SCSI-2 controller, and each must have a unique SCSI ID.

The entire SCSI bus length, from terminator to terminator, must not exceed 6 meters for single-ended SCSI-2 at 5 MB/sec, or 3 meters for single-ended SCSI-2 at 10 MB/sec.

--For BA720 pedestal enclosures, the internal cabling for the removable media bus is 2.6 meters; therefore, the maximum lenght for external expansion is 3.4 meters.

--For BA740 pedestal enclosures, the internal cabling for the removable media bus is 2.5 meters; therefore, the maximum length for external expansion is 3.5 meters.

--For BA741 rackmount enclosures, the internal cabling for the removable media and internal disk-drives is 2.0 meters; therefore, the maximum length for external expansion is 4.0 meters.

BA720 Pedestal Systems

Fixed Disk Drives

Removable Media

BA740 Pedestal Systems

Fixed Disk Drives

Removable Media

BA741 Rackmount Systems

Fixed Disk Drives

Removable Media


Internal SCSI Bus, BA740

Installing Storage Devices
BA740 Pedestal Systems

Internal SCSI Bus

The Fast SCSI-2 adapter on the standard I/O module supports the internal

removable-media devices:

Up to three 5.25-in. half-height devices

or

One 5.25-in. full-height device and one 5.25-in. half-height device

This bus can be extended to a StorageWorks shelf or an external expander to support up to seven drives.

The BA740 pedestal supports up to two internal StorageWorks shelves (option number BA35E-AA) that can each support up to eight SCSI disk drives in a dual-bus configuration.

Note:  Extending the SCSI bus into the internal StorageWorks shelf forecloses the option to expand the bus externally.

Installing Removable Media Devices

Configuring the Removable Media Bus


Internal SCSI Bus, BA741

Installing Storage Devices
BA741 Rackmount Systems

Internal SCSI Bus

The Fast SCSI-2 adapter on the standard I/O module supports the internal SCSI drives:

One or two hard disk drives and up to two 5.25-in. half-height devices.

This bus can be extended to a rack-mounted StorageWorks shelf or to an external expander to support up to seven drives.

Installing Removable Media Devices


Installing Removable Media Devices, BA740

Installing Storage Devices
BA740 Pedestal Systems

Installing Removable Media Devices

This illustration shows how to install 5.25-in. half-height or full-height devices in the removable-media compartment.

Use the screws (4 flat-head screws per drive) that are provided with the system.  The screws are in a plastic bag taped to the unused storage bracket.

Be sure that you set the device's node ID so that there are no duplicate node IDs, as each device must have a unique node ID. Nodes 0--6 are available for drives, and node 7 is reserved for the host adapter.  For information on device switch settings, refer to the documentation supplied with the device.


Configuring the Removable Media Bus, BA740

Installing Storage Devices
BA740 Pedestal Systems

Configuring the Removable Media Bus

The removable-media bus can be configured to extend into an internal StorageWorks shelf or to allow expansion from the SCSI connector on the bulkhead at the rear of the enclosure.


External SCSI Expansion, BA740

External Expansion (SCSI)

When the bus is not extended into an internal StorageWorks shelf, the internal SCSI terminator (12-41296-01) is required.

External expansion from the back of the enclosure is available in this configuration. If the bus is not expanded, be sure the external SCSI terminator (12-37004-04) is in place.


Internal SCSI Expansion, BA740

Internal Expansion (SCSI)

When the bus is configured to extend into an internal StorageWorks shelf, the bus must be terminated at the bulkhead connector using the external SCSI terminator (12-37004-04).

External expansion from the back of the enclosure is not allowed in this configuration, as it would violate SCSI bus length rules.


Installing Fixed Disk Drives, BA740

Installing Storage Devices
BA740 Pedestal Systems

Internal SCSI Bus

The Fast SCSI-2 adapter on the standard I/O module supports the internal

removable-media devices:

Up to three 5.25-in. half-height devices

or

One 5.25-in. full-height device and one 5.25-in. half-height device

This bus can be extended to a StorageWorks shelf or an external expander to support up to seven drives.

The BA740 pedestal supports up to two internal StorageWorks shelves (option number BA35E-AA) that can each support up to eight SCSI disk drives in a dual-bus configuration.

Note:  Extending the SCSI bus into the internal StorageWorks shelf forecloses the option to expand the bus externally.

Internal StorageWorks Shelves

Internal StorageWorks Fixed-Disks

Configuring the Removable Media Bus


Installing Fixed-Disk Drives, BA741

Installing Storage Devices
BA741 Rackmount Systems

Internal SCSI Bus

The Fast SCSI-2 adapter on the standard I/O module supports the internal SCSI drives:

One or two hard disk drives and up to two 5.25-in. half-height devices.

This bus can be extended to a rack-mounted StorageWorks shelf or to an external expander to support up to seven drives.

Installing Fixed-Disk Drives


Configuring Internal StorageWorks Shelves, BA740

Installing Storage Devices
BA740 Pedestal Systems

Internal StorageWorks Shelves

Preferred SCSI Cable Routing

The backplane of the internal StorageWorks shelf supplies the drive's SCSI node ID according to the location of the drive within the storage shelf.  Each internal StorageWorks shelf can be configured in one of two ways: single bus or dual bus.


Preferred SCSI Cable Routing, BA740

Preferred SCSI Cable Routing: SWXCR-xx to Internal StorageWorks Shelves (BA740)


Single Bus StorageWorks Configuration, BA740

Single Bus

Single bus -- Up to seven drives, each with a unique node ID. In this configuration, the bottom slot is not used.

The storage shelf configuration is controlled by the position of the terminator (BA35X-MB) and jumper (BA35X-MC).


Dual Bus StorageWorks Configuration, BA740

Dual Bus

Dual bus -- Up to four pair of drives (node IDs 0--3, top to bottom).

The storage shelf configuration is controlled by the position of the terminator (BA35X-MB) and jumper (BA35X-MC).


SCSI Cable Routing

{bm?ma068993.bmp}


Hot Swap, BA740

Hot Swapping Drives

If the StorageWorks drives are plugged into an SWXCR-xx controller, you can "hot swap" drives, that is, you can install or replace drives without first shutting down the operating system or powering down the server hardware.  For more information, see StorageWorks RAID Array 200 Subsystem Family Installation and Configuration Guide, EK-SWRA2-IG.

If the StorageWorks drives are not plugged into an SWXCR-xx controller, you will need to shut down the operating system before swapping a drive.  However, you will not need to power down the server before installing the drive.


Installing Fixed Disk Drives, BA740

Installing Storage Devices
BA720/BA740 Pedestal Systems

Installing StorageWorks Fixed-Disks -- Pedestal (BA720/BA740)

If the StorageWorks drives are plugged into an SWXCR-xx controller, you can "hot swap" drives, that is, you can install or replace drives without first shutting down the operating system or powering down the server hardware.  For more information, see StorageWorks RAID Array 200 Subsystem Family Installation and Configuration GuideEK-SWRA2-IG.

Installation Procedure:

1.	If the StorageWorks drives are plugged into an SWXCR-xx controller, go to step 2.  If your drives are not plugged into an SWXCR-xx controller, shut down the operating system before you go to step 2.

2.	Remove a blank bezel by pressing the two mounting tabs and pull the bezel out of the shelf.

3.	Insert the hard-disk drive into the guide slots and push it in until the tabs lock in place.


Installing Removable Media Devices, BA741

Installing Storage Devices
BA741 Rackmount Systems

Installing Removable Media Devices

This illustration shows how to install 5.25-in. half-height devices in the removable-media compartment.  Use the screws (M3 x 6 mm, flathead) supplied in the accessories kit to mount the drives.

Be sure that you set the device's node ID so that there are no duplicate node IDs, as each device must have a unique node ID. Nodes 0--6 are available for drives, and node 7 is reserved for the host adapter.  For information on device switch settings, refer to the documentation supplied with the device.

Note:  RRDnn and TLZ0n drives use the set of bracket holes marked "A."  The TZK11 drive uses the set of bracket holes marked "B."


Installing Fixed-Disk Drives, BA741

Installing Storage Devices
BA741 Rackmount Systems

Installing Fixed-Disks

To install a hard-disk drive:

1.	Mount four rubber grommets provided in the accessories kit to the drive.

2.	Install drive.

Be sure that you set the device's node ID so that there are no duplicate node IDs, as each device must have a unique node ID.  Nodes 0--6 are available for drives, and node 7 is reserved for the host adapter.  For information

on device switch settings, refer to the documentation supplied with the device.


Installing Mass Storage Devices: Guidelines and Warnings, BA740

Caution: Before opening or removing system panels:

1.	Perform orderly shutdown of the operating system.
2.	Set the DC power switch on the operator control panel to off.
3.	For power supplies with AC On/Off switches, set switches to off.
4.	Unplug AC power cords.

Static electricity can damage integrated circuits.  Always use a grounded wrist strap (29-26246) and grounded work surface when working with internal parts of a computer system.

continue......


Installing Mass Storage Devices: Guidelines and Warnings, BA740

Caution: Before opening or removing system panels:

1.	Perform orderly shutdown of the operating system.
2.	Set the DC power switch on the operator control panel to off.
3.	For power supplies with AC On/Off switches, set switches to off.
4.	Unplug AC power cords.

Static electricity can damage integrated circuits.  Always use a grounded wrist strap (29-26246) and grounded work surface when working with internal parts of a computer system.

continue......


Installing Mass Storage Devices: Guidelines and Warnings, BA741

Warning: Before accessing enclosure compartments:

1.	Perform orderly shutdown of the operating system.
2.	Set the DC power switch on the operator control panel to off.
3.	Remove power by unplugging the AC power cored from each power supply.

The system weighs 45.4 kg (100 lb).  To prevent personal injury and equipment damage, ensure that only one system is extended out of the cabinet at any one time and that the cabinet is stabilized before pulling the system out on its slides.

The adjustable leveling feet should be down and the cabinet's stabilizing bar fully extended before any component is extended out of the cabinet on slides.

Caution:  Static electricity can damage integrated circuits.  Always use a grounded wrist strap (29-26246) and grounded work surface when working with internal parts of a computer system.

continue......


Installing Mass Storage Devices: Guidelines and Warnings, BA741

Warning: Before accessing enclosure compartments:

1.	Perform orderly shutdown of the operating system.
2.	Set the DC power switch on the operator control panel to off.
3.	Remove power by unplugging the AC power cored from each power supply.

The system weighs 45.4 kg (100 lb).  To prevent personal injury and equipment damage, ensure that only one system is extended out of the cabinet at any one time and that the cabinet is stabilized before pulling the system out on its slides.

The adjustable leveling feet should be down and the cabinet's stabilizing bar fully extended before any component is extended out of the cabinet on slides.

Caution:  Static electricity can damage integrated circuits.  Always use a grounded wrist strap (29-26246) and grounded work surface when working with internal parts of a computer system.

continue......


below is BA720 pedesal..


Installing Mass Storage Devices: Guidelines and Warnings, BA720

Caution: Before opening or removing system panels:

1.	Perform orderly shutdown of the operating system.
2.	Set the DC power switch on the operator control panel to off.
3.	For power supplies with AC On/Off switches, set switches to off.
4.	Unplug AC power cords.

Static electricity can damage integrated circuits.  Always use a grounded wrist strap (29-26246) and grounded work surface when working with internal parts of a computer system.

continue......


Installing Mass Storage Devices: Guidelines and Warnings, BA720

Caution: Before opening or removing system panels:

1.	Perform orderly shutdown of the operating system.
2.	Set the DC power switch on the operator control panel to off.
3.	For power supplies with AC On/Off switches, set switches to off.
4.	Unplug AC power cords.

Static electricity can damage integrated circuits.  Always use a grounded wrist strap (29-26246) and grounded work surface when working with internal parts of a computer system.

continue......


Internal SCSI Bus, BA720

Installing Storage Devices
BA720 Pedestal Systems

Internal SCSI Bus

The Fast SCSI-2 adapter on the standard I/O module supports up to two 5.25-inch, internal half-height removable-media devices.

This bus can be extended to a StorageWorks self or an external expander to support up to seven drives.

The BA720 pedestal supports an internal StorageWorks shelf that can support up to eight SCSI disk drives in a dual-bus configuration.

Note:  Extending the SCSI bus into the internal StorageWorks shelf forecloses the option to expand the bus externally.

Internal StorageWorks Shelves

Internal StorageWorks Fixed-Disks

Configuring the Removable Media Bus


Internal SCSI Bus, BA720

Installing Storage Devices
BA720 Pedestal Systems

Internal SCSI Bus

The Fast SCSI-2 adapter on the standard I/O module supports up to two 5.25-inch, internal half-height removable-media devices.

This bus can be extended to a StorageWorks self or an external expander to support up to seven drives.

The BA720 pedestal supports an internal StorageWorks shelf that can support up to eight SCSI disk drives in a dual-bus configuration.

Note:  Extending the SCSI bus into the internal StorageWorks shelf forecloses the option to expand the bus externally.

Installing Removable Media Devices

Configuring the Removable Media Bus


Installing Removable Media Devices, BA720

Installing Storage Devices
BA720 Pedestal Systems

Installing Removable Media Devices

This illustration shows how to install 5.25-in. half-height devices in the removable-media compartment.

Use the screws (4 flat-head screws per drive) that are provided with the system.  The screws are in a plastic bag taped to the unused storage bracket.

Be sure that you set the device's node ID so that there are no duplicate node IDs, as each device must have a unique node ID. Nodes 0--6 are available for drives, and node 7 is reserved for the host adapter.  For information on device switch settings, refer to the documentation supplied with the device.


Configuring the Removable Media Bus, BA720

Installing Storage Devices
BA720 Pedestal Systems

Configuring the Removable Media Bus

The removable-media bus can be configured to extend into an internal StorageWorks shelf or to allow expansion from the SCSI connector on the bulkhead at the rear of the enclosure.


Configuring Internal StorageWorks Shelves, BA720

Installing Storage Devices
BA720 Pedestal Systems

Internal StorageWorks Shelves

Preferred SCSI Cable Routing

The backplane of the internal StorageWorks shelf supplies the drive's SCSI node ID according to the location of the drive within the storage shelf.  Each internal StorageWorks shelf can be configured in one of two ways: single bus or dual bus.


Preferred SCSI Cable Routing, BA720

Preferred SCSI Cable Routing: SWXCR-xx to Internal StorageWorks Shelves (BA720)


Single Bus StorageWorks Configuration, BA720

Single Bus

Single bus -- Up to seven drives, each with a unique node ID. In this configuration, the bottom slot is not used.

The storage shelf configuration is controlled by the position of the terminator (BA35X-ME) and jumper (BA35X-MF).


Dual Bus StorageWorks Configuration, BA720

Dual Bus

Dual bus -- Up to four pair of drives (node IDs 0--3, top to bottom).

The storage shelf configuration is controlled by the position of the terminator (BA35X-ME) and jumper (BA35X-MF).


Exit

Do you want to exit this application?


Notices
Welcome to Fast Track

Notices

Contributors


Welcome

Welcome to Fast Track!

Welcome to the Fast Track to Information!  This set of floppy disks contains complete user information for the Digital 2100 Server.  By navigating Fast Track, you can learn how to operate, troubleshoot, and maintain the 2100 Server.  You will also find information to help you upgrade the system, add options, obtain support, and order additional products and services.


Notices

V2 January 1995

Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.

Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor.

Copyright  Digital Equipment Corporation, 1995.  All Rights Reserved.

The following are trademarks of Digital Equipment Corporation:  Alpha AXP, AXP, DEC, Digital, OpenVMS, StorageWorks, VAX, VT, the AXP logo, and the DIGITAL logo.

The following are third party trademarks:  OSF/1 is a trademark of the Open Software Foundation, Inc.  PostScript is a trademark of Adobe Systems, Inc.  UNIX is a registered trademark of UNIX System Laboratories, a wholly owned subsidiary of Novell, Inc.  Windows and Windows NT are trademarks of Microsoft Corp.  All other trademarks and registered trademarks are the property of their respective holders.

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


Contributors

Program

Jon Mysel - Usability Specialist

Joyce Snow - Program Manager

Hypertext Writing

Kathe Rhoades - Writer/Project Leader

Susan Marsh - Writer

Rich Trubey - Writer

Hypertext Design

Oleg Klimowicz - Illustrator

Andrea Thurber - Graphic Designer

Cheryle West - Interface /Graphic Designer


Navigating Hints

Backtracking

Bookmark Menu Commands

Edit Menu Commands

File Menu Commands

Looking Up Topics in the Index

Printing Topics

Selecting a Hot Spot

Searching for a Word or Phrase

Using Buttons

Using "Folder" Tabs

Using the History Button

Using the Map

Using the Scroll Bar


File Menu Commands

Navigating Hints

File Menu Commands

The File menu contains these commands:

Open

Print Topic

Print Setup

Exit

Open

Displays a dialog box in which you can select and open a topic.

Print Topic

Prints the displayed topic (assuming you have a printer installed and turned on).

Print Setup

Displays a dialog box in which you can change printer settings before printing.

Exit

Closes the application.


Edit Menu Commands

Navigating Hints

Edit Menu Commands

The Edit menu contains these commands:

Copy

Annotate

Copy…

Places a copy of the displayed topic in a dialog box, where you can select text to copy to the Clipboard.

Annotate…

Displays a dialog box in which you can add your own notes to the current topic.


Bookmark Menu Commands

Navigating Hints

Bookmark Menu Commands

The Bookmark menu contains these commands:

Define

More

Define…

Displays a dialog box in which you can add a bookmark to the current topic or delete an existing bookmark.

More…

This command appears only when more than nine bookmarks have been added to the Bookmark menu.  Displays a dialog box in which you can select a bookmark.

Defining and Using a Bookmark


Defining and Using a Bookmark

Navigating Hints

Defining and Using a Bookmark

Just as you can place bookmarks in a printed book to mark specific references, you can place bookmarks at the on-line topics you view frequently.  Once you have placed a bookmark at a topic, you can quickly display that topic from the Bookmark menu.

To place a bookmark:

1	Display the topic at which you want to place a bookmark.

2	From the Bookmark menu, choose Define.

3	The application proposes the topic title as the bookmark name.  If you want to change the name, type a new name in the Bookmark Name box.

4	Choose the OK button.

The bookmark name appears on the Bookmark menu.

To go to a marked topic:

From the Bookmark menu, choose the topic you want to view.

Underlined numbers precede the first nine bookmark titles. You can press the corresponding number key or double-click on the bookmark title to go quickly to a marked topic.

If more than nine bookmarks have been defined, choose More from the Bookmark menu.  Select a bookmark in the Go To box, and then choose the OK button.

To remove a bookmark:

1	From the Bookmark menu, choose Define.

2	Click on the bookmark you want to remove.

3	Choose the Delete button.

4	Choose the OK button.


Backtracking

Navigating Hints

Backtracking

To backtrack through topics in the order you viewed them:

Choose the Back button in the application window.  The Back button takes you back one screen at a time.

If the current topic is the first topic you viewed, the Back button appears dimmed.


Printing Topics

Navigating Hints

Printing Topics

To print an entire topic:

1	Display the topic.

2	From the File menu, choose Print Topic.

To print part of a topic:

1	Display the topic.

2	From the Edit menu, choose Copy.

3	In the Copy dialog box, select the text you want to print, and then choose the OK button.

4	Paste the text into a word-processing application.

5	Use the Print command on the application's File menu to print the text.


Selecting a Hot Spot

Navigating Hints

Selecting a Hot Spot

To select a hot spot:

1	Place the mouse pointer on the hot spot. Normally, hot spots appear in bright green letters on the screen.

The mouse pointer changes to the shape of a pointing finger.

2	Click on the hot spot.

The application jumps to the topic, pops up the window, or carries out the command referenced by the hot spot.


Searching for a Word or Phrase

Navigating Hints

Searching for a Word or Phrase

To search for topics that contain a certain word or phrase:

1	Choose the Search button in the application window.

2	In the Search For box, type the text topic you are searching for.

Tip:  You can choose the Hints button in the Search dialog box for examples of search queries.

3	Under Look At, select Topic Titles Only to search only each topic title, or select All Text to search all the text in each topic.

4	Choose the Search button.

The application lists the title of each topic that contains a search hit in the Topics Found window.


Using Buttons

Navigating Hints

Using Buttons

The following buttons appear at the top of the screen.  The table below lists the buttons and their functions:

Button	Function
	Returns to the first screen of the program.
	Keyword search.  Searches by predetermined keywords.
	Backs up one screen.
	Provides full-text search.  Searches the program's content for the word or phrase you type.
	Lists the screens that you have accessed.
	Contains helpful navigating hints.
	Contains a list of glossary terms
	Browses to next topic.
	Browses to previous topic.


Main Menu

The Main Menu screen displays the buttons for each section of the Digital 2100 Server Fast Track to Information.  You can click on any of these buttons to access information for that topic.


Navigating Hints

History Button

Using the History Button


Navigating Hints

Using the History Button

To jump back to a topic by using the History button:

1	Choose the History button in the application window.

The application lists the last 40 topics you have viewed in the History window.  Topics that are not in the open book are prefixed by an abbreviation of their book name.

2	Double-click on the topic you want to view.

Use the scroll bar to see topics not visible in the list.

3	The History window goes to the background.  You can choose the History button again to bring it to the front, and then choose another topic.  You can also resize or move the History window.

Tip: You may want to arrange the application window and the History window so that they are side by side.

To close the History window:

Double-click on the Control menu box in the History window.


Navigating Hints

Index

Looking Up Topics in the Index


Navigating Hints

Looking Up Topics in the Index

To look up a topic using the index:

1	Choose the Index button in the application window.

2	Type the word you want to search for or select the word from the list.

You can press a key on your keyboard to move quickly to different parts of the list.  For example, type "S" to move to words beginning with the letter "S" and then type "O" to see words beginning with "So."

3	Choose the Show Topics button.

The application lists the topics that are linked to the word you entered or selected.

4	Double-click on the topic you want to view or select the topic and choose the Go To button.

Use the vertical scroll bar to see topics not visible in the list.

Tip:  Double-click on a word to list the related topics automatically.


Navigating Hints

Search Menu

Searching for a Word or Phrase


The hand symbol indicates there is more information in the topic.  Click on the hand symbol pointing right to browse forward in the topic.


The hand symbol indicates there is more information in the topic.  Click on the hand symbol pointing left to browse backward in the topic.


Using "file folder" Tabs

Navigating Hints

Using "Folder" Tabs

Folder tabs allow you to quickly navigate between sections.


Using the Map

Navigating Hints

Using the Map

The map allows you to quickly navigate between sections.


Using the Scroll Bar

Navigating Hints

Using the Scroll Bar

A scroll bar to the right of the screen indicates that there is more information for that topic. Click and drag the scroll bar down to see the additional information.  Click and drag the scroll bar up to backtrack.