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


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/diagnostic displays 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.


Power Problems

Diagnostic Flow for Power Problems

AlphaServer 2100A (BA740-B9 Pedestal Enclosure)

AlphaServer 2100A RM/CAB (BA744-A9 Rackmount Enclosure)


Power Problems

Troubleshooting
Power Problems

AlphaServer 2000  (BA720 Pedestal Enclosure)

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


Power Supply Cable Connections (BA720 Enclosure)


Power Supply Configuration Rules (BA720)

Troubleshooting
Power Problems

Power Supply Configuration Rules (BA720 Enclosure)

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

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

Power supply modes of operation:

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

      One CPU

      Two memory modules

      One diskette drive

      Two removable drives

      Eight 3.5-inch StorageWorks hard disks

      Ten I/O slots

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

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

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

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

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

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

 36 A or less of 3.3 V power

 52 A or less of 5.0 V power

 11 A or less of +12.0 V power

 0.2 A or less of -12.0 V power

 0.2 A or less of -5.0 V power

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

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

 Install a second power supply (H7845-AA).

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


Power Problems

Troubleshooting
Power Problems

AlphaServer 2100A (BA740-B9 Pedestal Enclosure)

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


Power Supply Configuration Rules (BA740)

Troubleshooting
Power Problems

Power Supply Configuration Rules (BA740-B9 Enclosure)

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

Power supply modes of operation:

1.	Single power supply---Supports entry-level systems, such as a  system with:

 	Two CPUs

One memory module

One floppy drive and one CD-ROM drive

One internal StorageWorks shelf with eight 3.5-in drives

Up to eight PCI/EISA options.

2.	Dual Power Supply (redundant mode)---Provides redundant power (n + 1) for entry-level systems and moderately configured systems, such as the system configuration listed above.

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

The redundant power jumper (W1) on the system backplane must be installed to activate redundant mode power.

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

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

 602 watts DC output power or less

 39 A or less of 3.3 V power

 62 A or less of 5.1 V power

 12.5 A or less of +12 V power

 1.0 A of -12 V power


Power Problems

Troubleshooting
Power Problems

AlphaServer 2100A RM/CAB (BA744-A9 Rackmount Enclosure)

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


AC OK LED, BA740 Enclosure

Power Supply LEDs (BA740-B9) Enclosure

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


Problems Getting to Console Mode

Troubleshooting
No Access to Console Mode

Diagnostic Flow for Problems Getting to Console Mode

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


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 initializing drivers or running power-up diagnostics.

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

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

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

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

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

A hardware or power failure, or accidental power down during a firmware upgrade

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

A driver error at power-up

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

Fail-Safe Loader Functions

Activating the Fail-Safe Loader


Fail-Safe Loader Functions

From the FSL program, you can:

Update or load new console firmware

Edit the nvram file (using the edit command)

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

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

Note:  The nonvolatile file, nvram, is shipped from the factory with no contents.  The customer can use the edit command to create a customized script or command file that is executed as the last step of every power-up. Refer to the AlphaServer 2000/2100/2100A Firmware Reference Guide, EK-AXPFW-RM.

To initialize all available drivers and boot firmware, enter the following commands.  Substitute the name of the update file for the variable update_file.

ash> init -driver 6

ash> boot update_file


Activating the Fail-Safe Loader

Troubleshooting
No Access to Console Mode

Activating the Fail-Safe Loader

Caution:  If you have manually activated the FSL by setting the FSL enable switch on the system backplane (pedestal systems) or PCI/EISA backplane (rackmount systems), you must set the FSL enable switch to off  before performing the firmware update.

When you perform a system upgrade, such as replacing existing CPUs with faster CPUs, or replace a system backplane (pedestal systems) or PCI/EISA backplane (rackmount systems), you should update the fail-safe loader.  This is to ensure that the FSL will support the new CPUs installed during the upgrade, or in the case of replacing a backplane, to load the FSL console, which is not preloaded on the replacement backplanes.

Instructions on updating the FSL are provided with system upgrade kits and with replacement backplanes.

To activate the FSL:

1.	Make sure the system is off and locate the two FSL switches on the backplane (system backplane) for pedestal systems; (PCI/EISA backplane) for rackmount systems.

2.	Using a small flat implement, set the FSL enable switch to ON.  The default is OFF.

3.	Turn on the system.

4.	Use the FSL program, ash>, to update or load new console firmware, edit the nvram file, set environment variables, or initialize phase 6 drivers.

5.	When you have finished, power down and remove the FSL enable switch to OFF.


Fail-Safe Loader Switches  (BA470-B9)

Fail-Safe Loader Switches (BA740-B9 Pedestal Enclosure)

FSL Enable	Selects FSL console firmware when set to ON.
FSL Console Update	Allows writes to the fail-safe loader when set to ON.  Used to update the fail-safe loader console firmware.  When updating the FSL console, the FSL enable switch should be set to OFF.


Fail-Safe Loader Switches (BA744-A9)

Fail-Safe Loader Switches (BA744-A9 Rackmount Enclosure)

FSL Enable	Selects FSL console firmware when set to ON.
FSL Console Update	Allows writes to the fail-safe loader when set to ON.  Used to update the fail-safe loader console firmware.  When updating the FSL console, the FSL enable switch should be set to OFF.


Fail-Safe Loader Jumper (BA720)

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

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


Console Event Log

Troubleshooting
Console-Reported Failures

Console Event Log

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

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 abbreviated console event logs that contain standard error messages:

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

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

3.	The third indicates a failing memory module, MEM0.

P00>>> more el

starting console on CPU 0

initialized idle PCB

initializing semaphores

initializing heap

.

.

.

CPU 0 speed is 5.26 ns (190MHz)

access NVRAM

entering idle loop

Starting Memory Diagnostics

.

.

.

initializing keyboard

** no mouse interrupts received **   (1)

.

.

.

Change mode to Internal loopback.

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

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

.

.

.

Change to Normal Operating Mode.

P00>>>

P00>>> cat el

starting console on CPU 0

initialized idle PCB

initializing semaphores

.

.

.

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

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

Failing address:     00000020

Bank Number:         0

ASIC ID:             1

Error Type:          0

Error Syndrome:      00000710

.

.

.

P00>>>


Boot Problems

Troubleshooting
Boot Failures

Diagnostic Flow for Boot Problems

Symptom	Action
System cannot find boot device.	Check system configuration for correct device parameters (node ID, device name, and so on).  For Digital UNIX and OpenVMS:      show config      show device For Windows NT:      Display hardware configuration      Set default variables Check the system configuration for correct environment variable settings.  For Digital UNIX and OpenVMS:     auto_action     bootdef_dev     boot_osflags     os_type For problems booting over a network, check the ew*0_protocols or er*0_protocols environment variable settings: Systems booting from a 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.	Check that the Halt button is not set to in (depressed). If bugcheck errors are generated while attempting to boot from an EISA device on systems running OpenVMS V6.1 or earlier, make sure that the bus_probe_algorithm environment variable is set to old. 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. Run device tests to check that boot device is operating.


Operating System Reported Problems

Troubleshooting
Operating System-Reported Failures

Diagnostic Flow for Errors Reported by the Operating System

Symptom	Action
System is hung or has crashed.	Examine the crash dump file.   Refer to OpenVMS 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. Use the show error command to examine error information contained in serial control bus EEPROMs (console environment error log).
Errors have been logged and the operating system is up.	Examine the operating system error log files to isolate the problem.   If the problem occurs intermittently, run an operating system exerciser, such as DEC VET, to stress the system. Refer to the DEC Verifier and Exerciser Tool User's Guide (AA-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.

Fixed-Media Troubleshooting Table

Removable-Media Troubleshooting Table


Fixed-Media Mass Storage Troubleshooting Table

Troubleshooting
Console-Reported Failures

Fixed-Media Mass Storage Troubleshooting Table

Problem	Symptom	Corrective Action
Drive failure	Fault LED for drive is on (steady).	Replace drive.
Duplicate SCSI IDs	Drives with duplicate SCSI IDs are missing from the show config display	Correct drive  SCSI IDs.
SCSI ID set to 7 (reserved for host ID)	Valid drives are missing from the show config display. One drive may appear seven times on the configuration screen display.	Correct SCSI IDs.
Duplicate host IDs on a shared bus	Valid drives are missing from the show config display. One drive may appear seven times on the configuration screen display.	Change host ID through the pk*0_host_id environment variable, using set pk*0_host_id for systems running OpenVMS or Digital UNIX (SRM console).   For systems running Windows NT (ARC console), choose Set default configuration in the Setup Menu.
Extra terminator	Devices produce errors or device IDs are dropped.	Check that bus is terminated only at beginning and end.  Remove unnecessary terminators.
PCI or EISA storage adapter option failure	Problems persist after eliminating the above problem sources.	Replace storage adapter module.

Troubleshooting tips for AlphaServer systems using the StorageWorks RAID Array 200 Subsystem.  The RAID subsystem includes either the SWXCR-Ex (KZESC-xx) or the SWXCR-Px (KZPSC-zz) PCI backplane RAID controller.


Power-Up Sequence

Troubleshooting
Console-Reported Failures

Power-Up Sequence

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

The power-up sequence includes the following:

Power supply power-up:

AC power-up

DC power-up

Two sets of power-on diagnostics:

Serial ROM diagnostics

Console firmware-based diagnostics

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


AC Power-Up Sequence

Troubleshooting
Console-Reported Failures

AC Power-Up Sequence

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

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

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

For pedestal  enclosures, the AC OK LED is illuminated when AC power is applied.

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

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


DC Power-Up Sequence

Troubleshooting
Console-Reported Failures

DC Power-Up Sequence

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

operator control panel.

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

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

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

3.	With a POK_H condition established and DC voltages stabilized, the power supply delivers a DCOK_H signal to the backplane.

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

Redundant:	POK_H = PS1_POK_H or PS2_POK_H

       DCOK_H = PS1_DCOK_H or PS2_DCOK_H

Full:	POK_H = PS1_POK_H and PS2_POK_H

       DCOK_H = PS1_DCOK_H and PS2_DCOK_H

For pedestal systems, redundant power jumper (W1) on the system backplane controls the mode of power supply operation.

For rackmount systems, redundant power jumper (W1) on the PCI/EISA backplane controls the mode of power supply operation.

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


Power Supply Mode Jumper (W1)- BA740-B9

Redundant Power Jumper (W1) on the System Backplane (BA740-B9 Pedestal Enclosure)

Redundant power (W1)	When installed, dual power supplies operate in redundant mode.


Power Supply Mode Jumper (W1)- BA744-A9

Redundant Power Jumper (W1) on the PCI/EISA Backplane (BA744-A9 Rackmount Enclosure)

Redundant power (W1)	When installed, dual power supplies operate in redundant mode.


Power Supply Mode Jumper (J3)- BA720

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

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


Firmware Power-Up Diagnostics

Troubleshooting
Power Problems

Firmware Power-Up Diagnostics

Serial-ROM Diagnostics

Console Firmware-Based Diagnostics

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

These tests are performed as two distinct sets of diagnostics:

Serial ROM diagnostics --These tests are loaded from the serial ROM located on the CPU module into the CPU's instruction cache (I-cache). They check the basic functionality of the system and load the console code from the FEPROM on the system backplane (pedestal systems) or PCI/EISA backplane (rackmount systems) into system memory.

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

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

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


Serial ROM Diagnostics

Troubleshooting
Power Problems

Serial ROM Diagnostics

The serial ROM diagnostics are loaded from the serial ROM located on the CPU module into the CPU's instruction cache (I-cache).  They check the basic functionality of the system and load the console code from the FEPROM on the system backplane (pedestal systems) or PCI/EISA backplane (rackmount systems) into system memory.

Failures during these tests are indicted by the power-up/diagnostic display on the operator control panel.  Diagnostic test and exerciser failures are also logged in EEPROM as TDD error logs via the serial control bus for CPU, memory, and system backplane. Serial ROM diagnostics test the system in the following order:

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

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

3.	Test the system bus to PCI bus bridge and system bus to EISA bus bridge. If the PCI bridge fail, or EISA bridge fail, an I/O failure is indicated on the power-up/diagnostic display on the OCP.  The power-up tests continue despite these errors.

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

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

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

6.	Check the access to the FEPROMs on the system backplane (pedestal systems) or PCI/EISA backplane (rackmount systems).

7.	The SRM console program is loaded into memory from the FEPROM on the systems backplane (pedestal systems) or PCI/EISA backplane (rackmount systems).  A checksum test is executed for the console image.  If the checksum test fails, the fail-safe loader (FSL) is automatically loaded into memory and the system displays the FSL prompt, ash>.

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

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


Console Firmware-Based Diagnostics

Troubleshooting
Power Problems

Console Firmware-Based Diagnostics

Console firmware-based tests are executed once control is passed to the console code in memory.  They test the core system, including all boot  path devices.

Failures during these tests are reported to the console terminal via the power-up screen or console event log.  Diagnostic test and exerciser failures are also logged in EEPROM as TDD or SDD error logs via the serial control bus for CPU, memory, and system backplane. Console firmware-based tests check the system in the following order:

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

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

Steps 3--6 may be completed in parallel.

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

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

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

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

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

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

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


Removable-Media Mass Storage Troubleshooting Table

Troubleshooting
Console-Reported Failures

Removable-Media Mass Storage Troubleshooting Table

Problem	Symptom	Corrective Action
Drive failure	Fault LED for drive is on (steady).	Replace drive.
Duplicate SCSI IDs	Drives with duplicate SCSI IDs are missing from the show config display.	Correct SCSI IDs.
SCSI ID set to 7 (reserved for host ID)	Valid drives are missing from the show config display. One drive may appear seven times on the show config display.	Correct SCSI IDs
Duplicate host IDs on a shared bus	Valid drives are missing from the show config display. One drive may appear seven times on the configuration screen display.	Change host ID through the pk*0_host_id environment variable, using set pk*0_host_id for systems running OpenVMS or Digital UNIX (SRM console).   For systems running Windows NT (ARC console), choose Set default configuration in the Setup Menu.
Missing or loose cables.	Activity LEDs do not come on.  Drive missing from the show config display.	Remove device and inspect cable connections.
Missing internal terminator.	Read/write errors in console event log; storage adapter port may fail.	Check that the cable terminator (12-36929-01) is installed at the end of the SCSI bus cable.
Extra terminator.	Devices produce errors or device Ids are dropped.	Check that cable terminator (12-36929-01) is removed if bus cable is connected to the internal StorageWorks shelf.
Backplane  failure	Problems persist after eliminating the above problem sources.	Replace the systems backplane (pedestal systems); PCI/EISA backplane (rackmount systems).


Troubleshooting Table for Console Reported Problems

Troubleshooting
Console-Reported Failures

Diagnostic Flow for Problems Reported by the Console Program

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

More information on firmware power-up diagnostics


EISA Bus Problems

Troubleshooting
Console-Reported Failures

EISA Bus Problems Indicated at Power-Up

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

EISA Configuration Error. Run the EISA Configuration Utility.

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

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

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


Additional EISA Troubleshooting Tips

Troubleshooting
Console-Reported Failures

Additional EISA Troubleshooting Tips

The following tips can aid in isolating EISA bus problems.

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

Be sure you run the correct version of ECU for the operating system.  For Windows NT, use the 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 systems.  Some CFG files call overlay files that are not required on this system or may reference inappropriate system resources, for example, BIOS addresses.  Contact the option vender to obtain the proper CFG file.

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

Systems running Windows NT can assign shared interrupt lines (IRQs).   Digital UNIX and OpenVMS do not allow shared interrupts.

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

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

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

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


PCI Problems at Power-Up

Troubleshooting
Console-Reported Failures

PCI Bus Problems Indicated at Power-Up

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

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


Additional PCI Troubleshooting Tips

Troubleshooting
Console-Reported Failures

Additional PCI Troubleshooting Tips

AlphaServer 2100A systems have a PCI-to-PCI bridge (DECchip 21050) on the system backplane.

Physical PCI slots 4, 5, 6, and 7 (primary PCI) are located before the bridge.

Physical PCI slots 0, 1, 2, and 3 (secondary PCI) are located behind the bridge.

PCI options that also contain a PCI-to-PCI bridge must be installed on the primary PCI bus, slots 4, 5, 6, or 7.  Refer to the following documents for restrictions on specific PCI options:

AlphaServer 2100A Hardware Release Notes---Shipped with the system.

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

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

http://www.service.digital.com/alpha/server/as2100a/docs.html


Interpreting Operator Control Panel Display Messages

Troubleshooting
No Access to Console Mode

Interpreting Operator Control Panel Power-Up Display

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

Message	Meaning
TEST	Displayed while the system performs diagnostic tests and exercisers.  The type of module under test, its slot number, and the currently executing EV4 countdown number or EV5 countdown number are also displayed.
NO MEM INSTALLED	Displayed if you power up with no memory installed.
FAIL module_type	If an error is detected in the CPU, memory, or I/O, a failure message is displayed and the Halt button LED lights for a few seconds.  The error is logged to the appropriate module via the serial control bus.  In nearly all cases, the power-up tests continue. The module_type and slot number for the field replaceable unit (FRU) that failed, along with the countdown number that detected the error, are also displayed. Module types and slot numbers: CPU_nn--CPU module (0--3) MEM_nn--Memory module (0--3) I/O_0--System backplane
CPU STATUS	Summary of CPU testing --The status of each CPU, starting with CPU0, is displayed: "P"--CPU passed "F"--CPU failed "--"--CPU not present
STARTING CPU #	The console is starting the primary CPU.
CONSOLE STARTED	The console has been unloaded from flash ROM and has assumed control of the system.
TEST MEM BANK #	The console is testing memory.
PROBE I/O SUBSYS	The console is checking the PCI and EISA bridges.
SYSTEM RESET	The Reset button has been pressed.
Model n/nnn	When the system is under operating system control, the CPU variant (n) and the approximate CPU speed (nnn) are displayed unless you supply your own text using the ocp_text environment variable.
Additional EV5-Only Processor OCP Messages
21164 TIMEOUT	An Alpha 21164 microprocessor IBOX time-out occurred.
3.3V/CLOCK FAIL	A voltage or clock failure occurred on the CPU module.
MEM_nn NVR ERROR	A checksum error occurred in the memory EEROM.


SIMM Note

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


Isolating Failing SIMMs

Troubleshooting
Failing SIMMs Reported by OCP Power-Up Display

Isolating Failing SIMMs

Using the Memory Data Bits in Error Table

AlphaServer 2000 Memory Module Layout

Memory Data Bits in Error and Corresponding SIMM Positions

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


Using the Memory Data Bits in Error Table

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

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

FAIL MEM_00 01

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

FAIL MEM_00 1718

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

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


Memory Module Layout

AlphaServer 2000 Memory Module (Carrier) Layout


EV4 Serial ROM Countdown Description and Field Replaceable Units

Troubleshooting
No Access to Console Mode

EV4 Serial ROM Power-Up Countdown Description and Field Replaceable Units (FRUs)

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


EV5 Serial ROM Countdown Description and Field Replaceable Units

Troubleshooting
No Access to Console Mode

EV5 Serial ROM Power-Up Countdown Description and Field Replaceable Units (FRUs)

Countdown Number	Description	Likely FRU
CPU0  CPU1  CPU2  CPU3
F8    F9    A       FB	Serial control bus read error	CPU
F4    F5    F6     F7	EEROM Checksum error	CPU
F0    F1    F2     F3	EV5 IBOX timeout	CPU
EC   ED   EE    EF	DC_OK Fail	CPU
D4    D5   D6    D7	No memory present	Memory is missing
D0    D1   D2    D3	Memory EEROM checksum error	MEM
CC   CD   CE   CF	CPU disabled	CPU
C8    C9   CA   CB	EV5 BIST failed	CPU
C4    C5   C6   C7	EV5 BIST errors	CPU
BC   BD   BE   BF	652/654 power-on & run	Non-specific/Status message
B8    B9   BA   BB	Sent sync byte	Non-specific/Status message
B4   B5    B6   B7	Received sync byte	Non-specific/Status message
60   61     62   63	B-cache init	CPU
5C  5D    5E   5F	S-cache data march test	CPU
58   59     5A   5B	S-cache TAG march test	CPU
54   55     56    57	B-cache data march test	CPU
50   51     52    53	B-cache TAG march test	CPU
4C  4D    4E    4F	B-cache DT-TAG test	CPU
48   49    4A    4B	System bus, PCI, EISA test	CPU or MBD Note
44   45    46     47	S-cache, B-cache, and rattler init	CPU
40   41    42     43	End of initial test	Non-specific/Status message
28  [29]  [2A]   [2B]	Memory test bank 0	MEM
24  [25]  [26]   [27]	Memory test bank 1	MEM
20  [21]  [22]   [23]	Memory test bank 2	MEM
1C [1D]  [1E]  [1F]	Memory test bank 3	MEM
18  [19]   [1A]  [1B]	PCI bridge test	MBD
14  [15]   [16]  [17]	End of memory/bridge test	Non-specific/Status message
--    11      12    13	Spin on CPU PMBR	Non-specific/Status message
0C  [0D]   [0E]  [0F]	Start ESC config	MBD
08   [09]   [0A]  [0B]	End ESC config & start FEPROM unload	MBD
04   [05]   [06]  [07]	End of FEPROM unload & start checksum	MBD
00   [01]   [02]  [03]	End of checksum & jump to console	MBD


Test Number 79 and show error Command

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

If no error is logged for test number 7, the system backplane is the likely module at fault.

For rackmount systems, which have a system bus backplane and PCI/EISA backplane, the PCI/EISA backplane, which contains more components is more likely to fail than the systems bus backplane that contains the T3 (system bus-to-PCI-bus bridge chip).


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 [-default] val

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


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


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


Startup Action -- Description

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

Whenever you change the value of this environment variable, you must initialize the systems to put the new setting into effect.  To initialize the system, enter the init command.


Startup Action - Example

Troubleshooting
Boot Failures

Example

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

P00>>> show auto_action

auto_action	halt

P00>>> set auto_action boot

P00>>> init

.

.

.

P00>>> 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.  Use 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 setting 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.

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.

P00>>> set bootdef_dev dka0

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

P00>>> set bootdef_dev dub0,dka0

P00>>> 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	Load operating system software from the specified boot device (autoboot). Boot to multi-user mode.
i	Prompt for the name of a file to load and other options (boot interactively). Boot to single user mode.
s	Stop in single-user mode. Boots /vmunix to single-user mode and stops at the # (root) prompt.
D	Full dump, implies "s" as well. By default, if Digital UNIX crashes, it completes a partial memory dump. Specifying "D" forces a full dump at system crash.


Root Number Settings (OpenVMS)

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

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


Boot Flags (OpenVMS)

Possible boot flags settings and their meanings for OpenVMS systems are:

Flag Setting	Bit Number	Meaning
1	0	Bootstrap conversationally (enables you to modify SYSGEN parameters in SYSBOOT).
2	1	Map XDELTA to running system.
4	2	Stop at initial system breakpoint.
8	3	Perform diagnostic breakpoints.
10	4	Stop at the bootstrap breakpoints.
20	5	Omit header from secondary bootstrap image.
80	7	Prompt for the name of the secondary bootstrap file.
100	8	Halt before secondary bootstrap.
10000	16	Display debug messages during booting.
20000	17	Display user messages during booting.

Note:  You can specify multiple boot flags by adding the flag values together (logical Oring).  For example, the flag value 10080 executes both 80 and 10000 flag settings.


Boot Flags -- Description

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

To change the boot flags for the current boot only, you can use boot 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, boot_flags.


Default Boot Flags - Example

Troubleshooting
Boot Failures

Example 1 -- Digital UNIX

The boot flags are set to autoboot:

P00>>> set boot_osflags a

Example 2-- OpenVMS

The root number is set to 2 and boot flags is set to 1.  With this setting, the system will boot from root directory SYS2.SYSEXE to the SYSBOOT prompt.

P00>>> set boot_osflags 2,1

Example 3 -- OpenVMS

The root_number is set to 0 and boot_flags is set to 80.  With this setting, the operator will be prompted for the name of the secondary bootstrap file.

P00>>> set boot_osflags 0,80


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

In the following 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.

>>> show os_type

os_type            vms

>>> set os_type nt

>>> init


os type	Description
Digital UNIX	Sets the default operating system to Digital UNIX; starts SRM firmware
OpenVMS	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 that will be started whenever the system powers up, is halted or restarted, or the operating system 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 or OSF, the system starts the SRM firmware, and Digital UNIX is the default operating system.

If os_type is set to NT, the system 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.

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.

P00>>> set pkb0_host_id 6

P00>>> init

   .

   .

   .

P00>>> show pkb0_host_id

pkb0_host_id 	6


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


Controller Host Bus Node ID --- Description

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

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

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

To list the controllers on your system, enter the show device command.  SCSI devices being with the letters pk, for example pka0.  The third letter is the adapter ID for the controller.

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


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

Name	Description
multi(0)key(0)keyboard(0) multi(0)serial(0) multi(0)serial(1)	The multi() devices are located on the system module. These devices include the keyboard port and the serial line ports.
eisa(0)video(0)monitor(0) eisa(0)disk(0)fdisk(0)	The eisa() devices are provided by devices on the EISA bus. These devices include the monitor and the floppy drive.
scsi(0)disk(0)rdisk(0) scsi(0)cdrom(5)fdisk(0)	The scsi() devices are SCSI disk or CD-ROM devices. These examples represent SCSI devices on SCSI bus A. The disk drive is set to SCSI ID 0 and the CD-ROM drive is set to SCSI ID 5. Both 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:  The Available boot 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.

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	21164
Processor Revision	2.2
System Revision	0x0
Processor Speed	250.00 Mhz
Physical Memory	512 MB

Extended Firmware Information:

  Version 4.43 951101.1202

  NVRAM Environment Usage: 52%

     (540 of 1024 bytes)

Video Option detected:

  24 Plane Frame Buffer video card: ZLXp-E2

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(1)rdisk(0)	(RAW)	DEC RZ28 (C) DEC007C
scsi(0)disk(2)rdisk(0)	(RAW)	DEC RZ28 (C) DECD41C
scsi(0)disk(3)rdisk(0)	(RAW)	DEC RZ28 (C) DEC0006
**scsi(0)tape(5)tape(0)		DEC TLZ09 (C) DEC0491
scsi(0)cdrom(6)fdisk(0)	Removable	DEC RRD45 (C) DEC 108
scsi(1)disk(8)rdisk(0)	(2 Partitions)	MYLEX CAC960
scsi(1)disk(9)rdisk(0)	(RAW)	MYLEX DAC960
scsi(1)disk(10)rdisk(0)	(RAW)	MYLEX DAC960

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	0	0	1011	2	23	22	Ethernet
0	1	0	1000	1	1	21	SCSI
0	2	0	8086	3	3	0	EISA bridge
0	7	0	1011	4	3	24	Video card

Press any key to continue...

12/20/1995  9:06:23 AM

EISA slot information:

Slot	Device	Identifier
0	Other	DEC2A01
4	Display	PHI8041
6	Unknown	ADP0001
7	Disk	MLX0075
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	When set to the default value (FALSE), disables parity checking on the PCI bus in order to prevent machine check errors that can occur if the PCI device has not properly set the parity on the bus.  Also allows the peripheral devices that do not fully conform to the PCI specification to be used without generating parity errors.
FLOPPY	The capacity of the default floppy drive, either 1 (1.2 MB), 2 (1.44 MB), or 3 (2.88 MB).
FLOPPY2	The capacity of an optional second floppy drive, either N (not installed), 1, 2, or 3.
FWSEARCHPATH	The search path used by the ARC firmware and other programs to locate particular files. The default value is the same as the SYSTEMPARTITION environment variable value.
KEYBOARDTYPE	The keyboard language. The default is U.S. (English).
TIMEZONE	The time zone in which the system is located. This variable accepts ISO/IEC9945-1 (POSIX) standard values.
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 (CPU and memory), PCI bus, and EISA bus.  You can use the information in the display to identify target devices for commands such as boot and test, as well as to verify that the system sees all the devices that are installed.

The configuration display includes the following:

Core System Status

Hose 0, Bus 0 PCI

Hose 0, Bus 1, EISA

Hose 0, Bus 2, PCI

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


show config

Core System Status

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


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 0--1 = Reserved

Slot 2 = PCI to EISA bridge chip

Slot 3 = PCI to PCI bridge chip

Slot 2 = EISA to PCI bridge chip

Slots 4--5 = Reserved

Slots 6-9 = Correspond to physical PCI card cage slots on the primary PCI bus: Slot 6 = PCI4

Slot 7 = PCI5

Slot 8 = PCI6

Slot 9 = PCI7

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


show config

Hose 0, Bus 1, EISA

All controllers on Hose 0, Bus 1 of the EISA bus. The logical slot numbers in the left column of the display correspond to physical EISA card cage slots 1--3.

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


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, 2--5 = Reserved

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

Slots 6--9 = Correspond to physical PCI card cage slots on the secondary PCI bus:

    Slot 6 = PCI0

Slot 7 = PCI1

Slot 8 = PCI2

Slot 9 = PCI3

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


show config - Example

Troubleshooting
Boot Failures

Example

P00>>> show config

                  Digital Equipment Corporation

                      AlphaServer 2100A 5/300

SRM Console T4.3-134      VMS PALcode V1.15-3, OSF PALcode X1.18-2

Component       Status  Module ID

CPU 0           P       B2020-BA DECchip (tm) 21164-1

CPU 1           P       B2020-BA DECchip (tm) 21164-1

Memory 0        P       B2021-CA  128 MB

Memory 1        P       B2021-CA  128 MB

I/O                     B22222-AA

                        dva0.0.0.1000.1      RX26

 Slot Option            Hose 0, Bus 0, PCI

  2  Intel 82375EB    Bridge to Bus 1, EISA

  3  DECchip 21050-AA   Bridge to Bus 2, PCI

  7  DECchip 21050-AA            Bridge to Bus 3, PCI

  9  S3 Trio64/Trio32

Slot Option            Hose 0, Bus 1, EISA

  1  DEC4220

Slot Option            Hose 0, Bus 2, PCI

  1  NRC  53C810        pka0.7.0.2001.0      SCSI Bus ID 7

                        dka0.0.0.2100.0      RZ28

                        dka600.6.0.2001.0    RRD43

                        mka400.4.0.2001.0    TLZ06

                        mka500.5.0.2001.0    TZK11

Slot Option            Hose 0, Bus 3, PCI

  0  DECchip 21040-AA   ewa0.0.0.3000.0      08-002B-E4-AE-A4

                        pkb0.7.0.3001.0      SCSI Bus ID 7

                        pkb0.0.0.3001.0      RZ28

                        pkb100.1.0.3001.0    RZ28

                        pkb200.2.0.3001.0    RZ26L

P00>>>


show device

Troubleshooting
Boot Failures

show device

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

Driver ID

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

dka0.0.0.2001.0               DKA0                          RZ28   435E

dka100.1.0.2001.0             DKA100                        RZ28   435E

dka600.6.0.2001.0             DVKA600                       RRD43  1084

dka0.0.0.1000.0               DVA                           RZ26

mka500.5.0.2001.0             MKA500                        TLZK11 00A1

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

pka0.7.0.2001.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 card cage physical slot numbers (1-3)

For PCI options

Slot 0 = Reserved

Slot 1 = SCSI controller on system backplane

Slot 2 = PCI to EISA bridge chip

Slot 3 = PCI to PCI bridge chip

Slots 6--9 = (Primary bus) Correspond to physical PCI card cage slots:

 	PCI4, PCI5, PCI6, and PCI7.

Slots 6--9 = (Secondary bus) Correspond to physical PCI card cage slots:

 	PCI10, PCI11, PCI12, and PCI13.


Multiprocessor Failover

Troubleshooting
Power Problems

Multiprocessor Failover

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

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

If any of the CPUs fail during power-up, the halt button LED on the operator control panel lights for a few seconds and the CPU status message on the power-up/diagnostic display indicates which CPU failed.

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

power-up tests.

show fru

show error

show config

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


SWXCR-XX controller

Troubleshooting
Console-Reported Failures

Troubleshooting 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 200 Subsystems Controller Installation and Standalone Utility Users Guide , EK-SWRA2-IG. Reminder: several physical disks can be grouped as a single logical DRAn device.
Drives on the controller power up with the amber Fault light on.	Whenever you move drives onto or off the controller, run the RAID configuration to set up the drives and logical units.   Follow the instructions in the StorageWorks RAID Array 200 Subsystems Controller Installation and Standalone Utility Users Guide , EK-SWRA2-IG.
Cannot access disks connected to the RAID subsystem on Windows NT systems.	On Windows NT systems, disk 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 list the network devices on the system, enter the show device command.  The Ethernet controllers start with the letters "ew" or "er."  The third letter is the adapter ID for the specific 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	When both qualifiers are listed, the system attempts to use the mop protocol first, regardless of which protocol is listed first.  If not successful, it then attempts the bootp protocol.


Default Boot Flags - Example

Troubleshooting
Boot Failures

Example 1

The network protocol is set to mop.

P00>>> set ewa0_protocols mop

P00>>> show ewa0_protocols

ewa0_protocols          MOP

Example 2

The network protocol is set to bootp.

P00>>> set ewa0_protocols bootp

P00>>> show ewa0_protocols

ewa0_protocols          BOOTP

Example 3

The network protocol is set to mop or bootp.

P00>>> set ewa0_protocols bootp,mop

P00>>> show ewa0_protocols

ewa0_protocols          BOOTP,MOP


bus_probe_algorithm

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.

P00>>> set bus_probe_algorithm new

P00>>> init

 .

 .

 .

P00>>> show bus_probe_algorithm

 Bus_probe_algorithm      new


Console Port Configurations

Troubleshooting
No Access to Console Mode

Console Port Configurations

Power-up information is typically displayed on the systems 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.
com1_baud and com2_baud	Changes the baud rate of the COM1 or COM2 port.

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:

P00>>> set console serial

P00>>> init

 .

 .

 . !Now switch to the serial terminal.

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

P00>>> set console serial

P00>>> set tt_allow_login 1

P00>>> init

 .

 .

 .


set com1_baud or com2_baud

The com1_baud and com2_baud environment variables allow you to change the baud rate for the COM1 and COM2 serial ports.

Synopsis:

set com1_baud [baud_value]

set com2_baud [baud_value]

Baud Rate Values:

The baud rate values are 300, 600, 1200, 4800, 9600, 19200.

Note:  If you reset the baud rate, make sure the new setting is compatible with the baud rate setting for the terminal.

Example:

P00>>> set com1_baud 19200


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:

P00>>> show tga_sync_green

tga_sync_green   0

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

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


Setting Up a Serial Terminal to Run ECU

You can run the ECU from either a VGA-compatible graphics monitor or from a serial terminal (VT200 or higher, or equivalent).  Graphics is the default.  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.

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

P00>>> set console serial

P00>>> init

 .

 .

 .  !Now switch to the serial terminal.

P00>>> show console

console   serial


BA740-B9 Enclosure FRUs and Procedures

FRU List and Procedures

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

AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)---FRU Removal and Replacement


Removal and Replacement: Guidelines and Warnings, BA740-B9

Caution: Before opening or removing system panels:

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

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

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

Continue. . .


FRU List - BA740-B9

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

Part #	Description

Cables
17-03870-01	Fan/removable media cable (12-pin)
17-04299-01	Floppy drive cable (34-pin)
17-03868-01	Internal StorageWorks power cable (5-pin)
17-03869-01	OCP module cable (10-pin)
17-00083-15	Power cord
17-02784-03	Remote I/O cable (60-pin)
17-04193-01	SCSI removable-media cable (50-pin)
17-04180-01	SCSI StorageWorks cable (68-pin)
CPU Modules
B2020-AA	KN450 CPU module, 4/200
B2020-BA	KN455 CPU module, 4/233
B2024-AA	KN460 CPU module, 4/275
B2040-AB	KN470 CPU module, 5/250
B2040-BA	KN480 CPU module, 5/300
Fans
12-23609-09	4.5-Inch Fan
12-36202-02	6.75-Inch Fan
54-23260-01	Fan speed control board
I/O Modules
54-23151-01	Remote I/O module
Internal StorageWorks
RZnn - VW	StorageWorks disk drive
54-23343-01	Internal StorageWorks backplane
BA35X-ME  (54-23376-01)	Internal StorageWorks terminator
BA35X-MF  (54-23378-01)	Internal StorageWorks jumper
Memory Modules
B2021-BA	MS450-BA, 64MB, 80-ns memory module
B2021-CA	MS450-CA, 128MB, 80-ns memory module
B2022-CA	MS451-CA, 512MB, 80-ns memory module
B2022-DA	MS451-DA, 128MB, 80-ns memory module
B2022-FA	MS451-FA, 512MB, 80-ns memory module
Other Modules and Components
B2222-AA (54-24129-01)	System backplane
54-23180-01	OCP module
30-41274-01	Power supply
12-39309-01	Speaker
12-36437-03	Key for door
12-34165-02	Serial line loopback
17-04203-01	SCSI terminator
12-41296-01	Internal SCSI terminator
Removable Media
RRDnn -CA	CD-ROM drives
TLZnn -LG	Tape drives
TZKnn -LG	Tape drives
RXnn -AA	Floppy drive


System Backplane Removal, BA740-B9: Step 1

Removal and Replacement
System Backplane, AlphaServer 2100A (BA740-B9 Enclosure)

Step 1:  Remove modules and divider

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

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


System Backplane, Removal, BA740-B9: Step 2

Removal and Replacement
System Backplane, AlphaServer 2100A (BA740-B9 Enclosure)

Step 2:  Remove power supplies.

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


System Backplane, Removal, BA740-B9: Step 3

Removal and Replacement
System Backplane, AlphaServer 2100A (BA740-B9 Enclosure)

Step 3:  Detach cables and remove backplane.

When replacing backplane, install screws in order indicated.

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


System Backplane, Removal, BA740-B9: Step 4

Removal and Replacement
System Backplane, AlphaServer 2100A (BA740-B9 Enclosure)

Step 4:  Move NVRAM chip to new backplane and set the redundant power supply jumper.

Move the socketed NVRAM chip (position E49) to the replacement backplane and set the redundant power supply jumper (W1) to match previous setting.

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


System Backplane, Removal, BA740-B9: Step 5

Removal and Replacement
System Backplane, AlphaServer 2100A (BA740-B9 Enclosure)

Step 5:  Set the FSL enable switch to off; and set the FSL console update switch to on.

The replacement backplane ships with incomplete firmware.  The backplane contains no ARC console or fail-safe loader firmware.  After installing the backplane, you will need to update the firmware by invoking the Loadable Firmware Utility (LFU) from the CD-ROM, as described in Step 6.

FSL Enable	Selects FSL console firmware when set to ON.
FSL Console Update	Allows writes to the fail-safe loader when set to ON.  Used to update the fail-safe loader console firmware.
Redundant Power (W1)	When installed, dual power supplies operate in redundant mode.

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


System Backplane, Removal, BA740-B9: Step 6

Removal and Replacement
System Backplane, AlphaServer 2100A (BA740-B9 Enclosure)

Step 6:  After installing the system backplane, update the console firmware.

Power up with the FSL console update switch set to ON.  Invoke the LFU and update the firmware as described in the Mandatory AlphaServer 2xxx Flash ROM Update, EK-B2110-CL, shipped with the replacement backplane.

Note:  After completing the update, remember to power down and set the FSL console update switch to OFF.


Remote I/O Removal, BA740-B9

Remote I/O Module


OCP Cable Removal, BA740-B9

OCP Module Cable (10-pin)


SCSI StorageWorks Cable, Removal, BA740-B9

SCSI StorageWorks Cable (68-pin)


Floppy Cable Removal, BA740-B9

Floppy Drive Cable (34-pin)


SCSI Multinode Cable (50-pin) Removal, BA740-B9

SCSI Removable-Media Cable (50-pin)


Remote I/O Cable Removal, BA740-B9

Remote I/O Cable (60-pin)


OCP Module Removal, BA740-B9: Step 1

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

Step 1:  Detach OCP cable and remove OCP cover.

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


OCP Module Removal, BA740-B9: Step 2

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

Step 2:  Remove OCP module.


CPU Module Removal, BA740-B9: Step 1

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

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

Before replacing a CPU module, perform the following steps to verify which CPU is failing.  After installing a new CPU, repeat this procedure to ensure that the new CPU is working properly.

Step 1: Check for errors logged to the CPU.

Verify that errors have been logged through the serial control bus before replacing a CPU module.  Using the show fru  and show error console commands, you can determine if errors are logged for a bad CPU.

If an event is logged for any other test than test number 00, the CPU should be replaced.

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

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

Example

P00>>> show fru

                           Rev               Events logged

Slot   Option  Part#      Hw Sw  Serial#     SDD     TDD

  0    IO      B2222-AA   B2 0   NI53400096  00      00

  2    CPU0    B2020-AA   B2 10  KA426C0457  00      01

  3    CPU1    B2020-AA   B2 10  KA34509090  00      00

  4    MEM0    B2021-CA   A1 0   ML34398735  00      00

  7    MEM3    B2022-CA   A1 0   ML34100008  00      00

.

.

.

P00>>>

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

Example

P00>>> show error cpu0

CPU0 Module EEROM Event Log

Test Directed Errors

Entry: 0  Test Number: 02       Subtest Number: 02

Parameter 1: 00000000,00000010

Parameter 2: ffffffff,ffffffff

Parameter 3: fffffeff,ffffffff

CPU Event Counters

C3_CA_NOACK     0

.

.

.

C3_DT_PAR_E     0

C3_DT_PAR_O     0

B-Cache Correctable Errors

Entry   Syndrome        Offset L        Offset H        Count

No Entries Found

P00>>>

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


CPU Module Removal, BA740-B9: Step 2

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

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

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

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

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

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

module.

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

System Bus Card Cage

System Bus Configuration (according to number of CPUs)

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


System Bus Card Cage, BA740-B9

System Bus Card Cage


System Bus Configuration, B740-B9

System Bus Configurations


CPU Module Removal, BA740-B9: Step 3

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

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

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

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

Example

P00>>> show fru

                           Rev               Events logged

Slot   Option  Part#      Hw Sw  Serial#     SDD     TDD

  0    IO      B2222-AA   B2 0   NI53400096  00      00

  2    CPU0    B2020-AA   B2 10  KA426C0457  00      00

  3    CPU1    B2020-AA   B2 10  KA34509090  00      00

  4    MEM0    B2021-CA   A1 0   ML34398735  00      00

  7    MEM3    B2022-CA   A1 0   ML34100008  00      00

.

.

.

P00>>>


Memory Removal, BA740-B9

Memory Module

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

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

module.

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


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

Removal and Replacement
Fans and Fan Speed Control Board, AlphaServer 2100A (BA740-B9 Enclosure)

Step 1:  Remove fan assembly.

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


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

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

Step 2:  Remove fan component.

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


Fan/Removable media Cable Removal, BA740-B9

Fan/Removable Media Cable (12-pin)


Internal Storage Works Terminator and Jumper Removal, BA740-B9

Internal StorageWorks Terminator and Jumper


Removal - Internal Storage Works Drive, BA740-B9

StorageWorks Disk Drive

Note:  If the StorageWorks drives are plugged into a RAID 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 a RAID controller,

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


Floppy Drive Removal, BA740-B9

Floppy Drive


Removal - Internal Storage Works Power Cable, BA470-B9

Internal StorageWorks Power Cable (5-pin)


Floppy Cable Removal, BA740-B9

Speaker


Removable Media Devices, Removing, BA740-B9

Removable Media Drives (Tape and CD-ROM)


Power Cord Removal, BA740-B9

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

Power Cord


Power Cord Part Numbers

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

Power Cord Numbers

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


Storageworks Backplane Removal, BA740-B9: Step 1

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

Step 1:  Remove internal StorageWorks shelf.

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


Storageworks Backplane Removal, BA740-B9: Step 2

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

Step 2:  Remove internal StorageWorks backplane.


Power Supply Removal, BA740-B9

Power Supply

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


Door and Panel Removal, BA740-B9

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

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


Front/Left View, BA740-B9

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


Rear/Right View, BA740-B9

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


Removal and Replacement: Guidelines and Warnings, BA744-A9
Warning: Before accessing enclosure compartments:

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

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

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

Do not extend more than one slide assembly at a time, cabinet instability may result.

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

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

Continue. . .


FRU List - BA744-A9

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

Part #	Description

Cables
17-04085-01	Floppy drive cable (34-pin)
17-04013-01	Multinode fan/storage device cable (12-pin)
17-03971-01	OCP module cable (10-pin)
17-00083-51	Power cord 120V
17-00083-52	Power cord 240V (CAB systems)
17-04014-01	Power supply control cable assembly (24-pin to 15-pin)
17-04015-01	Power supply 12V cable assembly (16-pin to 8-pin)
17-02784-03	Remote I/O cable (60-pin)
17-04203-01	SCSI storage-media cable (50-pin)
CPU Modules
B2020-AA	KN450 CPU module, 4/200
B2020-BA	KN455 CPU module, 4/233
B2024-AA	KN460 CPU module, 4/275
B2040-AB	KN470 CPU module, 4/250
B2040-BA	KN480 CPU module, 4/300
Fans
12-23374-02 or 12-36202-02	6.75-Inch Fan
54-22615-01	Fan speed control board
I/O Modules
54-23151-01	Remote I/O module
Memory Modules
B2021-BA	MS450-BA, 64MB, 80-ns memory module
B2021-CA	MS450-CA, 128MB, 80-ns memory module
B2022-CA	MS451-CA, 512MB, 80-ns memory module
B2022-DA	MS451-DA, 128MB, 80-ns memory module
B2022-FA	MS451-FA, 512MB, 80-ns memory module
Other Modules and Components
54-23180-03	OCP module
30-41765-01	Power supply
12-39309-03	Speaker
54-24281-01	System bus backplane
54-24283-01	PCI/EISA bus backplane
09-11194-01	Key, 1/4-turn fastener
12-34165-02	Serial Line Loopback
17-04203-01	SCSI terminator
Removable Media
RRDnn -AA	CD-ROM drives
TLZnn -LG	Tape drives
TZKnn -LG	Tape drives
RXnn -AA	Floppy drive
Fixed Disk Drives
RZnn -E	Disk drive


System Backplane, Removal, BA744-A9: Step 1

Removal and Replacement
System Backplane/PCI/EISA Backplane, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

Step 1:  Remove all power supply cables from system backplane.

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

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

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


System Backplane, Removal, BA744-A9: Step 2

Removal and Replacement
System Backplane/PCI/EISA Backplane, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

Step 2:  Remove cable bracket from rear of system.

Cables can remain attached to the cable bracket.

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


System Backplane, Removal, BA744-A9: Step 3

Removal and Replacement
System Backplane/PCI/EISA Backplane, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

Step 3:  Remove enclosure from cabinet.

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

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


System Backplane, Removal, BA744-A9: Step 4 and Step 5

Removal and Replacement
System Backplane/PCI/EISA Backplane, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

Step 4:  Remove CPU and memory modules.

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

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

Remove any other cables that exit from the PCI/EISA bus compartment.  If you are going to replace the PCI/EISA backplane, remove all the modules from the compartment as well.

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


System Backplane, Removal, BA744-A9: Step 6

Removal and Replacement
System Backplane/PCI/EISA Backplane, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

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

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

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


System Backplane, Removal, BA744-A9: Step 7

Removal and Replacement
System Backplane/PCI/EISA Backplane, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

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

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


System Backplane, Removal, BA744-A9: Step 8

Removal and Replacement
System Backplane/PCI/EISA Backplane, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

Step 8:  Remove the four power bus bars.

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


System Backplane, Removal, BA744-A9: Step 9

Removal and Replacement
System Backplane/PCI/EISA Backplane, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

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

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


System Backplane, Removal, BA744-A9: Step 10

Removal and Replacement
System Backplane/PCI/EISA Backplane, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

Step 10:  Remove system bus backplane.

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

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


System Backplane, Removal, BA744-A9: Step 11

Removal and Replacement
System Backplane/PCI/EISA Backplane, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

Step 11:  Remove PCI/EISA daughter board (if required).

Note:  When replacing the backplane, install screws in order indicated.

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


System Backplane, Removal, BA744-A9: Step 12

Removal and Replacement
System Backplane/PCI/EISA Backplane, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

Step 12:  Move NVRAM chip to new backplane and set redundant power jumper.

Move the socketed NVRAM chip (position E47) to the replacement PCI/EISA backplane and set the redundant power jumper (W1) to match previous setting.

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


System Backplane, Removal, BA744-A9: Step 13

Removal and Replacement
System Backplane/PCI/EISA Backplane, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

Step 13:  Set the FSL enable switch to OFF; and the FSL console update switch to ON.

The replacement backplane ships with incomplete firmware.  The backplane contains no ARC console or fail-safe loader firmware.  After installing the backplane, you will need to update the firmware by invoking the Loadable Firmware Utility (LFU) from the CD-ROM, as described in Step 14.

FSL Enable	Selects FSL console firmware when set to ON.
FSL Console Update	Allows writes to the fail-safe loader when set to ON.  Used to update the fail-safe loader console firmware.
Redundant Power (W1)	When installed, dual power supplies operate in redundant mode.

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


System Backplane,  Removal, BA744-A9: Step 14

Removal and Replacement
System Backplane/PCI/EISA Backplane, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

Step 14:  After installing the PCI/EISA backplane, update the console firmware.

Power up with the FSL console update switch set to ON.  Invoke the LFU and update the firmware as described in the Mandatory AlphaServer 2xxx Flash ROM Update, EK-B2110-CL, shipped with the replacement backplane.

Note:  After completing the update, remember to power down and set the FSL console update switch to OFF.


Remote I/O Module Removal, BA744-A9: Step 1 & 2

Removal and Replacement
Remote I/O Module, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

Step 1: Remove screw at rear cutout.

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


OCP Cable Removal, BA744-A9

OCP Module Cable (10-pin)


Floppy Cable Removal, BA744-A9

Floppy Drive Cable (34-pin)


SCSI Storge-Media Cable (50-pin) Removal, BA744-A9

SCSI Storage-Media Cable (50-pin)


Remote I/O Cable Removal, BA744-A9

Remote I/O Cable (60-pin)


OCP Module Removal, BA744-A9

Removal and Replacement
OCP Module, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

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


CPU Module Removal, BA744-A9: Step 1

Removal and Replacement
CPU Module, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

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

Before replacing a CPU module, perform the following steps to verify which CPU is failing.  After installing a new CPU, repeat this procedure to ensure that the new CPU configuration is working properly.

Step 1: Check for errors logged to the CPU.

Verify that errors have been logged through the serial control bus before replacing a CPU module. Using the show fru and show error console commands, you can determine if errors are logged for a bad CPU.

If an event is logged for any test other than test number 00, the CPU should be replaced.

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

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

Example

P00>>> show fru

                           Rev               Events logged

Slot   Option  Part#      Hw Sw  Serial#     SDD     TDD

  0    IO      B2222-AA   B2 0   NI53400096  00      00

  2    CPU0    B2020-AA   B2 10  KA426C0457  00      01

  3    CPU1    B2020-AA   B2 10  KA34509090  00      00

  4    MEM0    B2021-CA   A1 0   ML34398735  00      00

  7    MEM3    B2022-CA   A1 0   ML34100008  00      00

.

.

.

P00>>>

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

Example

P00>>> show error cpu0

CPU0 Module EEROM Event Log

Test Directed Errors

Entry: 0  Test Number: 02       Subtest Number: 02

Parameter 1: 00000000,00000010

Parameter 2: ffffffff,ffffffff

Parameter 3: fffffeff,ffffffff

CPU Event Counters

C3_CA_NOACK     0

.

.

.

C3_DT_PAR_E     0

C3_DT_PAR_O     0

B-Cache Correctable Errors

Entry   Syndrome        Offset L        Offset H        Count

No Entries Found

P00>>>

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


CPU Module Removal, BA744-A9: Step 2

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

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

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

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

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

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

module.

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

System Bus Card Cage

System Bus Configuration (according to number of CPUs)

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


System Bus Card Cage, BA744-A9

System Bus Card Cage(BA744-A9)


System Bus Configurations, BA744-A9

System Bus Configurations (BA744-A9)


CPU Module Removal, BA744-A9: Step 3

Removal and Replacement
CPU Module, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

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

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

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

Example

P00>>> show fru

                           Rev               Events logged

Slot   Option  Part#      Hw Sw  Serial#     SDD     TDD

  0    IO      B2222-AA   B2 0   NI53400096  00      00

  2    CPU0    B2020-AA   B2 10  KA426C0457  00      00

  3    CPU1    B2020-AA   B2 10  KA34509090  00      00

  4    MEM0    B2021-CA   A1 0   ML34398735  00      00

  7    MEM3    B2022-CA   A1 0   ML34100008  00      00

.

.

.

P00>>>


Memory Module Removal, BA744-A9

Removal and Replacement
Memory Module, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

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

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

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

module.

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


Fans, Fan Speed Control Module Removal, BA744-A9: Step 1

Removal and Replacement
Fans, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

Step 1:  Unplug fans.

Step 2:  Remove fan assembly and replace failing fan.


Removal - Fan Speed Control Board, BA744-A9

Fan Speed Control Board


Removal - Multinode fan/storage device cable, BA744-A9

Multinode Fan/Storage Device Cable (12-pin to 6-pin)


Floppy Drive, BA744-A9

Floppy Drive


Speaker, BA744-A9

Speaker


Removable Media Devices, Removing, BA744-A9

Removable Media Drives (Tape and CD-ROM)

Note: RRDnn and TLZ0n drives use the set of bracket holes marked A. The TZK11 drive uses the set of bracket holes marked B.


Power Cord Removal, BA744-A9

Removal and Replacement
Power Cord, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

Power Cord


Power Cord Part Numbers, BA744-A9

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

Power Cord Numbers

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


Power Supply Removal, BA744-A9: Step 1 and Step 2

Removal and Replacement
Power Supply, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

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

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

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

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

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


Power Supply Removal, BA744-A9: Step 3

Removal and Replacement
Power Supply, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

Step 3:  Remove power supply.

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


Power Bus Bars and Connectors on System Backplane, BA744-A9

Power Bus Bars and Power Connectors on System Backplane


Accessing FRUs, BA744-A9: Step 1

Removal and Replacement
Accessing FRUs, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

Step 1:  Stabilize cabinet.

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

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

Example of Cabinet Stabilized with Leveling Feet and Stabilizing Bar

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


Accessing FRUs, BA744-A9: Step 2

Removal and Replacement
Accessing FRUs, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

Step 2:  Remove front panel.

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


Accessing FRUs, BA744-A9: Step 3

Removal and Replacement
Accessing FRUs, AlphaServer 2100A RM/CAB (BA744-A9 Enclosure)

Step 3:  Slide out rackmount system.

 Accessing the mass storage compartment.

 Accessing the PCI/EISA bus compartment.

 Accessing the system bus compartment.


Accessing the Mass Storage Compartment, BA744-A9

Accessing the Mass Storage Compartment

Note:  The mass storage compartment cover requires a number 1 Phillips screwdriver to loosen the 6 quarter-turn fasteners.


Accessing the PCI/EISA Compartment, BA744-A9

Accessing the PCI/EISA Compartment


Accessing the System Bus Compartment, BA744-A9

Accessing the System Bus Compartment


FRUs, Upper Compartments, BA744-A9

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


FRUs, Lower Compartments, BA744-A9

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


Power Supply Control Cable, BA744-A9

Power Supply Control Cable Assembly (15-pin to 24-pin)


Power Supply 12V Cable Assembly, BA744-A9

Power Supply 12V Cable Assembly (8-pin to 16-pin)


Disk Drives, BA744-A9

Disk Drives


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

AlphaServer 2100A 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).  If you are running Windows NT, you will need to switch consoles.

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

Acceptance Testing and Initialization


Acceptance Testing and Initialization

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

CPU modules

Memory modules

System backplane

PCI/EISA backplane (rackmount systems)

Storage devices

PCI or EISA options

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

2.  If you have added or moved an EISA or some ISA options, 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 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 Systems Diagnostics

Summary of Diagnostic and Related Commands

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


Command Reference --- sys_exer

Troubleshooting
ROM-Based Diagnostics (RBDs)

sys_exer

Synopsis

Exercises core system.  Runs tests concurrently.

Command

sys_exer ([lb])

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


sys_exer --- Description

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

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

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

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

Certain memory errors that are reported by the OCP may not be reported by the ROM-based 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:

P00>>> set auto_action halt

P00>>> init

 .

 .

 .

P00>>> sys_exer

P00>>> init

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


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


sys_exer - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example

P00>>> sys_exer

Exercising the Memory

Exercising the DK* Disks (read only)

Exercising the MK* Disks (read only)

Exercising the Floppy (read only)

Exercising the VGA (Alphanumeric Mode only)

Exercising the EWA0 network

Type init in order to boot the operating system

P00>>> show_status

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


Command Reference --- show error

Troubleshooting
ROM-Based Diagnostics (RBDs)

show error

Synopsis

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

Command

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

Memory Errors

CPU Errors


show error --- Description

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

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


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


Memory Error - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example -- Memory Errors

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

Correctable errors are indicated by event type 00.  If five or more correctable errors are logged for the same memory module, the specified module should be replaced.

For all unncorrectable errors, indicated by event types 01 and 10, you should replace the failing memory module.

P00>>> show error mem3

Test Directed Errors

No Entries Found

Symptom Directed Errors

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


CPU Error - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example -- CPU Errors

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

If an event is logged for any other test than test number 00, the CPU should be replace.  Event logs with just test number 00 do not indicate a bad CPU.  Test number 00 indicates that a CPU failover occurred sometime in the past.

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

P00>>> show error cpu0

CPU0 Module EEROM Event Log

Test Directed Errors

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

Parameter 2:  ffffffff,ffffffff

Parameter 3:  ffffffff,ffffffff

CPU Event Counters

C3_CA_NOACK     0

    .

    .

    .

C3_DT_PAR_E     0

C3_DT_PAR_O     0

B-Cache Correctable Errors

Entry    Syndrome    Offset L    Offset H     Count

No Entries Found

P00>>>


Test Number

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


Entry

Event log entry number.


Fail Address

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


Bits/Syndrome

First two failing bits (in hexadecimal) for uncorrectable errors; syndrome (in hexadecimal) for correctable errors.


Bank Number

The bank number of the failing DRAM.


ASIC Number

The asic chip that detected the error.


Source

The software or firmware that logged the error.

0	SROM

1	SRM firmware (RBDs)

2	UNIX

3	VMS

4	NT

5-7	Reserved


Event Type

00	Data correctable

01	Data uncorrectable

10	Data uncorrectable (first two bits logged)

11	Other (address and syndrome fields not valid)


Command Reference --- clear_error

Troubleshooting
ROM-Based Diagnostics (RBDs)

clear_error

Synopsis

Clears error information logged through the serial control bus.

Command

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

Example

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

P00>>> clear_error all

P00>>>


Command Reference --- exer_read

Troubleshooting
ROM-Based Diagnostics (RBDs)

exer_read

Synopsis

Test a disk by performing random reads.

Command

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

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


exer_read --- Description

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

The tests continue until one of the following conditions occurs:

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

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

3.	The specified time has elapsed.

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


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


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


exer_read - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example

P00>>> exer_read

failed to send command to pkc0.1.0.2.0

failed to send Read to dkc100.1.0.2.0

*** Hard Error - Error #5 -

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

*** End of Error

P00>>>


Command Reference --- memexer

Troubleshooting
ROM-Based Diagnostics (RBDs)

memexer

Synopsis

Exercises memory by running a specified number of memory tests.

Command

memexer [number]

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


memexer --- Description

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

in twice the backup cache size blocks for each pass.

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

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


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


memexer - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example with no errors.

P00>>> memexer 4

P00>>> show_status

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

P00>>>

Example with a memory compare error indicating a bad module.

P00>>> memexer 4

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

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

P00>>> kill diags

P00>>>


Command Reference --- memexer_mp

Troubleshooting
ROM-Based Diagnostics (RBDs)

memexer_mp

Synopsis

Tests memory in a multiprocessor system.

Command

memexer_mp [number]

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


memexer_mp -- Description

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

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

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


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


memexer_mp - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example

P00>>> memexer_mp 2

P00>>> show status

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

P00>>>


Command Reference --- nettest

Troubleshooting
ROM-Based Diagnostics (RBDs)

nettest

Synopsis

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

Command

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

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


nettest --- Description

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

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


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

Note:  The LANCE chip controller, era0, is not a supported boot device for AlphaServer 2100A systems.


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


nettest - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example -- Testing an Ethernet Port:

P00>>> nettest ewa0 -p 0 &

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

P00>>>kill_diags

P00>>>

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

1.  Create a list of nodes for which to send MOP loopback packets from port ewa0.  The following command place the node addresses (from the network database) into the file, lp_nodes_ewa0, in a format that the driver can read.

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

2. View the list nodes.

P00>>> cat ndbr/lp_nodes_ewa0

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

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

4. View the status of the test.

P00>>> show_status

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

5. Stop the testing.

P00>> kill_diags

P00>>


Command Reference --- net-s

Troubleshooting
ROM-Based Diagnostics (RBDs)

net -s

Synopsis

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

Command

net -s ewa0

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

P00>>>


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

P00>>> net -ic ewa0

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

P00>>>


Command Reference --- kill and kill_diags

Troubleshooting
ROM-Based Diagnostics (RBDs)

kill and kill_diags

Synopsis

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

Command

kill_diags

kill [PID . . . ]


kill --- Description

The kill command terminates a specified process or diagnostic.


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

P00>>>show_status

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


ID

Process ID.


Program

Program module name.


Device

Device under test.


Pass

Diagnostic pass count.


Hard/Soft

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


Bytes Written

Bytes successfully written by diagnostic.


Bytes Read

Bytes successfully read by diagnostic.


Exit

Do you want to exit this application?


Testing the System (test)

Console Firmware
ROM-Based Diagnostics (RBDs)

Testing the System (test)

Synopsis

Runs firmware diagnostics on the system.

Command

test ([lb])

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

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

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


Testing the system (test)- Example

Console Firmware
ROM-Based Diagnostics (RBDs)

Example 1

The system is tested, and the tests complete successfully.

P00>>> test

Testing the Memory

Testing the DK* Disks(read only)

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

file open failed for dkb600.6.0.2.1

No DR* Disks available for testing

Testing the MK* Tapes(read only)

Testing the DV* Floppy Disks(read only)

file open failed for dva0.0.0.0.1

Testing the VGA(Alphanumeric Mode only)

Testing the EW* Network

P00>>>

Example 2

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

P00>>> test

Testing the Memory

Testing the DK* Disks(read only)

No DR* Disks available for testing

Testing the MK* Tapes(read only)

Testing the DV* Floppy Disks(read only)

Testing the VGA(Alphanumeric Mode only)

Testing the EW* Network

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

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

P00>>>


Test Command --Description

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

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.

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:

P00>>> set auto_action halt

P00>>> init

 .

 .

 .

P00>>> test

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

The test script tests devices in the following order:

1.	Memory tests (one pass)

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

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

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

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

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


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


show fru Command

Troubleshooting
ROM-Based Diagnostics (RBDs)

show fru

Synopsis:

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

Command:

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

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


show fru Command - Example

Troubleshooting
ROM-Based Diagnostics (RBDs)

Example -- for AlphaServer 2100A Systems

P00>>>show fru

                             Rev                   Events

                                                   Logged

Slot   Option     Part#      Hw  Sw    Serial#     SDD TDD

  0    I/O        B2222-AA   B2  0     KA427P0593  00  00

  2    CPU0       B2020-AA   B2  10    KA426C0457  00  00

  4    MEM0       B2021-BA   A1  0     ML34156292  00  00

Slot   Option                Hose 0, Bus 2, PCI on Primary I/O

Slot   Option                Hose 0, Bus 0, PCI on Primary I/O

  6    DECchip 21050-AA        PCI Option Slot 4

  9    Compaq 1280/P           PCI Option Slot 7

Slot   Option                Hose 0, Bus 1, EISA on Primary I/O

  1    DEC4220

P00>>>


show fru Command

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

CPU modules

Memory modules

I/O modules

For each of the above FRUs, the slot position, option, part, revision, and serial numbers, as well as any reported symptom-directed diagnostics (SDD) and test-directed diagnostics (TDD) event logs are displayed.

In addition, installed PCI and EISA modules are displayed with their respective slot numbers.


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


show fru

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

Slot 0: System backplane

Slot 1--3, 5: CPU modules

Slot 4--7: Memory modules


Option

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


Part#

Part number of option


Rev

Revision numbers (hardware and firmware)


Serial#

Serial number of option


Events Logged

Events logged:

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

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


Switching Between Interfaces

Console Firmware
ROM-Based Diagnostics (RBDs)

Switching Between Interfaces

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

The test command is run from the SRM interface.

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

Switching from SRM to ARC

Switching from ARC to SRM


Switching from SRM to ARC

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

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

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

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

P00>>> set os_type NT

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

4.  Select your operating system, then select the Setup menu and press Enter.

5.  When the "Power-cycle the system to implement the change" message is displayed, press the Reset button.  Once the console firmware is loaded and device drivers are initialized, the SRM console prompt, P00>>>, is displayed.

Once the console firmware is loaded and device drivers are initialized, you can boot the operating system.


Error Log Analysis

Troubleshooting
Error Log Analysis

Fault Detection and Reporting

Machine Check/Interrupts

System Bus Transaction Cycle

Error Logging and Event Log Entry Format

Event Record Translation

Error Log Analysis--Interpreting System Faults


Fault Detection and Reporting

Troubleshooting
Error Log Analysis

PALcode Exception Handling

Fault Detection and Reporting

Component	Fault Detection/Correction Capability
KN4nn Processor Module
DECchip 21064 (EV4), 21064A (EV45), and 21164 (EV5) microprocessors	Contains error detection and correction (EDC) logic for data cycles.  There are check bits associated for all data entering and exiting the microprocessor. A single-bit error on any of the four longwords (or quadwords for EV5 processors) being read can be corrected (per cycle).
Backup cache (B-cache)	EDC check bits on the data store; and parity on the tag store and duplicate tag store and control store.
MS450/MS451 Memory Modules
Memory module	EDC logic protects data by detecting and correcting up to 2 bits per DRAM chip per gate array. The four bits of data per DRAM are spread across two gate arrays (one for even longwords, the other for odd longwords).
System Backplane (Pedestal Systems) or PCI/EISA Backplane (Rackmount Systems)
System backplane or PCI/EISA backplane	SCSI Controller: SCSI data parity is generated. PCI to EISA bridge chip: PCI data parity is generated. PCI to PCI bridge chip: PCI data parity is generated.
System Backplane (Pedestal Systems) or System Bus Backplane (Rackmount Systems)
System backplane or system bus backplane	System bus to PCI bus bridge chip (T3): Longword parity on address and data.


Fault Detection and Reporting

PALcode Exception Handling

Generally, PALcode handles exceptions as follows:

The PALcode determines the cause of the exception.

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

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


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

Troubleshooting
Error Log Analysis

Machine Check/Interrupts

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

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

Processor Machine Check (SCB: 670)

System Machine Check (SCB: 660)

Processor-Corrected Machine Check (SCB: 630)

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


Processor Machine Check

Processor Machine Check (SCB: 670)

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

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

--Uncorrectable B-cache data error

--Uncorrectable memory data error (CU_ERR asserted)

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

A B-cache tag or tag control parity error occurred

Hard error was asserted in response to:

--A system bus read data parity error

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


System Machine Check

System Machine Check (SCB: 660)

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

Fatal errors:

The system backplane or systems bus backplane detected a system bus data parity error while serving as system bus commander:

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

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

--PCI-reported address data or timeout errors

Any system bus device detected a command/address parity error

A bus responder detected a write data parity error

Memory or system bus gate array detected an internal error (SYNC error)

Nonfatal errors:

A memory module corrected data

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

Duplicate tag store parity errors occurred


Processor-Corrected Machine Check

Processor-Corrected Machine Check (SCB: 630)

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


System Bus Transaction Cycle

Troubleshooting
Error Log Analysis

System Bus Transaction Cycle

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

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

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

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

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

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


Error Log Format

Troubleshooting
Error Log Analysis

Error Logging and Event Log Entry Format

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.


Event Record Translation

Troubleshooting
Error Log Analysis

Event Record Translation

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

At product introduction, AlphaServer 2100A systems are not supported by the DECevent Translation and Reporting Utility.


Error Log Analysis---Interpreting System Faults

Troubleshooting
Error Log Analysis

Error Log Analysis---Interpreting System Faults

System faults are isolated by examining translated system error logs or using the DECevent Analysis and Notification Utility.

At product introduction, AlphaServer 2100A systems are not supported by the DECevent Analysis and Notification Utility.


Installing Storage Devices

Removal and Replacement
Installing Storage Devices

SCSI Buses

An onboard, PCI-based controller on the system backplane (pedestal systems) or PCI/EISA backplane (rackmount systems) provides 8-bit (narrow) Fast SCSI-2 support for removable-media devices for pedestal systems or internal SCSI drives (removable and fixed) for rackmount systems.

External SCSI 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 AlphaServer 2100A Supported Options List on the Internet or contact the hardware vendor.

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

http://www.service.digital.com/alpha/server/as2100a/docs.html

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

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

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

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

BA740-B9 Pedestal Systems

Fixed Disk Drives

Removable Media

BA744-A9 Rackmount Systems

Fixed Disk Drives

Removable Media


Internal SCSI Bus, BA740-B9

Installing Storage Devices
BA740-B9 Pedestal Systems

Internal SCSI Bus

The Fast SCSI-2 controller on the system backplane supports the removable-media devices:

Up to three 5.25-in. half-height devices

or

One 5.25-in. full-height device and one 5.25-in. half-height device

This bus can be extended to an internal StorageWorks shelf.

The BA740-B9 pedestal supports up to two 16-bit (wide) internal StorageWorks shelves (option number BA35E-SA) that can each support up to eight SCSI disk drives in a dual-bus configuration.

Installing Removable Media Devices

Extending the Removable Media Bus to an Internal StorageWorks Shelf


Internal SCSI Bus, BA744-A9

Installing Storage Devices
BA744-A9 Rackmount Systems

Internal SCSI Bus

The Fast SCSI-2 controller on the PCI/EISA backplane provides 8-bit (narrow) Fast SCSI-2 support for the internal SCSI drives:

One or two hard disk drives and up to two 5.25-in. half-height removable devices.

Installing Removable Media Devices


Installing Removable Media Devices, BA744-A9

Installing Storage Devices
BA740-B9 Pedestal Systems

Installing Removable Media Devices

This illustration shows how to install 5.25-in. half-height or full-height devices in the removable-media compartment.

Use the screws (4 flat-head screws per drive) that are provided with the system.  The screws are in a plastic bag taped to the unused storage bracket.

Be sure that you set the device's node ID so that there are no duplicates, as each device must have a unique node ID. Nodes 0--6 are available for drives, and node 7 is reserved for the host adapter.  For information on device switch settings, refer to the documentation supplied with the device.


Extending the Removable Media Bus to StorageWorks Shelf, BA740-B9

Installing Storage Devices
BA740-B9 Pedestal Systems

Extending the Removable Media Bus to an Internal StorageWorks Shelf

The removable-media bus can be configured to extend into an internal StorageWorks shelf as follows:

1.	Remove the internal SCSI terminator from the SCSI cable.

2.	Connect the SCSI cable to the StorageWorks backplane.

3.	Connect the terminator and jumper on the internal StorageWorks shelf.

Note:  When the bus is not extended into an internal StorageWorks shelf, the internal SCSI cable terminator is required.


Installing Fixed Disk Drives, BA740-B9

Installing Storage Devices
BA740-B9 Pedestal Systems

Internal SCSI Bus

The Fast SCSI-2 controller on the system backplane supports the removable-media devices:

Up to three 5.25-in. half-height devices

or

One 5.25-in. full-height device and one 5.25-in. half-height device

This bus can be extended to an internal StorageWorks shelf.

The BA740-B9 pedestal supports up to two 16-bit (wide) internal StorageWorks shelves (option number BA35E-SA) that can each support up to eight SCSI disk drives in a dual-bus configuration.

Note:  When the bus is not extended into an internal StorageWorks shelf, the internal SCSI cable terminator is required.

Internal StorageWorks Shelves

Internal StorageWorks Fixed-Disks

Extending the Removable Media Bus to an Internal StorageWorks Shelf


Installing Fixed-Disk Drives, BA744-A9

Installing Storage Devices
BA744-A9 Rackmount Systems

Internal SCSI Bus

The Fast SCSI-2 controller on the PCI/EISA backplane provides 8-bit (narrow) Fast SCSI-2 support for the internal SCSI drives:

One or two hard disk drives and up to two 5.25-in. half-height removable devices.

Installing Fixed-Disk Drives


Configuring Internal StorageWorks Shelves, BA740-B9

Installing Storage Devices
BA740-B9 Pedestal Systems

Internal StorageWorks Shelves

SCSI Cable Routing for Second Internal StorageWorks Shelf

The backplane of the internal StorageWorks shelf supplies the drive's SCSI node ID according to the location of the drive within the storage shelf.  Each internal StorageWorks shelf can be configured in one of two ways: single bus or dual bus.

Alternative SCSI configurations for AlphaServer 2100A pedestal systems are shown below.  The pedestal system does not support 16 devices on a single bus internal to the enclosure.  Check the controller and operating system support for 16 devices external to the pedestal enclosure.

In planning a SCSI configuration, 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.

Supported devices and configuration rules for wide SCSI-2 are described in the Wide SCSI Technical Bulletin.  This bulletin is frequently updated and can be downloaded from the Internet:

http://www.service.digital.com/alpha/server/as2100a/docs/


Cable Routing for Second StorageWorks Shelf, BA740-B9

SCSI Cable Routing for Second Internal StorageWorks Shelf (BA740-B9)


Single Bus StorageWorks Configuration, BA740-B9

Single Bus

Single bus -- Up to seven drives, each with a unique node ID. In this configuration, the bottom slot is not used.

The storage shelf configuration is controlled by the position of the terminator (BA35X-ME) and jumper (BA35X-MF).


Dual Bus StorageWorks Configuration, BA740-B9

Dual Bus

Dual bus -- Up to four pair of drives (node IDs 0--3, top to bottom).

The storage shelf configuration is controlled by the position of the terminator (BA35X-ME) and jumper (BA35X-MF).


Alternative Single Bus StorageWorks Configuration, BA740-B9

Single Bus

In the alternative single bus configuration, the node ID jumper is on any 2 pins (enabled), and the SCSI node IDs are numbered 8--14.


Alternative Dual Bus StorageWorks Configuration, BA740-B9

Dual Bus

In the alternative dual bus configuration, the node ID jumper is on any two pins (enabled), and the SCSI node IDs are numbered 8--11, top to bottom, for both buses.


Hot Swap, BA740-B9

Hot Swapping Drives

If the StorageWorks drives are connected to a StorageWorks Array 200 Subsystem Controller, you can "hot swap" drives, that is, you can install or replace drives without first shutting down the operating system or powering down the system.  The RAID subsystem includes either the KZESC-xx (SWXCR-Ex) EISA or KZPSC-xx (SWXCR-Px) PCI backplane RAID controller.

For information on hot swapping drives, see StorageWorks RAID Array 200 Subsystems Controller Installation and Standalone Configuration Utility Users Guide, EK-SWRA2-IG, provided with the StorageWorks RAID Array 200 Software Kit.

If the StorageWorks drives are not plugged into the RAID subsystems, shut down the operating system before swapping a drive.  However, you do not need to powered down the server before installing the drive.


Installing Fixed Disk Drives, BA740-B9

Installing Storage Devices
BA740-B9 Pedestal Systems

Installing StorageWorks Fixed-Disks -- Pedestal (BA740-B9)

If the StorageWorks drives are connected to a StorageWorks Array 200 Subsystem Controller, you can "hot swap" drives, that is, you can install or replace drives without first shutting down the operating system or powering down the system.

Installation Procedure:

1.	If the StorageWorks drives are plugged into the RAID subsystem, go to step 2.  If your drives are not plugged into the RAID subsystem, shut down the operating system before you go to step 2.

2.	Remove a blank bezel by pressing the two mounting tabs and pull the bezel out of the shelf.

3.	Insert the hard-disk drive into the guide slots and push it in until the tabs lock in place.


Installing Removable Media Devices, BA744-A9

Installing Storage Devices
BA744-A9 Rackmount Systems

Installing Removable Media Devices

This illustration shows how to install 5.25-in. half-height devices in the removable-media compartment.  Use the screws (M3 x 6 mm, flathead) supplied in the accessories kit to mount the drives.

Be sure that you set the device's node ID so that there are no duplicate node IDs, as each device must have a unique node ID. Nodes 0--6 are available for drives, and node 7 is reserved for the host adapter.  For information on device switch settings, refer to the documentation supplied with the device.

Note:  RRDnn and TLZ0n drives use the set of bracket holes marked "A."  The TZK11 drive uses the set of bracket holes marked "B."


Installing Fixed-Disk Drives, BA744-A9

Installing Storage Devices
BA744-A9 Rackmount Systems

Installing Fixed-Disks

To install a hard-disk drive:

1.	Mount four rubber grommets provided in the accessories kit to the drive.

2.	Install drive.

Be sure that you set the device's node ID so that there are no duplicate node IDs, as each device must have a unique node ID.  Nodes 0--6 are available for drives, and node 7 is reserved for the host adapter.  For information on device switch settings, refer to the documentation supplied with the device.


Installing Mass Storage Devices: Guidelines and Warnings, BA740-B9

Caution: Before opening or removing system panels:

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

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

continue......


Installing Mass Storage Devices: Guidelines and Warnings, BA744-A9

Caution: Before opening or removing system panels:

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

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

continue......


Installing Mass Storage Devices: Guidelines and Warnings, BA744-A9

Warning: Before accessing enclosure compartments:

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

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

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

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

continue......


Installing Mass Storage Devices: Guidelines and Warnings, BA744-A9

Warning: Before accessing enclosure compartments:

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

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

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

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

continue......


Exit

Do you want to exit this application?


Notices

V1 March 1996

Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.

Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor.

Copyright  Digital Equipment Corporation, 1996.  All Rights Reserved.

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

Digital UNIX Version 3.0 is and X/Open UNIX 93 branded product.  Microsof Windows NT is a trademark of Microsoft Corp.  All other trademarks and registered trademarks are the property of their respective holders.

FCC NOTICE: The equipment described in this manual generates, uses, and may emit radio frequency energy.  The equipment has been type tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such radio frequency interference when operated in a commercial environment.  Operation of this equipment in a residential area may cause interference, in which case the user at his own expense may be required to take measures to correct the interference.

Information Services

Contributors


Contributors

Oleg Klimowicz - Illustrator

Andrea Thurber - Graphic Designer/Illustrator

Rich Trubey - Writer/Designer

Cheryle West - Interface /Graphic 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 backplane, you need to update the system firmware.  An Alpha Firmware CD-ROM is shipped on an as released bases with Digital UNIX, OpenVMS, an 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/

http://www.service.digital.com/alpha/server/firmware/

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-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 for managing AlphaServer 2100A systems.

FTP Address:

ftp.digital.com

cd /pub/Digital/Alpha/systems

World Wide Web address:

http://www.service.digital.com/alpha/server/

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


Supported Options

Refer to the AlphaServer 2100A 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/as2100/docs/

World Wide Web address:

http://www.service.digital.com/alpha/server/as2100/docs.html

You can obtain information about hardware configurations for the AlphaServer 2100A from the Digital Systems and Options Catalog.  The catalog is regularly published to assists in ordering and configuring systems and hardware options.  Each printing of the catalog presents all of the 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/


Training

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

AlphaServer 2100 Installation and Troubleshooting: EY-M915E

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


Searching for a Word or Phrase

Navigating Hints

Searching for a Word or Phrase

To search for topics that contain a certain word or phrase:

1	Choose the Search button in the application window.

2	In the Search For box, type the text topic you are searching for.

Tip:  You can choose the Hints button in the Search dialog box for examples of search queries.

3	Under Look At, select Topic Titles Only to search only each topic title, or select All Text to search all the text in each topic.

4	Choose the Search button.

The application lists the title of each topic that contains a search hit in the Topics Found window.


Using Buttons

Navigating Hints

Using Buttons

The following buttons appear at the top of the screen.  The table below lists the buttons and their functions:

Button	Function
	Returns to the first screen of the program.
	Keyword search.  Searches by predetermined keywords.
	Backs up one screen.
	Provides full-text search.  Searches the program's content for the word or phrase you type.
	Lists the screens that you have accessed.
	Contains helpful navigating hints.
	Contains a list of glossary terms
	Browses to next topic.
	Browses to previous topic.


Main Menu

The Main Menu screen displays the buttons for each section of the Digital 2100 Server Fast Track to Information.  You can click on any of these buttons to access information for that topic.


Navigating Hints

History Button

Using the History Button


Navigating Hints

Using the History Button

To jump back to a topic by using the History button:

1	Choose the History button in the application window.

The application lists the last 40 topics you have viewed in the History window.  Topics that are not in the open book are prefixed by an abbreviation of their book name.

2	Double-click on the topic you want to view.

Use the scroll bar to see topics not visible in the list.

3	The History window goes to the background.  You can choose the History button again to bring it to the front, and then choose another topic.  You can also resize or move the History window.

Tip: You may want to arrange the application window and the History window so that they are side by side.

To close the History window:

Double-click on the Control menu box in the History window.


Navigating Hints

Index

Looking Up Topics in the Index


Navigating Hints

Looking Up Topics in the Index

To look up a topic using the index:

1	Choose the Index button in the application window.

2	Type the word you want to search for or select the word from the list.

You can press a key on your keyboard to move quickly to different parts of the list.  For example, type "S" to move to words beginning with the letter "S" and then type "O" to see words beginning with "So."

3	Choose the Show Topics button.

The application lists the topics that are linked to the word you entered or selected.

4	Double-click on the topic you want to view or select the topic and choose the Go To button.

Use the vertical scroll bar to see topics not visible in the list.

Tip:  Double-click on a word to list the related topics automatically.


Navigating Hints

Search Menu

Searching for a Word or Phrase


The hand symbol indicates there is more information in the topic.  Click on the hand symbol pointing right to browse forward in the topic.


The hand symbol indicates there is more information in the topic.  Click on the hand symbol pointing left to browse backward in the topic.


Using "file folder" Tabs

Navigating Hints

Using "Folder" Tabs

Folder tabs allow you to quickly navigate between sections.


Using the Map

Navigating Hints

Using the Map

The map allows you to quickly navigate between sections.


Using the Scroll Bar

Navigating Hints

Using the Scroll Bar

A scroll bar to the right of the screen indicates that there is more information for that topic. Click and drag the scroll bar down to see the additional information.  Click and drag the scroll bar up to backtrack.