Copyright: Copyright ® Digital Equipment Corp. 1996, 1997
Citation: Copyright ® Digital Equipment Corp. 1996, 1997


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?  If so, are the revision numbers compatible for the AlphaServer and the operating system? (Refer to the hardware and operating system release notes).

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 display and ROM-based diagnostics (RBDs).

If the operating system is running, use the operating system environment diagnostic tools, such as the DECevent management utility (to translate and interpret 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 1000A Model 4/xxx system architecture

AlphaServer 1000A Model 5/xxx system architecture


System Architecture

AlphaServer 1000A Model 4/xxx System Architecture


System Architecture

AlphaServer 1000A Model 5/xxx 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 1000A systems support two different modes of operation. In addition, UPS options are available.

Power supply modes of operation:

1.	Single power supply

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.

The H7290-AA power supply kit is used to order a second power supply and current sharing cables.


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.  In addition to beep codes, model 5/xxx systems display error codes on the OCP. 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 variable is 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) is a redundant or backup ROM that allows you to power up without running power-up diagnostics and load new SRM/ARC or SRM/AlphaBIOS and FSL console firmware from the firmware diskette.

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

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 hardware or power failure, or accidental power down during a firmware upgrade occurred.

A configuration error, such as an incorrect environment variable setting or an inappropriate nvram script.

A driver error at power-up.

A checksum error is detected when the SRM console is loading at power-up (corrupted firmware).

From the FSL program, you can update or load new SRM/ARC or SRM/AlphaBIOS console firmware and FSL console firmware.  The fail-safe loader program is available on diskette.

Activating the Fail-Safe Loader


Activating the Fail-Safe Loader

Troubleshooting
No Access to Console Mode

Activating the Fail-Safe Loader

Note:  When installing new console firmware, the flash ROM VPP enable jumper (J50) on the motherboard must be enabled.

To activate the FSL:

1.	Install the jumper at bank 7 of the J1 or J4 jumper on the CPU daughter board.  The jumper is normally installed in the standard boot setting (bank 1 for AlphaServer 1000A Model 4/xxx systems, bank 0 or 1 for Model 5/xxx systems).

2.	Install the console firmware floppy diskette and turn on the system. Two messages are displayed on the operator control panel (OCP) when the FSL program loads the diskette:

OCP Message	Meaning
Floppy Loader	FSL firmware is executing
Starting CPU	FSL firmware found a valid boot block, loaded the program into memory, and is attempting to transfer control to the loaded program.
3.	Reinstall the console firmware from a firmware diskette.

4.	When you have finished, power down and return the J1 or J4 jumper to the standard boot setting (bank1).


Console Event Log

Troubleshooting
Console-Reported Failures

Console Event Log

AlphaServer 1000A 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 more el or 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 two standard error messages.  The first indicates that the mouse is not plugged in or is not working, and the second indicates that SROM tests detected a bad SIMM (bank1, SIMM3).

>>> cat el

ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.ef.df.ee.f4
probing hose 0, PCI
probing PCI-to EISA bridge, bus 1
probing PCI-to-PCI bridge, bus 2
bus 2, slot 0 -- pka -- Qlogic ISP1020
bus 0, slot 11 -- ewa -- DECchip 21040-AA
ed.ec.

** mouse error **
*** Bad memory detected by serial rom
*** SROM failing Bank 1, SIMM3

eb.ea.e9.e8.e7.e6. e5.e4.e3.e2.e1.e0.

X4.6-10166, built on Aug 30 1996 at 09:26:04

.
.
.

>>>


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 DIGITAL UNIX and OpenVMS:      show config      show device      For Windows NT using the ARC console:      Display hardware configuration      Set default variables     For Windows NT using the AlphaBIOS console, use the AlphaBIOS menus to examine and set the system configuration. Check the system configuration for correct environment variable settings.  For DIGITAL UNIX and OpenVMS:     auto_action     bootdef_dev     boot_osflags     os_type     bus_probe_algorithm For problems booting over a network, check the ew*0_protocols or er*0_protocols environment variable settings: Systems booting from a DIGITAL UNIX 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 DIGITAL UNIX  server should be set to bootp; systems booting from an OpenVMS server should be set to mop. For systems running DIGITAL UNIX and OpenVMS, make sure that the bus_probe_algorithm environment variable is set to new. Run device tests to check that boot device is operating.


Displaying System Configuration: AlphaBIOS

Troubleshooting
Boot Failures

AlphaBIOS Menu Options for Windows NT

The following AlphaBIOS menu options are used for verifying system configuration on Windows NT systems:

Display System Configuration menu---Provides information about the systems installed processor, memory, attached devices, and option boards.

From the AlphaBIOS Setup screen, select Display System Configuration..., then the category for the requisite information.

CMOS Setup menu--CMOS Setup is used to configure several system parameters.  CMOS Setup has two modes: Standard CMOS Setup is used to configure basic system parameters; Advanced CMOS Setup is used for system-specific parameters and password protection.


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 Alpha System Dump Analyzer Utility Manual (AA-PV6UB-TE) for information on how to interpret OpenVMS crash dump files. Refer to the Guide to Kernel Debugging (AA-PS2TD-TE) for information on using the DIGITAL UNIX 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-PTTMD-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 RAID Array Subsystem.


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
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, (set pk*0_host_id) for systems running DIGITAL UNIX or OpenVMS (SRM console). For systems running Windows NT (ARC console), choose Set default configuration in the Setup Menu.
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 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.
Terminator missing or wrong terminator used	Read/write errors in the console event log; storage adapter port may fail. If the bulkhead terminator for the removable-media bus is missing, removable-media devices may not be recognized by the system and may be missing from the show config and show device displays.	Attach appropriate terminators as needed (external SCSI terminator for use with the RAID Array 200 Subsystem, 12-41667-04 (68-pin), 17-04166-02 (50-pin); external SCSI terminator for removable bus, 12-41667-05). Note: The SCSI terminator jumper (J51) 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 (J51) 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 1000A 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 1000A 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 (system 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 board 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, the console event log, and for Model 5/xxx systems, OCP error codes.

Failures of customized SROM tests for Model 4/xxx systems 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 daughter board.

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 fails or EISA bridge fails, an audible error beep code (3-3-1) sounds.  The power-up tests continue despite these errors.

4.	Test the PCI-to-PCI bus bridge.  If the bridge fails, an error beep code (3-3-2) sounds.

5.	Test the native SCSI controller. If the controller fails, an error beep code (3-1-2) sounds.

6.	Configure the memory in the system and test only the first 16 MB of memory.

If the memory test fails, the failing bank is mapped out and memory is reconfigured and re-tested.  Testing continues until good memory is found.  If good memory is not found, an error beep code (1-3-3) is generated and the power-up tests are terminated.

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

8.	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 (Model 4/xxx systems) or AlphaBIOS (Model 5/xxx systems) console is loaded into memory, and control is passed to the ARC or AlphaBIOS 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 self-tests.  In addition, model 5/xxx systems display error codes on the OCP.
Console program reports error: Error beep codes report an error at power-up. Power-up screen includes error messages. Model 5/xxx systems display error codes on the OCP.	Use the error beep codes and/or console terminal to determine error. In addition, model 5/xxx systems display error codes on the OCP.  Examine the console event log (enter the more 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. Note:  The external SCSI terminator must be installed on the SCSI port at the rear of the enclosure.  Without the termination, some SCSI drives will be missing from the show config display.   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 the ROM-based diagnostic (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 DIGITAL UNIX 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 1000A 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.

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 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 have a parity-generating scheme in which parity is sometimes incorrect or is not compliant with the PCI Specification. In such cases, the device functions properly as long as parity is not checked. The pci_parity environment variable for the SRM console, or the ENABLEPCIPARITY 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, even those devices 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.
Additional PCI Troubleshooting Tips


PCI Troubleshooting Tips

Additional PCI Troubleshooting Tips

Some PCI options are restricted to the  primary PCI bus, slots 11, 12, and 13.  Refer to the following documents for restrictions on specific PCI options.

AlphaServer 1000A READ THIS FIRST---shipped with the system.

AlphaServer 1000A Supported Options List---The options list is available from the Internet at the following locations:

ftp://ftp.digital.com/pub/Digital/Alpha/systems/

http://www.digital.com/info/alphaserver/


Interpreting error beep codes

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

Be sure to check that the CPU daughter board is properly seated in its connector if errors are reported.

Note:  A single beep is emitted for model 5/xxx systems when the SROM code has successfully  completed.  The console firmware then continues with its power-up tests.

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-2	ROM data path error detected while loading the console code.	1. Use the Fail-Safe Loader to load new console code. 2. If successfully loading new console firmware does not solve the problem, replace the motherboard.
1-1-4	The SROM code is unable to load the console code: Flash ROM header area or checksum error detected.	1. Use the Fail-Safe Loader to load new console code. 2. If successfully loading new console firmware does not solve the problem, replace the motherboard.
1-2-1	TOY NVRAM failure.	Replace the TOY NVRAM chip (E78) on motherboard.
1-2-4	Backup cache error.	Replace the CPU daughter board.  Model 5/xxx systems can be operated with the Bcache disabled until a replacement CPU daughter baord is available.  Bank 4 fo the J1 or J4 jumper on the CPU daughter board is used to disable the Bcache.
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 solve the problem, replace the motherboard.
3-1-2	J1 jumper on the CPU daughter board set incorrectly or failure of native SCSI controller (Qlogic 1020A).	1. Check that the J1 jumper on the CPU daughter board is set at bank 1 for AlphaServer 1000A systems, as opposed to bank 0, reserved for AlphaServer 1000 systems.   Note that model 5/xxx systems can use either standard boot setting, bank 0 or 1, regardless of system, and that model 5/300 systems use jumper designator J4 rather than J1. 2. If the J1 jumper setting is not the problem, replace the motherboard. .
3-3-1	Generic system failure. Possible problem sources include the TOY NVRAM chip (Dallas DS1287A) or PCI-to-EISA bridge chipset (Intel 82375EB).	1. Replace the TOY NVRAM chip (E78) on system motherboard.  2. If replacing the TOY NVRAM chip did not solve the problem, replace the motherboard.
3-3-2	J1 jumper on the CPU daughter board set incorrectly or failure of the PCI-to-PCI bridge (DECchip 21050).	1. Check that the J1 jumper on the CPU daughter board is set at bank 1 for AlphaServer 1000A systems, as opposed to bank 0, reserved for AlphaServer 1000 systems.   Note that model 5/xxx systems can use either standard boot setting, bank 0 or 1, regardless of system, and that model 5/300 systems use jumper designator J4 rather than J1. 2. If the J1 jumper setting is not the problem, replace the motherboard.
3-3-3	J1 jumper on the CPU daughter board set incorrectly or failure of the native SCSI controller (NCR810) on the system motherboard.	1. Check that the J1 jumper on the CPU daughter board is set at bank 1 for AlphaServer 1000A systems, as opposed to bank 0, reserved for AlphaServer 1000 systems.   Note that model 5/xxx systems can use either standard boot setting, bank 0 or 1, regardless of system, and that model 5/300 systems use jumper designator J4 rather than J1. 2. If the J1 jumper setting is not the problem, replace the motherboard.


Isolating Failing SIMMs

Troubleshooting
Model 4/xxx SROM Memory Power-Up Tests

Isolating Failing SIMMs

If the power-up tests or ROM-based diagnostics indicate a memory error without identifying the failing bank and SIMM position, you can match the failing address to a table using the procedure provided with the memory command, or for model 4/xxx systems, you can run specific SROM power-up tests using jumper J1 on 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 3, Backup Cache Test

Bank 5, Memory Test, Backup and Data Cache Disabled

Bank 6, Memory Tests, Backup and Data Cache Enabled

Bank 4, Backup Cache and MemoryTest


SROM Memory Tests, Bank 6

Troubleshooting
SROM Memory Power-Up Tests

Model 4/xxx SROM Memory Power-Up Tests, Bank 6

Bank #	Test Description	Test Results
6	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 correctable errors, replace  the suspected ECC SIMMs with good SIMMs and repeat the memory tests. ECC SIMMs cannot be used in the standard memory banks (banks 0--3).   ECC SIMMs are specialized for use only in ECC banks.


SROM Memory Tests, Bank 4

Troubleshooting
SROM Memory Power-Up Tests

Model 4/xxx SROM Memory Power-Up Tests, Bank 4

Bank #	Test Description	Test Results
4	Backup Cache Test: Test: Tests 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 correctable errors, replace  the suspected ECC SIMMs with good SIMMs and repeat the memory tests. ECC SIMMs cannot be used in the standard memory banks (banks 0--3).   ECC SIMMs are specialized for use only in ECC banks.


SROM Memory Tests, Bank 3

Model 4/xxx SROM Memory Power-Up Tests, Bank 3

Bank #	Test Description	Test Results
3	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

Model 4/xxx SROM Memory Power-Up Tests, Bank 5

Bank #	Test Description	Test Results
5	Memory Test: Tests: 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 correctable errors, swap the suspected ECC SIMMs with good SIMMs and repeat the memory tests. ECC SIMMs cannot be used in the standard memory banks (banks 0--3).   ECC SIMMs are specialized for use only in ECC banks.


Memory Layout

Model 4/xxx AlphaServer 1000A Memory Layout


Startup Action (set auto_action)

Troubleshooting
Boot Failures

Startup Action (set auto_action)

Synopsis

Set the console action at power-up and restart.

Command

set auto_action  value

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


Value	Description
halt	Causes the system to remain in console mode after the system is powered up or it fails (default).
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

Sets the action the console should take any time the system is powered up, fails, 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.

Whenever you change the value of this environment variable, you must initialize the firmware with the init command.


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

>>> init

 .

 .

 .

>>> 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 of a boot device.  See the show device command for device naming conventions.


Boot Device -- Description

Troubleshooting
Boot Failures

Boot Device -- Description

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

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

DIGITAL UNIX Command:

set boot_osflags bootflag

OpenVMS Command:

set boot_osflags root number,bootflag

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


Boot Flags (DIGITAL UNIX)

Possible boot flag settings and their meanings for DIGITAL UNIX systems are:

Flag Setting	Meaning
a	Autoboot to multi-user mode.
i	Boot interactively to single user mode.  Prompts for the name of a file to load and other options.
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 DIGITAL UNIX fails, it completes a partial memory dump. Specifying "D" forces a full dump.


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:  You can specify multiple boot flags by adding the flag values together (logical Oring).  For example, the flag value 10080 executes both the 80 and 10000 flag settings.


Boot Flags -- Description

Boot flags contain information used by the operating system to determine some aspects of a system bootstrap.  Under normal circumstances, you can use the default boot flag settings.

To change the boot flags for the current boot only, you can use the flags_value option with the boot command.

The argument flags_value is specific to the operating system.

The DIGITAL UNIX operating system takes a single ASCII character as an argument.

The OpenVMS operating system expects an ordered pair: 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 -- DIGITAL UNIX

The boot flags are set to autoboot:

>>> set boot_osflags a

Example 2-- OpenVMS

The root_number is set to 2 and boot_flags is set to 1:

>>> set boot_osflags 2,1

With this setting, the system will boot from root directory SYS2.SYSEXE to the SYSBOOT prompt.

Example 3 -- OpenVMS

The root_number is set to 0 and boot_flags is set to 80:

>>> set boot_osflags 1

With this setting, the operator will be prompted for the name of the secondary bootstrap file.


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 reset from OpenVMS to Microsoft Windows NT.  After the system is initialized, the Windows NT Boot menu will be displayed.

>>> set os_type nt

>>> init

 .

 .

 .


os type	Description
UNIX or OSF	Sets the default operating system to DIGITAL UNIX; starts SRM firmware
VMS	Sets the default operating system to OpenVMS; starts SRM firmware
NT	Sets the default operating system to Microsoft Windows NT; starts ARC firmware


Operating System -- Description

The operating system is set at the factory to DIGITAL UNIX, OpenVMS, or Windows NT, depending on the operating system purchased.  The set os_type command is used to change the factory default setting to the operating system you specify.  The os_type environment variable also sets the firmware environment variable that will be started whenever the system powers up, is halted or restarted, or the operating systems is shut down.

If os_type is set to OpenVMS, the system starts the SRM firmware, and OpenVMS is the default operating system.

If os_type is set to DIGITAL UNIX, the system starts the SRM firmware, and DIGITAL UNIX is the default operating system.

If os_type is set to Windows NT, the systems starts the ARC firmware, and Windows NT is the default operating system.

If you decide to change operating systems, from DIGITAL UNIX or OpenVMS to Windows NT or from Windows NT to DIGITAL UNIX or OpenVMS, you must reset the os_type environment variable in order to activate the appropriate firmware for the operating system.  If you change to Windows NT, you must also use the appropriate EISA Configuration Utility diskette.

Whenever you change the value of this environment variable, you must initialize the firmware with the init command.


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.

Whenever you change the value of this environment variable, you must initialize the firmware with the init command.

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

>>> init

 .

 .

 .

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

To get a list of the controllers on your system, enter the show device command.  SCSI devices begin with the letters pk, for example pka0.  The third letter is the adapter ID for the controller.  When entering the set pk*_host_id command, replace the asterisk (*) with the adapter ID letter.


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 Display hardware configuration menu item and press Enter.	The system displays the hardware configuration screens.
ARC Firmware Device Names

Note:  The Available hardware devices display marks tape devices as not used by the firmware.  All PCI and EISA network cards are listed under the PCI and EISA screen displays.

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.

The hardware configuration display provides the following information:

The first screen displays system information, such as the memory, CPU type, speed, NVRAM usage, the ARC version time stamp, and the type of video option detected.

The second screen displays devices detected by the firmware, including the monitor, keyboard, serial ports and devices on the SCSI bus.  Tape devices are displayed, but cannot be accessed from the firmware.

The third screen contains the PCI slot information: bus number, device number, function number, vendor ID, revision ID, interrupt vector and device type.  All PCI network cards are displayed.

The fourth screen contains the EISA slot information: slot, device, and identifier.  All EISA network cards are displayed.

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


Listing ARC Firmware Boot Device Names - Example

Troubleshooting
Boot Failures

Example

Hardware Configuration Display

12/20/1995  9:06:23 AM

Alpha Processor and System Information:

Processor ID	21064
Processor Revision	3
System Revision	0x1
Processor Speed	266.02 Mhz
Physical Memory	64 MB
Backup Cache Size	2 MB

Extended Firmware Information:

  Version 4.45 (Proto) 951212.0949

  NVRAM Environment Usage: 75%

     (744 of 1024 bytes)

Video Option detected:

  BIOS controlled video card

Press any key to continue...

12/20/1995  9:06:23 AM

Devices detected by the firmware:

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)	(4 Partitions)	DEC RZ29B (C)DEC007C
scsi(0)cdrom(0)fdisk(0)	(Removable)	DEC RRD43 (C)DEC 1084

Press any key to continue...

12/20/1995  9:06:23 AM

PCI slot information:

Bus Number	Device Number	Function Number	Vendor     ID	Device    ID	Revision    ID	Interrupt  Vector	Device   Type
0	7	0	8986	482	4	0	EISA bridge
0	8	0	1011	1	2	0	PCI bridge
0	11	0	1011	2	23	13	Ethernet
1	1	0	1000	1	1	19	SCSI

Press any key to continue...

12/20/1995  9:06:23 AM

EISA slot information:

Slot	Device	Identifier
0	Other	DEC5000
0	Disk	FLOPPY

Press any key to continue...


Default ARC Environment Variables

Troubleshooting
Boot Failures

Set Default Environment Variables

Caution:  Do not edit or delete the default firmware Windows NT environment variables. This can 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.
ENABLEPCIPARITY 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 disabled.
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 Windows NT 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.
VERSION	The firmware version.

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:

Console Firmware Version Prior to V4.6

Firmware

Memory

PCI Bus

EISA Bus

Console Firmware Version V4.6 or Later

Firmware

Memory

Hose 0, Bus 0, PCI

Hose 0, Bus 1, EISA

Hose 0, Bus 2, PCI

Hose 0, Bus 3, PCI

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:

Bus 0, Slot 7 = PCI to EISA bridge chip

Bus 0, Slot 8 = PCI to PCI bridge chip

---Bus 2, Slot 0 = SCSI controller on backplane, along with storage drives on the bus

---Bus 2, Slots 1--4 correspond to physical PCI card cage slots on the secondary PCI bus:

Slot 1 = PCI1

Slot 2 = PCI2

Slot 3 = PCI3

Slot 4 = PCI4

In the case of storage controllers, the devices off the controller are also displayed.

---Bus 0, Slots 11--13 correspond to physical PCI card cage slots on the primary PCI bus:

Slot 11 = PCI11

Slot 12 = PCI12

Slot 13 = PCI13

In the case of storage controllers, the devices off the controller are also displayed.

Physical Slot Locations on the Card Cage


show config

EISA Bus:

Slot numbers correspond to EISA card cage slots (1 and 2). For storage controllers, the devices off the controller are also displayed.


show config

Hose 0, Bus 0, PCI:

All controllers on Hose 0, Bus 0 of the primary PCI bus.  The logical slot numbers are listed in the left column of the display.

Slot 7 = PCI to EISA bridge chip

Slot 8 = PCI to PCI bridge chip

Slots 11--13 correspond to physical PCI card cage slots on the primary PCI bus:

Slot 11 = PCI11

Slot 12 = PCI12

Slot 13 = PCI13

In the case of storage controllers, the devices off the controller are also displayed.

Physical Slot Locations on the Card Cage


show config

Hose 0, Bus 1, EISA:

All controllers on Hose 0, Bus 1 of the EISA bus.  The logicall slot numbers in the left column of the display correspond to physical EISA card cage slots (1 and 2).

In the case of storage controllers, the devices off the controller are also displayed.

Physical Slot Locations on the Card Cage


show config

Hose 0, Bus 2, PCI:

All controllers on Hose 0, Bus 2 of the secondary PCI bus.  The logical slot numbers are listed in the left column of the display.

Slot 0 = SCSI controller on the system backplane, along with storage drives on the bus.

Slots 1--4 correspond to physical PCI card cage slots on the secondary PCI bus:

Slot 1 = PCI1

Slot 2 = PCI2

Slot 3 = PCI3
Slot 4 = PCI4

In the case of storage controllers, the devices off the controller are also displayed.

Physical Slot Locations on the Card Cage


show config

Hose 0, Bus 3, PCI:

If PCI options contain a PCI-to-PCI bridge, such as the DECchip 21050-AA in the secondary PCI bus, slot 4 in the show configuration example, the additional bus is represented in the display.

For each option that contains a PCI-to-PCI bridge, the bus number increments by 1, and the logical numbers start anew at 0.

Physical Slot Locations on the Card Cage


Physical Slot Locations

Physical Slot Locations on the Card Cage


show config - Example

Troubleshooting
Boot Failures

Example (Firmware Version Prior to V4.6)

>>> show config

Firmware

SRM Console:    X4.4-5365

ARC Console:4.43p

PALcode:        VMS PALcode X5.48-115, OSF PALcode X1.35-84

Serial Rom:     X2.1

Processor

DECchip (tm) 21064-6

MEMORY

     48 Meg of System Memory

     Bank 0 = 32 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 07: Intel  8275EB PCI to EISA Bridge

   Bus 00  Slot 08: Digital PCI to PCI Bridge Chip

  Bus 02  Slot 00:  ISP1020 SCSI Controller

                                   pka0.7.0.2000.0      SCSI Bus ID 7

                                   dka0.0.0.2000.0      RZ29B

                                   dka500.5.0.2000.0    RRD45

  Bus 02  Slot 04:  DECchip 21040 Network Controller

                                   ewa0.0.0.2004.0    08-00-2B-E5-6A-41

   Bus 00  Slot 11: DECchip 21040 Network Controller

                                   ewb0.0.0.11.0      08-00-2B-E1-03-19

EISA Bus Modules (installed)

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

>>>

Note: The onboard SCSI controller (Qlogic 1020A) is always device pka.

The following show config example illustrates how PCI options that contain a PCI-to-PCI bridge are represented in the display.  For each option that contains a PCI-to-PCI bridge, the bus number increments by 1, and the logical slot numbers start anew at 0.

The sample system configuration contains the following options:

 Primary Bus

Physical PCI slot 11: KZPSM option with PCI-to-PCI bridge (1)

Physical PCI slot 12: KZPSM option with PCI-to-PCI bridge (2)

Physical PCI slot 13: ---

 Secondary Bus

Physical PCI slot 1: ---

Physical PCI slot 2: ---

Physical PCI slot 3: KZPSM option with PCI-to-PCI bridge (3)

Physical PCI slot 4: NCR810 SCSI controller

Example (Firmware Version Prior to V4.6)

>>> show config

Firmware

SRM Console:    X4.4-5365

ARC Console:4.43p

PALcode:        VMS PALcode X5.48-115, OSF PALcode X1.35-84

Serial Rom:     X2.1

Processor

DECchip (tm) 21064-6

MEMORY

     48 Meg of System Memory

     Bank 0 = 32 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 07: Intel  8275EB PCI to EISA Bridge

   Bus 00  Slot 08: Digital PCI to PCI Bridge Chip

  Bus 02  Slot 00:  ISP1020 SCSI Controller

                                   pka0.7.0.2000.0      SCSI Bus ID 7

                                   dka0.0.0.2000.0      RZ29B

                                   dka500.5.0.2000.0    RRD45

  Bus 02  Slot 03:  Digital PCI to PCI Bridge Chip (3)

          Bus  3  Slot 0           ewa0.0.3000.0    08-00-3C-E6-6B-41

          Bus  3  Slot 1           ISP1020 Controller

                                   pkb0.7.0.3001.0

                                   dkb0.0.0.3001.0

                                   dkb100.0.0.3001.0

  Bus 02  Slot 04:  NCR 810 SCSI Controller

                                   dkc100.1.0.2004.0

                                   dkc200.2.0.2004.0

   Bus 00  Slot 11: Digital PCI to PCI Bridge Chip (1)

     Bus 04  Slot 0:  DEC 21040 Network Controller

                                 ewb0.0.0.4000.0  08-12-2E-C3-04-92

     Bus 04  Slot 1:  ISP1020 Controller

                                 pkd0.7.0.4001.0

   Bus 00  Slot 12: Digital PCI to PCI Bridge Chip (2)

     Bus 05  Slot 0:  DEC 21040 Network Controller

                                 ewc0.0.0.5000.0  08-24-3D-C6-08-04

     Bus 05  Slot 1:  ISP1020 Controller

                                  pke0.7.0.5001.0

EISA Bus Modules (installed)

   Slot 01: MLX0075 SCSI Controller

                                  dkc0.7.0.2004.0

>>>

Example (Firmware Version V4.6 or Later)

>>> show config

                   Digital Equipment Corporation

                      AlphaServer 1000A 5/300

Firmware

SRM Console:    X4.6-322

ARC Console:5.12

PALcode:        VMS PALcode V1.18-2, OSF PALcode V1.21-4

Serial Rom:     T1.1

Processor

DECchip (tm) 21164-5 300MHz

MEMORY

     64 Meg of System Memory

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

     Bank 1 = No Memory Detected

     Bank 2 = No Memory Detected

     Bank 3 = No Memory Detected

Slot   Option        Hose 0, Bus 0, PCI

  7    Intel  8275EB          Bridge to Bus 1, EISA

  8    DECchip 21050-AA       Bridge to Bus 3, PCI

 11    DECchip 21040-AA    ewb0.0.0.11.0   08-00-2B-E5-CC-B1

Slot   Option        Hose 0. Bus 1, EISA

  1    DE422         era.0.0.0.1001.0      08-00-2B-39-4F-4E

Slot   Option        Hose 0, Bus 2, PCI

  0    Qlogic ISP1020   pka0.7.0.2000.0      SCSI Bus ID 7

                        dka0.0.0.2000.0      RZ29B

                        dka400.4.0.2000.0    RRD45

  4    DECchip 21050-AA            Brige to Bus 3, PCI

Slot   Option       Hose 0, Bus 3, PCI

  0    DECchip 21040-AA  ewa0.0.3000.0    08-00-3C-E6-6B-41

  2    QLogic ISP1020    pkb0.7.0.3002.0     SCSI Bus ID 7

  3    QLogic ISP1020    pkc0.7.0.3003.0     SCSI Bus ID 7

>>>


show device

Troubleshooting
Boot Failures

show device

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

Driver ID

Storage adapter ID

Device Unit Number

Bus Node Number

Channel Number

Logical 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

ewa0.0.0.2.1               EWA0              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


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 option physical slot numbers (1 and 2)

For PCI options:

Slot 8 = PCI to PCI bridge chip
Slot 0 = SCSI controller on system backplane.
Slot 1--4 = (Secondary bus)  Correspond to physical PCI options slots: PCI1, PCI2, PCI3, and PCI4

Slots 11--13 = (Primary bus)  Correspond to physical PCI options slots: PCI11, PCI12, and PCI13


SWXCR-XX controller

Troubleshooting
Console-Reported Failures

Troubleshooting RAID Problems

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 Subsystems Controller Installation and Standalone Configuration Utility Users Guide. 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-04 (68-pin); 17-41667-02 (50-pin).
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 Subsystems Controller Installation and Standalone Configuration Utility Users Guide. External SCSI terminators used with the SWXCR controller must be of the following type: 12-41667-04 (68-pin); 17-41667-02 (50-pin).
Cannot access disks connected to the RAID subsystems on Windows NT systems.	On Windows NT systems, disks connected to the controller must be spun up before they can be accessed.  While running the ECU, verify that the controller is set to spin up two disks every six seconds.  This is the default setting if you are using the default configuration files for the controller.  If the settings are different, adjust them as needed.


ew*0_protocols, er*0_protocols

Troubleshooting
Boot Failures

er*0_protocols, ew*0_protocols

Synopsis

Enable 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 device 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 (Maintenance Operations Protocol): the setting typically used for systems using the OpenVMS operating system (default setting).
bootp	Sets the network protocol to bootp: the setting typically used for systems using the DIGITAL UNIX operating system.
bootp,mop	The bootp and mop qualifiers can be used in a list, separated by a comma.  When the settings are used in a list, the system attempts to use the mop protocol first, regardless of which protocol is listed first.  If not successful, it then attempts to use the bootp protocol.


Default Boot Flags - Example

Troubleshooting
Boot Failures

Example 1

The network protocol is set to mop for the devices ewa0.

>>> set ewa0_protocols mop

>>> show ewa0_protocols

ewa0_protocols          MOP

Example 2

The network protocol is set to bootp for device ewa0.

>>> set ewa0_protocols bootp

>>> show ewa0_protocols

ewa0_protocols          BOOTP

Example 3

The network protocol is set to mop or bootp for device ewa0.

>>> set ewa0_protocols bootp,mop

>>> show ewa0_protocols

ewa0_protocols          BOOTP,MOP


bus_probe_alorithm

Troubleshooting
Boot Failures

bus_probe_algorithm

Synopsis

Specifies a bus probe algorithm for the systems. Not applicable for systems running Windows NT.

Qualifier	Meaning
old	Systems running OpenVMS V6.1 or earlier must set the bus probe algorithm to old---failure to do so could result in bugcheck errors when booting from an EISA device.
new	Systems running DIGITAL UNIX V3.0B or later or OpenVMS V6.2 or later should be set to new.  This setting improves the bus sizing and configuration for DIGITAL UNIX systems.

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


Bus Probe Algorithm - Example

Troubleshooting
Boot Failures

Example

The bus probe algorithm is set to new.

>>> set bus_probe_algorithm new

>>> init

 .

 .

 .

>>> show bus_probe_algorithm

bus_probe_algorithm       new


Power-up Screen

Troubleshooting
Boot Failures

Power-Up Screen

During power-up self-tests, the test status and result are displayed on the console terminal.  Information similar to the following should be displayed on the screen.

Model 4/xxx Systems

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

ef.df.ee.f4.ed.ec.initializing keyboard

eb.....ea.e9.e8.e7.e6.e5.e4.e3.e2.e1.e0.

X4.4-5365, built on Oct 27 1995 at 09:26:04

Model 5/xxx Systems

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

probing hose 0, PCI
probing PCI-to-PCI bridge, bus 1
bus 1, slot  0 -- pka --Qlogic ISP 1020
bus 0, slot 11 -- ewa -- DECchip 21040-AA
probing hose 1, EISA
ed.ec.eb....ea.e9.e8.e7.e6.e5.e4.e3.e2.e1.e0.

X4.6-8189, built on Jul 29 1996 at 09:26:04
Memory Testing and Configuration Status
32 Meg of System Memory
Bank 0 = 32 Mbytes (8 MB Per SIMM) Starting at 0x00000000
Bank 1 = No Memory Detected
Bank 2 = No Memory Detected
Bank 3 = No Memory Detected

Testing the System
Change mode to Internal loopback.
Change to Normal Operating Mode.
>>>

If the power-up display stops, use the error beep codes and a description of the power-up countdown to isolate the likely field-replaceable unit (FRU).  Model 5/xxx systems report errors and status  to the OCP during SROM power-up tests.

DIGITAL UNIX or OpenVMS Systems

DIGITAL UNIX and OpenVMS operating systems are supported by the SRM firmware.  The SRM console prompt, >>>, is available using SRM console firmware.

Windows NT for Model 4/xxx Systems

The Windows NT operating system is supported by the ARC firmware for model 4/xxx systems.  Model 4/xxx systems using Windows NT power up to the ARC boot menu as follows:

Alpha Firmware Version n.nn

Copyright (c) 1993-1995 Microsoft Corporation

Copyright (c) 1993-1995 Digital Equipment Corporation

Boot menu:

  Boot Windows NT

  Boot an alternate operating system...

  Run a program...

  Supplementary menu...

Use the arrow keys to select, then press Enter.

Windows NT for Model 5/xxx Systems

The Windows NT operating system is supported by the AlphaBIOS firmware for model 5/xxx systems.  Model 5/xxx systems using Windows NT power up to the AlphaBIOS boot menu as follows:

Refer to the AlphaServer 1000/1000A Model 5/xxx Owners Guide Supplement for information on the AlphaBIOS firmware.


Power-up countdown description and Field Replaceable Units (FRUs)

Troubleshooting
Boot Failures

Console Power-Up Countdown Description and Field Replaceable

Units (FRUs)

Countdown Number	Description	Likely FRU
ff	Console initiation  started	Non-specific/Status message
fe	Initialized idle PCB	Non-specific/Status message
fd	Initializing semaphores	Non-specific/Status message
fc,fb,fa	Initializing heap	Non-specific/Status message
f9	Initializing driver structures	Non-specific/Status message
f8	Initializing idle process PID	Non-specific/Status message
f7	Initializing file system	TOY chip (E78)
f6	Initializing timer data structures	Non-specific/Status message
f5	Lowering IPL	Non-specific/Status message
f4	Entering idle loop	TOY chip (E78)
ef	Start memory configuration (heap)	SIMM memory or backplane
df	Configure PCI and EISA bus	PCI or EISA option
ee	Start phase 1 drivers: NVRAM and PCICFG drivers	NVRAM chip (E14) or PCI option
ed	Start phase 2 drivers: IIC and OCP drivers	Non-specific/Status message
ec	Start phase 3 drivers (console selct): tt serial line class, tga graphics, vga graphics, and keyboard drivers	Keyboard, VGA or TGA option, or backplane
eb	Run power-up memory test	SIMM memory
ea	Start phase 4 drivers	Non-specific/Status message
e9	Phase 4 drivers complete	Non-specific/Status message
e8	Initialize environment variables	Non-specific/Status message
e7	Start SCSI class driver	Backplane (on-board Qlogic 1020A)
e6	Start phase 5 drivers: I/O drivers	PCI or EISA option
e5	Restore timers	TOY chip (E78)


Model 5/xxx SROM Test/Status Codes

Troubleshooting
Boot Failures

Model 5/xxx SROM Error Codes

Model 5/xxx systems report error and status to the OCP display during SROM power-up tests.  The table below provides an explanation of the status and error codes that may be displayed:

  Fatal error codes identify errors that prevent the system from accessing the console and booting the operating system.

  Nonfatal error codes identify errors that may not prevent the system from accessing the console, but may prevent the system from successfully booting the operating system.

  Execution status codes identify the process that is currently underway.

Note:  If errors are reported, be sure that the CPU daughter board is properly seated in its connectors.

OCP Code	Description	Likely FRU
Fatal Error Codes

FF	N s-cache bits set in sc_ctl register	CPU daughter board
FD	Floppy load error	Bad or wrong diskette drive
FA	No usable memory detected	SIMM memory or backplane
F9	System init failure	CPU daughter board
F8	PCI data path error	CPU daughter board
F7	CIA/PCEB I/O register init failure	CPU daughter board
F6	Bad CIA memor csr detected	CPU daughter board
F4	Bcache data path error	CPU daughter board
F3	Bcache address line error	CPU daughter board
F1	Flash ROM data path read error	CPU daughter board
Nonfatal Error Codes

EB	CPU speed error detected	CPU daughter board
EA	PCI-to-PCI (PPB) data path error	Motherboard
E9	No real-time clock (TOY)	TOY/NVRAM chip
E6	EISA configuration NVRAM
E5	Main memory data path error
E4	Q-Logic SCSI data path error
E3	Main memory address lines error
E2	Super I/O error
E1	Main memory cell test error
E0	Flash ROM checksum error
Execution Status Codes

DF	SROM program beginning to initialize the EV5 CPU
DE	Initialize CPU and system interface
DD	Sizing CPU speed
DC	Sizing S-cache
DB	Initializing and testing the PCI bus
DA	Sizing B-cache
D9	Sizing memory
D8	Configuring memory
D7	Initializing Bcache
D6	Testing memory
D5	Testing Bcache bits
D4	Testing memory bits
D3	Testing Bcache address
D2	Testing memory address
D1	Testing Bcache cells
D0	Testing memory cells
CF	Initializing memory
CD	Loading Flash ROM code
CC	Re-initializing CPU and system interface
CB	SROM execution completed	The system could hang here if EV4 code is used with 5/xxx systems.


SCSI Terminator

SCSI Termination at Rear Port


Console Port Configurations

Troubleshooting
No Access to Console Mode

Console Port Configurations

Power-up information is typically displayed on the system's console terminal.  The console terminal may be either a graphics monitor or a serial terminal (connected through the COM1 serial port).

There are several SRM console environment variables related with configuring console ports:

Environment Variable	Description
console	Determines where the system will display power-up output.  Set this environment variable according to the console terminal that you are using.
tt_allow_login	Enables or disables login to the SRM console firmware on alternative console ports.

In addition, the tga_sync_green environment variable is used to synchronize monitors using the high-performance turbo graphics adapter card (PBXGA).

A serial terminal can also be configured to run the ECU.


set console

The setting of the console environment variable determines where the system will display power-up output.  Power-up information is typically displayed on the console terminal.  The console terminal can either be a graphics monitor or a serial terminal.  Set this environment variable  to the console terminal that you are using.

Whenever you change the value of this environment variable, you must initialize the firmware with the init command.

Synopsis:

set console output_device

Arguments:

graphics	Sets the power-up output to be displayed at a graphics monitor or a device that is connected to the VGA module at the rear of the system (default setting).
serial	Sets the power-up output to be displayed on the device that is connected to the COM1 port at the rear of the system.
Example:

>>> set console serial

>>> init

 .

 .

 . !Now switch to the serial terminal.

>>> show console

Console      serial


set tt_allow_login

The setting of the tt_allow_login environment variable enables or disables login to the SRM console firmware on alternative console ports.

Whenever you change the value of this environment variable, you must initialize the firmware with the init command.

Synopsis:

set tt_allow_login [0,1]

Arguments:

1	Enables login on alternative ports (default setting). If the console output device is set to serial, allows you to log in on the primary COM1 port, or alternate COM2 port, or the graphics monitor. If the console output device is set to graphics, allows you to log in through either the primary graphics monitor or the alternate COM1 or COM2 console port.
0	Disables login on alternative console ports.
Example:

>>> set console serial

>>> set tt_allow_login 1

>>> init

 .

 .

 .


set tga_sync_green

The tga_sync_green environment variable set the location of the SYNC signal generated by the ZLX-p-E PCI graphics accelerator card.

The correct setting, displayed with the show command, is:

>>> show tga_sync_green

tga_sync_green   0

If the monitor does not synchronize, set the parameter as follows:

>>> set tga_sync_green 00

This command sets all graphics cards to synchronize on a separate vertical SYNC line, as required by some monitors.  See the monitor documentation for all other information.


Running AlphaBIOS or ARC on a Serial Terminal

Troubleshooting
No Access to Console Mode

Setting Up a Serial Terminal to Run the ARC or AlphaBIOS
Console and the ECU

You can run the ECU and interface with the ARC or AlphaBIOS console from either a VGA-compatible graphics monitor or from a serial terminal (VT320 or higher, or equivalent).  Graphics is the default.  If you use the serial line, use serial line equivalents to the graphics line keyboard commands.  To use a serial terminal with the ECU, do the following:

1.	Invoke the terminal setup utility as described in the documentation for the serial terminal and change settings as follows:

  From the General menu, set the terminal mode to Vtxxx, 8-bit controls.

  From the Comm menu, set the character format to 8 bit, no parity, and set receive XOFF to 128 or greater.

  From the Keyboard menu, set the keyboard so that the tilde (~) key sends the escape (ESC) signal.

2.	Enter the following commands at the SRM console prompt to set the console terminal to receive in serial mode.

>>> set console serial

>>> init

 .

 .

 .  !Now switch to the serial terminal.

>>> show console

console   serial


Serial Line Keyboard Commands

Graphics Line Commands	Serial Line Commands
F1	CTRL +A
F2	CTRL +B
F3	CTRL +C
F4	CTRL +D
F5	CTRL +E
F6	CTRL +F
F7	CTRL +P
F8	CTRL +R
F9	CTRL +T
F10	CTRL +U
Insert	CTRL +V
Delete	CTRL +W
Backspace	CTRL +H
ESC	CTRL +[


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 1000A 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-04195-01	Power supply current sharing cable (3-pin)
17-31346-01	Power supply DC cable assembly: Signal/misc, (15-pin) 17-03965-01, +5V harness (24-pin), 17-03966-01, +3.3V harness (20-pin) 17-03968-01
17-03969-01	Power supply storage harness (12-pin)
70-32283-01	Interlock/Server management cable (2-pin)
17-04021-01	Internal StorageWorks jumper cable (68-pin)
17-04022-01	Wide-SCSI (option controller to StorageWorks shelf) cable (68-pin)
17-04022-02	Wide-SCSI (native controller to StorageWorks shelf) cable (68-pin)
17-04019-01	Wide-SCSI (J10 to bulkhead connector) cable (68-pin)
17-04233-01	SCSI (embedded 8-bit) removable-media cable (50-pin)
CPU Modules
54-24799-01	400 MHz CPU daughter board
54-24799-02	333 MHz CPU daughter board
54-24719-02	300 MHz CPU daughter board
54-23297-04	266 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 - VW	StorageWorks disk drive (16-bit SCSI)
54-23365-01	Internal StorageWorks backplane
12-45490-01	Internal SCSI terminator
17-04021-01	Internal StorageWorks jumper cable (68-pin)
Memory Modules
54-21225-BA	1 x 4MB SIMM
54-21246-BA	1 x 8MB SIMM
54-23170-BA	1 x 16MB SIMM
54-21277-BA	1 x 32MB SIMM
54-24123-AA	1 x 64MB SIMM
Other Modules and Components
70-31348-01	Interlock switch
54-23499-01/-02	System Motherboard
21-29631-02	NVRAM chip (E14)
54-32423-01	NVRAM TOY clock chip (E78)
54-23302-02	OCP module
	PCI/EISA Options
30-43120-02	Power supply (H7290-AA)
70-31349-01	Speaker
12-41667-05	External SCSI terminator (50-pin, removable-media bus)
12-41667-04	External SCSI RAID terminator (68-pin)
12-41667-02	External SCSI RAID terminator (50-pin)
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 1000A

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

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

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

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

NVRAM Chip (E14) and NVRAM TOY Chip (E78)

Note:  The NVRAM TOY clock chip contains the os_type environment variable.  The default setting is for the SRM console for OpenVMS or DIGITAL UNIX operating systems.


Interlock Switch Removal

Interlock Switch


OCP Cable Removal

OCP Module Cable (10-pin)


SCSI Cables

17-04022-01, Wide-SCSI (option controller to StorageWorks shelf) cable (68-pin)

17-04022-02, Wide-SCSI (native controller to StorageWorks shelf) cable (68-pin)

17-04019-01, Wide-SCSI (J10 to bulkhead connector) cable (68-pin)

17-04233-01, SCSI (embedded 8-bit) removable-media cable (50-pin)


Wide-SCSI Native Controller to StorageWorks Shelf (68-pin)

Wide-SCSI (Native Controller to StorageWorks Shelf) Cable (68-pin)


Wide-SCS (J10 to Bulkhead Connector) Cable (68-pin)

Wide-SCSI (J10 to Bulkhead Connector) Cable (68-pin)


Floppy Cable Removal

Floppy Drive Cable (34-pin)


SCSI (embedded 8-bit) Removable-Media Cable (50-pin)


Power Supply Current Sharing Cable (3-pin)


Power Supply DC Cable Assembly: Step 1

Removal and Replacement
Power Supply DC Cable Assembly, AlphaServer 1000A

Step 1:  Remove the cable channel guide.

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


Power Supply DC Cable Assembly: Step 2

Removal and Replacement
Power Supply DC Cable Assembly, AlphaServer 1000A

Step 2:  Remove the supply DC cable assembly.

The power supply DC cable assembly contains the following cables:

 Power supply signal/misc cable (15-pin)

 Power supply +5V cable (24-pin)

 Power supply +3.3V (20-pin)


Power Supply Storage Harness (12-pin)


Interlock/Server Management Cable (2-pin)


Internal StorageWorks Jumper Cable (68-pin)

Internal StorageWorks Jumper Cable and Terminator (68-pin)


Wide_SCSI (option controller to StorageWorks shelf) cable (68-pin)

Wide-SCSI (Option Controller to StorageWorks Shelf) Cable (68-pin)


SCSI Bulkhead Connector to Multinode Cable (50-pin)


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


PCI/EISA Option Removal: Steps 1 and 2

PCI/EISA Options

Step 1: Record the position of the failing EISA or PCI option.

Step 2: Remove failing option.

PCI and EISA slots


OCP Module Removal: Step 1

Removal and Replacement
OCP Module, AlphaServer 1000A

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

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

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

SIMM Memory Modules

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

reported by SROM power-up scripts or through the ROM-based diagnostic commands (memory and memexer).

AlphaServer 1000A system memory configuration rules

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


AlphaServer 1000 Memory Configuration Rules

AlphaServer 1000A System Memory Configuration Rules

Bank 0 must contain a memory option.

A memory option consists of five SIMMs for 4/xxx systems (0, 1, 2, 3, and 1 ECC SIMM for the bank), or four SIMMs for 5/xxx systems (0,1,2, and 3).  Model 5/xxx memory SIMMs have built in error detection and correction (ECC) logic and do not use the ECC SIMMs.

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

The ECC SIMM is not compatible with memory bank SIMMs.

Do not place an ECC SIMM in a memory bank slot.


Memory Module Removal: Steps 1 and 2

Removal and Replacement
Memory Modules, AlphaServer 1000A

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

Step 2: Locate the failing SIMM on the motherboard.

Model 4/xxx: AlphaServer 1000A Memory Layout

Model 5/xxx AlphaServer 1000A Memory Layout

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


Memory Module Removal: Step 3

Removal and Replacement
Memory Modules, AlphaServer 1000A

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

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

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


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 Subsystems Controller Installation and Standalone Configuration Utility Users 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 1000A

Power Cord


Power Cord Part Numbers

Removal and Replacement
Power Cord, AlphaServer 1000A

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


Internal StorageWorks Backplane: Step 1

Removal and Replacement
Internal StorageWorks Backplane, AlphaServer 1000A

Step 1:  Remove power supplies.

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


Internal StorageWorks Backplane: Step 2

Removal and Replacement
Internal StorageWorks Backplane, AlphaServer 1000A

Step 2:  Remove internal StorageWorks backplane.


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

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


Rear/Right View

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


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 1000A 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 DIGITAL UNIX operating  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 multipurpose system maintenance tool that performs exerciser-oriented maintenance testing.  DEC VET runs on OpenVMS, DIGITAL UNIX, 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 system loading, that is, simultaneous exercising of multiple devices.

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


Diagnostic Commands

Troubleshooting
ROM-Based Diagnostics (RBDs)

Running System 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.  For Model 4/xxx systems, the tests are run concurrently and indefinitely. For Model 5/xxx systems, the test command runs one pass of the tests.  To run the tests concurrently and indefinitely on Model 5/xxx systems, use the sys_exer command.
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
memexer	Exercises memory by running a specified number of memory tests on Model 5/xxx systems.  The tests are run in the background.
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.
sys_exer	Exercises core system for Model 5/xxx systems.  Runs tests concurrently.
Loopback Testing
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.
sys_exer -lb	Conducts loopback tests for COM2 and the parallel port in addition to core system tests for Model 5/xxx systems.
test_-lb	Conducts loopback tests for COM2 and the parallel port in addition to quick core system tests.
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 console event log at power-up, during normal system operation, and while running system tests.

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

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 abbreviated console event log that contains a standard error message indicating that the keyboard is not plugged in or is not working.

>>> cat el

*** keyboard not plugged in...

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

The following is an example with a memory compare error indicating bad SIMMs.  In most cases, the failing bank and SIMM position are specified in the error message.  If the failing SIMM information is not provided, you can manually determine the failing SIMM.

>>> 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:	25c07
Received value:	35c07
Failing addr:	a11848

*** End of Error ***

>>> kill diags

>>>


Isolating failing SIMM

Troubleshooting
ROM-Based Diagnostics (RBDs)

Manually Isolating a Failing SIMM

The following is an example with a memory compare error indicating bad SIMMs.  Use the procedure following the example to isolate the failing SIMM.

>>> memory  (or memexer 3 for EV5 systems)

>>> 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:	25c07
Received value:	35c07
Failing addr:	a11848

*** End of Error ***

>>> kill diags

>>>

To find the failing bank, compare the failing bank, compare the failing address (a11848 in this example) with the show memory display or memory portion of the show config command display:

1.	Banks with no memory present are eliminated as possible failing banks.

2.	If the failing address is greater than the bank starting address, but less than the starting address for the next bank, then the failing SIMM is within this bank (Bank 0 in the example using failing address a11848 and the following memory display).

>>> show memory
Memory

32 Meg of System Memory

Bank 0 = 16 Mbytes (4MB per SIMM) Starting at 0x00000000
Bank 1 = 16 Mbytes (4MB per SIMM) Starting at 0x01000000
Bank 2 = No Memory Detected

Bank 3 = No Memory Detected

>>>

To determine the failing SIMM:

Model 4/xxx Systems:

Match the least significant nibble of the failing address to the failing SIMM using the table below.

Failing Address Least  Significant Nibble	Failing SIMM
0	0
4	1
8	2
C	3

In the example, a11848, the 8 would indicate SIMM 2 as the failing SIMM.

Model 5/xxx Systems:

Match the least significant nibble of the failing address and the bit range in which the bad data is received to the failing SIMM using the table below.

Failing Address Least Significant Nibble	Data Miscompare In Bit Range	Failing SIMM
0 or 8	bits 15:0	0
0 or 8	bits 31:16	1
4 or C	bits 15:0	2
4 or C	bits 31:16	3
In the example the least significant nibble in the failing address is 8 (a11848).  The expected data value was 25c07, the received value was 35c07.

The data miscompare occurred in bits 16--19 or within bits 31:16; therefore, the failing SIMM is SIMM 1.

Model 4/xxx: AlphaServer 1000A Memory Layout

Model 5/xxx AlphaServer 1000A Memory Layout


Model 4/xxx: AlphaServer 1000A Memory Layout


Model 5/xxx: AlphaServer 1000A Memory Layout


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 also be used to test a 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, you 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:

netew 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 also be used to test a 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, you 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.


network --- Description

When the network 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:

network 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 run concurrently in the background. Fatal errors are reported to the console terminal.

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

For Model 4/xxx systems, the tests are run concurrently and indefinitely (until you stop them with the kill_diags or init  command); they are useful in flushing out intermittent hardware problems.

For Model 5/xxx systems, the test command runs one pass of the tests.  To run tests concurrently and indefinitely on Model 5/xxx systems, use the sys_exer command.

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.

The test command does not test the DNSES, TGA card, PCI to memory channel interconnect options or third-party options.

When using the test command after shutting down an operating system, you must initialize the system to a quiescent state.  Enter the following commands at the SRM console:

>>> set auto_action halt

>>> init

 .

 .

 .

>>> test

After testing is completed, set the auto_action environment variable to its previous value (usually, boot) and use the Reset button to reset the system.

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

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

A Model 4/xxx 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

A Model 4/xxx system is tested, and the system reports a fatal 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

>>>

Example 3

A Model 5/xxx system is tested and tests terminate after successfully completing one pass of the diagnostics.

>>> test

Testing the Memory

Testing the DK* Disks (read only)

No DU* Disks available for testing

No DR* Disks available for testing

No MK* Disks available for testing

No MU* Disks available for testing

Testing the DV* Floppy Disks (read only)

Testing the VGA (Alphanumeric Mode only )

Testing the EWA0 Network

Testing the EWB0 Network

>>>


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 console environment variable is set to serial." The VGA console test displays rows of the letter "H". or Digital.


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.


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 and sys_exer commands are run from the SRM interface.

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

Switching from SRM to ARC or AlphaBIOS

Switching from ARC to SRM

Switching from AlphaBIOS to SRM


Switching from SRM to ARC

Switching from SRM to ARC or AlphaBIOS

Two SRM console commands are used to temporarily switch to the ARC or AlphaBIOS console:

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

The ecu command loads the ARC firmware and then boots the ECU diskette.  For Model 5/xxx systems, the ecu command loads the AlphaBIOS firmware (same as the arc command).

For systems that boot the Windows NT operating system, return to the ARC console by setting the os_type environment variable to NT, then enter the init command:

>>> set os_type NT

>>> init


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 UNIX 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 the system is initialized, the SRM console prompt, >>>, is displayed.


Switching from ARC to SRM

Switching from AlphaBIOS to SRM

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

1.  From the CMOS Setup menu, press F6 to enter Advanced CMOS setup.

2.  From the Advanced CMOS Setup menu, select Windows NT (AlphaBIOS).

3.  Press F10 to save the change.

Note:  For information on AlphaBIOS, refer to the AlphaServer 1000/1000A Model 5/xxx Owners Guide Supplement.


Testing the System, Model 5/xxx (sys_exer)

Console Firmware
ROM-Based Diagnostics (RBDs)

Testing the System, Model 5/xxx (sys_exer)

Synopsis

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

Note:  The diagnostics started by the sys_exer command require extra memory resources.  The init command must be used to reconfigure memory before booting and operating the system.

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

Note:  By default, no write tests are performed on disk and tape drives.  Media must be installed to test the floppy drive and tape drives. A loopback connector is required for the COM2 (9-pin loopback connector, 12-27351-01) port when the -lb argument is used.

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.

When using the sys_exer command after shutting down an operating system, you must initialize the system to a quiescent state.  Enter the following commands at the SRM console:

>>> set auto_action halt

>>> init

 .

 .

 .

>>> sys_exer

After testing is completed, set the auto_action environment variable to its previous value (usually, boot) and use the Reset button to reset the system.

To terminate the tests, use the init command.

Command

sys_exer ([-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 (sys_exer)- Example

Console Firmware
ROM-Based Diagnostics (RBDs)

Example

A Model 5/xxx system is tested, and the tests complete successfully.

>>> sys_exer

Default zone extended at the expense of memzone.

Use INIT before booting

Exercising the Memory

Exercising the DK* Disks (read only)

Exercising the Floppy (read only)

Testing the VGA (Alphanumeric Mode only)

Exercising the EWA0 Network

Exercising the EWB0 Network

Type init in order to boot the operating system

Type show_status to display testing progress

Type cat el to redisplay recent errors

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

ff,fe,fd,fc,fb,fa,f9,f8,f7,f6,f5,ef,df,ee,f4.

.

.

.

>>>


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


Command Reference --- memexer

Troubleshooting
ROM-Based Diagnostics (RBDs)

memexer

Synopsis

Exercises memory by running a specified number of memory exercisers for Model 5/xxx systems.  The exercisers are run in the background and nothing is displayed unless an error occurs.

Command

memexer [number]

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


memory --- Description

The memexer command tests memory by running a specified number of memory exercisers.  The exercisers are run in the background and nothing is displayed unless an error occurs.  Each exerciser test all available memory in twice the backup cache size blocks for each pass.

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

>>> memexer 4

>>> 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
00000079	memtest	memory	1	0    0	24117248	24117248
>>> kill diags

>>>

Example with a memory compare error indicating bad SIMMs

The following is an example with a memory compare error indicating bad SIMMs.  In most cases, the failing bank and SIMM position are specified in the error message.  If the failing SIMM information is not provided, you can manually determine the failing SIMM.

>>> memexer 3

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

Diagnostic Name	ID	Device	Pass	Test	Hard/Soft	1-JUN-1996
memtest	000000c8	brd0	1	1	1     0	12:00:01
Expected value:	25c07
Received value:	35c07
Failing addr:	a11848

*** End of Error ***

>>> kill diags

>>>


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 Alpha 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 21164 microprocessors	Contains error detection and correction (EDC) logic for data cycles. There are check bits associated with all data entering and exiting the 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 PCI-to-PCI bridge chip	SCSI data parity is generated. PCI 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 21164 microprocessors.

The DECchip 21064 or DECchip 21164 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 microprocessor and possibly not related to the activities of the CPU. These errors are specific to AlphaServer 1000A systems.

Fatal errors:

System overtemperature failure

System complete power supply failure

The power supply number is called out in the register: power supply 1 is the bottom supply; power supply 2 is the top supply.

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 21164 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 21164 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 1000A-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 Alpha 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 Alpha, User and Reference Guide, AA-Q73KC-TE.

System faults can be isolated by examining translated system error logs or using the DECevent Analysis and Notification Utility.  Refer to the DECevent Analysis and Notification Utility for OpenVMS Alpha, User and Reference Guide, AA-Q73LC-TE, for more information.


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, AA-QAA3-TE.

System faults can be isolated by examining translated system error logs or using the DECevent Analysis and Notification Utility.  Refer to the DECevent Analysis and Notification Utility for DIGITAL UNIX, User and Reference Guide, AA-QAA4A-TE, for more information.


SCSI Buses
Single- and Multiple-Controller Configurations

SCSI Buses

An on-board, PCI-based controller on the motherboard provides 8-bit Fast SCSI-2 support for removable-media devices, and 16-bit fast-wide SCSI-2 support for internal StorageWorks devices. The on-board controller supports a 50-pin connector for the 5.25 inch removable-media devices, as well as a 68-pin connector for the fast-wide SCSI devices.

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. Use the SCSI configuration rules to determine whether a device can be used on the system.

The AlphaServer 1000A 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 drive's 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).

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

When configuring the StorageWorks shelf, note the following:

Narrow SCSI (8-bit) devices can be used in the wide StorageWorks shelf, as long as the devices are at a supported revision level.  The narrow devices will run in narrow mode.

Narrow and wide devices can be mixed in the wide StorageWorks shelf.  In a mixed configuration, wide devices run in wide mode and narrow devices run in narrow mode.

For best performance, wide devices should be operated in wide SCSI-2 mode.

SCSI Storage Configurations

SCSI Buses	Configuration
Single	The native Fast SCSI-2 controller on the backplane provides 8-bit SCSI support for the removable-media bus; and 16-bit SCSI support for up to five or six StorageWorks drives in the internal StorageWorks shelf.
Dual	Split StorageWorks Backplane: The native Fast SCSI-2 controller on the backplane provides 8-bit SCSI support for the removable-media bus; and 16-bit support for up to four StorageWorks drives in the internal StorageWorks shelf.  An additional option card provides 16-bit support for the remaining StorageWorks drives in the internal StorageWorks shelf.
Triple	Split StorageWorks Backplane: The native Fast SCSI-2 controller on the backplane provides 8-bit SCSI support  for the removable-media bus.  Two additional option cards provide support for the  StorageWorks drives in a split StorageWorks backplane configuration.


SCSI Configuration Rules for External SCSI Expansion

External SCSI Expansion:

External SCSI-2 devices, such as tabletop or rackmounted storage devices, can be connected to the system using EISA- or PCI-based SCSI adapters.  Use the following rules to determine if a particular device can be used:

The device must be supported by the operating system. Consult the software product description or hardware vendor.

A maximum seven devices can be on any one SCSI-2 controller.

Each device on the bus must have a unique SCSI ID.  You may need to change a device's default SCSI ID to make it unique.  All removable-media device bus node IDs are set via switches on the device.  For information about setting a device's ID, refer to the guide for that device.

The entire SCSI bus length, from end-to-end, terminator to terminator, must not exceed 3 meters for Fast SCSI-2 at 10 MB/sec (6 meters at 5 MB/sec).

Ensure that the SCSI bus is properly terminated and that no devices in the middle of the bus are terminated.


SCSI Buses, Single Controller

Single Controller Configuration


SCSI Buses, Dual Controller with Split StorageWorks Backplane

Dual Controller Configuration with Split StorageWorks Backplane


SCSI Buses, Triple Controller with Split StorageWorks Backplane

Triple Controller Configuration with Split StorageWorks Backplane


Exit

Do you want to exit this application?


Notices

V2 June 1997

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  1997 by Digital Equipment Corporation.  All Rights Reserved.

The following are trademarks of Digital Equipment Corporation:  AlphaServer, DEC VET, DIGITAL, OpenVMS, StorageWorks, and the DIGITAL logo.

UNIX Version is a registered trademark in the U.S. and other countries, licensed exclusively through the X/Open Company Ltd.  Windows NT is a trademark of Microsoft Corp.  All other trademarks and registered trademarks are the property of their respective holders.

Information Services

Contributors


Contributors

Phil Barrett - Graphic Designer

Andrea Thurber - Interface /Graphic Designer

Rich Trubey - Writer/Designer


Information Services

Alpha Firmware Updates

ECU Revisions

OpenVMS Patches

Late-Breaking Technical Information

Supported Options

Training

Digital Assisted Services


Alpha Firmware Updates

Under certain circumstances, such as a CPU upgrade or replacement of the system motherboard, you may need to update the system firmware.  An Alpha Firmware CD-ROM is available with DIGITAL UNIX, OpenVMS, and Windows NT operating systems.  The Alpha firmware files can also be downloaded from the Internet as follows:

ftp://ftp.digital.com/pub/Digital/Alpha/firmware/readme.html

The above README file describes the firmware directory structure, and how the files can be downloaded and used.

New versions of firmware released between shipments of the Alpha Firmware CD-ROM are available in an interim directory:

ftp://ftp.digital.com/pub/Digital/Alpha/firmware/interim/


ECU Revisions

The EISA Configuration Utility (ECU) is used for configuring EISA options on AlphaServer systems.  Systems are shipped with an ECU kit, which includes the ECU license.  Customers who already have the ECU and license, but need the latest revision of the ECU, can order a separate kit.  Call 1-800-DIGITAL to order.

If the customer plans to migrate from DIGITAL UNIX or OpenVMS to Windows NT, you must re-run the appropriate ECU.  Failure to run the operating system-specific ECU will result in system failure.


OpenVMS Patches

Software patches for the OpenVMS operating system are available from the World Wide Web as follows:

http://www.service.digital.com/html/patch_service.html

Chose the Contract Access option if you have a valid software contract with DIGITAL or you wish to become a software contract customer.  Choose the Public Access options if you do not have a software service contract.


Late Breaking Technical Information

Late-Breaking Technical Information

You can download up-to-date files and late-breaking technical information from the Internet.

The information includes firmware updates, the latest configuration utilities, software patches, lists of supported options, Wide SCSI information and more.

FTP Address:

ftp.digital.com

cd /pub/Digital/Alpha/systems/

World Wide Web address:

http://www.service.digital.com/info/alphaserver/tech_docs/


Supported Options

Refer to the AlphaServer 1000A Supported Options List for a list of options supported under DIGITAL UNIX, OpenVMS, and Windows NT.  The options list is available from the Internet as follows:

FTP Address:

ftp://ftp.digital.com/pub/Digital/Alpha/systems/

World Wide Web address:

http://www.digital.com/info/alphaserver/tech_docs/

You can obtain information about hardware configurations for the AlphaServer 1000A from the Digital Systems and Options Catalog. The catalog can be used to order and configure systems and hardware options.  The catalog presents all products that are announced, actively marketed, and available for ordering.

Access printable postscript files of any section of the catalog from the Internet as follows (be sure to check the Readme file):

ftp://ftp.digital.com/pub/Digital/info/SOC/

Access printable Postscript files of any section of the catalog from the Internet as follows (Be sure to check the Readme file):

ftp://ftp.digital.com/pub/Digital/info/SOC/


Training

Computer Based Training (CBT) and lecture lab courses are available from the DIGITAL training center:

Alpha Concepts

DSSI Concepts: EY-9823E

ISA and EISA Bus Concepts: EY-I113E-P0

RAID Concepts: EY-N935E

SCSI Concepts and Troubleshooting: EY-P841E, EY-N838E


Assisted Services

DIGITAL Assisted Services

DIGITAL Assisted Services (DAS) offers products, services, and programs to customers who participate in the maintenance of DIGITAL computer equipment. Components of DIGITAL assisted services include:

Spare parts and kits

Diagnostics and service information/documentation

Tools and test equipment

Parts repair services, including Field Change Orders


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.


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 or J4 jumper on the CPU daughter board


CPU Daughter Board, J3 and J4 Jumpers

CPU Daughter Board (J3 and J4) Supported Settings

AlphaServer 1000A 5/400 CPU

AlphaServer 1000A 5/333 CPU

AlphaServer 1000A 5/300 CPU

AlphaServer 1000A 4/266 CPU

AlphaServer 1000A 4/233 CPU


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

AlphaServer 1000A 4/266 CPU

CPU Daughter Board (J3 and J4) Supported Settings

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

J4 Jumper	J3 Jumper
Off	Off
Off
On
Off
On


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

AlphaServer 1000A 4/233 CPU

CPU Daughter Board (J3 and J4) Supported Settings

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

J4 Jumper	J3 Jumper
Off	Off
On
Off
Off
On


CPU Daughter Board (400 MHz), J3 Jumper

AlphaServer 1000A 5/400 CPU

CPU Daughter Board (J3) Supported Settings

Note: : These jumpers affect the clock speed and other critical system settings. The settings shown below are the supported jumper settings for AlphaServer 1000A 5/400 systems.

J3 Jumper

On
On
Off
Off
Off


CPU Daughter Board (333 MHz), J3 Jumper

AlphaServer 1000A 5/333 CPU

CPU Daughter Board (J3) Supported Settings

Note: : These jumpers affect the clock speed and other critical system settings. The settings shown below are the supported jumper settings for AlphaServer 1000A 5/333 systems.

J3 Jumper

On
Off
On
Off
Off


CPU Daughter Board (300 MHz), J3 Jumper

AlphaServer 1000A 5/300 CPU

CPU Daughter Board (J3) Supported Settings

Note: : These jumpers affect the clock speed and other critical system settings. The settings shown below are the supported jumper settings for AlphaServer 1000A 5/300 systems.

J3 Jumper

Off
On
On
Off
Off


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 J51
Jumper	Name	Description	Default Setting
J51	SCSI Termination	Allows the internal SCSI terminator to be disabled.	Enabled (as show).


Motherboard Jumper J16
Jumper	Name	Description	Default Setting
J16	Large Fan	Allows the large fan to be disabled to accommodate the alternative enclosures	This jumper is not installed on AlphaServer 1000A Systems.


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	Force Shutdown	Allows the operating system  to shut down the system if a fan fails or an over temperature condition occurs.	Enabled (as shown).


Motherboard Jumper J55
Jumper	Name	Description	Default Setting
J55	Small Fan	Allows the small fan to be disabled to accommodate the alternative enclosures.	This jumper is not installed on AlphaServer 1000A 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 when an enclosure fan fails--it is up to the operating system to shut the system down.	Enabled (as shown).


Motherboard Jumper J25
Jumper	Name	Description	Default Setting
J25	Remote Console Module (RCM) DC Enable	When enabled, activates the RCM DC enable connector (J17) for use with the RCM.	Disabled (as shown).


CPU Daughter Board, Jumper J1 or J4

CPU Daughter Board (Jumper J1 or J4)

Model 5/xxx J4 Jumper

Model 5/xxx J1 Jumper

Model 4/xxx J1 Jumper


CPU Daughter Board (4/xxx), Jumper J1

Default Jumper Settings
CPU Daughter Board (J1 Jumper)

Model 4/xxx CPU Daughter Board (Jumper J1)


J1 Jumper, Model 4/xxx
Bank	Jumper Setting
0	Standard boot setting (AlphaServer 1000 systems)
1	Standard boot setting (AlphaServer 1000A systems)
2	Mini-console setting: Internal use only
3	SROM CacheTest: backup cache test
4	SROM BCacheTest: backup cache and memory test
5	SROM memTest: memory test with backup and data cache disabled
6	SROM memTestCacheOn: memory test with backup and data cache enabled
7	Fail-Safe Loader setting: selects fail-safe loader firmware


CPU Daughter Board (5/xxx), Jumper J1

Default Jumper Settings
CPU Daughter Board (J1 Jumper)

Model 5/xxx CPU Daughter Board (Jumper J1)


J1 or J4 Jumper, Model 5/xxx
Bank	Jumper Setting
0	Standard boot setting (AlphaServer 1000 systems)
1	Standard boot setting (AlphaServer 1000A systems)
2	Mini-console setting: Internal use only
3	SROM CacheTest: backup cache test
4	SROM BCacheTest: backup cache and memory test
5	SROM memTest: memory test with backup and data cache disabled
6	SROM memTestCacheOn: memory test with backup and data cache enabled
7	Fail-Safe Loader setting: selects fail-safe loader firmware


CPU Daughter Board (5/xxx), Jumper J4

Default Jumper Settings
CPU Daughter Board (J4 Jumper)

Model 5/xxx CPU Daughter Board (Jumper J4)