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.

AlphaServer 1000 system archiecture


System Architecture

AlphaServer 1000 System Architecture


Power Problems

Troubleshooting
Power Problems

Symptom	Action
System does not power on.	Check the power source and power cord.
	Check that the system s top is properly secured.  A safety interlock switch shuts off power to the system if the top cover is removed.
	If there are two power supplies, make sure both power supplies are plugged in.
	Check the On/Off switch setting on the operator control panel.
	Check that the ambient room temperature is within environmental specifications (10-40ºC, 50-104ºF).
	Check that internal power supply cables are plugged in at both the power supply and system motherboard.
Power supply shuts down after a few seconds (fan failure).	Using a flashlight, look through the front (to the left of the internal StorageWorks shelf) to determine if the fans are spinning at power-up.  A failure of either fan causes the system to shut down after a few seconds.
More information on power-up


Power Supply Cable Connections


Power Supply Configuration Rules

Troubleshooting
Power Problems

Power Supply Configuration Rules

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

Power supply modes of operation:

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

2.	Dual power supply (redundant mode)---Provides redundant power (n + 1).

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.

No jumper needs to be installed to activate redundant mode power.

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.


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.	Interpret the error beep codes at power up for a failure detected 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 a VGA controller other than the standard on-board VGA controller is being used, make sure the CIRRUS VGA option is disabled.   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 the baud rate setting for the 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." For certain situations, power up using the fail-safe loader to load new console firmware from a diskette.


Disabling on-board VGA controller

Troubleshooting
No Access to Console Mode

Using a VGA Controller Other than the Standard, On-Board VGA

When the system is configured to use a PCI- or EISA-based VGA controller instead of the standard on-board VGA (CIRRUS), consider the following:

•	The on-board CIRRUS VGA option must be set to disabled through the ECU.

•	The VGA jumper (J27) on the upper-left corner of the motherboard must then be set to disable (off).

•	The console environment variable should be set to graphics.

•	If there are multiple VGA controllers, the system will direct console output to the first controller that finds it.


Fail-Safe Loader

Troubleshooting
No Access to Console Mode

Fail-Safe Loader

The fail-safe loader (FSL) allows you to attempt to recover 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

A checksum failure or flash ROM header error while the SROM code is trying to load the SRM/ARC console firmware.

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/ARC console is loading at power-up (error beep code 1-1-4), you need to activate the fail-safe loader and reinstall the firmware.

From the FSL program, you can update or load new console firmware.

Activating the Fail-Safe Loader


Activating the Fail-Safe Loader

Troubleshooting
No Access to Console Mode

Activating the Fail-Safe Loader

To activate the FSL:

Install the jumper at bank 7 of the J1 jumper on the CPU daughter board.  The jumper is normally installed in the standard boot setting (bank 0).

Install the console firmware floppy diskette and turn on the system.

Reinstall the console fimrware using the floppy diskette.

When you have finished, power down and return the J1 jumper to the standard boot setting (bank0).


Fail-Safe Loader Jumper

Jumper J1 on the CPU Daughter Board

Bank	Jumper Setting
0	Standard boot setting (default)
1	Mini-console setting: Internal use only
2	SROM CacheTest: backup cache test
3	SROM BCacheTest: backup cache and memory test
4	SROM memTest: memory test with backup and data cache disabled
5	SROM memTestCacheOn: memory test with backup and data cache enabled
6	SROM Bcache Tag Test: backup cache tag test
7	Fail-Safe Loader setting: selects fail-safe loader firmware


Console Event Log

Troubleshooting
Console-Reported Failures

Console Event Log

AlphaServer 1000 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 to view an example.


Console Event Log Example

Troubleshooting
Console-Reported Failures

Console Event Log Example

The following example shows a console event log that contains standard error messages:

(1)	The keyboard is not plugged in or is not working.

>>> cat el

*** keyboard not plugged in...  (1)

ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.

ef.df.ee.f4.ed.ec.eb.ea.e9.e8.e7.e6.port pka0.7.0.6.0 initialized,

scripts are at 4f7faa0

resetting the SCSI bus on pka0.7.0.6.0

port pkb0.7.0.12.0 initialized, scripts are at 4f82be0

resetting the SCSI bus on pkb0.7.0.12.0

e5.e4.e3.e2.e1.e0.

V1.1-1, built on Nov  4 1994 at 16:44:07

device dka400.4.0.6.0 (RRD43) found on pka0.4.0.6.0

>>>


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.	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.
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.

Mass Storage Troubleshooting Table

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


Mass Storage Troubleshooting Table

Troubleshooting
Console-Reported Failures

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. May need to reconfigure internal StorageWorks backplane. [jump]
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.
Missing or loose cables. Drives not properly seated on StorageWorks shelf	Activity LEDs do not come on.  Drive missing from the show config display.	Remove device and inspect cable connections. Reseat drive on StorageWorks shelf.
SCSI bus length exceeded	Drives may disappear intermittently from the show config and show device displays.	A SCSI bus extended to the internal StorageWorks shelf with the backplane configured as a single bus, cannot be extended outside of the enclosure.  A SCSI bus extended to the internal StorageWorks shelf with the backplane configured as a dual bus, can be extended 1 meter outside of the enclosure.  The entire SCSI bus length, from terninator to terminator, must not exceed 5 meters for single-ended SCSI-2 at 5 MB/sec, or 3 meters for single-ended SCSI-2 at 10 MB/sec.
Terminator missing or wrong terminator used	Read/write errors in the console event log; storage adapter port may fail.	Attach appropriate terminators as needed (external SCSI terminator for use with the SWXCR-xx RAID controller, 12-41667-02; external SCSI terminator for native controller, 12-37004 or 12-41667-02). Note: The SCSI terminator jumper (J49) on the motherboard should be set to on to enable the onboard SCSI termination.
Extra terminator	Devices produce errors or device IDs are dropped.	Check that bus is terminated only at beginning and end.  Remove unnecessary terminators. Note: The SCSI terminator jumper (J49) on the motherboard should be set to on to enable the onboard SCSI termination.
SCSI storage controller failure	Problems persist after eliminating the problem sources.	Replace the failing EISA or PCI storage adapter module (or motherboard for the native SCSI controller).


StorageWorks Disk Drive LEDs

StorageWorks Disk Drive LEDs (SCSI)


Power-Up Sequence

Troubleshooting
Console-Reported Failures

Power-Up Sequence

During the AlphaServer 1000 power-up sequence, the power supplies are stabilized and the system is initialized and tested through 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 AlphaServer 1000 enclosure will not power up if the top cover is not securely attached. Removing the top panel will cause the system to shut down.


AC Power-Up Sequence

Troubleshooting
Console-Reported Failures

AC Power-Up Sequence

The following power-up sequence occurs when AC power is applied to the system (systems is plugged in) or when electricity is restored after a power outage:

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

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

Note:  The top cover and side panels must be securely installed.  A safety interlock prevents the system from being powered on with the cover and panels 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 follows:

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.


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, 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 daughter baord 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 motherboard into system memory.

Failures during these tests are indicated by audible error beep codes. Failures of customized SROM tests, set using the J1 jumper on the CPU daughter board, are displayed on the operator control panel.

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 through the power-up screen or console event log.


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 daughter board.  The diagnostics  test the system in the following order:

1.	Test the CPU and backup cache located on the CPU duaghterboard.

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 fails, an audible error beep code sounds..  The power-up tests continue despite these errors.

4.	Configure the memory in the system and test only the first 4 MB of memory. 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 failing bank is mapped out and memory is reconfigured and re-tested. Testing continues until a good memory is found. If good memory is not found, an error beep code (1-3-3) is generated and power-up tests are terminated.

5.	Check the data path to the FEPROMs on the motherboard.

6.	The console program is loaded into memory from the FEPROM on the motherboard.  A checksum test is executed for the console image.  If the checksum test fails, an error beep code (1-1-4) is generated and the power-up tests are terminated.

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


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.

Steps 2--5 may be completed in parallel.

2.	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).

3.	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.

4.	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.

5.	Enter console mode or boot the operating system.  This action is determined by the 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.


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.	Interpret the error beep codes at power-up and check the power-up screen for a failure detected during sef-tests. If the power-up display stops on e6, an EISA or PCI board is causing the system to hang.
Console program reports error: Error beep codes report an error at power-up. Power-up screen includes error messages.	Use the error beep codes and/or console terminal to determine error. 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 table 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 messages 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 test to exercise the storage devices off the EISA controller option. Ethernet adapter -- Run netew or network 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.

Be sure you run the correct version of ECU for the operating system. For Windows NT, use ECU diskette DECpc AXP (AK-PYCJ*-CA); for DEC OSF/1 and OpenVMS, use ECU diskette DECpc AXP (AK-Q2CR*-CA).

The CFG files supplied with the option you want to install may not work on AlphaServer 1000 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.

Note: Some PCI devices do not implement PCI parity, and some hae a parity-generating scheme in which parity is sometimes incorrect or is not compliant with the PCI Specification. In such caes, the device functions properly as long as parity is not checked. The pci_parity environment variable for the SRM console, or the DISABLEPCIPARITY CHECKING for the ARC console, allow you to turn off parity checking so that false PCI parity errors do not result in machine check errors.

When you disable PCI parity, no parity checking is implemented for any PCI device, enven those that produce correct, compliant parity.

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 test to exercise the storage devices off the PCI controller option. Ethernet adapter -- Run netew or network 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 Error Beep Codes

If errors are detected at power-up, audible beep codes are emitted from the system. For example, if the SROM code could not fine any good memory, you would hear a 1-3-3 beep code (one beep, a pause, a burst of three beeps, a pause, and another burst of three beeps).

The beep codes are the primary diagnostic tool for troubleshooting problems when console mode cannot be accessed. Use the table below to interpret error beep codes.

Beep Code	Problem	Corrective Action
1-1-4	The SROM code is unable to load the console code: Flash ROM header areaor checksum error detected.	1. Use the Fail-Safe Loader to load new ARC/SRM console code. 2. If successfully loading new console firmware does not solve the problem, replace the motherboard.
3-3-1	Generic system failure. Possible problem sources include the following motherboard components: navtive SCSI controller (NCR 53C810), remote I/O chip (Intel 87312), or NVRAM chip (position E14).	1. Replace the NVRAM chip (E14) on system motherboard.  2. If replacing the NVRAM chip did not solve the problem, replace the motherboard.
1-2-1	TOY NVRAM failure.	Replace the TOY NVRAM chip (E78) on motherboard.
1-3-3	No usable memory detected.	1. Verify that the memory modules are properly seated and try powering up again. 2. Swap bank 0 memory with known good memory and run SROM memory tests at power-up. 3. If populating bank 0 with known good memory does not solve the problem, replace the CPU daughter board. 4. If replacing the CPU daughter board does not sovle the problem, replace the motherboard.


Isolating Failing SIMMs

Troubleshooting
SROM Memory Power-Up Tests

Isolating Failing SIMMs

To test SIMM memory and report the position of a failing SIMM, set SROM power-up tests by using the J1 jumper of the CPU daughter board. The progress and results of these tests are reported on the LCD display on the operator control panel (OCP).

To thoroughly test memory and data paths, complete the SROM tests in the order listed below.  If a SIMM is reported bad, replace the SIMM and resume testing at bank 4 (Memory Test).

Bank 6, Backup Cache Tag Test

Bank 2, Cache Test

Bank 4, Memory Test

Bank 5, Memory Test, Cache Enabled

Bank 3, Backup Cache Test


SROM Memory Tests, Bank 6

SROM Memory Power-Up Tests, Bank 6

Bank #	Test Description	Test Results
6	Backup Cache Tag Test	Test status displays on OCP: 1.2.3.done. If the tests take longer than a few seconds between each number displayed in the test count, there is a problem with the cache---replace the CPU duaghter board.


SROM Memory Tests, Bank 2

Troubleshooting
SROM Memory Power-Up Tests

SROM Memory Power-Up Tests, Bank 4

Bank #	Test Description	Test Results
4	Memory Test: Tests memory with backup and data cache disabled.	Test status displays on OCP: 12345.done. If an error is detected, the bank and failing SIMM position are displayed.  The following OCP message indicates a failing SIMM at bank 0, SIMM position 2. FAIL B:0 S:2 Test duration: Approximately 10 seconds per 8 megabytes of memory.  Replace the bad SIMM after determining its position. Note: The memory tests do not test the ECC SIMMs.  If the operating system logs five or more single-bit correctible errors, swap the suspected ECC SIMMs with good SIMMs and repeat the memory tests.


SROM Memory Tests, Bank 4

SROM Memory Power-Up Tests, Bank 2

Bank #	Test Description	Test Results
2	Cache Test: Tests backup cache.	Test status displays on OCP: ....done. If the tests take longer than a few seconds to complete, there is a problem with the backup cache---replace the CPU daughter board.


SROM Memory Tests, Bank 5

Troubleshooting
SROM Memory Power-Up Tests

SROM Memory Power-Up Tests, Bank 5

Bank #	Test Description	Test Results
5	Memory Test, Cache Enabled: Tests memory with backup and data cache enabled.	Test status displays on OCP: 12345.done. If an error is detected, the bank and failing SIMM position are displayed.  The following OCP message indicates a failing SIMM at bank 0, SIMM position 2. FAIL B:0 S:2 Test duration: Approximately 2 seconds per 8 megabytes of memory.  Replace the bad SIMM after determining its position. Note: The memory tests do not test the ECC SIMMs.  If the operating system logs five or more single-bit correctible errors, swap the suspected ECC SIMMs with good SIMMs and repeat the memory tests.


SROM Memory Tests, Bank 3

Troubleshooting
SROM Memory Power-Up Tests

SROM Memory Power-Up Tests, Bank 3

Bank #	Test Description	Test Results
3	Backup Cache Test: Test backup cache alternatively with data cache enabled then disabled.	Test status displays on OCP: d 12345.done. D 12345.done. D 12345.done. d 12345.done. If an error is detected, the bank and failing SIMM position are displayed.  The following OCP message indicates a failing SIMM at bank 0, SIMM position 2. FAIL B:0 S:2 Test duration: Approximately 2 seconds per 8 megabytes of memory.  Replace the bad SIMM after determining its position. Note: The memory tests do not test the ECC SIMMs.  If the operating system logs five or more single-bit correctible errors, swap the suspected ECC SIMMs with good SIMMs and repeat the memory tests.


Memory Layout

AlphaServer 1000 Memory Layout


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 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 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 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 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 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 diskette drive.
scsi(0)disk(0)rdisk(0) scsi(0)cdrom(5)fdisk(0)	The scsi() devices are SCSI disk or CD-ROM devices. These examples represent installed SCSI devices. The disk drives are set to SCSI ID 0 and the CD-ROM drive is set to SCSI ID 5. The devices have logical unit numbers of 0.

Note: Click on the [image] icon 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	200 Mhz
Physical Memory	48 MB
Backup Cache Size	2 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	6	0	1000	1	1	SCSI
0	7	0	8086	482	3	EISA bridge
0	7	0	1011	2	23	Ethernet

 Press any key to continue...

Extended Firmware Information:

Version: 4.1-19950117.1606

NVRAM Environment Usage: 32%

   (330 of 1024 bytes)

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
A:	The default floppy drive. The default value is eisa()disk()fdisk().
AUTOLOAD	The default startup action, either YES (boot) or  NO or undefined (remain in ARC firmware).
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().
COUNTDOWN	The default time limit in seconds before the system boots automatically when AUTOLOAD is set to yes. The default value is 10.
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.
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.
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.
KEYBOARDTYPE	The keyboard language. The default is U.S. (English).
TIMEZONE	The time zone in which the system is located. This variable accepts ISO/IEC9945-1 (POSIX) standard values.

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:

Firmware

Memory

PCI Bus

EISA Bus

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


show config

Firmware:

The version numbers for the firmware code, PALcode, SROM chip, and CPU are displayed.


show config

Memory:

The memory size and configuration for each bank of memory is displayed.


show config

PCI Bus:

Slot 6 = SCSI controller on the motherboard, along with storage drives on the bus.

Slot 7 = EISA to PCI bridge chip

Slots 11--13 = Correspond to PCI card cage slots: PCI0, PCI1, and PCI2. For storage controllers, the devices off the controller are also displayed.


show config

EISA Bus:

Slot numbers correspond to PCI card cage slots: PCI0, PCI1, and PCI2. For storage controllers, the devices off the controller are also displayed.


show config - Example

Troubleshooting
Boot Failures

Example

>>> show config

Firmware

SRM Console:    V1.1-1

ARC Console:    3.5-14

PALcode:        VMS PALcode X5.55, OSF PALcode X1.35-53

Serial Rom:      1.1

Processor

DECchip (tm) 21064-2

MEMORY

     48 Meg of System Memory

     Bank 0 = 16 Mbytes(4 MB Per Simm) Starting at 0x00000000

     Bank 1 = 16 Mbytes(4 MB Per Simm) Starting at 0x01000000

     Bank 2 = 16 Mbytes(4 MB Per Simm) Starting at 0x02000000

     Bank 3 = No Memory Detected

PCI Bus

   Bus 00  Slot 06: NCR     810 Scsi Controller

                                   pka0.7.0.6.0          SCSI Bus ID 7

                                   dka400.4.0.6.0        RRD43

   Bus 00  Slot 07: Intel   8275EB PCI to Eisa Bridge

   Bus 00  Slot 13: Compaq 1280/P

EISA Bus

   Slot 2  DEC4220               era0.0.0.2.1           08-00-2B-BC-93-7A

>>>


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 device names.

Driver ID

Adapter ID

Device Unit Number

Bus Node Number

Channel Number

Slot Number

Hose Number

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


show device - Example

Troubleshooting
Boot Failures

Examples

>>> show device

dka400.4.0.6.0             DKA400                        RRD43  2893

dva0.0.0.0.1               DVA0                          RX26

dka100.1.0.1.0             DKA100                        RZ25L  0006

era0.0.0.2.1               ERA0              08-00-2B-3B-42-FD

pka0.7.0.6.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) or reserved on AlphaServer 2000 systems.

Slot 1=SCSI controller on standard I/O or I/O backplane.

Slot 2=EISA to PCI bridge chip

Slots 3-5=Reserved

Slots 6-8=Correspond to PCI card cage slots: PCI0, PCI1, and PCI2.


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. External SCSI terminators used with the SWXCR controller must be of the following type: 12-41667-02.
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. External SCSI terminators used with the SWXCR controller must be of the following type: 12-41667-02.
Image copy of DRA logical drive does not boot (OpenVMS 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 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


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 motherboard, offer many powerful diagnostic utilities, including the ability to examine error logs from the console environment and run system- or device-specific exercisers.

AlphaServer 1000 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 systems).  If you are running a Windows NT system, you will need to switch consoles.

RBDs report errors 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 daughter board

Memory modules

Motherboard

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 runs on OpenVMS, DEC OSF/1, and Windows NT operating systems. 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.

Refer to the DEC Verifier and Exerciser Tool Users Guide (AA-PTTMA-TE) for instructions on running DEC VET.


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
cat el	Displays the console event log.
more el	Displays the console event log one screen at a time.
Extended Testing and Troubleshooting
memory	Runs memory exercises each time the command is entered.  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.
netew	Runs external mop loopback tests for specified EISA- or PCI-based ew* (DECchip 21040, TULIP) Ethernet ports.
network	Runs external mop loopback tests for specified EISA- or PCI-based er* (DEC 4220, LANCE) Ethernet ports.
Loopback Testing
test_lb	Conducts loopback tests for COM2 and the parallel port in addition to quick core system tests.
netew	Runs external mop loopback tests for specified EISA- or PCI-based ew* (DECchip 21040, TULIP) Ethernet ports.
network	Runs external mop loopback tests for specified EISA- or PCI-based er* (DEC 4220, LANCE) 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 --- 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 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)

cat el and more el

Command

The cat el and more el commands display the current contents of the console event log.  Status and error messages (if problems occur) are logged to the consolw event log at power-up, during normal system operation, and while running system tests.

Standard error messages are indicated by asterrisks (***).

When cat el is used, the contents of the console event log scroll by. You can use the Ctrl/S combination to stop the screen from scrolling, Ctrl/Q to resume scrolling.

The more el command allows you to view the console event log one screen at a time.

Synopsis

cat el

or

more el

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


exer_read - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example

The following example shows an an abbreviated console event log tht contains a standard error message:

(1) This error message indicated the keyboard is not plugged in or is not working.

>>> cat el

*** keyboard not plugged in...  (1)

ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.

ef.df.ee.f4.ed.ec.eb.ea.e9.e8.e7.e6.port pka0.7.0.6.0 initialized,

scripts are at 4f7faa0

resetting the SCSI bus on pka0.7.0.6.0

port pkb0.7.0.12.0 initialized, scripts are at 4f82be0

resetting the SCSI bus on pkb0.7.0.12.0

e5.e4.e3.e2.e1.e0.

V1.1-1, built on Nov  4 1994 at 16:44:07

device dka400.4.0.6.0 (RRD43) found on pka0.4.0.6.0

>>>


Command Reference --- memory

Troubleshooting
ROM-Based Diagnostics (RBDs)

memory

Synopsis

Exercises memory by running a memory exerciser each teim the command is entered.

Command

memory

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


memory --- Description

The memory command tests memory by running a memory exerciser each time the command is entered.  The exercisers are run in the background and nothing is displayed unless an error occurs.

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.

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.


memexer - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example with no errors

>>> memory

>>> memory

>>> memory

>>> show_status

ID --------	Program -------	Device -----------	Pass ----	Hard/Soft -----	Bytes Written -------	Bytes Read -------
00000001	idle	system	0	0    0	0	0
0000006b	memtest	memory	1	0    0	53477376	53477376
00000071	memtest	memory	1	0    0	31457280	31457280
00000077	memtest	memory	1	0    0	24117248	24117248
>>> kill diags

>>>

Example with a memory compare error indicating bad SIMMs

>>> memory

>>> memory

>>> memory

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

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

*** End of Error ***

>>> 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 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 --- netew

Troubleshooting
ROM-Based Diagnostics (RBDs)

netew

Synopsis

Runs MOP loopback tests for any EISA- or PCI-based ew* (DECchip 21040, TULIP) Ethernet ports. The command can aslo be used to testa port on a "live" network.

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.

Note: While some results of network tests are reported directly to the console, yu should examine the console event log (using the cat el or more el commands) for complete test results.

Command

netew

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


netew --- Description

When the netew command is entered, the following script is executed:

net -sa ew*0>ndbr/lp_nodes_ew*0

set ew*0_loop_count 2 2>nl

set ew*0_loop_inc 1 2>nl

set ew*0_loop_patt ffffffff 2>nl

set ew*0_loop_size 10 2>nl

set ew*0_lp_msg_node 1 2>nl

net -cm ex ew*0

echo "Testing the network"

nettest ew*0 -sv 3 -mode nc -p 0 -w 1 &

The script builds a list of nodes for which to send MOP loopback packets,

sets certain test environment variables, and tests the Ethernet port

by using the following variation of the nettest exerciser:

nettest ew*0 -sv 3 -mode nc -p 0 -w 1 &


nettest - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example -- Testing an Ethernet Port: (netew)

>>> netew

>>> 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

>>>


Command Reference --- network

Troubleshooting
ROM-Based Diagnostics (RBDs)

network

Synopsis

Runs MOP loopback tests for any EISA- or PCI-based er* (DEC 4220, LANCE) Ethernet ports. The command can aslo be used to testa port on a "live" network.

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.

Note: While some results of network tests are reported directly to the console, yu should examine the console event log (using the cat el or more el commands) for complete test results.

Command

network

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


nettest --- Description

When the nettest command is entered, the following script is executed:

echo "setting up the network test, this will take about 20 seconds"

net -stop er*0

net -sa er*0>ndbr/lp_nodes_er*0

net ic er*0

set er*0_loop_count 2 2>nl

set er*0_loop_inc 1 2>nl

set er*0_loop_patt ffffffff 2>nl

set er*0_loop_size 10 2>nl

set er*0_lp_msg_node 1 2>nl

net -start er*0

echo "Testing the network"

nettest er*0 -sv 3 -mode nc -p 0 -w 1 &

The script builds a list of nodes for which to send MOP loopback packets,

sets certain test environment variables, and tests the Ethernet port

by using the following variation of the nettest exerciser:

nettest er*0 -sv 3 -mode nc -p 0 -w 1 &


network - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example -- Testing an Ethernet Port: (network)

>>> network

>>> 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.0.0	13	0    0	308672	308672

>>>kill_diags

>>>


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 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 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.

Note:  A serial loopback connector (12-27351-01) must be installed on the COM2 serial port for the kill_diags command to successfully terminate system tests.

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 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	era0.0.0.2.1	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

The test command runs firmware diagnostics for the entire core system.  The tests are concurrently in the background. Fatal errors are reported to the console termininal.

The cat el command should be used in conjunction with the test command to examine test/error information reported to the console event log.

Because the tests are run concurrently and indefinitely (until you stop them with the kill_diags 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.  A loopback connector is required for the COM2 (9-pin loopback connector, 12-27351-01) port.

Note:  A serial loopback connector (12-27351-01) must be installed on the COM2 serial port for the kill_diags command to successfully terminate system tests.

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 examine test/error information, examine the console event log using the cat el command.

Note:  Click on the [image] icon 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

Requires diskette and loopback connectors on COM2 and parallel port

type kill_diags to halt testing

type show_status to display testing progress

type cat el to redisplay recent errors

Testing COM2 port

Setting up network test, this will take about 20 seconds

Testing the network

  48 Meg of System Memory

  Bank 0 = 16 Mbytes(4 MB Per Simm) Starting at 0x00000000

  Bank 1 = 16 Mbytes(4 MB Per Simm) Starting at 0x01000000

  Bank 2 = 16 Mbytes(4 MB Per Simm) Starting at 0x02000000

  Bank 3 = No Memory Detected

Testing the memory

Testing parallel port

Testing the SCSI Disks

Non-destructive Test of the Floppy started dka400.4.0.6.0 has no media present or is disabled via the RUN/STOP switch

file open failed for dka400.4.0.6.0

Testing the VGA(Alphanumeric Mode only)

Printer offline

file open failed for para

>>> show_status

ID -------	Program -------	Device ------	Pass ----	Hard/Soft -----	Bytes Written -------	Bytes Read -------
00000001	idle	system	0	0	0	0
0000002d	exer_kid	tta1	0	0	1	0
0000003d	nettest	era0.0.0.2.1	43	0	1376	1376
00000045	memtest	memory	7	0	424673280	424673280
00000052	exer_kid	dka100.1.0.6	0	0	0	2688512
00000053	exer_kid	dka200.2.0.6	0	0	0	922624
>>> kill_diags

>>>

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

Requires diskette and loopback connectors on COM2 and parallel port

type kill_diags to halt testing

type show_status to display testing progress

type cat el to redisplay recent errors

Testing COM2 port

Setting up network test, this will take about 20 seconds

Testing the network

*** Error (era0), 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 script tests devices in the following order:

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

2.	Network external loopback tests for E*A0. This test requires that the Ethernet port be terminated or connected to a live network; otherwise, the test will fail.

3.	Memory tests (one pass).

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

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


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

Note:  A serial loopback connector (12-27351-01) must be installed on the COM2 serial port for the kill_diags command to successfully terminate system tests.


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

Error Logging and Event Log Entry Format

Event Record Translation

Open VMS Translation Using DECevent

Digital UNIX Translation Using DECevent


Fault Detection and Reporting

Troubleshooting
Error Log Analysis

Fault Detection and Reporting

PALcode Exception Handling

Component	Fault Detection/Correction Capability
KN22A Processor Module
DECchip 21064 and 21064A microprocessors	Contains error detection and correction (EDC) logic for data cycles. There are check bits associated with all data entering and exiting the 21064(A) microprocessor. A single-bit error on any of the four longwords being read can be corrected (per cycle).  A double-bit error on any of the four longwords being read can be detected (per cycle).
Backup cache (B-cache)	EDC check bits on the data store; and parity on the tag address store and tag control store.
Memory Subsystem
Memory SIMMs	EDC logic protects data by detecting and correcting data cycle errors.  A single-bit on any of the four longwords can be corrected (per cycle).  A double-bit error on any of the four longwords being read can be detected (per cycle).
System Motherboard
SCSI controller EISA-to-PCI bridge chip	SCSI data parity is generated. PCI data parity is generated.


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; system-corrected mac

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 four types of machine check/interrupts related to system events:

1.	Processor Machine Check (SCB 670)

2.	System Machine Check (SCB 660)

3.	Processor-Corrected Machine Check (SCB 630)

4.	System-Corrected Machine Check (SCB 620)

Note:  The system control block (SCB) vector through which PALcode transfers controls to the operating system is shown in parentheses.

During the error handling process, errors are first handled by the appropriate PALcode error routine and then by the associated operating system error handler.


Processor Machine Check

Processor Machine Check (SCB: 670)

Processor machine check errors are fatal system errors that will result in a system crash.  The error handling code for these errors are common across all platforms using the DECchip 21064 and DECchip 21064A microprocessors.

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

--Uncorrectable B-cache data error

--Uncorrectable memory data error

A B-cache tag or tag control parity error occurred

Hard error was asserted in response to:

--Double-bit Istream ECC error

--Double-bit Dstream ECC error

--System transaction terminated with CACK_HERR

--I-cache parity errors

--D-cache parity errors


System Machine Check

Troubleshooting
Error Log Analysis

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. These errors are specific to AlphaServer 1000 systems.

Fatal errors:

System overtemperature failure

System complete power supply failure

System fan failure

I/O read/write retry timeout

DMA data parity error

I/O data parity error

Slave abort PCI transaction

DEVSEL not asserted

Uncorrectable read error

Invalid page table lookup (scatter gather)

Memory cycle error

B-cache tag address parity error

B-cache tag control parity error

Non-existent memory error

ESC NMI:IOCHK


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 or 21064A microprocessor.  These are nonfatal errors and result in an error log entry.  The error handling code for these errors are common across all platforms using the DECchip 21064 and 21064A microprocessors.

Single-bit Istream ECC error

Single-bit Dstream ECC error

System transaction terminated with CACK_SERR


System-Corrected Machine Check

System-Corrected Machine Check (SCB: 620)

System-corrected machine check errors are AlphaServer 1000-specific correctable errors.  These errors result in the generation of the correctable machine check logout frame:

Correctable read errors

Single power supply failure when operating with redundant power supplies

System overtemperature warning


Error Log Format

Error Logging and Event Log Entry Format

The Digital UNIX 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, several device frames, and an end frame.  Most entries have a PAL-generated logout frame, and may contain frames for CPU, memory, and I/O.


Event Record Translation

Troubleshooting
Error Log Analysis

Event Record Translation

Systems running Digital UNIX and OpenVMS operating systems use the DECevent management utility to translate events into ASCII reports derived from system event entries (bit-to-text translations).

The DECevent utility has the following features relating to the translation of events:

Translating event log entries into readable reports

Selecting input and output sources

Filtering input events

Selecting alternate reports

Translating events as they occur

Maintaining and customizing the user environment with the interactive shell     commands

Error Log Format

OpenVMS AXP Translation Using DECevent

Digital UNIX Translation Using DECevent

Note:  Microsoft Windows NT does not currently provide bit-to-text translation of system errors.


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-1995

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


Digital UNIX Translation Using DECevent

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

Format:

dia [-a -f infile[...]]

Example:

% dia -t s:14-jun-1995:10:00

For more information on generating error log reports using DECevent, refer to the DECevent Translation and Reporting Utility for Digital UNIX User and Reference Guide.


Removal and Replacement: Guidelines and Warnings

Caution: Before removing the top cover and side panels:

1.	Perform an orderly shutdown of the operating system.
2.	Set the On/Off button power 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

Removal and Replacement -
Field-Replaceable Units for AlphaServer 1000 Systems (Pedestal Enclosure)

Part #	Description

Cables
17-03970-02	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-31346-01	Power supply DC cable assembly (signal/misc, 15-pin), (+5V, 24-pin), (+3.3V, 20-pin)
17-03969-01	Power supply storage harness (12-pin)
70-32283-01	Interlock/Server management cable (2-pin)
17-03960-01	Internal StorageWorks jumper cable (50-pin)
17-03962-01	SCSI (J15 StorageWorks shelf to bulkhead connector or bulkhead to multinode) cable (50-pin)
17-03962-02	SCSI (J1 or J14 StorageWorks shelf to bulkhead connector) cable (50-pin)
17-03959-01	SCSI (embedded 8-bit) multinode cable (50-pin)
17-03960-02	SCSI RAID internal cable (50-pin)
CPU Modules
54-23297-01	200 MHz CPU daughter board
54-23297-03	233 MHz CPU daughter board
Fans
70-31350-01	99 mm fan
70-31351-01	120 mm fan
Internal StorageWorks
RZnn - VA	StorageWorks disk drive
54-23365-01	Internal StorageWorks backplane
17-03960-01	Internal StorageWorks jumper cable
Memory Modules
ME524-DE	1 x 4MB SIMM
ME534-DE	1 x 8MB SIMM
ME644-DE	1 x 16MB SIMM
ME654-DE	1 x 32MB SIMM
Other Modules and Components
70-31348-01	Interlock switch
54-23308-01	Motherboard
21-29631-02	NVRAM chip (E14)
54-32423-01	NVRAM TOY clock chip
54-23302-02	OCP module
30-41976-01	Power supply
70-31349-01	Speaker
12-41297-01	External SCSI terminator
12-41667-02	External SCSI terminator (for use with SWXCR controller)
12-27351-01	Serial port loopback connector (9-pin)
12-35619-01	Ethernet twisted-pair loopback connector
H8223	Ethernet BNC T connector
H8225	Ethernet BNC terminator (2)
74-50062-01	Key for door
Removable Media
RRDnn -CA	CD-ROM drives
TLZnn -LG	Tape drives
TZKnn -LG	Tape drives
RXnn -AA	Floppy drive


Motherboard Removal: Step 1, 2

Removal and Replacement
Motherboard, AlphaServer 1000

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

Step 2:  Remove the EISA and PCI options.

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


Motherboard Removal: Step 3

Removal and Replacement
System Bus Motherboard, AlphaServer 1000

Step 3:  Remove CPU daughter board.

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 to go to next step.


Motherboard Removal: Step 4

Removal and Replacement
System Bus Motherboard, AlphaServer 1000

Step 4:  Detach motherboard cables, remove screws and motherboard.

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

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


Motherboard Removal: Step 5

Removal and Replacement
System Bus Motherboard, AlphaServer 1000

Step 5:  Move the NVRAM chip (E14) and NVRAM TOY chip (E78) to the replacement motherboard and set the jumpers to match previous settings.


NVRAM Chip, NVRAM TOY Chip, Removal

Removal and Replacement
NVRAM Chip (E14) and NVRAM TOY Chip (E78), AlphaServer 1000

Motherboard Layout


Interlock Switch Removal

Interlock Switch


OCP Cable Removal

OCP Module Cable (10-pin)


SCSI Cables

SCSI (J15 StorageWorks shelf to bulkhead connector)

SCSI (J1 or J14 StorageWorks shelf to bulkhead connector)

SCSI RAID internal cable


SCSI RAID Internal Cable

Removal and Replacement
SCSI RAID Internal Cable (50-Pin), AlphaServer 1000

SCSI RAID Internal Cable (50-Pin) (Single-Channel)

SCSI RAID Internal Cable (50-Pin) (Dual-Channel)


SCSI RAID Internal Cable, (Single-Channel)

SCSI RAID Internal Cable (50-pin) (Single-Channel)


SCSI RAID Internal Cable, (Dual-Channel)

SCSI RAID Internal Cable (50-pin) (Dual-Channel)


Floppy Cable Removal

Floppy Drive Cable (34-pin)


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


Power Supply Current Sharing Cable (3-pin)


Power Supply DC Cable Assembly

Power Supply DC Cable Assembly (Signal/Misc,15-pin), (+5V, 24-pin), (+3.3V, 20-pin)


Power Supply Storage Harness (12-pin)


Interlock/Server Management Cable (2-pin)


Internal StorageWorks Jumper Cable (50-pin)


SCSI (J15 StorageWorks shelf to bulkhead connector) cable (50-pin)

Removal and Replacement
SCSI RAID Internal Cable (50-Pin), AlphaServer 1000

SCSI Bulkhead Connector to Multinode Cable (50-pin)

SCSI Bulkhead Connector to J15 StorageWorks Shelf Cable (50-pin)


SCSI Bulkhead Connector to Multinode Cable (50-pin)


SCSI Bulkhead Connector to J15 StorageWorks Shelf Cable (50-pin)


OCP Module Removal: Step 1

Removal and Replacement
OCP Module, AlphaServer 1000

Step 1:  Remove front door.

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


OCP Module Removal: Step 2

Removal and Replacement
OCP Module, AlphaServer 1000

Step 2:  Remove front panel.

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


OCP Module Removal: Step 3

Removal and Replacement
OCP Module, AlphaServer 1000

Step 3:  Remove OCP module.


CPU Daughter Board, Removal

CPU Daughter Board

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


Memory Removal

Removal and Replacement
Memory Modules, AlphaServer 1000

SIMM Memory Modules

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

reported by SROM power-up scripts.

AlphaServer 1000 system memory configuration rules

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


AlphaServer 1000 Memory Configuration Rules

AlphaServer 1000 System Memory Configuration Rules

Bank 0 must contain a memory option (5 SIMMs: 0. 1, 2, 3, and 1 ECC SIMM).

The memory option consists of five SIMMs (0, 1, 2, 3, and 1 ECC SIMM for the bank).

All SIMMs within a bank must be of the same capacity.


Memory Module Removal: Steps 1 and 2

Removal and Replacement
Memory Modules, AlphaServer 1000

Step 1: Record the position of the failing SIMMs (from SROM power-up tests).

Step 2: Locate the failing SIMM on the motherboard.

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


Memory Module Removal: Step 3

Removal and Replacement
Memory Modules, AlphaServer 1000

Step 3: Replace the failing SIMM(s).

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

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

Removing SIMMs from Motherboard

Installing SIMMs on Motherboard


SIMM Memory Removal

Removing SIMMs

Note:  SIMMs can only be removed and installed in successive order. For example; to remove a SIMM at bank 0, SIMM 1, SIMMs 0 and 1 for banks 3, 2, and 1 must first be removed.


SIMM Memory Installation

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.


Fans: Step 1

Removal and Replacement
Fans, AlphaServer 1000

Step 1:  Remove the CPU daughter board and any other options blocking access to the fan screws.

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 to go to next step.


Fans: Step 2

Removal and Replacement
Fans, AlphaServer 1000

Step 2:  Disconnect the fan cable from the motherboard and remove fan.


SCSI (J1 or J14 StorageWorks Shelf to bulhead connector) cable (50-pin)

SCSI (J1 or J14 StorageWorks Shelf to Bulkhead Connector) Cable (50-pin)


Removal - Internal Storage Works Drive

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

Floppy Drive


Speaker


CD-ROM Drive, Removing

CD-ROM Drive


Tape Drive, Removing

Tape Drive


Power Cord, Removal

Removal and Replacement
Power Cord, AlphaServer 1000

Power Cord


Power Cord Part Numbers

Removal and Replacement
Power Cord, AlphaServer 1000

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

Internal StorageWorks Backplane


Power Supply, Removal

Power Supply

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


Cover and Panels, Removal

Removal and Replacement
Removal of Top Cover and Side Panels, AlphaServer 1000

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


Front/Left View

Removal and Replacement
Front/Left View--FRUs, AlphaServer 1000


Rear/Right View

Removal and Replacement
Rear/Right View--FRUs, AlphaServer 1000


SCSI Buses
Single- and Multiple-Controller Configurations

SCSI Buses

A Fast SCSI-2 adapter on the motherboard provides a single-ended SCSI bus for AlphaServer 1000 systems.

All tabletop or rackmounted SCSI-2 devices are supported through  EISA- or PCI-based SCSI adapters. Use the SCSI configuration rules to determine whether a device can be used on your system:

The Fast SCSI-2 adapter on the motherboard supports up to two 5.25-inch, internal half-height removable-media devices. This bus can be extended to  the internal StorageWorks shelf or to an external expander to support up to seven drives.

The AlphaServer 1000 deskside wide-tower supports an internal StorageWorks shelf that can support up to seven SCSI disk drives in a dual-bus configuration.

The backplane of the internal StorageWorks shelf supplies the drives SCSI node ID according to the location of the drive within the storage shelf. The internal StorageWorks shelf can be configured in one of two ways:

Single bus --- Up to seven drives, each with a unique node ID.

Dual bus --- Up to seven drives (bus A node Ids 0--3, bus B node Ids 0--2).No more than seven devices can be on any one SCSI-2 controller, and each must have a unique SCSI ID.

The internal StorageWorks shelf configuration is controlled by a StorageWorks jumper cable (17-03960-01).

Single Controller (On-Board) Configurations

 On-board controller configuration with internal StorageWorks backplane configured as a dual bus

 On-board controller configuration with internal StorageWorks backplane configure as a single bus.

Multiple Controller Configurations

 Two controller configuration with internal StorageWorks backplane configured as a dual bus

 Two controller configuration with internal StorageWorks backplane configured as a single bus


SCSI Coonfiguration Rules

SCSI Configuration Rules:

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.


SCSI Buses, Single Controller with Dual Bus StorageWorks

Single Controller Configuration with Dual Bus StorageWorks Shelf


SCSI Buses, Single Controller with Single Bus StorageWorks

Single Controller Configuration with Single Bus StorageWorks Shelf


SCSI Buses, Dual Controllers with Single Bus StorageWorks

Dual Controller Configuration with Single Bus StorageWorks Shelf


SCSI Buses, Dual Controllers with Dual Bus StorageWorks

Dual Controller Configuration with Dual Bus StorageWorks Shelf


Default Jumpers

Default Jumper Settings
Motherboard and CPU Daughter Board

Jumper Settings:

Motherboard jumpers

Supported setting for jumpers J3 and J4 on the CPU daughter board

J1 jumper on the CPU daughter board


CPU Daughter Board, J3 and J4 Jumpers

CPU Daughter Board (J3 and J4) Supported Settings

AlphaServer 1000 4/200 CPU

AlphaServer 1000 4/233 CPU


CPU Daughter Board (200 MHz), J3 and J4 Jumpers

AlphaServer 1000 4/200 CPU

CPU Daughter Board (J3 and J4) Supported Settings

Note: : Thes jumpers affect the clock speed and other critical system settings. The settings shown below are the supported jumper settings for AlphaServer 1000 4/200 systems.

J4 Jumper	J3 Jumper
Off	Off
On
On
Off
On


CPU Daughter Board (233 MHz), J3 and J4 Jumpers

AlphaServer 1000 4/233 CPU

CPU Daughter Board (J3 and J4) Supported Settings

Note: : Thes jumpers affect the clock speed and other critical system settings. The settings shown below are the supported jumper settings for AlphaServer 1000 4/233 systems.

J4 Jumper	J3 Jumper
Off	Off
On
Off
Off
On


Motherboard Jumpers

Default Jumper Settings
Motherboard

Motherboard Jumpers (Default Settings)


Motherboard Jumper J27
Jumper	Name	Description	Default Setting
J27	VGA Enable	When enabled (as shown), the on-board VGA logic is activated.	Enabled for on-board VGA; Disabled if an EISA- or PCI-based VGA option is installed.


Motherboard Jumper J49
Jumper	Name	Description	Default Setting
J49	SCSI Termination	Allows the internal SCSI terminator to be disabled.	Enabled (as shown).


Motherboard Jumper J50
Jumper	Name	Description	Default Setting
J50	Flash ROM VPP Enable	Permits the 12V voltage needed to update the Flash ROMS.	Jumper installed.


Motherboard Jumper J52
Jumper	Name	Description	Default Setting
J52	Temperature Shutdown	Allows the temperature sensor to shut down the system in an over temperature condition.	Currently ships enabled (as shown).


Motherboard Jumper J53
Jumper	Name	Description	Default Setting
J53	Fan Shutdown	Allows the software to shut down the system if a fan fails.	Enabled (as shown).


Motherboard Jumper J55
Jumper	Name	Description	Default Setting
J55	Small Fan	Allows the small fan to be disabled to accommodate rackmount enclosure.	This jumper is not installed on AlphaServer 1000 systems.


Motherboard Jumper J56
Jumper	Name	Description	Default Setting
J56	Fan Fault	When enabled, the hardware forces the system to shut down if a fan fails. When disabled, the firmware generates a machine check; the system crashes and shuts down if a fan fails	Enabled (as shown).


CPU Daughter Board, Jumper J1

Default Jumper Settings
CPU Daughter Board (J1 Jumper)

CPU Daughter Board (Jumper J1)

Bank	Jumper Setting
0	Standard boot setting (default)
1	Mini-console setting: Internal use only
2	SROM CacheTest: backup cache test
3	SROM BCacheTest: backup cache and memory test
4	SROM memTest: memory test with backup and data cache disabled
5	SROM memTestCacheOn: memory test with backup and data cache enabled
6	SROM Bcache Tag Test: backup cache tag test
7	Fail-Safe Loader setting: selects fail-safe loader firmware


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

V1 July 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.

Digital UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd.  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 B 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


Contributors

Phil Barrett - Graphic Designer

Rich Trubey - Writer/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.